hcq/MaxScale
hcq/MaxScale
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Fix cluster sync documentation

Browse Source 
The MaxScale instance isn't stopped if the synchronization fails. Added
missing documentation for the command argument.
This commit is contained in:
Markus Mäkelä 2020-05-07 16:48:59 +03:00
parent b4108270dc
commit 73eba01ce9
No known key found for this signature in database
GPG Key ID: 5CE746D557ACC499
1 changed files with 2 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
maxctrl/lib/cluster.js
View File

@ -178,9 +178,8 @@ exports.builder = function(yargs) {
})
.command('sync <target>', 'Synchronize the cluster with target MaxScale server.', function(yargs) {
return yargs.epilog('This command will alter all MaxScale instances given in the --hosts ' +
'option to represent the <target> MaxScale. If the synchronization of ' +
'a MaxScale instance fails, it will be disabled by executing the `stop maxscale` ' +
'command on that instance. Synchronization can be attempted again if a previous ' +
'option to represent the <target> MaxScale. Value of <target> ' +
'must be in HOST:PORT format. Synchronization can be attempted again if a previous ' +
'attempt failed due to a network failure or some other ephemeral error. Any other ' +
'errors require manual synchronization of the MaxScale configuration files and a ' +
'restart of the failed Maxscale.\n\n' +