Quorum is defined as
(replication_factor / 2) + 1
therefore quorum when rf = 2 is 2! so in your case, both nodes must be up.
Really, using Quorum only starts making sense as a 'quorum' when RF=3
On 07/26/2012 10:38 PM, Yan Chunlu wrote:
I am using Cassandra 1.0.2, have a 3 nodes
Sorry for the confusion created. I need to store emails registered
just for a single application. So although my data model would fit
into just a single row. But is storing a hundred million columns(col
name size= 8 byte; col value size=4 byte ) in a single row a good idea
? I am very much
Hello!
if we are dealing with append-only data model, so what if I disable
compaction on certain CF ?
any side effect ?
can I do it with
update column family with compaction_strategy = null ?
Cheers,
Ilya Shipitsin
setMaxCompactionThreshold(0)
setMinCompactionThreshold(0)
2012/7/27 Илья Шипицин chipits...@gmail.com
Hello!
if we are dealing with append-only data model, so what if I disable
compaction on certain CF ?
any side effect ?
can I do it with
update column family with
a) how does that setting affect C* in a non-restoring start?
renew_counter_id regenerates a new NodeId for the cassandra VM which
is used to keep track of the counter shards the node holds. If you
regenerate node ids on each restart, you will most likely corrupt your
counter data.
The
What about if I spread these columns across 20 rows ? Then I have to
query each of these 20 rows for 500 columns. but still this seems a
better solution than one row for all cols or separate row for each
email id approaches !?
On Fri, Jul 27, 2012 at 11:36 AM, Aklin_81 asdk...@gmail.com wrote:
HI!
I tried starting a cluster with
Cluster started with these options:
--clustername Name --totalnodes 3 --version community --release 1.0.8
But Cassandra's version is 1.1.2
Thanks
*Tamar Fraenkel *
Senior Software Engineer, TOK Media
[image: Inline image 1]
ta...@tok-media.com
Tel: +972 2
Hi again,
Nobody has a clue about this issue ?
I'm still facing this problem.
Alain
2012/7/23 Alain RODRIGUEZ arodr...@gmail.com:
Does anyone knows how to totally remove a dead node that only appears
when doing a describe cluster from the cli ?
I still got this issue in my production
nope
my last ideas would be (and I am not sure these are the best)
- try removetoken with -f option. I do not believe it will change anything
but...
- try nodeltool ring on ALL nodes and check all nodes see the unreachable
node. If not, you could maybe juste decommission the one(s) that see
Dave, per my understanding of Yan's description he has 3 nodes and took one
down manually to test; that should have worked, no?
On Thu, Jul 26, 2012 at 11:00 PM, Dave Brosius dbros...@mebigfatguy.comwrote:
Quorum is defined as
(replication_factor / 2) + 1
therefore quorum when rf = 2 is 2!
I think Dave is right, I have read this article again:
http://thelastpickle.com/2011/07/04/Cassandra-Query-Plans/
I have data on two nodes, and QUORUM read means it need read from both
two nodes.
I guess I need to increase the RF to 3, to make the system can tolerance
one node failure.
thanks
Ah!
Yan I think you want your writes to use QUORUM and your reads to just be a
single node right?
If you need/want the read-repair, then I suppose you would need more nodes
up (or deployed in your cluster) but if you are keeping 3 machines a RF of
2 with a write consistency of 2 and a read of 1
http://wiki.apache.org/cassandra/FAQ#unsubscribe
On Fri, Jul 27, 2012 at 9:46 AM, Samir Rayani samir.ray...@gmail.comwrote:
--
Tyler Hobbs
DataStax http://datastax.com/
You have RF=2, CL= Quorum but 3 nodes. So each row is represented on 2 of the 3
nodes.If you take a node down, one of two things can happen when you attempt to
read a row.The row lives on the two nodes that are still up. In this case you
will successfully read the data.The row lives on one node
On Thu, Jul 26, 2012 at 11:25 PM, Adeel Akbar adeel.ak...@panasiangroup.com
wrote:
I used Cassandra 0.8.1 and pycasa 0.2. If I upgrade pycasa, then it have
compatibility issue. please suggest
You can use the latest version of pycassa with Cassandra 0.8.
--
Tyler Hobbs
DataStax
Dave,
What I was suggesting for Yan was to:
WRITE: RF=2, CL=QUORUM
READ: CL=ONE
But you have a good pt... if he hits one of the replicas that didn't have
the data, that would be bad.
Thanks for clearing that up.
On Fri, Jul 27, 2012 at 11:43 AM, Dave Brosius dbros...@mebigfatguy.comwrote:
Oh you're right, sorry about that. The concept of keeping older packages
was recently implemented and while using --version community, you would
need --release 1.0 in order to get 1.0.10.
If you are using --version enterprise, you can use --release 2.0 to get
DataStax Enterprise 2.0 which comes
17 matches
Mail list logo