-
Notifications
You must be signed in to change notification settings - Fork 90
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
Comments
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. |
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? |
@a-nldisr Yes |
thnx |
Fixed in #302 |
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.
The text was updated successfully, but these errors were encountered: