After our otherwise successful upgrade procedure to enable vnodes, when adding
back new hosts to our cluster, one non-seed host ran into a hardware issue
during bootstrap. By the time the hardware issue was fixed a week later, all
other nodes were added successfully, cleaned, repaired. The
After a few tests, it does not depend on the query. Whatever cql3 query I do, I
always get the same exception. If someone sees something ...
--
Cyril SCETBON
On 13 Feb 2014, at 17:22, Cyril Scetbon cyril.scet...@free.fr wrote:
Hi,
I get a weird issue with cassandra 1.2.13. As written in
Check for consisteny level and socket timeout setting on client side.
-Vivek
On Fri, Feb 14, 2014 at 2:36 PM, Cyril Scetbon cyril.scet...@free.frwrote:
After a few tests, it does not depend on the query. Whatever cql3 query I
do, I always get the same exception. If someone sees something ...
Hi,
Good advice. I found earlier in the morning that it's related to consistency
LOCAL_ONE. I'll check later if it should raise an error in some cases.
Thanks
--
Cyril SCETBON
On 14 Feb 2014, at 10:12, Vivek Mishra mishra.v...@gmail.com wrote:
Check for consisteny level and socket timeout
Hi Paulo,
Did you find out how to fix this issue ? I am experimenting the exact same
issue after trying to help you on this exact subject a few days ago :).
Config : 32 C*1.2.11 nodes, Vnodes enabled, RF=3, 1 DC, On AWS EC2
m1.xlarge.
We added a few nodes (4) and it seems that this occurs on
Hello,
I am seeing below exception in my cassandra
logs(/var/log/cassandra/system.log).
INFO [ScheduledTasks:1] 2014-02-13 13:13:57,641 GCInspector.java (line 119)
GC for ParNew: 273 ms for 1 collections, 2319121816 used; max is 445
6448000
INFO [ScheduledTasks:1] 2014-02-13 13:14:02,695
Hi,
I am using Cassandra 2.0.2 version. On a wide row (approx. 1 columns),
I expire few column by setting TTL as 1 second. At times these columns show
up during slice query.
When I have this issue, running count and get commands for that row using
Cassandra cli it gives different column
I am just learning, I don't know answer to your question, but What is the
use case for TTL as 1 second?
On Fri, Feb 14, 2014 at 6:45 AM, mahesh rajamani
rajamani.mah...@gmail.comwrote:
Hi,
I am using Cassandra 2.0.2 version. On a wide row (approx. 1 columns),
I expire few column by
Hello Alain,
I solved this with a brute force solution, but didn't understand exactly
what happened behind the scenes. What I did was:
a) removed the failed node from the ring with the unsafeAssassinate JMX
option.
b) this caused requests to that node to be routed to the following node
which
You should upgrade. Cassandra 2.0.2 is not the latest version. If you still
have the problem report a bug.
On Fri, Feb 14, 2014 at 12:50 PM, Yogi Nerella ynerella...@gmail.comwrote:
I am just learning, I don't know answer to your question, but What is the
use case for TTL as 1 second?
On
Sorry, I have not had a chance to file a JIRA ticket. We have not been
able to resolve the issue. But since Joel mentioned that upgrading to
Cassandra 2.0.X solved it for them, we may need to upgrade. We are
currently on Java 1.7 and Cassandra 1.2.8
On Thu, Feb 13, 2014 at 12:40 PM, Keith
Hi Mahesh,
is it possible you are creating columns with a long TTL, then update these
columns with a smaller TTL?
kind regards,
Christian
On Fri, Feb 14, 2014 at 3:45 PM, mahesh rajamani
rajamani.mah...@gmail.comwrote:
Hi,
I am using Cassandra 2.0.2 version. On a wide row (approx. 1
It is my understanding that rows with TTLs don't mix well with rows that don't
have TTLs. ie they should all have TTL or all not have TTL.
That said if you can create a small java class (test case) that demonstrates
the problem, I'm happy to try it out on 2.0.5. This code can be attached to a
On Fri, Feb 14, 2014 at 10:08 AM, Paulo Ricardo Motta Gomes
paulo.mo...@chaordicsystems.com wrote:
But in our case, our cluster was not using VNodes, so this workaround will
probably not work with VNodes, since you cannot specify the 256 tokens from
the old node.
Sure you can, in a comma
Hi,
Using now oracle 7. commented out the line StringTableSize=103
same issue. but nothing in the log file now.
but I start from, the command line the works.
Thanks
On Fri, Feb 14, 2014 at 9:48 AM, Michael Shuler mich...@pbandjelly.orgwrote:
On 02/13/2014 07:03 PM, David
On 02/14/2014 06:58 PM, David Montgomery wrote:
Hi,
Using now oracle 7. commented out the line StringTableSize=103
same issue. but nothing in the log file now.
but I start from, the command line the works.
What user are you running c* with, when running from the command line?
What
On 02/14/2014 07:34 PM, Michael Shuler wrote:
On 02/14/2014 06:58 PM, David Montgomery wrote:
Hi,
Using now oracle 7. commented out the line StringTableSize=103
same issue. but nothing in the log file now.
but I start from, the command line the works.
What user are you running c*
On 02/14/2014 08:10 PM, Michael Shuler wrote:
Attached a console log and the conf I used. Here's what I did:
- installed c* 2.0.5 with /var/{lib,log}/cassandra owned by my user, as
usual
- verified c* runs fine from the command line
- killed c*
- installed supervisor package and added the
On 02/14/2014 08:10 PM, Michael Shuler wrote:
mshuler@debian:~$ sudo supervisorctl status
cassandra_server:cassandra FATAL Exited too quickly (process log may
have details)
I imagine the problems all stem from the fact that the initializing
script, in my case,
On 02/14/2014 08:27 PM, Michael Shuler wrote:
On 02/14/2014 08:10 PM, Michael Shuler wrote:
mshuler@debian:~$ sudo supervisorctl status
cassandra_server:cassandra FATAL Exited too quickly
(process log may have details)
I imagine the problems all stem from the fact that the
On 02/14/2014 08:32 PM, Michael Shuler wrote:
On 02/14/2014 08:27 PM, Michael Shuler wrote:
On 02/14/2014 08:10 PM, Michael Shuler wrote:
mshuler@debian:~$ sudo supervisorctl status
cassandra_server:cassandra FATAL Exited too quickly
(process log may have details)
I imagine the
So.. see the rest of my replies for a working configuration, but I
wanted to reply to your initial post.
What problem are you trying to solve, and why do you think using
supervisord to restart a failed c* node will help?
You really don't want a node to be bouncing up and down.. A dead or
I had to give up on supervisor. I installed the deb package rather than
from source. that worked though.
thanks
On Sat, Feb 15, 2014 at 10:10 AM, Michael Shuler mich...@pbandjelly.orgwrote:
On 02/14/2014 07:34 PM, Michael Shuler wrote:
On 02/14/2014 06:58 PM, David Montgomery wrote:
Hi,
23 matches
Mail list logo
