-
Enhancement
-
Resolution: Done
-
Major
-
None
-
None
Today, when using a shared store the cluster publisher will still send requests by which node owns what segments (determined by topology). Instead we should prefer just staying on the local node instead of going remote when a shared store is present.
We also can lower the delivery guarantee when invoking an operation on the local node to AT_LEAST_ONCE for segments we know we will always have (example REPL or shared store).
- causes
-
ISPN-15758 Publisher should fetch data from remote nodes with SKIP_CACHE_LOAD
- Resolved
-
ISPN-14860 Verify reindex performances when a SQL query cache store is configured
- Resolved