[Bugs] [Bug 1306852] Tiering threads can starve each other
bugzilla at redhat.com
bugzilla at redhat.com
Mon Feb 29 01:32:28 UTC 2016
https://bugzilla.redhat.com/show_bug.cgi?id=1306852
--- Comment #4 from Vijay Bellur <vbellur at redhat.com> ---
COMMIT: http://review.gluster.org/13433 committed in master by Dan Lambright
(dlambrig at redhat.com)
------
commit 87b19927ed41cfe47579c1c069cb6640fd47a732
Author: Dan Lambright <dlambrig at redhat.com>
Date: Tue Feb 9 03:37:31 2016 +0000
cluster/tier: make promotion and demotion independant
Currently a main loop in tiering spawns promotion and demotion threads,
and does a join to wait for them to complete. When one of the two
threads takes a long time, the main thread waits for it
before exiting the join. It may wait so long the scheduled time
for the other thread is skipped. In the case of demotion, it may be
a long time before another attempt. This patch fixes that by
making the promotion and demotion activities independant. A side
effect of this change is the logic is significantly simplified.
Change-Id: I1196bd4bbfc95e8aa326a9bd4ebf395032369d1c
BUG: 1306852
Signed-off-by: Dan Lambright <dlambrig at redhat.com>
Reviewed-on: http://review.gluster.org/13433
Smoke: Gluster Build System <jenkins at build.gluster.com>
Reviewed-by: Joseph Fernandes
NetBSD-regression: NetBSD Build System <jenkins at build.gluster.org>
CentOS-regression: Gluster Build System <jenkins at build.gluster.com>
--
You are receiving this mail because:
You are the QA Contact for the bug.
You are on the CC list for the bug.
More information about the Bugs
mailing list