Re: Uneven token distribution with allocate_tokens_for_keyspace

2019-12-04 Thread Anthony Grasso
Hi Enrico, Glad to hear the problem has been resolved and thank you for the feedback! Kind regards, Anthony On Mon, 2 Dec 2019 at 22:03, Enrico Cavallin wrote: > Hi Anthony, > thank you for your hints, now the new DC is well balanced within 2%. > I did read your article, but I thought it was n

Re: "Maximum memory usage reached (512.000MiB), cannot allocate chunk of 1.000MiB"

2019-12-04 Thread Reid Pinchback
Probably helps to think of how swap actually functions. It has a valid place, so long as the behavior of the kernel and the OOM killer are understood. You can have a lot of cold pages that have nothing at all to do with C*. If you look at where memory goes, it isn’t surprising to see things th

Re: "Maximum memory usage reached (512.000MiB), cannot allocate chunk of 1.000MiB"

2019-12-04 Thread Shishir Kumar
Correct. Normally one should avoid this, as performance might degrade, but system will not die (until process gets paged out). In production we haven't done this (just changed mmap_index_only). We have an environment which gets used for customer to train/beta test that grows rapidly. Investing on

Re: "Maximum memory usage reached (512.000MiB), cannot allocate chunk of 1.000MiB"

2019-12-04 Thread Hossein Ghiyasi Mehr
"3. Though Datastax do not recommended and recommends Horizontal scale, so based on your requirement alternate old fashion option is to add swap space." Hi Shishir, swap isn't recommended by DataStax! *---* *VafaTech.com - A Total Solution for Da