Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Memcache extension appears to always have expiretime=None #18

Open
rorygrandin opened this issue May 18, 2012 · 1 comment
Open

Memcache extension appears to always have expiretime=None #18

rorygrandin opened this issue May 18, 2012 · 1 comment

Comments

@rorygrandin
Copy link

This appears to be because in container.py, when calling set_value on the namespace manager, no expiretime is passed through, just a tuple that contains the expire_argument.

@cangove
Copy link

cangove commented Jan 25, 2013

This seems to be because of how timeouts are now handled in beaker. The timeout is handled inside the Beacker container code where it does the expiration timeouts and not in the plugins. Therefore memcached will not set the timeout and the cache will continue to grow. Kind of painful and causes all kinds of problems in our setup.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants