[root@octopus ~]# stasher
Ready, EOF to exit.
> admin
Connected to objrepo.example.com, node octopus.objrepo.example.com.
Maximum 10 objects, 32 Mb aggregate object size, per transaction.
Maximum 10 concurrent subscriptions.
octopus> setlimits 20 64mb
octopus> [EOF, CTRL-D]
[root@octopus ~]# stasher
Ready, EOF to exit.
> admin
Connected to objrepo.example.com, node octopus.objrepo.example.com.
Maximum 20 objects, 64 Mb aggregate object size, per transaction.
Maximum 10 concurrent subscriptions.
octopus> editcluster addnode octopus set host=octopus.example.com
octopus:
HOST=octopus.example.com
octopus> savecluster
octopus> status
Cluster:
Status: master: octopus.objrepo.example.com (uuid S85HVpjTVrQqA000_F1aJm00001vhGO00318n4AS), 0 slaves, timestamp 2012-03-17 16:15:56 -0400
This node:
HOST=octopus.example.com
... long output deleted ...
octopus> [EOF, CTRL-D]
[root@octopus ~]#
The default stasher configuration allows a transaction to add, update, or delete at most ten objects in the object repository, with the total aggregate size of all new or updated objects of 32 megabytes. the setlimits command adjusts these parameters. Disconnecting and reconnecting confirms that the updated settings took hold. See stashermg(1) for more information on the setlimits command.
Use editcluster to define the first node's hostname in the object repository cluster's configuration. This setting defines which machine each node runs on. Here, the “cluster” command specifies that the “octopus” node, the first node in the cluster, runs on machine called “octopus.example.com”. Even though the new node started with an empty configuration, the first node's hostname must be explicitly set, as the first order of business.
The output from the status command verifies the “HOST” setting in the “This node” section. This confirms that the configuration was properly updated.