Details
-
New Feature
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Fixed
-
None
-
None
-
MXS-SPRINT-184, MXS-SPRINT-185
Description
As described in MXS-4214, there's a need to have finer control over when the schemarouter caches are emptied as the act of populating the cache causes a one-time increase in query latency.
Being able to manually clear the cache, both globally and for a single user, would make it easier to manage when the expensive work of loading the database and table information takes place.
Attachments
Activity
| Field | Original Value | New Value |
|---|---|---|
| Assignee | Todd Stoffel [ toddstoffel ] |
| Attachment | schemarouter-clear-caches.patch [ 65260 ] |
| Rank | Ranked higher |
| Fix Version/s | Icebox [ 22648 ] |
| Fix Version/s | 23.08 [ 28436 ] | |
| Fix Version/s | Icebox [ 22648 ] |
| Assignee | Todd Stoffel [ toddstoffel ] | markus makela [ <markus.makela ] |
| Fix Version/s | Icebox [ 22648 ] | |
| Fix Version/s | 23.08 [ 28436 ] | |
| Assignee | markus makela [ <markus.makela ] | Todd Stoffel [ toddstoffel ] |
| Fix Version/s | 23.08 [ 28436 ] | |
| Fix Version/s | Icebox [ 22648 ] |
| Rank | Ranked lower |
| Assignee | Todd Stoffel [ toddstoffel ] | markus makela [ <markus.makela ] |
| Sprint | MXS-SPRINT-184 [ 720 ] |
| Rank | Ranked lower |
| Status | Open [ 1 ] | In Progress [ 3 ] |
| Status | In Progress [ 3 ] | In Review [ 10002 ] |
The command should also allow the cache to be marked a stale instead of clearing it completely. This way the cache can still be used if max_staleness is set to a high value.
| Sprint | MXS-SPRINT-184 [ 720 ] | MXS-SPRINT-184, MXS-SPRINT-185 [ 720, 723 ] |
| Fix Version/s | 23.08.0 [ 28440 ] | |
| Fix Version/s | 23.08 [ 28436 ] | |
| Resolution | Fixed [ 1 ] | |
| Status | In Review [ 10002 ] | Closed [ 6 ] |
| Zendesk Related Tickets | 146212 |
I needed this for testing of some other stuff so I wrote a patch for it (attached to the issue).