stand-eventually-consistent-tp6038330p6038330.html
Sent from the cassandra-u...@incubator.apache.org mailing list archive at
Nabble.com.
e.com/Understand-eventually-consistent-tp6038330p6038330.html
Sent from the cassandra-u...@incubator.apache.org mailing list archive at Nabble.com.
curs cassandra will return to the client only when the
> writes go to commit log on 2 nodes successfully?
>
> 2. When read happens cassandra will return only when it is able to read
> from
> 2 nodes and determine that it has consistent copy?
> --
> View this message
turn to the client only when the
>> writes go to commit log on 2 nodes successfully?
>>
>> 2. When read happens cassandra will return only when it is able to read
>> from
>> 2 nodes and determine that it has consistent copy?
>> --
>> View this message in context:
>> http://cassandra-user-incubator-apache-org.3065146.n2.nabble.com/Understand-eventually-consistent-tp6038330p6038330.html
>> Sent from the cassandra-u...@incubator.apache.org mailing list archive at
>> Nabble.com.
>>
>>
>
t happens?
>>>
>>> 1. When write occurs cassandra will return to the client only when the
>>> writes go to commit log on 2 nodes successfully?
>>>
>>> 2. When read happens cassandra will return only when it is able to read
>>> from
>>> 2 nodes and determine that it has consistent copy?
>>> --
>>> View this message in context:
>>> http://cassandra-user-incubator-apache-org.3065146.n2.nabble.com/Understand-eventually-consistent-tp6038330p6038330.html
>>> Sent from the cassandra-u...@incubator.apache.org mailing list archive at
>>> Nabble.com.
>>
>
>
On Fri, Feb 18, 2011 at 12:00 AM, Stu Hood wrote:
> But, the reason that it isn't safe to say that we are a strongly consistent
> store is that if 2 of your 3 replicas were to die and come back with no
> data, QUORUM might return the wrong result.
Not so. If you allow vaporizing arbitrary numbe
andra-user-incubator-apache-org.3065146.n2.nabble.com/Understand-eventually-consistent-tp6038330p6040893.html
Sent from the cassandra-u...@incubator.apache.org mailing list archive at
Nabble.com.
ventually consistent.
> --
> View this message in context:
> http://cassandra-user-incubator-apache-org.3065146.n2.nabble.com/Understand-eventually-consistent-tp6038330p6040893.html
> Sent from the cassandra-u...@incubator.apache.org mailing list archive at
> Nabble.com.
>
27;t this same as other RDBMS? Oracle does the same thing
> it writes to REDO log and somepoint later does a checkpoint and flushes data
> to disk. But RDBMS is not called eventually consistent.
> --
> View this message in context:
> http://cassandra-user-incubator-apache-org.3065146.n2
On Fri, 2011-02-18 at 12:01 -0600, Anthony John wrote:
> Writes will go thru w/hinted handoff, read will fail
That is not correct. Hinted handoffs do not count toward reaching QUORUM
counts.[1]
[1] http://wiki.apache.org/cassandra/HintedHandoff
--
David Strauss
| da...@davidstrauss.net
|
other problem with this logic?
--
View this message in context:
http://cassandra-user-incubator-apache-org.3065146.n2.nabble.com/Understand-eventually-consistent-tp6038330p6049678.html
Sent from the cassandra-u...@incubator.apache.org mailing list archive at
Nabble.com.
> I read the logic of why writes are not allowed. But other alternative is to
> allow write and just fail the reads until it's in sync again. Is there some
> other problem with this logic?
The problem lies in "until it's in sync again". A given node cannot
easily know for a given read, whether "e
message in context:
http://cassandra-user-incubator-apache-org.3065146.n2.nabble.com/Understand-eventually-consistent-tp6038330p6058576.html
Sent from the cassandra-u...@incubator.apache.org mailing list archive at
Nabble.com.
View this message in context:
> http://cassandra-user-incubator-apache-org.3065146.n2.nabble.com/Understand-eventually-consistent-tp6038330p6058576.html
> Sent from the cassandra-u...@incubator.apache.org mailing list archive at
> Nabble.com.
ll the nodes to be up.
http://wiki.apache.org/cassandra/API
--
View this message in context:
http://cassandra-user-incubator-apache-org.3065146.n2.nabble.com/Understand-eventually-consistent-tp6038330p6061399.html
Sent from the cassandra-u...@incubator.apache.org mailing list archive at
Nabble.com.
he nodes to be up.
> http://wiki.apache.org/cassandra/API
>
> --
> View this message in context:
> http://cassandra-user-incubator-apache-org.3065146.n2.nabble.com/Understand-eventually-consistent-tp6038330p6061399.html
> Sent from the cassandra-u...@incubator.apache.org mailing list archive at
> Nabble.com.
>
/Understand-eventually-consistent-tp6038330p6061593.html
Sent from the cassandra-u...@incubator.apache.org mailing list archive at
Nabble.com.
On Thu, Feb 24, 2011 at 1:26 PM, mcasandra wrote:
>
> Does HH count towards QUORUM? Say RF=1 and CL of W=QUORUM and one node
> that
> owns the key dies. Would subsequent write operations for that key be
> successful? I am guessing it will not succeed.
>
No, it would not succeed. It would only s
ew this message in context:
> http://cassandra-user-incubator-apache-org.3065146.n2.nabble.com/Understand-eventually-consistent-tp6038330p6061593.html
> Sent from the cassandra-u...@incubator.apache.org mailing list archive at
> Nabble.com.
>
UORUM and one node
>> that
>> owns the key dies. Would subsequent write operations for that key be
>> successful? I am guessing it will not succeed.
>> --
>> View this message in context:
>> http://cassandra-user-incubator-apache-org.3065146.n2.nabble.com/Understand-e
;
> >
> > On Thu, Feb 24, 2011 at 4:26 PM, mcasandra
> wrote:
> >
> >>
> >> Does HH count towards QUORUM? Say RF=1 and CL of W=QUORUM and one node
> >> that
> >> owns the key dies. Would subsequent write operations for that key be
> >
Thanks. This helps a lot!
--
View this message in context:
http://cassandra-user-incubator-apache-org.3065146.n2.nabble.com/Understand-eventually-consistent-tp6038330p6061838.html
Sent from the cassandra-u...@incubator.apache.org mailing list archive at
Nabble.com.
You're welcomed!
On Thu, Feb 24, 2011 at 5:30 PM, mcasandra wrote:
>
> Thanks. This helps a lot!
> --
> View this message in context:
> http://cassandra-user-incubator-apache-org.3065146.n2.nabble.com/Understand-eventually-consistent-tp6038330p6061838.html
> Se
23 matches
Mail list logo
