[Bugs] [Bug 1274411] Fully support data-tiering in 3.7.x, remove out of 'experimental' status
bugzilla at redhat.com
bugzilla at redhat.com
Fri Nov 20 11:26:44 UTC 2015
https://bugzilla.redhat.com/show_bug.cgi?id=1274411
nchilaka <nchilaka at redhat.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ON_QA |VERIFIED
--- Comment #4 from nchilaka <nchilaka at redhat.com> ---
I Dont see the cli "tiering is in tech preview" or similar messages while
attach ro any tier operations. Hence moving to verified
[root at zod distrep]# gluster v tier distrep_fus
Usage: volume tier <VOLNAME> status
volume tier <VOLNAME> attach [<replica COUNT>] <NEW-BRICK>...
volume tier <VOLNAME> detach <start|stop|status|commit|[force]>
Tier command failed
[root at zod distrep]# gluster v tier distrep_fus detach start
volume detach-tier start: success
ID: c8e7c567-b93d-4813-92eb-a3df4446243f
[root at zod distrep]# gluster v create hi zod:/rhs/brick/hi
volume create: hi: failed: Failed to create brick directory for brick
zod:/rhs/brick/hi. Reason : No such file or directory
[root at zod distrep]# gluster v create hi zod:/rhs/brick1/hi
volume create: hi: success: please start the volume to access data
[root at zod distrep]# gluster v tier hi attach zod:/rhs/brick1/h2
volume attach-tier: success
Tiering Migration Functionality: hi: failed: Volume hi needs to be started to
perform rebalance
Failed to run tier start. Please execute tier start command explictly
Usage : gluster volume rebalance <volname> tier start
Tier command failed
[root at zod distrep]# gluster v start hi
volume start: hi: success
[root at zod distrep]# gluster v tier hi attach zod:/rhs/brick1/h2
volume attach-tier: failed: Volume hi is already a tier.
Tier command failed
[root at zod distrep]# gluster v info hi
Volume Name: hi
Type: Tier
Volume ID: 4cedaf4f-f10d-41fe-b60c-2e77fda73a5c
Status: Started
Number of Bricks: 2
Transport-type: tcp
Hot Tier :
Hot Tier Type : Distribute
Number of Bricks: 1
Brick1: zod:/rhs/brick1/h2
Cold Tier:
Cold Tier Type : Distribute
Number of Bricks: 1
Brick2: zod:/rhs/brick1/hi
Options Reconfigured:
features.ctr-enabled: on
performance.readdir-ahead: on
[root at zod distrep]# gluster v tier hi status
Node Promoted files Demoted files Status
--------- --------- --------- ---------
localhost 0 0 in progress
yarrow 0 0 in progress
Tiering Migration Functionality: hi: success
[root at zod distrep]# gluster v create hi zod:/rhs/brick1/hi
volume create: hi: failed: Volume hi already exists
[root at zod distrep]# gluster v create hm zod:/rhs/brick1/hm
volume create: hm: success: please start the volume to access data
[root at zod distrep]# guster v start hm
bash: guster: command not found...
[root at zod distrep]# gluster v start hm
gluster v status hmvolume start: hm: success
[root at zod distrep]# gluster v status hm
Status of volume: hm
Gluster process TCP Port RDMA Port Online Pid
------------------------------------------------------------------------------
Brick zod:/rhs/brick1/hm 49325 0 Y 30142
NFS Server on localhost N/A N/A N N/A
NFS Server on yarrow N/A N/A N N/A
Task Status of Volume hm
------------------------------------------------------------------------------
There are no active volume tasks
[root at zod distrep]# gluster v tier hm attach zod:/rhs/brick1/hm_ho
volume attach-tier: success
gluster v tier hm statTiering Migration Functionality: hm: success: Attach tier
is successful on hm. use tier status to check the status.
ID: 9bd4da8b-10ef-4087-9bc1-fe0216edea42
[root at zod distrep]# gluster v tier hm status
Node Promoted files Demoted files Status
--------- --------- --------- ---------
localhost 0 0 in progress
yarrow 0 0 not started
Tiering Migration Functionality: hm: success
[root at zod distrep]# gluster v tier hm status
Node Promoted files Demoted files Status
--------- --------- --------- ---------
localhost 0 0 in progress
yarrow 0 0 not started
Tiering Migration Functionality: hm: success
[root at zod distrep]# gluster v tier hm force start
Usage: volume tier <VOLNAME> status
volume tier <VOLNAME> attach [<replica COUNT>] <NEW-BRICK>...
volume tier <VOLNAME> detach <start|stop|status|commit|[force]>
Tier command failed
[root at zod distrep]# gluster v tier hm start force
Usage: volume tier <VOLNAME> status
volume tier <VOLNAME> attach [<replica COUNT>] <NEW-BRICK>...
volume tier <VOLNAME> detach <start|stop|status|commit|[force]>
Tier command failed
[root at zod distrep]# gluster v start hm force
volume start: hm: success
[root at zod distrep]# gluster v tier hm force start
Usage: volume tier <VOLNAME> status
volume tier <VOLNAME> attach [<replica COUNT>] <NEW-BRICK>...
volume tier <VOLNAME> detach <start|stop|status|commit|[force]>
Tier command failed
[root at zod distrep]# gluster v tier hm status
Node Promoted files Demoted files Status
--------- --------- --------- ---------
localhost 0 0 in progress
yarrow 0 0 in progress
Tiering Migration Functionality: hm: success
[root at zod distrep]#
[root at zod distrep]# rpm -qa|grep gluster
glusterfs-libs-3.7.5-6.el7rhgs.x86_64
glusterfs-fuse-3.7.5-6.el7rhgs.x86_64
glusterfs-3.7.5-6.el7rhgs.x86_64
glusterfs-server-3.7.5-6.el7rhgs.x86_64
glusterfs-client-xlators-3.7.5-6.el7rhgs.x86_64
glusterfs-cli-3.7.5-6.el7rhgs.x86_64
glusterfs-api-3.7.5-6.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=lthWrcLi89&a=cc_unsubscribe
More information about the Bugs
mailing list