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:
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.
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,