This indeed fixed the problem.
Thanks Aaron and Oleg for your help in this.
On Dec 14, 2010, at 11:26 PM, Oleg Anastasyev wrote:
This is probably because rmi code jmx uses to listen detected wrong address.
To fix this add the following to cassandra nodes startup script instances:
This is a crash with Cassandra 0.7.0-beta3 but I am pretty sure I also have got
this on a rc1 server too ( We are dropping and recreating keyspaces when this
happens)
I do have the JNA enabled but it looks like it is still calling an external
program - presumably this would cause it to ask for
I am seeing very strange things when trying to decommission a node in my
cluster (detailed logs attached). Here is a nodetool ring report *after*
decommissioning of node 192.168.4.19 (as seen by any other, properly
functioning node).
192.168.4.15Up Normal 49.9 GB 25.00%
This is a crash with Cassandra 0.7.0-beta3 but I am pretty sure I also have
got this on a rc1 server too ( We are dropping and recreating keyspaces when
this happens)
I do have the JNA enabled but it looks like it is still calling an external
program – presumably this would cause it to
This is rc2 I am assuming?
One thing about remove, the removetoken force command is meant to be run on
the node that originally started a remove and doesn't take a token
parameter. Not relevant to you problem though.
Is this a test cluster and have you tried to reproduce the error? I would be
Just realized the ring output is included in the logs for both of those
nodes. Disregard my earlier request :).
On Wed, Dec 15, 2010 at 8:27 AM, Nick Bailey n...@riptano.com wrote:
This is rc2 I am assuming?
One thing about remove, the removetoken force command is meant to be run on
the
Your logs seem to indicate you have some node flapping problems.
The logs complain about nodes *.18 and *.17 going down and immediately
coming back up, even before the decommission. Is that common throughout
your logs? If thats the case I would attribute seeing *.17 down after the
decommission
*Hello,*
*I'm using cassandra 0.7.0 rc1, a single node configuration, replication
factor 1, random partitioner, 2 GO heap size.*
*I ran my hector client to insert 5.000.000 rows but after a couple of
hours, the following Exception occurs : *
WARN [main] 2010-12-15 16:38:53,335
Hey Peter,
On 14 December 2010 20:19, Peter Schuller peter.schul...@infidyne.com wrote:
So, now that I get that we have two different cases ;)
Yup. My problem is java / environment based, occurring
after several weeks, using 0.6.6 instances. Our thread
hijacking friend / learned
http://www.riptano.com/docs/0.6/troubleshooting/index#java-reports-an-error-saying-there-are-too-many-open-files
On Wed, Dec 15, 2010 at 11:13 AM, Amin Sakka, Novapost
amin.sa...@novapost.fr wrote:
*Hello,*
*I'm using cassandra 0.7.0 rc1, a single node configuration, replication
factor 1,
*Hello,*
*I'm using cassandra 0.7.0 rc1, a single node configuration, replication
factor 1, random partitioner, 2 GO heap size.*
*I ran my hector client to insert 5.000.000 rows but after a couple of
hours, the following Exception occurs : *
WARN [main] 2010-12-15 16:38:53,335
This is rc2 I am assuming?
No, RC1. I had a number of problems when trying to upgrade to RC2; I am in
the process of setting up a separate, clean cluster to see if the errors are
reproducible.
Your logs seem to indicate you have some node flapping problems.
The logs complain about
Helllo,
I want to remove one column from all super columns in one row (for one key)
(via Thrift, Cassandra 0.7) but I got exception (see below).
I just call remove method where ColumnPath structure has column_family
and column members set (super_column not set).
ERROR 17:57:46,924 Error in
On Dec 14, 2010, at 9:20 PM, Jonathan Ellis wrote:
Correct. https://issues.apache.org/jira/browse/CASSANDRA-1830 is open to fix
that. If you'd like to review the patch there, that would be very helpful. :)
That patch looks good to me :-) Should have checked jira first ...
Speaking of
That sounds like an interesting patch (as you point out we have had #982
open for a while), but I don't think we want to do something relatively
invasive on the 0.6 branch. Let's target 0.7 or trunk.
On Wed, Dec 15, 2010 at 11:23 AM, Daniel Doubleday daniel.double...@gmx.net
wrote:
On Dec
Created https://issues.apache.org/jira/browse/CASSANDRA-1866 to turn this
into an InvalidRequestException.
On Wed, Dec 15, 2010 at 11:47 AM, Jonathan Ellis jbel...@gmail.com wrote:
The API does not support this. You can remove a column from a supercolumn,
or a supercolumn from a row; if you
The API does not support this. You can remove a column from a supercolumn,
or a supercolumn from a row; if you wan tto remove a column from each
supercolumn, you'll need to slice out the supercolumns, then create a batch
of remove-subcolumn operations.
On Wed, Dec 15, 2010 at 11:03 AM, Michal
i am seeing several different exceptions across my 8 node cluster.
running 0.7 RC2. the following are all from one node. is this a known
issue?
ERROR [MutationStage:35] 2010-12-15 09:25:06,466
RowMutationVerbHandler.java (line 83) Error in row mutation
On Wed, Dec 15, 2010 at 3:48 PM, B. Todd Burruss bburr...@real.com wrote:
i am seeing several different exceptions across my 8 node cluster. running
0.7 RC2. the following are all from one node. is this a known issue?
https://issues.apache.org/jira/browse/CASSANDRA-1860
-Brandon
i am seeing several different exceptions across my 8 node cluster.
running 0.7 RC2. the following are all from one node. is this a known
issue?
https://issues.apache.org/jira/browse/CASSANDRA-1860
So in short - upgrade to the latest 0.7 branch or wait for rc3 (or
incorporate the patch
since the 0.7beta2 version doesnt support indexes for Super CF or for
columns that you might not now the name yet, im supporting them manually by
adding a row on the same CF where the key is the name of the column plus the
value, and in the columns hold the key to the referenced rows
this works
On Tue, Dec 14, 2010 at 7:14 AM, Alberto Velandia
betovelan...@gmail.com wrote:
Hi has anyone noticed that the documentation for the Cassandra Class is gone
from the website?
http://blog.evanweaver.com/2010/12/06/cassandra-0-8/
http://rdoc.info/gems/cassandra will always have the latest
There's no problem doing deletions with batch_mutate, but you are probably
seeing this:
http://wiki.apache.org/cassandra/FAQ#range_ghosts
- Tyler
On Wed, Dec 15, 2010 at 4:26 PM, Nick Santini nick.sant...@kaseya.comwrote:
since the 0.7beta2 version doesnt support indexes for Super CF or for
thats not exactly what im seeing, is not a row, but columns on a row that i
was deleting
ie:
suppose i have a row where the key is sec_index_1 where i have two columns
with information about other row keys
sec_index_1 { key1:key1, key2:key2 }
then i add a deletion for the column named key2, run
thanks
Nicolas Santini
On Thu, Dec 16, 2010 at 12:08 PM, Jonathan Ellis jbel...@gmail.com wrote:
Known bug. Upgrade.
On Wed, Dec 15, 2010 at 4:19 PM, Nick Santini nick.sant...@kaseya.comwrote:
Hi,
im working with the 0.7beta2 version and using the supported secondary
indexes for
What client are you using? If you're not using a client, what does your
deletion code look like?
- Tyler
On Wed, Dec 15, 2010 at 4:58 PM, Nick Santini nick.sant...@kaseya.comwrote:
thats not exactly what im seeing, is not a row, but columns on a row that i
was deleting
ie:
suppose i have a
Nick,The docs for the DateTime in .net say it's resolution is only 10ms. You should try to find a higher resolution time source to avoidaccidentallysending multiple mutations (including deletions) with the same time stamp. I'm not sure it's the cause of this problem, but it can result in cases
Hi,
I have a test node with apache-cassandra-0.6.8 on ubuntu 10.4. The hardware
environment is an OpenVZ container. JVM settings is
# java -Xmx128m -version
java version 1.6.0_18
OpenJDK Runtime Environment (IcedTea6 1.8.2) (6b18-1.8.2-4ubuntu2)
OpenJDK 64-Bit Server VM (build 16.0-b13, mixed
found the issue, was on the logic of the test
sorry about crying wolf :-p
thanks for reading and all your help guys
Nicolas Santini
On Thu, Dec 16, 2010 at 3:55 PM, Nick Santini nick.sant...@kaseya.comwrote:
btw, inside the test the data row gets deleted, but not the secondary index
After investigating it deeper, I suspect it's native memory leak of JVM.
The large anonymous map on lower address space should be the native heap of
JVM, but not java object heap. Has anybody met it before?
I'll try to upgrade the JVM tonight.
best regards,
hanzhu
On Thu, Dec 16, 2010 at
Hi!
Using v0.6.6, I have a 16 node cluster.
One column family has 16 keys(corresponding to node number) but only 9 get
listed with get_range_slices with a predicate and a key_range with empty start
and end.
When I do a get_slice with one of the keys that I know is there (but not listed
by
Is this https://issues.apache.org/jira/browse/CASSANDRA-1722 related?
From: Rajat Chopra [mailto:rcho...@makara.com]
Sent: Wednesday, December 15, 2010 9:45 PM
To: user@cassandra.apache.org
Subject: get_range_slices does not work properly
Hi!
Using v0.6.6, I have a 16 node cluster.
One
Looks like the patch that introduced that bug was added in 0.6.6 and wasn't
fixed until 0.6.8 so yes I'd say that is your problem with get_range_slices.
Is there a reason you can't update?
For nodetool ring, if every node in your cluster is not showing one of the
nodes in the ring, then that node
The test node is behind a firewall. So I took some time to find a way to get
JMX diagnostic information from it.
What's interesting is, both the HeapMemoryUsage and NonHeapMemoryUsage
reported by JVM is quite reasonable. So, it's a myth why the JVM process
maps such a big anonymous memory
Sorry for spam again. :-)
I think I find the root cause. Here is a bug report[1] on memory leak of
ParNewGC. It is solved by OpenJDK 1.6.0_20(IcedTea6 1.9.2)[2].
So the suggestion is: for who runs cassandra of Ubuntu 10.04, please
upgrade OpenJDK to the latest version.
[1]
35 matches
Mail list logo
