Bug 1567745 - dht.commithash xattr is not assigned to a newly created volume
Summary: dht.commithash xattr is not assigned to a newly created volume
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Gluster Storage
Classification: Red Hat
Component: distribute
Version: rhgs-3.4
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
: ---
Assignee: Nithya Balachandran
QA Contact: Prasad Desala
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-04-16 07:12 UTC by Prasad Desala
Modified: 2019-10-10 03:12 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-10-10 03:12:22 UTC
Target Upstream Version:


Attachments (Terms of Use)

Description Prasad Desala 2018-04-16 07:12:01 UTC
Description of problem:
=======================
commithash mechanism which lookup optimize uses is not assigned to a newly created volume. 
With cluster.lookup-optimize enabled default in code for 3.4.0, when a new volume is created dht.commithash xattr should be assigned to the volume.

getfattr -d -e hex -m . /bricks/brick*/commit-*/
getfattr: Removing leading '/' from absolute path names
# file: bricks/brick0/commit-b0/
security.selinux=0x73797374656d5f753a6f626a6563745f723a676c7573746572645f627269636b5f743a733000
trusted.gfid=0x00000000000000000000000000000001
trusted.glusterfs.dht=0x0000000100000000000000007ffffffe
trusted.glusterfs.volume-id=0x85e3f07e1e2244b3abafafdccbd446f9

Version-Release number of selected component (if applicable):
3.12.2-7.el7rhgs.x86_64

How reproducible:
always

Steps to Reproduce:
===================
1) On 3.12.2-7.el7rhgs.x86_64 (this build has lookup-optimize enabled by default in code), create a x3 volume.
2) FUSE mount it on a client and do a lookup.
3) Check for commithash xattr on the backend bricks.

Actual results:
===============
dht.commithash xattr is not assigned to a newly created volume.

Expected results:
=================
when a new volume is created with lookup-optimize enabled, dht.commithash xattr should be assigned to the volume.

Comment 10 Nithya Balachandran 2019-10-10 03:12:22 UTC
As the lack of the xattr is treated as a zero commit hash value, this does not affect the functionality. Closing this with WontFix.


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