> On Apr 16, 2020, at 5:50 PM, Dor Laor wrote:
>
> You should configure swap for safety, better be slow than crash,
>
For most production use cases, it’s almost always better to crash than be slow.
-
To unsubscribe, e-mail
On Thu, Apr 16, 2020 at 5:09 PM Kunal wrote:
>
> Thanks for the responses. Appreciae it.
>
> @Dor, so you are saying if we add "memlock unlimited" in limits.conf, the
> entire heap (Xms=Xmx) can be locked at startup ? Will this be applied to all
> Java processes ? We have couple of Java program
Thank you for the clarifications,
If this is not recommended, our last resort is to upgrade the entire
cluster.
About Kafka Connect, we sound following Source Connectors which can be used
to Ingest data from C* to Kafka .
https://debezium.io/documentation/reference/connectors/cassandra.html
http
Thanks for the responses. Appreciae it.
@Dor, so you are saying if we add "memlock unlimited" in limits.conf, the
entire heap (Xms=Xmx) can be locked at startup ? Will this be applied to
all Java processes ? We have couple of Java programs running with the same
owner.
Thanks
Kunal
On Thu, Apr
It is good to configure swap for the OS but exempt Cassandra
from swapping. Why is it good? Since you never know the
memory utilization of additional agents and processes you or
other admins will run on your server.
So do configure a swap partition.
You can control the eagerness of the kernel by t
Cassandra attempts to lock the heap at startup, but all the memory allocated
after startup is not locked. So you do want to make sure the allowed locked
memory is large.
Disabling or vastly dialing down swappiness is a best practice for all server
software, not just Cassandra, so you should s
Swap is controlled by OS and will use it when running short of memory. I don’t
think you can disable at Cassandra level
Regards,
Nitan
Cell: 510 449 9629
> On Apr 16, 2020, at 5:50 PM, Kunal wrote:
>
>
> Hello,
>
> I need some suggestion from you all. I am new to Cassandra and was reading
Hello,
I need some suggestion from you all. I am new to Cassandra and was reading
Cassandra best practices. On one document, it was mentioned that Cassandra
should not be using swap, it degrades the performance.
My question is instead of disabling swap system wide, can we force
Cassandra not to
If I understand the logic of things like SlabAllocator properly, this is
essentially buffer space that has been allocated for the purpose and C* pulls
off ByteBuffer hunks of it as needed. The notion of reclaiming by the kernel
wouldn’t apply, C* would be managing the use of the space itself.
Hello Erick,
I can see the bootstrap message "Bootstrap
24359390-4443-11ea-af19-1fbf341b76a0" every time, I spin up a 3rd
datacenter. I can confirm that there are no network issues and cluster is
not overloaded, as this is the new cluster without any data. 1 and 2
regions don't have any Bootstrap
I agree – do not aim for a mixed version as normal. Mixed versions are fine
during an upgrade process, but the goal is to complete the upgrade as soon as
possible.
As for other parts of your plan, the Kafka Connector is a “sink-only,” which
means that it can only insert into Cassandra. It doesn
Thanks a lot. We are working on removing views and control the partition
size. I hope the improvements help us
Best regards
Gb
Erick Ramirez 于2020年4月16日周四 下午2:08写道:
> GC collector is G1. I ever repair the node after scale up. The JVM issue
>> reproduced. Can I increase the heap to 40 GB on
12 matches
Mail list logo