Bug 927391

Summary: GlusterFileSystem.getFileStatus() hardcodes the block replication factor to zero
Product: [Red Hat Storage] Red Hat Gluster Storage Reporter: Steve Watt <swatt>
Component: rhs-hadoopAssignee: Jay Vyas <jvyas>
Status: CLOSED DUPLICATE QA Contact: hcfs-gluster-bugs
Severity: low Docs Contact:
Priority: medium    
Version: 2.0CC: aavati, matt, rhs-bugs, vbellur
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-04-29 19:59:58 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 947153    

Description Steve Watt 2013-03-25 20:04:34 UTC 
Description of problem:

GlusterFileSystem.getFileStatus() first determines if the object is a file or a directory. If it is a file it returns a new FileStatus objection and passes in 0 for the third parameter, which is the block replication factor. This should be passing in the replica factor set on the volume as indicated by the same methods implementation in the DistributedFileSystem class. To date, we have seen no actual errors with the 0 replica setting, but we need to understand where this gets called by the computational layers, how it gets used and the impact of leaving this hardcoded.
Comment 2 Jay Vyas 2013-04-29 19:59:58 UTC 
Closing as this is essentially a duplicate of 927422 

Updating that bug with the info in this thread.

*** This bug has been marked as a duplicate of bug 927422 ***