Thanks.
I'm gonna try and use QUORUM to read and/or write and see if data is
returned consistently.
On Thu, Nov 10, 2011 at 3:00 PM, Jeremiah Jordan <
jeremiah.jor...@morningstar.com> wrote:
> No, that is what I thought you wanted. I was thinking your machines in
> DC1 had extra disk space or
No, that is what I thought you wanted. I was thinking your machines in
DC1 had extra disk space or something...
(I stopped replying to the dev list)
On 11/10/2011 04:09 PM, Subrahmanya Harve wrote:
Thanks Ed and Jeremiah for that useful info.
"I am pretty sure the way you have K1 configured
Thanks Ed and Jeremiah for that useful info.
"I am pretty sure the way you have K1 configured it will be placed across
both DC's as if you had large ring. If you want it only in DC1 you need to
say DC1:1, DC2:0."
Infact i do want K1 to be available across both DCs as if i had a large
ring. I just
I am pretty sure the way you have K1 configured it will be placed across
both DC's as if you had large ring. If you want it only in DC1 you need
to say DC1:1, DC2:0.
If you are writing and reading at ONE you are not guaranteed to get the
data if RF > 1. If RF = 2, and you write with ONE, you d
On Thu, Nov 10, 2011 at 3:27 PM, Subrahmanya Harve <
subrahmanyaha...@gmail.com> wrote:
> I am facing an issue in 0.8.7 cluster -
>
> - I have two clusters in two DCs (rather one cross dc cluster) and two
> keyspaces. But i have only configured one keyspace to replicate data to the
> other DC and
I am facing an issue in 0.8.7 cluster -
- I have two clusters in two DCs (rather one cross dc cluster) and two
keyspaces. But i have only configured one keyspace to replicate data to the
other DC and the other keyspace to not replicate over to the other DC.
Basically this is the way i ran the keys
