[Bugs] [Bug 1229241] Data Tiering:remove cold/hot brick seems to be behaving like or emulating detach-tier
bugzilla at redhat.com
bugzilla at redhat.com
Fri Jun 19 12:02:13 UTC 2015
https://bugzilla.redhat.com/show_bug.cgi?id=1229241
nchilaka <nchilaka at redhat.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |VERIFIED
--- Comment #5 from nchilaka <nchilaka at redhat.com> ---
Have tried to remove both cold and hot bricks with force and graceful.
Dont see the issue anymore.
Hence moving it to verified:
Last login: Thu Jun 18 17:48:36 2015 from dhcp35-163.lab.eng.blr.redhat.com
[root at tettnang ~]# gluster peer status
Number of Peers: 1
Hostname: 10.70.35.75
Uuid: 3a23617c-40e5-4dda-8903-032bbe875c4b
State: Peer in Cluster (Disconnected)
[root at tettnang ~]# gluster peer detach 10.70.35.75
peer detach: success
[root at tettnang ~]# gluster peer status
Number of Peers: 0
[root at tettnang ~]# gluster peer status
Number of Peers: 0
[root at tettnang ~]# gluster peer probe
Usage: peer probe <HOSTNAME>
[root at tettnang ~]# gluster peer probe zod
peer probe: success.
[root at tettnang ~]# gluster peer probe yarrow
peer probe: success.
[root at tettnang ~]# Write failed: Broken pipe
bash-4.3$ ssh root at tettnang
root at tettnang's password:
Last login: Thu Jun 18 17:51:39 2015 from dhcp35-163.lab.eng.blr.redhat.com
[root at tettnang ~]#
[root at tettnang ~]# history|grep create
299 history|grep create
[root at tettnang ~]# gluster v create nag replica 2 ^C
[root at tettnang ~]# ls /rhs/brick^C
[root at tettnang ~]# gluster v create nag replica 2 ^C
[root at tettnang ~]# gluster peer status
Number of Peers: 2
Hostname: zod
Uuid: 4f625789-7121-478f-9fe7-913ec6b0a424
State: Peer in Cluster (Connected)
Hostname: yarrow
Uuid: 3a23617c-40e5-4dda-8903-032bbe875c4b
State: Peer in Cluster (Connected)
[root at tettnang ~]# gluster peer probe zod^C
[root at tettnang ~]# gluster v create nag replica 2 yarrow:/rhs/brick1/nag
zod:/rhs/brick1/nag yarrow:/rhs/brick2/nag zod:/rhs/brick2/nag
volume create: nag: success: please start the volume to access data
[root at tettnang ~]# gluster v start nag
volume start: nag: success
[root at tettnang ~]# gluster v info nag
Volume Name: nag
Type: Distributed-Replicate
Volume ID: dd816c6b-a1fd-49e5-be36-68f4e2c04d0c
Status: Started
Number of Bricks: 2 x 2 = 4
Transport-type: tcp
Bricks:
Brick1: yarrow:/rhs/brick1/nag
Brick2: zod:/rhs/brick1/nag
Brick3: yarrow:/rhs/brick2/nag
Brick4: zod:/rhs/brick2/nag
Options Reconfigured:
performance.readdir-ahead: on
[root at tettnang ~]# gluster v attach-tier nag yarrow:/rhs/brick7/nag
zod:/rhs/brick7/nag
Attach tier is recommended only for testing purposes in this release. Do you
want to continue? (y/n) y
volume attach-tier: success
gluster v info nag
glustvolume rebalance: nag: success: Rebalance on nag has been started
successfully. Use rebalance status command to check status of the rebalance
process.
ID: 30684f9d-806c-4be9-bcbb-872f242198dd
[root at tettnang ~]# gluster v info nag
e
Volume Name: nag
Type: Tier
Volume ID: dd816c6b-a1fd-49e5-be36-68f4e2c04d0c
Status: Started
Number of Bricks: 6
Transport-type: tcp
Hot Tier :
Hot Tier Type : Distribute
Number of Bricks: 2
Brick1: zod:/rhs/brick7/nag
Brick2: yarrow:/rhs/brick7/nag
Cold Tier:
Cold Tier Type : Distributed-Replicate
Number of Bricks: 2 x 2 = 4
Brick3: yarrow:/rhs/brick1/nag
Brick4: zod:/rhs/brick1/nag
Brick5: yarrow:/rhs/brick2/nag
Brick6: zod:/rhs/brick2/nag
Options Reconfigured:
performance.readdir-ahead: on
[root at tettnang ~]# gluster v status nag
Status of volume: nag
Gluster process TCP Port RDMA Port Online Pid
------------------------------------------------------------------------------
Hot Bricks:
Brick zod:/rhs/brick7/nag 49154 0 Y 12510
Brick yarrow:/rhs/brick7/nag 49154 0 Y 13660
Cold Bricks:
Brick yarrow:/rhs/brick1/nag 49152 0 Y 13600
Brick zod:/rhs/brick1/nag 49152 0 Y 12410
Brick yarrow:/rhs/brick2/nag 49153 0 Y 13618
Brick zod:/rhs/brick2/nag 49153 0 Y 12434
NFS Server on localhost N/A N/A N N/A
NFS Server on yarrow N/A N/A N N/A
NFS Server on zod N/A N/A N N/A
Task Status of Volume nag
------------------------------------------------------------------------------
Task : Rebalance
ID : 30684f9d-806c-4be9-bcbb-872f242198dd
Status : in progress
[root at tettnang ~]# gluster v info nag
Volume Name: nag
Type: Tier
Volume ID: dd816c6b-a1fd-49e5-be36-68f4e2c04d0c
Status: Started
Number of Bricks: 6
Transport-type: tcp
Hot Tier :
Hot Tier Type : Distribute
Number of Bricks: 2
Brick1: zod:/rhs/brick7/nag
Brick2: yarrow:/rhs/brick7/nag
Cold Tier:
Cold Tier Type : Distributed-Replicate
Number of Bricks: 2 x 2 = 4
Brick3: yarrow:/rhs/brick1/nag
Brick4: zod:/rhs/brick1/nag
Brick5: yarrow:/rhs/brick2/nag
Brick6: zod:/rhs/brick2/nag
Options Reconfigured:
performance.readdir-ahead: on
[root at tettnang ~]# gluster v add-brick
Usage: volume add-brick <VOLNAME> [<stripe|replica> <COUNT>] <NEW-BRICK> ...
[force]
[root at tettnang ~]# gluster v remove-brick nag
Usage: volume remove-brick <VOLNAME> [replica <COUNT>] <BRICK> ...
<start|stop|status|commit|force>
[root at tettnang ~]# gluster v remove-brick nag zod:/rhs/brick7/nag start
volume remove-brick start: failed: Removing brick from a Tier volume is not
allowed
[root at tettnang ~]# gluster v status nag
Status of volume: nag
Gluster process TCP Port RDMA Port Online Pid
------------------------------------------------------------------------------
Hot Bricks:
Brick zod:/rhs/brick7/nag 49154 0 Y 12510
Brick yarrow:/rhs/brick7/nag 49154 0 Y 13660
Cold Bricks:
Brick yarrow:/rhs/brick1/nag 49152 0 Y 13600
Brick zod:/rhs/brick1/nag 49152 0 Y 12410
Brick yarrow:/rhs/brick2/nag 49153 0 Y 13618
Brick zod:/rhs/brick2/nag 49153 0 Y 12434
NFS Server on localhost N/A N/A N N/A
NFS Server on yarrow N/A N/A N N/A
NFS Server on zod N/A N/A N N/A
Task Status of Volume nag
------------------------------------------------------------------------------
Task : Rebalance
ID : 30684f9d-806c-4be9-bcbb-872f242198dd
Status : in progress
[root at tettnang ~]# gluster v remove-brick nag zod:/rhs/brick7/nag force
Removing brick(s) can result in data loss. Do you want to Continue? (y/n) y
volume remove-brick commit force: failed: Removing brick from a Tier volume is
not allowed
[root at tettnang ~]# gluster v status nag
Status of volume: nag
Gluster process TCP Port RDMA Port Online Pid
------------------------------------------------------------------------------
Hot Bricks:
Brick zod:/rhs/brick7/nag 49154 0 Y 12510
Brick yarrow:/rhs/brick7/nag 49154 0 Y 13660
Cold Bricks:
Brick yarrow:/rhs/brick1/nag 49152 0 Y 13600
Brick zod:/rhs/brick1/nag 49152 0 Y 12410
Brick yarrow:/rhs/brick2/nag 49153 0 Y 13618
Brick zod:/rhs/brick2/nag 49153 0 Y 12434
NFS Server on localhost N/A N/A N N/A
NFS Server on yarrow N/A N/A N N/A
NFS Server on zod N/A N/A N N/A
Task Status of Volume nag
------------------------------------------------------------------------------
Task : Rebalance
ID : 30684f9d-806c-4be9-bcbb-872f242198dd
Status : in progress
[root at tettnang ~]# gluster v remove-brick nag zod:/rhs/brick7/nag status
volume remove-brick status: failed: remove-brick not started.
[root at tettnang ~]# gluster v remove-brick nag zod:/rhs/brick7/nag commit
Removing brick(s) can result in data loss. Do you want to Continue? (y/n) y
volume remove-brick commit: failed: Removing brick from a Tier volume is not
allowed
[root at tettnang ~]# gluster v remove-brick nag zod:/rhs/brick7/nag status
volume remove-brick status: failed: remove-brick not started.
[root at tettnang ~]# gluster v remove-brick nag zod:/rhs/brick7/nag force
Removing brick(s) can result in data loss. Do you want to Continue? (y/n) y
volume remove-brick commit force: failed: Removing brick from a Tier volume is
not allowed
[root at tettnang ~]# gluster v remove-brick nag zod:/rhs/brick7/nag status
volume remove-brick status: failed: remove-brick not started.
[root at tettnang ~]# gluster v remove-brick nag zod:/rhs/brick1/nag status
volume remove-brick status: failed: remove-brick not started.
[root at tettnang ~]# gluster v remove-brick nag zod:/rhs/brick1/nag start
volume remove-brick start: failed: Removing brick from a Tier volume is not
allowed
[root at tettnang ~]# gluster v remove-brick nag zod:/rhs/brick1/nag status
volume remove-brick status: failed: remove-brick not started.
[root at tettnang ~]# gluster v remove-brick nag zod:/rhs/brick1/nag force
Removing brick(s) can result in data loss. Do you want to Continue? (y/n) y
volume remove-brick commit force: failed: Removing brick from a Tier volume is
not allowed
[root at tettnang ~]# gluster v remove-brick nag zod:/rhs/brick1/nag status
volume remove-brick status: failed: remove-brick not started.
[root at tettnang ~]# gluster v remove-brick nag zod:/rhs/brick1/nag status^C
[root at tettnang ~]#
[root at tettnang ~]#
[root at tettnang ~]# gluster v info
Volume Name: nag
Type: Tier
Volume ID: dd816c6b-a1fd-49e5-be36-68f4e2c04d0c
Status: Started
Number of Bricks: 6
Transport-type: tcp
Hot Tier :
Hot Tier Type : Distribute
Number of Bricks: 2
Brick1: zod:/rhs/brick7/nag
Brick2: yarrow:/rhs/brick7/nag
Cold Tier:
Cold Tier Type : Distributed-Replicate
Number of Bricks: 2 x 2 = 4
Brick3: yarrow:/rhs/brick1/nag
Brick4: zod:/rhs/brick1/nag
Brick5: yarrow:/rhs/brick2/nag
Brick6: zod:/rhs/brick2/nag
Options Reconfigured:
performance.readdir-ahead: on
[root at tettnang ~]# rpm -qa|grep gluster
glusterfs-cli-3.7.1-4.el7rhgs.x86_64
glusterfs-client-xlators-3.7.1-4.el7rhgs.x86_64
glusterfs-fuse-3.7.1-4.el7rhgs.x86_64
glusterfs-geo-replication-3.7.1-4.el7rhgs.x86_64
glusterfs-libs-3.7.1-4.el7rhgs.x86_64
glusterfs-api-3.7.1-4.el7rhgs.x86_64
glusterfs-rdma-3.7.1-4.el7rhgs.x86_64
glusterfs-3.7.1-4.el7rhgs.x86_64
glusterfs-debuginfo-3.7.1-4.el7rhgs.x86_64
--
You are receiving this mail because:
You are on the CC list for the bug.
Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=SgQW3Alv6q&a=cc_unsubscribe
More information about the Bugs
mailing list