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.
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 ***