[MXS-4554] route the first select after insert on a columnstore table to master Created: 2023-03-10 Updated: 2023-04-13 Resolved: 2023-03-15 |
|
| Status: | Closed |
| Project: | MariaDB MaxScale |
| Component/s: | N/A |
| Affects Version/s: | None |
| Fix Version/s: | N/A |
| Type: | New Feature | Priority: | Major |
| Reporter: | Richard Stracke | Assignee: | Todd Stoffel (Inactive) |
| Resolution: | Won't Do | Votes: | 0 |
| Labels: | None | ||
| Issue Links: |
|
||||||||
| Description |
|
With enabled "insert cache" on columnstore the changes are not visible on the replicas Therefore Maxscale should forward the first select after an insert to the master node on a "Accumulated inserts are flushed into columnstore on various events (all non inserts, including SELECT - and settable size threshold defaulted to 500,000 rows in the cache)." https://mariadb.com/docs/columnstore/ref/mdb/system-variables/columnstore_cache_use_import/ |
| Comments |
| Comment by markus makela [ 2023-03-10 ] |
|
I think you can do this with the ccrfilter module: https://mariadb.com/kb/en/mariadb-maxscale-2208-consistent-critical-read-filter/ |
| Comment by Todd Stoffel (Inactive) [ 2023-03-15 ] |
|
markus makela This is not a MaxScale ticket per se. We should probably close this. We'll defer to the original ticket https://jira.mariadb.org/browse/MCOL-5038 |