date:20110518


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

Pavel Yaskevich updated CASSANDRA-2616:
---

Attachment: (was: CASSANDRA-2616-v2.patch)

 Add DROP INDEX command to CLI
 ---

 Key: CASSANDRA-2616
 URL: https://issues.apache.org/jira/browse/CASSANDRA-2616
 Project: Cassandra
  Issue Type: New Feature
Reporter: Pavel Yaskevich
Assignee: Pavel Yaskevich
 Fix For: 0.8.1

 Attachments: CASSANDRA-2616.patch




--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (CASSANDRA-2616) Add DROP INDEX command to CLI


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

Pavel Yaskevich updated CASSANDRA-2616:
---

Attachment: CASSANDRA-2616-v2.patch

 Add DROP INDEX command to CLI
 ---

 Key: CASSANDRA-2616
 URL: https://issues.apache.org/jira/browse/CASSANDRA-2616
 Project: Cassandra
  Issue Type: New Feature
Reporter: Pavel Yaskevich
Assignee: Pavel Yaskevich
 Fix For: 0.8.1

 Attachments: CASSANDRA-2616.patch




--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (CASSANDRA-2616) Add DROP INDEX command to CLI


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

Pavel Yaskevich updated CASSANDRA-2616:
---

Attachment: CASSANDRA-2616-v2.patch

 Add DROP INDEX command to CLI
 ---

 Key: CASSANDRA-2616
 URL: https://issues.apache.org/jira/browse/CASSANDRA-2616
 Project: Cassandra
  Issue Type: New Feature
Reporter: Pavel Yaskevich
Assignee: Pavel Yaskevich
 Fix For: 0.8.1

 Attachments: CASSANDRA-2616-v2.patch, CASSANDRA-2616.patch




--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Created] (CASSANDRA-2663) JDBC driver for CQL works only with Strings

2011-05-18 Thread Roman Kuzmin (JIRA)

JDBC driver for CQL works only with Strings
---

 Key: CASSANDRA-2663
 URL: https://issues.apache.org/jira/browse/CASSANDRA-2663
 Project: Cassandra
  Issue Type: Bug
  Components: API
Affects Versions: 0.8.0 beta 2
 Environment: It happens to JDBC driver for both: 0.8.0 beta version 
and 0.8.0-rc1
Reporter: Roman Kuzmin


CassandraPreparedStatement.java

Line 141:

String stringParam = makeCqlString(type.toString(param));

It crashes with ClassCastException for all parameters that are not Strings. It 
is because, when the method applyDualBindings is called from makeUpdate it 
ALWAYS get one and the same type as parameter. In fact it is a comparator of 
columnfamily itself.

In my case it is UTF8Type. And UTF8Type.toString() method expects only Strings.

I think it must be column-dependent.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Created] (CASSANDRA-2664) JDBC driver for CQL works only with Strings

2011-05-18 Thread Roman Kuzmin (JIRA)

JDBC driver for CQL works only with Strings
---

 Key: CASSANDRA-2664
 URL: https://issues.apache.org/jira/browse/CASSANDRA-2664
 Project: Cassandra
  Issue Type: Bug
  Components: API
Affects Versions: 0.8.0 beta 2
 Environment: It happens to JDBC driver for both: 0.8.0 beta version 
and 0.8.0-rc1
Reporter: Roman Kuzmin


CassandraPreparedStatement.java

Line 141:

String stringParam = makeCqlString(type.toString(param));

It crashes with ClassCastException for all parameters that are not Strings. It 
is because, when the method applyDualBindings is called from makeUpdate it 
ALWAYS get one and the same type as parameter. In fact it is a comparator of 
columnfamily itself.

In my case it is UTF8Type. And UTF8Type.toString() method expects only Strings.

I think it must be column-dependent.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

svn commit: r1124257 - /cassandra/tags/cassandra-0.7.6/

2011-05-18 Thread slebresne

Author: slebresne
Date: Wed May 18 13:32:14 2011
New Revision: 1124257

URL: http://svn.apache.org/viewvc?rev=1124257view=rev
Log:
Creating 0.7.6 tag

Added:
cassandra/tags/cassandra-0.7.6/   (props changed)
  - copied from r1102594, cassandra/branches/cassandra-0.7/

Propchange: cassandra/tags/cassandra-0.7.6/
--
--- svn:ignore (added)
+++ svn:ignore Wed May 18 13:32:14 2011
@@ -0,0 +1,8 @@
+.classpath
+.project
+.settings
+temp-testng-customsuite.xml
+build
+build.properties
+.idea
+out

Propchange: cassandra/tags/cassandra-0.7.6/
--
--- svn:mergeinfo (added)
+++ svn:mergeinfo Wed May 18 13:32:14 2011
@@ -0,0 +1,9 @@
+/cassandra/branches/cassandra-0.6:922689-1081914,1083000
+/cassandra/branches/cassandra-0.7:1026516,1035666,1050269
+/cassandra/branches/cassandra-0.7.0:1053690-1055654
+/cassandra/tags/cassandra-0.7.0-rc3:1051699-1053689
+/cassandra/trunk:1026516-1026734,1028929
+/incubator/cassandra/branches/cassandra-0.3:774578-796573
+/incubator/cassandra/branches/cassandra-0.4:810145-834239,834349-834350
+/incubator/cassandra/branches/cassandra-0.5:72-915439
+/incubator/cassandra/branches/cassandra-0.6:911237-922688

[jira] [Commented] (CASSANDRA-2664) JDBC driver for CQL works only with Strings


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

Jonathan Ellis commented on CASSANDRA-2664:
---

How are you getting that path to be invoked w/ non-Strings?

Can you submit a patch to PreparedStatementTest that reproduces the error?

 JDBC driver for CQL works only with Strings
 ---

 Key: CASSANDRA-2664
 URL: https://issues.apache.org/jira/browse/CASSANDRA-2664
 Project: Cassandra
  Issue Type: Bug
  Components: API
Affects Versions: 0.8.0 beta 2
 Environment: It happens to JDBC driver for both: 0.8.0 beta version 
 and 0.8.0-rc1
Reporter: Roman Kuzmin
  Labels: cql, jdbc
   Original Estimate: 4h
  Remaining Estimate: 4h

 CassandraPreparedStatement.java
 Line 141:
 String stringParam = makeCqlString(type.toString(param));
 It crashes with ClassCastException for all parameters that are not Strings. 
 It is because, when the method applyDualBindings is called from makeUpdate it 
 ALWAYS get one and the same type as parameter. In fact it is a comparator 
 of columnfamily itself.
 In my case it is UTF8Type. And UTF8Type.toString() method expects only 
 Strings.
 I think it must be column-dependent.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Created] (CASSANDRA-2665) Debian 0.7.5-0.7.6 upgrade: Use of uninitialized value

2011-05-18 Thread Viliam Holub (JIRA)

Debian 0.7.5-0.7.6 upgrade: Use of uninitialized value
---

 Key: CASSANDRA-2665
 URL: https://issues.apache.org/jira/browse/CASSANDRA-2665
 Project: Cassandra
  Issue Type: Bug
  Components: Packaging
Affects Versions: 0.7.6
 Environment: Debian 5.0.8
Reporter: Viliam Holub


When trying to upgrade Cassandra from 0.7.5 to 0.7.6 I'm getting this error 
message:

Setting up cassandra (0.7.6) ...
Installing new version of config file /etc/init.d/cassandra ...
Use of uninitialized value $level in string ne at /usr/sbin/update-rc.d line 
199.
Use of uninitialized value $level in pattern match (m//) at 
/usr/sbin/update-rc.d line 200.
update-rc.d: error: expected runlevel [0-9S] (did you forget . ?)
usage: update-rc.d [-n] [-f] basename remove
   update-rc.d [-n] basename defaults [NN | SS KK]
   update-rc.d [-n] basename start|stop NN runlvl [runlvl] [...] .
-n: not really
-f: force
dpkg: error processing cassandra (--configure):
 subprocess post-installation script returned error exit status 1
Errors were encountered while processing:
 cassandra
E: Sub-process /usr/bin/dpkg returned an error code (1)
A package failed to install.  Trying to recover:
Setting up cassandra (0.7.6) ...
Use of uninitialized value $level in string ne at /usr/sbin/update-rc.d line 
199.
Use of uninitialized value $level in pattern match (m//) at 
/usr/sbin/update-rc.d line 200.
update-rc.d: error: expected runlevel [0-9S] (did you forget . ?)
usage: update-rc.d [-n] [-f] basename remove
   update-rc.d [-n] basename defaults [NN | SS KK]
   update-rc.d [-n] basename start|stop NN runlvl [runlvl] [...] .
-n: not really
-f: force
dpkg: error processing cassandra (--configure):
 subprocess post-installation script returned error exit status 1
Errors were encountered while processing:
 cassandra


--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (CASSANDRA-2616) Add DROP INDEX command to CLI


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

Jonathan Ellis commented on CASSANDRA-2616:
---

should we also support drop index indexname?

 Add DROP INDEX command to CLI
 ---

 Key: CASSANDRA-2616
 URL: https://issues.apache.org/jira/browse/CASSANDRA-2616
 Project: Cassandra
  Issue Type: New Feature
Reporter: Pavel Yaskevich
Assignee: Pavel Yaskevich
 Fix For: 0.8.1

 Attachments: CASSANDRA-2616-v2.patch, CASSANDRA-2616.patch




--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

svn commit: r1124273 - in /cassandra/branches/cassandra-0.8: ./ src/java/org/apache/cassandra/cli/ src/resources/org/apache/cassandra/cli/ test/unit/org/apache/cassandra/cli/

2011-05-18 Thread jbellis

Author: jbellis
Date: Wed May 18 14:07:55 2011
New Revision: 1124273

URL: http://svn.apache.org/viewvc?rev=1124273view=rev
Log:
add DROP INDEX support to CLI
patch by pyaskevich; reviewed by jbellis for CASSANDRA-2616

Modified:
cassandra/branches/cassandra-0.8/CHANGES.txt
cassandra/branches/cassandra-0.8/src/java/org/apache/cassandra/cli/Cli.g

cassandra/branches/cassandra-0.8/src/java/org/apache/cassandra/cli/CliClient.java

cassandra/branches/cassandra-0.8/src/resources/org/apache/cassandra/cli/CliHelp.yaml

cassandra/branches/cassandra-0.8/test/unit/org/apache/cassandra/cli/CliTest.java

Modified: cassandra/branches/cassandra-0.8/CHANGES.txt
URL: 
http://svn.apache.org/viewvc/cassandra/branches/cassandra-0.8/CHANGES.txt?rev=1124273r1=1124272r2=1124273view=diff
==
--- cassandra/branches/cassandra-0.8/CHANGES.txt (original)
+++ cassandra/branches/cassandra-0.8/CHANGES.txt Wed May 18 14:07:55 2011
@@ -4,9 +4,10 @@
  * update CQL consistency levels (CASSANDRA-2566)
  * mark BRAF buffer invalid post-flush so we don't re-flush partial
buffers again, especially on CL writes (CASSANDRA-2660)
+ * add DROP INDEX support to CLI (CASSANDRA-2616)
 
 
-0.8.0-rc1
+0.8.0-rc1 
  * faster flushes and compaction from fixing excessively pessimistic 
rebuffering in BRAF (CASSANDRA-2581)
  * fix returning null column values in the python cql driver (CASSANDRA-2593)

Modified: 
cassandra/branches/cassandra-0.8/src/java/org/apache/cassandra/cli/Cli.g
URL: 
http://svn.apache.org/viewvc/cassandra/branches/cassandra-0.8/src/java/org/apache/cassandra/cli/Cli.g?rev=1124273r1=1124272r2=1124273view=diff
==
--- cassandra/branches/cassandra-0.8/src/java/org/apache/cassandra/cli/Cli.g 
(original)
+++ cassandra/branches/cassandra-0.8/src/java/org/apache/cassandra/cli/Cli.g 
Wed May 18 14:07:55 2011
@@ -61,6 +61,7 @@ tokens {
 NODE_TRUNCATE;
 NODE_ASSUME;
 NODE_CONSISTENCY_LEVEL;
+NODE_DROP_INDEX;
 
 // Internal Nodes.
 NODE_COLUMN_ACCESS;
@@ -160,6 +161,7 @@ statement
 | truncateStatement
 | assumeStatement
 | consistencyLevelStatement
+| dropIndex
 | - ^(NODE_NO_OP)
 ;
 
@@ -203,6 +205,8 @@ helpStatement
 - ^(NODE_HELP NODE_DEL_KEYSPACE)
 | HELP DROP COLUMN FAMILY 
 - ^(NODE_HELP NODE_DEL_COLUMN_FAMILY)
+| HELP DROP INDEX
+- ^(NODE_HELP NODE_DROP_INDEX)
 | HELP GET 
 - ^(NODE_HELP NODE_THRIFT_GET)
 | HELP SET 
@@ -337,6 +341,11 @@ delColumnFamily
 - ^(NODE_DEL_COLUMN_FAMILY columnFamily)
 ;
 
+dropIndex
+: DROP INDEX ON columnFamily '.' columnName
+- ^(NODE_DROP_INDEX columnFamily columnName)
+;
+
 showVersion
 : SHOW API_VERSION
 - ^(NODE_SHOW_VERSION)
@@ -562,6 +571,8 @@ TRUNCATE:'TRUNCATE';
 ASSUME:  'ASSUME';
 TTL: 'TTL';
 CONSISTENCYLEVEL:   'CONSISTENCYLEVEL';
+INDEX:   'INDEX';
+ON:  'ON';
 
 IP_ADDRESS 
 : IntegerPositiveLiteral '.' IntegerPositiveLiteral '.' 
IntegerPositiveLiteral '.' IntegerPositiveLiteral

Modified: 
cassandra/branches/cassandra-0.8/src/java/org/apache/cassandra/cli/CliClient.java
URL: 
http://svn.apache.org/viewvc/cassandra/branches/cassandra-0.8/src/java/org/apache/cassandra/cli/CliClient.java?rev=1124273r1=1124272r2=1124273view=diff
==
--- 
cassandra/branches/cassandra-0.8/src/java/org/apache/cassandra/cli/CliClient.java
 (original)
+++ 
cassandra/branches/cassandra-0.8/src/java/org/apache/cassandra/cli/CliClient.java
 Wed May 18 14:07:55 2011
@@ -269,6 +269,10 @@ public class CliClient
 case CliParser.NODE_THRIFT_DECR:
 executeIncr(tree, -1L);
 break;
+case CliParser.NODE_DROP_INDEX:
+executeDropIndex(tree);
+break;
+
 case CliParser.NODE_NO_OP:
 // comment lines come here; they are treated as no ops.
 break;
@@ -1295,6 +1299,58 @@ public class CliClient
 printSliceList(columnFamilyDef, keySlices);
 }
 
+// DROP INDEX ON CF.COLUMN
+private void executeDropIndex(Tree statement)
+{
+if (!CliMain.isConnected() || !hasKeySpace())
+return;
+
+// getColumnFamily will check if CF exists for us
+String columnFamily = CliCompiler.getColumnFamily(statement, 
keyspacesMap.get(keySpace).cf_defs);
+String rawColumName = statement.getChild(1).getText();
+
+CfDef cfDef = getCfDef(columnFamily);
+
+ByteBuffer columnName = columnNameAsBytes(rawColumName, cfDef);
+
+boolean foundColumn = false;
+
+for (ColumnDef column : cfDef.getColumn_metadata())
+{
+if (column.name.equals(columnName))
+{
+

[jira] [Commented] (CASSANDRA-2616) Add DROP INDEX command to CLI


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

Jonathan Ellis commented on CASSANDRA-2616:
---

Eh, it's not worth it in the cli.  But when we do this for CQL let's support 
the name form too.

 Add DROP INDEX command to CLI
 ---

 Key: CASSANDRA-2616
 URL: https://issues.apache.org/jira/browse/CASSANDRA-2616
 Project: Cassandra
  Issue Type: New Feature
Reporter: Pavel Yaskevich
Assignee: Pavel Yaskevich
 Fix For: 0.8.1

 Attachments: CASSANDRA-2616-v2.patch, CASSANDRA-2616.patch




--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[Cassandra Wiki] Update of ArticlesAndPresentations by JonathanEllis

2011-05-18 Thread Apache Wiki

Dear Wiki user,

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

The ArticlesAndPresentations page has been changed by JonathanEllis.
http://wiki.apache.org/cassandra/ArticlesAndPresentations?action=diffrev1=120rev2=121

--

   * 
[[http://www.slideshare.net/benjaminblack/introduction-to-cassandra-replication-and-consistency|Introduction
 to Cassandra Replication and Consistency]]
  
  = Recommended advanced material =
+  * [[http://devops.com/2011/03/08/cassandra-and-puppet/|Cassandra and Puppet]]
   * What's new in Cassandra 
[[http://www.datastax.com/blog/annotated-changelog-cassandra-061|0.6.1]], 
[[http://www.datastax.com/blog/cassandra-annotated-changelog-062|0.6.2]], 
[[http://www.datastax.com/blog/cassandra-annotated-changelog-063|0.6.3]], 
[[http://www.datastax.com/blog/whats-new-cassandra-064|0.6.4]], 
[[http://www.datastax.com/blog/whats-new-cassandra-065|0.6.5]]
   * [[http://riptano.blip.tv/file/4011985/|Cassandra performance tuning]]
   * [[http://riptano.blip.tv/file/4012133/|Cassandra troubleshooting: out of 
the shadows]]

[jira] [Commented] (CASSANDRA-2616) Add DROP INDEX command to CLI


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

Pavel Yaskevich commented on CASSANDRA-2616:


Sure.

 Add DROP INDEX command to CLI
 ---

 Key: CASSANDRA-2616
 URL: https://issues.apache.org/jira/browse/CASSANDRA-2616
 Project: Cassandra
  Issue Type: New Feature
Reporter: Pavel Yaskevich
Assignee: Pavel Yaskevich
 Fix For: 0.8.1

 Attachments: CASSANDRA-2616-v2.patch, CASSANDRA-2616.patch




--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (CASSANDRA-2662) Nodes get ignored by dynamic snitch when read repair chance is zero

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

Brandon Williams commented on CASSANDRA-2662:
-

To clarify what this patch does: on the first round, behavior is unchanged, it
will fall back to the subsnitch as usual. On the second round however, the
nodes will have scores so the dynamic snitch will determine the best host.
This seems like a good idea, but I think we should proceed cautiously with
regard to CASSANDRA-1314. This is certainly going to blow the cache on the
second round, since the unpinned hosts at zero are guaranteed to be ranked
higher than the pinned one. However, in the current implementation, the
badness threshold in CASSANDRA-1519 can never take effect at RR = 0 since the
scores of the other replicas will always be null, and thus diversion to the
subsnitch will always occur, returning the pinned replica. With this patch,
the second replica is likely to end up being the pinned one, which I think will
be ok, as long as all coordinators agree, though this might not always be the
case.

Nodes get ignored by dynamic snitch when read repair chance is zero
---

Key: CASSANDRA-2662
URL: https://issues.apache.org/jira/browse/CASSANDRA-2662
Project: Cassandra
Issue Type: Bug
Components: Core
Affects Versions: 0.7.6
Reporter: Daniel Doubleday
Priority: Trivial
Attachments: dynsnitch.patch

DynamicEndpointSnitch falls back to subsnitch when one of the scores of the
endpoints being compared is missing.
This leads to a stable order of hosts until reads will lead to recorded
scores.
If setting read repair chance to 0 and reads are performed with quorum then
(rf - # quorum nodes) will never get reads.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Assigned] (CASSANDRA-2662) Nodes get ignored by dynamic snitch when read repair chance is zero


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

Brandon Williams reassigned CASSANDRA-2662:
---

Assignee: Brandon Williams

 Nodes get ignored by dynamic snitch when read repair chance is zero
 ---

 Key: CASSANDRA-2662
 URL: https://issues.apache.org/jira/browse/CASSANDRA-2662
 Project: Cassandra
  Issue Type: Bug
  Components: Core
Affects Versions: 0.7.6
Reporter: Daniel Doubleday
Assignee: Brandon Williams
Priority: Trivial
 Attachments: dynsnitch.patch


 DynamicEndpointSnitch falls back to subsnitch when one of the scores of the 
 endpoints being compared is missing.
 This leads to a stable order of hosts until reads will lead to recorded 
 scores. 
 If setting read repair chance to 0 and reads are performed with quorum then 
 (rf - # quorum nodes) will never get reads.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (CASSANDRA-2616) Add DROP INDEX command to CLI

2011-05-18 Thread Hudson (JIRA)


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

Hudson commented on CASSANDRA-2616:
---

Integrated in Cassandra-0.8 #113 (See 
[https://builds.apache.org/hudson/job/Cassandra-0.8/113/])
add DROP INDEX support to CLI
patch by pyaskevich; reviewed by jbellis for CASSANDRA-2616

jbellis : 
http://svn.apache.org/viewcvs.cgi/?root=Apache-SVNview=revrev=1124273
Files : 
* 
/cassandra/branches/cassandra-0.8/src/java/org/apache/cassandra/cli/CliClient.java
* /cassandra/branches/cassandra-0.8/CHANGES.txt
* 
/cassandra/branches/cassandra-0.8/src/resources/org/apache/cassandra/cli/CliHelp.yaml
* 
/cassandra/branches/cassandra-0.8/test/unit/org/apache/cassandra/cli/CliTest.java
* /cassandra/branches/cassandra-0.8/src/java/org/apache/cassandra/cli/Cli.g


 Add DROP INDEX command to CLI
 ---

 Key: CASSANDRA-2616
 URL: https://issues.apache.org/jira/browse/CASSANDRA-2616
 Project: Cassandra
  Issue Type: New Feature
Reporter: Pavel Yaskevich
Assignee: Pavel Yaskevich
 Fix For: 0.8.1

 Attachments: CASSANDRA-2616-v2.patch, CASSANDRA-2616.patch




--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (CASSANDRA-2481) C* .deb installs C* init.d scripts such that C* comes up before mdadm and related

2011-05-18 Thread Gasol Wu (JIRA)


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

Gasol Wu commented on CASSANDRA-2481:
-

{quote}
Installing new version of config file /etc/init.d/cassandra ...
update-rc.d: error: start|stop arguments not terminated by .
{quote}

find dh_installinit in debian/rules and edit like following line.

dh_installinit -u'start 50 2 3 4 5 . stop 50 0 1 6 .'

it works for me.

 C* .deb installs C* init.d scripts such that C* comes up before mdadm and 
 related
 -

 Key: CASSANDRA-2481
 URL: https://issues.apache.org/jira/browse/CASSANDRA-2481
 Project: Cassandra
  Issue Type: Bug
  Components: Packaging
Reporter: Matthew F. Dennis
Assignee: paul cannon
Priority: Minor
 Fix For: 0.7.6, 0.8.0

 Attachments: 2481.txt


 the C* .deb packages install the init.d scripts at S20 which is before mdadm 
 and various other services.  This means that when a node reboots that C* is 
 started before the RAID sets are up and mounted causing C* to think it has no 
 data and attempt bootstrapping again.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (CASSANDRA-2659) Improve forceDeserialize/getCompactedRow encapsulation


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

Jonathan Ellis updated CASSANDRA-2659:
--

Attachment: 2659-v3.txt

v3 updates ValidationCompactionIterator to create a controller w/ 
forceDeserialize, and removes the echoing special case from LCR.write.

 Improve forceDeserialize/getCompactedRow encapsulation
 --

 Key: CASSANDRA-2659
 URL: https://issues.apache.org/jira/browse/CASSANDRA-2659
 Project: Cassandra
  Issue Type: Improvement
  Components: Core
Reporter: Jonathan Ellis
Assignee: Jonathan Ellis
Priority: Minor
 Fix For: 0.8.1

 Attachments: 2659-v2.txt, 2659-v3.txt, 2659.txt




--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Assigned] (CASSANDRA-2665) Debian 0.7.5-0.7.6 upgrade: Use of uninitialized value

2011-05-18 Thread paul cannon (JIRA)


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

paul cannon reassigned CASSANDRA-2665:
--

Assignee: paul cannon

 Debian 0.7.5-0.7.6 upgrade: Use of uninitialized value
 ---

 Key: CASSANDRA-2665
 URL: https://issues.apache.org/jira/browse/CASSANDRA-2665
 Project: Cassandra
  Issue Type: Bug
  Components: Packaging
Affects Versions: 0.7.6
 Environment: Debian 5.0.8
Reporter: Viliam Holub
Assignee: paul cannon

 When trying to upgrade Cassandra from 0.7.5 to 0.7.6 I'm getting this error 
 message:
 Setting up cassandra (0.7.6) ...
 Installing new version of config file /etc/init.d/cassandra ...
 Use of uninitialized value $level in string ne at /usr/sbin/update-rc.d line 
 199.
 Use of uninitialized value $level in pattern match (m//) at 
 /usr/sbin/update-rc.d line 200.
 update-rc.d: error: expected runlevel [0-9S] (did you forget . ?)
 usage: update-rc.d [-n] [-f] basename remove
update-rc.d [-n] basename defaults [NN | SS KK]
update-rc.d [-n] basename start|stop NN runlvl [runlvl] [...] .
   -n: not really
   -f: force
 dpkg: error processing cassandra (--configure):
  subprocess post-installation script returned error exit status 1
 Errors were encountered while processing:
  cassandra
 E: Sub-process /usr/bin/dpkg returned an error code (1)
 A package failed to install.  Trying to recover:
 Setting up cassandra (0.7.6) ...
 Use of uninitialized value $level in string ne at /usr/sbin/update-rc.d line 
 199.
 Use of uninitialized value $level in pattern match (m//) at 
 /usr/sbin/update-rc.d line 200.
 update-rc.d: error: expected runlevel [0-9S] (did you forget . ?)
 usage: update-rc.d [-n] [-f] basename remove
update-rc.d [-n] basename defaults [NN | SS KK]
update-rc.d [-n] basename start|stop NN runlvl [runlvl] [...] .
   -n: not really
   -f: force
 dpkg: error processing cassandra (--configure):
  subprocess post-installation script returned error exit status 1
 Errors were encountered while processing:
  cassandra

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (CASSANDRA-2481) C* .deb installs C* init.d scripts such that C* comes up before mdadm and related

2011-05-18 Thread paul cannon (JIRA)


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

paul cannon updated CASSANDRA-2481:
---

Attachment: 2481-fix.txt

fix for previous

 C* .deb installs C* init.d scripts such that C* comes up before mdadm and 
 related
 -

 Key: CASSANDRA-2481
 URL: https://issues.apache.org/jira/browse/CASSANDRA-2481
 Project: Cassandra
  Issue Type: Bug
  Components: Packaging
Reporter: Matthew F. Dennis
Assignee: paul cannon
Priority: Minor
 Fix For: 0.7.6, 0.8.0

 Attachments: 2481-fix.txt, 2481.txt


 the C* .deb packages install the init.d scripts at S20 which is before mdadm 
 and various other services.  This means that when a node reboots that C* is 
 started before the RAID sets are up and mounted causing C* to think it has no 
 data and attempt bootstrapping again.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Resolved] (CASSANDRA-2665) Debian 0.7.5-0.7.6 upgrade: Use of uninitialized value

2011-05-18 Thread paul cannon (JIRA)


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

paul cannon resolved CASSANDRA-2665.


Resolution: Duplicate

This was caused by an incomplete fix for CASSANDRA-2481, which is reopened to 
address this issue.

 Debian 0.7.5-0.7.6 upgrade: Use of uninitialized value
 ---

 Key: CASSANDRA-2665
 URL: https://issues.apache.org/jira/browse/CASSANDRA-2665
 Project: Cassandra
  Issue Type: Bug
  Components: Packaging
Affects Versions: 0.7.6
 Environment: Debian 5.0.8
Reporter: Viliam Holub
Assignee: paul cannon

 When trying to upgrade Cassandra from 0.7.5 to 0.7.6 I'm getting this error 
 message:
 Setting up cassandra (0.7.6) ...
 Installing new version of config file /etc/init.d/cassandra ...
 Use of uninitialized value $level in string ne at /usr/sbin/update-rc.d line 
 199.
 Use of uninitialized value $level in pattern match (m//) at 
 /usr/sbin/update-rc.d line 200.
 update-rc.d: error: expected runlevel [0-9S] (did you forget . ?)
 usage: update-rc.d [-n] [-f] basename remove
update-rc.d [-n] basename defaults [NN | SS KK]
update-rc.d [-n] basename start|stop NN runlvl [runlvl] [...] .
   -n: not really
   -f: force
 dpkg: error processing cassandra (--configure):
  subprocess post-installation script returned error exit status 1
 Errors were encountered while processing:
  cassandra
 E: Sub-process /usr/bin/dpkg returned an error code (1)
 A package failed to install.  Trying to recover:
 Setting up cassandra (0.7.6) ...
 Use of uninitialized value $level in string ne at /usr/sbin/update-rc.d line 
 199.
 Use of uninitialized value $level in pattern match (m//) at 
 /usr/sbin/update-rc.d line 200.
 update-rc.d: error: expected runlevel [0-9S] (did you forget . ?)
 usage: update-rc.d [-n] [-f] basename remove
update-rc.d [-n] basename defaults [NN | SS KK]
update-rc.d [-n] basename start|stop NN runlvl [runlvl] [...] .
   -n: not really
   -f: force
 dpkg: error processing cassandra (--configure):
  subprocess post-installation script returned error exit status 1
 Errors were encountered while processing:
  cassandra

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

svn commit: r1124338 - /cassandra/branches/cassandra-0.7/debian/rules

2011-05-18 Thread brandonwilliams

Author: brandonwilliams
Date: Wed May 18 17:10:14 2011
New Revision: 1124338

URL: http://svn.apache.org/viewvc?rev=1124338view=rev
Log:
Fix for dh_installinit syntax for CASSANDRA-2481
Patch by Paul Cannon, reviewed by brandonwilliams

Modified:
cassandra/branches/cassandra-0.7/debian/rules

Modified: cassandra/branches/cassandra-0.7/debian/rules
URL: 
http://svn.apache.org/viewvc/cassandra/branches/cassandra-0.7/debian/rules?rev=1124338r1=1124337r2=1124338view=diff
==
--- cassandra/branches/cassandra-0.7/debian/rules (original)
+++ cassandra/branches/cassandra-0.7/debian/rules Wed May 18 17:10:14 2011
@@ -46,7 +46,7 @@ binary-indep: build install
dh_testdir
dh_testroot
dh_installchangelogs
-   dh_installinit -u'start 50 2 3 4 5 . stop 50 0 1 6'
+   dh_installinit -u'start 50 2 3 4 5 . stop 50 0 1 6 .'
dh_installdocs README.txt CHANGES.txt NEWS.txt
dh_compress
dh_fixperms

[jira] [Commented] (CASSANDRA-2481) C* .deb installs C* init.d scripts such that C* comes up before mdadm and related


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

Brandon Williams commented on CASSANDRA-2481:
-

Fix committed.

 C* .deb installs C* init.d scripts such that C* comes up before mdadm and 
 related
 -

 Key: CASSANDRA-2481
 URL: https://issues.apache.org/jira/browse/CASSANDRA-2481
 Project: Cassandra
  Issue Type: Bug
  Components: Packaging
Affects Versions: 0.7.6, 0.8.0
Reporter: Matthew F. Dennis
Assignee: paul cannon
Priority: Minor
 Fix For: 0.7.6, 0.8.0

 Attachments: 2481-fix.txt, 2481.txt


 the C* .deb packages install the init.d scripts at S20 which is before mdadm 
 and various other services.  This means that when a node reboots that C* is 
 started before the RAID sets are up and mounted causing C* to think it has no 
 data and attempt bootstrapping again.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (CASSANDRA-2481) C* .deb installs C* init.d scripts such that C* comes up before mdadm and related

2011-05-18 Thread Hudson (JIRA)


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

Hudson commented on CASSANDRA-2481:
---

Integrated in Cassandra-0.7 #488 (See 
[https://builds.apache.org/hudson/job/Cassandra-0.7/488/])
Fix for dh_installinit syntax for CASSANDRA-2481
Patch by Paul Cannon, reviewed by brandonwilliams

brandonwilliams : 
http://svn.apache.org/viewcvs.cgi/?root=Apache-SVNview=revrev=1124338
Files : 
* /cassandra/branches/cassandra-0.7/debian/rules


 C* .deb installs C* init.d scripts such that C* comes up before mdadm and 
 related
 -

 Key: CASSANDRA-2481
 URL: https://issues.apache.org/jira/browse/CASSANDRA-2481
 Project: Cassandra
  Issue Type: Bug
  Components: Packaging
Affects Versions: 0.7.6, 0.8.0
Reporter: Matthew F. Dennis
Assignee: paul cannon
Priority: Minor
 Fix For: 0.7.6, 0.8.0

 Attachments: 2481-fix.txt, 2481.txt


 the C* .deb packages install the init.d scripts at S20 which is before mdadm 
 and various other services.  This means that when a node reboots that C* is 
 started before the RAID sets are up and mounted causing C* to think it has no 
 data and attempt bootstrapping again.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

svn commit: r1124355 - /cassandra/branches/cassandra-0.8/src/java/org/apache/cassandra/db/CompactionManager.java

2011-05-18 Thread jbellis

Author: jbellis
Date: Wed May 18 17:56:14 2011
New Revision: 1124355

URL: http://svn.apache.org/viewvc?rev=1124355view=rev
Log:
r/m unused code

Modified:

cassandra/branches/cassandra-0.8/src/java/org/apache/cassandra/db/CompactionManager.java

Modified: 
cassandra/branches/cassandra-0.8/src/java/org/apache/cassandra/db/CompactionManager.java
URL: 
http://svn.apache.org/viewvc/cassandra/branches/cassandra-0.8/src/java/org/apache/cassandra/db/CompactionManager.java?rev=1124355r1=1124354r2=1124355view=diff
==
--- 
cassandra/branches/cassandra-0.8/src/java/org/apache/cassandra/db/CompactionManager.java
 (original)
+++ 
cassandra/branches/cassandra-0.8/src/java/org/apache/cassandra/db/CompactionManager.java
 Wed May 18 17:56:14 2011
@@ -1169,31 +1169,6 @@ public class CompactionManager implement
 }
 }
 
-public void checkAllColumnFamilies() throws IOException
-{
-// perform estimates
-for (final ColumnFamilyStore cfs : ColumnFamilyStore.all())
-{
-Runnable runnable = new Runnable()
-{
-public void run ()
-{
-logger.debug(Estimating compactions for  + 
cfs.columnFamily);
-final SetListSSTableReader buckets = 
getBuckets(convertSSTablesToPairs(cfs.getSSTables()), 50L * 1024L * 1024L);
-updateEstimateFor(cfs, buckets);
-}
-};
-executor.submit(runnable);
-}
-
-// actually schedule compactions.  done in a second pass so all the 
estimates occur before we
-// bog down the executor in actual compactions.
-for (ColumnFamilyStore cfs : ColumnFamilyStore.all())
-{
-submitMinorIfNeeded(cfs);
-}
-}
-
 public int getActiveCompactions()
 {
 return executor.getActiveCount();

[jira] [Commented] (CASSANDRA-2662) Nodes get ignored by dynamic snitch when read repair chance is zero

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

Brandon Williams commented on CASSANDRA-2662:
-

Thinking this through a bit more:

Given coordinator A, and replicas X, Y, and Z (in subsnitch order), on the
first round X will be chosen, and let's say it receives a score of 1. With the
patch, at this point Y and Z will be initialized with zero. On the next round,
Y will be chosen, and let's say it receives a score of or near 1, depending on
network latency. On the third round, Z will be chosen, and let's say it also
receives a score similar to Y. Now the cache is hot on all nodes, and
subsequent reads have the possibility to oscillate between all three based on
network latency variance. This can be mitigated though with the badness
threshold. With the badness threshold on, the first round will occur as
before, but subsequent rounds will continue to use X until it degrades past the
threshold, at which point they will use Y, until the dynamic snitch reset()s,
at which point everything will repeat. I don't think this is harmful to
CASSANDRA-1314 after all.

Nodes get ignored by dynamic snitch when read repair chance is zero
---

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Issue Comment Edited] (CASSANDRA-2662) Nodes get ignored by dynamic snitch when read repair chance is zero


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

Brandon Williams edited comment on CASSANDRA-2662 at 5/18/11 7:48 PM:
--

There is one problem with this patch, rather that initializing the score to 
zero, it needs to create an empty AdaptiveLatencyTracker for them before 
checking the scores, otherwise DES.reset() will never have an effect on those 
hosts.

  was (Author: brandon.williams):
There is one problem with this patch, rather that initializing the score to 
zero, it needs to create an empty AdaptiveLatencyTracker for them before 
checking the scores, otherwise DES.reset() will never have an affect on those 
hosts.
  
 Nodes get ignored by dynamic snitch when read repair chance is zero
 ---

 Key: CASSANDRA-2662
 URL: https://issues.apache.org/jira/browse/CASSANDRA-2662
 Project: Cassandra
  Issue Type: Bug
  Components: Core
Affects Versions: 0.7.6
Reporter: Daniel Doubleday
Assignee: Brandon Williams
Priority: Trivial
 Attachments: dynsnitch.patch


 DynamicEndpointSnitch falls back to subsnitch when one of the scores of the 
 endpoints being compared is missing.
 This leads to a stable order of hosts until reads will lead to recorded 
 scores. 
 If setting read repair chance to 0 and reads are performed with quorum then 
 (rf - # quorum nodes) will never get reads.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (CASSANDRA-2662) Nodes get ignored by dynamic snitch when read repair chance is zero


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

Brandon Williams commented on CASSANDRA-2662:
-

There is one problem with this patch, rather that initializing the score to 
zero, it needs to create an empty AdaptiveLatencyTracker for them before 
checking the scores, otherwise DES.reset() will never have an affect on those 
hosts.

 Nodes get ignored by dynamic snitch when read repair chance is zero
 ---

 Key: CASSANDRA-2662
 URL: https://issues.apache.org/jira/browse/CASSANDRA-2662
 Project: Cassandra
  Issue Type: Bug
  Components: Core
Affects Versions: 0.7.6
Reporter: Daniel Doubleday
Assignee: Brandon Williams
Priority: Trivial
 Attachments: dynsnitch.patch


 DynamicEndpointSnitch falls back to subsnitch when one of the scores of the 
 endpoints being compared is missing.
 This leads to a stable order of hosts until reads will lead to recorded 
 scores. 
 If setting read repair chance to 0 and reads are performed with quorum then 
 (rf - # quorum nodes) will never get reads.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (CASSANDRA-2477) CQL support for describing keyspaces / column familes


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

Jonathan Ellis updated CASSANDRA-2477:
--

Attachment: 2477-virtual-cfs-false-start.txt

bq. How will you actually grok the schema without Avro?

That's the question, isn't it?

What I want to avoid is a special query type (i.e. anything not SELECT) 
because it makes the language less orthogonal because of implementation details 
that are subject to change (in an ideal world, we'd move away from avro and 
store schema information in real columns, with indexes so you could easily 
say give me all the columns for CF X at schema version Y.)

You'd also be limited to basically an RPC style call -- no specifying which 
columns to select, or which rows you're interested in. Not without reinventing 
that wheel on a LOT of code (because SELECT right now relies on CFS to perform 
the actual queries).

My first stab was to create a class of virtual CFs that would contain 
read-only data for this kind of query. (Attached.) I stopped when I got to a 
chicken/egg problem: the natural place to update this view CF is 
DD.setTableDefinition, but that gets called on startup when Table/CFS objects 
aren't live yet.

Trying to fake this at the QueryProcessor layer is also unsatisfactory -- we 
come back to the same kind of limitations we'd have with a special-case query 
type, that we don't have full SELECT support on non-CFS objects without insane 
amounts of work.

Starting to think that we'll have to bite the bullet and get rid of avro schema 
serialization to do this right.  Which I do think is doable, but it's more than 
I want to bite off right now. (Until then, clients like JDBC DatabaseMetadata 
can continue to use the thrift describe_ calls.)

 CQL support for describing keyspaces / column familes
 -

 Key: CASSANDRA-2477
 URL: https://issues.apache.org/jira/browse/CASSANDRA-2477
 Project: Cassandra
  Issue Type: Sub-task
  Components: API, Core
Reporter: Eric Evans
Assignee: Jonathan Ellis
  Labels: cql
 Fix For: 0.8.1

 Attachments: 2477-virtual-cfs-false-start.txt




--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (CASSANDRA-2477) CQL support for describing keyspaces / column familes


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

Jonathan Ellis updated CASSANDRA-2477:
--

Assignee: (was: Jonathan Ellis)

 CQL support for describing keyspaces / column familes
 -

 Key: CASSANDRA-2477
 URL: https://issues.apache.org/jira/browse/CASSANDRA-2477
 Project: Cassandra
  Issue Type: Sub-task
  Components: API, Core
Reporter: Eric Evans
  Labels: cql
 Fix For: 0.8.1

 Attachments: 2477-virtual-cfs-false-start.txt




--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (CASSANDRA-2170) Load spikes


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

Brandon Williams commented on CASSANDRA-2170:
-

I never saw anyone reliably report this on any platform except ec2, so I 
strongly the suspect the cause was what is covered in this link:

https://silverline.librato.com/blog/main/EC2_Users_Should_be_Cautious_When_Booting_Ubuntu_10_04_AMIs

 Load spikes
 ---

 Key: CASSANDRA-2170
 URL: https://issues.apache.org/jira/browse/CASSANDRA-2170
 Project: Cassandra
  Issue Type: Bug
Affects Versions: 0.6.11
Reporter: Jonathan Ellis

 as reported on CASSANDRA-2058, some users are still seeing load spikes on 
 0.6.11, even with fairly low-volume read workloads.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (CASSANDRA-2661) Canary CLHM v1.2

2011-05-18 Thread Benjamin Manes (JIRA)

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

Benjamin Manes commented on CASSANDRA-2661:
---

Validated compatibility with NonBlockingHashMap.

CLHM is implemented as a decorator to CHM to provide the bounded capacity
semantics. This allows it to remain a light-weight addition without incurring
the complexity of the hash-table design. It is implemented as a mostly
non-blocking decorator, where the blocking calls are low impact (#clear(),
snapshot views).

As described in [1], the java_util_concurrent_chm.jar can be added to the
bootclasspath to swap CHM with NBHM. If Cassandra did this, then it would
transparently switch the backing hash-table for CLHM and observe the
scalability benefits. This would be preferred v.s. requiring changes by CLHM.
It does not appear that Cassandra is taking advantage of this at this time.

[1]
http://high-scale-lib.cvs.sourceforge.net/viewvc/high-scale-lib/high-scale-lib/README

Canary CLHM v1.2

Key: CASSANDRA-2661
URL: https://issues.apache.org/jira/browse/CASSANDRA-2661
Project: Cassandra
Issue Type: Task
Reporter: Benjamin Manes
Attachments: clhm-20110517.jar

I am hoping to release ConcurrentLinkedHashMap v1.2 by the end of the week.
This task is optional, but gives you the opportunity to canary the library
and provide any final feedback. There are currently 285 tests (some threaded)
plus a load test, so reliability-wise I'm fairly confident.
This release has numerous performance improvements. See the change log for
details.
It also includes a few useful features that may be of interest,
- Snapshot iteration in order of hotness (CASSANDRA-1966)
- Optionally defer LRU maintenance penalty to a background executor (instead
of amortized on caller threads)
http://code.google.com/p/concurrentlinkedhashmap/

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (CASSANDRA-2661) Canary CLHM v1.2

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

Jonathan Ellis commented on CASSANDRA-2661:
---

bq. CLHM is implemented as a decorator to CHM to provide the bounded capacity
semantics the java_util_concurrent_chm.jar can be added to the
bootclasspath to swap CHM with NBHM.

That's a good idea. I'd want to check the dozen-ish uses of CHM in our code to
make sure none of them are relying on implementation-specific behavior, but
after a quick glance I'm optimistic.

Canary CLHM v1.2

Key: CASSANDRA-2661
URL: https://issues.apache.org/jira/browse/CASSANDRA-2661
Project: Cassandra
Issue Type: Task
Reporter: Benjamin Manes
Attachments: clhm-20110517.jar

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (CASSANDRA-2506) Push read repair setting down to the DC-level