You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jun 20, 2018. It is now read-only.
When setting WSGIDaemonProcess process=[>1], the updated memcache that refreshes when changing switch status is only visible with one process. For example, as far as resulting behavior, in an environment where WSGIDaemonProcess process=2, every other page request will appear to have the correct updated switch status (process used goes back-and-forth between the process with correctly refreshed memcached switch status and the other process oblivious to the switch update). Restarting apache refreshes memcache for all processes, however this is not a sustainable approach given the intended usage of switches.
I noticed a setting "GARGOYLE_CACHE_NAME" in the switch manager. Same faulty behavior exists when designating a cache for this setting. No documentation seems to exist for any of this.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
When setting WSGIDaemonProcess process=[>1], the updated memcache that refreshes when changing switch status is only visible with one process. For example, as far as resulting behavior, in an environment where WSGIDaemonProcess process=2, every other page request will appear to have the correct updated switch status (process used goes back-and-forth between the process with correctly refreshed memcached switch status and the other process oblivious to the switch update). Restarting apache refreshes memcache for all processes, however this is not a sustainable approach given the intended usage of switches.
I noticed a setting "GARGOYLE_CACHE_NAME" in the switch manager. Same faulty behavior exists when designating a cache for this setting. No documentation seems to exist for any of this.
The text was updated successfully, but these errors were encountered: