Thanks all for your valuable inputs. We will try some of the suggested
methods in this thread, and see how it goes. We will keep you updated on
our progress.
Thanks a lot once again!
Jaydeep
On Fri, May 5, 2023 at 8:55 AM Bowen Song via user <
user@cassandra.apache.org> wrote:
> Depending on
Have you thought of using "-Dcassandra.replace_address_first_boot=..."
(or "-Dcassandra.replace_address=..." if you are using an older
version)? This will not result in a topology change, which means
"nodetool cleanup" is not needed after the operation is completed.
On 05/05/2023 05:24,
We are doing the "adding a node then decommissioning a node" to
achieve better availability. Replacing a node need to shut down one node
first, if another node is down during the node replacement period, we will
get availability drop because most of our use case is local_quorum with
replication
Depending on the number of vnodes per server, the probability and
severity (i.e. the size of the affected token ranges) of an availability
degradation due to a server failure during node replacement may be
small. You also have the choice of increasing the RF if that's still not
acceptable.
I run clean-up in parallel, not serially, since it is a node-only kind of
operation. And I only run in the impacted DC. With only 300 GB on a node,
clean-up should not take very long. Check your compactionthroughput.
I ran clean-up in parallel on 53 nodes with over 3 TB of data each. It took
Lots of caveats on these suggestions, let me try to hit most of them.
Cleanup in parallel is good and fine and common. Limit number of threads in
cleanup if you're using lots of vnodes, so each node runs one at a time and
not all nodes use all your cores at the same time.
If a host is fully
https://infra.apache.org/slack.html
The directions say someone with apache.org powers needs to do it.
I lost my job recently and I was in the slack with my work account.
Thanks, Jeff, for the detailed steps and summary.
We will keep the community (this thread) up to date on how it plays out in
our fleet.
Jaydeep
On Fri, May 5, 2023 at 9:10 AM Jeff Jirsa wrote:
> Lots of caveats on these suggestions, let me try to hit most of them.
>
> Cleanup in parallel is
The Cassandra team is pleased to announce the release of Apache Cassandra
version 3.11.15.
Apache Cassandra is a fully distributed database. It is the right choice when
you need scalability and high availability without compromising performance.
http://cassandra.apache.org/
Downloads of
You can replace the node directly why to add a node and decommission the
another node. Just replace the node with the new node and your topology
remains the same so no need to run the cleanup .
On Fri, May 5, 2023 at 10:26 AM Jaydeep Chovatia
wrote:
> We use STCS, and our experience with
10 matches
Mail list logo
