[
https://issues.apache.org/jira/browse/CASSANDRA-7870?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14120034#comment-14120034
]
Sergio Bossa edited comment on CASSANDRA-7870 at 9/3/14 4:27 PM:
-----------------------------------------------------------------
bq. for the same reason that we reject quorum when only 1 node of 3 is alive:
because we can't deliver our contract
Consistency level and atomic batches both fulfil a contract but a different
one: while it is correct to preserve the requested CL when there are no enough
nodes alive, forbidding an atomic batch because there's only one node alive
looks to me like an implementation artifact, rather than a contract fulfilment,
as if the coordinator node dies midway, it should be able to replay its own
logged batch at restart. Or am I missing anything?
was (Author: sbtourist):
bq. for the same reason that we reject quorum when only 1 node of 3 is alive:
because we can't deliver our contract
Consistency level and atomic batches both fulfil a contract but a different
one: while it is correct to preserve the requested CL when there are no enough
nodes alive, forbidding an atomic batch because there's only one node alive
looks to me like an implementation artifact, rather than a contract fulfilment,
as if the coordinator node dies midway, it should be able to reply its own
logged batch. Or am I missing anything?
> Cannot execute logged batch when only the coordinator node is alive
> -------------------------------------------------------------------
>
> Key: CASSANDRA-7870
> URL: https://issues.apache.org/jira/browse/CASSANDRA-7870
> Project: Cassandra
> Issue Type: Bug
> Components: Core
> Reporter: Sergio Bossa
> Priority: Critical
>
> As per issue summary.
> This is probably a bug, rather than a consequence of needing to replicate the
> batchlog, as if only the coordinator is alive the batch cannot be partially
> executed on other nodes (as there are no other nodes).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
