Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

After reconcillication, GUI does not show true state of cluster #206

Closed
philwinder opened this issue Aug 6, 2015 · 5 comments
Closed

After reconcillication, GUI does not show true state of cluster #206

philwinder opened this issue Aug 6, 2015 · 5 comments
Assignees
Labels
Milestone

Comments

@philwinder
Copy link
Contributor

The introduced cluster management code does not update the GUI Task data structure, because some fields are not available when reconciling. E.g. the slave IP address is not available.

We need to consider removing items that are not available to the scheduler at reconcillication time. E.g. the IP address of the slave.

If they are important then we need to implement custom code to pass those details from the executors.

  • Scheduler death: GUI will show zero tasks
  • Executor death: GUI will show n + 1 tasks, since the task is not removed from the task list.
@frankscholten frankscholten modified the milestone: Backlog Aug 20, 2015
@philwinder philwinder added the bug label Aug 24, 2015
@philwinder
Copy link
Contributor Author

Could initialize com.sonian.elasticsearch.zookeeper.discovery.ZooKeeperClusterState in the scheduler to read the ES state written by ES-zookeeper-discovery? Then we should be able to parse the hostname and ports from Elasticsearch's DiscoveryNode.

This is probably the best idea, because the data is already there and required for the ES discovery mechanism. However, this does couple the scheduler code to ES/ES-Zookeeper. Should seperate the code out from the scheduler as much as possible.

This should result in minimal changes to the web GUI.

@a-nldisr
Copy link

a-nldisr commented Sep 2, 2015

Is my assumption correct that this is related to when an executor fails and rescheduled, this failed executor is still listed in the dropdown list on the GUI?

@frankscholten frankscholten modified the milestones: 0.3.1, Backlog Sep 8, 2015
@frankscholten
Copy link
Contributor

@a-nldisr Yes

@a-nldisr
Copy link

thnx

@philwinder
Copy link
Contributor Author

Fixed in #302

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

4 participants