[RELEASE] Apache Cassandra 2.1.8 released

[Jake Luciani]

The Cassandra team is pleased to announce the release of Apache Cassandra
version 2.1.8.

Apache Cassandra is a fully distributed database. It is the right choice
when you need scalability and high availability without compromising
performance.

 http://cassandra.apache.org/

Downloads of source and binary distributions are listed in our download
section:

 http://cassandra.apache.org/download/

This version is a bug fix release[1] on the 2.1 series. As always, please
pay
attention to the release notes[2] and Let us know[3] if you were to
encounter
any problem.

Enjoy!

[1]: http://goo.gl/heI10N (CHANGES.txt)
[2]: http://goo.gl/BIe5dS (NEWS.txt)
[3]: https://issues.apache.org/jira/browse/CASSANDRA

[RELEASE] Apache Cassandra 2.2.0-rc2 released

[Jake Luciani]

The Cassandra team is pleased to announce the release of Apache Cassandra
version 2.2.0-rc2.

Apache Cassandra is a fully distributed database. It is the right choice
when you need scalability and high availability without compromising
performance.

 http://cassandra.apache.org/

Downloads of source and binary distributions are listed in our download
section:

 http://cassandra.apache.org/download/

This version is a release candidate[1] on the 2.2 series. As always, please
pay
attention to the release notes[2] and Let us know[3] if you were to
encounter
any problem.

Enjoy!

[1]: http://goo.gl/pE0pPF (CHANGES.txt)
[2]: http://goo.gl/h5OJie (NEWS.txt)
[3]: https://issues.apache.org/jira/browse/CASSANDRA

Re: Question on 'Average tombstones per slice' when running cfstats

[Venkatesh Kandaswamy]

That is correct, we are doing heavy delete-insert. We have been debating doing 
update instead of delete-insert. But conversations with some engineers indicate 
that behind the scenes an update is a delete-insert and will still create 
tombstones. Is there any way we can avoid tombstones (other than 
re-architecting the application) on heavy update (or delete –insert) workload.

[cid:FB14A4F6-B834-469B-BE39-BD9E89CDE0A9]
Venky Kandaswamy
@WalmartLabs
925-200-7124


From: Jonathan Haddad mailto:j...@jonhaddad.com>>
Reply-To: "user@cassandra.apache.org" 
mailto:user@cassandra.apache.org>>
Date: Monday, July 6, 2015 at 5:38 PM
To: "user@cassandra.apache.org" 
mailto:user@cassandra.apache.org>>
Subject: Re: Question on 'Average tombstones per slice' when running cfstats

Wouldn't it suggest a delete heavy workload, rather than update?

On Mon, Jul 6, 2015 at 5:21 PM Robert Coli 
mailto:rc...@eventbrite.com>> wrote:
On Mon, Jul 6, 2015 at 4:19 PM, Venkatesh Kandaswamy 
mailto:ve...@walmartlabs.com>> wrote:
I cannot find documentation on the last two parameters given by cfstats 
below. It looks like most examples show 0 for these metrics, but our table has 
large numbers. What do these mean?
Average live cells per slice (last five minutes): 2.0
Average tombstones per slice (last five minutes): 60.0

They mean what they say they mean?

For each "slice" (which is a weird legacy thriftism you should be able to parse 
as "request" in this context) there was an average of 2 un-masked ("live") 
cells read and 60 cells which were masked ("tombstones").

This is a pretty bad ratio, and suggests that your design does UPDATE-like 
operations, which are not being merged fast enough by compaction to avoid you 
reading past them.

=Rob

Re: Is there a way to remove a node with Opscenter?

[Sid Tantia]

Found my mistake: I was typing the command on the node I was trying to remove 
from the cluster. After trying the command on another node in the cluster, it 
worked (`nodetool status` shows the node as removed), however OpsCenter still 
does not recognize the node as removed.


Any ways to fix OpsCenter so that it stops trying to connect to the node that 
is already removed?

On Tue, Jul 7, 2015 at 11:38 PM, Jean Tremblay
 wrote:

> When you do a nodetool command and you don’t specify a hostname, it sends the 
> requests via JMX to the localhost node. If that node is down then the command 
> will not succeed.
> In your case you are probably doing the command from a machine which has not 
> cassandra running, in that case you need to specify a node with the switch -h.
> So for your that would be:
> nodetool -h  removenode 
> where  is the address of a server which has cassandra 
> daemon running.
> Cheers
> Jean
> On 08 Jul 2015, at 01:39 , Sid Tantia 
> mailto:sid.tan...@baseboxsoftware.com>> wrote:
> I tried both `nodetool remove node ` and `nodetool decommission` and 
> they both give the error:
> nodetool: Failed to connect to '127.0.0.1:7199' - ConnectException: 
> 'Connection refused’.
> Here is what I have tried to fix this:
> 1) Uncommented JVM_OPTS=”$JVM_OPTS -Djava.rmi.server.hostname=”
> 2) Changed rpc_address to 0.0.0.0
> 3) Restarted cassandra
> 4) Restarted datastax-agent
> (Note that I installed my cluster using opscenter so that may have something 
> to do with it? )
> On Tue, Jul 7, 2015 at 2:08 PM, Surbhi Gupta 
> mailto:surbhi.gupt...@gmail.com>> wrote:
> If node is down use :
> nodetool removenode 
> We have to run the below command when the node is down & if the cluster does 
> not use vnodes, before running the nodetool removenode command, adjust the 
> tokens.
> If the node is up, then the command would be “nodetool decommission” to 
> remove the node.
> Remove the node from the “seed list” within the configuration cassandra.yaml.
> On 7 July 2015 at 12:56, Sid Tantia 
> mailto:sid.tan...@baseboxsoftware.com>> wrote:
> Thanks for the response. I’m trying to remove a node that’s already down for 
> some reason so its not allowing me to decommission it, is there some other 
> way to do this?
> On Tue, Jul 7, 2015 at 12:45 PM, Kiran mk 
> mailto:coolkiran2...@gmail.com>> wrote:
> Yes, if your intension is to decommission a node.  You can do that by 
> clicking on the node and decommission.
> Best Regards,
> Kiran.M.K.
> On Jul 8, 2015 1:00 AM, "Sid Tantia" 
> mailto:sid.tan...@baseboxsoftware.com>> wrote:
> I know you can use `nodetool removenode` from the command line but is there a 
> way to remove a node from a cluster using OpsCenter?

cqlsh LexicalUUIDType display

[Marcin Pietraszek]

Hi!

Is there any way to force cqlsh to display LexicalUUIDType values in
"more readable way"?

Currently it looks like a hex value mixed with some strange chars (^t @ * g=)

http://www.wepaste.com/kbl/

-- 
mp