suspendbalancing

Run the serverManager suspendbalancing command to suspend partition balancing across the Insight Servers in a multiple-server production cluster. You can run the command on any server in the cluster.

Purpose

Use the serverManager script with the suspendbalancing command to temporarily suspend and then resume the movement of partition shards among servers in the cluster. When you add multiple servers to a production cluster at the same time, you can reduce the performance impact by balancing the partitions after all the servers are added. Start all the servers that you added to the cluster, then run the serverManager resumebalancing command.

The catalogServerHost and catalogServerPort parameters are required when you suspend balancing for a runtime server in a multiple-server production cluster. Communication is established with the catalog server to determine the status of WebSphere® eXtreme Scale processes. The command waits until the WebSphere eXtreme Scale are complete on the catalog server and then suspends rebalancing on the runtime server.

The following example shows how to run the commands to manage balancing between runtime servers 4, 5 and 6 in a cluster.

serverManager suspendbalancing --catalogServerHost=catalog1.mycompany.com --catalogServerPort=8086
server start runtime_server4
server start runtime_server5
server start runtime_server6
serverManager resumebalancing --catalogServerHost=catalog1.mycompany.com --catalogServerPort=8086

where you run the suspendbalancing command and the resumebalancing command on any server in the cluster, and run the server start command on the individual runtime servers.

Syntax

serverManager suspendbalancing 
--catalogServerHost=catalog_hostname
--catalogServerPort=catalog_port
[--propertiesFile=properties_file]
[--username=username]
[--password=password]
[--host=hostname] 
[--port=port] 
[--keyStoreLocation=keystore_location]
[--keyStorePassword=keystore_password]
[--readTimeout=timeout_value]
[--sslProtocol=sslProtocol]
[--trustStorePassword=truststore_password]
[--trustStoreLocation=truststore_location]
[--disableSSLHostnameVerification=true|false]
[--disableServerCertificateVerification=true|false]

Description

Table 1. Mandatory parameters for solutionManager suspendbalancing
Mandatory parameter	Description
catalogServerHost	Required to suspend balancing on a runtime server. The script communicates with the catalog server to make sure that it is safe to suspend balancing the runtime server.
catalogServerPort	Required to suspend balancing on a runtime server. The script communicates with the catalog server to make sure that it is safe to suspend balancing the runtime server.

Table 2. Optional parameters for serverManager suspendbalancing
Optional parameter	Description
propertiesFile	The path to a properties file from which to read properties. If you do not specify a value, the default path to the connection.properties file in the runtime/ia/etc directory is used.
username	The user name of a user who has the administrator role. If you do not specify a value, the value that is specified by the propertiesFile is used.
password	The password of a user who has the administrator role. If you do not specify a value, the value that is specified by the propertiesFile is used.
host	The default host name is localhost. To change the host name, specify the fully qualified name of the remote server. For example: myserver.mycompany.com.
port	The default port value is 9443. To change the port, specify the port of the remote server.
trustStorePassword	The password for remote Secure Sockets Layer (SSL) authentication. If you do not specify a value, the value that is specified by the propertiesFile is used. If the property is not set, the truststore is not validated.
trustStoreLocation	Location of the truststore (javax.net.ssl.trustStore). Default is cisDev/resources/security/key.jks in the servers directory.
disableSSLHostnameVerification	If this value is set to `true`, SSL host name verification is disabled. If you do not specify a value, the value that is specified by the propertiesFile is used. If a value is not specified, either on the command line or in the properties file, the default value `false` is used.
disableServerCertificateVerification	This parameter is used to disable server certificate verification. If you set this parameter to true, the client does not check whether the certificate presented by the server is trusted. If the server is not trusted, authentication credentials and other user information might be passed on through the JMX connection. This parameter is optional. If not specified, it uses the value in the properties file specified by the --propertiesFile option. If no value is specified on the command line or in the properties file, it defaults to false.
keyStoreLocation	The location of the keystore. If you do not specify a value, this parameter uses the value in the properties file specified by the `--propertiesFile` option. If no value is specified on the command line or in the properties file, no keystore is used.
keyStorePassword	The keystore password. If you do not specify a value, this parameter uses the value in the properties file specified by the `--propertiesFile` option. If no value is specified on the command line or in the properties file, you are asked to provide a password interactively.
readTimeout	The amount of time expressed in milliseconds that the utility waits for a response from the server before closing a connection. This parameter is optional. If you do not specify a value, it uses the value that is specified by the --propertiesFile option. If no value is specified on the command line or in the properties file, the default value is 60000 (1 minute).
sslProtocol	The SSL protocol for the connection. If you do not specify a value, this parameter uses the value in the properties file specified by the `--propertiesFile` option. If no value is specified on the command line or in the properties file, the value "TLSv1.2" is used.