-
Notifications
You must be signed in to change notification settings - Fork 3.7k
[Doris On ES][Bug-Fix] ES queries always route at same 3 BE nodes (#4351) #4352
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
Conversation
| if (usingRandomBackend) { | ||
| for (int i = 0; i < numBe; ++i) { | ||
| candidateBeList.add(backendList.get(beIndex++ % numBe)); | ||
| candidateBeList.add(backendList.get(beIndex++ % backendList.size())); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
| candidateBeList.add(backendList.get(beIndex++ % backendList.size())); | |
| candidateBeList.add(backendList.get(beIndex++ % size)); |
obtain size = backendList.size() in other place
wuyunfeng
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This Looks good to me, but I left some minor comment
|
I've obtained size = backendList.size() in the front of loop. Is it better? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It would be nice to add some UT to cover this case, but writing this is a bit complicated for you. At this time I would +1 and merge this PR soon. Thanks.
…ache#4351) (apache#4352) resolve the problem of querying ES table always route at same 3 BE nodes because of random strategy
Fix Issue:
#4351