[
https://issues.apache.org/jira/browse/CASSANDRA-17763?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17570271#comment-17570271
]
Gil Ganz commented on CASSANDRA-17763:
--------------------------------------
I agree with Caleb, best method is via yaml parameter, not sure it should be
disabled by default though, is there any point in starting a node when pending
compactions are at a really high value like 200? As previously mentioned actual
ideal number depends on many variables, but perhaps it's better to always that
that high value as a baseline. One thing to notice is that it requires hints to
be enabled, otherwise by design each new node will be missing data.
> Allow node to serve traffic only once compactions settle
> --------------------------------------------------------
>
> Key: CASSANDRA-17763
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17763
> Project: Cassandra
> Issue Type: New Feature
> Components: Local/Compaction
> Reporter: Gil Ganz
> Priority: Normal
> Fix For: 4.x
>
>
> Today when nodes are joined to the cluster, once data streaming is completed,
> node starts serving traffic, but it's possible there are a lot of pending
> compactions, so having reads accessing sstables during that time is going to
> make these reads slower and load the server. In some cases performance is so
> bad it can bring the application down.
> Today I overcome this by stopping native transport to a node after join
> finishes, and enabling it after compactions pending reach a certain
> threshold, it would be nice to have that as part of the join process, only
> consider join completed once there are not that many compactions pending.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
