Thank you
On Thu, Apr 15, 2021 at 7:20 PM Kane Wilson wrote:
> Yes that warning will still appear because it's a startup check and
> doesn't take into account the disk_access_mode setting.
>
> You may be able to cope with just indexes. Note this is still not an ideal
> solution as you won't be
Yes that warning will still appear because it's a startup check and doesn't
take into account the disk_access_mode setting.
You may be able to cope with just indexes. Note this is still not an ideal
solution as you won't be making full use of your available memory.
raft.so - Cassandra
Also,
I just restarted my Cassandra process by setting "disk_access_mode:
mmap_index_only" and I still see the same WARN message, I believe it's
just a startup check and doesn't rely on the disk_access_mode value
WARN [main] 2021-04-16 00:08:00,088 StartupChecks.java:311 - Maximum
> number of
Thank you Kane and Jeff.
can I survive with a low mmap value of 65530 with "disk_acces_mode =
mmap_index_only" ? does this hold true even for higher workloads with
larger datasets like ~1TB per node?
On Thu, Apr 15, 2021 at 4:43 PM Jeff Jirsa wrote:
> disk_acces_mode = mmap_index_only to use
disk_acces_mode = mmap_index_only to use fewer maps (or disable it entirely
as appropriate).
On Thu, Apr 15, 2021 at 4:42 PM Kane Wilson wrote:
> Cassandra mmaps SSTables into memory, of which there can be many files
> (including all their indexes and what not). Typically it'll do so greedily
Cassandra mmaps SSTables into memory, of which there can be many files
(including all their indexes and what not). Typically it'll do so greedily
until you run out of RAM. 65k map areas tends to be quite low and can
easily be exceeded - you'd likely need very low density nodes to avoid
going over
