Bug 854753

Summary: Hadoop Integration, Address known write performance issues
Product: [Community] GlusterFS Reporter: Kaleb KEITHLEY <kkeithle>
Component: gluster-hadoopAssignee: Diane Feddema <dfeddema>
Status: CLOSED NOTABUG QA Contact: hcfs-gluster-bugs
Severity: unspecified Docs Contact:
Priority: medium    
Version: mainlineCC: aavati, bugs, eboyd, matt, poelstra, rhs-bugs, vbellur
Target Milestone: ---Keywords: FutureFeature, Triaged
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-04-07 09:16:22 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:

Description Kaleb KEITHLEY 2012-09-05 18:27:21 UTC 
Description of problem:

Blocker BZ for RHS 2.1

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


How reproducible:


Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:
Comment 4 Steve Watt 2013-05-10 17:50:05 UTC 
Assigning to Diane to analyze write performance. The current observation is that because of the glusterfs use of the elastic hashing algorithm, writes get written to the server that will hosts the data according the hash. In some cases, this results in non-local writes.
Comment 6 Kaleb KEITHLEY 2015-04-07 09:16:22 UTC 
This was opened to track a concern raised by Doug Williams which ultimately turned out to be a red herring.

Closing as it's old and there doesn't seem to be any real issue. Please open a new BZ if this is not the case.

Thanks,