chadvclusterconfig

Modifies the advanced cluster settings.

Read syntax diagramSkip visual syntax diagram
>>-chadvclusterconfig--+--------+--+---------+------------------>
                       +- -?----+  '- -quiet-'
                       +- -h----+
                       '- -help-'

>--+----------------------+--+----------------------+----------->
   '- -nwhbthresh--number-'  '- -nwhbinterval--time-'

>--+-----------------------+--+---------------------+----------->
   '- -clientretry--number-'  '- -clientlease--time-'

>--+----------------------------+--+------------------------+--->
   '- -clientmultiplier--number-'  '- -diskhbthresh--number-'

>--+----------------------------+--+-------------------+-------><
   '- -diskhbinterval--time_out-'  '- -lang--+-en_us-+-'
                                             '-ja_jp-'

Parameters

–? | –h | –help
Displays a detailed description of this command, including syntax, parameter descriptions, and examples. If you specify a help option, all other command options are ignored.
–quiet
Turns off confirmation messages for this command.
–nwhbthresh number
Specifies the maximum number of missed network heartbeats before the metadata server declares a possible path-failure problem with another metadata server in the cluster. If this threshold is reached or exceeded and the metadata server is running, the metadata server goes into the not-running state, and stays in that state until it is repaired. If the metadata server was not running, the ejected metadata server abnormally ends, restarts, and rejoins the cluster.

You can specify a value from 1 to 100. The default value is 40.

–nwhbinterval time
Specifies the network heartbeat interval, in milliseconds, for periodic pings among metadata servers in the cluster. You can specify a value from 200 to 10 000. The default value is 500.
–clientretry number
Specifies the maximum number of times a send can be attempted from the metadata server to the client before declaring the client's session lease to be expired. You can specify a value from 1 to 100. The default value is 5.
–clientlease time
Specifies the amount of time, in seconds, that a lock is leased to a client when the metadata server grants a lock. The metadata server applies the client-lease-period multiplier to this value before ending the lease. You can specify a value from 10 to 120. The default value is 20.
–clientmultiplier number
Specifies the client-lease-period multiplier. This multiplier accommodates possible networking delays between the time a message gets sent from the client until it is received by the metadata server. You can specify a value from 0 to 4. A value of 0 prevents this multiplier from affecting the client-lease period. The default value is 2.
–diskhbthresh number
Specifies the maximum number of missed disk heartbeats before the metadata server is dropped from the cluster. You can specify a value from 1 to 100. The default value is 4.
–diskhbinterval time
Specifies the disk heartbeat interval, in milliseconds, for periodic pings among metadata servers in the cluster. You can specify a value from 200 to 10 000. The default value is 500.
–lang
Specifies the language that the metadata server runs. You can specify one of these values:
en_us
United States English UTF8
ja_jp
Japanese UTF8
Note: This is a disruptive setting. If you change the language, you must restart the cluster.

Prerequisites

This task must be performed only by trained service personnel.

You must have Administrator privileges to use the command.

You must be logged in to the operating system on the engine hosting the master metadata server to run this command.

Description

Note: Modifying these settings requires you to reboot the cluster before changes will apply.

After you run this command, you cannot run the chadvclusterconfig or chclusterconfig command until you restart the cluster.

After you modify any of these disruptive cluster settings, you cannot modify any cluster settings (using the chadvclusterconfigor chclusterconfig command) until you restart the cluster.

Restriction: This command cannot be used when the cluster is quiesced.

Example

Changes the network heartbeat threshold The following example changes the network heartbeat threshold to 10 missed heartbeats.
sfscli> chadvclusterconfig -nwhbthresh 10
Are you sure you want to change advanced cluster configuration settings, 
which will require a immediate cluster restart for changes to apply? [y/n]  Y
Cluster successfully modified. Restart the cluster for all changes to apply.

Parent topic: Administrative commands

Related reference
chclusterconfig
quiescecluster
resumecluster
startcluster
statcluster
stopcluster
upgradecluster

Terms of use | Feedback
(C) Copyright IBM Corporation 2003, 2004. All Rights Reserved.