Re: CQL DELETE does not work

[Vivek Mishra]

Using cassandra version 1.1.x and cql3?

-Vivek

On Fri, Oct 12, 2012 at 11:21 PM, Sridharan Kuppa <
sridharan.ku...@outlook.com> wrote:

> Hi,
>
>   I have created table schema using CQL, and I am able to insert and
> select from that table.  Everything works great but DELETE is not working.
>  When I execute the DELETE statement it throws "Bad Request: Failed parsing
> statement: [COL1, COL2, from TABLE1;] reason NullPointerException: null"  I
> tried without column names and with column names but always throws the same
> exception.
>
> Thanks,
> -Sridharan
>

Re: Super columns and arrays

[Thierry Templier]

Thanks very much, Viktor! Is it something that is supported from CQL3? 
If so, how can I create such column kind using CREATE TABLE?


Thierry

struct SuperColumn {
1: required binary name,
2: required list columns,
}


Best regards / Pagarbiai

Viktor Jevdokimov
Senior Developer

Email: viktor.jevdoki...@adform.com
Phone: +370 5 212 3063
Fax: +370 5 261 0453

J. Jasinskio 16C,
LT-01112 Vilnius,
Lithuania



Disclaimer: The information contained in this message and attachments is intended 
solely for the attention and use of the named addressee and may be confidential. 
If you are not the intended recipient, you are reminded that the information 
remains the property of the sender. You must not use, disclose, distribute, copy, 
print or rely on this e-mail. If you have received this message in error, please 
contact the sender immediately and irrevocably delete this message and any 
copies.> -Original Message-

From: Thierry Templier [mailto:thierry.templ...@restlet.com]
Sent: Friday, October 12, 2012 13:44
To: user@cassandra.apache.org
Subject: Super columns and arrays

Hello,

I wonder if it's possible to specify an array of values as a value of a super
column... If it's not possible, is there another way to do that?
Thanks very much for your help.

Thierry

Re: CQL DELETE does not work

[Sylvain Lebresne]

On Fri, Oct 12, 2012 at 7:51 PM, Sridharan Kuppa
 wrote:
> Hi,
>
>   I have created table schema using CQL, and I am able to insert and select
> from that table.  Everything works great but DELETE is not working.  When I
> execute the DELETE statement it throws "Bad Request: Failed parsing
> statement: [COL1, COL2, from TABLE1;] reason NullPointerException: null"  I
> tried without column names and with column names but always throws the same
> exception.

Please make sure you have tried against Cassandra 1.1.5 to be sure
this haven't been fixed yet. But if that hasn't, to be able to help
you we'll need:
- An example query that triggers that this exception.
- Which version of CQL you are using (2 or 3)

--
Sylvain

Problem getting Column Family type

[Felipe Schmidt]

Hello!

I'm trying to get the column family type and I don't know why it's not
working.
I try to use the following code line:
Schema.instance.getColumnFamilyType("School", "Grades");

This Keyspace and Column Family are inserted in Cassandra and this method
only returns null. If I try to get some information of the Keyspace
'system' it works.
I also tried Schema.instance.getNonSystemTables(); and it returns null.

I'm using the commit log for some analyzes and the way it get's the Column
Family information using the internal CfId is this one:
Schema.instance.getCF(cfId);

That's why I think I need to use this instance of the Schema to retrieve
the desired information.

Someone has some idea?
Thanks in advance.

Regards,
Felipe Mathias Schmidt
*(Computer Science UFRGS, RS, Brazil)*

*"Most people do not listen with the intent to understand; they listen with
the intend to reply" - Stephen Covey*

any reason for distributing Cassandra binaries without mx4j-tools.jar

[Илья Шипицин]

Hello!

is there any reason why Cassandra is shipped without mx4j-tools.jar ?
memory leaking ?
licensing issue ?

Cheers,
Ilya Shipitsin

Re: Why my Cassandra is compacting like mad

[Michael Kjellman]

I had a similar bug with 1.1.5 but I couldn't reproduce it so I didn't file a 
bug. I did a rolling restart of my nodes and things went back to normal.

From: Manu Zhang mailto:owenzhang1...@gmail.com>>
Reply-To: "user@cassandra.apache.org" 
mailto:user@cassandra.apache.org>>
Date: Monday, October 15, 2012 8:02 AM
To: "user@cassandra.apache.org" 
mailto:user@cassandra.apache.org>>
Subject: Why my Cassandra is compacting like mad

My Cassandra is compacting like mad (look at the following messages) after I 
restart it after a timeout query. It won't stop until I kill the process.


INFO 22:57:41,839 Compacting 
[SSTableReader(path='/home/manuzhang/cassandra/data/system/schema_columns/system-schema_columns-ia-1258-Data.db')]
 INFO 22:57:42,077 Compacted to 
[/home/manuzhang/cassandra/data/system/schema_columns/system-schema_columns-ia-1259-Data.db,].
  4,377 to 4,377 (~100% of original) bytes for 3 keys at 0.017539MB/s.  Time: 
238ms.
 INFO 22:57:42,079 Compacting 
[SSTableReader(path='/home/manuzhang/cassandra/data/system/schema_columns/system-schema_columns-ia-1259-Data.db')]
 INFO 22:57:42,309 Compacted to 
[/home/manuzhang/cassandra/data/system/schema_columns/system-schema_columns-ia-1260-Data.db,].
  4,377 to 4,377 (~100% of original) bytes for 3 keys at 0.018149MB/s.  Time: 
230ms.
 INFO 22:57:42,311 Compacting 
[SSTableReader(path='/home/manuzhang/cassandra/data/system/schema_columns/system-schema_columns-ia-1260-Data.db')]
 INFO 22:57:42,574 Compacted to 
[/home/manuzhang/cassandra/data/system/schema_columns/system-schema_columns-ia-1261-Data.db,].
  4,377 to 4,377 (~100% of original) bytes for 3 keys at 0.015872MB/s.  Time: 
263ms.
 INFO 22:57:42,576 Compacting 
[SSTableReader(path='/home/manuzhang/cassandra/data/system/schema_columns/system-schema_columns-ia-1261-Data.db')]
 INFO 22:57:42,814 Compacted to 
[/home/manuzhang/cassandra/data/system/schema_columns/system-schema_columns-ia-1262-Data.db,].
  4,377 to 4,377 (~100% of original) bytes for 3 keys at 0.017539MB/s.  Time: 
238ms.
 INFO 22:57:42,816 Compacting 
[SSTableReader(path='/home/manuzhang/cassandra/data/system/schema_columns/system-schema_columns-ia-1262-Data.db')]
 INFO 22:57:43,070 Compacted to 
[/home/manuzhang/cassandra/data/system/schema_columns/system-schema_columns-ia-1263-Data.db,].
  4,377 to 4,377 (~100% of original) bytes for 3 keys at 0.016434MB/s.  Time: 
254ms.

'Like' us on Facebook for exclusive content and other resources on all 
Barracuda Networks solutions.
Visit http://barracudanetworks.com/facebook

Re: Why my Cassandra is compacting like mad

[Manu Zhang]

oh, forgot to mention that my Cassandra is 1.2beta-2

On Mon, Oct 15, 2012 at 11:11 PM, Michael Kjellman
wrote:

> I had a similar bug with 1.1.5 but I couldn't reproduce it so I didn't
> file a bug. I did a rolling restart of my nodes and things went back to
> normal.
>
> From: Manu Zhang 
> Reply-To: "user@cassandra.apache.org" 
> Date: Monday, October 15, 2012 8:02 AM
> To: "user@cassandra.apache.org" 
> Subject: Why my Cassandra is compacting like mad
>
> My Cassandra is compacting like mad (look at the following messages) after
> I restart it after a timeout query. It won't stop until I kill the process.
>
>
> INFO 22:57:41,839 Compacting
> [SSTableReader(path='/home/manuzhang/cassandra/data/system/schema_columns/system-schema_columns-ia-1258-Data.db')]
>  INFO 22:57:42,077 Compacted to
> [/home/manuzhang/cassandra/data/system/schema_columns/system-schema_columns-ia-1259-Data.db,].
>  4,377 to 4,377 (~100% of original) bytes for 3 keys at 0.017539MB/s.
>  Time: 238ms.
>  INFO 22:57:42,079 Compacting
> [SSTableReader(path='/home/manuzhang/cassandra/data/system/schema_columns/system-schema_columns-ia-1259-Data.db')]
>  INFO 22:57:42,309 Compacted to
> [/home/manuzhang/cassandra/data/system/schema_columns/system-schema_columns-ia-1260-Data.db,].
>  4,377 to 4,377 (~100% of original) bytes for 3 keys at 0.018149MB/s.
>  Time: 230ms.
>  INFO 22:57:42,311 Compacting
> [SSTableReader(path='/home/manuzhang/cassandra/data/system/schema_columns/system-schema_columns-ia-1260-Data.db')]
>  INFO 22:57:42,574 Compacted to
> [/home/manuzhang/cassandra/data/system/schema_columns/system-schema_columns-ia-1261-Data.db,].
>  4,377 to 4,377 (~100% of original) bytes for 3 keys at 0.015872MB/s.
>  Time: 263ms.
>  INFO 22:57:42,576 Compacting
> [SSTableReader(path='/home/manuzhang/cassandra/data/system/schema_columns/system-schema_columns-ia-1261-Data.db')]
>  INFO 22:57:42,814 Compacted to
> [/home/manuzhang/cassandra/data/system/schema_columns/system-schema_columns-ia-1262-Data.db,].
>  4,377 to 4,377 (~100% of original) bytes for 3 keys at 0.017539MB/s.
>  Time: 238ms.
>  INFO 22:57:42,816 Compacting
> [SSTableReader(path='/home/manuzhang/cassandra/data/system/schema_columns/system-schema_columns-ia-1262-Data.db')]
>  INFO 22:57:43,070 Compacted to
> [/home/manuzhang/cassandra/data/system/schema_columns/system-schema_columns-ia-1263-Data.db,].
>  4,377 to 4,377 (~100% of original) bytes for 3 keys at 0.016434MB/s.
>  Time: 254ms.
>
> --
> 'Like' us on Facebook for exclusive content and other resources on all
> Barracuda Networks solutions.
> Visit http://barracudanetworks.com/facebook
>   ­­
>

Re: Why my Cassandra is compacting like mad

[Alain RODRIGUEZ]

Well I guess we will need some information to help you...

At least:

-Hardware ?
-Version of Cassandra ?
-Any specific action before restarting ?
-cassandra.yaml (options about compaction) ?
-...

Alain

2012/10/15 Manu Zhang 

> My Cassandra is compacting like mad (look at the following messages) after
> I restart it after a timeout query. It won't stop until I kill the process.
>
>
> INFO 22:57:41,839 Compacting
> [SSTableReader(path='/home/manuzhang/cassandra/data/system/schema_columns/system-schema_columns-ia-1258-Data.db')]
>  INFO 22:57:42,077 Compacted to
> [/home/manuzhang/cassandra/data/system/schema_columns/system-schema_columns-ia-1259-Data.db,].
>  4,377 to 4,377 (~100% of original) bytes for 3 keys at 0.017539MB/s.
>  Time: 238ms.
>  INFO 22:57:42,079 Compacting
> [SSTableReader(path='/home/manuzhang/cassandra/data/system/schema_columns/system-schema_columns-ia-1259-Data.db')]
>  INFO 22:57:42,309 Compacted to
> [/home/manuzhang/cassandra/data/system/schema_columns/system-schema_columns-ia-1260-Data.db,].
>  4,377 to 4,377 (~100% of original) bytes for 3 keys at 0.018149MB/s.
>  Time: 230ms.
>  INFO 22:57:42,311 Compacting
> [SSTableReader(path='/home/manuzhang/cassandra/data/system/schema_columns/system-schema_columns-ia-1260-Data.db')]
>  INFO 22:57:42,574 Compacted to
> [/home/manuzhang/cassandra/data/system/schema_columns/system-schema_columns-ia-1261-Data.db,].
>  4,377 to 4,377 (~100% of original) bytes for 3 keys at 0.015872MB/s.
>  Time: 263ms.
>  INFO 22:57:42,576 Compacting
> [SSTableReader(path='/home/manuzhang/cassandra/data/system/schema_columns/system-schema_columns-ia-1261-Data.db')]
>  INFO 22:57:42,814 Compacted to
> [/home/manuzhang/cassandra/data/system/schema_columns/system-schema_columns-ia-1262-Data.db,].
>  4,377 to 4,377 (~100% of original) bytes for 3 keys at 0.017539MB/s.
>  Time: 238ms.
>  INFO 22:57:42,816 Compacting
> [SSTableReader(path='/home/manuzhang/cassandra/data/system/schema_columns/system-schema_columns-ia-1262-Data.db')]
>  INFO 22:57:43,070 Compacted to
> [/home/manuzhang/cassandra/data/system/schema_columns/system-schema_columns-ia-1263-Data.db,].
>  4,377 to 4,377 (~100% of original) bytes for 3 keys at 0.016434MB/s.
>  Time: 254ms.
>

Re: Why my Cassandra is compacting like mad

[Michael Kjellman]

And to clarify my reply, this was a loop in compactions on 
system-schema_columns specifically.

From: Michael Kjellman mailto:mkjell...@barracuda.com>>
Reply-To: "user@cassandra.apache.org" 
mailto:user@cassandra.apache.org>>
Date: Monday, October 15, 2012 8:11 AM
To: "user@cassandra.apache.org" 
mailto:user@cassandra.apache.org>>
Subject: Re: Why my Cassandra is compacting like mad

I had a similar bug with 1.1.5 but I couldn't reproduce it so I didn't file a 
bug. I did a rolling restart of my nodes and things went back to normal.

From: Manu Zhang mailto:owenzhang1...@gmail.com>>
Reply-To: "user@cassandra.apache.org" 
mailto:user@cassandra.apache.org>>
Date: Monday, October 15, 2012 8:02 AM
To: "user@cassandra.apache.org" 
mailto:user@cassandra.apache.org>>
Subject: Why my Cassandra is compacting like mad

My Cassandra is compacting like mad (look at the following messages) after I 
restart it after a timeout query. It won't stop until I kill the process.


INFO 22:57:41,839 Compacting 
[SSTableReader(path='/home/manuzhang/cassandra/data/system/schema_columns/system-schema_columns-ia-1258-Data.db')]
 INFO 22:57:42,077 Compacted to 
[/home/manuzhang/cassandra/data/system/schema_columns/system-schema_columns-ia-1259-Data.db,].
  4,377 to 4,377 (~100% of original) bytes for 3 keys at 0.017539MB/s.  Time: 
238ms.
 INFO 22:57:42,079 Compacting 
[SSTableReader(path='/home/manuzhang/cassandra/data/system/schema_columns/system-schema_columns-ia-1259-Data.db')]
 INFO 22:57:42,309 Compacted to 
[/home/manuzhang/cassandra/data/system/schema_columns/system-schema_columns-ia-1260-Data.db,].
  4,377 to 4,377 (~100% of original) bytes for 3 keys at 0.018149MB/s.  Time: 
230ms.
 INFO 22:57:42,311 Compacting 
[SSTableReader(path='/home/manuzhang/cassandra/data/system/schema_columns/system-schema_columns-ia-1260-Data.db')]
 INFO 22:57:42,574 Compacted to 
[/home/manuzhang/cassandra/data/system/schema_columns/system-schema_columns-ia-1261-Data.db,].
  4,377 to 4,377 (~100% of original) bytes for 3 keys at 0.015872MB/s.  Time: 
263ms.
 INFO 22:57:42,576 Compacting 
[SSTableReader(path='/home/manuzhang/cassandra/data/system/schema_columns/system-schema_columns-ia-1261-Data.db')]
 INFO 22:57:42,814 Compacted to 
[/home/manuzhang/cassandra/data/system/schema_columns/system-schema_columns-ia-1262-Data.db,].
  4,377 to 4,377 (~100% of original) bytes for 3 keys at 0.017539MB/s.  Time: 
238ms.
 INFO 22:57:42,816 Compacting 
[SSTableReader(path='/home/manuzhang/cassandra/data/system/schema_columns/system-schema_columns-ia-1262-Data.db')]
 INFO 22:57:43,070 Compacted to 
[/home/manuzhang/cassandra/data/system/schema_columns/system-schema_columns-ia-1263-Data.db,].
  4,377 to 4,377 (~100% of original) bytes for 3 keys at 0.016434MB/s.  Time: 
254ms.

--
'Like' us on Facebook for exclusive content and other resources on all 
Barracuda Networks solutions.
Visit http://barracudanetworks.com/facebook
  ­­

'Like' us on Facebook for exclusive content and other resources on all 
Barracuda Networks solutions.
Visit http://barracudanetworks.com/facebook

Re: Why my Cassandra is compacting like mad

[Manu Zhang]

I use default option for compaction:
   in_memory_compaction_limit_in_mb: 64
   multithreaded_compaction: false
   compaction_throughput_mb_per_sec: 16
   compaction_preheat_key_cache: true


I aborted Cassandra after a timeout query;
my Cassandra is 1.2beta-2
I don't what hardware information may help

On Mon, Oct 15, 2012 at 11:19 PM, Michael Kjellman
wrote:

> And to clarify my reply, this was a loop in compactions on
> system-schema_columns specifically.
>
> From: Michael Kjellman 
> Reply-To: "user@cassandra.apache.org" 
> Date: Monday, October 15, 2012 8:11 AM
> To: "user@cassandra.apache.org" 
> Subject: Re: Why my Cassandra is compacting like mad
>
> I had a similar bug with 1.1.5 but I couldn't reproduce it so I didn't
> file a bug. I did a rolling restart of my nodes and things went back to
> normal.
>
> From: Manu Zhang 
> Reply-To: "user@cassandra.apache.org" 
> Date: Monday, October 15, 2012 8:02 AM
> To: "user@cassandra.apache.org" 
> Subject: Why my Cassandra is compacting like mad
>
> My Cassandra is compacting like mad (look at the following messages) after
> I restart it after a timeout query. It won't stop until I kill the process.
>
>
> INFO 22:57:41,839 Compacting
> [SSTableReader(path='/home/manuzhang/cassandra/data/system/schema_columns/system-schema_columns-ia-1258-Data.db')]
>  INFO 22:57:42,077 Compacted to
> [/home/manuzhang/cassandra/data/system/schema_columns/system-schema_columns-ia-1259-Data.db,].
>  4,377 to 4,377 (~100% of original) bytes for 3 keys at 0.017539MB/s.
>  Time: 238ms.
>  INFO 22:57:42,079 Compacting
> [SSTableReader(path='/home/manuzhang/cassandra/data/system/schema_columns/system-schema_columns-ia-1259-Data.db')]
>  INFO 22:57:42,309 Compacted to
> [/home/manuzhang/cassandra/data/system/schema_columns/system-schema_columns-ia-1260-Data.db,].
>  4,377 to 4,377 (~100% of original) bytes for 3 keys at 0.018149MB/s.
>  Time: 230ms.
>  INFO 22:57:42,311 Compacting
> [SSTableReader(path='/home/manuzhang/cassandra/data/system/schema_columns/system-schema_columns-ia-1260-Data.db')]
>  INFO 22:57:42,574 Compacted to
> [/home/manuzhang/cassandra/data/system/schema_columns/system-schema_columns-ia-1261-Data.db,].
>  4,377 to 4,377 (~100% of original) bytes for 3 keys at 0.015872MB/s.
>  Time: 263ms.
>  INFO 22:57:42,576 Compacting
> [SSTableReader(path='/home/manuzhang/cassandra/data/system/schema_columns/system-schema_columns-ia-1261-Data.db')]
>  INFO 22:57:42,814 Compacted to
> [/home/manuzhang/cassandra/data/system/schema_columns/system-schema_columns-ia-1262-Data.db,].
>  4,377 to 4,377 (~100% of original) bytes for 3 keys at 0.017539MB/s.
>  Time: 238ms.
>  INFO 22:57:42,816 Compacting
> [SSTableReader(path='/home/manuzhang/cassandra/data/system/schema_columns/system-schema_columns-ia-1262-Data.db')]
>  INFO 22:57:43,070 Compacted to
> [/home/manuzhang/cassandra/data/system/schema_columns/system-schema_columns-ia-1263-Data.db,].
>  4,377 to 4,377 (~100% of original) bytes for 3 keys at 0.016434MB/s.
>  Time: 254ms.
>
> --
> 'Like' us on Facebook for exclusive content and other resources on all
> Barracuda Networks solutions.
> Visit http://barracudanetworks.com/facebook
>   ­­
>
> --
> 'Like' us on Facebook for exclusive content and other resources on all
> Barracuda Networks solutions.
> Visit http://barracudanetworks.com/facebook
>   ­­
>

RE: CQL DELETE does not work

[Sridharan Kuppa]

Thank you for the reply.
I am using the CQL 2.0 with Cassandra 1.1.5.  The problem can be seen from 
cqlsh too.  The cqlsh commands are below,  If CQL delete is executed with where 
clause then it works.  Hope this helps,  
BTW, my environment is Windows 7, JDK 1.7, Cassandra 1.1.5, cqlsh using cygwin.
--- cqlsh  
---Connected to Test 
Cluster at localhost:9160.[cqlsh 2.2.0 | Cassandra 1.1.5 | CQL spec 2.0.0 | 
Thrift protocol 19.32.0]Use HELP for help.cqlsh>cqlsh> use demo1;cqlsh:demo1> 
create table user (id varchar primary key, fname varchar, lname 
varchar);cqlsh:demo1> insert into user (id, fname, lname) values (1, 'john', 
'doe');cqlsh:demo1> insert into user (id, fname, lname) values (2, 'foo', 
'bar');cqlsh:demo1> delete from user;Bad Request: Failed parsing statement: 
[delete from user;] reason: NullPointerException nullcqlsh:demo1> delete fname, 
lname from user;Bad Request: Failed parsing statement: [delete fname, lname 
from user;] reason: NullPointerException nullcqlsh:demo1> delete from user 
where id = 2;cqlsh:demo1>--- cqlsh  
---
Thanks,-Sridharan
> Date: Mon, 15 Oct 2012 10:39:08 +0200
> Subject: Re: CQL DELETE does not work
> From: sylv...@datastax.com
> To: user@cassandra.apache.org
> 
> On Fri, Oct 12, 2012 at 7:51 PM, Sridharan Kuppa
>  wrote:
> > Hi,
> >
> >   I have created table schema using CQL, and I am able to insert and select
> > from that table.  Everything works great but DELETE is not working.  When I
> > execute the DELETE statement it throws "Bad Request: Failed parsing
> > statement: [COL1, COL2, from TABLE1;] reason NullPointerException: null"  I
> > tried without column names and with column names but always throws the same
> > exception.
> 
> Please make sure you have tried against Cassandra 1.1.5 to be sure
> this haven't been fixed yet. But if that hasn't, to be able to help
> you we'll need:
> - An example query that triggers that this exception.
> - Which version of CQL you are using (2 or 3)
> 
> --
> Sylvain
  

[RELEASE] Apache Cassandra 1.1.6 released

[Sylvain Lebresne]

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

Cassandra is a highly scalable second-generation distributed database,
bringing together Dynamo's fully distributed design and Bigtable's
ColumnFamily-based data model. You can read more here:

 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 maintenance/bug fix release[1] on the 1.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/W3SRr (CHANGES.txt)
[2]: http://goo.gl/Nl6ak (NEWS.txt)
[3]: https://issues.apache.org/jira/browse/CASSANDRA

CQL load balancing

[John Sanda]

Hector provides load balancing so that requests can be distributed across
cluster nodes based on a specified policy, like round robin. Is there
anything similar planned for CQL? I see that there is an open issue (
http://code.google.com/a/apache-extras.org/p/cassandra-jdbc/issues/detail?id=41)
to add support for pooled connections in cassandra-jdbc.Could load
balancing be incorporated into the connection pooling support? I have also
started reading up on the CQL transport protocol and am wondering if it
does or will provide anything for load balancing.

Thanks

- John

Re: [RELEASE] Apache Cassandra 1.1.6 released

[Michael Kjellman]

Sylvain - Getting a 404 still. I assume this is due to a delay in syncing
out to Apache content mirrors?

On 10/15/12 9:46 AM, "Sylvain Lebresne"  wrote:

>The Cassandra team is pleased to announce the release of Apache Cassandra
>version 1.1.6.
>
>Cassandra is a highly scalable second-generation distributed database,
>bringing together Dynamo's fully distributed design and Bigtable's
>ColumnFamily-based data model. You can read more here:
>
> 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 maintenance/bug fix release[1] on the 1.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/W3SRr (CHANGES.txt)
>[2]: http://goo.gl/Nl6ak (NEWS.txt)
>[3]: https://issues.apache.org/jira/browse/CASSANDRA


'Like' us on Facebook for exclusive content and other resources on all 
Barracuda Networks solutions.
Visit http://barracudanetworks.com/facebook

Re: [RELEASE] Apache Cassandra 1.1.6 released

[Sylvain Lebresne]

On Mon, Oct 15, 2012 at 7:24 PM, Michael Kjellman
 wrote:
> Sylvain - Getting a 404 still. I assume this is due to a delay in syncing
> out to Apache content mirrors?

Yes, the apache mirrors can be rather long to sync. I usually send the
release email as soon as it is sync on
http://www.apache.org/dist/cassandra/, but other mirror can easily lag
behind.
I do have messed up in the past, but it seems to be a mirror not in
sync problem since I've been able to get it with some mirrors.

--
Sylvain

>
> On 10/15/12 9:46 AM, "Sylvain Lebresne"  wrote:
>
>>The Cassandra team is pleased to announce the release of Apache Cassandra
>>version 1.1.6.
>>
>>Cassandra is a highly scalable second-generation distributed database,
>>bringing together Dynamo's fully distributed design and Bigtable's
>>ColumnFamily-based data model. You can read more here:
>>
>> 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 maintenance/bug fix release[1] on the 1.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/W3SRr (CHANGES.txt)
>>[2]: http://goo.gl/Nl6ak (NEWS.txt)
>>[3]: https://issues.apache.org/jira/browse/CASSANDRA
>
>
> 'Like' us on Facebook for exclusive content and other resources on all 
> Barracuda Networks solutions.
>
> Visit http://barracudanetworks.com/facebook
>
>
>
>

run repair on each node or every R nodes?

[Alexis Midon]

Hi all,

I have a 9-node cluster with a replication factor R=3. When I run repair
-pr on node-00, I see the exact same load and activity on node-{01,02}.
Specifically, compactionstats shows the same Validation tasks.
Does this mean that all 3 nodes will be repaired when nodetool returns? or
do I still have to trigger a nodetool-repair on node-{01,02}?

Thanks,

Alexis

Re: what happens while node is bootstrapping?

[John Lewis]

Bootstrapping nodes do not handle reads requests until the bootstrap process is 
complete.

JLewis

On Oct 13, 2012, at 11:19 PM, Andrey Ilinykh  wrote:

> Hello, everybody!
> I'd like to clarify a bootstrapping process. As far as I understand,
> bootstrapping node starts to accept writes immediately.  What about
> reads?
> Bootstrapping node doesn't have all information, only replica nodes
> have. Does it mean read operations with CL ALL may fail during
> bootstrapping process?
> 
> Thank you,
>  Andrey

RF update

[Matthias Broecheler]

Hey,

we are writing a lot of data into a cassandra cluster for a batch loading
use case. We cannot use the sstable batch loader, so in order to speed up
the loading process we are using RF=1 while the data is loading. After the
load is complete, we want to increase the RF. For that, we are updating the
RF in the schema and then run the node repair tool on each cassandra
instance to stream the data over. However, we are noticing that this
process is slowed down by a lot of compactions (the actually streaming of
data only takes a couple of minutes).

Cassandra is already running a major compaction after the data loading
process has completed. But then, there are to be two more compactions (one
on the sender and one on the receiver) happening and those take a very long
time even on the aws high i/o instance with no compaction throttling.

Question: These additional compactions seem redundant since there are no
reads or writes on the cluster after the first major compaction
(immediately after the data load), is that right? And if so, what can we do
to avoid them? We are currently waiting multiple days.

Thank you very much for your help,
Matthias

Re: what happens while node is bootstrapping?

[Andrey Ilinykh]

Does it mean that during bootstrapping process only replicas serve
read requests for new node range? In other words, replication factor
is RF-1?

On Mon, Oct 15, 2012 at 12:20 PM, John Lewis  wrote:
> Bootstrapping nodes do not handle reads requests until the bootstrap process 
> is complete.
>
> JLewis
>
> On Oct 13, 2012, at 11:19 PM, Andrey Ilinykh  wrote:
>
>> Hello, everybody!
>> I'd like to clarify a bootstrapping process. As far as I understand,
>> bootstrapping node starts to accept writes immediately.  What about
>> reads?
>> Bootstrapping node doesn't have all information, only replica nodes
>> have. Does it mean read operations with CL ALL may fail during
>> bootstrapping process?
>>
>> Thank you,
>>  Andrey
>

Re: run repair on each node or every R nodes?

[Will Martin]

+1Is this a consensus activity and is the master fixed, or does the voting 
process migrate during the cycles??



On Oct 15, 2012, at 2:56 PM, Alexis Midon wrote:

> 
> Hi all,
> 
> I have a 9-node cluster with a replication factor R=3. When I run repair -pr 
> on node-00, I see the exact same load and activity on node-{01,02}. 
> Specifically, compactionstats shows the same Validation tasks.
> Does this mean that all 3 nodes will be repaired when nodetool returns? or do 
> I still have to trigger a nodetool-repair on node-{01,02}?
> 
> Thanks,
> 
> Alexis

Re: RF update

[Will Martin]

+1   It doesn't make sense that the xfr compactions are heavy unless they are 
translating the file. This could be a protocol mismatch: however the 
requirements for node level compaction and wire compaction I would expect to be 
pretty different.
On Oct 15, 2012, at 4:42 PM, Matthias Broecheler wrote:

> Hey,
> 
> we are writing a lot of data into a cassandra cluster for a batch loading use 
> case. We cannot use the sstable batch loader, so in order to speed up the 
> loading process we are using RF=1 while the data is loading. After the load 
> is complete, we want to increase the RF. For that, we are updating the RF in 
> the schema and then run the node repair tool on each cassandra instance to 
> stream the data over. However, we are noticing that this process is slowed 
> down by a lot of compactions (the actually streaming of data only takes a 
> couple of minutes).
> 
> Cassandra is already running a major compaction after the data loading 
> process has completed. But then, there are to be two more compactions (one on 
> the sender and one on the receiver) happening and those take a very long time 
> even on the aws high i/o instance with no compaction throttling. 
> 
> Question: These additional compactions seem redundant since there are no 
> reads or writes on the cluster after the first major compaction (immediately 
> after the data load), is that right? And if so, what can we do to avoid them? 
> We are currently waiting multiple days.
> 
> Thank you very much for your help,
> Matthias
> 

Re: what happens while node is bootstrapping?

[Will Martin]

The Kafka team has resources for tuning the socket buffer sizes. It seems that 
with a reasonable amount of memory, there should be an activity queue waiting 
after the bootstrap process. Is this checked? Is it feasible to pick it up? Is 
this already done?




On Oct 15, 2012, at 4:50 PM, Andrey Ilinykh wrote:

> Does it mean that during bootstrapping process only replicas serve
> read requests for new node range? In other words, replication factor
> is RF-1?
> 
> On Mon, Oct 15, 2012 at 12:20 PM, John Lewis  wrote:
>> Bootstrapping nodes do not handle reads requests until the bootstrap process 
>> is complete.
>> 
>> JLewis
>> 
>> On Oct 13, 2012, at 11:19 PM, Andrey Ilinykh  wrote:
>> 
>>> Hello, everybody!
>>> I'd like to clarify a bootstrapping process. As far as I understand,
>>> bootstrapping node starts to accept writes immediately.  What about
>>> reads?
>>> Bootstrapping node doesn't have all information, only replica nodes
>>> have. Does it mean read operations with CL ALL may fail during
>>> bootstrapping process?
>>> 
>>> Thank you,
>>> Andrey
>> 

Re: run repair on each node or every R nodes?

[Andrey Ilinykh]

Only one region (node-00 is responsible for) will get repaired on all
three nodes.
Andrey
On Mon, Oct 15, 2012 at 11:56 AM, Alexis Midon  wrote:
>
> Hi all,
>
> I have a 9-node cluster with a replication factor R=3. When I run repair -pr
> on node-00, I see the exact same load and activity on node-{01,02}.
> Specifically, compactionstats shows the same Validation tasks.
> Does this mean that all 3 nodes will be repaired when nodetool returns? or
> do I still have to trigger a nodetool-repair on node-{01,02}?
>
> Thanks,
>
> Alexis

RE: what happens while node is bootstrapping?

[Jaipal Deswal]

According to my experience if bootstrap is running on already Live cluster node 
(and dead from sometime) then it start serving read during bootstrap process 
also but if bootstrap is running on new node (which is joining cluster first 
time) then read requests will not go to this node until bootstrap completes

-Original Message-
From: John Lewis [mailto:lewili...@gmail.com]
Sent: 16 October 2012 00:51
To: user@cassandra.apache.org
Subject: Re: what happens while node is bootstrapping?

Bootstrapping nodes do not handle reads requests until the bootstrap process is 
complete.

JLewis

On Oct 13, 2012, at 11:19 PM, Andrey Ilinykh  wrote:

> Hello, everybody!
> I'd like to clarify a bootstrapping process. As far as I understand,
> bootstrapping node starts to accept writes immediately.  What about
> reads?
> Bootstrapping node doesn't have all information, only replica nodes
> have. Does it mean read operations with CL ALL may fail during
> bootstrapping process?
>
> Thank you,
>  Andrey



CONFIDENTIALITY NOTICE
==
This email message and any attachments are for the exclusive use of the 
intended recipient(s) and may contain confidential and privileged information. 
Any unauthorized review, use, disclosure or distribution is prohibited. If you 
are not the intended recipient, please contact the sender by reply email and 
destroy all copies of the original message along with any attachments, from 
your computer system. If you are the intended recipient, please be advised that 
the content of this message is subject to access, review and disclosure by the 
sender's Email System Administrator.

Re: run repair on each node or every R nodes?

[Alexis Midon]

I see. So if I don't use the '-pr' option, triggering repair on node-00 is
sufficient to repair the first 3 nodes.
No need to cron a repair on node-{01,02}.
correct?

thanks for your answer.

On Mon, Oct 15, 2012 at 6:51 PM, Andrey Ilinykh  wrote:

> Only one region (node-00 is responsible for) will get repaired on all
> three nodes.
> Andrey
> On Mon, Oct 15, 2012 at 11:56 AM, Alexis Midon 
> wrote:
> >
> > Hi all,
> >
> > I have a 9-node cluster with a replication factor R=3. When I run repair
> -pr
> > on node-00, I see the exact same load and activity on node-{01,02}.
> > Specifically, compactionstats shows the same Validation tasks.
> > Does this mean that all 3 nodes will be repaired when nodetool returns?
> or
> > do I still have to trigger a nodetool-repair on node-{01,02}?
> >
> > Thanks,
> >
> > Alexis
>

Re: run repair on each node or every R nodes?

[Alexis Midon]

forget it. this was nonsense.

On Mon, Oct 15, 2012 at 10:05 PM, Alexis Midon wrote:

> I see. So if I don't use the '-pr' option, triggering repair on node-00 is
> sufficient to repair the first 3 nodes.
> No need to cron a repair on node-{01,02}.
> correct?
>
> thanks for your answer.
>
>
> On Mon, Oct 15, 2012 at 6:51 PM, Andrey Ilinykh wrote:
>
>> Only one region (node-00 is responsible for) will get repaired on all
>> three nodes.
>> Andrey
>> On Mon, Oct 15, 2012 at 11:56 AM, Alexis Midon 
>> wrote:
>> >
>> > Hi all,
>> >
>> > I have a 9-node cluster with a replication factor R=3. When I run
>> repair -pr
>> > on node-00, I see the exact same load and activity on node-{01,02}.
>> > Specifically, compactionstats shows the same Validation tasks.
>> > Does this mean that all 3 nodes will be repaired when nodetool returns?
>> or
>> > do I still have to trigger a nodetool-repair on node-{01,02}?
>> >
>> > Thanks,
>> >
>> > Alexis
>>
>
>