Bug 1428086 - Make Halo calculate & use average latencies, not realtime
Summary: Make Halo calculate & use average latencies, not realtime
Keywords:
Status: CLOSED DEFERRED
Alias: None
Product: GlusterFS
Classification: Community
Component: replicate
Version: mainline
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: bugs@gluster.org
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-03-01 19:06 UTC by Vijay Bellur
Modified: 2019-03-08 04:42 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-03-08 04:42:43 UTC
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Embargoed:

Attachments (Terms of Use)

Description Vijay Bellur 2017-03-01 19:06:36 UTC 
Make Halo calculate & use average latencies, not realtime

Summary:
- Realtime latencies in practice have far too much jitter under real
  loading conditions, instead let's use a running average which will get
  very "heavy" over time such that temp spikes in brick latency will not
  affect halo decisions.

Test Plan: - Run prove tests

Reviewed By: mmckeen

Change-Id: I5ebf9bc93c67d9a226287796dd7ca5eeb7b1cfa5
Signed-off-by: Kevin Vigor <kvigor>
Reviewed-on: http://review.gluster.org/16301
CentOS-regression: Gluster Build System <jenkins.org>
NetBSD-regression: NetBSD Build System <jenkins.org>
Smoke: Gluster Build System <jenkins.org>
Reviewed-by: Shreyas Siravara <sshreyas>
Comment 1 Ravishankar N 2019-03-08 04:42:43 UTC 
Basic halo replication functionality is present in master.There are no immediate plans for forward porting any pending halo related patches from the release-3.8-fb branch into master, hence closing the bug. Please feel free to re-open if there is a need for re-assessment.
Note You need to log in before you can comment on or make changes to this bug.