Changes between Initial Version and Version 1 of Ticket #29203, comment 10


Ignore:
Timestamp:
03/22/2018 10:50:35 AM (3 years ago)
Author:
Kenial Sookyum Lee
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #29203, comment 10

    initial v1  
    66> As far as I know, Django generally [https://github.com/jazzband/django-constance/issues/236#issuecomment-346974084) requires the cache to be available]. It might be that we should document this requirement and discourage use of the "ignore connection timeout exception" option that you mentioned.
    77
    8 Agreed. But, the thing is, cache downtime itself is inevitable. As I told you, I found out this bug when I test failover AWS Elasticache - it means, this can happen during any kind of cache backend failover scenario. If "CAUTION: failover of cache backend might cause termination of Django sessions unintentionally" is in documentation, well... It sounds awkward.
     8Agreed. But, the thing is, cache downtime itself is inevitable. As I told you, I found out this bug when I tested failover scenario of AWS Elasticache - it means, this can happen during any kind of cache backend failover scenario. If "CAUTION: failover of cache backend might cause termination of Django sessions unintentionally" is in documentation, well... It sounds awkward.
Back to Top