Red Hat Bugzilla – Bug 1273215
Data Tiering:Promotions fail when brick of EC (disperse) cold layer are down
Last modified: 2016-06-16 09:40:47 EDT
+++ 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):
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
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@rhsqe-repo bug.1272334]$ hostname
REVIEW: http://review.gluster.org/12397 (cluster/tier do not abort migration if a single brick is down) posted (#1) for review on master by Dan Lambright (firstname.lastname@example.org)
REVIEW: http://review.gluster.org/12397 (cluster/tier do not abort migration if a single brick is down) posted (#2) for review on master by Dan Lambright (email@example.com)
COMMIT: http://review.gluster.org/12397 committed in master by Dan Lambright (firstname.lastname@example.org)
Author: Dan Lambright <email@example.com>
Date: Mon Oct 19 20:42:56 2015 -0400
cluster/tier do not abort migration if a single brick is down
When a bricks are down, promotion/demotion should still be possible.
For example, if an EC brick is down, the other bricks are able to
recover the data and migrate it.
Signed-off-by: Dan Lambright <firstname.lastname@example.org>
Tested-by: NetBSD Build System <email@example.com>
Tested-by: Gluster Build System <firstname.lastname@example.org>
Reviewed-by: Joseph Fernandes
This bug is getting closed because a release has been made available that should address the reported issue. In case the problem is still not fixed with glusterfs-3.8.0, please open a new bug report.
glusterfs-3.8.0 has been announced on the Gluster mailinglists , packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist  and the update infrastructure for your distribution.