KYLIN-4295 Instances displayed on Query Node are inconsistent with JobNode #1014
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Query Node can't get allParticipants because query node no need to run job scheduler, so the jobClient is null.
Job Node:
Query Node:
We can add instance of the mode equals ‘job’ or ‘all’ to job node list in query server, but query server can not find which job node is Leader. In order to avoid instance page display a leader as a follower by mistake, just display the Leader of job node as Job Node (Leader), the others display as Job Node.
Job Node:
Query Node: