[Bugs] [Bug 1282076] New: cache mode must be the default mode for tiered volumes
bugzilla at redhat.com
bugzilla at redhat.com
Sat Nov 14 19:27:55 UTC 2015
https://bugzilla.redhat.com/show_bug.cgi?id=1282076
Bug ID: 1282076
Summary: cache mode must be the default mode for tiered volumes
Product: GlusterFS
Version: mainline
Component: tiering
Assignee: bugs at gluster.org
Reporter: dlambrig at redhat.com
QA Contact: bugs at gluster.org
CC: bugs at gluster.org
Description of problem:
Make cache mode the default for tiering
Version-Release number of selected component (if applicable):
How reproducible:
always
Steps to Reproduce:
1.
2.
3.
Actual results:
test mode is default
Expected results:
cache mode is default
Additional info:
test mode is for internal QE testing and should not be used by customers. Test
mode forces all unused data to be destaged from the hot tier when no IO is
received, rendering the SSD unused / wasted. If the demote cycle time is made
large as a workaround, data will stay on the hot tier but will not react to
changing conditions, which means unused data may fill the hot tier resource. A
long cycle times also means the system will stay static even when close to
full, which will put the system into a degraded mode.
The cache mode is supposed to keep data on the hot tier but also demote data
quickly when the hot tier is close to full. The cycle time can be set to a
desired reaction time to swap out lesser used data and bring in more frequently
accessed data without flushing the entire SSD.
--
You are receiving this mail because:
You are the QA Contact for the bug.
You are on the CC list for the bug.
You are the assignee for the bug.
More information about the Bugs
mailing list