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

[bugzilla at redhat.com]

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

            Bug ID: 1272341
           Summary: Data Tiering:Promotions fail when brick of EC
                    (disperse) cold layer are down
           Product: Red Hat Gluster Storage
         Component: glusterfs
     Sub Component: tiering
          Severity: high
          Priority: urgent
          Assignee: rhs-bugs at redhat.com
          Reporter: nchilaka at redhat.com
        QA Contact: nchilaka at redhat.com
                CC: bugs at gluster.org
        Depends On: 1272334



+++ This bug was initially created as a clone of Bug #1272334 +++

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 10.70.34.43:49243 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
/rhs/brick3/ecvol/.glusterfs/ecvol.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):
============================================================
glusterfs-server-3.7.5-0.22.gitb8ba012.el7.centos.x86_64



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

--- Additional comment from nchilaka on 2015-10-16 03:18:30 EDT ---

logs and sosreport available @ /home/repo/sosreports/nchilaka/bug.1272334
[nchilaka at rhsqe-repo bug.1272334]$ hostname
rhsqe-repo.lab.eng.blr.redhat.com


Referenced Bugs:

https://bugzilla.redhat.com/show_bug.cgi?id=1272334
[Bug 1272334] Data Tiering:Promotions fail when brick of EC (disperse) cold
layer are down
-- 
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=SDsfk8nm2S&a=cc_unsubscribe