OpsCenter detecting decommissioning node

While decommissioning nodes...Why doesn't OpsCenter show it as an activity or something in the status of the node? That would be helpful to monitor the progress, as when upgrading sstables or compacting for example. Regards Carlos Alonso | Software Engineer | @calonso

Secondary indices on boolean type columns

I have two questions, 1. Does creating secondary index on low cardinality columns like of boolean type helps in read performance any ways? Because there will be only two values( true and false ) for that column in index table. 2. Should secondary indexes be created on clustering columns even if

Stale node decommission?

Hi guys, I’m decommissioning a node and the nodetool netstats bytes count doesn’t move, have you seen it before? Mode: LEAVING Unbootstrap 6eeec0c0-6d9a-11e5-addd-8bc1b1cfbf0a /XXX.XXX.XXX.XXX Sending 0 files, 2773603294 bytes total. Already sent 0 files, 0 bytes total

Re: Why can't nodetool status include a hostname?

Have you tried using the -r or --resolve-ip option? 2015-10-07 19:59 GMT-07:00 Kevin Burton : > I find it really frustrating that nodetool status doesn't include a > hostname > > Makes it harder to track down problems. > > I realize it PRIMARILY uses the IP but perhaps

Re: Secondary indices on boolean type columns

Secondary indexes are not a recommended best practice. Better choices: 1. The new 3.0 materialized views. 2. Manual query tables 3. DSE Search/Solr 4a. Stratio Lucene indexing 4b. TupleJump Stargate Lucene indexing In any case, low cardinality is not recommended for indexes. The goal is that a

Cassandra 1.x upgrade to Cassandra 2.x

Hi, When planning an upgrade on a 20 node multi DC cluster from Cassandra 1.x to Cassandra 2.x version, does the order of running upgradesstables matter? What is the difference between: (a) upgrade Cassandra and run upgradesstables one node at a time; -versus- (b) upgrade every Cassandra node,

Node won't go away

We had some problems with a node, so we decided to rebootstrap it. My IT guy screwed up, and when he added -Dcassandra.replace_address to cassandra-env.sh, he forgot the closing quote. The node bootstrapped, and then refused to join the cluster. We shut it down, and then noticed that nodetool

Re: Secondary indices on boolean type columns

On Thu, Oct 8, 2015 at 2:37 AM, anuja jain wrote: > 1. Does creating secondary index on low cardinality columns like of > boolean type helps in read performance any ways? > No. > 2. Should secondary indexes be created on clustering columns even if these > columns are not

RE: Cassandra 1.x upgrade to Cassandra 2.x

Is there any reason to wait for all the Cassandra nodes to be upgrades from 1.x to 2.x before running the first upgradesstables? From: Robert Coli [mailto:rc...@eventbrite.com] Sent: Thursday, October 08, 2015 11:30 AM To: user@cassandra.apache.org Subject: Re: Cassandra 1.x upgrade to

Re: Does failing to run "nodetool cleanup" end up causing more data to be transferred during bootstrapping?

On Wed, Oct 7, 2015 at 9:06 PM, Kevin Burton wrote: > Let's say I have 10 nodes, I add 5 more, if I fail to run nodetool > cleanup, is excessive data transferred when I add the 6th node? IE do the > existing nodes send more data to the 6th node? > No. Streaming only streams

Re: Why can't nodetool status include a hostname?

Yeah, -r or --resolve-ip is what you're looking for. Cassandra's nodetool command is kind of wonky. Inconsistent across functions (e.g. sometimes 'keyspace.columnfamily' other times 'keyspace columnfamily', pay attention to the character between the items), doesn't resolve IPs by default (while

Re: Cassandra 1.x upgrade to Cassandra 2.x

On Thu, Oct 8, 2015 at 7:44 AM, Caraballo, Rafael < rafael.caraba...@twcable.com> wrote: > When planning an upgrade on a 20 node multi DC cluster from Cassandra 1.x > to Cassandra 2.x version, does the order of running upgradesstables matter? > > > > What is the difference between: > > (a)

Re: Stale node decommission?

On Thu, Oct 8, 2015 at 5:20 AM, Carlos Alonso wrote: > Hi guys, I’m decommissioning a node and the nodetool netstats bytes count > doesn’t move, have you seen it before? > Your decom stream is hung, if you don't have a version with the new non-infinite timeout for streams,

[cassandra 2.1.3] Missing host ID

Hi Guys, I have a custer with 12 nodes. when I restart one of them I receive the error "Missing host ID": WARN [SharedPool-Worker-1] 2015-10-08 13:15:33,882 AbstractTracingAwareExecutorService.java:169 - Uncaught exception on thread Thread[SharedPool-Worker-1,5,main]: {}

Re: Node won't go away

On 10/08/2015 10:27 AM, Robert Wille wrote: nodetool status doesn’t list it, but its still in system.peers, and OpsCenter still shows it. When I run nodetool removenode, it says that it can’t find the node. How do I completely get rid of it?

Re: Stale node decommission?

I ended up killing the node (nodetool removenode) because the streaming was not working (probably because of the different sstables versions) These guys were appearing in logs: ERROR [STREAM-IN-/XXX.XXX.XXX.XXX] 2015-10-08 12:52:43,202 StreamSession.java:505 - [Stream

Output from FailureDetector MBean changed in 2.1.10

Hello, We use the output from the AllEndpointStates attribute of the org.apache.cassandra.net:type=FailureDetector MBean via MX4J for basic monitoring/sanity checking. I've found that the output changed between 2.1.9 and 2.1.10; there is now additional info for some of the keys (DC,

Re: [cassandra 2.1.3] Missing host ID

Hello Paulo, this issue started today and always happened in the same node. Run the following command seems to solve the problem : $ nodetool truncatehints Now the node is up. Regards Eduardo 2015-10-08 15:41 GMT-03:00 Paulo Motta : > Hello Eduardo, > > Your

Re: Duplicate records returned

If anyone is following this, I also logged the bug at https://datastax-oss.atlassian.net/browse/JAVA-943. I suspect that its a driver bug, so I anticipate CASSANDRA-10442 being closed, and hopefully the folks at datastax can get this fixed. This bug must affect a whole lot of people. On Oct 3,

Re: Cassandra query degradation with high frequency updated tables.

Upgrade to 2.2.2. Your sstables are probably not compacting due to CASSANDRA-10270 , which was fixed in 2.2.2. Additionally, you may want to look into using leveled compaction (

Realtime data and (C)AP

How the two things can fit together? Cassandra endorses the AP side of the CAP theorem. So how Cassandra can deliver realtime consistent data? AFAIK, choosing a consistency level equals to ALL can be a huge performance hit for C*, so, please, explain me why I should choose C* for realtime data

Cassandra query degradation with high frequency updated tables.

Hi, so we are developing a system that computes profile of things that it observes. The observation comes in form of events. Each thing that it observe has an id and each thing has a set of subthings in it which has measurement of some kind. Roughly there are about 500 subthings within each

CQL error when adding multiple conditional update statements in the same batch

Hi, I am trying to understand this error message that CQL is throwing when I try to update 2 different rows with different values on same conditional columns. Doesn't CQL support that? I am wondering why CQL has this restriction (since condition applies to each row independently, why does CQL

Re: CQL error when adding multiple conditional update statements in the same batch

could you also provide the columnfamily schema. On Thu, Oct 8, 2015 at 4:13 PM, Peddi, Praveen wrote: > Hi, > > I am trying to understand this error message that CQL is throwing when I > try to update 2 different rows with different values on same conditional > columns.

Re: Realtime data and (C)AP

Your options are 1. Read & write at quorum 2. Recognize that, in general, if you've got a real need for Cassandra, your data is out of date almost immediately after you've read it no matter what guarantee your DB gives you, so you might as well just forget about ever getting the "right" answer

Re: Realtime data and (C)AP

Renato, please watch this netflix video on consistency: http://www.planetcassandra.org/blog/a-netflix-experiment-eventual-consistency-hopeful-consistency-by-christos-kalantzis/ All the best, [image: datastax_logo.png] Sebastián Estévez Solutions Architect | 954 905

Re: CQL error when adding multiple conditional update statements in the same batch

I assume you're running Cassandra 2.0? In 2.1.1 the check for "incompatible" conditions was removed (see this comment for details). I

Re: Re : Nodetool Cleanup on multiple nodes in parallel

Unless you're close to running out of disk space, what's the harm in it taking a while? How big is your DC? At 45 min per node, you can do 32 nodes a day. Diverting traffic away from a DC just to run cleanup feels like overkill to me. On Thu, Oct 8, 2015 at 2:39 PM sai krishnam raju potturi

Re: Re : Nodetool Cleanup on multiple nodes in parallel

We plan to do it during non-peak hours when customer traffic is less. That sums up to 10 nodes a day, which is concerning as we have other data centers to be expanded eventually. Since cleanup is similar to compaction, which is CPU intensive and will effect reads if this data center were to

Re: CQL error when adding multiple conditional update statements in the same batch

Sorry Cassandra 2.0.9 (I was using 2.0.8 but there was another bug in 2.0.8 so upgraded to 2.0.9) On Oct 8, 2015, at 4:43 PM, Peddi, Praveen > wrote: Cassandra 2.0.8. From: Tyler Hobbs > Reply-To:

Re: Re : Nodetool Cleanup on multiple nodes in parallel

My hunch is the bigger your cluster the less impact it will have, as each node takes part in smaller and smaller % of total queries. Considering that compaction is always happening, I'd wager if you've got a big cluster (as you say you do) you'll probably be ok running several cleanups at a time.

Re: CQL error when adding multiple conditional update statements in the same batch

Cassandra 2.0.8. From: Tyler Hobbs > Reply-To: "user@cassandra.apache.org" > Date: Thursday, October 8, 2015 at 4:41 PM To:

Re : Nodetool Cleanup on multiple nodes in parallel

hi; our cassandra cluster currently uses DSE 4.6. The underlying cassandra version is 2.0.14. We are planning on adding multiple nodes to one of our datacenters. This requires "nodetool cleanup". The "nodetool cleanup" operation takes around 45 mins for each node. Datastax documentation

Re: Realtime data and (C)AP

I'm asking because the DataStax DS-201 course states that C* is an ideal fit for messaging applications. What I'm not understanding? :-) Messaging applications generally must be totally consistent, expecially real-time ones. Il 09/10/2015 01:34, Jonathan Haddad ha scritto: Your options are

Re: Realtime data and (C)AP

Hi Renato, Your original statement is not entirely correct, and the video Sebastian is suggesting can probably help make it clearer. It's not that Cassandra favors the AP side of CAP. It more that Cassandra allows you to tune what level of consistency you require. Cassandra does force you to

Re: Is replication possible with already existing data?

On Thu, Oct 8, 2015 at 9:47 AM, Ajay Garg wrote: > Thanks Eric for the reply. > > > On Thu, Oct 8, 2015 at 1:44 AM, Eric Stevens wrote: >> If you're at 1 node (N=1) and RF=1 now, and you want to go N=3 RF=3, you >> ought to be able to increase RF to 3

Re: Realtime data and (C)AP

Most of the things that people thing are "totally consistent" or instant are in reality, not. Examples include banks (inconsistent by days), the time it takes for light to travel around the earth (~150ms), and messaging (email can take quite minutes). Try to imagine being perfectly consistent

Re: Node won't go away

the below solution should work. For each node in the cluster : a : Stop cassandra service on the node. b : manually delete data under $data_directory/system/peers/ directory. c : In cassandra-env.sh file, add the line JVM_OPTS="$JVM_OPTS -Dcassandra.load_ring_state=false". d : Restart

Re: [cassandra 2.1.3] Missing host ID

Hello Eduardo, Your node is trying to write a hint to another node (after a timed out write), but because of some race condition it does not have its token table updated soon after startup, so it cannot locate the node with that ID. You should not be worried, as the only consequence is that one

Re: Cassandra 1.x upgrade to Cassandra 2.x

On Thu, Oct 8, 2015 at 9:40 AM, Caraballo, Rafael < rafael.caraba...@twcable.com> wrote: > Is there any reason to wait for all the Cassandra nodes to be upgrades > from 1.x to 2.x before running the first upgradesstables? > Not really, because the new version nodes will start to flush new