Opened 5 years ago
Closed 5 years ago
#30454 closed Cleanup/optimization (invalid)
doc error about "Cache key prefixing".
| Reported by: | Bilige MengDe | Owned by: | nobody |
|---|---|---|---|
| Component: | Documentation | Version: | dev |
| Severity: | Normal | Keywords: | Cache key prefixing |
| Cc: | Triage Stage: | Unreviewed | |
| Has patch: | no | Needs documentation: | no |
| Needs tests: | no | Patch needs improvement: | no |
| Easy pickings: | no | UI/UX: | no |
Description
native sentence is "If the format of cached data is different between servers, this can lead to some very hard to diagnose problems."
but I think "cache key prefixing" is used for distinguish between servers cache, so the doc may be "If the format of cached data is SAME between servers, this can lead to some very hard to diagnose problems."
doc url is : https://docs.djangoproject.com/zh-hans/2.2/topics/cache/#cache-key-prefixing
Change History (2)
comment:1 by , 5 years ago
| Component: | Uncategorized → Documentation |
|---|---|
| Type: | Uncategorized → Bug |
comment:2 by , 5 years ago
| Resolution: | → invalid |
|---|---|
| Status: | new → closed |
| Summary: | doc error about "Cache key prefixing" → doc error about "Cache key prefixing". |
| Type: | Bug → Cleanup/optimization |
| Version: | 2.2 → master |
Note:
See TracTickets
for help on using tickets.
Current sentence sounds good for me:
i.e. if you are sharing a cache instance between servers ... and the format of cached data is different between servers, this can lead to some very hard to diagnose problems. It is just another reason to use a different
KEY_PREFIX.