-
Notifications
You must be signed in to change notification settings - Fork 77
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
bugfix: fix a typo in chash.reinit #25
Conversation
`newnodes` should be assigned to `self.nodes` rather than `self.newnodes`.
@doujiang24 Will you have a look at this? Thanks. |
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.
@ArchangelSDY nice catch, will you please add a test case for it?
@doujiang24 Sure, updated. |
@ArchangelSDY Thanks a lot :) |
@doujiang24 Could you merge this PR and tag a new release so that we can pick this change in downstream projects? |
@ArchangelSDY |
This fixes bug in chash:reinit which prevents endpoints from being updated correctly. See openresty/lua-resty-balancer#25
What's the impact of this bug? As long as a user you aren't relying on nodes to be in sync (covered at https://github.com/openresty/lua-resty-balancer/pull/25/files#diff-cad7d8fbdf9d2fb89f5ee95f0b73dff7R338), there should not be any issue, right? |
That's right as long as you don't need to read |
newnodes
should be assigned toself.nodes
rather thanself.newnodes
.