[Bugs] [Bug 1215571] Data Tiering: add tiering set options to volume set help (cluster.tier-demote-frequency and cluster.tier-promote-frequency)

[bugzilla at redhat.com]

https://bugzilla.redhat.com/show_bug.cgi?id=1215571

Joseph Elwin Fernandes <josferna at redhat.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |josferna at redhat.com



--- Comment #1 from Joseph Elwin Fernandes <josferna at redhat.com> ---
Option: cluster.tier-demote-frequency
Default Value: 0
Description: Defines how often the demotion should be triggered i.e periodicity
of demotion cycles. The value is in secs.

Option: cluster.tier-promote-frequency
Default Value: 0
Description: Defines how often the promotion should be triggered i.e
periodicity of promotion cycles. The value is in secs.

Option: cluster.read-freq-threshold
Default Value: 0
Description: Defines the number of reads, in a promotion/demotion cycle, that
would mark a file HOT for promotion. Any file that has read hits less than this
value will be considers COLD and will be demoted.

Option: cluster.write-freq-threshold 0
Default Value: 0
Description: Defines the number of writes, in a promotion/demotion cycle, that
would mark a file HOT for promotion. Any file that has write hits less than
this value will be considers COLD and will be demoted.

Option: features.ctr-enabled
Default Value: off
Description: Enables the CTR

Option: features.record-counters
Default Value: off
Description: Its a CTR Xlator option to enable recording write and read heat
counters.

Option: features.ctr_link_consistency
Default Value: off
Description: Enable a crash consistent way of recording hardlink updates by CTR
Xlator. When recording in a crash consistent way the IO's will be slow.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are on the CC list for the bug.