Package org.ovirt.engine.sdk4.services
Interface GlusterVolumeService.RebalanceRequest
-
- All Superinterfaces:
Request<GlusterVolumeService.RebalanceRequest,GlusterVolumeService.RebalanceResponse>
- Enclosing interface:
- GlusterVolumeService
public static interface GlusterVolumeService.RebalanceRequest extends Request<GlusterVolumeService.RebalanceRequest,GlusterVolumeService.RebalanceResponse>
Rebalance the gluster volume. Rebalancing a gluster volume helps to distribute the data evenly across all the bricks. After expanding or shrinking a gluster volume (without migrating data), we need to rebalance the data among the bricks. In a non-replicated volume, all bricks should be online to perform the rebalance operation. In a replicated volume, at least one of the bricks in the replica should be online. For example, to rebalance a gluster volume with identifier `123` in cluster `456`, send a request like this: [source] ---- POST /ovirt-engine/api/clusters/456/glustervolumes/123/rebalance ----
-
-
Method Summary
All Methods Instance Methods Abstract Methods Modifier and Type Method Description GlusterVolumeService.RebalanceRequest
async(Boolean async)
Indicates if the rebalance should be performed asynchronously.GlusterVolumeService.RebalanceRequest
fixLayout(Boolean fixLayout)
If set to true, rebalance will only fix the layout so that new data added to the volume is distributed across all the hosts.GlusterVolumeService.RebalanceRequest
force(Boolean force)
Indicates if the rebalance should be force started.
-
-
-
Method Detail
-
async
GlusterVolumeService.RebalanceRequest async(Boolean async)
Indicates if the rebalance should be performed asynchronously.
-
fixLayout
GlusterVolumeService.RebalanceRequest fixLayout(Boolean fixLayout)
If set to true, rebalance will only fix the layout so that new data added to the volume is distributed across all the hosts. But it will not migrate/rebalance the existing data. Default is `false`.
-
force
GlusterVolumeService.RebalanceRequest force(Boolean force)
Indicates if the rebalance should be force started. The rebalance command can be executed with the force option even when the older clients are connected to the cluster. However, this could lead to a data loss situation. Default is `false`.
-
-