[
https://issues.apache.org/jira/browse/CASSANDRA-20362?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
guo Maxwell updated CASSANDRA-20362:
------------------------------------
Change Category: Operability
Complexity: Low Hanging Fruit
Reviewers: guo Maxwell
Priority: Normal (was: Low)
Status: Open (was: Triage Needed)
> add setcachecapacity to nodetool
> --------------------------------
>
> Key: CASSANDRA-20362
> URL: https://issues.apache.org/jira/browse/CASSANDRA-20362
> Project: Apache Cassandra
> Issue Type: New Feature
> Components: Tool/nodetool
> Reporter: Ling Mao
> Assignee: Ling Mao
> Priority: Normal
> Fix For: 5.x
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> When I want to restart a Cassandra node, I aim to immediately flush my entire
> local cache to expedite the cache warm-up process. Currently, I can achieve
> this by using the _*{{setcacheperiod}}*_ command:
> {code:java}
> ./nodetool setcacheperiod 60 60 60 {code}
> This command helps me flush the cache as soon as possible.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
