[MXS-3376] More control over primary node for columnstore 5.x Created: 2021-01-15  Updated: 2021-05-02  Resolved: 2021-01-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: Richard Stracke
Resolution: Won't Do Votes: 0
Labels: None

Issue Links:
Relates
relates to MCOL-4427 broken function: possibility to choos... Closed

 Description   

with mcsadmin the primary can be chossed with

Choose Primary

This function is lost and no equivalent in cmapi/maxscale exists.

In the maxscale module csmon is a function
primary

"The primary parameter controls which server is chosen as the master server. "

csmon is deprecated and only for 1.2 and below.

So we need a feature, where a user can define a primary
and maxscale keep this primary as primary back after columnstore choosed a different node as primary after a failover from columnstore side.



 Comments   
Comment by Todd Stoffel (Inactive) [ 2021-01-15 ]

This feature is already available in MaxScale via the Cluster Manipulation Operations function. Use MariaDBMon.

Generated at Thu Feb 08 04:20:58 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.