Bug 1128750 - DHT:REBALANCE- random rebalance migration failures saying "failed to get node-uuid"
Summary: DHT:REBALANCE- random rebalance migration failures saying "failed to get node...
Alias: None
Product: Red Hat Gluster Storage
Classification: Red Hat
Component: distribute
Version: 2.1
Hardware: x86_64
OS: Linux
Target Milestone: ---
: ---
Assignee: Bug Updates Notification Mailing List
QA Contact:
Depends On:
Blocks: 1173332
TreeView+ depends on / blocked
Reported: 2014-08-11 13:13 UTC by shylesh
Modified: 2015-11-18 09:28 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
: 1173332 (view as bug list)
Last Closed: 2015-11-18 09:28:46 UTC

Attachments (Terms of Use)

Description shylesh 2014-08-11 13:13:25 UTC
Description of problem:
Rebalance migrations fails randomly with the error message "failed to get node-uuid"

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

How reproducible:

Steps to Reproduce:
1.created a dist-rep volume of 40 bricks 
2.did kernel untar on the mount point
3.add-brick and start rebalance

Actual results:

Random migration failures

Additional info:
[2014-08-11 11:31:57.949696] W [dht-linkfile.c:44:dht_linkfile_lookup_cbk] 0-self-dht: got non-linkfile self-replicate-1:/level1/linux-
[2014-08-11 11:31:57.950446] W [afr-inode-read.c:846:afr_getxattr_node_uuid_cbk] 0-self-replicate-7: op_ret (-1): Re-querying afr-child (1/2)
[2014-08-11 11:31:57.950981] E [dht-common.c:2484:dht_vgetxattr_cbk] 0-self-dht: Subvolume self-replicate-7 returned -1 (No such file or directory)
[2014-08-11 11:31:57.951097] E [dht-rebalance.c:1277:gf_defrag_migrate_data] 0-self-dht: Failed to get node-uuid for /level1/linux-
[2014-08-11 11:31:57.983117] I [dht-rebalance.c:708:dht_migrate_file] 0-self-dht: /level1/linux- attempting to move from self-replicate-16 to self-replicate-20
[2014-08-11 11:31:58.113125] I [dht-common.c:1010:dht_lookup_everywhere_done] 0-self-dht: _RR_ STATUS: hashed_subvol self-replicate-20cached_subvol self-replicate-20

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