Labels: Type-Defect Priority-Medium
New issue 986 by marc.bee: Multiple instance of reviewboard on the same
server causes troubles with a cache mechanism
*NOTE: Do not post confidential information in this bug report.*
What's the URL of the page containing the problem?
What steps will reproduce the problem?
1. run memcached -v -vv
2. run two instances of review board by manage.py for instance
3. access to any page and have a look the the memcached output
What is the expected output? What do you see instead?
whatever the site you will access, the key used for the configuration
settings will always be:
What operating system are you using? What browser?
Please provide any additional information below.
In fact, there is a solution: having a separate memcached daemon for each
instance of django applicative server who uses the djblets.
But is it really accurate?
The problem comes from djblets.siteconfig.models, line 118.
Do you think that including the web root or web complete url to build the
key should be a better idea than one instance of memcached per reviewboard?
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
You received this message because you are subscribed to the Google Groups
To post to this group, send email to firstname.lastname@example.org
To unsubscribe from this group, send email to
For more options, visit this group at