Details
-
New Feature
-
Status: In Progress (View Workflow)
-
Critical
-
Resolution: Unresolved
-
None
-
2025-4, 2025-6, 2025-7, 2025-8
Description
This project solves horizontall scale problem to increase read-only QPS in real-time by adding more nodes.
As of 23.02 MCS can't add read-only nodes sharing the same data between the nodes neither for S3, nor for distributed File Systems or block device technologies.
The topology would consist of 3 major elements:
- MaxScale proxy to Load Balance read-only requests between read-only nodes and route DML/DDL to the read-write node
- Read-write node that "owns" dbroot/-s with data
- Multiple read-only nodes that doesn't run WE or "own" dbroot/-s.
The problems to solve:
- add declarative description for a set of read-only nodes into Columnstore.xml
- teach CMAPI how to add a node with read-only role into a cluster
- handle read-only ownership in StorageManager for S3 installations
Attachments
Issue Links
- includes
-
MCOL-6018 ASAN memory leaks and UBSAN in plugin
-
- In Progress
-
- is blocked by
-
MCOL-5861 Read-only Columnstore node
-
- In Progress
-
- relates to
-
MCOL-5962 Fix rollback in mcs cli and passing errors during broadcasting config.
-
- Closed
-
-
MCOL-5996 Cmapi+ Multinode Failover tests infrastructure
-
- Closed
-
-
MCOL-6160 Read replica with S3
-
- Open
-
-
MCOL-6169 Support creating POSIX shared storage in columnstore-ansible-aws
-
- In Review
-
- mentioned on