Details
-
Bug
-
Status: Closed
-
Major
-
Resolution: Fixed
-
2.1.1-beta
-
None
-
Reviewed
Description
Only nodes in the RUNNING state are tracked by schedulers. When a node reconnects, RMNodeImpl.ReconnectNodeTransition tries to remove it, even if it's in the RUNNING state. The FairScheduler doesn't guard against this.
I think the best way to fix this is to check to see whether a node is RUNNING before telling the scheduler to remove it.