Version
6.10
Operating System
Linux/Unix
Bug description
In a high traffic gerrit environment we are observing rare cases when refs get rewinded.
Actual behavior
In high traffic gerrit environment when multiple actions happen on a change, possibly a comment/vote and them submitting the change, We did see through our logs that meta ref did update to point to new commit created using submit strategy and then was rewinded to reflect the other meta ref update.
Expected behavior
Concurrent updates should either fail with a lock failure or should be applied in correct order.
Relevant log output
Other information
No response
Version
6.10
Operating System
Linux/Unix
Bug description
In a high traffic gerrit environment we are observing rare cases when refs get rewinded.
Actual behavior
In high traffic gerrit environment when multiple actions happen on a change, possibly a comment/vote and them submitting the change, We did see through our logs that meta ref did update to point to new commit created using submit strategy and then was rewinded to reflect the other meta ref update.
Expected behavior
Concurrent updates should either fail with a lock failure or should be applied in correct order.
Relevant log output
Other information
No response