Created attachment 1169665 [details] iometer config file Description of problem: When using either a replica 3 or sharded replica 3 volume with virtual machines, profiles that exhibit random writes cause high latencies than can sometimes span several seconds. This has been observed with both fio and iometer as load generators Sequential writes do NOT exhibit this affect Version-Release number of selected component (if applicable): How reproducible: Every time the workload is run this profile is observed Steps to Reproduce: 1. use either an fio workload with random write or an iometer profile (attached) 2. track the latency in the vm with pcp 3. Actual results: High latencies are observed which could impact application response times Expected results: Spikes in random write workloads are accepted - may be in the 10's of milliseconds - but latencies that are between 600ms 2s are a problem Additional info:
Created attachment 1169677 [details] screenshot showing the max latency at 4secs within the iometer run Added a screenshot showing the max latency observed from the iometer run. This is from a single vm running the workload (as per the icf file attached to the case)
This bug is getting closed because GlusteFS-3.7 has reached its end-of-life. Note: This bug is being closed using a script. No verification has been performed to check if it still exists on newer releases of GlusterFS. If this bug still exists in newer GlusterFS releases, please reopen this bug against the newer release.