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

Wipe configchecksums also on assignment changes (backport) #357

Merged
merged 2 commits into from
Apr 1, 2019

Conversation

mpfz0r
Copy link
Contributor

@mpfz0r mpfz0r commented Apr 1, 2019

If an assignment is changed to switch a backend from
one configuration to another, we would still send configuration requests
using the old checksum.
The server will respond with NotModified and we don't try to restart
the backend.

Instead of also resetting the checksum when we update the assignment
store, simply wipe the entire checksum map if either the assignment
or the backends have changed.

Fixes #352

Also bump version to 1.0.1

mpfz0r added 2 commits April 1, 2019 14:44
If an assignemnt is changed to switch a backend from
one configuration to another, we would still send configuration requests
using the old checksum.
The server will respond with `NotModified` and we don't try to restart
the backend.

Instead of also resetting the checksum when we update the assignment
store, simply wipe the entire checksum map if either the assignment
or the backends have changed.

Fixes #352

(cherry picked from commit dca0b17)
@mariussturm mariussturm merged commit 09e30f3 into 1.0 Apr 1, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants