Feature switches don't immediately take effect

[Wes Winham]

Does anyone else see a lag before their condition changes take effect? We run across multiple app servers with 2 apache/mod_wsgi processes per server, and when we make changes through the admin, they don't seem to take effect until we restart apache. 

At first I just assumed this was by design, but today I looked at the ModelDict code, and I had the impression that cache invalidation was the goal. So now I'm asking if this is a bug, by design, or if maybe there's something specific to my environment that's causing what we're seeing.

Thanks

-Wes

[David Cramer]

That's definitely not how it's designed to act. How do you have your processes setup through Apache?

-- 
David Cramer

twitter.com/zeeg

disqus.com/zeeg

[Wes Winham]

Our current WSGIDaemonProcess setting:

WSGIDaemonProcess example.com user=example threads=4 processes=2

 

Would the fact that we have the default cache timeout set to 30 days matter?

CACHE_TIMEOUT = 24 * 60 * 60 * 30 # 30 days

Also, we're not running on the latest version. I checked the closed issues to see if this was something fixed, but nothing caught my eye. We're on 0.1.2

-Wes