Details
-
New Feature
-
Status: Open (View Workflow)
-
Major
-
Resolution: Unresolved
-
None
-
None
-
None
-
None
-
2026-2
Description
as a user I would like known errors surfaced sooner rather than waiting till an outage, failed failover, wrong master selected, broken replication etc. to begin digging into the logs.
Today if the user doesnt configure a cross engine user, columnstore assumes every node in a cluster is primary.
get_primary returns {'is_primary': 'True'} |
Which can lead to wrong dbroot assignments , wrong primary node and bad failovers.
When starting columnstore via cmapi with "mcs start" and a cluster is configured, start should fail with an error output that cross engine credentials dont work
ERROR: ColumnStore failed to start due to invalid or missing Cross-Engine credentials, which is required for clustered installs |