6.5 HP StoreAll OS User Guide

5. Verify that the partitions are rebalanced by checking all builder file configurations
(account/container/object). Send the following commands:
a. [root@swift1 ~]# swift-ring-builder
/ifs1/ObjectStore6/config/swift/account.builder
Sample output:
/ifs1/ObjectStore6/config/swift/account.builder, build version 4
4096 partitions, 1.000000 replicas, 1 regions, 1 zones, 2 devices, 0.02 balance
The minimum number of hours before a partition can be reassigned is 0
Devices:
id region zone ip address port name weight partitions balance meta
0 1 1 10.21.19.43 6046 node010021019043 200.00 2731 0.01
1 1 1 10.21.19.44 6049 node010021019044 100.00 1365 -0.02
b. [root@swift1 ~]# swift-ring-builder
/ifs1/ObjectStore6/config/swift/container.builder
Sample output:
/ifs1/ObjectStore6/config/swift/container.builder, build version 4
4096 partitions, 1.000000 replicas, 1 regions, 1 zones, 2 devices, 0.02 balance
The minimum number of hours before a partition can be reassigned is 0
Devices:
id region zone ip address port name weight partitions balance meta
0 1 1 10.21.19.43 6045 node010021019043 200.00 2731 0.01
1 1 1 10.21.19.44 6048 node010021019044 100.00 1365 -0.02
c. root@swift1 ~]# swift-ring-builder
/ifs1/ObjectStore6/config/swift/object.builder
Sample output:
/ifs1/ObjectStore6/config/swift/object.builder, build version 4
4096 partitions, 1.000000 replicas, 1 regions, 1 zones, 2 devices, 0.02 balance
The minimum number of hours before a partition can be reassigned is 0
Devices:
d region zone ip address port name weight partitions balance meta
0 1 1 10.21.19.43 6044 node010021019043 200.00 2731 0.01
1 1 1 10.21.19.44 6047 node010021019044 100.00 1365 -0.02
6. To ensure the rebalance operation has completed, view the /var/log/rsyncd.log to see
if data movement has completed or is still in progress by verifying if there are ongoing object
rsync messages. An example of a message showing ongoing data movement:
rsync to object/node010021013063/objects/2255 from
wai13s5.ibrixdom.com(10.21.18.3)
Removing the server configuration
When you select an Object Store couplet configuration for deletion, object replication to the devices
of the existing couplet will start as a background task. Once rebalancing is done, the Object Store
services will be stopped on that couplet, all related Object Store configuration will be removed,
and the configuration delete will be completed.
NOTE: In the case of couplet decommissioning, this is a pre-requisite step.
Before removing the server configuration
IMPORTANT: Please follow these pre-requisite steps before removal of the Object Store
configuration from an existing server pair.
1. Freeze I/O (input/output) to the Object Store.
2. Ensure none of the servers are in failed-over state.
3. All servers must be up and running.
Upon deleting the Object Store configuration, the existing data gets rebalanced to the segments
of the remaining nodes and you may observe downtime to access existing containers and objects,
although you will still be able to upload new data.
164 Using Object Store