[
https://issues.apache.org/jira/browse/CASSANDRA-4358?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vijay resolved CASSANDRA-4358.
------------------------------
Resolution: Not A Problem
{quote}
But at least doing it for one source and throwing the others into L0 would be a
decent optimization.
{quote}
Sure that reduces fragmentation. In-fact we stream only from 2 nodes but the
range requests are fragmented we can send one request per node instead of one
request per range. (will try this in a different ticket).
{quote}
Shouldn't the new SEVERITY level in the dsnitch avoid the node until it's done
compacting?
{quote}
it should, but still the compaction can run forever with throttle enabled. We
could run into issues when another node goes down.
{quote}
So imo it will be much less fragile to let user do that and start thrift once
they consider the new node "stable" enough rather than trying to do that
automatically.
{quote}
It is scriptable both un-throttling and stopping thrift traffic. Let me close
this ticket and try that route (Priam).
> Delay Joining the ring until bootstrap and its compaction completes
> -------------------------------------------------------------------
>
> Key: CASSANDRA-4358
> URL: https://issues.apache.org/jira/browse/CASSANDRA-4358
> Project: Cassandra
> Issue Type: Improvement
> Components: Core
> Affects Versions: 1.1.1, 1.2
> Reporter: Vijay
> Priority: Minor
> Fix For: 1.2
>
>
> LCS adds a lot of small SST's while bootstrapping a node (after streaming),
> followed by a large amount of compactions.
> We might want to do the following to speedup the compaction and reduce the
> impact to the incoming traffic:
> 1) Delay the node from joining the ring and wait until the node settles down
> with compactions.
> 2) Un-throttle the compactions and do it ASAP.
> 3) Once the node settles down we can enable thrift and join the ring.
> at the Least it might be better for us to avoid thrift traffic until the
> compaction completes.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
