I enabled the debug level for logging. following is the debug entry for the
same exception from node2. Someone please help me
DEBUG 14:53:58,372 Connection version 6 from /10.96.10.105
DEBUG 14:53:58,374 Upgrading incoming connection to be compressed
DEBUG 14:53:58,378 Max version for /10.96.10.10
You would, however, want to clear the snapshot folder afterword, right? I
thought that truncate, like drop table, created a snapshot (unless that
feature had been disabled in your yaml.
On Thu, Aug 29, 2013 at 6:51 PM, Robert Coli wrote:
> On Thu, Aug 29, 2013 at 3:48 PM, S C wrote:
>
>> Do w
On Thu, Aug 29, 2013 at 4:25 PM, Anthony Grasso wrote:
> Puppet was the first thing that came to mind for us as well. In addition,
> we had the same thought about auto-restarting nodes when the configuration
> is changed. If a configuration on all the nodes is changed, we would want
> to restart o
An alternative to cssh is fabric. It's very flexible in that you can
automate almost any repetitive task that you'd send to machines in a
cluster, and it's written in python, meaning if you're in AWS you can mix
it with boto to automate pretty much anything you want.
On Thu, Aug 29, 2013 at 4:25
Thanks Nate! We will look into this one to see if we can use it.
Regards,
Anthony
On Tue, Aug 27, 2013 at 12:22 AM, Nate McCall wrote:
>
>> For example, if I want to make some changes to the configuration file
>> that resides on each node, is there a tool that will propagate the change
>> to ea
Hi Particia,
Thank you for the feedback. It has been helpful.
On Tue, Aug 27, 2013 at 12:02 AM, Patricia Gorla
wrote:
> Anthony,
>
> We use a number of tools to manage our Cassandra cluster.
>
> * Datastax OpsCenter [0] for at a glance information, and trending
> statistics. You can also run op
On Thu, Aug 29, 2013 at 3:48 PM, S C wrote:
> Do we have to run "nodetool repair" or "nodetool cleanup" after Truncating
> a Column Family?
>
No. Why would you?
=Rob
No.
Andrey
On Thu, Aug 29, 2013 at 3:48 PM, S C wrote:
> Do we have to run "nodetool repair" or "nodetool cleanup" after Truncating
> a Column Family?
>
> Thanks,
> SC
>
Do we have to run "nodetool repair" or "nodetool cleanup" after Truncating a
Column Family?
Thanks,SC
Hi!
I've been wondering... is there anyone in the cassandra-user audience who
has used "shuffle" feature successfully on a non-toy-or-testing cluster? If
so, could you describe the experience you had and any problems you
encountered?
Thanks!
=Rob
Hi all,
We're using a Cassandra table to store search results in a
table/column family that that look like this:
++-+-+-+
|| 0 | 1 | 2 | ...
++-+-+-+
| row_id | text... | text... | text... | ...
The
# the number of full memtables to allow pending flush, that is,
# waiting for a writer thread. At a minimum, this should be set to
# the maximum number of secondary indexes created on a single CF.
memtable_flush_queue_size: 4
There was an interesting thread a while back:
http://mail-archives.apa
On Thu, Aug 29, 2013 at 11:21 AM, Ken Hancock wrote:
> I don't think this is strictly true? There's also the periodic flush
> that can cause a storm of flushes if you have multiple column
> families. I sent out a query to the list last week on this topic but
> didn't get any responses -- I'm ver
Ken,
What queue size are you referring to?
Thanks,SC
> From: ken.hanc...@schange.com
> Date: Thu, 29 Aug 2013 14:21:04 -0400
> Subject: Re: Flush writer all time blocked
> To: user@cassandra.apache.org
>
> On Thu, Aug 29, 2013 at 1:57 PM, Robert Coli wrote:
> > On Thu, Aug 29, 2013 at 10:49 AM,
On Thu, Aug 29, 2013 at 1:57 PM, Robert Coli wrote:
> On Thu, Aug 29, 2013 at 10:49 AM, S C wrote:
>> I see a high count "All time blocked" for Flush Writer on nodetool tpstats.
>>
>> Is it how many blocked ever since the server was online? Can somebody
>> explain me what it is? I really appreci
On Thu, Aug 29, 2013 at 11:04 AM, S C wrote:
> Thanks Rob. Will it contribute to any performance problems?
>
Yes, though perhaps more accurate would be that it is often an effect of
performance problems. In general Cassandra flushes memtables because it
believes it needs to. If it is unable to d
Thanks Rob. Will it contribute to any performance problems?
Thanks,SC
Date: Thu, 29 Aug 2013 10:57:30 -0700
Subject: Re: Flush writer all time blocked
From: rc...@eventbrite.com
To: user@cassandra.apache.org
On Thu, Aug 29, 2013 at 10:49 AM, S C wrote:
I see a high count "All time blocke
On Thu, Aug 29, 2013 at 10:49 AM, S C wrote:
> I see a high count "All time blocked" for Flush Writer on nodetool
> tpstats.
>
> Is it how many blocked ever since the server was online? Can somebody
> explain me what it is? I really appreciate it.
>
Yes.
Flush Writer thread pool is the thread
I see a high count "All time blocked" for Flush Writer on nodetool tpstats.
Is it how many blocked ever since the server was online? Can somebody explain
me what it is? I really appreciate it.
http://pastebin.com/GAiu2q74
Thanks,SC
On Thu, Aug 29, 2013 at 10:24 AM, Ertio Lew wrote:
> Running Cassandra (1.0.0 final) single node with default configurations
> on Windows dev machine. Using Hector.
>
Why are you running such an insanely old version of Cassandra in dev?
=Rob
Running Cassandra (1.0.0 final) single node with default configurations on
Windows dev machine. Using Hector.
On Thu, Aug 29, 2013 at 10:50 PM, Ertio Lew wrote:
> I suddenly started to encounter this weird issue after writing some data
> to Cassandra. Didn't know exactly what was written befo
I suddenly started to encounter this weird issue after writing some data to
Cassandra. Didn't know exactly what was written before this or due to which
this started happening.
ERROR [pool-2-thread-30] 2013-08-29 19:55:24,778
CustomTThreadPoolServer.java (line 205) Error occurred during processin
Hi,
We recently upgraded from version 1.1 to 1.2
It all went well, including setting up vnodes, but shuffle fails.
We have 2 nodes, hosted on Amazon AWS
The steps we took (on each of our nodes) are pretty straight forward:
1. upgrade binaries
2. adjust cassandra.yaml (keep token)
3. nodetool upg
On 29 August 2013 01:55, Ike Walker wrote:
> What is the best practice for how many seed nodes to have in a Cassandra
> cluster? I remember reading a recommendation of 2 seeds per datacenter in
> Datastax documentation for 0.7, but I'm interested to know what other
> people are doing these days,
Facing the same issue with rpc_address set to the same as listen address on
both nodes
Checked with having
in first node - rpc_address: 10.96.10.207
in second node - rpc_address: 10.96.10.223
On Thu, Aug 29, 2013 at 12:40 PM, Andrew Cobley wrote:
> Have you tried setting rpc_address to the sa
Have you tried setting rpc_address to the same as listen_address ?
Andy
On 29 Aug 2013, at 07:47, Dinesh
mailto:dinesh.gad...@gmail.com>> wrote:
My first node is running and second node is not running in this case
I tried telnet from second node to first node. Following is the stdout
# telnet
26 matches
Mail list logo
