cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jonathan Ellis (JIRA)" <>
Subject [jira] Commented: (CASSANDRA-497) Include bootstrap targets in consistencylevel computations
Date Tue, 20 Oct 2009 22:43:59 GMT


Jonathan Ellis commented on CASSANDRA-497:

Ah, I see what you mean now.  You're right.

So we need to block on write for quorum(normal) + bootstrap, not quorum(normal + bootstrap)

> Include bootstrap targets in consistencylevel computations
> ----------------------------------------------------------
>                 Key: CASSANDRA-497
>                 URL:
>             Project: Cassandra
>          Issue Type: Bug
>            Reporter: Jonathan Ellis
>            Assignee: Jonathan Ellis
>            Priority: Minor
>             Fix For: 0.5
>         Attachments: 0001-CASSANDRA-497-rename-nodePicker-replicationStrategy.txt, 0002-make-write-targets-computable-independent-of-replicati.txt,
0003-Make-EndPoint-objects-immmutable-so-hashcode-can-t-ch.txt, imports.patch
> We want to preserve ConsistencyLevel semantics during bootstrap, and if a CL.quorum/all
write is sent to a bootstrap target, it would have to wait for the forwarded write to complete
to report in turn that the write is good.
> Leaving write propagation to be done by the write originator means we don't have this
extra layer of latency.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message