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.

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

Jump to bottom

Cannot unmerge users reliably: EFFECTIVE_ID_CACHE may be inconsistent #4

Open
dpoon opened this issue Jun 21, 2016 · 1 comment
Open

Cannot unmerge users reliably: EFFECTIVE_ID_CACHE may be inconsistent #4

dpoon opened this issue Jun 21, 2016 · 1 comment

Comments

@dpoon
Copy link

dpoon commented Jun 21, 2016 •
edited
Loading

%EFFECTIVE_ID_CACHE is flushed whenever a user is merged or unmerged.

If Request Tracker runs on a server farm of web servers, or on certain Apache MPMs, then one process would be unaware when a merge/unmerge happens via another. The cache inconsistency can cause weird behaviour, like unmerge operations that appear to succeed, but modifications to one user still show up on the other.

The cache is also flushed every 100 requests, which is too infrequent to prevent cache inconsistency.

The %EFFECTIVE_ID_CACHE should either be eliminated altogether or be flushed on every request.
@dpoon dpoon changed the title EFFECTIVE_ID_CACHE does not play well with load balancers Cannot unmerge users reliably: EFFECTIVE_ID_CACHE may be inconsistent Jun 21, 2016
@dpoon
Copy link
Author

dpoon commented Jun 21, 2016

Also filed this bug report as https://rt.cpan.org/Ticket/Display.html?id=115495

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@dpoon