Hello,
After a 'DROP TABLE' command that returns errors={}, last_host=127.0.0.1
(like most DROP commands do) from CQLSH with C* 2.1.0-rc2, I stopped C*.
And I can not start one node. It says :
ERROR 09:18:34 Exception encountered during startup
java.lang.NullPointerException: null
at
It would be nice if you can try with 2.1.0-rc5 (there has been quite a bit
of bug fixes since rc2). If you can still reproduce that NPE there, please
do open a jira ticket with the reproduction steps.
On Thu, Aug 7, 2014 at 11:29 AM, Fabrice Larcher fabrice.larc...@level5.fr
wrote:
Hello,
tl;dr: Decommissioning datacenters by running nodetool decommission on a
node deletes the data on the decommissioned node - is this expected ?
I am trying our some tests on my multi-datacenter setup. Somewhere in the
docs I read that decommissioning a node will stream its data to other nodes
but
Hello all
Usually, when using DELETE in CQL3 on some fields, C* creates tombstone
columns for those fields.
Now if I delete a whole PARTITION (delete from MyTable where
partitionKey=...), what will C* do ? Will it create as many tombstones as
there are physical columns on this partition or
On Thu, Aug 7, 2014 at 8:26 AM, srmore comom...@gmail.com wrote:
tl;dr: Decommissioning datacenters by running nodetool decommission on a
node deletes the data on the decommissioned node - is this expected ?
What does deletes mean? What does lost all my keyspaces (and data) mean?
=Rob
On Tue, Aug 5, 2014 at 6:01 PM, Elias Ross gen...@noderunner.net wrote:
Has this been fixed? Is this a new bug? This is Cassandra 1.2.9.
Dunno, though as you say there are Decommission improvements upstream in
2.x.
If I were you, and could repro this, I would :
1) file a JIRA with repro
Hello Rob
Sorry for being ambiguous. By deletes I mean that running decommission I
can no longer see any keyspaces owned by this node or replicated by other
nodes using the cfstats command. I am also seeing the same behavior when I
remove a single node from a cluster (without datacenters).
On
On Thu, Aug 7, 2014 at 10:04 AM, srmore comom...@gmail.com wrote:
Sorry for being ambiguous. By deletes I mean that running decommission
I can no longer see any keyspaces owned by this node or replicated by other
nodes using the cfstats command. I am also seeing the same behavior when I
Did the jmx path work?
On Thu, Jul 31, 2014 at 11:16 AM, thorsten.s...@t-systems.com wrote:
Well, we ran StorageService.bulkLoad via JMX.
According to http://www.datastax.com/dev/blog/bulk-loading this should
have the same effect and can be done on the same machine:
Because the
On Thu, Aug 7, 2014 at 12:27 PM, Robert Coli rc...@eventbrite.com wrote:
On Thu, Aug 7, 2014 at 10:04 AM, srmore comom...@gmail.com wrote:
Sorry for being ambiguous. By deletes I mean that running decommission
I can no longer see any keyspaces owned by this node or replicated by other
nodes
My reading is it didn't forget the schema. It lost the data.
My reading is decomissioning worked fine. Possibly when you changed the
replication on a keyspace to include a second data center, the data didn't
get replicated.
When you ADD a datacenter, you need to do a nodetool rebuild to get
Thanks for the detailed reply Ken, this really helps. I also realized that
I wasn't doing a 'nodetool rebuild' after reading your email. I was
following the steps mentioned here
http://www.datastax.com/documentation/cassandra/1.2/cassandra/operations/ops_decomission_dc_t.html
I do a test with
I tried using 'nodetool rebuild' after I add the datacenters,date same
outcome, and after I decommission my keyspaces are getting wiped out, I
don't understand this.
On Thu, Aug 7, 2014 at 1:54 PM, srmore comom...@gmail.com wrote:
Thanks for the detailed reply Ken, this really helps. I also
On Thu, Aug 7, 2014 at 12:29 PM, srmore comom...@gmail.com wrote:
I tried using 'nodetool rebuild' after I add the datacenters,date same
outcome, and after I decommission my keyspaces are getting wiped out, I
don't understand this.
File a JIRA with steps to reproduce the issue, and someone
I plan to have a multi data center Cassandra 2 setup with 2-4 nodes per
data center and several 10s of data centers. We have keyspaces replicated
on a certain number of nodes on *each* data center. Essentially, each data
center has a logical ring that covers all token ranges. We have a vnode
based
On Thu, Aug 7, 2014 at 2:46 PM, Viswanathan Ramachandran
vish.ramachand...@gmail.com wrote:
I plan to have a multi data center Cassandra 2 setup with 2-4 nodes per
data center and several 10s of data centers. We have My understanding is
that nodetool cleanup removes data which no longer
16 matches
Mail list logo
