disqus / gargoyle

Feature switches in Django
http://engineering.disqus.com
Apache License 2.0
746 stars 112 forks source link

Faulty switch behavior between multiple processes #69

Open pianojet opened 11 years ago

pianojet commented 11 years ago

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.