Details
-
Task
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Won't Do
-
1.0.10
-
None
Description
This may be just cosmetic or actually safe design decision. I am unsure if the following flow would result in a clean copy of dbroots:
suspendDatabaseWrites
|
check for WRITE_SUSPEND |
(another admin starts redistributeData)
|
lvm snapshot dbroots
|
resumeDatabaseWrites
|
copy data from snapshot
|
[root@mg-cstore ~]# mcsadmin suspendDatabaseWrites y
|
suspenddatabasewrites Fri Aug 11 18:46:27 2017
|
|
|
This command suspends the DDL/DML writes to the MariaDB ColumnStore Database
|
|
|
Suspend Calpont Database Writes Request successfully completed
|
[root@mg-cstore ~]# mcsadmin getsysteminfo | awk '$1 = /WriteEngineServer/ {print $3}'
|
WRITE_SUSPEND
|
[root@mg-cstore ~]# mcsadmin redistributeData statusredistributedata Fri Aug 11 18:46:43 2017
|
WriteEngineServer returned status 3: Redistribute is finished.
|
0 success, 0 skipped, 0 failed.
|
Total time: 0 seconds.
|
|
|
[root@mg-cstore ~]# mcsadmin redistributeData start
|
redistributedata Fri Aug 11 18:46:51 2017
|
redistributeData START
|
Source dbroots: 1 2
|
Destination dbroots: 1 2
|
|
|
WriteEngineServer returned status 1: Cleared.
|
WriteEngineServer returned status 2: Redistribute is started.
|
[root@mg-cstore ~]# mcsadmin redistributeData status
|
redistributedata Fri Aug 11 18:47:00 2017
|
WriteEngineServer returned status 3: Redistribute is finished.
|
0 success, 0 skipped, 0 failed.
|
Total time: 0 seconds.
|
|
|
[root@mg-cstore ~]# mcsadmin getsysteminfo | awk '$1 = /WriteEngineServer/ {print $3}'
|
WRITE_SUSPEND
|
|