[YUNIKORN-1065] panic in nodeUpdate when node disappears

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 1.0.0
• Component/s: core - scheduler
• Labels: pull-request-available
• Target Version: 1.0.0
• Assignee: Wilfred Spiegelenburg
• Reporter: Wilfred Spiegelenburg
• Created: 31/Jan/22 23:46
• Updated: 04/May/22 23:52
• Resolved: 01/Feb/22 15:31

Description

Based on a message in the chat channel:

panic: runtime error:
invalid memory address or nil pointer dereference signal SIGSEGV:
segmentation violation code=0x1 addr=0x0 pc=0x9f4da0]
goroutine 16 [running]: github.com/apache/incubator-yunikorn-core/pkg/scheduler.(*ClusterContext).updateNode(0xc00014d2c0, 0xc020451f10)   
  /go/pkg/mod/github.com/apache/incubator-yunikorn-core@v0.0.6/pkg/scheduler/context.go:620 +0x3a0 
github.com/apache/incubator-yunikorn-core/pkg/scheduler.(*ClusterContext).processNodes(0xc00014d2c0, 0xc0213e0410)
 /go/pkg/mod/github.com/apache/incubator-yunikorn-core@v0.0.6/pkg/scheduler/context.go:230 +0x405 
github.com/apache/incubator-yunikorn-core/pkg/scheduler.(*ClusterContext).handleRMUpdateNodeEvent(...) 
 /go/pkg/mod/github.com/apache/incubator-yunikorn-core@v0.0.6/pkg/scheduler/context.go:206

 

Thanks to Ben Roubicek for finding this

Issue Links

• links to: GitHub Pull Request #366