Closed dcvan24 closed 6 years ago
The issue is caused mainly because the agent
parameter of the scheduler
in the custom local scheduler is overridden. The fix does not prevent the custom scheduler from overriding the parameters and causing the issue. Cautions have been added to the abstract class.
The local scheduler observes inconsistent agents between different scheduling calls, even the agents are not changed and consistently returned from the calls to the Mesos API. For instance, there are 9 agents up and running in the cluster, but the local scheduler sometimes only observes 1 agent up and running.