[ 
https://issues.apache.org/jira/browse/CASSANDRA-4285?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13408147#comment-13408147
 ] 

Sylvain Lebresne commented on CASSANDRA-4285:
---------------------------------------------

bq. Our hands may be tied though, how do you default to RF=2 and not screw over 
single node clusters?

Yeah, that's the thing I haven't really figure out yet. Maybe it wouldn't be 
too hard to check at startup for each node if there is more than one node and 
then update the RF to 2. But that's a bit hacky. It's just that the DCL will be 
an internal thing, and I think it would be really great if 90% of users don't 
have to even know it exists, even less have to change the RF. But if we don't 
have a better solution, the WARN thing might be an option.

bq. So if we can get to a place where clients don't need to retry except in 
obscure corner cases

I agree. What I'm saying is that CASSANDRA-4414 is doing just that and actually 
solves the problem not only for atomic batches but for writes in general.

bq. which is where the InProgressException comes in

Again, really just saying that adding InProgressException is just a subpart of 
CASSANDRA-4414 (the ticket suggests reusing TOE and adding info with it, but 
I'm fine discussion the option of adding other exception instead (which would 
achieve the exact same thing)).
                
> Atomic, eventually-consistent batches
> -------------------------------------
>
>                 Key: CASSANDRA-4285
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-4285
>             Project: Cassandra
>          Issue Type: New Feature
>          Components: API, Core
>            Reporter: Jonathan Ellis
>            Assignee: Jonathan Ellis
>
> I discussed this in the context of triggers (CASSANDRA-1311) but it's useful 
> as a standalone feature as well.

--
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

        

Reply via email to