#16358: cached_db session with memcached forgets big values
-------------------------------------+-------------------------------------
Reporter: ccrisan | Owner: manfre
Type: Bug | Status: closed
Component: Core (Cache system) | Version: master
Severity: Normal | Resolution: fixed
Keywords: session cache | Triage Stage: Ready for
memcached | checkin
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Michael Manfre <mmanfre@…>):
* status: assigned => closed
* resolution: => fixed
Comment:
In [changeset:"bc8abe36ba5508fe788f6d49a26749268d368583"]:
{{{
#!CommitTicketReference repository=""
revision="bc8abe36ba5508fe788f6d49a26749268d368583"
Fixed #16358 - Made memcache backend delete old value on a failure to set.
Default Memcached configuration allows for a maximum object of 1MB and
will fail to set the key if it is too large. The key will be deleted from
memcached if it fails to be set. This is needed to avoid an issue with
cache_db session backend using the old value stored in memcached, instead
of the newer value stored in the database.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/16358#comment:8>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/065.ded0da01750b0576a92dec0107dc8cb2%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
