Bug 1395221 - Remove-brick: Remove-brick rebalance failed during continuous lookup+directory rename
Summary: Remove-brick: Remove-brick rebalance failed during continuous lookup+director...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: GlusterFS
Classification: Community
Component: distribute
Version: mainline
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ---
Assignee: Susant Kumar Palai
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-11-15 12:54 UTC by Susant Kumar Palai
Modified: 2018-08-29 03:35 UTC (History)
7 users (show)

Fixed In Version: glusterfs-4.1.3 (or later)
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 1368437
Environment:
Last Closed: 2018-08-29 03:35:48 UTC
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Embargoed:


Attachments (Terms of Use)

Comment 1 Worker Ant 2016-12-14 07:38:47 UTC
REVIEW: http://review.gluster.org/15846 (dht/rebalance: reveify lookup failures) posted (#3) for review on master by Susant Palai (spalai)

Comment 2 Worker Ant 2016-12-14 09:22:11 UTC
REVIEW: http://review.gluster.org/15846 (dht/rebalance: reverify lookup failures) posted (#4) for review on master by Susant Palai (spalai)

Comment 3 Worker Ant 2016-12-19 09:35:03 UTC
REVIEW: http://review.gluster.org/15846 (dht/rebalance: reverify lookup failures) posted (#5) for review on master by Susant Palai (spalai)

Comment 4 Worker Ant 2016-12-20 12:08:28 UTC
REVIEW: http://review.gluster.org/15846 (dht/rebalance: reverify lookup failures) posted (#6) for review on master by Susant Palai (spalai)

Comment 5 Worker Ant 2016-12-21 09:03:06 UTC
REVIEW: http://review.gluster.org/15846 (dht/rebalance: reverify lookup failures) posted (#7) for review on master by Susant Palai (spalai)

Comment 6 Amar Tumballi 2018-08-29 03:35:48 UTC
This update is done in bulk based on the state of the patch and the time since last activity. If the issue is still seen, please reopen the bug.


Note You need to log in before you can comment on or make changes to this bug.