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

Bug fix/user manager version race (#14382) #14392

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 5 commits into from
Jun 22, 2021
Merged

Bug fix/user manager version race (#14382) #14392

Changes from 1 commit
Commits
Show all changes
5 commits
Select commit Hold shift + click to select a range
c187f30
Bug fix/user manager version race (#14382)
mchacki Jun 22, 2021
6a085aa
Merge remote-tracking branch 'origin/3.7' into bug-fix-3.7/user-manag…
mchacki Jun 22, 2021
ba1e41e
Moved Changelog entry to correct place
mchacki Jun 22, 2021
d6c105d
Ifdefed testonly method
mchacki Jun 22, 2021
ceb420a
Update CHANGELOG
KVS85 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
Update CHANGELOG
  • Loading branch information
@KVS85
KVS85 authored Jun 22, 2021
commit ceb420a5ba41393412889a35cf285a745a1fcba5
14 changes: 7 additions & 7 deletions CHANGELOG
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,16 +1,16 @@
v3.7.13 (XXXX-XX-XX)
--------------------

* Fixed reloading of users within the Cluster.
* Fixed ES-863: reloading of users within the Cluster.
If a Coordinator is asked to reload its 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 it is used), in concurrency 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
of any other users/permissions. Unfortunately this bug can cascade and when
hit again, the coordinator can now be off by two updates.
In DC2DC this situation is more likely to happen on the target datacenter,
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 of any other users/permissions. Unfortunately this bug can
cascade and when hit again, the coordinator can now be off by two updates.
In DC2DC this situation is more likely to happen on the target datacenter,
causing this datacenter to have other users/permissions than the source one.

* Fix BTS-446: When finding a not yet fully initialized agency, do not
Expand Down
0