Re: Nodetool command to pre-load the chunk cache

Something additional to consider (outside C* fix) is using a tool like happycache to have consistent pagecache between them. Might be sufficient if the data is in memory already. Chris On Tue, Mar 21, 2023 at 2:48 PM Jeff Jirsa wrote: > We

Re: Nodetool command to pre-load the chunk cache

We serialize the other caches to disk to avoid cold-start problems, I don't see why we couldn't also serialize the chunk cache? Seems worth a JIRA to me. Until then, you can probably use the dynamic snitch (badness + severity) to route around newly started hosts. I'm actually pretty surprised

Re: Nodetool command to pre-load the chunk cache

It sounds like a bad policy, and you should push for that to be changed. Failing that, you have some options: 1. Use faster disks. This improves cold start performance, without relying on the caches. 2. Rely on row cache instead. It can be saved periodically and loaded at startup time. 3.

Nodetool command to pre-load the chunk cache

Hi Team, We are heavy users of Cassandra at a pretty big bank. Security measures require us to constantly refresh our C* nodes every x number of days. We normally do this in a rolling fashion, taking one node down at a time and then refreshing it with a new instance. This process has been