Skip to content

Cannot unmerge users reliably: EFFECTIVE_ID_CACHE may be inconsistent #4

Open
@dpoon

Description

@dpoon

%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.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions