[
https://issues.apache.org/jira/browse/CASSANDRA-3868?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13214918#comment-13214918
]
Peter Schuller commented on CASSANDRA-3868:
-------------------------------------------
On a non-trivially sized cluster, especially given that capacity adds are
currently kind of difficult to do, the probability that you're going to be
adding a node in a small time window of running with ROW set to off, seems much
smaller than the probability that you have to e.g. replace a node due to a bad
disk. And in the replacement case, you will loose increments if you're at
CL.ONE (assuming that writes are being dropped left and right since the
hypothesized situation is that you're having throughput/capacity problems). Of
course if you expect to turn off ROW and then add a bunch of nodes to mitigate
the effect, *now* you're in trouble. :)
I can troll through the docs/source and add comments and submit the patch to
that effect as you suggest, if you're comfortable going this route.
> Remove or nullify replicate_on_write option
> -------------------------------------------
>
> Key: CASSANDRA-3868
> URL: https://issues.apache.org/jira/browse/CASSANDRA-3868
> Project: Cassandra
> Issue Type: Improvement
> Components: Core
> Affects Versions: 0.8.0
> Reporter: Brandon Williams
> Fix For: 1.1.0
>
> Attachments: 3868.txt
>
>
> My understanding from Sylvain is that setting this option to false is rather
> dangerous/stupid, and you should basically never do it. So 1.1 is a good
> time to get rid of it, or make it a no-op.
--
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
