[Cassandra Wiki] Trivial Update of Allison42 by Allison42

2013-04-05 Thread Apache Wiki
Dear Wiki user,

You have subscribed to a wiki page or wiki category on Cassandra Wiki for 
change notification.

The Allison42 page has been changed by Allison42:
http://wiki.apache.org/cassandra/Allison42?action=diffrev1=8rev2=9

- There is still a remedy so you can get the bucks you'll need in a hurry. You 
may also use the money to pay for for nearly anything, from a company vehicle 
or cellphone to office equipment, rent on a new workplace, salaries, or 
payments to vendors. Worse, underwriting these private middlemen with 
government guarantees has allowed them to game the machine. There are several 
mortgage loan options offered to house buyers in the current market. This from 
your man whose salary may be the highest salary within the nation for 
legislatures.BR
+ The charge card advance loan comes with a very high fee, as well as the 
monthly interest about it is greater than that for the purchases made, using 
the finance card.BR
  BR
- Here is my blog post :: 
[[http://forums.mabuhaydavao.com/groups/several-weeks-obtain-a-new-striker-with-form-however-eight-goal-daniel-sturridge-is-about-bank-loan-at-bolton/|payday
 loans hawaii]]
+ Along with payment protection insurance, this might be an excellent way of 
providing yourself with a little extra leeway, especially if you're borrowing a 
significant amount over a prolonged period. Again, the chance of the money is 
cut down tremendously when the lender turns into a lien around the property. 
Living disabled was worth the expense of escaping of their predicament. 
Underwriting criteria became so strict that no self employed was eligible to 
get a remortgage or a secured loan without concrete evidence of income.BR
+ BR
+ My web-site; [[http://www.drbobart.net/dbaguest/view.php|personel loans]]
  


[jira] [Commented] (CASSANDRA-4501) Gossip the ip and port used by the binary protocol

2013-04-05 Thread Sylvain Lebresne (JIRA)

[ 
https://issues.apache.org/jira/browse/CASSANDRA-4501?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13623440#comment-13623440
 ] 

Sylvain Lebresne commented on CASSANDRA-4501:
-

Sorry, I realize I've been a bit carried away. I saw cql schema definitions 
and somehow assumed we were talking of one of the schema_* table but we're not. 
 The peers table is a local one, so there is no problem with backward 
compatibility as far as rolling upgrade are concerned, my bad (and so using a 
composite PK would indeed be an option).

There is compatibility issues to consider however, and that's for clients. The 
peers table is the new describe_ring|token_map of CQL3 clients that thus use 
it. For those, just adding a new 'port' column (without renaming existing ones) 
will definitively be easier to handle that adding a new data type.

But I have more important concerns. Multiple nodes on the same IP means also by 
necessity means multiple RPC/native protocol port in the cluster too.

So far, clients assumed that 1) nodes are identified by just their ip address 
and 2) all nodes were using the same port for thrift/native protocol. And I'll 
note that they largely had no choice about making those assumptions because the 
(RPC/native protocol) ports where not really exposed. But this issue breaks 
those 2 assumptions. Meaning that 1) all existing client drivers and tools that 
were identifying node with just the ip addresses will have to be fixed and 2) 
we'd have to start gossiping the rpc port (CASSANDRA-4501) because otherwise 
doing node auto-discovery properly becomes much more harder (and for instance, 
binary protocol notifications *assume* that all node use the same rpc port 
since we don't have CASSANDRA-4501).

I'll also note that none of the describe_* thrift calls include the port 
currently, and there is no easy way to return it without breaking the thrift 
API (of course, shoving the port in the string currently used to return the ip 
address would be breaking and thus non acceptable).

So I have to ask, are we absolutely sure that this addition is worth the pretty 
substantial headache it will be for most clients drivers and tools? I'm no 
network expert but can't one just use multiple IP aliases if he want multiple 
instances on the same NIC.

To be clear, I absolutely agree that it is lame we haven't identified nodes by 
ip and port from day one. But it seems to me too much trouble for little 
benefit to change it now.


 Gossip the ip and port used by the binary protocol
 --

 Key: CASSANDRA-4501
 URL: https://issues.apache.org/jira/browse/CASSANDRA-4501
 Project: Cassandra
  Issue Type: Improvement
Reporter: Sylvain Lebresne
Assignee: Brandon Williams
Priority: Minor
 Fix For: 2.0


 Same as we gossip the rpc_address, we should add gossipping of the native 
 transport address (including the port). CASSANDRA-4480 has one reason why we 
 would want to do that.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


[jira] [Commented] (CASSANDRA-5400) Allow multiple ports to gossip from a single IP address

2013-04-05 Thread Sylvain Lebresne (JIRA)

[ 
https://issues.apache.org/jira/browse/CASSANDRA-5400?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13623441#comment-13623441
 ] 

Sylvain Lebresne commented on CASSANDRA-5400:
-

Sorry, I realize I've been a bit carried away. I saw cql schema definitions 
and somehow assumed we were talking of one of the schema_* table but we're not. 
 The peers table is a local one, so there is no problem with backward 
compatibility as far as rolling upgrade are concerned, my bad (and so using a 
composite PK would indeed be an option).

There is compatibility issues to consider however, and that's for clients. The 
peers table is the new describe_ring|token_map of CQL3 clients that thus use 
it. For those, just adding a new 'port' column (without renaming existing ones) 
will definitively be easier to handle that adding a new data type.

But I have more important concerns. Multiple nodes on the same IP means also by 
necessity means multiple RPC/native protocol port in the cluster too.

So far, clients assumed that 1) nodes are identified by just their ip address 
and 2) all nodes were using the same port for thrift/native protocol. And I'll 
note that they largely had no choice about making those assumptions because the 
(RPC/native protocol) ports where not really exposed. But this issue breaks 
those 2 assumptions. Meaning that 1) all existing client drivers and tools that 
were identifying node with just the ip addresses will have to be fixed and 2) 
we'd have to start gossiping the rpc port (CASSANDRA-4501) because otherwise 
doing node auto-discovery properly becomes much more harder (and for instance, 
binary protocol notifications *assume* that all node use the same rpc port 
since we don't have CASSANDRA-4501).

I'll also note that none of the describe_* thrift calls include the port 
currently, and there is no easy way to return it without breaking the thrift 
API (of course, shoving the port in the string currently used to return the ip 
address would be breaking and thus non acceptable).

So I have to ask, are we absolutely sure that this addition is worth the pretty 
substantial headache it will be for most clients drivers and tools? I'm no 
network expert but can't one just use multiple IP aliases if he want multiple 
instances on the same NIC.

To be clear, I absolutely agree that it is lame we haven't identified nodes by 
ip and port from day one. But it seems to me too much trouble for little 
benefit to change it now.


 Allow multiple ports to gossip from a single IP address
 ---

 Key: CASSANDRA-5400
 URL: https://issues.apache.org/jira/browse/CASSANDRA-5400
 Project: Cassandra
  Issue Type: New Feature
Affects Versions: 2.0
Reporter: Carl Yeksigian
Assignee: Carl Yeksigian
 Fix For: 2.0

 Attachments: 5400.txt, 5400-v2.txt, 5400-v3.patch, 5400-v4.patch


 If a fat client is running on the same machine as a Cassandra node, the fat 
 client must be allocated a new IP address. However, since the node is now a 
 part of the gossip, the other nodes in the ring must be able to talk to it. 
 This means that a local only address (127.0.0.n) won't actually work for the 
 rest of the ring.
 This also would allow for multiple Cassandra service instances to run on a 
 single machine, or from a group of machines behind a NAT.
 The change is simple in concept: instead of using an InetAddress, use a 
 different class. Instead of using an InetSocketAddress, which would still tie 
 us to using InetAddress, I've added a new class, CassandraInstanceEndpoint. 
 The serializer allows for reading a serialized Inet4Address or Inet6Address; 
 also, the message service can still communicate with 
 non-CassandraInstanceEndpoint aware code.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


[jira] [Issue Comment Deleted] (CASSANDRA-4501) Gossip the ip and port used by the binary protocol

2013-04-05 Thread Sylvain Lebresne (JIRA)

 [ 
https://issues.apache.org/jira/browse/CASSANDRA-4501?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Sylvain Lebresne updated CASSANDRA-4501:


Comment: was deleted

(was: Sorry, I realize I've been a bit carried away. I saw cql schema 
definitions and somehow assumed we were talking of one of the schema_* table 
but we're not.  The peers table is a local one, so there is no problem with 
backward compatibility as far as rolling upgrade are concerned, my bad (and so 
using a composite PK would indeed be an option).

There is compatibility issues to consider however, and that's for clients. The 
peers table is the new describe_ring|token_map of CQL3 clients that thus use 
it. For those, just adding a new 'port' column (without renaming existing ones) 
will definitively be easier to handle that adding a new data type.

But I have more important concerns. Multiple nodes on the same IP means also by 
necessity means multiple RPC/native protocol port in the cluster too.

So far, clients assumed that 1) nodes are identified by just their ip address 
and 2) all nodes were using the same port for thrift/native protocol. And I'll 
note that they largely had no choice about making those assumptions because the 
(RPC/native protocol) ports where not really exposed. But this issue breaks 
those 2 assumptions. Meaning that 1) all existing client drivers and tools that 
were identifying node with just the ip addresses will have to be fixed and 2) 
we'd have to start gossiping the rpc port (CASSANDRA-4501) because otherwise 
doing node auto-discovery properly becomes much more harder (and for instance, 
binary protocol notifications *assume* that all node use the same rpc port 
since we don't have CASSANDRA-4501).

I'll also note that none of the describe_* thrift calls include the port 
currently, and there is no easy way to return it without breaking the thrift 
API (of course, shoving the port in the string currently used to return the ip 
address would be breaking and thus non acceptable).

So I have to ask, are we absolutely sure that this addition is worth the pretty 
substantial headache it will be for most clients drivers and tools? I'm no 
network expert but can't one just use multiple IP aliases if he want multiple 
instances on the same NIC.

To be clear, I absolutely agree that it is lame we haven't identified nodes by 
ip and port from day one. But it seems to me too much trouble for little 
benefit to change it now.
)

 Gossip the ip and port used by the binary protocol
 --

 Key: CASSANDRA-4501
 URL: https://issues.apache.org/jira/browse/CASSANDRA-4501
 Project: Cassandra
  Issue Type: Improvement
Reporter: Sylvain Lebresne
Assignee: Brandon Williams
Priority: Minor
 Fix For: 2.0


 Same as we gossip the rpc_address, we should add gossipping of the native 
 transport address (including the port). CASSANDRA-4480 has one reason why we 
 would want to do that.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


[Cassandra Wiki] Trivial Update of WallaceBa by WallaceBa

2013-04-05 Thread Apache Wiki
Dear Wiki user,

You have subscribed to a wiki page or wiki category on Cassandra Wiki for 
change notification.

The WallaceBa page has been changed by WallaceBa:
http://wiki.apache.org/cassandra/WallaceBa

New page:
Theportswear -likeown jacketillecome the new favourite in winter season.BR
Young children moncler jackets have additional option on coloration deciding 
upon.BR
BR
Feel free to surf to my web blog 
[[http://businessservices20.com/wiki/index.php?title=Usuario:MarieMint|モンクレール 
メンズ]]


[Cassandra Wiki] Trivial Update of Pablo32B by Pablo32B

2013-04-05 Thread Apache Wiki
Dear Wiki user,

You have subscribed to a wiki page or wiki category on Cassandra Wiki for 
change notification.

The Pablo32B page has been changed by Pablo32B:
http://wiki.apache.org/cassandra/Pablo32B

New page:
My name: Pablo FreyBR
Age: 20BR
Country: FranceBR
Home town: Lons-Le-Saunier BR
ZIP: 39000BR
Address: 83 Rue Hubert de LisleBR
BR
[[http://www.fi-developpement.com/|creation site internet marchand]]


git commit: fix build and test error, should not use QueryPath

2013-04-05 Thread marcuse
Updated Branches:
  refs/heads/trunk e37ca25cf - 6afbed371


fix build and test error, should not use QueryPath


Project: http://git-wip-us.apache.org/repos/asf/cassandra/repo
Commit: http://git-wip-us.apache.org/repos/asf/cassandra/commit/6afbed37
Tree: http://git-wip-us.apache.org/repos/asf/cassandra/tree/6afbed37
Diff: http://git-wip-us.apache.org/repos/asf/cassandra/diff/6afbed37

Branch: refs/heads/trunk
Commit: 6afbed371c0d12a15a969e4f52ba670998bab282
Parents: e37ca25
Author: Marcus Eriksson marc...@spotify.com
Authored: Fri Apr 5 10:40:50 2013 +0200
Committer: Marcus Eriksson marc...@spotify.com
Committed: Fri Apr 5 10:40:50 2013 +0200

--
 .../apache/cassandra/config/ColumnDefinition.java  |4 +++-
 test/unit/org/apache/cassandra/SchemaLoader.java   |2 +-
 .../db/index/PerRowSecondaryIndexTest.java |8 
 3 files changed, 8 insertions(+), 6 deletions(-)
--


http://git-wip-us.apache.org/repos/asf/cassandra/blob/6afbed37/src/java/org/apache/cassandra/config/ColumnDefinition.java
--
diff --git a/src/java/org/apache/cassandra/config/ColumnDefinition.java 
b/src/java/org/apache/cassandra/config/ColumnDefinition.java
index fed095d..a777d1a 100644
--- a/src/java/org/apache/cassandra/config/ColumnDefinition.java
+++ b/src/java/org/apache/cassandra/config/ColumnDefinition.java
@@ -20,6 +20,7 @@ package org.apache.cassandra.config;
 import java.nio.ByteBuffer;
 import java.util.*;
 
+import com.google.common.annotations.VisibleForTesting;
 import com.google.common.base.Objects;
 import com.google.common.collect.Maps;
 
@@ -97,7 +98,8 @@ public class ColumnDefinition
 this(name, validator, null, null, null, componentIndex, type);
 }
 
-private ColumnDefinition(ByteBuffer name, AbstractType? validator, 
IndexType index_type, MapString, String index_options, String index_name, 
Integer componentIndex, Type type)
+@VisibleForTesting
+public ColumnDefinition(ByteBuffer name, AbstractType? validator, 
IndexType index_type, MapString, String index_options, String index_name, 
Integer componentIndex, Type type)
 {
 assert name != null  validator != null;
 this.name = name;

http://git-wip-us.apache.org/repos/asf/cassandra/blob/6afbed37/test/unit/org/apache/cassandra/SchemaLoader.java
--
diff --git a/test/unit/org/apache/cassandra/SchemaLoader.java 
b/test/unit/org/apache/cassandra/SchemaLoader.java
index 55e5591..0035b1e 100644
--- a/test/unit/org/apache/cassandra/SchemaLoader.java
+++ b/test/unit/org/apache/cassandra/SchemaLoader.java
@@ -310,7 +310,7 @@ public class SchemaLoader
 IndexType.CUSTOM,
 indexOptions,
 ByteBufferUtil.bytesToHex(cName),
-null));
+null, ColumnDefinition.Type.REGULAR));
 }});
 }
 

http://git-wip-us.apache.org/repos/asf/cassandra/blob/6afbed37/test/unit/org/apache/cassandra/db/index/PerRowSecondaryIndexTest.java
--
diff --git 
a/test/unit/org/apache/cassandra/db/index/PerRowSecondaryIndexTest.java 
b/test/unit/org/apache/cassandra/db/index/PerRowSecondaryIndexTest.java
index 3a4f947..4ca84cb 100644
--- a/test/unit/org/apache/cassandra/db/index/PerRowSecondaryIndexTest.java
+++ b/test/unit/org/apache/cassandra/db/index/PerRowSecondaryIndexTest.java
@@ -50,7 +50,7 @@ public class PerRowSecondaryIndexTest extends SchemaLoader
 // create a row then test that the configured index instance was able 
to read the row
 RowMutation rm;
 rm = new RowMutation(PerRowSecondaryIndex, 
ByteBufferUtil.bytes(k1));
-rm.add(new QueryPath(Indexed1, null, 
ByteBufferUtil.bytes(indexed)), ByteBufferUtil.bytes(foo), 1);
+rm.add(Indexed1, ByteBufferUtil.bytes(indexed), 
ByteBufferUtil.bytes(foo), 1);
 rm.apply();
 
 ColumnFamily indexedRow = TestIndex.LAST_INDEXED_ROW;
@@ -59,7 +59,7 @@ public class PerRowSecondaryIndexTest extends SchemaLoader
 
 // update the row and verify what was indexed
 rm = new RowMutation(PerRowSecondaryIndex, 
ByteBufferUtil.bytes(k1));
-rm.add(new QueryPath(Indexed1, null, 
ByteBufferUtil.bytes(indexed)), ByteBufferUtil.bytes(bar), 2);
+rm.add(Indexed1, ByteBufferUtil.bytes(indexed), 
ByteBufferUtil.bytes(bar), 2);
 rm.apply();
 
 indexedRow = TestIndex.LAST_INDEXED_ROW;
@@ -80,7 +80,7 @@ public class PerRowSecondaryIndexTest extends SchemaLoader
 public void index(ByteBuffer rowKey)
 {
 QueryFilter filter = 

[jira] [Commented] (CASSANDRA-5397) Updates to PerRowSecondaryIndex don't use most current values

2013-04-05 Thread Marcus Eriksson (JIRA)

[ 
https://issues.apache.org/jira/browse/CASSANDRA-5397?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13623467#comment-13623467
 ] 

Marcus Eriksson commented on CASSANDRA-5397:


pushed a build fix to trunk (basically only fixed the test case): 
6afbed371c0d12a15a969e4f52ba670998bab282 RowMutations do not take QueryPath in 
trunk

 Updates to PerRowSecondaryIndex don't use most current values 
 --

 Key: CASSANDRA-5397
 URL: https://issues.apache.org/jira/browse/CASSANDRA-5397
 Project: Cassandra
  Issue Type: Bug
Affects Versions: 1.2.3
Reporter: Sam Tunnicliffe
Assignee: Sam Tunnicliffe
Priority: Minor
 Fix For: 1.2.4

 Attachments: 5397_12.txt, 5397-1.2-v3.txt, 5397-1.2-v4.txt, 
 5397_trunk.txt, 5397.txt


 The way that updates to secondary indexes are performed using  
 SecondaryIndexManager.Updater is flawed for PerRowSecondaryIndexes.  Unlike 
 PerColumnSecondaryIndexes, which only require the old  new values for a 
 single column,  the expectation is that a PerRow indexer can be given just a 
 key which it will use to retrieve the entire row (or as many columns as it 
 requires) and perform its indexing on those columns.  As the indexes are 
 updated before the memtable atomic swap occurs, a per-row indexer may only 
 read the previous values for the row, not the new ones that are being 
 written. In the case of an insert, there is no previous value and so nothing 
 is added to the index.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


[Cassandra Wiki] Trivial Update of DemetraBu by DemetraBu

2013-04-05 Thread Apache Wiki
Dear Wiki user,

You have subscribed to a wiki page or wiki category on Cassandra Wiki for 
change notification.

The DemetraBu page has been changed by DemetraBu:
http://wiki.apache.org/cassandra/DemetraBu

New page:
I am 24 years old and my name is Ben Barlow. I life in Nice (France).BR
BR
BR
Check out my web-site :: [[http://www.jujunation.org/ErnieHart|Insurance 
Adjuster Jobs Tampa Fl]]


[Cassandra Wiki] Trivial Update of AlisonCoa by AlisonCoa

2013-04-05 Thread Apache Wiki
Dear Wiki user,

You have subscribed to a wiki page or wiki category on Cassandra Wiki for 
change notification.

The AlisonCoa page has been changed by AlisonCoa:
http://wiki.apache.org/cassandra/AlisonCoa

New page:
My name: Alison CoatesBR
Age: 20BR
Country: AustraliaBR
Town: Delan BR
ZIP: 4671BR
Address: 22 Delan RoadBR
BR
My webpage: 
[[http://aagi.ceavi.udesc.br/wiki/index.php?title=Utilizador:AbigailLo|Sennett 
Residence discount]]


[Cassandra Wiki] Trivial Update of Allison42 by Allison42

2013-04-05 Thread Apache Wiki
Dear Wiki user,

You have subscribed to a wiki page or wiki category on Cassandra Wiki for 
change notification.

The Allison42 page has been changed by Allison42:
http://wiki.apache.org/cassandra/Allison42?action=diffrev1=9rev2=10

- The charge card advance loan comes with a very high fee, as well as the 
monthly interest about it is greater than that for the purchases made, using 
the finance card.BR
+ Simply put, a home loan loan that gives 100% financing does not need a 
downpayment. Unlike the money shark, hired thugs aren't sent to get the 
borrowed funds money if the payment is late. For slander lives upon succession, 
Forever housed where it gets possession. Nonetheless, problems continue to 
exist with the strict secularization of society. Adapting for your expediency 
you'll be able to submit an application on an instant cash loans via online or 
offline ways.BR
  BR
+ my web blog: [[|Payday loans instant cash]]
- Along with payment protection insurance, this might be an excellent way of 
providing yourself with a little extra leeway, especially if you're borrowing a 
significant amount over a prolonged period. Again, the chance of the money is 
cut down tremendously when the lender turns into a lien around the property. 
Living disabled was worth the expense of escaping of their predicament. 
Underwriting criteria became so strict that no self employed was eligible to 
get a remortgage or a secured loan without concrete evidence of income.BR
- BR
- My web-site; [[http://www.drbobart.net/dbaguest/view.php|personel loans]]
  


[Cassandra Wiki] Trivial Update of Which_will_pay_for_debit_card_benefits_ by Allison42

2013-04-05 Thread Apache Wiki
Dear Wiki user,

You have subscribed to a wiki page or wiki category on Cassandra Wiki for 
change notification.

The Which_will_pay_for_debit_card_benefits_ page has been changed by 
Allison42:
http://wiki.apache.org/cassandra/Which_will_pay_for_debit_card_benefits_

New page:
Actually, since the technology is advancing, people prefer to go online to use 
for the payday loan than to go to a local loan shop. The projects approved 
today will support a lot more than 260 jobs. They not just help you to repay 
your loan easily, but in addition enable you to maintain a fantastic credit 
file. I screamed and bellowed and railed and wept angry unaccepting tears 
yesterday evening as I fully began to find out exactly how warped my thinking 
and feeling has grown to be. Fair FICO numerous 620 to 659 are regarded with 
much consideration as these are not good digits based on the FICO score 
scale.BR
BR
[[http://dotegypt.net/home/blog/view/1035172/a-bad-credit-score-company-loans-to-get-started-a-different-enterprise|payday
 online]] [[http://plae.com/blog/48738/bad-credit-remortgage/|personal loans 
rates]] [[http://cmc.jbcourse.com/blog/index.php?postid=72228|faxless payday 
loans]] [[http://illda.eu/moodle/user/view.php?id=16course=1|signature loans]] 
[[http://peachio.com/kfc/groups/fa-pot-giant-killers-notts-nation-business-banking-on-tv-to-help-make-the-big-cash-advance/|payday
 loans without checking account]] 
[[http://seaporttattoos.com/war_junkies/groups/consolidation-personal-loans-for-money-improve-comfort/|boat
 loans calculator]] 
[[http://snakeeyezz.com/money/index.php?p=blogs/viewstory/904858|pls payday 
loans]] [[http://www.idvanzio.it/members/kami9627/activity/212026|payday loan 
direct]] [[http://chat.seyghalan.com/link/5702|loans for bad credit people]] 
[[http://mycityupdate.com/Hudsonholding/blogs/viewstory/131707|the payday loans 
online]]BR
BR
Through a wire transfer your hard earned money will typically be available with 
the following day. Another time to make use of your bank card is to get a 
weekly expense like food shopping, where it can be much easier to just put that 
on your own bank card. Arizona wouldn't function as first state to remove 
payday lenders. Oftentimes in life, the need arises to gain access to quick 
cash, that is what makes all the cash advance so appealing to numerous 
borrowers. Another factor will be the Texans offensive system where tight ends 
and running backs are an integral part in the passing attack [[|]][[|Payday 
loans instant cash]]/a in order in order to avoid that you simply should 
inquire about financing officer's reputation. For Residents of Fresno, Peoria 
and San Jose- Payday Loans Help Them Manage Their Monthly Bills.BR
BR
 BR
BR
Buying a totally new car or home more regularly absolutely nothing requires 
some kind of loan through the bank, whether it can be a bank mortgage or it 
could be an individual bank loan while using the seller. This loan scheme plays 
a significant role to enhance your small business sector or to fulfill 
challenges. If you imagine about it, celebrate perfect sense; A 84 month car 
finance is 7 years. After obtaining a reverse mortgage, borrowers must continue 
to generate necessary home repairs and be careful of these property. There are 
many options online for non status loans from the bank and other lenders. It 
isn't always important to wait for any job opening, as many school districts 
will always be accepting applications to help keep on file.


[Cassandra Wiki] Trivial Update of NicholasG by NicholasG

2013-04-05 Thread Apache Wiki
Dear Wiki user,

You have subscribed to a wiki page or wiki category on Cassandra Wiki for 
change notification.

The NicholasG page has been changed by NicholasG:
http://wiki.apache.org/cassandra/NicholasG

New page:
Glenn is what you can call me but you can call me anything you like.BR
Software developing is the place where I make a living. Ohio is where my wife 
and i live but now I'm considering other options. My wife doesn't like it means 
I do but what Thought about like doing is playing badminton but I can't make it 
my profession really.BR
BR
my web page [[http://scpoolguys.com|swimming pool repair chapin sc]]


[Cassandra Wiki] Trivial Update of LeonBarry by LeonBarry

2013-04-05 Thread Apache Wiki
Dear Wiki user,

You have subscribed to a wiki page or wiki category on Cassandra Wiki for 
change notification.

The LeonBarry page has been changed by LeonBarry:
http://wiki.apache.org/cassandra/LeonBarry

New page:
Name: Leon BarryBR
Age: 28BR
Country: NetherlandsBR
City: Almere BR
ZIP: 1321 AustriaBR
Address: Couperusweg 62BR
BR
My website: [[http://www.newpropertyguide.com/village-pasir-panjang|click here]]


[Cassandra Wiki] Trivial Update of Laurie59H by Laurie59H

2013-04-05 Thread Apache Wiki
Dear Wiki user,

You have subscribed to a wiki page or wiki category on Cassandra Wiki for 
change notification.

The Laurie59H page has been changed by Laurie59H:
http://wiki.apache.org/cassandra/Laurie59H

New page:
Nothing to say about myself at all.BR
Finally a member of this community.BR
I just hope I'm useful at allBR
BR
Feel free to surf to my page; [[http://www.assassinscreed3.info|Assassins Creed 
3]]


[jira] [Created] (CASSANDRA-5428) CQL3 don't validate that collections haven't more than 64K elements

2013-04-05 Thread Sylvain Lebresne (JIRA)
Sylvain Lebresne created CASSANDRA-5428:
---

 Summary: CQL3 don't validate that collections haven't more than 
64K elements
 Key: CASSANDRA-5428
 URL: https://issues.apache.org/jira/browse/CASSANDRA-5428
 Project: Cassandra
  Issue Type: Bug
Affects Versions: 1.2.0
Reporter: Sylvain Lebresne
Priority: Minor


This is somewhat similar to CASSANDRA-5355 but with a twist. When we serialize 
collections, not only does the size of the elements is limited to 64K, but the 
number of elements is too because it is also an unsigned short.

Now the same argument than in CASSANDRA-5355 that collections are places to 
denormalize small amounts of data is true here too. So the fact that 
collections are limited to 64K elements is something I could live with. 
However, we don't validate that no more than 64K elements are inserted. And in 
fact, we can't validate it if the elements are added one by one.

So in practice, you can insert more than 64K elements, but if you try to read 
it, you will only get back some subset of the collection. And the number of 
elements returned will correspond to the 2 last bytes of the real size (so a 
collection of 65536 elements will be returned as 1 element). Imo, that's more 
problematic.

So since unfortunately we can't validate this at insertion, I suggest that as a 
first step we:
# document that limitation (in http://cassandra.apache.org/doc/cql3/CQL.html 
typically)
# when we read a collection that has  64K elements, we detect it and when 
serializing that for the client, we:
** return as much as we can, i.e. the 64K first ones
** log a warning that something is wrong

On the longer term, for 2.0, maybe we should just change the serialization 
format and use an int for the collection size, using an unsigned short was 
probably misguided. Of course that changes said serialization format so we have 
to bump the native protocol version for that (and thus can't do that in 1.2).

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


[jira] [Reopened] (CASSANDRA-3533) TimeoutException when there is a firewall issue.

2013-04-05 Thread Brandon Williams (JIRA)

 [ 
https://issues.apache.org/jira/browse/CASSANDRA-3533?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Brandon Williams reopened CASSANDRA-3533:
-


Something's wrong here, because I'm randomly seeing these in the dtests:

{noformat}
 INFO [main] 2013-04-05 04:53:22,574 ThriftServer.java (line 90) Binding thrift 
service to /127.0.0.2:9160
 INFO [main] 2013-04-05 04:53:22,622 ThriftServer.java (line 102) Using 
TFramedTransport with a max frame size of 15728640 bytes.
ERROR [GossipStage:1] 2013-04-05 04:53:23,048 CassandraDaemon.java (line 179) 
Exception in thread Thread[GossipStage:1,5,main]
java.lang.AssertionError
at 
org.apache.cassandra.service.EchoVerbHandler.doVerb(EchoVerbHandler.java:17)
at 
org.apache.cassandra.net.MessageDeliveryTask.run(MessageDeliveryTask.java:56)
at 
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:895)
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:918)
at java.lang.Thread.run(Thread.java:662)
{noformat}

 TimeoutException when there is a firewall issue.
 

 Key: CASSANDRA-3533
 URL: https://issues.apache.org/jira/browse/CASSANDRA-3533
 Project: Cassandra
  Issue Type: Improvement
  Components: Core
Reporter: Vijay
Assignee: Vijay
Priority: Minor
 Fix For: 2.0

 Attachments: 0001-CASSANDRA-3533.patch, 3533.txt


 When one node in the cluster is not able to talk to the other DC/RAC due to 
 firewall or network related issue (StorageProxy calls fail), and the nodes 
 are NOT marked down because at least one node in the cluster can talk to the 
 other DC/RAC, we get timeoutException instead of throwing a 
 unavailableException.
 The problem with this:
 1) It is hard to monitor/identify these errors.
 2) It is hard to diffrentiate from the client if the node being bad vs a bad 
 query.
 3) when this issue happens we have to wait for at-least the RPC timeout time 
 to know that the query wont succeed.
 Possible Solution: when marking a node down we might want to check if the 
 node is actually alive by trying to communicate to it? So we can be sure that 
 the node is actually alive.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


[jira] [Reopened] (CASSANDRA-5378) Fat Client: No longer works in 1.2

2013-04-05 Thread Sylvain Lebresne (JIRA)

 [ 
https://issues.apache.org/jira/browse/CASSANDRA-5378?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Sylvain Lebresne reopened CASSANDRA-5378:
-


 Fat Client: No longer works in 1.2
 --

 Key: CASSANDRA-5378
 URL: https://issues.apache.org/jira/browse/CASSANDRA-5378
 Project: Cassandra
  Issue Type: Bug
Affects Versions: 1.2.0
Reporter: Carl Yeksigian
Assignee: Carl Yeksigian
  Labels: client
 Fix For: 1.2.4

 Attachments: 5378-1.2.txt, 5378.txt, 5378-v2.txt


 The current client only example doesn't compile. After doing some updates, 
 the fat client still won't work, mainly because the schema is not being 
 pushed to the fat client.
 I've made changes to the client to support CQL3 commands, to the 
 ServiceManager to wait until a migration has completed before starting the 
 client, and to the MigrationManager to not try to pull schemas from a fat 
 client.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


[jira] [Commented] (CASSANDRA-5378) Fat Client: No longer works in 1.2

2013-04-05 Thread Sylvain Lebresne (JIRA)

[ 
https://issues.apache.org/jira/browse/CASSANDRA-5378?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13623599#comment-13623599
 ] 

Sylvain Lebresne commented on CASSANDRA-5378:
-

This broke a dtests, namely cql_tests.py:TestCQL.bug_5240_test.

The reason is that the patch modifies SelectStatement.java and call 
CFMetadata.getKeyName(), but that method should not be called from CQL3 ever. 
I'm not sure I understand why fixing the fat client would involve making any 
kind of change in SelectStatement tbh.

 Fat Client: No longer works in 1.2
 --

 Key: CASSANDRA-5378
 URL: https://issues.apache.org/jira/browse/CASSANDRA-5378
 Project: Cassandra
  Issue Type: Bug
Affects Versions: 1.2.0
Reporter: Carl Yeksigian
Assignee: Carl Yeksigian
  Labels: client
 Fix For: 1.2.4

 Attachments: 5378-1.2.txt, 5378.txt, 5378-v2.txt


 The current client only example doesn't compile. After doing some updates, 
 the fat client still won't work, mainly because the schema is not being 
 pushed to the fat client.
 I've made changes to the client to support CQL3 commands, to the 
 ServiceManager to wait until a migration has completed before starting the 
 client, and to the MigrationManager to not try to pull schemas from a fat 
 client.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


[Cassandra Wiki] Trivial Update of JocelynBl by JocelynBl

2013-04-05 Thread Apache Wiki
Dear Wiki user,

You have subscribed to a wiki page or wiki category on Cassandra Wiki for 
change notification.

The JocelynBl page has been changed by JocelynBl:
http://wiki.apache.org/cassandra/JocelynBl

New page:
There is nothing to tell about me I think.BR
I enjoy of finally being a member of apache.org.BR
I really wish I'm useful in some way .BR
BR
my weblog ... [[http://mp3sdown.com/music/download/1/aretha-franklin.html|mp3s]]


[Cassandra Wiki] Trivial Update of Cecil5546 by Cecil5546

2013-04-05 Thread Apache Wiki
Dear Wiki user,

You have subscribed to a wiki page or wiki category on Cassandra Wiki for 
change notification.

The Cecil5546 page has been changed by Cecil5546:
http://wiki.apache.org/cassandra/Cecil5546

New page:
Nothing to say about me really.BR
Great to be a member of apache.org.BR
I just wish I'm useful in one way here.BR
BR
my website: 
[[http://layhillvillage.surflayhill.com/members/shondasto/activity/34317|click 
through the next article]]


[jira] [Commented] (CASSANDRA-5428) CQL3 don't validate that collections haven't more than 64K elements

2013-04-05 Thread Jonathan Ellis (JIRA)

[ 
https://issues.apache.org/jira/browse/CASSANDRA-5428?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13623622#comment-13623622
 ] 

Jonathan Ellis commented on CASSANDRA-5428:
---

Sounds like a reasonable plan.

 CQL3 don't validate that collections haven't more than 64K elements
 ---

 Key: CASSANDRA-5428
 URL: https://issues.apache.org/jira/browse/CASSANDRA-5428
 Project: Cassandra
  Issue Type: Bug
Affects Versions: 1.2.0
Reporter: Sylvain Lebresne
Priority: Minor

 This is somewhat similar to CASSANDRA-5355 but with a twist. When we 
 serialize collections, not only does the size of the elements is limited to 
 64K, but the number of elements is too because it is also an unsigned short.
 Now the same argument than in CASSANDRA-5355 that collections are places to 
 denormalize small amounts of data is true here too. So the fact that 
 collections are limited to 64K elements is something I could live with. 
 However, we don't validate that no more than 64K elements are inserted. And 
 in fact, we can't validate it if the elements are added one by one.
 So in practice, you can insert more than 64K elements, but if you try to read 
 it, you will only get back some subset of the collection. And the number of 
 elements returned will correspond to the 2 last bytes of the real size (so a 
 collection of 65536 elements will be returned as 1 element). Imo, that's more 
 problematic.
 So since unfortunately we can't validate this at insertion, I suggest that as 
 a first step we:
 # document that limitation (in http://cassandra.apache.org/doc/cql3/CQL.html 
 typically)
 # when we read a collection that has  64K elements, we detect it and when 
 serializing that for the client, we:
 ** return as much as we can, i.e. the 64K first ones
 ** log a warning that something is wrong
 On the longer term, for 2.0, maybe we should just change the serialization 
 format and use an int for the collection size, using an unsigned short was 
 probably misguided. Of course that changes said serialization format so we 
 have to bump the native protocol version for that (and thus can't do that in 
 1.2).

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


git commit: Revert EchoMessage code

2013-04-05 Thread jbellis
Updated Branches:
  refs/heads/trunk 6afbed371 - b27c61ba5


Revert EchoMessage code

This reverts commits c3ab05f3936b1bedd2e28ebf86790c0eaa45eaba and 
a7b2ff65ac1946ca8e7e52e00374a83ebe922627.


Project: http://git-wip-us.apache.org/repos/asf/cassandra/repo
Commit: http://git-wip-us.apache.org/repos/asf/cassandra/commit/b27c61ba
Tree: http://git-wip-us.apache.org/repos/asf/cassandra/tree/b27c61ba
Diff: http://git-wip-us.apache.org/repos/asf/cassandra/diff/b27c61ba

Branch: refs/heads/trunk
Commit: b27c61ba5f48f0d719ed95d2254693cf41d343d0
Parents: 6afbed3
Author: Jonathan Ellis jbel...@apache.org
Authored: Fri Apr 5 08:40:38 2013 -0500
Committer: Jonathan Ellis jbel...@apache.org
Committed: Fri Apr 5 08:42:09 2013 -0500

--
 src/java/org/apache/cassandra/gms/EchoMessage.java |   29 --
 src/java/org/apache/cassandra/gms/Gossiper.java|   44 +--
 .../org/apache/cassandra/net/MessagingService.java |4 -
 .../apache/cassandra/service/EchoVerbHandler.java  |   22 ---
 .../apache/cassandra/service/StorageService.java   |1 -
 .../apache/cassandra/io/CompactSerializerTest.java |1 -
 6 files changed, 14 insertions(+), 87 deletions(-)
--


http://git-wip-us.apache.org/repos/asf/cassandra/blob/b27c61ba/src/java/org/apache/cassandra/gms/EchoMessage.java
--
diff --git a/src/java/org/apache/cassandra/gms/EchoMessage.java 
b/src/java/org/apache/cassandra/gms/EchoMessage.java
deleted file mode 100644
index 3f5f566..000
--- a/src/java/org/apache/cassandra/gms/EchoMessage.java
+++ /dev/null
@@ -1,29 +0,0 @@
-package org.apache.cassandra.gms;
-
-import java.io.DataInput;
-import java.io.DataOutput;
-import java.io.IOException;
-
-import org.apache.cassandra.io.IVersionedSerializer;
-
-public class EchoMessage
-{
-public static IVersionedSerializerEchoMessage serializer = new 
EchoMessageSerializer();
-
-public static class EchoMessageSerializer implements 
IVersionedSerializerEchoMessage
-{
-public void serialize(EchoMessage t, DataOutput out, int version) 
throws IOException
-{
-}
-
-public EchoMessage deserialize(DataInput in, int version) throws 
IOException
-{
-return new EchoMessage();
-}
-
-public long serializedSize(EchoMessage t, int version)
-{
-return 0;
-}
-}
-}

http://git-wip-us.apache.org/repos/asf/cassandra/blob/b27c61ba/src/java/org/apache/cassandra/gms/Gossiper.java
--
diff --git a/src/java/org/apache/cassandra/gms/Gossiper.java 
b/src/java/org/apache/cassandra/gms/Gossiper.java
index 04ece7a..ae920e1 100644
--- a/src/java/org/apache/cassandra/gms/Gossiper.java
+++ b/src/java/org/apache/cassandra/gms/Gossiper.java
@@ -33,8 +33,6 @@ import org.slf4j.LoggerFactory;
 import org.apache.cassandra.concurrent.DebuggableScheduledThreadPoolExecutor;
 import org.apache.cassandra.config.DatabaseDescriptor;
 import org.apache.cassandra.dht.Token;
-import org.apache.cassandra.net.IAsyncCallback;
-import org.apache.cassandra.net.MessageIn;
 import org.apache.cassandra.net.MessageOut;
 import org.apache.cassandra.net.MessagingService;
 import org.apache.cassandra.service.StorageService;
@@ -761,35 +759,21 @@ public class Gossiper implements 
IFailureDetectionEventListener, GossiperMBean
 
 }
 
-private void markAlive(final InetAddress addr, final EndpointState 
localState)
+private void markAlive(InetAddress addr, EndpointState localState)
 {
-MessageOutEchoMessage echoMessage = new 
MessageOutEchoMessage(MessagingService.Verb.ECHO, new EchoMessage(), 
EchoMessage.serializer);
-logger.trace(Sending a EchoMessage to {}, addr);
-IAsyncCallback echoHandler = new IAsyncCallback()
-{
-public boolean isLatencyForSnitch()
-{
-return false;
-}
-
-public void response(MessageIn msg)
-{
-if (logger.isTraceEnabled())
-logger.trace(marking as alive {}, addr);
-localState.markAlive();
-localState.updateTimestamp(); // prevents doStatusCheck from 
racing us and evicting if it was down  aVeryLongTime
-liveEndpoints.add(addr);
-unreachableEndpoints.remove(addr);
-expireTimeEndpointMap.remove(addr);
-logger.debug(removing expire time for endpoint :  + addr);
-logger.info(InetAddress {} is now UP, addr);
-for (IEndpointStateChangeSubscriber subscriber : subscribers)
-subscriber.onAlive(addr, localState);
-if (logger.isTraceEnabled())
-logger.trace(Notified  + subscribers);
-  

[Cassandra Wiki] Trivial Update of FloridaTo by FloridaTo

2013-04-05 Thread Apache Wiki
Dear Wiki user,

You have subscribed to a wiki page or wiki category on Cassandra Wiki for 
change notification.

The FloridaTo page has been changed by FloridaTo:
http://wiki.apache.org/cassandra/FloridaTo

New page:
Name: Florida TomlinBR
My age: 21BR
Country: NetherlandsBR
City: Amsterdam BR
Post code: 1074 BKBR
Street: Hemonystraat 14BR
BR
Here is my blog post - 
[[http://storns.net/mediawiki/index.php?title=Utente:ClarkGiro|http://storns.net/mediawiki/index.php?title=Utente:ClarkGiro]]


[jira] [Commented] (CASSANDRA-3533) TimeoutException when there is a firewall issue.

2013-04-05 Thread Jonathan Ellis (JIRA)

[ 
https://issues.apache.org/jira/browse/CASSANDRA-3533?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13623627#comment-13623627
 ] 

Jonathan Ellis commented on CASSANDRA-3533:
---

Reverted pending fix.

 TimeoutException when there is a firewall issue.
 

 Key: CASSANDRA-3533
 URL: https://issues.apache.org/jira/browse/CASSANDRA-3533
 Project: Cassandra
  Issue Type: Improvement
  Components: Core
Reporter: Vijay
Assignee: Vijay
Priority: Minor
 Fix For: 2.0

 Attachments: 0001-CASSANDRA-3533.patch, 3533.txt


 When one node in the cluster is not able to talk to the other DC/RAC due to 
 firewall or network related issue (StorageProxy calls fail), and the nodes 
 are NOT marked down because at least one node in the cluster can talk to the 
 other DC/RAC, we get timeoutException instead of throwing a 
 unavailableException.
 The problem with this:
 1) It is hard to monitor/identify these errors.
 2) It is hard to diffrentiate from the client if the node being bad vs a bad 
 query.
 3) when this issue happens we have to wait for at-least the RPC timeout time 
 to know that the query wont succeed.
 Possible Solution: when marking a node down we might want to check if the 
 node is actually alive by trying to communicate to it? So we can be sure that 
 the node is actually alive.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


[jira] [Updated] (CASSANDRA-5074) Add an official way to disable compaction

2013-04-05 Thread Marcus Eriksson (JIRA)

 [ 
https://issues.apache.org/jira/browse/CASSANDRA-5074?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Marcus Eriksson updated CASSANDRA-5074:
---

Attachment: 0001-CASSANDRA-5074-make-it-possible-to-disable-autocompa.patch

 Add an official way to disable compaction
 -

 Key: CASSANDRA-5074
 URL: https://issues.apache.org/jira/browse/CASSANDRA-5074
 Project: Cassandra
  Issue Type: Bug
Reporter: Jonathan Ellis
Assignee: Marcus Eriksson
Priority: Minor
 Fix For: 2.0

 Attachments: 
 0001-CASSANDRA-5074-make-it-possible-to-disable-autocompa.patch


 We've traditionally used min or max compaction threshold = 0 to disable 
 compaction, but this isn't exactly intuitive and it's inconsistently 
 implemented -- allowed from jmx, not allowed from cli.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


buildbot success in ASF Buildbot on cassandra-trunk

2013-04-05 Thread buildbot
The Buildbot has detected a restored build on builder cassandra-trunk while 
building cassandra.
Full details are available at:
 http://ci.apache.org/builders/cassandra-trunk/builds/2531

Buildbot URL: http://ci.apache.org/

Buildslave for this Build: portunus_ubuntu

Build Reason: scheduler
Build Source Stamp: [branch trunk] b27c61ba5f48f0d719ed95d2254693cf41d343d0
Blamelist: Jonathan Ellis jbel...@apache.org

Build succeeded!

sincerely,
 -The Buildbot





[Cassandra Wiki] Trivial Update of Jimmy60D by Jimmy60D

2013-04-05 Thread Apache Wiki
Dear Wiki user,

You have subscribed to a wiki page or wiki category on Cassandra Wiki for 
change notification.

The Jimmy60D page has been changed by Jimmy60D:
http://wiki.apache.org/cassandra/Jimmy60D

New page:
The important fact is that payment is made against metered heat.BR
1) Heat pumps don't burn oxygen or create stuffiness like open fires do. BR
BR
BR
BR
I am 35 years old and my name is Nilda Velasco. I life in Beek 
(Netherlands).BR
BR
Feel free to surf to my page :: 
[[http://waermepumpeinfo.de/|http://waermepumpeinfo.de]]


[Cassandra Wiki] Trivial Update of CliftonAl by CliftonAl

2013-04-05 Thread Apache Wiki
Dear Wiki user,

You have subscribed to a wiki page or wiki category on Cassandra Wiki for 
change notification.

The CliftonAl page has been changed by CliftonAl:
http://wiki.apache.org/cassandra/CliftonAl

New page:
My name is Opal Turk. I life in West Takone (Australia).BR
BR
BR
my web blog; 
[[http://crimeindetroit.com/awstats/cgi-bin/awstats.pl?framename=mainrightoutput=refererpages|mouse
 click the following webpage]]


[Cassandra Wiki] Trivial Update of Stewart20 by Stewart20

2013-04-05 Thread Apache Wiki
Dear Wiki user,

You have subscribed to a wiki page or wiki category on Cassandra Wiki for 
change notification.

The Stewart20 page has been changed by Stewart20:
http://wiki.apache.org/cassandra/Stewart20

New page:
Not much to say about myself I think.BR
Finally a part of this community.BR
I really hope I am useful in some way here.BR
BR
my website: [[http://www.imasturbate.org/social/link/28594|click the up coming 
document]]


[1/3] git commit: Add nodetool methods to disable/enable native transport. Patch by Michal Michalski, reviewed by brandonwilliams for CASSANDRA-5425

2013-04-05 Thread brandonwilliams
Updated Branches:
  refs/heads/cassandra-1.2 8a422179c - 1533f124c
  refs/heads/trunk b27c61ba5 - 0f479eb0f


Add nodetool methods to disable/enable native transport.
Patch by Michal Michalski, reviewed by brandonwilliams for
CASSANDRA-5425


Project: http://git-wip-us.apache.org/repos/asf/cassandra/repo
Commit: http://git-wip-us.apache.org/repos/asf/cassandra/commit/1533f124
Tree: http://git-wip-us.apache.org/repos/asf/cassandra/tree/1533f124
Diff: http://git-wip-us.apache.org/repos/asf/cassandra/diff/1533f124

Branch: refs/heads/cassandra-1.2
Commit: 1533f124c12257bcb17bfdf0d9096c239ac78fe8
Parents: 8a42217
Author: Brandon Williams brandonwilli...@apache.org
Authored: Fri Apr 5 09:52:29 2013 -0500
Committer: Brandon Williams brandonwilli...@apache.org
Committed: Fri Apr 5 09:52:29 2013 -0500

--
 .../apache/cassandra/service/CassandraDaemon.java  |4 ++--
 .../apache/cassandra/service/StorageService.java   |2 +-
 src/java/org/apache/cassandra/tools/NodeCmd.java   |4 
 src/java/org/apache/cassandra/tools/NodeProbe.java |   10 ++
 .../org/apache/cassandra/transport/Server.java |3 ++-
 .../org/apache/cassandra/tools/NodeToolHelp.yaml   |6 ++
 6 files changed, 25 insertions(+), 4 deletions(-)
--


http://git-wip-us.apache.org/repos/asf/cassandra/blob/1533f124/src/java/org/apache/cassandra/service/CassandraDaemon.java
--
diff --git a/src/java/org/apache/cassandra/service/CassandraDaemon.java 
b/src/java/org/apache/cassandra/service/CassandraDaemon.java
index 4e3bdfc..1eae488 100644
--- a/src/java/org/apache/cassandra/service/CassandraDaemon.java
+++ b/src/java/org/apache/cassandra/service/CassandraDaemon.java
@@ -368,13 +368,13 @@ public class CassandraDaemon
 if ((nativeFlag != null  Boolean.parseBoolean(nativeFlag)) || 
(nativeFlag == null  DatabaseDescriptor.startNativeTransport()))
 nativeServer.start();
 else
-logger.info(Not starting native transport as requested. Use JMX 
(StorageService-startNativeTransport()) to start it);
+logger.info(Not starting native transport as requested. Use JMX 
(StorageService-startNativeTransport()) or nodetool (enablebinary) to start 
it);
 
 String rpcFlag = System.getProperty(cassandra.start_rpc);
 if ((rpcFlag != null  Boolean.parseBoolean(rpcFlag)) || (rpcFlag == 
null  DatabaseDescriptor.startRpc()))
 thriftServer.start();
 else
-logger.info(Not starting RPC server as requested. Use JMX 
(StorageService-startRPCServer()) to start it);
+logger.info(Not starting RPC server as requested. Use JMX 
(StorageService-startRPCServer()) or nodetool (enablethrift) to start it);
 }
 
 /**

http://git-wip-us.apache.org/repos/asf/cassandra/blob/1533f124/src/java/org/apache/cassandra/service/StorageService.java
--
diff --git a/src/java/org/apache/cassandra/service/StorageService.java 
b/src/java/org/apache/cassandra/service/StorageService.java
index 2069484..658f583 100644
--- a/src/java/org/apache/cassandra/service/StorageService.java
+++ b/src/java/org/apache/cassandra/service/StorageService.java
@@ -343,7 +343,7 @@ public class StorageService extends 
NotificationBroadcasterSupport implements IE
 {
 if (daemon == null)
 {
-throw new IllegalStateException(No configured  daemon);
+throw new IllegalStateException(No configured daemon);
 }
 daemon.nativeServer.stop();
 }

http://git-wip-us.apache.org/repos/asf/cassandra/blob/1533f124/src/java/org/apache/cassandra/tools/NodeCmd.java
--
diff --git a/src/java/org/apache/cassandra/tools/NodeCmd.java 
b/src/java/org/apache/cassandra/tools/NodeCmd.java
index b7ff504..4f3e1e1 100644
--- a/src/java/org/apache/cassandra/tools/NodeCmd.java
+++ b/src/java/org/apache/cassandra/tools/NodeCmd.java
@@ -107,10 +107,12 @@ public class NodeCmd
 COMPACT,
 COMPACTIONSTATS,
 DECOMMISSION,
+DISABLEBINARY,
 DISABLEGOSSIP,
 DISABLEHANDOFF,
 DISABLETHRIFT,
 DRAIN,
+ENABLEBINARY,
 ENABLEGOSSIP,
 ENABLEHANDOFF,
 ENABLETHRIFT,
@@ -1048,6 +1050,8 @@ public class NodeCmd
 case TPSTATS : 
nodeCmd.printThreadPoolStats(System.out); break;
 case VERSION : 
nodeCmd.printReleaseVersion(System.out); break;
 case COMPACTIONSTATS : 
nodeCmd.printCompactionStats(System.out); break;
+case DISABLEBINARY   : probe.stopNativeTransport(); break;
+case ENABLEBINARY: probe.startNativeTransport(); break;
 case 

[2/3] git commit: Add nodetool methods to disable/enable native transport. Patch by Michal Michalski, reviewed by brandonwilliams for CASSANDRA-5425

2013-04-05 Thread brandonwilliams
Add nodetool methods to disable/enable native transport.
Patch by Michal Michalski, reviewed by brandonwilliams for
CASSANDRA-5425


Project: http://git-wip-us.apache.org/repos/asf/cassandra/repo
Commit: http://git-wip-us.apache.org/repos/asf/cassandra/commit/1533f124
Tree: http://git-wip-us.apache.org/repos/asf/cassandra/tree/1533f124
Diff: http://git-wip-us.apache.org/repos/asf/cassandra/diff/1533f124

Branch: refs/heads/trunk
Commit: 1533f124c12257bcb17bfdf0d9096c239ac78fe8
Parents: 8a42217
Author: Brandon Williams brandonwilli...@apache.org
Authored: Fri Apr 5 09:52:29 2013 -0500
Committer: Brandon Williams brandonwilli...@apache.org
Committed: Fri Apr 5 09:52:29 2013 -0500

--
 .../apache/cassandra/service/CassandraDaemon.java  |4 ++--
 .../apache/cassandra/service/StorageService.java   |2 +-
 src/java/org/apache/cassandra/tools/NodeCmd.java   |4 
 src/java/org/apache/cassandra/tools/NodeProbe.java |   10 ++
 .../org/apache/cassandra/transport/Server.java |3 ++-
 .../org/apache/cassandra/tools/NodeToolHelp.yaml   |6 ++
 6 files changed, 25 insertions(+), 4 deletions(-)
--


http://git-wip-us.apache.org/repos/asf/cassandra/blob/1533f124/src/java/org/apache/cassandra/service/CassandraDaemon.java
--
diff --git a/src/java/org/apache/cassandra/service/CassandraDaemon.java 
b/src/java/org/apache/cassandra/service/CassandraDaemon.java
index 4e3bdfc..1eae488 100644
--- a/src/java/org/apache/cassandra/service/CassandraDaemon.java
+++ b/src/java/org/apache/cassandra/service/CassandraDaemon.java
@@ -368,13 +368,13 @@ public class CassandraDaemon
 if ((nativeFlag != null  Boolean.parseBoolean(nativeFlag)) || 
(nativeFlag == null  DatabaseDescriptor.startNativeTransport()))
 nativeServer.start();
 else
-logger.info(Not starting native transport as requested. Use JMX 
(StorageService-startNativeTransport()) to start it);
+logger.info(Not starting native transport as requested. Use JMX 
(StorageService-startNativeTransport()) or nodetool (enablebinary) to start 
it);
 
 String rpcFlag = System.getProperty(cassandra.start_rpc);
 if ((rpcFlag != null  Boolean.parseBoolean(rpcFlag)) || (rpcFlag == 
null  DatabaseDescriptor.startRpc()))
 thriftServer.start();
 else
-logger.info(Not starting RPC server as requested. Use JMX 
(StorageService-startRPCServer()) to start it);
+logger.info(Not starting RPC server as requested. Use JMX 
(StorageService-startRPCServer()) or nodetool (enablethrift) to start it);
 }
 
 /**

http://git-wip-us.apache.org/repos/asf/cassandra/blob/1533f124/src/java/org/apache/cassandra/service/StorageService.java
--
diff --git a/src/java/org/apache/cassandra/service/StorageService.java 
b/src/java/org/apache/cassandra/service/StorageService.java
index 2069484..658f583 100644
--- a/src/java/org/apache/cassandra/service/StorageService.java
+++ b/src/java/org/apache/cassandra/service/StorageService.java
@@ -343,7 +343,7 @@ public class StorageService extends 
NotificationBroadcasterSupport implements IE
 {
 if (daemon == null)
 {
-throw new IllegalStateException(No configured  daemon);
+throw new IllegalStateException(No configured daemon);
 }
 daemon.nativeServer.stop();
 }

http://git-wip-us.apache.org/repos/asf/cassandra/blob/1533f124/src/java/org/apache/cassandra/tools/NodeCmd.java
--
diff --git a/src/java/org/apache/cassandra/tools/NodeCmd.java 
b/src/java/org/apache/cassandra/tools/NodeCmd.java
index b7ff504..4f3e1e1 100644
--- a/src/java/org/apache/cassandra/tools/NodeCmd.java
+++ b/src/java/org/apache/cassandra/tools/NodeCmd.java
@@ -107,10 +107,12 @@ public class NodeCmd
 COMPACT,
 COMPACTIONSTATS,
 DECOMMISSION,
+DISABLEBINARY,
 DISABLEGOSSIP,
 DISABLEHANDOFF,
 DISABLETHRIFT,
 DRAIN,
+ENABLEBINARY,
 ENABLEGOSSIP,
 ENABLEHANDOFF,
 ENABLETHRIFT,
@@ -1048,6 +1050,8 @@ public class NodeCmd
 case TPSTATS : 
nodeCmd.printThreadPoolStats(System.out); break;
 case VERSION : 
nodeCmd.printReleaseVersion(System.out); break;
 case COMPACTIONSTATS : 
nodeCmd.printCompactionStats(System.out); break;
+case DISABLEBINARY   : probe.stopNativeTransport(); break;
+case ENABLEBINARY: probe.startNativeTransport(); break;
 case DISABLEGOSSIP   : probe.stopGossiping(); break;
 case ENABLEGOSSIP: probe.startGossiping(); break;

[3/3] git commit: Merge branch 'cassandra-1.2' into trunk

2013-04-05 Thread brandonwilliams
Merge branch 'cassandra-1.2' into trunk


Project: http://git-wip-us.apache.org/repos/asf/cassandra/repo
Commit: http://git-wip-us.apache.org/repos/asf/cassandra/commit/0f479eb0
Tree: http://git-wip-us.apache.org/repos/asf/cassandra/tree/0f479eb0
Diff: http://git-wip-us.apache.org/repos/asf/cassandra/diff/0f479eb0

Branch: refs/heads/trunk
Commit: 0f479eb0f139f690e130a021191ba31be4f8efe7
Parents: b27c61b 1533f12
Author: Brandon Williams brandonwilli...@apache.org
Authored: Fri Apr 5 09:54:06 2013 -0500
Committer: Brandon Williams brandonwilli...@apache.org
Committed: Fri Apr 5 09:54:06 2013 -0500

--
 .../apache/cassandra/service/CassandraDaemon.java  |4 ++--
 .../apache/cassandra/service/StorageService.java   |2 +-
 src/java/org/apache/cassandra/tools/NodeCmd.java   |4 
 src/java/org/apache/cassandra/tools/NodeProbe.java |   10 ++
 .../org/apache/cassandra/transport/Server.java |3 ++-
 .../org/apache/cassandra/tools/NodeToolHelp.yaml   |6 ++
 6 files changed, 25 insertions(+), 4 deletions(-)
--


http://git-wip-us.apache.org/repos/asf/cassandra/blob/0f479eb0/src/java/org/apache/cassandra/service/CassandraDaemon.java
--

http://git-wip-us.apache.org/repos/asf/cassandra/blob/0f479eb0/src/java/org/apache/cassandra/service/StorageService.java
--

http://git-wip-us.apache.org/repos/asf/cassandra/blob/0f479eb0/src/java/org/apache/cassandra/tools/NodeProbe.java
--



[jira] [Commented] (CASSANDRA-5400) Allow multiple ports to gossip from a single IP address

2013-04-05 Thread Jonathan Ellis (JIRA)

[ 
https://issues.apache.org/jira/browse/CASSANDRA-5400?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13623686#comment-13623686
 ] 

Jonathan Ellis commented on CASSANDRA-5400:
---

bq. all existing client drivers and tools that were identifying node with just 
the ip addresses will have to be fixed

To be fair, it only means that you can't run your cluster in multi-port mode 
until you've upgraded your client.

bq. none of the describe_* thrift calls include the port currently, and there 
is no easy way to return it without breaking the thrift API

We'd have to add new describe_multiport_* calls, again with an eye towards 
making it opt-in.

bq. it seems to me too much trouble for little benefit to change it now

I'm on the fence.  Does this solve any other problem than I don't have to 
create IP aliases?  (Which I have done, with non-local addresses, so yes, it's 
quite possible.)

While not a critical downside, I will also note that this gives people quite a 
lot of rope to make troubleshooting why won't node X talk to node Y very 
difficult.

 Allow multiple ports to gossip from a single IP address
 ---

 Key: CASSANDRA-5400
 URL: https://issues.apache.org/jira/browse/CASSANDRA-5400
 Project: Cassandra
  Issue Type: New Feature
Affects Versions: 2.0
Reporter: Carl Yeksigian
Assignee: Carl Yeksigian
 Fix For: 2.0

 Attachments: 5400.txt, 5400-v2.txt, 5400-v3.patch, 5400-v4.patch


 If a fat client is running on the same machine as a Cassandra node, the fat 
 client must be allocated a new IP address. However, since the node is now a 
 part of the gossip, the other nodes in the ring must be able to talk to it. 
 This means that a local only address (127.0.0.n) won't actually work for the 
 rest of the ring.
 This also would allow for multiple Cassandra service instances to run on a 
 single machine, or from a group of machines behind a NAT.
 The change is simple in concept: instead of using an InetAddress, use a 
 different class. Instead of using an InetSocketAddress, which would still tie 
 us to using InetAddress, I've added a new class, CassandraInstanceEndpoint. 
 The serializer allows for reading a serialized Inet4Address or Inet6Address; 
 also, the message service can still communicate with 
 non-CassandraInstanceEndpoint aware code.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


[jira] [Commented] (CASSANDRA-5418) repair freezing

2013-04-05 Thread Igor Ivanov (JIRA)

[ 
https://issues.apache.org/jira/browse/CASSANDRA-5418?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13623692#comment-13623692
 ] 

Igor Ivanov commented on CASSANDRA-5418:


Since that I've tried to run offline sstablescrub, it didn't help. As was 
suggested on IRC, I've tried sstable2json on data file and it worked. But when 
joining node tries to stream file - it fails repeatedly on that file.

 repair freezing
 ---

 Key: CASSANDRA-5418
 URL: https://issues.apache.org/jira/browse/CASSANDRA-5418
 Project: Cassandra
  Issue Type: Bug
  Components: Core
Affects Versions: 1.2.2
 Environment: 5 nodes, RackInferring snitch, OpenVZ VMs, Centos 6, 
 Oracle JVM with JNA enabled.
Reporter: Igor Ivanov

 When I run *nodetool repair* on cas01 node it get's stuck at some point.
 I see following exceptions in cas01 system.log:
 {quote}
 ERROR [Streaming to /10.10.45.60:28] 2013-04-02 09:03:55,353 
 CassandraDaemon.java (line 132) Exception in thread Thread[Streaming to 
 /10.10.45.60:28,5,main]
 java.lang.RuntimeException: java.io.EOFException
   at com.google.common.base.Throwables.propagate(Throwables.java:160)
   at 
 org.apache.cassandra.utils.WrappedRunnable.run(WrappedRunnable.java:32)
   at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown 
 Source)
   at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
   at java.lang.Thread.run(Unknown Source)
 Caused by: java.io.EOFException
   at java.io.DataInputStream.readInt(Unknown Source)
   at 
 org.apache.cassandra.streaming.FileStreamTask.receiveReply(FileStreamTask.java:193)
   at 
 org.apache.cassandra.streaming.compress.CompressedFileStreamTask.stream(CompressedFileStreamTask.java:114)
   at 
 org.apache.cassandra.streaming.FileStreamTask.runMayThrow(FileStreamTask.java:91)
   at 
 org.apache.cassandra.utils.WrappedRunnable.run(WrappedRunnable.java:28)
   ... 3 more
 ERROR [Thread-2076] 2013-04-02 09:07:12,261 CassandraDaemon.java (line 132) 
 Exception in thread Thread[Thread-2076,5,main]
 java.lang.AssertionError: incorrect row data size 130921 written to 
 /var/lib/cassandra/data/EDITED/content_list/footballsite-content_list-tmp-ib-3660-Data.db;
  correct is 131074
   at 
 org.apache.cassandra.io.sstable.SSTableWriter.appendFromStream(SSTableWriter.java:285)
   at 
 org.apache.cassandra.streaming.IncomingStreamReader.streamIn(IncomingStreamReader.java:179)
   at 
 org.apache.cassandra.streaming.IncomingStreamReader.read(IncomingStreamReader.java:122)
   at 
 org.apache.cassandra.net.IncomingTcpConnection.stream(IncomingTcpConnection.java:238)
   at 
 org.apache.cassandra.net.IncomingTcpConnection.handleStream(IncomingTcpConnection.java:178)
   at 
 org.apache.cassandra.net.IncomingTcpConnection.run(IncomingTcpConnection.java:78)
 {quote}
 On other machines there are some exceptions too:
 {quote}
 ERROR [Thread-1424] 2013-04-02 09:07:12,248 CassandraDaemon.java (line 132) 
 Exception in thread Thread[Thread-1424,5,main]
 java.lang.AssertionError: incorrect row data size 130921 written to 
 /var/lib/cassandra/data/EDITED/content_list/footballsite-content_list-tmp-ib-2268-Data.db;
  correct is 131074
   at 
 org.apache.cassandra.io.sstable.SSTableWriter.appendFromStream(SSTableWriter.java:285)
   at 
 org.apache.cassandra.streaming.IncomingStreamReader.streamIn(IncomingStreamReader.java:179)
   at 
 org.apache.cassandra.streaming.IncomingStreamReader.read(IncomingStreamReader.java:122)
   at 
 org.apache.cassandra.net.IncomingTcpConnection.stream(IncomingTcpConnection.java:238)
   at 
 org.apache.cassandra.net.IncomingTcpConnection.handleStream(IncomingTcpConnection.java:178)
   at 
 org.apache.cassandra.net.IncomingTcpConnection.run(IncomingTcpConnection.java:78)
 ERROR [Streaming to /10.10.45.58:55] 2013-04-02 09:07:12,263 
 CassandraDaemon.java (line 132) Exception in thread Thread[Streaming to 
 /10.10.45.58:55,5,main]
 java.lang.RuntimeException: java.io.EOFException
   at com.google.common.base.Throwables.propagate(Throwables.java:160)
   at 
 org.apache.cassandra.utils.WrappedRunnable.run(WrappedRunnable.java:32)
   at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown 
 Source)
   at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
   at java.lang.Thread.run(Unknown Source)
 Caused by: java.io.EOFException
   at java.io.DataInputStream.readInt(Unknown Source)
   at 
 org.apache.cassandra.streaming.FileStreamTask.receiveReply(FileStreamTask.java:193)
   at 
 org.apache.cassandra.streaming.compress.CompressedFileStreamTask.stream(CompressedFileStreamTask.java:114)
   at 
 org.apache.cassandra.streaming.FileStreamTask.runMayThrow(FileStreamTask.java:91)
   at 
 

[jira] [Comment Edited] (CASSANDRA-5418) repair freezing

2013-04-05 Thread Igor Ivanov (JIRA)

[ 
https://issues.apache.org/jira/browse/CASSANDRA-5418?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13623692#comment-13623692
 ] 

Igor Ivanov edited comment on CASSANDRA-5418 at 4/5/13 3:05 PM:


Since that I've tried to run offline sstablescrub, it didn't help. As was 
suggested on IRC, I've tried sstable2json on data file and it worked. But when 
joining node tries to stream file - it fails repeatedly on the same file.

  was (Author: radev):
Since that I've tried to run offline sstablescrub, it didn't help. As was 
suggested on IRC, I've tried sstable2json on data file and it worked. But when 
joining node tries to stream file - it fails repeatedly on that file.
  
 repair freezing
 ---

 Key: CASSANDRA-5418
 URL: https://issues.apache.org/jira/browse/CASSANDRA-5418
 Project: Cassandra
  Issue Type: Bug
  Components: Core
Affects Versions: 1.2.2
 Environment: 5 nodes, RackInferring snitch, OpenVZ VMs, Centos 6, 
 Oracle JVM with JNA enabled.
Reporter: Igor Ivanov

 When I run *nodetool repair* on cas01 node it get's stuck at some point.
 I see following exceptions in cas01 system.log:
 {quote}
 ERROR [Streaming to /10.10.45.60:28] 2013-04-02 09:03:55,353 
 CassandraDaemon.java (line 132) Exception in thread Thread[Streaming to 
 /10.10.45.60:28,5,main]
 java.lang.RuntimeException: java.io.EOFException
   at com.google.common.base.Throwables.propagate(Throwables.java:160)
   at 
 org.apache.cassandra.utils.WrappedRunnable.run(WrappedRunnable.java:32)
   at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown 
 Source)
   at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
   at java.lang.Thread.run(Unknown Source)
 Caused by: java.io.EOFException
   at java.io.DataInputStream.readInt(Unknown Source)
   at 
 org.apache.cassandra.streaming.FileStreamTask.receiveReply(FileStreamTask.java:193)
   at 
 org.apache.cassandra.streaming.compress.CompressedFileStreamTask.stream(CompressedFileStreamTask.java:114)
   at 
 org.apache.cassandra.streaming.FileStreamTask.runMayThrow(FileStreamTask.java:91)
   at 
 org.apache.cassandra.utils.WrappedRunnable.run(WrappedRunnable.java:28)
   ... 3 more
 ERROR [Thread-2076] 2013-04-02 09:07:12,261 CassandraDaemon.java (line 132) 
 Exception in thread Thread[Thread-2076,5,main]
 java.lang.AssertionError: incorrect row data size 130921 written to 
 /var/lib/cassandra/data/EDITED/content_list/footballsite-content_list-tmp-ib-3660-Data.db;
  correct is 131074
   at 
 org.apache.cassandra.io.sstable.SSTableWriter.appendFromStream(SSTableWriter.java:285)
   at 
 org.apache.cassandra.streaming.IncomingStreamReader.streamIn(IncomingStreamReader.java:179)
   at 
 org.apache.cassandra.streaming.IncomingStreamReader.read(IncomingStreamReader.java:122)
   at 
 org.apache.cassandra.net.IncomingTcpConnection.stream(IncomingTcpConnection.java:238)
   at 
 org.apache.cassandra.net.IncomingTcpConnection.handleStream(IncomingTcpConnection.java:178)
   at 
 org.apache.cassandra.net.IncomingTcpConnection.run(IncomingTcpConnection.java:78)
 {quote}
 On other machines there are some exceptions too:
 {quote}
 ERROR [Thread-1424] 2013-04-02 09:07:12,248 CassandraDaemon.java (line 132) 
 Exception in thread Thread[Thread-1424,5,main]
 java.lang.AssertionError: incorrect row data size 130921 written to 
 /var/lib/cassandra/data/EDITED/content_list/footballsite-content_list-tmp-ib-2268-Data.db;
  correct is 131074
   at 
 org.apache.cassandra.io.sstable.SSTableWriter.appendFromStream(SSTableWriter.java:285)
   at 
 org.apache.cassandra.streaming.IncomingStreamReader.streamIn(IncomingStreamReader.java:179)
   at 
 org.apache.cassandra.streaming.IncomingStreamReader.read(IncomingStreamReader.java:122)
   at 
 org.apache.cassandra.net.IncomingTcpConnection.stream(IncomingTcpConnection.java:238)
   at 
 org.apache.cassandra.net.IncomingTcpConnection.handleStream(IncomingTcpConnection.java:178)
   at 
 org.apache.cassandra.net.IncomingTcpConnection.run(IncomingTcpConnection.java:78)
 ERROR [Streaming to /10.10.45.58:55] 2013-04-02 09:07:12,263 
 CassandraDaemon.java (line 132) Exception in thread Thread[Streaming to 
 /10.10.45.58:55,5,main]
 java.lang.RuntimeException: java.io.EOFException
   at com.google.common.base.Throwables.propagate(Throwables.java:160)
   at 
 org.apache.cassandra.utils.WrappedRunnable.run(WrappedRunnable.java:32)
   at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown 
 Source)
   at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
   at java.lang.Thread.run(Unknown Source)
 Caused by: java.io.EOFException
   at java.io.DataInputStream.readInt(Unknown Source)
  

[jira] [Updated] (CASSANDRA-5418) repair freezing

2013-04-05 Thread Igor Ivanov (JIRA)

 [ 
https://issues.apache.org/jira/browse/CASSANDRA-5418?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Igor Ivanov updated CASSANDRA-5418:
---

Affects Version/s: 1.2.3

 repair freezing
 ---

 Key: CASSANDRA-5418
 URL: https://issues.apache.org/jira/browse/CASSANDRA-5418
 Project: Cassandra
  Issue Type: Bug
  Components: Core
Affects Versions: 1.2.2, 1.2.3
 Environment: 5 nodes, RackInferring snitch, OpenVZ VMs, Centos 6, 
 Oracle JVM with JNA enabled.
Reporter: Igor Ivanov

 When I run *nodetool repair* on cas01 node it get's stuck at some point.
 I see following exceptions in cas01 system.log:
 {quote}
 ERROR [Streaming to /10.10.45.60:28] 2013-04-02 09:03:55,353 
 CassandraDaemon.java (line 132) Exception in thread Thread[Streaming to 
 /10.10.45.60:28,5,main]
 java.lang.RuntimeException: java.io.EOFException
   at com.google.common.base.Throwables.propagate(Throwables.java:160)
   at 
 org.apache.cassandra.utils.WrappedRunnable.run(WrappedRunnable.java:32)
   at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown 
 Source)
   at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
   at java.lang.Thread.run(Unknown Source)
 Caused by: java.io.EOFException
   at java.io.DataInputStream.readInt(Unknown Source)
   at 
 org.apache.cassandra.streaming.FileStreamTask.receiveReply(FileStreamTask.java:193)
   at 
 org.apache.cassandra.streaming.compress.CompressedFileStreamTask.stream(CompressedFileStreamTask.java:114)
   at 
 org.apache.cassandra.streaming.FileStreamTask.runMayThrow(FileStreamTask.java:91)
   at 
 org.apache.cassandra.utils.WrappedRunnable.run(WrappedRunnable.java:28)
   ... 3 more
 ERROR [Thread-2076] 2013-04-02 09:07:12,261 CassandraDaemon.java (line 132) 
 Exception in thread Thread[Thread-2076,5,main]
 java.lang.AssertionError: incorrect row data size 130921 written to 
 /var/lib/cassandra/data/EDITED/content_list/footballsite-content_list-tmp-ib-3660-Data.db;
  correct is 131074
   at 
 org.apache.cassandra.io.sstable.SSTableWriter.appendFromStream(SSTableWriter.java:285)
   at 
 org.apache.cassandra.streaming.IncomingStreamReader.streamIn(IncomingStreamReader.java:179)
   at 
 org.apache.cassandra.streaming.IncomingStreamReader.read(IncomingStreamReader.java:122)
   at 
 org.apache.cassandra.net.IncomingTcpConnection.stream(IncomingTcpConnection.java:238)
   at 
 org.apache.cassandra.net.IncomingTcpConnection.handleStream(IncomingTcpConnection.java:178)
   at 
 org.apache.cassandra.net.IncomingTcpConnection.run(IncomingTcpConnection.java:78)
 {quote}
 On other machines there are some exceptions too:
 {quote}
 ERROR [Thread-1424] 2013-04-02 09:07:12,248 CassandraDaemon.java (line 132) 
 Exception in thread Thread[Thread-1424,5,main]
 java.lang.AssertionError: incorrect row data size 130921 written to 
 /var/lib/cassandra/data/EDITED/content_list/footballsite-content_list-tmp-ib-2268-Data.db;
  correct is 131074
   at 
 org.apache.cassandra.io.sstable.SSTableWriter.appendFromStream(SSTableWriter.java:285)
   at 
 org.apache.cassandra.streaming.IncomingStreamReader.streamIn(IncomingStreamReader.java:179)
   at 
 org.apache.cassandra.streaming.IncomingStreamReader.read(IncomingStreamReader.java:122)
   at 
 org.apache.cassandra.net.IncomingTcpConnection.stream(IncomingTcpConnection.java:238)
   at 
 org.apache.cassandra.net.IncomingTcpConnection.handleStream(IncomingTcpConnection.java:178)
   at 
 org.apache.cassandra.net.IncomingTcpConnection.run(IncomingTcpConnection.java:78)
 ERROR [Streaming to /10.10.45.58:55] 2013-04-02 09:07:12,263 
 CassandraDaemon.java (line 132) Exception in thread Thread[Streaming to 
 /10.10.45.58:55,5,main]
 java.lang.RuntimeException: java.io.EOFException
   at com.google.common.base.Throwables.propagate(Throwables.java:160)
   at 
 org.apache.cassandra.utils.WrappedRunnable.run(WrappedRunnable.java:32)
   at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown 
 Source)
   at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
   at java.lang.Thread.run(Unknown Source)
 Caused by: java.io.EOFException
   at java.io.DataInputStream.readInt(Unknown Source)
   at 
 org.apache.cassandra.streaming.FileStreamTask.receiveReply(FileStreamTask.java:193)
   at 
 org.apache.cassandra.streaming.compress.CompressedFileStreamTask.stream(CompressedFileStreamTask.java:114)
   at 
 org.apache.cassandra.streaming.FileStreamTask.runMayThrow(FileStreamTask.java:91)
   at 
 org.apache.cassandra.utils.WrappedRunnable.run(WrappedRunnable.java:28)
   ... 3 more
 {quote}
 Then I see frozen status in *nodetool netstats* and repair never completes.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, 

[jira] [Commented] (CASSANDRA-5418) repair freezing

2013-04-05 Thread Igor Ivanov (JIRA)

[ 
https://issues.apache.org/jira/browse/CASSANDRA-5418?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13623696#comment-13623696
 ] 

Igor Ivanov commented on CASSANDRA-5418:


Also, I've tried shutting down one node, moving it's files to another box and 
starting it up with different IP/hostname - node was up and serving properly, 
but problem persisted.

 repair freezing
 ---

 Key: CASSANDRA-5418
 URL: https://issues.apache.org/jira/browse/CASSANDRA-5418
 Project: Cassandra
  Issue Type: Bug
  Components: Core
Affects Versions: 1.2.2, 1.2.3
 Environment: 5 nodes, RackInferring snitch, OpenVZ VMs, Centos 6, 
 Oracle JVM with JNA enabled.
Reporter: Igor Ivanov

 When I run *nodetool repair* on cas01 node it get's stuck at some point.
 I see following exceptions in cas01 system.log:
 {quote}
 ERROR [Streaming to /10.10.45.60:28] 2013-04-02 09:03:55,353 
 CassandraDaemon.java (line 132) Exception in thread Thread[Streaming to 
 /10.10.45.60:28,5,main]
 java.lang.RuntimeException: java.io.EOFException
   at com.google.common.base.Throwables.propagate(Throwables.java:160)
   at 
 org.apache.cassandra.utils.WrappedRunnable.run(WrappedRunnable.java:32)
   at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown 
 Source)
   at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
   at java.lang.Thread.run(Unknown Source)
 Caused by: java.io.EOFException
   at java.io.DataInputStream.readInt(Unknown Source)
   at 
 org.apache.cassandra.streaming.FileStreamTask.receiveReply(FileStreamTask.java:193)
   at 
 org.apache.cassandra.streaming.compress.CompressedFileStreamTask.stream(CompressedFileStreamTask.java:114)
   at 
 org.apache.cassandra.streaming.FileStreamTask.runMayThrow(FileStreamTask.java:91)
   at 
 org.apache.cassandra.utils.WrappedRunnable.run(WrappedRunnable.java:28)
   ... 3 more
 ERROR [Thread-2076] 2013-04-02 09:07:12,261 CassandraDaemon.java (line 132) 
 Exception in thread Thread[Thread-2076,5,main]
 java.lang.AssertionError: incorrect row data size 130921 written to 
 /var/lib/cassandra/data/EDITED/content_list/footballsite-content_list-tmp-ib-3660-Data.db;
  correct is 131074
   at 
 org.apache.cassandra.io.sstable.SSTableWriter.appendFromStream(SSTableWriter.java:285)
   at 
 org.apache.cassandra.streaming.IncomingStreamReader.streamIn(IncomingStreamReader.java:179)
   at 
 org.apache.cassandra.streaming.IncomingStreamReader.read(IncomingStreamReader.java:122)
   at 
 org.apache.cassandra.net.IncomingTcpConnection.stream(IncomingTcpConnection.java:238)
   at 
 org.apache.cassandra.net.IncomingTcpConnection.handleStream(IncomingTcpConnection.java:178)
   at 
 org.apache.cassandra.net.IncomingTcpConnection.run(IncomingTcpConnection.java:78)
 {quote}
 On other machines there are some exceptions too:
 {quote}
 ERROR [Thread-1424] 2013-04-02 09:07:12,248 CassandraDaemon.java (line 132) 
 Exception in thread Thread[Thread-1424,5,main]
 java.lang.AssertionError: incorrect row data size 130921 written to 
 /var/lib/cassandra/data/EDITED/content_list/footballsite-content_list-tmp-ib-2268-Data.db;
  correct is 131074
   at 
 org.apache.cassandra.io.sstable.SSTableWriter.appendFromStream(SSTableWriter.java:285)
   at 
 org.apache.cassandra.streaming.IncomingStreamReader.streamIn(IncomingStreamReader.java:179)
   at 
 org.apache.cassandra.streaming.IncomingStreamReader.read(IncomingStreamReader.java:122)
   at 
 org.apache.cassandra.net.IncomingTcpConnection.stream(IncomingTcpConnection.java:238)
   at 
 org.apache.cassandra.net.IncomingTcpConnection.handleStream(IncomingTcpConnection.java:178)
   at 
 org.apache.cassandra.net.IncomingTcpConnection.run(IncomingTcpConnection.java:78)
 ERROR [Streaming to /10.10.45.58:55] 2013-04-02 09:07:12,263 
 CassandraDaemon.java (line 132) Exception in thread Thread[Streaming to 
 /10.10.45.58:55,5,main]
 java.lang.RuntimeException: java.io.EOFException
   at com.google.common.base.Throwables.propagate(Throwables.java:160)
   at 
 org.apache.cassandra.utils.WrappedRunnable.run(WrappedRunnable.java:32)
   at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown 
 Source)
   at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
   at java.lang.Thread.run(Unknown Source)
 Caused by: java.io.EOFException
   at java.io.DataInputStream.readInt(Unknown Source)
   at 
 org.apache.cassandra.streaming.FileStreamTask.receiveReply(FileStreamTask.java:193)
   at 
 org.apache.cassandra.streaming.compress.CompressedFileStreamTask.stream(CompressedFileStreamTask.java:114)
   at 
 org.apache.cassandra.streaming.FileStreamTask.runMayThrow(FileStreamTask.java:91)
   at 
 

[jira] [Commented] (CASSANDRA-5425) disablebinary nodetool command

2013-04-05 Thread Jeremiah Jordan (JIRA)

[ 
https://issues.apache.org/jira/browse/CASSANDRA-5425?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13623705#comment-13623705
 ] 

Jeremiah Jordan commented on CASSANDRA-5425:


Should we add statusbinary as well?

 disablebinary nodetool command
 --

 Key: CASSANDRA-5425
 URL: https://issues.apache.org/jira/browse/CASSANDRA-5425
 Project: Cassandra
  Issue Type: Bug
  Components: Drivers
Affects Versions: 1.2.3
Reporter: Joaquin Casares
Assignee: Michał Michalski
Priority: Minor
  Labels: datastax_qa
 Fix For: 1.2.4

 Attachments: 5425-v1.txt


 The following commands are available via `nodetool`:
 {CODE}
   disablehandoff - Disable the future hints storing on the current 
 node
   disablegossip  - Disable gossip (effectively marking the node dead)
   disablethrift  - Disable thrift server
 {CODE}
 Is it possible to get disablebinary added to help with the testing of binary 
 client drivers?

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


[jira] [Comment Edited] (CASSANDRA-5425) disablebinary nodetool command

2013-04-05 Thread Jeremiah Jordan (JIRA)

[ 
https://issues.apache.org/jira/browse/CASSANDRA-5425?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13623705#comment-13623705
 ] 

Jeremiah Jordan edited comment on CASSANDRA-5425 at 4/5/13 3:23 PM:


Should we add statusbinary as well?  Like we have statusthrift?

  was (Author: jjordan):
Should we add statusbinary as well?
  
 disablebinary nodetool command
 --

 Key: CASSANDRA-5425
 URL: https://issues.apache.org/jira/browse/CASSANDRA-5425
 Project: Cassandra
  Issue Type: Bug
  Components: Drivers
Affects Versions: 1.2.3
Reporter: Joaquin Casares
Assignee: Michał Michalski
Priority: Minor
  Labels: datastax_qa
 Fix For: 1.2.4

 Attachments: 5425-v1.txt


 The following commands are available via `nodetool`:
 {CODE}
   disablehandoff - Disable the future hints storing on the current 
 node
   disablegossip  - Disable gossip (effectively marking the node dead)
   disablethrift  - Disable thrift server
 {CODE}
 Is it possible to get disablebinary added to help with the testing of binary 
 client drivers?

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


[jira] [Created] (CASSANDRA-5429) Update scrub and scrubtest for single-pass compaction format

2013-04-05 Thread Jonathan Ellis (JIRA)
Jonathan Ellis created CASSANDRA-5429:
-

 Summary: Update scrub and scrubtest for single-pass compaction 
format
 Key: CASSANDRA-5429
 URL: https://issues.apache.org/jira/browse/CASSANDRA-5429
 Project: Cassandra
  Issue Type: Bug
  Components: Core
Affects Versions: 2.0
Reporter: Jonathan Ellis
Assignee: Jason Brown
 Fix For: 2.0




--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


[jira] [Commented] (CASSANDRA-4180) Single-pass compaction for LCR

2013-04-05 Thread Jonathan Ellis (JIRA)

[ 
https://issues.apache.org/jira/browse/CASSANDRA-4180?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13623725#comment-13623725
 ] 

Jonathan Ellis commented on CASSANDRA-4180:
---

Broke out scrub into CASSANDRA-5429 so we can review this separately.

 Single-pass compaction for LCR
 --

 Key: CASSANDRA-4180
 URL: https://issues.apache.org/jira/browse/CASSANDRA-4180
 Project: Cassandra
  Issue Type: Improvement
  Components: Core
Reporter: Sylvain Lebresne
Assignee: Jonathan Ellis
  Labels: compaction
 Fix For: 2.0

 Attachments: scrub-error.txt


 LazilyCompactedRow reads all data twice to compact a row which is obviously 
 inefficient. The main reason we do that is to compute the row header. 
 However, CASSANDRA-2319 have removed the main part of that row header. What 
 remains is the size in bytes and the number of columns, but it should be 
 relatively simple to remove those, which would then remove the need for the 
 two-phase compaction.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


[jira] [Commented] (CASSANDRA-5400) Allow multiple ports to gossip from a single IP address

2013-04-05 Thread Sylvain Lebresne (JIRA)

[ 
https://issues.apache.org/jira/browse/CASSANDRA-5400?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13623734#comment-13623734
 ] 

Sylvain Lebresne commented on CASSANDRA-5400:
-

bq. To be fair, it only means that you can't run your cluster in multi-port 
mode until you've upgraded your client.

True, I meant by that, if we're not careful with the existing thrift and JMX 
calls. As you said, being careful implies a bunch of largely redundant new 
thrift/JMX methods. Definitively possible, but slightly messy, which decreases 
a bit more to me the appeal of this ticket :).

 Allow multiple ports to gossip from a single IP address
 ---

 Key: CASSANDRA-5400
 URL: https://issues.apache.org/jira/browse/CASSANDRA-5400
 Project: Cassandra
  Issue Type: New Feature
Affects Versions: 2.0
Reporter: Carl Yeksigian
Assignee: Carl Yeksigian
 Fix For: 2.0

 Attachments: 5400.txt, 5400-v2.txt, 5400-v3.patch, 5400-v4.patch


 If a fat client is running on the same machine as a Cassandra node, the fat 
 client must be allocated a new IP address. However, since the node is now a 
 part of the gossip, the other nodes in the ring must be able to talk to it. 
 This means that a local only address (127.0.0.n) won't actually work for the 
 rest of the ring.
 This also would allow for multiple Cassandra service instances to run on a 
 single machine, or from a group of machines behind a NAT.
 The change is simple in concept: instead of using an InetAddress, use a 
 different class. Instead of using an InetSocketAddress, which would still tie 
 us to using InetAddress, I've added a new class, CassandraInstanceEndpoint. 
 The serializer allows for reading a serialized Inet4Address or Inet6Address; 
 also, the message service can still communicate with 
 non-CassandraInstanceEndpoint aware code.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


[jira] [Commented] (CASSANDRA-5388) Windows unit tests fail due to ant/junit problem

2013-04-05 Thread Jonathan Ellis (JIRA)

[ 
https://issues.apache.org/jira/browse/CASSANDRA-5388?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13623735#comment-13623735
 ] 

Jonathan Ellis commented on CASSANDRA-5388:
---

I wonder if this could be related to pulling a second copy of ant down to 
build/lib/jars.  Maybe try manually removing build/lib/jars/ant-1.6.5.jar and 
run ant test -Dwithout.maven ?

 Windows unit tests fail due to ant/junit problem
 

 Key: CASSANDRA-5388
 URL: https://issues.apache.org/jira/browse/CASSANDRA-5388
 Project: Cassandra
  Issue Type: Bug
Affects Versions: 2.0
 Environment: Windows 7
 java 1.7.0_17
 ant 1.9.0
Reporter: Ryan McGuire

 Intermittently, but more often than not I get the following error when 
 running 'ant test' on Windows 7:
 {code}
 BUILD FAILED
 c:\Users\Ryan\git\cassandra3\build.xml:1121: The following error occurred 
 while executing this line:
 c:\Users\Ryan\git\cassandra3\build.xml:1064: Using loader 
 AntClassLoader[C:\Program 
 Files\Java\apache-ant-1.9.0\lib\ant-launcher.jar;c:\Program 
 Files\Java\apache-ant-1.9.0\lib\ant.jar;c:\Program 
 Files\Java\apache-ant-1.9.0\lib\ant-junit.jar;c:\Program 
 

git commit: Support pluggable internode authentication

2013-04-05 Thread aleksey
Updated Branches:
  refs/heads/cassandra-1.1 d4744e178 - 4a010ed91


Support pluggable internode authentication

patch by Aleksey Yeschenko; reviewed by Brandon Williams for
CASSANDRA-5401


Project: http://git-wip-us.apache.org/repos/asf/cassandra/repo
Commit: http://git-wip-us.apache.org/repos/asf/cassandra/commit/4a010ed9
Tree: http://git-wip-us.apache.org/repos/asf/cassandra/tree/4a010ed9
Diff: http://git-wip-us.apache.org/repos/asf/cassandra/diff/4a010ed9

Branch: refs/heads/cassandra-1.1
Commit: 4a010ed912711d7b8da16d248f32703ec001e4a2
Parents: d4744e1
Author: Aleksey Yeschenko alek...@apache.org
Authored: Fri Apr 5 19:13:33 2013 +0300
Committer: Aleksey Yeschenko alek...@apache.org
Committed: Fri Apr 5 19:13:33 2013 +0300

--
 CHANGES.txt|1 +
 NEWS.txt   |   13 
 conf/cassandra.yaml|4 +
 .../auth/AllowAllInternodeAuthenticator.java   |   36 
 .../cassandra/auth/IInternodeAuthenticator.java|   44 +++
 src/java/org/apache/cassandra/config/Config.java   |1 +
 .../cassandra/config/DatabaseDescriptor.java   |   14 +
 .../org/apache/cassandra/net/MessagingService.java |   10 +++-
 8 files changed, 122 insertions(+), 1 deletions(-)
--


http://git-wip-us.apache.org/repos/asf/cassandra/blob/4a010ed9/CHANGES.txt
--
diff --git a/CHANGES.txt b/CHANGES.txt
index d82bb74..fa407b5 100644
--- a/CHANGES.txt
+++ b/CHANGES.txt
@@ -12,6 +12,7 @@
  * cli: Quote ks and cf names in schema output when needed (CASSANDRA-5052)
  * Fix bad default for min/max timestamp in SSTableMetadata (CASSANDRA-5372)
  * Fix cf name extraction from manifest in Directories.migrateFile() 
(CASSANDRA-5242)
+ * Support pluggable internode authentication (CASSANDRA-5401)
 
 
 1.1.10

http://git-wip-us.apache.org/repos/asf/cassandra/blob/4a010ed9/NEWS.txt
--
diff --git a/NEWS.txt b/NEWS.txt
index b8954d4..f3511b7 100644
--- a/NEWS.txt
+++ b/NEWS.txt
@@ -8,6 +8,19 @@ upgrade, just in case you need to roll back to the previous 
version.
 (Cassandra version X + 1 will always be able to read data files created
 by version X, but the inverse is not necessarily the case.)
 
+1.1.11
+==
+
+Upgrading
+-
+- Nothing specific to this release, but please see the previous 
instructions
+  if you are not upgrading from 1.1.10.
+
+Features
+
+- Pluggable internode authentication.
+  See `internode_authenticator` setting in cassandra.yaml.
+
 1.1.10
 ==
 

http://git-wip-us.apache.org/repos/asf/cassandra/blob/4a010ed9/conf/cassandra.yaml
--
diff --git a/conf/cassandra.yaml b/conf/cassandra.yaml
index aa4db1c..37f41fb 100644
--- a/conf/cassandra.yaml
+++ b/conf/cassandra.yaml
@@ -275,6 +275,10 @@ listen_address: localhost
 # Leaving this blank will set it to the same value as listen_address
 # broadcast_address: 1.2.3.4
 
+# Internode authentication backend, implementing IInternodeAuthenticator;
+# used to allow/disallow connections from peer nodes.
+# internode_authenticator: 
org.apache.cassandra.auth.AllowAllInternodeAuthenticator
+
 # The address to bind the Thrift RPC service to -- clients connect
 # here. Unlike ListenAddress above, you *can* specify 0.0.0.0 here if
 # you want Thrift to listen on all interfaces.

http://git-wip-us.apache.org/repos/asf/cassandra/blob/4a010ed9/src/java/org/apache/cassandra/auth/AllowAllInternodeAuthenticator.java
--
diff --git 
a/src/java/org/apache/cassandra/auth/AllowAllInternodeAuthenticator.java 
b/src/java/org/apache/cassandra/auth/AllowAllInternodeAuthenticator.java
new file mode 100644
index 000..910ed85
--- /dev/null
+++ b/src/java/org/apache/cassandra/auth/AllowAllInternodeAuthenticator.java
@@ -0,0 +1,36 @@
+/*
+ * Licensed to the Apache Software Foundation (ASF) under one
+ * or more contributor license agreements.  See the NOTICE file
+ * distributed with this work for additional information
+ * regarding copyright ownership.  The ASF licenses this file
+ * to you under the Apache License, Version 2.0 (the
+ * License); you may not use this file except in compliance
+ *  with the License.  You may obtain a copy of the License at
+ *
+ *   http://www.apache.org/licenses/LICENSE-2.0
+ *
+ * Unless required by applicable law or agreed to in writing,
+ * software distributed under the License is distributed on an
+ * AS IS BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+ * KIND, either express or implied.  See the License for the
+ * specific language governing permissions and limitations
+ * under the 

[jira] [Commented] (CASSANDRA-4775) Counters 2.0

2013-04-05 Thread Nicolas Favre-Felix (JIRA)

[ 
https://issues.apache.org/jira/browse/CASSANDRA-4775?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13623757#comment-13623757
 ] 

Nicolas Favre-Felix commented on CASSANDRA-4775:


I would like to describe a design that was discussed at Acunu last year, aiming 
to resolve the problems pointed out by Sylvain as well as remove the read 
operation needed by replicate_on_write.

Our solution added a unique identifier per counter update operation, used to 
identify duplicate commands and avoid overcounts on retry. The main problem in 
storing (UUID, delta) pairs per counter is the O(N) read complexity; this is 
how people implemented counters before 0.8 and it is a pretty inefficient way 
of counting things.

Our idea was to merge those update pairs in the back-end, trying to always keep 
a small number of deltas instead of all of them. Merging those updates requires 
some level of synchronisation between the replicas, but that's not something 
that Cassandra is completely adverse to as active anty-entropy also requires 
all replicas to be available.
This design considered using a tree per counter, with time-based buckets 
containing all increments to the counter for a given time period - say, 5 
seconds by default. Once this time has passed, the bucket for the past 5 
seconds is queued for synchronization amongst all replicas and eventually 
replaced with an equivalent bucket containing a single increment with a UUID 
built from all the updates that it replaces (using XOR would work). If the 
replicas disagree on what needs to be in the bucket, they send each other 
missed updates in the same way that data is exchanged during repair. If a node 
is down, we keep accumulating 5-second buckets that will need to be merged 
later.
The 5-second buckets are eventually merged into a minute bucket, then an hour 
bucket, etc.

As an added bonus, the reduce function can be set to MIN, MAX, SUM_SQ, etc. 
instead of just SUM.

Here are the main drawbacks I see for this approach:

* The implementation becomes a fair bit more complicated.
* Counters take more space that they used to.
* The replicas need to all be up for the collapsing operation to run. It 
might just be that counters start to get slower if some of your nodes are down 
for a long time. You can't merge updates with a replica down or you might lose 
increments.
* We introduce an actual timestamp instead of the current binary blob.
* The implementation is not compatible with the current one.
* The performance characteristics of these counters are unknown.
* No code exists.


 Counters 2.0
 

 Key: CASSANDRA-4775
 URL: https://issues.apache.org/jira/browse/CASSANDRA-4775
 Project: Cassandra
  Issue Type: New Feature
  Components: Core
Reporter: Arya Goudarzi
Assignee: Aleksey Yeschenko
  Labels: counters
 Fix For: 2.0


 The existing partitioned counters remain a source of frustration for most 
 users almost two years after being introduced.  The remaining problems are 
 inherent in the design, not something that can be fixed given enough 
 time/eyeballs.
 Ideally a solution would give us
 - similar performance
 - less special cases in the code
 - potential for a retry mechanism

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


[1/2] git commit: Support pluggable internode authentication

2013-04-05 Thread aleksey
Updated Branches:
  refs/heads/cassandra-1.2 1533f124c - 7039168e0


Support pluggable internode authentication

patch by Aleksey Yeschenko; reviewed by Brandon Williams for
CASSANDRA-5401


Project: http://git-wip-us.apache.org/repos/asf/cassandra/repo
Commit: http://git-wip-us.apache.org/repos/asf/cassandra/commit/4a010ed9
Tree: http://git-wip-us.apache.org/repos/asf/cassandra/tree/4a010ed9
Diff: http://git-wip-us.apache.org/repos/asf/cassandra/diff/4a010ed9

Branch: refs/heads/cassandra-1.2
Commit: 4a010ed912711d7b8da16d248f32703ec001e4a2
Parents: d4744e1
Author: Aleksey Yeschenko alek...@apache.org
Authored: Fri Apr 5 19:13:33 2013 +0300
Committer: Aleksey Yeschenko alek...@apache.org
Committed: Fri Apr 5 19:13:33 2013 +0300

--
 CHANGES.txt|1 +
 NEWS.txt   |   13 
 conf/cassandra.yaml|4 +
 .../auth/AllowAllInternodeAuthenticator.java   |   36 
 .../cassandra/auth/IInternodeAuthenticator.java|   44 +++
 src/java/org/apache/cassandra/config/Config.java   |1 +
 .../cassandra/config/DatabaseDescriptor.java   |   14 +
 .../org/apache/cassandra/net/MessagingService.java |   10 +++-
 8 files changed, 122 insertions(+), 1 deletions(-)
--


http://git-wip-us.apache.org/repos/asf/cassandra/blob/4a010ed9/CHANGES.txt
--
diff --git a/CHANGES.txt b/CHANGES.txt
index d82bb74..fa407b5 100644
--- a/CHANGES.txt
+++ b/CHANGES.txt
@@ -12,6 +12,7 @@
  * cli: Quote ks and cf names in schema output when needed (CASSANDRA-5052)
  * Fix bad default for min/max timestamp in SSTableMetadata (CASSANDRA-5372)
  * Fix cf name extraction from manifest in Directories.migrateFile() 
(CASSANDRA-5242)
+ * Support pluggable internode authentication (CASSANDRA-5401)
 
 
 1.1.10

http://git-wip-us.apache.org/repos/asf/cassandra/blob/4a010ed9/NEWS.txt
--
diff --git a/NEWS.txt b/NEWS.txt
index b8954d4..f3511b7 100644
--- a/NEWS.txt
+++ b/NEWS.txt
@@ -8,6 +8,19 @@ upgrade, just in case you need to roll back to the previous 
version.
 (Cassandra version X + 1 will always be able to read data files created
 by version X, but the inverse is not necessarily the case.)
 
+1.1.11
+==
+
+Upgrading
+-
+- Nothing specific to this release, but please see the previous 
instructions
+  if you are not upgrading from 1.1.10.
+
+Features
+
+- Pluggable internode authentication.
+  See `internode_authenticator` setting in cassandra.yaml.
+
 1.1.10
 ==
 

http://git-wip-us.apache.org/repos/asf/cassandra/blob/4a010ed9/conf/cassandra.yaml
--
diff --git a/conf/cassandra.yaml b/conf/cassandra.yaml
index aa4db1c..37f41fb 100644
--- a/conf/cassandra.yaml
+++ b/conf/cassandra.yaml
@@ -275,6 +275,10 @@ listen_address: localhost
 # Leaving this blank will set it to the same value as listen_address
 # broadcast_address: 1.2.3.4
 
+# Internode authentication backend, implementing IInternodeAuthenticator;
+# used to allow/disallow connections from peer nodes.
+# internode_authenticator: 
org.apache.cassandra.auth.AllowAllInternodeAuthenticator
+
 # The address to bind the Thrift RPC service to -- clients connect
 # here. Unlike ListenAddress above, you *can* specify 0.0.0.0 here if
 # you want Thrift to listen on all interfaces.

http://git-wip-us.apache.org/repos/asf/cassandra/blob/4a010ed9/src/java/org/apache/cassandra/auth/AllowAllInternodeAuthenticator.java
--
diff --git 
a/src/java/org/apache/cassandra/auth/AllowAllInternodeAuthenticator.java 
b/src/java/org/apache/cassandra/auth/AllowAllInternodeAuthenticator.java
new file mode 100644
index 000..910ed85
--- /dev/null
+++ b/src/java/org/apache/cassandra/auth/AllowAllInternodeAuthenticator.java
@@ -0,0 +1,36 @@
+/*
+ * Licensed to the Apache Software Foundation (ASF) under one
+ * or more contributor license agreements.  See the NOTICE file
+ * distributed with this work for additional information
+ * regarding copyright ownership.  The ASF licenses this file
+ * to you under the Apache License, Version 2.0 (the
+ * License); you may not use this file except in compliance
+ *  with the License.  You may obtain a copy of the License at
+ *
+ *   http://www.apache.org/licenses/LICENSE-2.0
+ *
+ * Unless required by applicable law or agreed to in writing,
+ * software distributed under the License is distributed on an
+ * AS IS BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+ * KIND, either express or implied.  See the License for the
+ * specific language governing permissions and limitations
+ * under the 

[2/2] git commit: Merge branch 'cassandra-1.1' into cassandra-1.2

2013-04-05 Thread aleksey
Merge branch 'cassandra-1.1' into cassandra-1.2

Conflicts:
CHANGES.txt
NEWS.txt
conf/cassandra.yaml
src/java/org/apache/cassandra/config/DatabaseDescriptor.java


Project: http://git-wip-us.apache.org/repos/asf/cassandra/repo
Commit: http://git-wip-us.apache.org/repos/asf/cassandra/commit/7039168e
Tree: http://git-wip-us.apache.org/repos/asf/cassandra/tree/7039168e
Diff: http://git-wip-us.apache.org/repos/asf/cassandra/diff/7039168e

Branch: refs/heads/cassandra-1.2
Commit: 7039168e0a32dd14416c25fd11e64af49123
Parents: 1533f12 4a010ed
Author: Aleksey Yeschenko alek...@apache.org
Authored: Fri Apr 5 19:36:41 2013 +0300
Committer: Aleksey Yeschenko alek...@apache.org
Committed: Fri Apr 5 19:36:41 2013 +0300

--
 CHANGES.txt|1 +
 conf/cassandra.yaml|5 +-
 .../auth/AllowAllInternodeAuthenticator.java   |   36 
 .../cassandra/auth/IInternodeAuthenticator.java|   44 +++
 src/java/org/apache/cassandra/config/Config.java   |1 +
 .../cassandra/config/DatabaseDescriptor.java   |   13 
 .../org/apache/cassandra/net/MessagingService.java |   10 +++-
 7 files changed, 108 insertions(+), 2 deletions(-)
--


http://git-wip-us.apache.org/repos/asf/cassandra/blob/7039168e/CHANGES.txt
--
diff --cc CHANGES.txt
index 8bcde57,fa407b5..12f38b6
--- a/CHANGES.txt
+++ b/CHANGES.txt
@@@ -1,66 -1,4 +1,67 @@@
 -1.1.11
 +1.2.4
 + * Ensure that PerRowSecondaryIndex updates see the most recent values
 +   (CASSANDRA-5397)
 + * avoid duplicate index entries ind PrecompactedRow and 
 +   ParallelCompactionIterable (CASSANDRA-5395)
 + * remove the index entry on oldColumn when new column is a tombstone 
 +   (CASSANDRA-5395)
 + * Change default stream throughput from 400 to 200 mbps (CASSANDRA-5036)
 + * Gossiper logs DOWN for symmetry with UP (CASSANDRA-5187)
 + * Fix mixing prepared statements between keyspaces (CASSANDRA-5352)
 + * Fix consistency level during bootstrap - strike 3 (CASSANDRA-5354)
 + * Fix transposed arguments in AlreadyExistsException (CASSANDRA-5362)
 + * Improve asynchronous hint delivery (CASSANDRA-5179)
 + * Fix Guava dependency version (12.0 - 13.0.1) for Maven (CASSANDRA-5364)
 + * Validate that provided CQL3 collection value are  64K (CASSANDRA-5355)
 + * Make upgradeSSTable skip current version sstables by default 
(CASSANDRA-5366)
 + * Optimize min/max timestamp collection (CASSANDRA-5373)
 + * Invalid streamId in cql binary protocol when using invalid CL 
 +   (CASSANDRA-5164)
 + * Fix validation for IN where clauses with collections (CASSANDRA-5376)
 + * Copy resultSet on count query to avoid ConcurrentModificationException 
 +   (CASSANDRA-5382)
 + * Correctly typecheck in CQL3 even with ReversedType (CASSANDRA-5386)
 + * Fix streaming compressed files when using encryption (CASSANDRA-5391)
 + * cassandra-all 1.2.0 pom missing netty dependency (CASSANDRA-5392)
 + * Fix writetime/ttl functions on null values (CASSANDRA-5341)
 + * Fix NPE during cql3 select with token() (CASSANDRA-5404)
 + * IndexHelper.skipBloomFilters won't skip non-SHA filters (CASSANDRA-5385)
 + * cqlsh: Print maps ordered by key, sort sets (CASSANDRA-5413)
 + * Add null syntax support in CQL3 for inserts (CASSANDRA-3783)
 + * Allow unauthenticated set_keyspace() calls (CASSANDRA-5423)
 + * Fix potential incremental backups race (CASSANDRA-5410)
 +Merged from 1.1:
 + * cli: Quote ks and cf names in schema output when needed (CASSANDRA-5052)
 + * Fix bad default for min/max timestamp in SSTableMetadata (CASSANDRA-5372)
 + * Fix cf name extraction from manifest in Directories.migrateFile() 
 +   (CASSANDRA-5242)
++ * Support pluggable internode authentication (CASSANDRA-5401)
 +
 +
 +1.2.3
 + * add check for sstable overlap within a level on startup (CASSANDRA-5327)
 + * replace ipv6 colons in jmx object names (CASSANDRA-5298, 5328)
 + * Avoid allocating SSTableBoundedScanner during repair when the range does 
 +   not intersect the sstable (CASSANDRA-5249)
 + * Don't lowercase property map keys (this breaks NTS) (CASSANDRA-5292)
 + * Fix composite comparator with super columns (CASSANDRA-5287)
 + * Fix insufficient validation of UPDATE queries against counter cfs
 +   (CASSANDRA-5300)
 + * Fix PropertyFileSnitch default DC/Rack behavior (CASSANDRA-5285)
 + * Handle null values when executing prepared statement (CASSANDRA-5081)
 + * Add netty to pom dependencies (CASSANDRA-5181)
 + * Include type arguments in Thrift CQLPreparedResult (CASSANDRA-5311)
 + * Fix compaction not removing columns when bf_fp_ratio is 1 (CASSANDRA-5182)
 + * cli: Warn about missing CQL3 tables in schema descriptions (CASSANDRA-5309)
 + * Re-enable unknown option in replication/compaction strategies option 

[1/3] git commit: Support pluggable internode authentication

2013-04-05 Thread aleksey
Updated Branches:
  refs/heads/trunk 0f479eb0f - 3d0eb6231


Support pluggable internode authentication

patch by Aleksey Yeschenko; reviewed by Brandon Williams for
CASSANDRA-5401


Project: http://git-wip-us.apache.org/repos/asf/cassandra/repo
Commit: http://git-wip-us.apache.org/repos/asf/cassandra/commit/4a010ed9
Tree: http://git-wip-us.apache.org/repos/asf/cassandra/tree/4a010ed9
Diff: http://git-wip-us.apache.org/repos/asf/cassandra/diff/4a010ed9

Branch: refs/heads/trunk
Commit: 4a010ed912711d7b8da16d248f32703ec001e4a2
Parents: d4744e1
Author: Aleksey Yeschenko alek...@apache.org
Authored: Fri Apr 5 19:13:33 2013 +0300
Committer: Aleksey Yeschenko alek...@apache.org
Committed: Fri Apr 5 19:13:33 2013 +0300

--
 CHANGES.txt|1 +
 NEWS.txt   |   13 
 conf/cassandra.yaml|4 +
 .../auth/AllowAllInternodeAuthenticator.java   |   36 
 .../cassandra/auth/IInternodeAuthenticator.java|   44 +++
 src/java/org/apache/cassandra/config/Config.java   |1 +
 .../cassandra/config/DatabaseDescriptor.java   |   14 +
 .../org/apache/cassandra/net/MessagingService.java |   10 +++-
 8 files changed, 122 insertions(+), 1 deletions(-)
--


http://git-wip-us.apache.org/repos/asf/cassandra/blob/4a010ed9/CHANGES.txt
--
diff --git a/CHANGES.txt b/CHANGES.txt
index d82bb74..fa407b5 100644
--- a/CHANGES.txt
+++ b/CHANGES.txt
@@ -12,6 +12,7 @@
  * cli: Quote ks and cf names in schema output when needed (CASSANDRA-5052)
  * Fix bad default for min/max timestamp in SSTableMetadata (CASSANDRA-5372)
  * Fix cf name extraction from manifest in Directories.migrateFile() 
(CASSANDRA-5242)
+ * Support pluggable internode authentication (CASSANDRA-5401)
 
 
 1.1.10

http://git-wip-us.apache.org/repos/asf/cassandra/blob/4a010ed9/NEWS.txt
--
diff --git a/NEWS.txt b/NEWS.txt
index b8954d4..f3511b7 100644
--- a/NEWS.txt
+++ b/NEWS.txt
@@ -8,6 +8,19 @@ upgrade, just in case you need to roll back to the previous 
version.
 (Cassandra version X + 1 will always be able to read data files created
 by version X, but the inverse is not necessarily the case.)
 
+1.1.11
+==
+
+Upgrading
+-
+- Nothing specific to this release, but please see the previous 
instructions
+  if you are not upgrading from 1.1.10.
+
+Features
+
+- Pluggable internode authentication.
+  See `internode_authenticator` setting in cassandra.yaml.
+
 1.1.10
 ==
 

http://git-wip-us.apache.org/repos/asf/cassandra/blob/4a010ed9/conf/cassandra.yaml
--
diff --git a/conf/cassandra.yaml b/conf/cassandra.yaml
index aa4db1c..37f41fb 100644
--- a/conf/cassandra.yaml
+++ b/conf/cassandra.yaml
@@ -275,6 +275,10 @@ listen_address: localhost
 # Leaving this blank will set it to the same value as listen_address
 # broadcast_address: 1.2.3.4
 
+# Internode authentication backend, implementing IInternodeAuthenticator;
+# used to allow/disallow connections from peer nodes.
+# internode_authenticator: 
org.apache.cassandra.auth.AllowAllInternodeAuthenticator
+
 # The address to bind the Thrift RPC service to -- clients connect
 # here. Unlike ListenAddress above, you *can* specify 0.0.0.0 here if
 # you want Thrift to listen on all interfaces.

http://git-wip-us.apache.org/repos/asf/cassandra/blob/4a010ed9/src/java/org/apache/cassandra/auth/AllowAllInternodeAuthenticator.java
--
diff --git 
a/src/java/org/apache/cassandra/auth/AllowAllInternodeAuthenticator.java 
b/src/java/org/apache/cassandra/auth/AllowAllInternodeAuthenticator.java
new file mode 100644
index 000..910ed85
--- /dev/null
+++ b/src/java/org/apache/cassandra/auth/AllowAllInternodeAuthenticator.java
@@ -0,0 +1,36 @@
+/*
+ * Licensed to the Apache Software Foundation (ASF) under one
+ * or more contributor license agreements.  See the NOTICE file
+ * distributed with this work for additional information
+ * regarding copyright ownership.  The ASF licenses this file
+ * to you under the Apache License, Version 2.0 (the
+ * License); you may not use this file except in compliance
+ *  with the License.  You may obtain a copy of the License at
+ *
+ *   http://www.apache.org/licenses/LICENSE-2.0
+ *
+ * Unless required by applicable law or agreed to in writing,
+ * software distributed under the License is distributed on an
+ * AS IS BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+ * KIND, either express or implied.  See the License for the
+ * specific language governing permissions and limitations
+ * under the License.
+ */
+

[2/3] git commit: Merge branch 'cassandra-1.1' into cassandra-1.2

2013-04-05 Thread aleksey
Merge branch 'cassandra-1.1' into cassandra-1.2

Conflicts:
CHANGES.txt
NEWS.txt
conf/cassandra.yaml
src/java/org/apache/cassandra/config/DatabaseDescriptor.java


Project: http://git-wip-us.apache.org/repos/asf/cassandra/repo
Commit: http://git-wip-us.apache.org/repos/asf/cassandra/commit/7039168e
Tree: http://git-wip-us.apache.org/repos/asf/cassandra/tree/7039168e
Diff: http://git-wip-us.apache.org/repos/asf/cassandra/diff/7039168e

Branch: refs/heads/trunk
Commit: 7039168e0a32dd14416c25fd11e64af49123
Parents: 1533f12 4a010ed
Author: Aleksey Yeschenko alek...@apache.org
Authored: Fri Apr 5 19:36:41 2013 +0300
Committer: Aleksey Yeschenko alek...@apache.org
Committed: Fri Apr 5 19:36:41 2013 +0300

--
 CHANGES.txt|1 +
 conf/cassandra.yaml|5 +-
 .../auth/AllowAllInternodeAuthenticator.java   |   36 
 .../cassandra/auth/IInternodeAuthenticator.java|   44 +++
 src/java/org/apache/cassandra/config/Config.java   |1 +
 .../cassandra/config/DatabaseDescriptor.java   |   13 
 .../org/apache/cassandra/net/MessagingService.java |   10 +++-
 7 files changed, 108 insertions(+), 2 deletions(-)
--


http://git-wip-us.apache.org/repos/asf/cassandra/blob/7039168e/CHANGES.txt
--
diff --cc CHANGES.txt
index 8bcde57,fa407b5..12f38b6
--- a/CHANGES.txt
+++ b/CHANGES.txt
@@@ -1,66 -1,4 +1,67 @@@
 -1.1.11
 +1.2.4
 + * Ensure that PerRowSecondaryIndex updates see the most recent values
 +   (CASSANDRA-5397)
 + * avoid duplicate index entries ind PrecompactedRow and 
 +   ParallelCompactionIterable (CASSANDRA-5395)
 + * remove the index entry on oldColumn when new column is a tombstone 
 +   (CASSANDRA-5395)
 + * Change default stream throughput from 400 to 200 mbps (CASSANDRA-5036)
 + * Gossiper logs DOWN for symmetry with UP (CASSANDRA-5187)
 + * Fix mixing prepared statements between keyspaces (CASSANDRA-5352)
 + * Fix consistency level during bootstrap - strike 3 (CASSANDRA-5354)
 + * Fix transposed arguments in AlreadyExistsException (CASSANDRA-5362)
 + * Improve asynchronous hint delivery (CASSANDRA-5179)
 + * Fix Guava dependency version (12.0 - 13.0.1) for Maven (CASSANDRA-5364)
 + * Validate that provided CQL3 collection value are  64K (CASSANDRA-5355)
 + * Make upgradeSSTable skip current version sstables by default 
(CASSANDRA-5366)
 + * Optimize min/max timestamp collection (CASSANDRA-5373)
 + * Invalid streamId in cql binary protocol when using invalid CL 
 +   (CASSANDRA-5164)
 + * Fix validation for IN where clauses with collections (CASSANDRA-5376)
 + * Copy resultSet on count query to avoid ConcurrentModificationException 
 +   (CASSANDRA-5382)
 + * Correctly typecheck in CQL3 even with ReversedType (CASSANDRA-5386)
 + * Fix streaming compressed files when using encryption (CASSANDRA-5391)
 + * cassandra-all 1.2.0 pom missing netty dependency (CASSANDRA-5392)
 + * Fix writetime/ttl functions on null values (CASSANDRA-5341)
 + * Fix NPE during cql3 select with token() (CASSANDRA-5404)
 + * IndexHelper.skipBloomFilters won't skip non-SHA filters (CASSANDRA-5385)
 + * cqlsh: Print maps ordered by key, sort sets (CASSANDRA-5413)
 + * Add null syntax support in CQL3 for inserts (CASSANDRA-3783)
 + * Allow unauthenticated set_keyspace() calls (CASSANDRA-5423)
 + * Fix potential incremental backups race (CASSANDRA-5410)
 +Merged from 1.1:
 + * cli: Quote ks and cf names in schema output when needed (CASSANDRA-5052)
 + * Fix bad default for min/max timestamp in SSTableMetadata (CASSANDRA-5372)
 + * Fix cf name extraction from manifest in Directories.migrateFile() 
 +   (CASSANDRA-5242)
++ * Support pluggable internode authentication (CASSANDRA-5401)
 +
 +
 +1.2.3
 + * add check for sstable overlap within a level on startup (CASSANDRA-5327)
 + * replace ipv6 colons in jmx object names (CASSANDRA-5298, 5328)
 + * Avoid allocating SSTableBoundedScanner during repair when the range does 
 +   not intersect the sstable (CASSANDRA-5249)
 + * Don't lowercase property map keys (this breaks NTS) (CASSANDRA-5292)
 + * Fix composite comparator with super columns (CASSANDRA-5287)
 + * Fix insufficient validation of UPDATE queries against counter cfs
 +   (CASSANDRA-5300)
 + * Fix PropertyFileSnitch default DC/Rack behavior (CASSANDRA-5285)
 + * Handle null values when executing prepared statement (CASSANDRA-5081)
 + * Add netty to pom dependencies (CASSANDRA-5181)
 + * Include type arguments in Thrift CQLPreparedResult (CASSANDRA-5311)
 + * Fix compaction not removing columns when bf_fp_ratio is 1 (CASSANDRA-5182)
 + * cli: Warn about missing CQL3 tables in schema descriptions (CASSANDRA-5309)
 + * Re-enable unknown option in replication/compaction strategies option for
 +   

[3/3] git commit: Merge branch 'cassandra-1.2' into trunk

2013-04-05 Thread aleksey
Merge branch 'cassandra-1.2' into trunk

Conflicts:
src/java/org/apache/cassandra/config/DatabaseDescriptor.java


Project: http://git-wip-us.apache.org/repos/asf/cassandra/repo
Commit: http://git-wip-us.apache.org/repos/asf/cassandra/commit/3d0eb623
Tree: http://git-wip-us.apache.org/repos/asf/cassandra/tree/3d0eb623
Diff: http://git-wip-us.apache.org/repos/asf/cassandra/diff/3d0eb623

Branch: refs/heads/trunk
Commit: 3d0eb62313cc2ce1c58f5b0380a7641dbf4e25a8
Parents: 0f479eb 7039168
Author: Aleksey Yeschenko alek...@apache.org
Authored: Fri Apr 5 19:38:59 2013 +0300
Committer: Aleksey Yeschenko alek...@apache.org
Committed: Fri Apr 5 19:38:59 2013 +0300

--
 CHANGES.txt|1 +
 conf/cassandra.yaml|5 +-
 .../auth/AllowAllInternodeAuthenticator.java   |   36 
 .../cassandra/auth/IInternodeAuthenticator.java|   44 +++
 src/java/org/apache/cassandra/config/Config.java   |1 +
 .../cassandra/config/DatabaseDescriptor.java   |   12 
 .../org/apache/cassandra/net/MessagingService.java |   10 +++-
 7 files changed, 107 insertions(+), 2 deletions(-)
--


http://git-wip-us.apache.org/repos/asf/cassandra/blob/3d0eb623/CHANGES.txt
--

http://git-wip-us.apache.org/repos/asf/cassandra/blob/3d0eb623/conf/cassandra.yaml
--

http://git-wip-us.apache.org/repos/asf/cassandra/blob/3d0eb623/src/java/org/apache/cassandra/config/Config.java
--

http://git-wip-us.apache.org/repos/asf/cassandra/blob/3d0eb623/src/java/org/apache/cassandra/config/DatabaseDescriptor.java
--
diff --cc src/java/org/apache/cassandra/config/DatabaseDescriptor.java
index 8bde2cc,a57ce9b..3ed7b81
--- a/src/java/org/apache/cassandra/config/DatabaseDescriptor.java
+++ b/src/java/org/apache/cassandra/config/DatabaseDescriptor.java
@@@ -85,388 -92,425 +86,394 @@@ public class DatabaseDescripto
  private static String localDC;
  private static ComparatorInetAddress localComparator;
  
 -/**
 - * Inspect the classpath to find storage configuration file
 - */
 -static URL getStorageConfigURL() throws ConfigurationException
 +static
  {
 -String configUrl = System.getProperty(cassandra.config);
 -if (configUrl == null)
 -configUrl = DEFAULT_CONFIGURATION;
 -
 -URL url;
 -try
 -{
 -url = new URL(configUrl);
 -url.openStream().close(); // catches well-formed but bogus URLs
 -}
 -catch (Exception e)
 +// In client mode, we use a default configuration. Note that the 
fields of this class will be
 +// left unconfigured however (the partitioner or localDC will be null 
for instance) so this
 +// should be used with care.
 +if (Config.isClientMode())
  {
 -ClassLoader loader = DatabaseDescriptor.class.getClassLoader();
 -url = loader.getResource(configUrl);
 -if (url == null)
 -throw new ConfigurationException(Cannot locate  + 
configUrl);
 +conf = new Config();
  }
 -
 -return url;
 -}
 -
 -static
 -{
 -if (Config.getLoadYaml())
 -loadYaml();
  else
 -conf = new Config();
 -}
 -static void loadYaml()
 -{
 -try
  {
 -URL url = getStorageConfigURL();
 -logger.info(Loading settings from  + url);
 -InputStream input;
  try
  {
 -input = url.openStream();
 +applyConfig(loadConfig());
  }
 -catch (IOException e)
 +catch (ConfigurationException e)
  {
 -// getStorageConfigURL should have ruled this out
 -throw new AssertionError(e);
 +logger.error(Fatal configuration error, e);
 +System.err.println(e.getMessage() + \nFatal configuration 
error; unable to start server. See log for stacktrace.);
 +System.exit(1);
  }
 -org.yaml.snakeyaml.constructor.Constructor constructor = new 
org.yaml.snakeyaml.constructor.Constructor(Config.class);
 -TypeDescription seedDesc = new 
TypeDescription(SeedProviderDef.class);
 -seedDesc.putMapPropertyType(parameters, String.class, 
String.class);
 -constructor.addTypeDescription(seedDesc);
 -Yaml yaml = new Yaml(new Loader(constructor));
 -conf = (Config)yaml.load(input);
 -
 -

[jira] [Commented] (CASSANDRA-4775) Counters 2.0

2013-04-05 Thread Jonathan Ellis (JIRA)

[ 
https://issues.apache.org/jira/browse/CASSANDRA-4775?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13623787#comment-13623787
 ] 

Jonathan Ellis commented on CASSANDRA-4775:
---

bq. The implementation becomes a fair bit more complicated

I'm not really sure about that.  Both with this and the above design [1], we do 
have more complexity on read/reconcile, but we trade that for zero special 
cases at the storage engine, which is a huge win.

[1] 
https://issues.apache.org/jira/browse/CASSANDRA-4775?focusedCommentId=13586715page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13586715

 Counters 2.0
 

 Key: CASSANDRA-4775
 URL: https://issues.apache.org/jira/browse/CASSANDRA-4775
 Project: Cassandra
  Issue Type: New Feature
  Components: Core
Reporter: Arya Goudarzi
Assignee: Aleksey Yeschenko
  Labels: counters
 Fix For: 2.0


 The existing partitioned counters remain a source of frustration for most 
 users almost two years after being introduced.  The remaining problems are 
 inherent in the design, not something that can be fixed given enough 
 time/eyeballs.
 Ideally a solution would give us
 - similar performance
 - less special cases in the code
 - potential for a retry mechanism

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


[jira] [Reopened] (CASSANDRA-5425) disablebinary nodetool command

2013-04-05 Thread JIRA

 [ 
https://issues.apache.org/jira/browse/CASSANDRA-5425?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Michał Michalski reopened CASSANDRA-5425:
-


Good point, I think it's reasonable.

 disablebinary nodetool command
 --

 Key: CASSANDRA-5425
 URL: https://issues.apache.org/jira/browse/CASSANDRA-5425
 Project: Cassandra
  Issue Type: Bug
  Components: Drivers
Affects Versions: 1.2.3
Reporter: Joaquin Casares
Assignee: Michał Michalski
Priority: Minor
  Labels: datastax_qa
 Fix For: 1.2.4

 Attachments: 5425-statusbinary.txt, 5425-v1.txt


 The following commands are available via `nodetool`:
 {CODE}
   disablehandoff - Disable the future hints storing on the current 
 node
   disablegossip  - Disable gossip (effectively marking the node dead)
   disablethrift  - Disable thrift server
 {CODE}
 Is it possible to get disablebinary added to help with the testing of binary 
 client drivers?

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


[jira] [Updated] (CASSANDRA-5425) disablebinary nodetool command

2013-04-05 Thread JIRA

 [ 
https://issues.apache.org/jira/browse/CASSANDRA-5425?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Michał Michalski updated CASSANDRA-5425:


Attachment: 5425-statusbinary.txt

Added statusbinary command.

 disablebinary nodetool command
 --

 Key: CASSANDRA-5425
 URL: https://issues.apache.org/jira/browse/CASSANDRA-5425
 Project: Cassandra
  Issue Type: Bug
  Components: Drivers
Affects Versions: 1.2.3
Reporter: Joaquin Casares
Assignee: Michał Michalski
Priority: Minor
  Labels: datastax_qa
 Fix For: 1.2.4

 Attachments: 5425-statusbinary.txt, 5425-v1.txt


 The following commands are available via `nodetool`:
 {CODE}
   disablehandoff - Disable the future hints storing on the current 
 node
   disablegossip  - Disable gossip (effectively marking the node dead)
   disablethrift  - Disable thrift server
 {CODE}
 Is it possible to get disablebinary added to help with the testing of binary 
 client drivers?

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


[1/3] git commit: add nodetool statusbinary command

2013-04-05 Thread brandonwilliams
Updated Branches:
  refs/heads/cassandra-1.2 7039168e0 - 530f5ba1e
  refs/heads/trunk 3d0eb6231 - aaa3648a4


add nodetool statusbinary command


Project: http://git-wip-us.apache.org/repos/asf/cassandra/repo
Commit: http://git-wip-us.apache.org/repos/asf/cassandra/commit/530f5ba1
Tree: http://git-wip-us.apache.org/repos/asf/cassandra/tree/530f5ba1
Diff: http://git-wip-us.apache.org/repos/asf/cassandra/diff/530f5ba1

Branch: refs/heads/cassandra-1.2
Commit: 530f5ba1e490457239e76b9472ee7c3bf8fd2138
Parents: 7039168
Author: Brandon Williams brandonwilli...@apache.org
Authored: Fri Apr 5 12:02:33 2013 -0500
Committer: Brandon Williams brandonwilli...@apache.org
Committed: Fri Apr 5 12:02:33 2013 -0500

--
 src/java/org/apache/cassandra/tools/NodeCmd.java   |7 +++
 src/java/org/apache/cassandra/tools/NodeProbe.java |5 +
 .../org/apache/cassandra/tools/NodeToolHelp.yaml   |3 +++
 3 files changed, 15 insertions(+), 0 deletions(-)
--


http://git-wip-us.apache.org/repos/asf/cassandra/blob/530f5ba1/src/java/org/apache/cassandra/tools/NodeCmd.java
--
diff --git a/src/java/org/apache/cassandra/tools/NodeCmd.java 
b/src/java/org/apache/cassandra/tools/NodeCmd.java
index 4f3e1e1..ed82e32 100644
--- a/src/java/org/apache/cassandra/tools/NodeCmd.java
+++ b/src/java/org/apache/cassandra/tools/NodeCmd.java
@@ -145,6 +145,7 @@ public class NodeCmd
 SETTRACEPROBABILITY,
 SNAPSHOT,
 STATUS,
+STATUSBINARY,
 STATUSTHRIFT,
 STOP,
 TPSTATS,
@@ -912,6 +913,11 @@ public class NodeCmd
 }
 }
 
+private void printIsNativeTransportRunning(PrintStream outs)
+{
+outs.println(probe.isNativeTransportRunning() ? running : not 
running);
+}
+
 private void printIsThriftServerRunning(PrintStream outs)
 {
 outs.println(probe.isThriftServerRunning() ? running : not 
running);
@@ -1052,6 +1058,7 @@ public class NodeCmd
 case COMPACTIONSTATS : 
nodeCmd.printCompactionStats(System.out); break;
 case DISABLEBINARY   : probe.stopNativeTransport(); break;
 case ENABLEBINARY: probe.startNativeTransport(); break;
+case STATUSBINARY: 
nodeCmd.printIsNativeTransportRunning(System.out); break;
 case DISABLEGOSSIP   : probe.stopGossiping(); break;
 case ENABLEGOSSIP: probe.startGossiping(); break;
 case DISABLEHANDOFF  : probe.disableHintedHandoff(); break;

http://git-wip-us.apache.org/repos/asf/cassandra/blob/530f5ba1/src/java/org/apache/cassandra/tools/NodeProbe.java
--
diff --git a/src/java/org/apache/cassandra/tools/NodeProbe.java 
b/src/java/org/apache/cassandra/tools/NodeProbe.java
index 43d99d2..e6eca7b 100644
--- a/src/java/org/apache/cassandra/tools/NodeProbe.java
+++ b/src/java/org/apache/cassandra/tools/NodeProbe.java
@@ -710,6 +710,11 @@ public class NodeProbe
 ssProxy.startNativeTransport();
 }
 
+public boolean isNativeTransportRunning()
+{
+return ssProxy.isNativeTransportRunning();
+}
+
 public void stopGossiping()
 {
 ssProxy.stopGossiping();

http://git-wip-us.apache.org/repos/asf/cassandra/blob/530f5ba1/src/resources/org/apache/cassandra/tools/NodeToolHelp.yaml
--
diff --git a/src/resources/org/apache/cassandra/tools/NodeToolHelp.yaml 
b/src/resources/org/apache/cassandra/tools/NodeToolHelp.yaml
index 6551b07..f3cd88e 100644
--- a/src/resources/org/apache/cassandra/tools/NodeToolHelp.yaml
+++ b/src/resources/org/apache/cassandra/tools/NodeToolHelp.yaml
@@ -55,6 +55,9 @@ commands:
   - name: enablebinary
 help: |
   Reenable native transport (binary protocol)
+  - name: statusbinary
+help: |
+  Status of native transport (binary protocol)
   - name: disablehandoff
 help: |
   Disable the future hints storing on the current node



[2/3] git commit: add nodetool statusbinary command

2013-04-05 Thread brandonwilliams
add nodetool statusbinary command


Project: http://git-wip-us.apache.org/repos/asf/cassandra/repo
Commit: http://git-wip-us.apache.org/repos/asf/cassandra/commit/530f5ba1
Tree: http://git-wip-us.apache.org/repos/asf/cassandra/tree/530f5ba1
Diff: http://git-wip-us.apache.org/repos/asf/cassandra/diff/530f5ba1

Branch: refs/heads/trunk
Commit: 530f5ba1e490457239e76b9472ee7c3bf8fd2138
Parents: 7039168
Author: Brandon Williams brandonwilli...@apache.org
Authored: Fri Apr 5 12:02:33 2013 -0500
Committer: Brandon Williams brandonwilli...@apache.org
Committed: Fri Apr 5 12:02:33 2013 -0500

--
 src/java/org/apache/cassandra/tools/NodeCmd.java   |7 +++
 src/java/org/apache/cassandra/tools/NodeProbe.java |5 +
 .../org/apache/cassandra/tools/NodeToolHelp.yaml   |3 +++
 3 files changed, 15 insertions(+), 0 deletions(-)
--


http://git-wip-us.apache.org/repos/asf/cassandra/blob/530f5ba1/src/java/org/apache/cassandra/tools/NodeCmd.java
--
diff --git a/src/java/org/apache/cassandra/tools/NodeCmd.java 
b/src/java/org/apache/cassandra/tools/NodeCmd.java
index 4f3e1e1..ed82e32 100644
--- a/src/java/org/apache/cassandra/tools/NodeCmd.java
+++ b/src/java/org/apache/cassandra/tools/NodeCmd.java
@@ -145,6 +145,7 @@ public class NodeCmd
 SETTRACEPROBABILITY,
 SNAPSHOT,
 STATUS,
+STATUSBINARY,
 STATUSTHRIFT,
 STOP,
 TPSTATS,
@@ -912,6 +913,11 @@ public class NodeCmd
 }
 }
 
+private void printIsNativeTransportRunning(PrintStream outs)
+{
+outs.println(probe.isNativeTransportRunning() ? running : not 
running);
+}
+
 private void printIsThriftServerRunning(PrintStream outs)
 {
 outs.println(probe.isThriftServerRunning() ? running : not 
running);
@@ -1052,6 +1058,7 @@ public class NodeCmd
 case COMPACTIONSTATS : 
nodeCmd.printCompactionStats(System.out); break;
 case DISABLEBINARY   : probe.stopNativeTransport(); break;
 case ENABLEBINARY: probe.startNativeTransport(); break;
+case STATUSBINARY: 
nodeCmd.printIsNativeTransportRunning(System.out); break;
 case DISABLEGOSSIP   : probe.stopGossiping(); break;
 case ENABLEGOSSIP: probe.startGossiping(); break;
 case DISABLEHANDOFF  : probe.disableHintedHandoff(); break;

http://git-wip-us.apache.org/repos/asf/cassandra/blob/530f5ba1/src/java/org/apache/cassandra/tools/NodeProbe.java
--
diff --git a/src/java/org/apache/cassandra/tools/NodeProbe.java 
b/src/java/org/apache/cassandra/tools/NodeProbe.java
index 43d99d2..e6eca7b 100644
--- a/src/java/org/apache/cassandra/tools/NodeProbe.java
+++ b/src/java/org/apache/cassandra/tools/NodeProbe.java
@@ -710,6 +710,11 @@ public class NodeProbe
 ssProxy.startNativeTransport();
 }
 
+public boolean isNativeTransportRunning()
+{
+return ssProxy.isNativeTransportRunning();
+}
+
 public void stopGossiping()
 {
 ssProxy.stopGossiping();

http://git-wip-us.apache.org/repos/asf/cassandra/blob/530f5ba1/src/resources/org/apache/cassandra/tools/NodeToolHelp.yaml
--
diff --git a/src/resources/org/apache/cassandra/tools/NodeToolHelp.yaml 
b/src/resources/org/apache/cassandra/tools/NodeToolHelp.yaml
index 6551b07..f3cd88e 100644
--- a/src/resources/org/apache/cassandra/tools/NodeToolHelp.yaml
+++ b/src/resources/org/apache/cassandra/tools/NodeToolHelp.yaml
@@ -55,6 +55,9 @@ commands:
   - name: enablebinary
 help: |
   Reenable native transport (binary protocol)
+  - name: statusbinary
+help: |
+  Status of native transport (binary protocol)
   - name: disablehandoff
 help: |
   Disable the future hints storing on the current node



[jira] [Commented] (CASSANDRA-5062) Support CAS

2013-04-05 Thread Sylvain Lebresne (JIRA)

[ 
https://issues.apache.org/jira/browse/CASSANDRA-5062?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13623839#comment-13623839
 ] 

Sylvain Lebresne commented on CASSANDRA-5062:
-

I haven't finished reviewing yet, but since I'll have to stop for today, here's 
a bunch of early remarks.

In SP.preparePaxos, if we throw if {{!mostRecentCommitHasQuorum}} and since 
PrepareCallback only waits for quorum response, I'm not sure later 
replicasMissingMostRecentCommit can ever return anything other than empty, and 
so I don't think we'll make progress. Furthermore, this means that that we'll 
throw as soon as one node of the quorum first responder is not up to date, 
which feels overly pessimistic.

So I think we should remove the mostRecentCommitHasQuorum check in 
preparePaxos.  But then, once we're received the prepare responses, we must 
still ensure that a quorum of node do are on the MRC before moving on.  So if 
we do have missingMRC  0, we would do the commit as is now, but then we would 
re-start the prepare phase, re-asking for promisses. I think it is necessary to 
re-prepare after the commits anyway because those commit will erase the paxos 
state on the replica, so some of the promise we got are not valid anymore. 
Another observation is that for the repair commit of the missingMRC, we can 
(and should in fact) use the MRC as ballot. So we can optimize this 
commit-and-re-prepare by sending just one special message (and only to the 
missingMRC nodes).

bq. I agree, but on the other hand just retry automatically is something that 
we avoid elsewhere for good reason (arbitrarily high latency with no visibility 
to the client what is going on). I also considered introducing a new exception 
type explaining the state, but throwing an exception when everything is working 
fine is also not intuitive. So I think all the options kind of suck, but this 
one sucks least IMO.

I disagree, I think that is the worst option tbh. That fact is, in almost all 
cases, when a user want to CAS something, he will need a real true or false, 
i.e. weither his CAS applies or not. Until then, an answer that says sorry but 
due to implementation details we haven't tested you CAS yet is useless and the 
user will retry 100% of the time. So retrying server side seems to me like the 
right and the most efficient one. Throwing a specific exception could work I 
suppose, but in the end it's just pushing the retry to client and since there 
is nothing better to do than retry, this will increase latency and expose more 
implementation details with no benefits that I can see. But returning false in 
those case, mean that user can't do anything with the false value. That's 
problematic because it means users will have to read to know if a false is a 
real false, or just the algorithm haven't win on the first round (in which 
case it still has to retry).

I do want to note that the algorithm haven't win on the first round can 
happen for reasons completely orthogonal to the user CAS, if only because the 
CAS is at the row level, and thus a CAS on a column c1 will conflict with one 
on column c2 (and in fact, due to the implementation of PaxosState, there is 
even some random cross-keys conflicts). I.e. a false currently does not even 
guarantee that there was a real conflict between the user CAS and some other 
CAS.

Also, I don't think this is at all comparable to other places when we don't 
retry automatically so I don't buy that argument. Besides, CASSANDRA-4705 does 
implement some form of automatic retry so there is prior art. But to be clear, 
I do not suggest that we should retry indefinitely, we should absolutely take 
the rpc timeout into account. I also think that you CAS will take longer if 
there is contention is something pretty intuitive to understand (even if, as 
said above, the contention can be slightly artificial in practice, due to 
implementation details).

Also:
* Nit: In CFMetaData PaxosCF definition: propsal - proposal
* When getting the prepare response, I think that as soon as we get a response 
that is not promised, we can stop waiting for the other responses. I don't 
think we win anything by waiting.


 Support CAS
 ---

 Key: CASSANDRA-5062
 URL: https://issues.apache.org/jira/browse/CASSANDRA-5062
 Project: Cassandra
  Issue Type: New Feature
  Components: API, Core
Reporter: Jonathan Ellis
 Fix For: 2.0

 Attachments: half-baked commit 1.jpg, half-baked commit 2.jpg, 
 half-baked commit 3.jpg


 Strong consistency is not enough to prevent race conditions.  The classic 
 example is user account creation: we want to ensure usernames are unique, so 
 we only want to signal account creation success if nobody else has created 
 the account yet.  But naive read-then-write allows clients to race and both 
 

[jira] [Commented] (CASSANDRA-5400) Allow multiple ports to gossip from a single IP address

2013-04-05 Thread Carl Yeksigian (JIRA)

[ 
https://issues.apache.org/jira/browse/CASSANDRA-5400?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13623855#comment-13623855
 ] 

Carl Yeksigian commented on CASSANDRA-5400:
---

For us, this is definitely something that would be useful. It would be better 
to have our fat clients using the same name. We are currently using virtual IP 
addresses, and while it works, it seems like a workaround, and this patch is 
meant to fix the workaround. We have to be careful to refer to the correct IP 
addresses, which has already caused us problems with hints being replayed to 
the fat client because we reversed the IP addresses in some of the 
configurations. While this is a large change, I do think that it is justified, 
but I do understand that the benefits may be minimal for a lot of users; I'm 
biased because it does solve our issues.

Assuming that we agree that we should support multi-port clusters, I think that 
there are a few changes that are necessary to make this work. Also, rather than 
continually posting 600k patches, I'm going to work on this on a git branch 
instead (https://github.com/carlyeks/cassandra/tree/cie).

1. multi-port should be a new mode, not a default operation. Updated clients 
can talk to the multi-port hosts, but the defaults would be that all of the 
hosts use the same port to communicate with.
2. If the multi-port mode is enabled, then the peers table will be altered in 
some way. Maybe we can drop the peers table (copying the data into memory, only 
used for the upgrade), and create a new peers table that uses (address, port) 
as the primary key.
3. Internally, Cassandra can switch to using the endpoint, since the serializer 
will use the CompactEndpointSerializer for prior messaging service versions.
4. We have to gossip the RPC endpoint (so, this issue will be blocked by 
CASSANDRA-4501).

 Allow multiple ports to gossip from a single IP address
 ---

 Key: CASSANDRA-5400
 URL: https://issues.apache.org/jira/browse/CASSANDRA-5400
 Project: Cassandra
  Issue Type: New Feature
Affects Versions: 2.0
Reporter: Carl Yeksigian
Assignee: Carl Yeksigian
 Fix For: 2.0

 Attachments: 5400.txt, 5400-v2.txt, 5400-v3.patch, 5400-v4.patch


 If a fat client is running on the same machine as a Cassandra node, the fat 
 client must be allocated a new IP address. However, since the node is now a 
 part of the gossip, the other nodes in the ring must be able to talk to it. 
 This means that a local only address (127.0.0.n) won't actually work for the 
 rest of the ring.
 This also would allow for multiple Cassandra service instances to run on a 
 single machine, or from a group of machines behind a NAT.
 The change is simple in concept: instead of using an InetAddress, use a 
 different class. Instead of using an InetSocketAddress, which would still tie 
 us to using InetAddress, I've added a new class, CassandraInstanceEndpoint. 
 The serializer allows for reading a serialized Inet4Address or Inet6Address; 
 also, the message service can still communicate with 
 non-CassandraInstanceEndpoint aware code.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


[jira] [Commented] (CASSANDRA-5378) Fat Client: No longer works in 1.2

2013-04-05 Thread Carl Yeksigian (JIRA)

[ 
https://issues.apache.org/jira/browse/CASSANDRA-5378?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13623861#comment-13623861
 ] 

Carl Yeksigian commented on CASSANDRA-5378:
---

The change to select statement is because the fat client can't use the CFS as 
it doesn't have the data. So, the only things that we have instead is the 
metadata. Since CQL3 is the way that most clients will want to interact with 
the service, I thought it made sense to try to update those statements to not 
use the CFS; any direction on how to fix this?

 Fat Client: No longer works in 1.2
 --

 Key: CASSANDRA-5378
 URL: https://issues.apache.org/jira/browse/CASSANDRA-5378
 Project: Cassandra
  Issue Type: Bug
Affects Versions: 1.2.0
Reporter: Carl Yeksigian
Assignee: Carl Yeksigian
  Labels: client
 Fix For: 1.2.4

 Attachments: 5378-1.2.txt, 5378.txt, 5378-v2.txt


 The current client only example doesn't compile. After doing some updates, 
 the fat client still won't work, mainly because the schema is not being 
 pushed to the fat client.
 I've made changes to the client to support CQL3 commands, to the 
 ServiceManager to wait until a migration has completed before starting the 
 client, and to the MigrationManager to not try to pull schemas from a fat 
 client.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


[jira] [Commented] (CASSANDRA-5418) repair freezing

2013-04-05 Thread Arya Goudarzi (JIRA)

[ 
https://issues.apache.org/jira/browse/CASSANDRA-5418?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13623875#comment-13623875
 ] 

Arya Goudarzi commented on CASSANDRA-5418:
--

I upgraded our 4 node sandbox cluster from 1.1.10 to 1.2.3. It is impossible to 
run repair on any node. They all get suck without any exception in the log. 
Could my issue be related? Is there a workaround? I have 2 more days till my 
gc_grace.

 repair freezing
 ---

 Key: CASSANDRA-5418
 URL: https://issues.apache.org/jira/browse/CASSANDRA-5418
 Project: Cassandra
  Issue Type: Bug
  Components: Core
Affects Versions: 1.2.2, 1.2.3
 Environment: 5 nodes, RackInferring snitch, OpenVZ VMs, Centos 6, 
 Oracle JVM with JNA enabled.
Reporter: Igor Ivanov

 When I run *nodetool repair* on cas01 node it get's stuck at some point.
 I see following exceptions in cas01 system.log:
 {quote}
 ERROR [Streaming to /10.10.45.60:28] 2013-04-02 09:03:55,353 
 CassandraDaemon.java (line 132) Exception in thread Thread[Streaming to 
 /10.10.45.60:28,5,main]
 java.lang.RuntimeException: java.io.EOFException
   at com.google.common.base.Throwables.propagate(Throwables.java:160)
   at 
 org.apache.cassandra.utils.WrappedRunnable.run(WrappedRunnable.java:32)
   at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown 
 Source)
   at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
   at java.lang.Thread.run(Unknown Source)
 Caused by: java.io.EOFException
   at java.io.DataInputStream.readInt(Unknown Source)
   at 
 org.apache.cassandra.streaming.FileStreamTask.receiveReply(FileStreamTask.java:193)
   at 
 org.apache.cassandra.streaming.compress.CompressedFileStreamTask.stream(CompressedFileStreamTask.java:114)
   at 
 org.apache.cassandra.streaming.FileStreamTask.runMayThrow(FileStreamTask.java:91)
   at 
 org.apache.cassandra.utils.WrappedRunnable.run(WrappedRunnable.java:28)
   ... 3 more
 ERROR [Thread-2076] 2013-04-02 09:07:12,261 CassandraDaemon.java (line 132) 
 Exception in thread Thread[Thread-2076,5,main]
 java.lang.AssertionError: incorrect row data size 130921 written to 
 /var/lib/cassandra/data/EDITED/content_list/footballsite-content_list-tmp-ib-3660-Data.db;
  correct is 131074
   at 
 org.apache.cassandra.io.sstable.SSTableWriter.appendFromStream(SSTableWriter.java:285)
   at 
 org.apache.cassandra.streaming.IncomingStreamReader.streamIn(IncomingStreamReader.java:179)
   at 
 org.apache.cassandra.streaming.IncomingStreamReader.read(IncomingStreamReader.java:122)
   at 
 org.apache.cassandra.net.IncomingTcpConnection.stream(IncomingTcpConnection.java:238)
   at 
 org.apache.cassandra.net.IncomingTcpConnection.handleStream(IncomingTcpConnection.java:178)
   at 
 org.apache.cassandra.net.IncomingTcpConnection.run(IncomingTcpConnection.java:78)
 {quote}
 On other machines there are some exceptions too:
 {quote}
 ERROR [Thread-1424] 2013-04-02 09:07:12,248 CassandraDaemon.java (line 132) 
 Exception in thread Thread[Thread-1424,5,main]
 java.lang.AssertionError: incorrect row data size 130921 written to 
 /var/lib/cassandra/data/EDITED/content_list/footballsite-content_list-tmp-ib-2268-Data.db;
  correct is 131074
   at 
 org.apache.cassandra.io.sstable.SSTableWriter.appendFromStream(SSTableWriter.java:285)
   at 
 org.apache.cassandra.streaming.IncomingStreamReader.streamIn(IncomingStreamReader.java:179)
   at 
 org.apache.cassandra.streaming.IncomingStreamReader.read(IncomingStreamReader.java:122)
   at 
 org.apache.cassandra.net.IncomingTcpConnection.stream(IncomingTcpConnection.java:238)
   at 
 org.apache.cassandra.net.IncomingTcpConnection.handleStream(IncomingTcpConnection.java:178)
   at 
 org.apache.cassandra.net.IncomingTcpConnection.run(IncomingTcpConnection.java:78)
 ERROR [Streaming to /10.10.45.58:55] 2013-04-02 09:07:12,263 
 CassandraDaemon.java (line 132) Exception in thread Thread[Streaming to 
 /10.10.45.58:55,5,main]
 java.lang.RuntimeException: java.io.EOFException
   at com.google.common.base.Throwables.propagate(Throwables.java:160)
   at 
 org.apache.cassandra.utils.WrappedRunnable.run(WrappedRunnable.java:32)
   at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown 
 Source)
   at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
   at java.lang.Thread.run(Unknown Source)
 Caused by: java.io.EOFException
   at java.io.DataInputStream.readInt(Unknown Source)
   at 
 org.apache.cassandra.streaming.FileStreamTask.receiveReply(FileStreamTask.java:193)
   at 
 org.apache.cassandra.streaming.compress.CompressedFileStreamTask.stream(CompressedFileStreamTask.java:114)
   at 
 

[Cassandra Wiki] Trivial Update of Denice12P by Denice12P

2013-04-05 Thread Apache Wiki
Dear Wiki user,

You have subscribed to a wiki page or wiki category on Cassandra Wiki for 
change notification.

The Denice12P page has been changed by Denice12P:
http://wiki.apache.org/cassandra/Denice12P

New page:
Name: Denice FifeBR
My age: 29BR
Country: NetherlandsBR
City: Sint Jansklooster BR
Post code: 8326 CGBR
Street: Kloosterweg 188BR
BR
my web page :: 
[[http://www.i88.ca/blog/view/83372/swift-secrets-of-psychotherapy-where-to-go|psihoterapie]]


[jira] [Commented] (CASSANDRA-5400) Allow multiple ports to gossip from a single IP address

2013-04-05 Thread Jonathan Ellis (JIRA)

[ 
https://issues.apache.org/jira/browse/CASSANDRA-5400?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13623881#comment-13623881
 ] 

Jonathan Ellis commented on CASSANDRA-5400:
---

bq. We are currently using virtual IP addresses, and while it works, it seems 
like a workaround

Right.  So it sounds to me like the choice is, do we optimize for fat clients 
colocated with C* nodes and deal with the pain that causes clients and the rest 
of the ecosystem, or do we optimize for thin clients and agree that colocating 
fat clients will remain possible but painful?

Put that way, it seems pretty clear to me that optimizing for a very niche use 
case at the expense of everyone else is the wrong thing to do.

(I'll also note that both embedding Cassandra in the same JVM, and more 
powerful server-side CQL constructs, may make colocated fat clients obsolete 
anyway in the relatively near term.)

 Allow multiple ports to gossip from a single IP address
 ---

 Key: CASSANDRA-5400
 URL: https://issues.apache.org/jira/browse/CASSANDRA-5400
 Project: Cassandra
  Issue Type: New Feature
Affects Versions: 2.0
Reporter: Carl Yeksigian
Assignee: Carl Yeksigian
 Fix For: 2.0

 Attachments: 5400.txt, 5400-v2.txt, 5400-v3.patch, 5400-v4.patch


 If a fat client is running on the same machine as a Cassandra node, the fat 
 client must be allocated a new IP address. However, since the node is now a 
 part of the gossip, the other nodes in the ring must be able to talk to it. 
 This means that a local only address (127.0.0.n) won't actually work for the 
 rest of the ring.
 This also would allow for multiple Cassandra service instances to run on a 
 single machine, or from a group of machines behind a NAT.
 The change is simple in concept: instead of using an InetAddress, use a 
 different class. Instead of using an InetSocketAddress, which would still tie 
 us to using InetAddress, I've added a new class, CassandraInstanceEndpoint. 
 The serializer allows for reading a serialized Inet4Address or Inet6Address; 
 also, the message service can still communicate with 
 non-CassandraInstanceEndpoint aware code.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


[jira] [Comment Edited] (CASSANDRA-5418) repair freezing

2013-04-05 Thread Arya Goudarzi (JIRA)

[ 
https://issues.apache.org/jira/browse/CASSANDRA-5418?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13623875#comment-13623875
 ] 

Arya Goudarzi edited comment on CASSANDRA-5418 at 4/5/13 6:09 PM:
--

I upgraded our 4 node sandbox cluster from 1.1.10 to 1.2.3. It is impossible to 
run repair on any node. They all get stuck without any exception in the log. 
Could my issue be related? Is there a workaround? I have 2 more days till my 
gc_grace.

  was (Author: arya):
I upgraded our 4 node sandbox cluster from 1.1.10 to 1.2.3. It is 
impossible to run repair on any node. They all get suck without any exception 
in the log. Could my issue be related? Is there a workaround? I have 2 more 
days till my gc_grace.
  
 repair freezing
 ---

 Key: CASSANDRA-5418
 URL: https://issues.apache.org/jira/browse/CASSANDRA-5418
 Project: Cassandra
  Issue Type: Bug
  Components: Core
Affects Versions: 1.2.2, 1.2.3
 Environment: 5 nodes, RackInferring snitch, OpenVZ VMs, Centos 6, 
 Oracle JVM with JNA enabled.
Reporter: Igor Ivanov

 When I run *nodetool repair* on cas01 node it get's stuck at some point.
 I see following exceptions in cas01 system.log:
 {quote}
 ERROR [Streaming to /10.10.45.60:28] 2013-04-02 09:03:55,353 
 CassandraDaemon.java (line 132) Exception in thread Thread[Streaming to 
 /10.10.45.60:28,5,main]
 java.lang.RuntimeException: java.io.EOFException
   at com.google.common.base.Throwables.propagate(Throwables.java:160)
   at 
 org.apache.cassandra.utils.WrappedRunnable.run(WrappedRunnable.java:32)
   at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown 
 Source)
   at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
   at java.lang.Thread.run(Unknown Source)
 Caused by: java.io.EOFException
   at java.io.DataInputStream.readInt(Unknown Source)
   at 
 org.apache.cassandra.streaming.FileStreamTask.receiveReply(FileStreamTask.java:193)
   at 
 org.apache.cassandra.streaming.compress.CompressedFileStreamTask.stream(CompressedFileStreamTask.java:114)
   at 
 org.apache.cassandra.streaming.FileStreamTask.runMayThrow(FileStreamTask.java:91)
   at 
 org.apache.cassandra.utils.WrappedRunnable.run(WrappedRunnable.java:28)
   ... 3 more
 ERROR [Thread-2076] 2013-04-02 09:07:12,261 CassandraDaemon.java (line 132) 
 Exception in thread Thread[Thread-2076,5,main]
 java.lang.AssertionError: incorrect row data size 130921 written to 
 /var/lib/cassandra/data/EDITED/content_list/footballsite-content_list-tmp-ib-3660-Data.db;
  correct is 131074
   at 
 org.apache.cassandra.io.sstable.SSTableWriter.appendFromStream(SSTableWriter.java:285)
   at 
 org.apache.cassandra.streaming.IncomingStreamReader.streamIn(IncomingStreamReader.java:179)
   at 
 org.apache.cassandra.streaming.IncomingStreamReader.read(IncomingStreamReader.java:122)
   at 
 org.apache.cassandra.net.IncomingTcpConnection.stream(IncomingTcpConnection.java:238)
   at 
 org.apache.cassandra.net.IncomingTcpConnection.handleStream(IncomingTcpConnection.java:178)
   at 
 org.apache.cassandra.net.IncomingTcpConnection.run(IncomingTcpConnection.java:78)
 {quote}
 On other machines there are some exceptions too:
 {quote}
 ERROR [Thread-1424] 2013-04-02 09:07:12,248 CassandraDaemon.java (line 132) 
 Exception in thread Thread[Thread-1424,5,main]
 java.lang.AssertionError: incorrect row data size 130921 written to 
 /var/lib/cassandra/data/EDITED/content_list/footballsite-content_list-tmp-ib-2268-Data.db;
  correct is 131074
   at 
 org.apache.cassandra.io.sstable.SSTableWriter.appendFromStream(SSTableWriter.java:285)
   at 
 org.apache.cassandra.streaming.IncomingStreamReader.streamIn(IncomingStreamReader.java:179)
   at 
 org.apache.cassandra.streaming.IncomingStreamReader.read(IncomingStreamReader.java:122)
   at 
 org.apache.cassandra.net.IncomingTcpConnection.stream(IncomingTcpConnection.java:238)
   at 
 org.apache.cassandra.net.IncomingTcpConnection.handleStream(IncomingTcpConnection.java:178)
   at 
 org.apache.cassandra.net.IncomingTcpConnection.run(IncomingTcpConnection.java:78)
 ERROR [Streaming to /10.10.45.58:55] 2013-04-02 09:07:12,263 
 CassandraDaemon.java (line 132) Exception in thread Thread[Streaming to 
 /10.10.45.58:55,5,main]
 java.lang.RuntimeException: java.io.EOFException
   at com.google.common.base.Throwables.propagate(Throwables.java:160)
   at 
 org.apache.cassandra.utils.WrappedRunnable.run(WrappedRunnable.java:32)
   at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown 
 Source)
   at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
   at java.lang.Thread.run(Unknown Source)
 Caused by: java.io.EOFException
   at 

[jira] [Commented] (CASSANDRA-5400) Allow multiple ports to gossip from a single IP address

2013-04-05 Thread Carl Yeksigian (JIRA)

[ 
https://issues.apache.org/jira/browse/CASSANDRA-5400?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13623891#comment-13623891
 ] 

Carl Yeksigian commented on CASSANDRA-5400:
---

I'm willing to close this as wontfix. While I think it's useful, I do agree 
that it's a rather niche case.

We're holding out on embedding Cassandra mainly because we don't want our code 
to bring down Cassandra, and it's a good feature to have the isolated processes 
for this.

I guess the other question is why have the fat client. It is rather painful to 
use, doesn't really feel like it's been supported, and might not even have the 
correct constructs. Can we remove that entire construct in 2.0?

 Allow multiple ports to gossip from a single IP address
 ---

 Key: CASSANDRA-5400
 URL: https://issues.apache.org/jira/browse/CASSANDRA-5400
 Project: Cassandra
  Issue Type: New Feature
Affects Versions: 2.0
Reporter: Carl Yeksigian
Assignee: Carl Yeksigian
 Fix For: 2.0

 Attachments: 5400.txt, 5400-v2.txt, 5400-v3.patch, 5400-v4.patch


 If a fat client is running on the same machine as a Cassandra node, the fat 
 client must be allocated a new IP address. However, since the node is now a 
 part of the gossip, the other nodes in the ring must be able to talk to it. 
 This means that a local only address (127.0.0.n) won't actually work for the 
 rest of the ring.
 This also would allow for multiple Cassandra service instances to run on a 
 single machine, or from a group of machines behind a NAT.
 The change is simple in concept: instead of using an InetAddress, use a 
 different class. Instead of using an InetSocketAddress, which would still tie 
 us to using InetAddress, I've added a new class, CassandraInstanceEndpoint. 
 The serializer allows for reading a serialized Inet4Address or Inet6Address; 
 also, the message service can still communicate with 
 non-CassandraInstanceEndpoint aware code.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


[jira] [Commented] (CASSANDRA-5400) Allow multiple ports to gossip from a single IP address

2013-04-05 Thread Jonathan Ellis (JIRA)

[ 
https://issues.apache.org/jira/browse/CASSANDRA-5400?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13623898#comment-13623898
 ] 

Jonathan Ellis commented on CASSANDRA-5400:
---

The pain of having an initClient entry point to StorageService and a use it if 
it's useful; don't complain if it breaks policy for StorageProxy is 
approximately zero, so I'm okay with keeping it around.  Then again, the 
tendency for it to code rot does seem to indicate that nobody's really actively 
using it, so I'd be fine with removing it too.  (Although part of me does want 
to port YCSB to it...  I bet that's one reason Voldemort tends to beat us at 
latency benchmarks.)

 Allow multiple ports to gossip from a single IP address
 ---

 Key: CASSANDRA-5400
 URL: https://issues.apache.org/jira/browse/CASSANDRA-5400
 Project: Cassandra
  Issue Type: New Feature
Affects Versions: 2.0
Reporter: Carl Yeksigian
Assignee: Carl Yeksigian
 Fix For: 2.0

 Attachments: 5400.txt, 5400-v2.txt, 5400-v3.patch, 5400-v4.patch


 If a fat client is running on the same machine as a Cassandra node, the fat 
 client must be allocated a new IP address. However, since the node is now a 
 part of the gossip, the other nodes in the ring must be able to talk to it. 
 This means that a local only address (127.0.0.n) won't actually work for the 
 rest of the ring.
 This also would allow for multiple Cassandra service instances to run on a 
 single machine, or from a group of machines behind a NAT.
 The change is simple in concept: instead of using an InetAddress, use a 
 different class. Instead of using an InetSocketAddress, which would still tie 
 us to using InetAddress, I've added a new class, CassandraInstanceEndpoint. 
 The serializer allows for reading a serialized Inet4Address or Inet6Address; 
 also, the message service can still communicate with 
 non-CassandraInstanceEndpoint aware code.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


[jira] [Commented] (CASSANDRA-5400) Allow multiple ports to gossip from a single IP address

2013-04-05 Thread Carl Yeksigian (JIRA)

[ 
https://issues.apache.org/jira/browse/CASSANDRA-5400?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13623912#comment-13623912
 ] 

Carl Yeksigian commented on CASSANDRA-5400:
---

Having used the fat client (and trying to fix it), I really think it's tendency 
to allow shotting oneself in the foot is really high.

I'd personally like to get rid of it, just so that others don't hurt themselves 
:)

 Allow multiple ports to gossip from a single IP address
 ---

 Key: CASSANDRA-5400
 URL: https://issues.apache.org/jira/browse/CASSANDRA-5400
 Project: Cassandra
  Issue Type: New Feature
Affects Versions: 2.0
Reporter: Carl Yeksigian
Assignee: Carl Yeksigian
 Fix For: 2.0

 Attachments: 5400.txt, 5400-v2.txt, 5400-v3.patch, 5400-v4.patch


 If a fat client is running on the same machine as a Cassandra node, the fat 
 client must be allocated a new IP address. However, since the node is now a 
 part of the gossip, the other nodes in the ring must be able to talk to it. 
 This means that a local only address (127.0.0.n) won't actually work for the 
 rest of the ring.
 This also would allow for multiple Cassandra service instances to run on a 
 single machine, or from a group of machines behind a NAT.
 The change is simple in concept: instead of using an InetAddress, use a 
 different class. Instead of using an InetSocketAddress, which would still tie 
 us to using InetAddress, I've added a new class, CassandraInstanceEndpoint. 
 The serializer allows for reading a serialized Inet4Address or Inet6Address; 
 also, the message service can still communicate with 
 non-CassandraInstanceEndpoint aware code.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


[jira] [Commented] (CASSANDRA-5378) Fat Client: No longer works in 1.2

2013-04-05 Thread Sylvain Lebresne (JIRA)

[ 
https://issues.apache.org/jira/browse/CASSANDRA-5378?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13623915#comment-13623915
 ] 

Sylvain Lebresne commented on CASSANDRA-5378:
-

Well looking at that code, what was the rational of adding the offending line 
was added in the first place:
{noformat}
+indexedNames.add(cfm.getKeyName());
{noformat}
Seems to me it could just be removed.

 Fat Client: No longer works in 1.2
 --

 Key: CASSANDRA-5378
 URL: https://issues.apache.org/jira/browse/CASSANDRA-5378
 Project: Cassandra
  Issue Type: Bug
Affects Versions: 1.2.0
Reporter: Carl Yeksigian
Assignee: Carl Yeksigian
  Labels: client
 Fix For: 1.2.4

 Attachments: 5378-1.2.txt, 5378.txt, 5378-v2.txt


 The current client only example doesn't compile. After doing some updates, 
 the fat client still won't work, mainly because the schema is not being 
 pushed to the fat client.
 I've made changes to the client to support CQL3 commands, to the 
 ServiceManager to wait until a migration has completed before starting the 
 client, and to the MigrationManager to not try to pull schemas from a fat 
 client.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


[jira] [Commented] (CASSANDRA-5378) Fat Client: No longer works in 1.2

2013-04-05 Thread Carl Yeksigian (JIRA)

[ 
https://issues.apache.org/jira/browse/CASSANDRA-5378?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13623941#comment-13623941
 ] 

Carl Yeksigian commented on CASSANDRA-5378:
---

If we don't have that, we won't be able to validate a query against the row key.

That is, if the schema is:
{code}
CREATE COLUMNFAMILY standard1 ( id ascii PRIMARY KEY , name ascii , value blob 
) ;
SELECT * FROM standard1 WHERE id='abc';
{code}

That select statement will not be validated, as no column is indexed, but the 
row key is. It'll throw the No indexed columns present in by-columns clause 
with Equal operator exception.

 Fat Client: No longer works in 1.2
 --

 Key: CASSANDRA-5378
 URL: https://issues.apache.org/jira/browse/CASSANDRA-5378
 Project: Cassandra
  Issue Type: Bug
Affects Versions: 1.2.0
Reporter: Carl Yeksigian
Assignee: Carl Yeksigian
  Labels: client
 Fix For: 1.2.4

 Attachments: 5378-1.2.txt, 5378.txt, 5378-v2.txt


 The current client only example doesn't compile. After doing some updates, 
 the fat client still won't work, mainly because the schema is not being 
 pushed to the fat client.
 I've made changes to the client to support CQL3 commands, to the 
 ServiceManager to wait until a migration has completed before starting the 
 client, and to the MigrationManager to not try to pull schemas from a fat 
 client.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


[Cassandra Wiki] Trivial Update of Allison42 by Allison42

2013-04-05 Thread Apache Wiki
Dear Wiki user,

You have subscribed to a wiki page or wiki category on Cassandra Wiki for 
change notification.

The Allison42 page has been changed by Allison42:
http://wiki.apache.org/cassandra/Allison42?action=diffrev1=10rev2=11

- Simply put, a home loan loan that gives 100% financing does not need a 
downpayment. Unlike the money shark, hired thugs aren't sent to get the 
borrowed funds money if the payment is late. For slander lives upon succession, 
Forever housed where it gets possession. Nonetheless, problems continue to 
exist with the strict secularization of society. Adapting for your expediency 
you'll be able to submit an application on an instant cash loans via online or 
offline ways.BR
+ Every time you may apply for your house loan prequalification, your lender 
will carefully look at history within this domain.BR
+ However, Barcelona are adamant that they will not allow the striker leave on 
loan and may only entertain a critical offer to get a permanent transfer. Not 
many individuals realize it but statistically, you can find a significant 
variety of people saved literally from immersing themselves in a bad loan.BR
+ The rest in the amount might be paid on easy timely repayments. Hardship Home 
Loan Modifications - At Risk Homeowners.BR
  BR
- my web blog: [[|Payday loans instant cash]]
+ Here is my web site: [[|payday lones]]
  


[jira] [Commented] (CASSANDRA-5400) Allow multiple ports to gossip from a single IP address

2013-04-05 Thread Brandon Williams (JIRA)

[ 
https://issues.apache.org/jira/browse/CASSANDRA-5400?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13623962#comment-13623962
 ] 

Brandon Williams commented on CASSANDRA-5400:
-

bq. Then again, the tendency for it to code rot does seem to indicate that 
nobody's really actively using it

It had rotted so badly before Carl fixed it, it still contained keyspaces/CFs 
defined in the yaml.

 Allow multiple ports to gossip from a single IP address
 ---

 Key: CASSANDRA-5400
 URL: https://issues.apache.org/jira/browse/CASSANDRA-5400
 Project: Cassandra
  Issue Type: New Feature
Affects Versions: 2.0
Reporter: Carl Yeksigian
Assignee: Carl Yeksigian
 Fix For: 2.0

 Attachments: 5400.txt, 5400-v2.txt, 5400-v3.patch, 5400-v4.patch


 If a fat client is running on the same machine as a Cassandra node, the fat 
 client must be allocated a new IP address. However, since the node is now a 
 part of the gossip, the other nodes in the ring must be able to talk to it. 
 This means that a local only address (127.0.0.n) won't actually work for the 
 rest of the ring.
 This also would allow for multiple Cassandra service instances to run on a 
 single machine, or from a group of machines behind a NAT.
 The change is simple in concept: instead of using an InetAddress, use a 
 different class. Instead of using an InetSocketAddress, which would still tie 
 us to using InetAddress, I've added a new class, CassandraInstanceEndpoint. 
 The serializer allows for reading a serialized Inet4Address or Inet6Address; 
 also, the message service can still communicate with 
 non-CassandraInstanceEndpoint aware code.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


[jira] [Created] (CASSANDRA-5430) Make Auth.SUPERUSER_SETUP_DELAY configurable

2013-04-05 Thread John Sanda (JIRA)
John Sanda created CASSANDRA-5430:
-

 Summary: Make Auth.SUPERUSER_SETUP_DELAY configurable
 Key: CASSANDRA-5430
 URL: https://issues.apache.org/jira/browse/CASSANDRA-5430
 Project: Cassandra
  Issue Type: Improvement
  Components: Core
Affects Versions: 1.2.2
Reporter: John Sanda
Priority: Minor


I would like to make SUPERUSER_SETUP_DELAY configurable for automated tests. I 
have tests that stand up a local cluster, and sometimes if I just run a single 
test class, the total execution time to stand up the (usually two) nodes and 
run the tests takes less than 20 seconds. I am running on fast hardware, so I 
can probably get by with a lower value in most cases, but maybe one of my 
teammates runs on slower hardware and needs a larger value.

I do not see this as a problem for production use. It would just be nice to 
have it configurable for dev environments.

Thanks

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


[jira] [Commented] (CASSANDRA-4914) Aggregate functions in CQL

2013-04-05 Thread Carl Yeksigian (JIRA)

[ 
https://issues.apache.org/jira/browse/CASSANDRA-4914?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13623987#comment-13623987
 ] 

Carl Yeksigian commented on CASSANDRA-4914:
---

For this, the proposal is to add a new AggregateFunction interface for a 
function like SUM, which is an extension of Function which takes many arguments?

I'm unsure of what the function's arguments are; in the example [~tjake] gives, 
it seems like the columns would be grouped by empid, then the aggregate 
function would be iteratively called on each grouping. Is that accurate?

 Aggregate functions in CQL
 --

 Key: CASSANDRA-4914
 URL: https://issues.apache.org/jira/browse/CASSANDRA-4914
 Project: Cassandra
  Issue Type: Bug
Reporter: Vijay
Assignee: Vijay
 Fix For: 2.0


 The requirement is to do aggregation of data in Cassandra (Wide row of column 
 values of int, double, float etc).
 With some basic agree gate functions like AVG, SUM, Mean, Min, Max, etc (for 
 the columns within a row).
 Example:
 SELECT * FROM emp WHERE empID IN (130) ORDER BY deptID DESC;  
   
  empid | deptid | first_name | last_name | salary
 ---+++---+
130 |  3 | joe| doe   |   10.1
130 |  2 | joe| doe   |100
130 |  1 | joe| doe   |  1e+03
  
 SELECT sum(salary), empid FROM emp WHERE empID IN (130);  
   
  sum(salary) | empid
 -+
1110.1|  130

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


[jira] [Commented] (CASSANDRA-5400) Allow multiple ports to gossip from a single IP address

2013-04-05 Thread T Jake Luciani (JIRA)

[ 
https://issues.apache.org/jira/browse/CASSANDRA-5400?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13623989#comment-13623989
 ] 

T Jake Luciani commented on CASSANDRA-5400:
---

I thought the real reason todo this was to support bulk streaming from the 
hadoop?  if the reducer wants to stream results to the local node (which is the 
only way we support running hadoop) then we would need one IP address per 
possible reducer instance, per node.

 Allow multiple ports to gossip from a single IP address
 ---

 Key: CASSANDRA-5400
 URL: https://issues.apache.org/jira/browse/CASSANDRA-5400
 Project: Cassandra
  Issue Type: New Feature
Affects Versions: 2.0
Reporter: Carl Yeksigian
Assignee: Carl Yeksigian
 Fix For: 2.0

 Attachments: 5400.txt, 5400-v2.txt, 5400-v3.patch, 5400-v4.patch


 If a fat client is running on the same machine as a Cassandra node, the fat 
 client must be allocated a new IP address. However, since the node is now a 
 part of the gossip, the other nodes in the ring must be able to talk to it. 
 This means that a local only address (127.0.0.n) won't actually work for the 
 rest of the ring.
 This also would allow for multiple Cassandra service instances to run on a 
 single machine, or from a group of machines behind a NAT.
 The change is simple in concept: instead of using an InetAddress, use a 
 different class. Instead of using an InetSocketAddress, which would still tie 
 us to using InetAddress, I've added a new class, CassandraInstanceEndpoint. 
 The serializer allows for reading a serialized Inet4Address or Inet6Address; 
 also, the message service can still communicate with 
 non-CassandraInstanceEndpoint aware code.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


[jira] [Resolved] (CASSANDRA-5411) Unexpired hints can potentially create previously deleted rows

2013-04-05 Thread Brandon Williams (JIRA)

 [ 
https://issues.apache.org/jira/browse/CASSANDRA-5411?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Brandon Williams resolved CASSANDRA-5411.
-

   Resolution: Won't Fix
Fix Version/s: (was: 1.2.4)

This isn't as simple as I originally thought, since hints store the original 
serialized mutation, which can cross multiple CFs, causing us to have to see 
which ones actually need to be removed, and then serialize the remainder in a 
new mutation.  This is getting expensive, so I'd rather just say deliver or 
truncate your hints if you need to modify gc_grace and don't want resurrection.

 Unexpired hints can potentially create previously deleted rows
 --

 Key: CASSANDRA-5411
 URL: https://issues.apache.org/jira/browse/CASSANDRA-5411
 Project: Cassandra
  Issue Type: Bug
  Components: Core
Affects Versions: 1.1.10
 Environment: Ubuntu 10.04
Reporter: Arya Goudarzi
Assignee: Brandon Williams

 Per discussion here: 
 http://www.mail-archive.com/user@cassandra.apache.org/msg28905.html
 Hints are TTLed to lowest gc_grace_seconds. If we have hints that are not 
 replayed, and the administrator updates schema to have lower gc_grace seconds 
 on some CF, chances are compactions will delete tombstones and history of 
 delete gets lost. If the deleted row is in some hints CF, since the TTL is 
 not updated, chances are it gets replayed and the deleted row comes back to 
 life. 
 I think it would be nice as part of schema migration, to also update the TTLs 
 on hints that already exists on any nodes hints column family. 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


[jira] [Commented] (CASSANDRA-5400) Allow multiple ports to gossip from a single IP address

2013-04-05 Thread Brandon Williams (JIRA)

[ 
https://issues.apache.org/jira/browse/CASSANDRA-5400?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13624014#comment-13624014
 ] 

Brandon Williams commented on CASSANDRA-5400:
-

bq. I thought the real reason todo this was to support bulk streaming from the 
hadoop

BOF already does this.

 Allow multiple ports to gossip from a single IP address
 ---

 Key: CASSANDRA-5400
 URL: https://issues.apache.org/jira/browse/CASSANDRA-5400
 Project: Cassandra
  Issue Type: New Feature
Affects Versions: 2.0
Reporter: Carl Yeksigian
Assignee: Carl Yeksigian
 Fix For: 2.0

 Attachments: 5400.txt, 5400-v2.txt, 5400-v3.patch, 5400-v4.patch


 If a fat client is running on the same machine as a Cassandra node, the fat 
 client must be allocated a new IP address. However, since the node is now a 
 part of the gossip, the other nodes in the ring must be able to talk to it. 
 This means that a local only address (127.0.0.n) won't actually work for the 
 rest of the ring.
 This also would allow for multiple Cassandra service instances to run on a 
 single machine, or from a group of machines behind a NAT.
 The change is simple in concept: instead of using an InetAddress, use a 
 different class. Instead of using an InetSocketAddress, which would still tie 
 us to using InetAddress, I've added a new class, CassandraInstanceEndpoint. 
 The serializer allows for reading a serialized Inet4Address or Inet6Address; 
 also, the message service can still communicate with 
 non-CassandraInstanceEndpoint aware code.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


[jira] [Commented] (CASSANDRA-5400) Allow multiple ports to gossip from a single IP address

2013-04-05 Thread Jonathan Ellis (JIRA)

[ 
https://issues.apache.org/jira/browse/CASSANDRA-5400?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13624021#comment-13624021
 ] 

Jonathan Ellis commented on CASSANDRA-5400:
---

I think Jake meant CASSANDRA-4047 -- Jake, see the last couple comments there.  
TLDR multiport is actually neither necessary nor sufficient.  (My mistake 
suggesting it would be.)

 Allow multiple ports to gossip from a single IP address
 ---

 Key: CASSANDRA-5400
 URL: https://issues.apache.org/jira/browse/CASSANDRA-5400
 Project: Cassandra
  Issue Type: New Feature
Affects Versions: 2.0
Reporter: Carl Yeksigian
Assignee: Carl Yeksigian
 Fix For: 2.0

 Attachments: 5400.txt, 5400-v2.txt, 5400-v3.patch, 5400-v4.patch


 If a fat client is running on the same machine as a Cassandra node, the fat 
 client must be allocated a new IP address. However, since the node is now a 
 part of the gossip, the other nodes in the ring must be able to talk to it. 
 This means that a local only address (127.0.0.n) won't actually work for the 
 rest of the ring.
 This also would allow for multiple Cassandra service instances to run on a 
 single machine, or from a group of machines behind a NAT.
 The change is simple in concept: instead of using an InetAddress, use a 
 different class. Instead of using an InetSocketAddress, which would still tie 
 us to using InetAddress, I've added a new class, CassandraInstanceEndpoint. 
 The serializer allows for reading a serialized Inet4Address or Inet6Address; 
 also, the message service can still communicate with 
 non-CassandraInstanceEndpoint aware code.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


[jira] [Commented] (CASSANDRA-5430) Make Auth.SUPERUSER_SETUP_DELAY configurable

2013-04-05 Thread Jonathan Ellis (JIRA)

[ 
https://issues.apache.org/jira/browse/CASSANDRA-5430?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13624023#comment-13624023
 ] 

Jonathan Ellis commented on CASSANDRA-5430:
---

Perhaps we could have it check RING_DELAY, which tests already special-case.

 Make Auth.SUPERUSER_SETUP_DELAY configurable
 

 Key: CASSANDRA-5430
 URL: https://issues.apache.org/jira/browse/CASSANDRA-5430
 Project: Cassandra
  Issue Type: Improvement
  Components: Core
Affects Versions: 1.2.2
Reporter: John Sanda
Priority: Minor
  Labels: authentication

 I would like to make SUPERUSER_SETUP_DELAY configurable for automated tests. 
 I have tests that stand up a local cluster, and sometimes if I just run a 
 single test class, the total execution time to stand up the (usually two) 
 nodes and run the tests takes less than 20 seconds. I am running on fast 
 hardware, so I can probably get by with a lower value in most cases, but 
 maybe one of my teammates runs on slower hardware and needs a larger value.
 I do not see this as a problem for production use. It would just be nice to 
 have it configurable for dev environments.
 Thanks

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


[jira] [Commented] (CASSANDRA-5411) Unexpired hints can potentially create previously deleted rows

2013-04-05 Thread Jonathan Ellis (JIRA)

[ 
https://issues.apache.org/jira/browse/CASSANDRA-5411?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13624026#comment-13624026
 ] 

Jonathan Ellis commented on CASSANDRA-5411:
---

Would it be worth splitting hints out into per-CF objects?  Would be fairly 
simple in hintFor.

 Unexpired hints can potentially create previously deleted rows
 --

 Key: CASSANDRA-5411
 URL: https://issues.apache.org/jira/browse/CASSANDRA-5411
 Project: Cassandra
  Issue Type: Bug
  Components: Core
Affects Versions: 1.1.10
 Environment: Ubuntu 10.04
Reporter: Arya Goudarzi
Assignee: Brandon Williams

 Per discussion here: 
 http://www.mail-archive.com/user@cassandra.apache.org/msg28905.html
 Hints are TTLed to lowest gc_grace_seconds. If we have hints that are not 
 replayed, and the administrator updates schema to have lower gc_grace seconds 
 on some CF, chances are compactions will delete tombstones and history of 
 delete gets lost. If the deleted row is in some hints CF, since the TTL is 
 not updated, chances are it gets replayed and the deleted row comes back to 
 life. 
 I think it would be nice as part of schema migration, to also update the TTLs 
 on hints that already exists on any nodes hints column family. 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


[jira] [Created] (CASSANDRA-5431) cassandra-shuffle with JMX usernames and passwords

2013-04-05 Thread Eric Dong (JIRA)
Eric Dong created CASSANDRA-5431:


 Summary: cassandra-shuffle with JMX usernames and passwords 
 Key: CASSANDRA-5431
 URL: https://issues.apache.org/jira/browse/CASSANDRA-5431
 Project: Cassandra
  Issue Type: Bug
Affects Versions: 1.2.3
Reporter: Eric Dong


Unlike nodetool, cassandra-shuffle doesn't allow passing in a JMX username and 
password. This stops those who want to switch to vnodes from doing so if JMX 
access requires a username and a password.

Patch to follow.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


[jira] [Commented] (CASSANDRA-5411) Unexpired hints can potentially create previously deleted rows

2013-04-05 Thread Arya Goudarzi (JIRA)

[ 
https://issues.apache.org/jira/browse/CASSANDRA-5411?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13624102#comment-13624102
 ] 

Arya Goudarzi commented on CASSANDRA-5411:
--

The notion of delivering or truncating hints before changing gc_grace isn't 
documented anywhere. IMHO it is not fair to the operator to have to remember 
and additional step in a scenario that can happen to anyone; specially, when 
several people in chatroom are dealing with tombstone cleanups situations and 
changing gc_grace has become part of their routine. So, I suggest re-opening 
it, until there is a feasible solution. I wished if I had the capacity to help 
you with this myself, but frankly I am running a one-man operation here and am 
kinda tied up. 

 Unexpired hints can potentially create previously deleted rows
 --

 Key: CASSANDRA-5411
 URL: https://issues.apache.org/jira/browse/CASSANDRA-5411
 Project: Cassandra
  Issue Type: Bug
  Components: Core
Affects Versions: 1.1.10
 Environment: Ubuntu 10.04
Reporter: Arya Goudarzi
Assignee: Brandon Williams

 Per discussion here: 
 http://www.mail-archive.com/user@cassandra.apache.org/msg28905.html
 Hints are TTLed to lowest gc_grace_seconds. If we have hints that are not 
 replayed, and the administrator updates schema to have lower gc_grace seconds 
 on some CF, chances are compactions will delete tombstones and history of 
 delete gets lost. If the deleted row is in some hints CF, since the TTL is 
 not updated, chances are it gets replayed and the deleted row comes back to 
 life. 
 I think it would be nice as part of schema migration, to also update the TTLs 
 on hints that already exists on any nodes hints column family. 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


[jira] [Reopened] (CASSANDRA-5411) Unexpired hints can potentially create previously deleted rows

2013-04-05 Thread Arya Goudarzi (JIRA)

 [ 
https://issues.apache.org/jira/browse/CASSANDRA-5411?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Arya Goudarzi reopened CASSANDRA-5411:
--


 Unexpired hints can potentially create previously deleted rows
 --

 Key: CASSANDRA-5411
 URL: https://issues.apache.org/jira/browse/CASSANDRA-5411
 Project: Cassandra
  Issue Type: Bug
  Components: Core
Affects Versions: 1.1.10
 Environment: Ubuntu 10.04
Reporter: Arya Goudarzi
Assignee: Brandon Williams

 Per discussion here: 
 http://www.mail-archive.com/user@cassandra.apache.org/msg28905.html
 Hints are TTLed to lowest gc_grace_seconds. If we have hints that are not 
 replayed, and the administrator updates schema to have lower gc_grace seconds 
 on some CF, chances are compactions will delete tombstones and history of 
 delete gets lost. If the deleted row is in some hints CF, since the TTL is 
 not updated, chances are it gets replayed and the deleted row comes back to 
 life. 
 I think it would be nice as part of schema migration, to also update the TTLs 
 on hints that already exists on any nodes hints column family. 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


[1/3] git commit: add missing 'stop' help back to nodetool

2013-04-05 Thread brandonwilliams
Updated Branches:
  refs/heads/cassandra-1.2 530f5ba1e - 67160090d
  refs/heads/trunk aaa3648a4 - dc3d74be3


add missing 'stop' help back to nodetool


Project: http://git-wip-us.apache.org/repos/asf/cassandra/repo
Commit: http://git-wip-us.apache.org/repos/asf/cassandra/commit/67160090
Tree: http://git-wip-us.apache.org/repos/asf/cassandra/tree/67160090
Diff: http://git-wip-us.apache.org/repos/asf/cassandra/diff/67160090

Branch: refs/heads/cassandra-1.2
Commit: 67160090d19fbe02b55b37ebc1ca2ad585b6cb89
Parents: 530f5ba
Author: Brandon Williams brandonwilli...@apache.org
Authored: Fri Apr 5 16:56:43 2013 -0500
Committer: Brandon Williams brandonwilli...@apache.org
Committed: Fri Apr 5 16:56:43 2013 -0500

--
 .../org/apache/cassandra/tools/NodeToolHelp.yaml   |3 +++
 1 files changed, 3 insertions(+), 0 deletions(-)
--


http://git-wip-us.apache.org/repos/asf/cassandra/blob/67160090/src/resources/org/apache/cassandra/tools/NodeToolHelp.yaml
--
diff --git a/src/resources/org/apache/cassandra/tools/NodeToolHelp.yaml 
b/src/resources/org/apache/cassandra/tools/NodeToolHelp.yaml
index f3cd88e..61cf1fe 100644
--- a/src/resources/org/apache/cassandra/tools/NodeToolHelp.yaml
+++ b/src/resources/org/apache/cassandra/tools/NodeToolHelp.yaml
@@ -155,6 +155,9 @@ commands:
   - name: getcompactionthreshold keyspace cfname
 help: |
   Print min and max compaction thresholds for a given column family
+  - name: stop compacion_type
+help: |
+  Supported types are COMPACTION, VALIDATION, CLEANUP, SCRUB, INDEX_BUILD
   - name: cfhistograms keyspace cfname
 help: |
   Print statistic histograms for a given column family



[2/3] git commit: add missing 'stop' help back to nodetool

2013-04-05 Thread brandonwilliams
add missing 'stop' help back to nodetool


Project: http://git-wip-us.apache.org/repos/asf/cassandra/repo
Commit: http://git-wip-us.apache.org/repos/asf/cassandra/commit/67160090
Tree: http://git-wip-us.apache.org/repos/asf/cassandra/tree/67160090
Diff: http://git-wip-us.apache.org/repos/asf/cassandra/diff/67160090

Branch: refs/heads/trunk
Commit: 67160090d19fbe02b55b37ebc1ca2ad585b6cb89
Parents: 530f5ba
Author: Brandon Williams brandonwilli...@apache.org
Authored: Fri Apr 5 16:56:43 2013 -0500
Committer: Brandon Williams brandonwilli...@apache.org
Committed: Fri Apr 5 16:56:43 2013 -0500

--
 .../org/apache/cassandra/tools/NodeToolHelp.yaml   |3 +++
 1 files changed, 3 insertions(+), 0 deletions(-)
--


http://git-wip-us.apache.org/repos/asf/cassandra/blob/67160090/src/resources/org/apache/cassandra/tools/NodeToolHelp.yaml
--
diff --git a/src/resources/org/apache/cassandra/tools/NodeToolHelp.yaml 
b/src/resources/org/apache/cassandra/tools/NodeToolHelp.yaml
index f3cd88e..61cf1fe 100644
--- a/src/resources/org/apache/cassandra/tools/NodeToolHelp.yaml
+++ b/src/resources/org/apache/cassandra/tools/NodeToolHelp.yaml
@@ -155,6 +155,9 @@ commands:
   - name: getcompactionthreshold keyspace cfname
 help: |
   Print min and max compaction thresholds for a given column family
+  - name: stop compacion_type
+help: |
+  Supported types are COMPACTION, VALIDATION, CLEANUP, SCRUB, INDEX_BUILD
   - name: cfhistograms keyspace cfname
 help: |
   Print statistic histograms for a given column family



[1/3] git commit: typo

2013-04-05 Thread brandonwilliams
Updated Branches:
  refs/heads/cassandra-1.2 67160090d - 7bad35230
  refs/heads/trunk dc3d74be3 - 28e52ded0


typo


Project: http://git-wip-us.apache.org/repos/asf/cassandra/repo
Commit: http://git-wip-us.apache.org/repos/asf/cassandra/commit/7bad3523
Tree: http://git-wip-us.apache.org/repos/asf/cassandra/tree/7bad3523
Diff: http://git-wip-us.apache.org/repos/asf/cassandra/diff/7bad3523

Branch: refs/heads/cassandra-1.2
Commit: 7bad35230c7be2c80311373edd4d0464d2b15cd4
Parents: 6716009
Author: Brandon Williams brandonwilli...@apache.org
Authored: Fri Apr 5 16:57:51 2013 -0500
Committer: Brandon Williams brandonwilli...@apache.org
Committed: Fri Apr 5 16:57:51 2013 -0500

--
 .../org/apache/cassandra/tools/NodeToolHelp.yaml   |2 +-
 1 files changed, 1 insertions(+), 1 deletions(-)
--


http://git-wip-us.apache.org/repos/asf/cassandra/blob/7bad3523/src/resources/org/apache/cassandra/tools/NodeToolHelp.yaml
--
diff --git a/src/resources/org/apache/cassandra/tools/NodeToolHelp.yaml 
b/src/resources/org/apache/cassandra/tools/NodeToolHelp.yaml
index 61cf1fe..d3e8436 100644
--- a/src/resources/org/apache/cassandra/tools/NodeToolHelp.yaml
+++ b/src/resources/org/apache/cassandra/tools/NodeToolHelp.yaml
@@ -155,7 +155,7 @@ commands:
   - name: getcompactionthreshold keyspace cfname
 help: |
   Print min and max compaction thresholds for a given column family
-  - name: stop compacion_type
+  - name: stop compaction_type
 help: |
   Supported types are COMPACTION, VALIDATION, CLEANUP, SCRUB, INDEX_BUILD
   - name: cfhistograms keyspace cfname



[2/3] git commit: typo

2013-04-05 Thread brandonwilliams
typo


Project: http://git-wip-us.apache.org/repos/asf/cassandra/repo
Commit: http://git-wip-us.apache.org/repos/asf/cassandra/commit/7bad3523
Tree: http://git-wip-us.apache.org/repos/asf/cassandra/tree/7bad3523
Diff: http://git-wip-us.apache.org/repos/asf/cassandra/diff/7bad3523

Branch: refs/heads/trunk
Commit: 7bad35230c7be2c80311373edd4d0464d2b15cd4
Parents: 6716009
Author: Brandon Williams brandonwilli...@apache.org
Authored: Fri Apr 5 16:57:51 2013 -0500
Committer: Brandon Williams brandonwilli...@apache.org
Committed: Fri Apr 5 16:57:51 2013 -0500

--
 .../org/apache/cassandra/tools/NodeToolHelp.yaml   |2 +-
 1 files changed, 1 insertions(+), 1 deletions(-)
--


http://git-wip-us.apache.org/repos/asf/cassandra/blob/7bad3523/src/resources/org/apache/cassandra/tools/NodeToolHelp.yaml
--
diff --git a/src/resources/org/apache/cassandra/tools/NodeToolHelp.yaml 
b/src/resources/org/apache/cassandra/tools/NodeToolHelp.yaml
index 61cf1fe..d3e8436 100644
--- a/src/resources/org/apache/cassandra/tools/NodeToolHelp.yaml
+++ b/src/resources/org/apache/cassandra/tools/NodeToolHelp.yaml
@@ -155,7 +155,7 @@ commands:
   - name: getcompactionthreshold keyspace cfname
 help: |
   Print min and max compaction thresholds for a given column family
-  - name: stop compacion_type
+  - name: stop compaction_type
 help: |
   Supported types are COMPACTION, VALIDATION, CLEANUP, SCRUB, INDEX_BUILD
   - name: cfhistograms keyspace cfname



[jira] [Updated] (CASSANDRA-5431) cassandra-shuffle with JMX usernames and passwords

2013-04-05 Thread Eric Dong (JIRA)

 [ 
https://issues.apache.org/jira/browse/CASSANDRA-5431?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Eric Dong updated CASSANDRA-5431:
-

Attachment: CASSANDRA-5431-whitespace.patch

My intended changes touch files that have formatting issues relative to the 
Cassandra formatter settings for Eclipse, so I'm posting a whitespace patch 
first.

 cassandra-shuffle with JMX usernames and passwords 
 ---

 Key: CASSANDRA-5431
 URL: https://issues.apache.org/jira/browse/CASSANDRA-5431
 Project: Cassandra
  Issue Type: Bug
Affects Versions: 1.2.3
Reporter: Eric Dong
 Attachments: CASSANDRA-5431-whitespace.patch


 Unlike nodetool, cassandra-shuffle doesn't allow passing in a JMX username 
 and password. This stops those who want to switch to vnodes from doing so if 
 JMX access requires a username and a password.
 Patch to follow.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


[jira] [Commented] (CASSANDRA-1740) Nodetool commands to query and stop compaction, repair, cleanup and scrub

2013-04-05 Thread Robert Coli (JIRA)

[ 
https://issues.apache.org/jira/browse/CASSANDRA-1740?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13624120#comment-13624120
 ] 

Robert Coli commented on CASSANDRA-1740:


To whom it may concern (people finding this ticket via CHANGES.txt/google 
and/or people who are wondering why their 1.2.x era nodetool help doesn't 
mention stop) :

While this code is in all versions of cassandra =1.1.0, the nodetool help 
line referring to it disappears in 1.2.0 (CASSANDRA-2293) and re-appears in 
1.2.4 (thx driftx!).

 Nodetool commands to query and stop compaction, repair, cleanup and scrub
 -

 Key: CASSANDRA-1740
 URL: https://issues.apache.org/jira/browse/CASSANDRA-1740
 Project: Cassandra
  Issue Type: Improvement
  Components: Tools
Reporter: Chip Salzenberg
Assignee: Vijay
Priority: Minor
  Labels: compaction
 Fix For: 1.1.0

 Attachments: 0001-Patch-to-Stop-compactions.patch, 
 0001-Patch-to-Stop-compactions-v2.patch, 
 0001-Patch-to-Stop-compactions-v3.patch, 
 0001-Patch-to-Stop-compactions-v4.patch, 
 0001-Patch-to-Stop-compactions-v5.patch, 
 0001-Patch-to-Stop-compactions-v6.patch, CASSANDRA-1740.patch

   Original Estimate: 24h
  Remaining Estimate: 24h

 The only way to stop compaction, repair, cleanup, or scrub in progress is to 
 stop and restart the entire Cassandra server.  Please provide nodetool 
 commands to query whether such things are running, and stop them if they are.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


[jira] [Commented] (CASSANDRA-3486) Node Tool command to stop repair

2013-04-05 Thread Robert Coli (JIRA)

[ 
https://issues.apache.org/jira/browse/CASSANDRA-3486?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13624146#comment-13624146
 ] 

Robert Coli commented on CASSANDRA-3486:


Regarding the priority of this ticket, operators frequently report hung repair 
streaming sessions on #cassandra/cassandra-user@. Currently the only thing we 
can tell them is to restart all affected nodes. This presumably gives them a 
bad impression of cassandra. First, because the repair (which they have to run 
once every GCGraceSeconds per best practice) hangs with no useful messaging. 
Second, because the only solution is to restart multiple nodes. It's a little 
bit surprising that this ticket suggests that this negative user experience is 
uncommon enough to not expose some version of this functionality via nodetool.. 
two people's clusters have been in this state in #cassandra so far today and 
it's only 2pm... 

 Node Tool command to stop repair
 

 Key: CASSANDRA-3486
 URL: https://issues.apache.org/jira/browse/CASSANDRA-3486
 Project: Cassandra
  Issue Type: Improvement
  Components: Tools
 Environment: JVM
Reporter: Vijay
Assignee: Vijay
Priority: Minor
  Labels: nodetool, repair, stop
 Fix For: 2.0

 Attachments: 0001-stop-repair-3583.patch


 After CASSANDRA-1740, If the validation compaction is stopped then the repair 
 will hang. This ticket will allow users to kill the original repair.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


[Cassandra Wiki] Trivial Update of MylesFord by MylesFord

2013-04-05 Thread Apache Wiki
Dear Wiki user,

You have subscribed to a wiki page or wiki category on Cassandra Wiki for 
change notification.

The MylesFord page has been changed by MylesFord:
http://wiki.apache.org/cassandra/MylesFord

New page:
There is nothing to say about myself really.BR
I enjoy of finally being a part of apache.org.BR
I just wish I'm useful in some way .BR
BR
My blog post :: [[http://www.7starstore.tk/q/10steptspc-index.html|make my pc 
very fast]]


git commit: fix inable - disable edit

2013-04-05 Thread jbellis
Updated Branches:
  refs/heads/trunk 28e52ded0 - 26bcbeea1


fix inable - disable edit


Project: http://git-wip-us.apache.org/repos/asf/cassandra/repo
Commit: http://git-wip-us.apache.org/repos/asf/cassandra/commit/26bcbeea
Tree: http://git-wip-us.apache.org/repos/asf/cassandra/tree/26bcbeea
Diff: http://git-wip-us.apache.org/repos/asf/cassandra/diff/26bcbeea

Branch: refs/heads/trunk
Commit: 26bcbeea1a2a7af74aa830290b03ecdb56ed16f3
Parents: 28e52de
Author: Jonathan Ellis jbel...@apache.org
Authored: Fri Apr 5 18:43:49 2013 -0500
Committer: Jonathan Ellis jbel...@apache.org
Committed: Fri Apr 5 18:43:53 2013 -0500

--
 src/java/org/apache/cassandra/tools/Shuffle.java |2 +-
 1 files changed, 1 insertions(+), 1 deletions(-)
--


http://git-wip-us.apache.org/repos/asf/cassandra/blob/26bcbeea/src/java/org/apache/cassandra/tools/Shuffle.java
--
diff --git a/src/java/org/apache/cassandra/tools/Shuffle.java 
b/src/java/org/apache/cassandra/tools/Shuffle.java
index 5cca029..341e59d 100644
--- a/src/java/org/apache/cassandra/tools/Shuffle.java
+++ b/src/java/org/apache/cassandra/tools/Shuffle.java
@@ -596,7 +596,7 @@ public class Shuffle extends AbstractJmxClient
 sb.append( ls   List pending 
relocations).append(String.format(%n));
 sb.append( clearClear pending 
relocations).append(String.format(%n));
 sb.append( en[able] Enable 
shuffling).append(String.format(%n));
-sb.append( in[able]Disable 
shuffling).append(String.format(%n%n));
+sb.append( dis[able]Disable 
shuffling).append(String.format(%n%n));
 
 printHelp(shuffle [options] sub-command, sb.toString());
 }



buildbot failure in ASF Buildbot on cassandra-trunk

2013-04-05 Thread buildbot
The Buildbot has detected a new failure on builder cassandra-trunk while 
building cassandra.
Full details are available at:
 http://ci.apache.org/builders/cassandra-trunk/builds/2536

Buildbot URL: http://ci.apache.org/

Buildslave for this Build: portunus_ubuntu

Build Reason: scheduler
Build Source Stamp: [branch trunk] 26bcbeea1a2a7af74aa830290b03ecdb56ed16f3
Blamelist: Jonathan Ellis jbel...@apache.org

BUILD FAILED: failed shell

sincerely,
 -The Buildbot





[Cassandra Wiki] Trivial Update of Wyatt06L by Wyatt06L

2013-04-05 Thread Apache Wiki
Dear Wiki user,

You have subscribed to a wiki page or wiki category on Cassandra Wiki for 
change notification.

The Wyatt06L page has been changed by Wyatt06L:
http://wiki.apache.org/cassandra/Wyatt06L

New page:
これは 全く 愛らしい 花タンキニ デザイナー マルク ・ ジェイコブス。 これはサファリが完了する コンセプト も なる この傾向は航海の ファッション 
この 時間。 このデザイナー タンキニは 利用可能な に 3 色相、ブラック、ロイヤル ブルーや白。 あなたを行う を崇拝する、特大 ダイヤルと 巨大な 数量 
も ですか?BR
BR
Also visit my website: [[http://www.marcjacobsja.com/|マークバイマークジェイコブス 財布]]


[jira] [Created] (CASSANDRA-5432) AntiEntropy Repair Freezing on 1.2.3

2013-04-05 Thread Arya Goudarzi (JIRA)
Arya Goudarzi created CASSANDRA-5432:


 Summary: AntiEntropy Repair Freezing on 1.2.3
 Key: CASSANDRA-5432
 URL: https://issues.apache.org/jira/browse/CASSANDRA-5432
 Project: Cassandra
  Issue Type: Bug
  Components: Core
Affects Versions: 1.2.3
 Environment: Ubuntu 10.04.1 LTS
C* 1.2.3
Sun Java 6 u43
JNA Enabled
Not using VNodes
Reporter: Arya Goudarzi
Priority: Critical


Since I have upgraded our sandbox cluster, I am unable to run repair on any 
node and I am reaching our gc_grace seconds this weekend. Please help. So far, 
I have tried the following suggestions:

- nodetool scrub
- offline scrub
- running repair on each CF separately. Didn't matter. All got stuck the same 
way.

The repair command just gets stuck and the machine is idling. Only the 
following logs are printed for repair job:

 INFO [Thread-42214] 2013-04-05 23:30:27,785 StorageService.java (line 2379) 
Starting repair command #4, repairing 1 ranges for keyspace 
cardspring_production
 INFO [AntiEntropySessions:7] 2013-04-05 23:30:27,789 AntiEntropyService.java 
(line 652) [repair #cc5a9aa0-9e48-11e2-98ba-11bde7670242] new session: will 
sync /X.X.X.190, /X.X.X.43, /X.X.X.56 on range 
(1808575600,42535295865117307932921825930779602032] for 
keyspace_production.[comma separated list of CFs]
 INFO [AntiEntropySessions:7] 2013-04-05 23:30:27,790 AntiEntropyService.java 
(line 858) [repair #cc5a9aa0-9e48-11e2-98ba-11bde7670242] requesting merkle 
trees for BusinessConnectionIndicesEntries (to [/X.X.X.43, /X.X.X.56, 
/X.X.X.190])
 INFO [AntiEntropyStage:1] 2013-04-05 23:30:28,086 AntiEntropyService.java 
(line 214) [repair #cc5a9aa0-9e48-11e2-98ba-11bde7670242] Received merkle tree 
for ColumnFamilyName from /X.X.X.43
 INFO [AntiEntropyStage:1] 2013-04-05 23:30:28,147 AntiEntropyService.java 
(line 214) [repair #cc5a9aa0-9e48-11e2-98ba-11bde7670242] Received merkle tree 
for ColumnFamilyName from /X.X.X.56

Please advise. 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


[jira] [Updated] (CASSANDRA-5411) Unexpired hints can potentially create previously deleted rows

2013-04-05 Thread Arya Goudarzi (JIRA)

 [ 
https://issues.apache.org/jira/browse/CASSANDRA-5411?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Arya Goudarzi updated CASSANDRA-5411:
-

Priority: Minor  (was: Major)

 Unexpired hints can potentially create previously deleted rows
 --

 Key: CASSANDRA-5411
 URL: https://issues.apache.org/jira/browse/CASSANDRA-5411
 Project: Cassandra
  Issue Type: Bug
  Components: Core
Affects Versions: 1.1.10
 Environment: Ubuntu 10.04
Reporter: Arya Goudarzi
Assignee: Brandon Williams
Priority: Minor

 Per discussion here: 
 http://www.mail-archive.com/user@cassandra.apache.org/msg28905.html
 Hints are TTLed to lowest gc_grace_seconds. If we have hints that are not 
 replayed, and the administrator updates schema to have lower gc_grace seconds 
 on some CF, chances are compactions will delete tombstones and history of 
 delete gets lost. If the deleted row is in some hints CF, since the TTL is 
 not updated, chances are it gets replayed and the deleted row comes back to 
 life. 
 I think it would be nice as part of schema migration, to also update the TTLs 
 on hints that already exists on any nodes hints column family. 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


[jira] [Updated] (CASSANDRA-4463) Nodes Don't Restart: Assertion Error on Serializing Cache provider

2013-04-05 Thread Arya Goudarzi (JIRA)

 [ 
https://issues.apache.org/jira/browse/CASSANDRA-4463?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Arya Goudarzi updated CASSANDRA-4463:
-

Priority: Minor  (was: Major)

 Nodes Don't Restart: Assertion Error on Serializing Cache provider
 --

 Key: CASSANDRA-4463
 URL: https://issues.apache.org/jira/browse/CASSANDRA-4463
 Project: Cassandra
  Issue Type: Bug
  Components: Core
Affects Versions: 1.1.5
 Environment: Ubuntu 12.04 Precise
 Cassandra 1.1.5
 Oracle Java 6
Reporter: Arya Goudarzi
Priority: Minor

 I stopped Cassandra on one of our 1.1.2 nodes and I couldn't start it any 
 more. System.log didn't have much useful info but output.log had this:
 java.lang.AssertionError
 at 
 org.apache.cassandra.cache.SerializingCacheProvider$RowCacheSerializer.serialize(SerializingCacheProvider.java:43)
 at 
 org.apache.cassandra.cache.SerializingCacheProvider$RowCacheSerializer.serialize(SerializingCacheProvider.java:39)
 at 
 org.apache.cassandra.cache.SerializingCache.serialize(SerializingCache.java:116)
 at 
 org.apache.cassandra.cache.SerializingCache.put(SerializingCache.java:174)
 at 
 org.apache.cassandra.cache.InstrumentingCache.put(InstrumentingCache.java:45)
 at 
 org.apache.cassandra.db.ColumnFamilyStore.initRowCache(ColumnFamilyStore.java:430)
 at org.apache.cassandra.db.Table.open(Table.java:124)
 at org.apache.cassandra.db.Table.open(Table.java:97)
 at 
 org.apache.cassandra.service.AbstractCassandraDaemon.setup(AbstractCassandraDaemon.java:204)
 at 
 org.apache.cassandra.service.AbstractCassandraDaemon.init(AbstractCassandraDaemon.java:254)
 at 
 com.netflix.priam.cassandra.NFThinCassandraDaemon.init(NFThinCassandraDaemon.java:41)
 at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
 at 
 sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
 at 
 sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
 at java.lang.reflect.Method.invoke(Method.java:597)
 at 
 org.apache.commons.daemon.support.DaemonLoader.load(DaemonLoader.java:212)
 Cannot load daemon
 Service exit with a return value of 3
 Deleting the stuff in saved_caches folder fixed the problem.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


[Cassandra Wiki] Trivial Update of WiltonMag by WiltonMag

2013-04-05 Thread Apache Wiki
Dear Wiki user,

You have subscribed to a wiki page or wiki category on Cassandra Wiki for 
change notification.

The WiltonMag page has been changed by WiltonMag:
http://wiki.apache.org/cassandra/WiltonMag

New page:
My name is Wilton Maggard. I life in Biadene (Italia).BR
[[http://social-promoters.com|social media strategie]]


[Cassandra Wiki] Trivial Update of Allison42 by Allison42

2013-04-05 Thread Apache Wiki
Dear Wiki user,

You have subscribed to a wiki page or wiki category on Cassandra Wiki for 
change notification.

The Allison42 page has been changed by Allison42:
http://wiki.apache.org/cassandra/Allison42?action=diffrev1=11rev2=13

+ They can observe videos about FM, read articles, have a look at news stories, 
all types of information is accessible to them and someone the same as them 
made all of it available FREE.BR
- Every time you may apply for your house loan prequalification, your lender 
will carefully look at history within this domain.BR
- However, Barcelona are adamant that they will not allow the striker leave on 
loan and may only entertain a critical offer to get a permanent transfer. Not 
many individuals realize it but statistically, you can find a significant 
variety of people saved literally from immersing themselves in a bad loan.BR
- The rest in the amount might be paid on easy timely repayments. Hardship Home 
Loan Modifications - At Risk Homeowners.BR
  BR
- Here is my web site: [[|payday lones]]
+ Assuming you've got got the bucks for any deposit, probably the most a bank 
will lend is between 85% and 90% of these valuation of your property which can 
be lower than the price tag. All of the above mistakes might be easily avoided 
using the right approach and attitude. He is reported as saying in The Sun: 
'This is really a new era for Milan.BR
+ But, should your next paycheck will be below 1 week when you possess the 
financing, you could possibly be exempt out of this guideline.BR
+ BR
+ My web page; 
[[http://www.letweplay.com/blog/view/18044/throughout-national-healthcare-debt-tie-and-bachmann039s-bid|instant
 loans online]]
  


[Cassandra Wiki] Trivial Update of Diane21G by Diane21G

2013-04-05 Thread Apache Wiki
Dear Wiki user,

You have subscribed to a wiki page or wiki category on Cassandra Wiki for 
change notification.

The Diane21G page has been changed by Diane21G:
http://wiki.apache.org/cassandra/Diane21G

New page:
Name: Diane MatthewsBR
Age: 24BR
Country: United StatesBR
Town: Stanley BR
ZIP: 58784BR
Street: 3190 Courtright StreetBR
BR
Look into my web site - [[http://Www.Cotomarketing.com|Read More Listed here]]


[Cassandra Wiki] Trivial Update of KristinWC by KristinWC

2013-04-05 Thread Apache Wiki
Dear Wiki user,

You have subscribed to a wiki page or wiki category on Cassandra Wiki for 
change notification.

The KristinWC page has been changed by KristinWC:
http://wiki.apache.org/cassandra/KristinWC

New page:
My name is Nick Blackmon. I life in Seubersdorf (Germany).BR
BR
BR
Also visit my webpage :: 
[[http://ensynefo.com/blogs/12341/16116/the-smartest-way-to-buy-car-insu|click 
through the up coming web page]]


[Cassandra Wiki] Trivial Update of DieterMul by DieterMul

2013-04-05 Thread Apache Wiki
Dear Wiki user,

You have subscribed to a wiki page or wiki category on Cassandra Wiki for 
change notification.

The DieterMul page has been changed by DieterMul:
http://wiki.apache.org/cassandra/DieterMul

New page:
A 優れた 女の子 名前付きのガブリエル ・ シャネルは 1883 年にフランスで生まれていた。 世紀 その後、シャネルが になる は チーフ から、パターン 
地球。BR
BR
Also visit my homepage ... [[http://www.shanerutenpos.com/|シャネル バッグ]]


  1   2   >