[Bugs] [Bug 1272334] New: Data Tiering:Promotions fail when brick of EC (disperse) cold layer are down

bugzilla at redhat.com bugzilla at redhat.com
Fri Oct 16 07:01:13 UTC 2015


            Bug ID: 1272334
           Summary: Data Tiering:Promotions fail when brick of EC
                    (disperse) cold layer are down
           Product: GlusterFS
           Version: 3.7.5
         Component: tiering
          Assignee: bugs at gluster.org
          Reporter: nchilaka at redhat.com
        QA Contact: bugs at gluster.org
                CC: bugs at gluster.org

Description of problem:
When a brick of a EC cold layer is down, promotions fail due to following error
[2015-10-16 06:43:59.589013] E [socket.c:2278:socket_connect_finish]
0-ecvol-client-5: connection to failed (Connection refused)
[2015-10-16 06:44:00.128952] E [MSGID: 109037] [tier.c:939:tier_process_brick]
0-tier: Failed gettingjournal_mode of sql db
[2015-10-16 06:44:00.128989] E [MSGID: 109087]
[tier.c:1033:tier_build_migration_qfile] 0-ecvol-tier-dht: Brick query failed

While the error makes complete sense, we must handle this scenario, where db
can be built or vetoed using the remaining up and running bricks as long as EC
quorum is not breached.

I.e in a 4+2 ec cold layer, even if 2 bricks are down, then the data is as good
as available as the quorum of 4 bricks is met. hence db should be built and
used based on these 4.

Version-Release number of selected component (if applicable):

Steps to Reproduce:
1.create a ec 4+2 vol and start it
2.Now create a file f1 and then bring down 1 or 2 bricks
3.Now modify f1
4. attach tier and modify f1 to heat it
5. Now create new file h1 and wait for it to be demoted
6. Now touch/modify h1 after it is demoted

Actual results:
both f1 and h1 fail to get promoted

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.

More information about the Bugs mailing list