Note: It is recommended that the coordinator console is used to configure rules. However, the coordinator node does have HTTP endpoints to programmatically configure rules.
Load rules indicate how many replicants of a segment should exist in a server tier.
Interval load rules are of the form:
{ "type" : "loadByInterval", "interval" : "2012-01-01/2013-01-01", "tier" : "hot" }
type
- this should always be “loadByInterval”interval
- A JSON Object representing ISO-8601 Intervalstier
- the configured historical node tierPeriod load rules are of the form:
{ "type" : "loadByPeriod", "period" : "P1M", "tier" : "hot" }
type
- this should always be “loadByPeriod”period
- A JSON Object representing ISO-8601 Periodstier
- the configured historical node tierThe interval of a segment will be compared against the specified period. The rule matches if the period overlaps the interval.
Drop rules indicate when segments should be dropped from the cluster.
Interval drop rules are of the form:
{ "type" : "dropByInterval", "interval" : "2012-01-01/2013-01-01" }
type
- this should always be “dropByInterval”interval
- A JSON Object representing ISO-8601 PeriodsA segment is dropped if the interval contains the interval of the segment.
Period drop rules are of the form:
{ "type" : "dropByPeriod", "period" : "P1M" }
type
- this should always be “dropByPeriod”period
- A JSON Object representing ISO-8601 PeriodsThe interval of a segment will be compared against the specified period. The period is from some time in the past to the current time. The rule matches if the period contains the interval.