[Bugs] [Bug 1258833] Data Tiering: Disallow attach tier on a volume where any rebalance process is in progress to avoid deadlock(like remove brick commit pending etc)

[bugzilla at redhat.com]

https://bugzilla.redhat.com/show_bug.cgi?id=1258833



--- Comment #1 from nchilaka <nchilaka at redhat.com> ---
Workaround:
==========
>do a detach tier commit forcefully
>do a remove brick commit forcefully(though the remove brick operation doesnt show up anymore in the vol status or rebalance status
>reattach the tier


[root at nag-manual-node1 glusterfs]# gluster v detach-tier rebal commit
volume detach-tier commit: failed: Brick 10.70.46.84:/rhs/brick4/rebalhot is
not decommissioned. Use start or force option
[root at nag-manual-node1 glusterfs]# gluster v detach-tier rebal commit force
volume detach-tier commit force: success
[root at nag-manual-node1 glusterfs]# gluster v info rebal

Volume Name: rebal
Type: Distribute
Volume ID: 3e272970-b319-4a35-a8cd-6845190761ee
Status: Started
Number of Bricks: 3
Transport-type: tcp
Bricks:
Brick1: 10.70.46.84:/rhs/brick1/rebal
Brick2: 10.70.46.36:/rhs/brick1/rebal
Brick3: 10.70.46.36:/rhs/brick2/rebal
Options Reconfigured:
performance.readdir-ahead: on
[root at nag-manual-node1 glusterfs]# gluster  v status rebal
Status of volume: rebal
Gluster process                             TCP Port  RDMA Port  Online  Pid
------------------------------------------------------------------------------
Brick 10.70.46.84:/rhs/brick1/rebal         49187     0          Y       7849 
Brick 10.70.46.36:/rhs/brick1/rebal         49186     0          Y       32414
Brick 10.70.46.36:/rhs/brick2/rebal         49187     0          Y       32432
NFS Server on localhost                     2049      0          Y       8455 
NFS Server on 10.70.46.36                   2049      0          Y       402  

Task Status of Volume rebal
------------------------------------------------------------------------------
There are no active volume tasks

[root at nag-manual-node1 glusterfs]# gluster v rebal rebal status
                                    Node Rebalanced-files          size      
scanned      failures       skipped               status   run time in secs
                               ---------      -----------   -----------  
-----------   -----------   -----------         ------------     --------------
volume rebalance: rebal: success: 
[root at nag-manual-node1 glusterfs]# gluster v remove-brick rebal
10.70.46.36:/rhs/brick2/rebal commit
Removing brick(s) can result in data loss. Do you want to Continue? (y/n) y
volume remove-brick commit: success
Check the removed bricks to ensure all files are migrated.
If files with data are found on the brick path, copy them via a gluster mount
point before re-purposing the removed brick.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are on the CC list for the bug.
You are the assignee for the bug.