[Bugs] [Bug 1215668] [geo-rep + tiering]: georep fails to create session on tiered volume
bugzilla at redhat.com
bugzilla at redhat.com
Tue May 19 09:07:36 UTC 2015
https://bugzilla.redhat.com/show_bug.cgi?id=1215668
Joseph Elwin Fernandes <josferna at redhat.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |ON_QA
--- Comment #2 from Joseph Elwin Fernandes <josferna at redhat.com> ---
We tested this on
1) Tested on master: works
2) Tested on 3.7 branch : works
[root at rhs-srv-09 test]# gluster volume info
Volume Name: test
Type: Tier
Volume ID: 28e37d68-8699-40dd-8e55-c04cf1ceb5a2
Status: Started
Number of Bricks: 4
Transport-type: tcp
Hot Tier :
Hot Tier Type : Replicate
Number of Bricks: 1 x 2 = 2
Brick1: rhs-srv-09:/home/ssd/s2
Brick2: rhs-srv-09:/home/ssd/s1
Cold Bricks:
Cold Tier Type : Replicate
Number of Bricks: 1 x 2 = 2
Brick3: rhs-srv-09:/home/disk/d1
Brick4: rhs-srv-09:/home/disk/d2
Options Reconfigured:
performance.readdir-ahead: on
geo-replication.indexing: on
geo-replication.ignore-pid-check: on
changelog.changelog: on
[root at rhs-srv-09 test]#
[root at rhs-srv-09 test]# gluster volume geo-rep test rhs-srv-08::test status
MASTER NODE MASTER VOL MASTER BRICK SLAVE
USER SLAVE SLAVE NODE STATUS CRAWL STATUS
LAST_SYNCED
-------------------------------------------------------------------------------------------------------------------------------------------------------------------------
rhs-srv-09.gdev.lab.eng.rdu2.redhat.com test /home/ssd/s2 root
rhs-srv-08::test rhs-srv-08 Active Changelog Crawl
2015-05-19 02:53:19
rhs-srv-09.gdev.lab.eng.rdu2.redhat.com test /home/ssd/s1 root
rhs-srv-08::test rhs-srv-08 Active Changelog Crawl
2015-05-19 02:53:19
rhs-srv-09.gdev.lab.eng.rdu2.redhat.com test /home/disk/d1 root
rhs-srv-08::test rhs-srv-08 Active Changelog Crawl N/A
rhs-srv-09.gdev.lab.eng.rdu2.redhat.com test /home/disk/d2 root
rhs-srv-08::test rhs-srv-08 Active Changelog Crawl
2015-05-19 02:52:18
--
You are receiving this mail because:
You are the QA Contact for the bug.
You are on the CC list for the bug.
More information about the Bugs
mailing list