#35516: Setting Client Name for Redis Connections
-------------------------------+--------------------------------------
Reporter: Aswin1105 | Owner: nobody
Type: Uncategorized | Status: new
Component: Uncategorized | Version: 5.0
Severity: Normal | Resolution:
Keywords: | Triage Stage: Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------+--------------------------------------
Comment (by Aswin1105):
You are correct, Whatever cache back-end they use, I think if it is
external, it will be a good practice to name the connections established.
For other backends, i think it wont create any harm in sending extra
parameters?, until we are using some external package for supporting that
(like in the case REDIS, django-redis).
Also, another case, even for a single service, redis can be connected
through different means like channel-redis has its own connection and
core.cache has its own connection. These different connections can be
differentiated and analysed if we name them.
The reason, why am i enforcing this change is that, i have made multiple
django services, each having same redis as a the cache backend. I faced
problem, when connection closed by server happened. I tried to find which
service is having stale connections or too many connections etc. But i
couldnt as these connections are unnamed.
But thanks for the reply and i accept it too. Also, if you feel the change
is unnecessary, u can close it. But i think the common cache backend in
production in Redis. So it may need this feature.
--
Ticket URL: <https://code.djangoproject.com/ticket/35516#comment:2>
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 [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/01070190024d863c-da1c0157-f00e-4f95-9a06-bbc3fb62052c-000000%40eu-central-1.amazonses.com.
