The node which shows that bootstrap session from January 31 won't go away
until you restart it. But you don't need to restart unless it's affecting
the node's operation. Cheers!
>
I usually recommend following document:
https://docs.datastax.com/en/dse/5.1/dse-dev/datastax_enterprise/config/configRecommendedSettings.html
- it's about DSE, but applicable to OSS Cassandra as well...
Kunal at "Thu, 16 Apr 2020 15:49:35 -0700" wrote:
K> Hello,
K>
K> I need some suggesti
I think there is some potential yak shaving to worrying excessively about swap.
The reality is that you should know the memory demands of what you are running
on your C* nodes and have things configured so that significant swap would be a
highly abnormal situation.
I'd expect to see excessive
I would pay attention to the dirty background writer activity at the O/S level.
If you see that it isn’t keeping up with flushing changes to disk, then you’ll
be in an even worse situation as you increase the JVM heap size, because that
will be done at the cost of the size of available buffer c
This is not causing any issues and with the restart it goes away. But I
would like understand why this is happening only on certain DC but not all
DC.
I am depending on this output to find whether a node is doing any streams
or not.
On Fri, Apr 17, 2020 at 2:37 AM Erick Ramirez
wrote:
> The node
If you're upgrading the whole cluster, I'd recommend going ahead and
upgrading all the way to 3.11.6 if possible. In my experience it's been
noticeably faster, more reliable, and easier to manage compared to 3.0.x.
On Thu, Apr 16, 2020 at 6:37 PM Ashika Umagiliya
wrote:
> Thank you for the clar
>
> If you're upgrading the whole cluster, I'd recommend going ahead and
> upgrading all the way to 3.11.6 if possible. In my experience it's been
> noticeably faster, more reliable, and easier to manage compared to 3.0.x.
>
Thanks, Elliott. That's really good to know. 👍
What will be the impact of setting the value of XX:MaxDirectMemorySize to
some low value. Currently default value for off heap is equal to heap
memory.
I saw this open ticket discussing this but could not infer much from it.
https://issues.apache.org/jira/browse/CASSANDRA-10930
Regards
Manish
Like most things, it depends on (a) what you're allowing and (b) how much
your nodes require. MaxDirectMemorySize is the upper-bound for off-heap
memory used for the direct byte buffer. C* uses it for Netty so if your
nodes are busy servicing requests, they'd have more IO threads consuming
memory.
>From the codebase as much I understood, if once a buffer is being
allocated, then it is not freed and added to a recyclable pool. When a new
request comes effort is made to fetch memory from recyclable pool and if is
not available new allocation request is made. And while allocating a new
request
10 matches
Mail list logo
