8000 Bug fix/user manager version race by mchacki · Pull Request #14382 · arangodb/arangodb · GitHub
[go: up one dir, main page]
Skip to content

Bug fix/user manager version race #14382

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.

Sign up for GitHub

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

Merged
merged 6 commits into from
Jun 22, 2021
Merged

Bug fix/user manager version race #14382

Changes from 1 commit
Commits
Show all changes
6 commits
Select commit Hold shift + click to select a range
5e66a04
Added first test for user manager in cluster. I am very unpleased by …
mchacki Jun 17, 2021
40c2e22
Added Changelog entry
mchacki Jun 17, 2021
05000db
Implemented the fix for UserManager skipping a version
mchacki Jun 17, 2021
c8a70cc
Added some more tests around user manager
mchacki Jun 17, 2021
2ee7dbb
Fixed typos in CHANGELOG
mchacki Jun 18, 2021
353b6ab
Update CHANGELOG
mchacki Jun 22, 2021
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Prev Previous commit
Next Next commit
Added Changelog entry
  • Loading branch information
@mchacki
mchacki committed Jun 17, 2021
commit 40c2e22e35554df83cc4aa20c075d8865a42ac3c
14 changes: 14 additions & 0 deletions CHANGELOG
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,6 +1,20 @@
devel
-----

* Fixed reloading of users within the Cluster
If a Coordinator is asked to reload it's users (e.g. by the UserManager in
Foxx, it is also possible to do via API, but this is internal and on purpose
not documented, so unlikely that you hit this), in concurency with user
management updates there is a chance that the reload is not correctly performed
on this coordinator. It may have missed the last update locally, causing
one user to have an older state. It will be fixed on the next modification
on any other users rights. Unfortunately this bug can cascade, if you are
in a bug situation, and hit the same bug again, this coordinator is now
off by two updates.
In DC-2-DC this situation is more likely to happen on the follower
datacenter, causing this datacenter to seemeingly having other rights
then the main one.

* Slightly improve specific warning messages for better readability.

* Fix URL request parsing in case data is handed in in small chunks.
Expand Down
0