[jira] [Commented] (CASSANDRA-13396) Cassandra 3.10: ClassCastException in ThreadAwareSecurityManager

[Claude Warren (JIRA)]

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

Claude Warren commented on CASSANDRA-13396:
---

+1 for [~qb3rt] summary, it touches all the points I was going to make and then 
some.

 

> Cassandra 3.10: ClassCastException in ThreadAwareSecurityManager
> 
>
> Key: CASSANDRA-13396
> URL: https://issues.apache.org/jira/browse/CASSANDRA-13396
> Project: Cassandra
>  Issue Type: Bug
>Reporter: Edward Capriolo
>Assignee: Eugene Fedotov
>Priority: Minor
>
> https://www.mail-archive.com/user@cassandra.apache.org/msg51603.html



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org

[jira] [Commented] (CASSANDRA-13396) Cassandra 3.10: ClassCastException in ThreadAwareSecurityManager

[Jason Brown (JIRA)]

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

Jason Brown commented on CASSANDRA-13396:
-

[~ehubert] Thank you. This use case summary was very helpful.

> Cassandra 3.10: ClassCastException in ThreadAwareSecurityManager
> 
>
> Key: CASSANDRA-13396
> URL: https://issues.apache.org/jira/browse/CASSANDRA-13396
> Project: Cassandra
>  Issue Type: Bug
>Reporter: Edward Capriolo
>Assignee: Eugene Fedotov
>Priority: Minor
>
> https://www.mail-archive.com/user@cassandra.apache.org/msg51603.html



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org

[jira] [Commented] (CASSANDRA-14183) CVE-2017-5929 Security vulnerability and redefine default log rotation policy

[Michael Shuler (JIRA)]

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

Michael Shuler commented on CASSANDRA-14183:


I committed the license file renames for trunk in 
[81ac654|https://github.com/apache/cassandra/commit/81ac654ff82f9149bc3265a18bfbdd6fbd2073f0]

> CVE-2017-5929 Security vulnerability and redefine default log rotation policy
> -
>
> Key: CASSANDRA-14183
> URL: https://issues.apache.org/jira/browse/CASSANDRA-14183
> Project: Cassandra
>  Issue Type: Improvement
>  Components: Libraries
>Reporter: Thiago Veronezi
>Assignee: Thiago Veronezi
>Priority: Major
>  Labels: patch, security
> Fix For: 4.0, 2.1.21, 2.2.13, 3.0.17, 3.11.3
>
> Attachments: 
> 0001-Update-to-logback-1.2.3-and-redefine-default-rotatio.patch
>
>
> Cassandra 3.11.1 is patched with logback 1.1.3, which contains the security 
> vulnerability described here. 
> [https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-5929]
> Also update to logback allows a simple date and size rotation policy to
> replace the default fixed policy, which is broken by design.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org

cassandra git commit: Add logback-1.2.3 licenses for CASSANDRA-14183 commit

[mshuler]

Repository: cassandra
Updated Branches:
  refs/heads/trunk c0aa79e54 -> 81ac654ff


Add logback-1.2.3 licenses for CASSANDRA-14183 commit

CVE-2017-5929 Security vulnerability and redefine default log rotation policy.

Patch by Michael Shuler; Reviewed by Ariel Weisberg for CASSANDRA-14183


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

Branch: refs/heads/trunk
Commit: 81ac654ff82f9149bc3265a18bfbdd6fbd2073f0
Parents: c0aa79e
Author: Michael Shuler 
Authored: Wed Feb 14 18:18:09 2018 -0600
Committer: Michael Shuler 
Committed: Wed Feb 14 18:18:09 2018 -0600

--
 lib/licenses/logback-classic-1.1.3.txt | 70 -
 lib/licenses/logback-classic-1.2.3.txt | 70 +
 lib/licenses/logback-core-1.1.3.txt| 70 -
 lib/licenses/logback-core-1.2.3.txt| 70 +
 4 files changed, 140 insertions(+), 140 deletions(-)
--


http://git-wip-us.apache.org/repos/asf/cassandra/blob/81ac654f/lib/licenses/logback-classic-1.1.3.txt
--
diff --git a/lib/licenses/logback-classic-1.1.3.txt 
b/lib/licenses/logback-classic-1.1.3.txt
deleted file mode 100644
index 79e486c..000
--- a/lib/licenses/logback-classic-1.1.3.txt
+++ /dev/null
@@ -1,70 +0,0 @@
-Eclipse Public License - v 1.0
-
-THE ACCOMPANYING PROGRAM IS PROVIDED UNDER THE TERMS OF THIS ECLIPSE PUBLIC 
LICENSE ("AGREEMENT"). ANY USE, REPRODUCTION OR DISTRIBUTION OF THE PROGRAM 
CONSTITUTES RECIPIENT'S ACCEPTANCE OF THIS AGREEMENT.
-
-1. DEFINITIONS
-
-"Contribution" means:
-
-a) in the case of the initial Contributor, the initial code and documentation 
distributed under this Agreement, and
-b) in the case of each subsequent Contributor:
-i) changes to the Program, and
-ii) additions to the Program;
-where such changes and/or additions to the Program originate from and are 
distributed by that particular Contributor. A Contribution 'originates' from a 
Contributor if it was added to the Program by such Contributor itself or anyone 
acting on such Contributor's behalf. Contributions do not include additions to 
the Program which: (i) are separate modules of software distributed in 
conjunction with the Program under their own license agreement, and (ii) are 
not derivative works of the Program.
-"Contributor" means any person or entity that distributes the Program.
-
-"Licensed Patents" mean patent claims licensable by a Contributor which are 
necessarily infringed by the use or sale of its Contribution alone or when 
combined with the Program.
-
-"Program" means the Contributions distributed in accordance with this 
Agreement.
-
-"Recipient" means anyone who receives the Program under this Agreement, 
including all Contributors.
-
-2. GRANT OF RIGHTS
-
-a) Subject to the terms of this Agreement, each Contributor hereby grants 
Recipient a non-exclusive, worldwide, royalty-free copyright license to 
reproduce, prepare derivative works of, publicly display, publicly perform, 
distribute and sublicense the Contribution of such Contributor, if any, and 
such derivative works, in source code and object code form.
-b) Subject to the terms of this Agreement, each Contributor hereby grants 
Recipient a non-exclusive, worldwide, royalty-free patent license under 
Licensed Patents to make, use, sell, offer to sell, import and otherwise 
transfer the Contribution of such Contributor, if any, in source code and 
object code form. This patent license shall apply to the combination of the 
Contribution and the Program if, at the time the Contribution is added by the 
Contributor, such addition of the Contribution causes such combination to be 
covered by the Licensed Patents. The patent license shall not apply to any 
other combinations which include the Contribution. No hardware per se is 
licensed hereunder.
-c) Recipient understands that although each Contributor grants the licenses to 
its Contributions set forth herein, no assurances are provided by any 
Contributor that the Program does not infringe the patent or other intellectual 
property rights of any other entity. Each Contributor disclaims any liability 
to Recipient for claims brought by any other entity based on infringement of 
intellectual property rights or otherwise. As a condition to exercising the 
rights and licenses granted hereunder, each Recipient hereby assumes sole 
responsibility to secure any other intellectual property rights needed, if any. 
For example, if a third party patent license is required to allow Recipient to 
distribute 

[jira] [Commented] (CASSANDRA-13396) Cassandra 3.10: ClassCastException in ThreadAwareSecurityManager

[Eric Hubert (JIRA)]

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

Eric Hubert commented on CASSANDRA-13396:
-

[~jasobrown], fair enough. From what I read/understood the majority of users 
(if not all, definitely including us) facing this issue, wanted to use 
Cassandra as an embedded server (mostly for integration testing purposes) 
utilizing class org.apache.cassandra.service.CassandraDaemon - so no production 
deployment of a standalone server or cluster.

While running alongside an application using slf4j with any slf4j supported 
backend != logback your are in trouble and no longer able to start the 
cassandra server, although logging/logging performance are none of your 
(primary) goals/concerns.

I doubt there are many users who want to configure a standalone single or 
multi-node Cassandra installation using a different logging backend to use this 
in production and have your support, but many users want to write automated 
integration/scenario tests of their own application interacting with Cassandra 
using an embedded Cassandra server in addition to plain unit tests using mocks 
without being forced to switch the logging backend chosen for their application 
for similar reasons you have. Therefore I see no conflict at all.

An implementation could even somehow enforce the differentation between 
embedded and standalone similar to "runManaged" to only allow/support other 
logging backends (skip special logging backend specific configuration) if 
CassandraDeamon is used/configured differently than from main() as done by a 
standalone server installation, this this is really a concern you want to see 
addressed.

> Cassandra 3.10: ClassCastException in ThreadAwareSecurityManager
> 
>
> Key: CASSANDRA-13396
> URL: https://issues.apache.org/jira/browse/CASSANDRA-13396
> Project: Cassandra
>  Issue Type: Bug
>Reporter: Edward Capriolo
>Assignee: Eugene Fedotov
>Priority: Minor
>
> https://www.mail-archive.com/user@cassandra.apache.org/msg51603.html



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org

[jira] [Updated] (CASSANDRA-13396) Cassandra 3.10: ClassCastException in ThreadAwareSecurityManager

[Jason Brown (JIRA)]

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

Jason Brown updated CASSANDRA-13396:

Reviewer: Jason Brown

> Cassandra 3.10: ClassCastException in ThreadAwareSecurityManager
> 
>
> Key: CASSANDRA-13396
> URL: https://issues.apache.org/jira/browse/CASSANDRA-13396
> Project: Cassandra
>  Issue Type: Bug
>Reporter: Edward Capriolo
>Assignee: Eugene Fedotov
>Priority: Minor
>
> https://www.mail-archive.com/user@cassandra.apache.org/msg51603.html



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org

[jira] [Updated] (CASSANDRA-14183) CVE-2017-5929 Security vulnerability and redefine default log rotation policy

[Ariel Weisberg (JIRA)]

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

Ariel Weisberg updated CASSANDRA-14183:
---
   Resolution: Fixed
Fix Version/s: (was: 3.11.x)
   4.0
   3.11.3
   3.0.17
   2.2.13
   2.1.21
   Status: Resolved  (was: Ready to Commit)

Committed as NEWS.txt change in 2.1 -> 3.11 
[4bbd28a043f15dd6c19de157acb5950319e8c16c|https://github.com/apache/cassandra/commit/4bbd28a043f15dd6c19de157acb5950319e8c16c]

Committed as a logback update with the log ration fix in trunk 
[c0aa79e5453d64a583ba2197b2ac76d04ecd7020|https://github.com/apache/cassandra/commit/c0aa79e5453d64a583ba2197b2ac76d04ecd7020]

Thanks everyone for helping sort this out.

> CVE-2017-5929 Security vulnerability and redefine default log rotation policy
> -
>
> Key: CASSANDRA-14183
> URL: https://issues.apache.org/jira/browse/CASSANDRA-14183
> Project: Cassandra
>  Issue Type: Improvement
>  Components: Libraries
>Reporter: Thiago Veronezi
>Assignee: Thiago Veronezi
>Priority: Major
>  Labels: patch, security
> Fix For: 2.1.21, 2.2.13, 3.0.17, 3.11.3, 4.0
>
> Attachments: 
> 0001-Update-to-logback-1.2.3-and-redefine-default-rotatio.patch
>
>
> Cassandra 3.11.1 is patched with logback 1.1.3, which contains the security 
> vulnerability described here. 
> [https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-5929]
> Also update to logback allows a simple date and size rotation policy to
> replace the default fixed policy, which is broken by design.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org

cassandra git commit: CVE-2017-5929 Security vulnerability and redefine default log rotation policy.

[aweisberg]

Repository: cassandra
Updated Branches:
  refs/heads/trunk 44ce9536f -> c0aa79e54


CVE-2017-5929 Security vulnerability and redefine default log rotation policy.

Patch by Michael Shuler; Reviewed by Ariel Weisberg for CASSANDRA-14183


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

Branch: refs/heads/trunk
Commit: c0aa79e5453d64a583ba2197b2ac76d04ecd7020
Parents: 44ce953
Author: Michael Shuler 
Authored: Wed Feb 14 11:42:59 2018 -0500
Committer: Ariel Weisberg 
Committed: Wed Feb 14 16:30:43 2018 -0500

--
 CHANGES.txt |   1 +
 build.xml   |   4 +--
 conf/logback.xml|  30 +--
 lib/logback-classic-1.1.3.jar   | Bin 280926 -> 0 bytes
 lib/logback-classic-1.2.3.jar   | Bin 0 -> 290339 bytes
 lib/logback-core-1.1.3.jar  | Bin 455041 -> 0 bytes
 lib/logback-core-1.2.3.jar  | Bin 0 -> 471901 bytes
 .../functions/ThreadAwareSecurityManager.java   |   5 
 test/conf/logback-test.xml  |   2 +-
 .../config/DatabaseDescriptorRefTest.java   |   6 ++--
 .../validation/operations/AggregationTest.java  |  12 
 11 files changed, 39 insertions(+), 21 deletions(-)
--


http://git-wip-us.apache.org/repos/asf/cassandra/blob/c0aa79e5/CHANGES.txt
--
diff --git a/CHANGES.txt b/CHANGES.txt
index e932b40..dd56770 100644
--- a/CHANGES.txt
+++ b/CHANGES.txt
@@ -1,4 +1,5 @@
 4.0
+ * CVE-2017-5929 Security vulnerability and redefine default log rotation 
policy (CASSANDRA-14183)
  * Use JVM default SSL validation algorithm instead of custom default 
(CASSANDRA-13259)
  * Better document in code InetAddressAndPort usage post 7544, incorporate 
port into UUIDGen node (CASSANDRA-14226)
  * Fix sstablemetadata date string for minLocalDeletionTime (CASSANDRA-14132)

http://git-wip-us.apache.org/repos/asf/cassandra/blob/c0aa79e5/build.xml
--
diff --git a/build.xml b/build.xml
index bc9f0a7..4b6ae70 100644
--- a/build.xml
+++ b/build.xml
@@ -383,8 +383,8 @@
   
   
   
-  
-  
+  
+  
   
   
   

http://git-wip-us.apache.org/repos/asf/cassandra/blob/c0aa79e5/conf/logback.xml
--
diff --git a/conf/logback.xml b/conf/logback.xml
index a22f131..b2c5b10 100644
--- a/conf/logback.xml
+++ b/conf/logback.xml
@@ -22,7 +22,7 @@ In order to disable debug.log, comment-out the ASYNCDEBUGLOG
 appender reference in the root level section below.
 -->
 
-
+
   
 
   
@@ -34,14 +34,14 @@ appender reference in the root level section below.
   INFO
 
 ${cassandra.logdir}/system.log
-
-  ${cassandra.logdir}/system.log.%i.zip
-  1
-  20
+
+  
+  
${cassandra.logdir}/system.log.%d{-MM-dd}.%i.zip
+  
+  50MB
+  7
+  5GB
 
-
-  20MB
-
 
   %-5level [%thread] %date{ISO8601} %F:%L - %msg%n
 
@@ -51,14 +51,14 @@ appender reference in the root level section below.
 
   
 ${cassandra.logdir}/debug.log
-
-  ${cassandra.logdir}/debug.log.%i.zip
-  1
-  20
+
+  
+  
${cassandra.logdir}/debug.log.%d{-MM-dd}.%i.zip
+  
+  50MB
+  7
+  5GB
 
-
-  20MB
-
 
   %-5level [%thread] %date{ISO8601} %F:%L - %msg%n
 

http://git-wip-us.apache.org/repos/asf/cassandra/blob/c0aa79e5/lib/logback-classic-1.1.3.jar
--
diff --git a/lib/logback-classic-1.1.3.jar b/lib/logback-classic-1.1.3.jar
deleted file mode 100644
index 2aa10a5..000
Binary files a/lib/logback-classic-1.1.3.jar and /dev/null differ

http://git-wip-us.apache.org/repos/asf/cassandra/blob/c0aa79e5/lib/logback-classic-1.2.3.jar
--
diff --git a/lib/logback-classic-1.2.3.jar b/lib/logback-classic-1.2.3.jar
new file mode 100644
index 000..bed00c0
Binary files /dev/null and b/lib/logback-classic-1.2.3.jar differ

http://git-wip-us.apache.org/repos/asf/cassandra/blob/c0aa79e5/lib/logback-core-1.1.3.jar
--
diff --git a/lib/logback-core-1.1.3.jar b/lib/logback-core-1.1.3.jar
deleted file mode 100644
index 996b722..000
Binary files 

[13/15] cassandra git commit: Merge branch 'cassandra-3.0' into cassandra-3.11

[aweisberg]

Merge branch 'cassandra-3.0' into cassandra-3.11


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

Branch: refs/heads/cassandra-3.11
Commit: 630c18eb38379a03d3766bb2be5835b1c78c66be
Parents: 1d506f9 2461187
Author: Ariel Weisberg 
Authored: Wed Feb 14 13:36:30 2018 -0500
Committer: Ariel Weisberg 
Committed: Wed Feb 14 13:36:30 2018 -0500

--
 CHANGES.txt | 4 
 NEWS.txt| 9 +
 2 files changed, 13 insertions(+)
--


http://git-wip-us.apache.org/repos/asf/cassandra/blob/630c18eb/CHANGES.txt
--
diff --cc CHANGES.txt
index e2ccc53,bbbca08..fdf045d
--- a/CHANGES.txt
+++ b/CHANGES.txt
@@@ -1,32 -1,14 +1,36 @@@
 -3.0.17
 -Merged from 2.1:
++3.11.3
++Merged from 2.1
+  * CVE-2017-5929 Security vulnerability in Logback warning in NEWS.txt 
(CASSANDRA-14183)
+ 
 -3.0.16
 - * Fix unit test failures in ViewComplexTest (CASSANDRA-14219)
 - * Add MinGW uname check to start scripts (CASSANDRA-12940)
 - * Protect against overflow of local expiration time (CASSANDRA-14092)
 +3.11.2
 + * Fix ReadCommandTest (CASSANDRA-14234)
 + * Remove trailing period from latency reports at keyspace level 
(CASSANDRA-14233)
 + * Backport CASSANDRA-13080: Use new token allocation for non bootstrap case 
as well (CASSANDRA-14212)
 + * Remove dependencies on JVM internal classes from JMXServerUtils 
(CASSANDRA-14173) 
 + * Add DEFAULT, UNSET, MBEAN and MBEANS to `ReservedKeywords` 
(CASSANDRA-14205)
 + * Add Unittest for schema migration fix (CASSANDRA-14140)
 + * Print correct snitch info from nodetool describecluster (CASSANDRA-13528)
 + * Close socket on error during connect on OutboundTcpConnection 
(CASSANDRA-9630)
 + * Enable CDC unittest (CASSANDRA-14141)
 + * Acquire read lock before accessing CompactionStrategyManager fields 
(CASSANDRA-14139)
 + * Split CommitLogStressTest to avoid timeout (CASSANDRA-14143)
 + * Avoid invalidating disk boundaries unnecessarily (CASSANDRA-14083)
 + * Avoid exposing compaction strategy index externally (CASSANDRA-14082)
 + * Prevent continuous schema exchange between 3.0 and 3.11 nodes 
(CASSANDRA-14109)
 + * Fix imbalanced disks when replacing node with same address with JBOD 
(CASSANDRA-14084)
 + * Reload compaction strategies when disk boundaries are invalidated 
(CASSANDRA-13948)
 + * Remove OpenJDK log warning (CASSANDRA-13916)
 + * Prevent compaction strategies from looping indefinitely (CASSANDRA-14079)
 + * Cache disk boundaries (CASSANDRA-13215)
 + * Add asm jar to build.xml for maven builds (CASSANDRA-11193)
 + * Round buffer size to powers of 2 for the chunk cache (CASSANDRA-13897)
 + * Update jackson JSON jars (CASSANDRA-13949)
 + * Avoid locks when checking LCS fanout and if we should defrag 
(CASSANDRA-13930)
 + * Correctly count range tombstones in traces and tombstone thresholds 
(CASSANDRA-8527)
 +Merged from 3.0:
 + * Add MinGW uname check to start scripts (CASSANDRA-12840)
   * Use the correct digest file and reload sstable metadata in nodetool verify 
(CASSANDRA-14217)
   * Handle failure when mutating repaired status in Verifier (CASSANDRA-13933)
 - * Close socket on error during connect on OutboundTcpConnection 
(CASSANDRA-9630)
   * Set encoding for javadoc generation (CASSANDRA-14154)
   * Fix index target computation for dense composite tables with dropped 
compact storage (CASSANDRA-14104)
   * Improve commit log chain marker updating (CASSANDRA-14108)

http://git-wip-us.apache.org/repos/asf/cassandra/blob/630c18eb/NEWS.txt
--


-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org

[07/15] cassandra git commit: Merge branch 'cassandra-2.1' into cassandra-2.2

[aweisberg]

Merge branch 'cassandra-2.1' into cassandra-2.2


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

Branch: refs/heads/cassandra-2.2
Commit: 08ebe8297b0ffbfda522036c0f750c4f6cf67e6f
Parents: 1602e60 4bbd28a
Author: Ariel Weisberg 
Authored: Wed Feb 14 13:23:41 2018 -0500
Committer: Ariel Weisberg 
Committed: Wed Feb 14 13:23:41 2018 -0500

--
 CHANGES.txt | 4 
 NEWS.txt| 9 +
 2 files changed, 13 insertions(+)
--


http://git-wip-us.apache.org/repos/asf/cassandra/blob/08ebe829/CHANGES.txt
--
diff --cc CHANGES.txt
index 82da6ad,0c25388..09930ce
--- a/CHANGES.txt
+++ b/CHANGES.txt
@@@ -1,9 -1,7 +1,13 @@@
 -2.1.21
++2.2.13
++Merged from 2.1:
+  * CVE-2017-5929 Security vulnerability in Logback warning in NEWS.txt 
(CASSANDRA-14183)
+ 
 -2.1.20
 +2.2.12
 + * Fix the inspectJvmOptions startup check (CASSANDRA-14112)
 + * Fix race that prevents submitting compaction for a table when executor is 
full (CASSANDRA-13801)
 + * Rely on the JVM to handle OutOfMemoryErrors (CASSANDRA-13006)
 + * Grab refs during scrub/index redistribution/cleanup (CASSANDRA-13873)
 +Merged from 2.1:
   * Protect against overflow of local expiration time (CASSANDRA-14092)
   * More PEP8 compliance for cqlsh (CASSANDRA-14021)
   * RPM package spec: fix permissions for installed jars and config files 
(CASSANDRA-14181)

http://git-wip-us.apache.org/repos/asf/cassandra/blob/08ebe829/NEWS.txt
--


-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org

[04/15] cassandra git commit: CVE-2017-5929 Security vulnerability in Logback warning in NEWS.txt

[aweisberg]

CVE-2017-5929 Security vulnerability in Logback warning in NEWS.txt

Patch by Ariel Weisberg; Reviewed by Jason Brown for CASSANDRA-14183


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

Branch: refs/heads/cassandra-3.0
Commit: 4bbd28a043f15dd6c19de157acb5950319e8c16c
Parents: b294943
Author: Ariel Weisberg 
Authored: Wed Feb 14 11:55:00 2018 -0500
Committer: Ariel Weisberg 
Committed: Wed Feb 14 11:55:00 2018 -0500

--
 CHANGES.txt | 3 +++
 NEWS.txt| 9 +
 2 files changed, 12 insertions(+)
--


http://git-wip-us.apache.org/repos/asf/cassandra/blob/4bbd28a0/CHANGES.txt
--
diff --git a/CHANGES.txt b/CHANGES.txt
index 9332354..0c25388 100644
--- a/CHANGES.txt
+++ b/CHANGES.txt
@@ -1,3 +1,6 @@
+2.1.21
+ * CVE-2017-5929 Security vulnerability in Logback warning in NEWS.txt 
(CASSANDRA-14183)
+
 2.1.20
  * Protect against overflow of local expiration time (CASSANDRA-14092)
  * More PEP8 compliance for cqlsh (CASSANDRA-14021)

http://git-wip-us.apache.org/repos/asf/cassandra/blob/4bbd28a0/NEWS.txt
--
diff --git a/NEWS.txt b/NEWS.txt
index fb6b4ee..232f3cd 100644
--- a/NEWS.txt
+++ b/NEWS.txt
@@ -18,6 +18,15 @@ CASSANDRA-14092.txt file.
 If you use or plan to use very large TTLS (10 to 20 years), read 
CASSANDRA-14092.txt
 for more information.
 
+PLEASE READ: CVE-2017-5929 LOGBACK BEFORE 1.2.0 SERIALIZATION VULNERABILITY
+--
+QOS.ch Logback before 1.2.0 has a serialization vulnerability affecting the
+SocketServer and ServerSocketReceiver components.
+
+Logback has not been upgraded to avoid breaking deployments and customizations
+based on older versions. If you are using vulnerable components you will need
+to upgrade to a newer version of Logback or stop using the vulnerable 
components.
+
 GENERAL UPGRADING ADVICE FOR ANY VERSION
 
 


-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org

[08/15] cassandra git commit: Merge branch 'cassandra-2.1' into cassandra-2.2

[aweisberg]

Merge branch 'cassandra-2.1' into cassandra-2.2


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

Branch: refs/heads/cassandra-3.0
Commit: 08ebe8297b0ffbfda522036c0f750c4f6cf67e6f
Parents: 1602e60 4bbd28a
Author: Ariel Weisberg 
Authored: Wed Feb 14 13:23:41 2018 -0500
Committer: Ariel Weisberg 
Committed: Wed Feb 14 13:23:41 2018 -0500

--
 CHANGES.txt | 4 
 NEWS.txt| 9 +
 2 files changed, 13 insertions(+)
--


http://git-wip-us.apache.org/repos/asf/cassandra/blob/08ebe829/CHANGES.txt
--
diff --cc CHANGES.txt
index 82da6ad,0c25388..09930ce
--- a/CHANGES.txt
+++ b/CHANGES.txt
@@@ -1,9 -1,7 +1,13 @@@
 -2.1.21
++2.2.13
++Merged from 2.1:
+  * CVE-2017-5929 Security vulnerability in Logback warning in NEWS.txt 
(CASSANDRA-14183)
+ 
 -2.1.20
 +2.2.12
 + * Fix the inspectJvmOptions startup check (CASSANDRA-14112)
 + * Fix race that prevents submitting compaction for a table when executor is 
full (CASSANDRA-13801)
 + * Rely on the JVM to handle OutOfMemoryErrors (CASSANDRA-13006)
 + * Grab refs during scrub/index redistribution/cleanup (CASSANDRA-13873)
 +Merged from 2.1:
   * Protect against overflow of local expiration time (CASSANDRA-14092)
   * More PEP8 compliance for cqlsh (CASSANDRA-14021)
   * RPM package spec: fix permissions for installed jars and config files 
(CASSANDRA-14181)

http://git-wip-us.apache.org/repos/asf/cassandra/blob/08ebe829/NEWS.txt
--


-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org

[09/15] cassandra git commit: Merge branch 'cassandra-2.1' into cassandra-2.2

[aweisberg]

Merge branch 'cassandra-2.1' into cassandra-2.2


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

Branch: refs/heads/cassandra-3.11
Commit: 08ebe8297b0ffbfda522036c0f750c4f6cf67e6f
Parents: 1602e60 4bbd28a
Author: Ariel Weisberg 
Authored: Wed Feb 14 13:23:41 2018 -0500
Committer: Ariel Weisberg 
Committed: Wed Feb 14 13:23:41 2018 -0500

--
 CHANGES.txt | 4 
 NEWS.txt| 9 +
 2 files changed, 13 insertions(+)
--


http://git-wip-us.apache.org/repos/asf/cassandra/blob/08ebe829/CHANGES.txt
--
diff --cc CHANGES.txt
index 82da6ad,0c25388..09930ce
--- a/CHANGES.txt
+++ b/CHANGES.txt
@@@ -1,9 -1,7 +1,13 @@@
 -2.1.21
++2.2.13
++Merged from 2.1:
+  * CVE-2017-5929 Security vulnerability in Logback warning in NEWS.txt 
(CASSANDRA-14183)
+ 
 -2.1.20
 +2.2.12
 + * Fix the inspectJvmOptions startup check (CASSANDRA-14112)
 + * Fix race that prevents submitting compaction for a table when executor is 
full (CASSANDRA-13801)
 + * Rely on the JVM to handle OutOfMemoryErrors (CASSANDRA-13006)
 + * Grab refs during scrub/index redistribution/cleanup (CASSANDRA-13873)
 +Merged from 2.1:
   * Protect against overflow of local expiration time (CASSANDRA-14092)
   * More PEP8 compliance for cqlsh (CASSANDRA-14021)
   * RPM package spec: fix permissions for installed jars and config files 
(CASSANDRA-14181)

http://git-wip-us.apache.org/repos/asf/cassandra/blob/08ebe829/NEWS.txt
--


-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org

[03/15] cassandra git commit: CVE-2017-5929 Security vulnerability in Logback warning in NEWS.txt

[aweisberg]

CVE-2017-5929 Security vulnerability in Logback warning in NEWS.txt

Patch by Ariel Weisberg; Reviewed by Jason Brown for CASSANDRA-14183


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

Branch: refs/heads/trunk
Commit: 4bbd28a043f15dd6c19de157acb5950319e8c16c
Parents: b294943
Author: Ariel Weisberg 
Authored: Wed Feb 14 11:55:00 2018 -0500
Committer: Ariel Weisberg 
Committed: Wed Feb 14 11:55:00 2018 -0500

--
 CHANGES.txt | 3 +++
 NEWS.txt| 9 +
 2 files changed, 12 insertions(+)
--


http://git-wip-us.apache.org/repos/asf/cassandra/blob/4bbd28a0/CHANGES.txt
--
diff --git a/CHANGES.txt b/CHANGES.txt
index 9332354..0c25388 100644
--- a/CHANGES.txt
+++ b/CHANGES.txt
@@ -1,3 +1,6 @@
+2.1.21
+ * CVE-2017-5929 Security vulnerability in Logback warning in NEWS.txt 
(CASSANDRA-14183)
+
 2.1.20
  * Protect against overflow of local expiration time (CASSANDRA-14092)
  * More PEP8 compliance for cqlsh (CASSANDRA-14021)

http://git-wip-us.apache.org/repos/asf/cassandra/blob/4bbd28a0/NEWS.txt
--
diff --git a/NEWS.txt b/NEWS.txt
index fb6b4ee..232f3cd 100644
--- a/NEWS.txt
+++ b/NEWS.txt
@@ -18,6 +18,15 @@ CASSANDRA-14092.txt file.
 If you use or plan to use very large TTLS (10 to 20 years), read 
CASSANDRA-14092.txt
 for more information.
 
+PLEASE READ: CVE-2017-5929 LOGBACK BEFORE 1.2.0 SERIALIZATION VULNERABILITY
+--
+QOS.ch Logback before 1.2.0 has a serialization vulnerability affecting the
+SocketServer and ServerSocketReceiver components.
+
+Logback has not been upgraded to avoid breaking deployments and customizations
+based on older versions. If you are using vulnerable components you will need
+to upgrade to a newer version of Logback or stop using the vulnerable 
components.
+
 GENERAL UPGRADING ADVICE FOR ANY VERSION
 
 


-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org

[14/15] cassandra git commit: Merge branch 'cassandra-3.0' into cassandra-3.11

[aweisberg]

Merge branch 'cassandra-3.0' into cassandra-3.11


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

Branch: refs/heads/trunk
Commit: 630c18eb38379a03d3766bb2be5835b1c78c66be
Parents: 1d506f9 2461187
Author: Ariel Weisberg 
Authored: Wed Feb 14 13:36:30 2018 -0500
Committer: Ariel Weisberg 
Committed: Wed Feb 14 13:36:30 2018 -0500

--
 CHANGES.txt | 4 
 NEWS.txt| 9 +
 2 files changed, 13 insertions(+)
--


http://git-wip-us.apache.org/repos/asf/cassandra/blob/630c18eb/CHANGES.txt
--
diff --cc CHANGES.txt
index e2ccc53,bbbca08..fdf045d
--- a/CHANGES.txt
+++ b/CHANGES.txt
@@@ -1,32 -1,14 +1,36 @@@
 -3.0.17
 -Merged from 2.1:
++3.11.3
++Merged from 2.1
+  * CVE-2017-5929 Security vulnerability in Logback warning in NEWS.txt 
(CASSANDRA-14183)
+ 
 -3.0.16
 - * Fix unit test failures in ViewComplexTest (CASSANDRA-14219)
 - * Add MinGW uname check to start scripts (CASSANDRA-12940)
 - * Protect against overflow of local expiration time (CASSANDRA-14092)
 +3.11.2
 + * Fix ReadCommandTest (CASSANDRA-14234)
 + * Remove trailing period from latency reports at keyspace level 
(CASSANDRA-14233)
 + * Backport CASSANDRA-13080: Use new token allocation for non bootstrap case 
as well (CASSANDRA-14212)
 + * Remove dependencies on JVM internal classes from JMXServerUtils 
(CASSANDRA-14173) 
 + * Add DEFAULT, UNSET, MBEAN and MBEANS to `ReservedKeywords` 
(CASSANDRA-14205)
 + * Add Unittest for schema migration fix (CASSANDRA-14140)
 + * Print correct snitch info from nodetool describecluster (CASSANDRA-13528)
 + * Close socket on error during connect on OutboundTcpConnection 
(CASSANDRA-9630)
 + * Enable CDC unittest (CASSANDRA-14141)
 + * Acquire read lock before accessing CompactionStrategyManager fields 
(CASSANDRA-14139)
 + * Split CommitLogStressTest to avoid timeout (CASSANDRA-14143)
 + * Avoid invalidating disk boundaries unnecessarily (CASSANDRA-14083)
 + * Avoid exposing compaction strategy index externally (CASSANDRA-14082)
 + * Prevent continuous schema exchange between 3.0 and 3.11 nodes 
(CASSANDRA-14109)
 + * Fix imbalanced disks when replacing node with same address with JBOD 
(CASSANDRA-14084)
 + * Reload compaction strategies when disk boundaries are invalidated 
(CASSANDRA-13948)
 + * Remove OpenJDK log warning (CASSANDRA-13916)
 + * Prevent compaction strategies from looping indefinitely (CASSANDRA-14079)
 + * Cache disk boundaries (CASSANDRA-13215)
 + * Add asm jar to build.xml for maven builds (CASSANDRA-11193)
 + * Round buffer size to powers of 2 for the chunk cache (CASSANDRA-13897)
 + * Update jackson JSON jars (CASSANDRA-13949)
 + * Avoid locks when checking LCS fanout and if we should defrag 
(CASSANDRA-13930)
 + * Correctly count range tombstones in traces and tombstone thresholds 
(CASSANDRA-8527)
 +Merged from 3.0:
 + * Add MinGW uname check to start scripts (CASSANDRA-12840)
   * Use the correct digest file and reload sstable metadata in nodetool verify 
(CASSANDRA-14217)
   * Handle failure when mutating repaired status in Verifier (CASSANDRA-13933)
 - * Close socket on error during connect on OutboundTcpConnection 
(CASSANDRA-9630)
   * Set encoding for javadoc generation (CASSANDRA-14154)
   * Fix index target computation for dense composite tables with dropped 
compact storage (CASSANDRA-14104)
   * Improve commit log chain marker updating (CASSANDRA-14108)

http://git-wip-us.apache.org/repos/asf/cassandra/blob/630c18eb/NEWS.txt
--


-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org

[01/15] cassandra git commit: CVE-2017-5929 Security vulnerability in Logback warning in NEWS.txt

[aweisberg]

Repository: cassandra
Updated Branches:
  refs/heads/cassandra-2.1 b2949439e -> 4bbd28a04
  refs/heads/cassandra-2.2 1602e6063 -> 08ebe8297
  refs/heads/cassandra-3.0 890f31914 -> 2461187c0
  refs/heads/cassandra-3.11 1d506f9d0 -> 630c18eb3
  refs/heads/trunk 7a424bc2a -> 44ce9536f


CVE-2017-5929 Security vulnerability in Logback warning in NEWS.txt

Patch by Ariel Weisberg; Reviewed by Jason Brown for CASSANDRA-14183


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

Branch: refs/heads/cassandra-2.1
Commit: 4bbd28a043f15dd6c19de157acb5950319e8c16c
Parents: b294943
Author: Ariel Weisberg 
Authored: Wed Feb 14 11:55:00 2018 -0500
Committer: Ariel Weisberg 
Committed: Wed Feb 14 11:55:00 2018 -0500

--
 CHANGES.txt | 3 +++
 NEWS.txt| 9 +
 2 files changed, 12 insertions(+)
--


http://git-wip-us.apache.org/repos/asf/cassandra/blob/4bbd28a0/CHANGES.txt
--
diff --git a/CHANGES.txt b/CHANGES.txt
index 9332354..0c25388 100644
--- a/CHANGES.txt
+++ b/CHANGES.txt
@@ -1,3 +1,6 @@
+2.1.21
+ * CVE-2017-5929 Security vulnerability in Logback warning in NEWS.txt 
(CASSANDRA-14183)
+
 2.1.20
  * Protect against overflow of local expiration time (CASSANDRA-14092)
  * More PEP8 compliance for cqlsh (CASSANDRA-14021)

http://git-wip-us.apache.org/repos/asf/cassandra/blob/4bbd28a0/NEWS.txt
--
diff --git a/NEWS.txt b/NEWS.txt
index fb6b4ee..232f3cd 100644
--- a/NEWS.txt
+++ b/NEWS.txt
@@ -18,6 +18,15 @@ CASSANDRA-14092.txt file.
 If you use or plan to use very large TTLS (10 to 20 years), read 
CASSANDRA-14092.txt
 for more information.
 
+PLEASE READ: CVE-2017-5929 LOGBACK BEFORE 1.2.0 SERIALIZATION VULNERABILITY
+--
+QOS.ch Logback before 1.2.0 has a serialization vulnerability affecting the
+SocketServer and ServerSocketReceiver components.
+
+Logback has not been upgraded to avoid breaking deployments and customizations
+based on older versions. If you are using vulnerable components you will need
+to upgrade to a newer version of Logback or stop using the vulnerable 
components.
+
 GENERAL UPGRADING ADVICE FOR ANY VERSION
 
 


-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org

[02/15] cassandra git commit: CVE-2017-5929 Security vulnerability in Logback warning in NEWS.txt

[aweisberg]

CVE-2017-5929 Security vulnerability in Logback warning in NEWS.txt

Patch by Ariel Weisberg; Reviewed by Jason Brown for CASSANDRA-14183


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

Branch: refs/heads/cassandra-2.2
Commit: 4bbd28a043f15dd6c19de157acb5950319e8c16c
Parents: b294943
Author: Ariel Weisberg 
Authored: Wed Feb 14 11:55:00 2018 -0500
Committer: Ariel Weisberg 
Committed: Wed Feb 14 11:55:00 2018 -0500

--
 CHANGES.txt | 3 +++
 NEWS.txt| 9 +
 2 files changed, 12 insertions(+)
--


http://git-wip-us.apache.org/repos/asf/cassandra/blob/4bbd28a0/CHANGES.txt
--
diff --git a/CHANGES.txt b/CHANGES.txt
index 9332354..0c25388 100644
--- a/CHANGES.txt
+++ b/CHANGES.txt
@@ -1,3 +1,6 @@
+2.1.21
+ * CVE-2017-5929 Security vulnerability in Logback warning in NEWS.txt 
(CASSANDRA-14183)
+
 2.1.20
  * Protect against overflow of local expiration time (CASSANDRA-14092)
  * More PEP8 compliance for cqlsh (CASSANDRA-14021)

http://git-wip-us.apache.org/repos/asf/cassandra/blob/4bbd28a0/NEWS.txt
--
diff --git a/NEWS.txt b/NEWS.txt
index fb6b4ee..232f3cd 100644
--- a/NEWS.txt
+++ b/NEWS.txt
@@ -18,6 +18,15 @@ CASSANDRA-14092.txt file.
 If you use or plan to use very large TTLS (10 to 20 years), read 
CASSANDRA-14092.txt
 for more information.
 
+PLEASE READ: CVE-2017-5929 LOGBACK BEFORE 1.2.0 SERIALIZATION VULNERABILITY
+--
+QOS.ch Logback before 1.2.0 has a serialization vulnerability affecting the
+SocketServer and ServerSocketReceiver components.
+
+Logback has not been upgraded to avoid breaking deployments and customizations
+based on older versions. If you are using vulnerable components you will need
+to upgrade to a newer version of Logback or stop using the vulnerable 
components.
+
 GENERAL UPGRADING ADVICE FOR ANY VERSION
 
 


-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org

[15/15] cassandra git commit: Merge branch 'cassandra-3.11' into trunk

[aweisberg]

Merge branch 'cassandra-3.11' into trunk


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

Branch: refs/heads/trunk
Commit: 44ce9536ff7bbc522a87839a85fc346ca3a279fe
Parents: 7a424bc 630c18e
Author: Ariel Weisberg 
Authored: Wed Feb 14 13:36:58 2018 -0500
Committer: Ariel Weisberg 
Committed: Wed Feb 14 13:36:58 2018 -0500

--

--



-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org

[05/15] cassandra git commit: CVE-2017-5929 Security vulnerability in Logback warning in NEWS.txt

[aweisberg]

CVE-2017-5929 Security vulnerability in Logback warning in NEWS.txt

Patch by Ariel Weisberg; Reviewed by Jason Brown for CASSANDRA-14183


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

Branch: refs/heads/cassandra-3.11
Commit: 4bbd28a043f15dd6c19de157acb5950319e8c16c
Parents: b294943
Author: Ariel Weisberg 
Authored: Wed Feb 14 11:55:00 2018 -0500
Committer: Ariel Weisberg 
Committed: Wed Feb 14 11:55:00 2018 -0500

--
 CHANGES.txt | 3 +++
 NEWS.txt| 9 +
 2 files changed, 12 insertions(+)
--


http://git-wip-us.apache.org/repos/asf/cassandra/blob/4bbd28a0/CHANGES.txt
--
diff --git a/CHANGES.txt b/CHANGES.txt
index 9332354..0c25388 100644
--- a/CHANGES.txt
+++ b/CHANGES.txt
@@ -1,3 +1,6 @@
+2.1.21
+ * CVE-2017-5929 Security vulnerability in Logback warning in NEWS.txt 
(CASSANDRA-14183)
+
 2.1.20
  * Protect against overflow of local expiration time (CASSANDRA-14092)
  * More PEP8 compliance for cqlsh (CASSANDRA-14021)

http://git-wip-us.apache.org/repos/asf/cassandra/blob/4bbd28a0/NEWS.txt
--
diff --git a/NEWS.txt b/NEWS.txt
index fb6b4ee..232f3cd 100644
--- a/NEWS.txt
+++ b/NEWS.txt
@@ -18,6 +18,15 @@ CASSANDRA-14092.txt file.
 If you use or plan to use very large TTLS (10 to 20 years), read 
CASSANDRA-14092.txt
 for more information.
 
+PLEASE READ: CVE-2017-5929 LOGBACK BEFORE 1.2.0 SERIALIZATION VULNERABILITY
+--
+QOS.ch Logback before 1.2.0 has a serialization vulnerability affecting the
+SocketServer and ServerSocketReceiver components.
+
+Logback has not been upgraded to avoid breaking deployments and customizations
+based on older versions. If you are using vulnerable components you will need
+to upgrade to a newer version of Logback or stop using the vulnerable 
components.
+
 GENERAL UPGRADING ADVICE FOR ANY VERSION
 
 


-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org

[10/15] cassandra git commit: Merge branch 'cassandra-2.2' into cassandra-3.0

[aweisberg]

Merge branch 'cassandra-2.2' into cassandra-3.0


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

Branch: refs/heads/trunk
Commit: 2461187c0e82d047e143f059124a6dc740ee853f
Parents: 890f319 08ebe82
Author: Ariel Weisberg 
Authored: Wed Feb 14 13:29:17 2018 -0500
Committer: Ariel Weisberg 
Committed: Wed Feb 14 13:32:59 2018 -0500

--
 CHANGES.txt | 4 
 NEWS.txt| 9 +
 2 files changed, 13 insertions(+)
--


http://git-wip-us.apache.org/repos/asf/cassandra/blob/2461187c/CHANGES.txt
--
diff --cc CHANGES.txt
index 90bd53f,09930ce..bbbca08
--- a/CHANGES.txt
+++ b/CHANGES.txt
@@@ -1,32 -1,8 +1,36 @@@
 -2.2.13
++3.0.17
+ Merged from 2.1:
+  * CVE-2017-5929 Security vulnerability in Logback warning in NEWS.txt 
(CASSANDRA-14183)
+ 
 -2.2.12
 +3.0.16
 + * Fix unit test failures in ViewComplexTest (CASSANDRA-14219)
 + * Add MinGW uname check to start scripts (CASSANDRA-12940)
 + * Protect against overflow of local expiration time (CASSANDRA-14092)
 + * Use the correct digest file and reload sstable metadata in nodetool verify 
(CASSANDRA-14217)
 + * Handle failure when mutating repaired status in Verifier (CASSANDRA-13933)
 + * Close socket on error during connect on OutboundTcpConnection 
(CASSANDRA-9630)
 + * Set encoding for javadoc generation (CASSANDRA-14154)
 + * Fix index target computation for dense composite tables with dropped 
compact storage (CASSANDRA-14104)
 + * Improve commit log chain marker updating (CASSANDRA-14108)
 + * Extra range tombstone bound creates double rows (CASSANDRA-14008)
 + * Fix SStable ordering by max timestamp in SinglePartitionReadCommand 
(CASSANDRA-14010)
 + * Accept role names containing forward-slash (CASSANDRA-14088)
 + * Optimize CRC check chance probability calculations (CASSANDRA-14094)
 + * Fix cleanup on keyspace with no replicas (CASSANDRA-13526)
 + * Fix updating base table rows with TTL not removing materialized view 
entries (CASSANDRA-14071)
 + * Reduce garbage created by DynamicSnitch (CASSANDRA-14091)
 + * More frequent commitlog chained markers (CASSANDRA-13987)
 + * Fix serialized size of DataLimits (CASSANDRA-14057)
 + * Add flag to allow dropping oversized read repair mutations 
(CASSANDRA-13975)
 + * Fix SSTableLoader logger message (CASSANDRA-14003)
 + * Fix repair race that caused gossip to block (CASSANDRA-13849)
 + * Tracing interferes with digest requests when using RandomPartitioner 
(CASSANDRA-13964)
 + * Add flag to disable materialized views, and warnings on creation 
(CASSANDRA-13959)
 + * Don't let user drop or generally break tables in system_distributed 
(CASSANDRA-13813)
 + * Provide a JMX call to sync schema with local storage (CASSANDRA-13954)
 + * Mishandling of cells for removed/dropped columns when reading legacy files 
(CASSANDRA-13939)
 + * Deserialise sstable metadata in nodetool verify (CASSANDRA-13922)
 +Merged from 2.2:
   * Fix the inspectJvmOptions startup check (CASSANDRA-14112)
   * Fix race that prevents submitting compaction for a table when executor is 
full (CASSANDRA-13801)
   * Rely on the JVM to handle OutOfMemoryErrors (CASSANDRA-13006)

http://git-wip-us.apache.org/repos/asf/cassandra/blob/2461187c/NEWS.txt
--


-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org

[06/15] cassandra git commit: Merge branch 'cassandra-2.1' into cassandra-2.2

[aweisberg]

Merge branch 'cassandra-2.1' into cassandra-2.2


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

Branch: refs/heads/trunk
Commit: 08ebe8297b0ffbfda522036c0f750c4f6cf67e6f
Parents: 1602e60 4bbd28a
Author: Ariel Weisberg 
Authored: Wed Feb 14 13:23:41 2018 -0500
Committer: Ariel Weisberg 
Committed: Wed Feb 14 13:23:41 2018 -0500

--
 CHANGES.txt | 4 
 NEWS.txt| 9 +
 2 files changed, 13 insertions(+)
--


http://git-wip-us.apache.org/repos/asf/cassandra/blob/08ebe829/CHANGES.txt
--
diff --cc CHANGES.txt
index 82da6ad,0c25388..09930ce
--- a/CHANGES.txt
+++ b/CHANGES.txt
@@@ -1,9 -1,7 +1,13 @@@
 -2.1.21
++2.2.13
++Merged from 2.1:
+  * CVE-2017-5929 Security vulnerability in Logback warning in NEWS.txt 
(CASSANDRA-14183)
+ 
 -2.1.20
 +2.2.12
 + * Fix the inspectJvmOptions startup check (CASSANDRA-14112)
 + * Fix race that prevents submitting compaction for a table when executor is 
full (CASSANDRA-13801)
 + * Rely on the JVM to handle OutOfMemoryErrors (CASSANDRA-13006)
 + * Grab refs during scrub/index redistribution/cleanup (CASSANDRA-13873)
 +Merged from 2.1:
   * Protect against overflow of local expiration time (CASSANDRA-14092)
   * More PEP8 compliance for cqlsh (CASSANDRA-14021)
   * RPM package spec: fix permissions for installed jars and config files 
(CASSANDRA-14181)

http://git-wip-us.apache.org/repos/asf/cassandra/blob/08ebe829/NEWS.txt
--


-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org

[12/15] cassandra git commit: Merge branch 'cassandra-2.2' into cassandra-3.0

[aweisberg]

Merge branch 'cassandra-2.2' into cassandra-3.0


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

Branch: refs/heads/cassandra-3.0
Commit: 2461187c0e82d047e143f059124a6dc740ee853f
Parents: 890f319 08ebe82
Author: Ariel Weisberg 
Authored: Wed Feb 14 13:29:17 2018 -0500
Committer: Ariel Weisberg 
Committed: Wed Feb 14 13:32:59 2018 -0500

--
 CHANGES.txt | 4 
 NEWS.txt| 9 +
 2 files changed, 13 insertions(+)
--


http://git-wip-us.apache.org/repos/asf/cassandra/blob/2461187c/CHANGES.txt
--
diff --cc CHANGES.txt
index 90bd53f,09930ce..bbbca08
--- a/CHANGES.txt
+++ b/CHANGES.txt
@@@ -1,32 -1,8 +1,36 @@@
 -2.2.13
++3.0.17
+ Merged from 2.1:
+  * CVE-2017-5929 Security vulnerability in Logback warning in NEWS.txt 
(CASSANDRA-14183)
+ 
 -2.2.12
 +3.0.16
 + * Fix unit test failures in ViewComplexTest (CASSANDRA-14219)
 + * Add MinGW uname check to start scripts (CASSANDRA-12940)
 + * Protect against overflow of local expiration time (CASSANDRA-14092)
 + * Use the correct digest file and reload sstable metadata in nodetool verify 
(CASSANDRA-14217)
 + * Handle failure when mutating repaired status in Verifier (CASSANDRA-13933)
 + * Close socket on error during connect on OutboundTcpConnection 
(CASSANDRA-9630)
 + * Set encoding for javadoc generation (CASSANDRA-14154)
 + * Fix index target computation for dense composite tables with dropped 
compact storage (CASSANDRA-14104)
 + * Improve commit log chain marker updating (CASSANDRA-14108)
 + * Extra range tombstone bound creates double rows (CASSANDRA-14008)
 + * Fix SStable ordering by max timestamp in SinglePartitionReadCommand 
(CASSANDRA-14010)
 + * Accept role names containing forward-slash (CASSANDRA-14088)
 + * Optimize CRC check chance probability calculations (CASSANDRA-14094)
 + * Fix cleanup on keyspace with no replicas (CASSANDRA-13526)
 + * Fix updating base table rows with TTL not removing materialized view 
entries (CASSANDRA-14071)
 + * Reduce garbage created by DynamicSnitch (CASSANDRA-14091)
 + * More frequent commitlog chained markers (CASSANDRA-13987)
 + * Fix serialized size of DataLimits (CASSANDRA-14057)
 + * Add flag to allow dropping oversized read repair mutations 
(CASSANDRA-13975)
 + * Fix SSTableLoader logger message (CASSANDRA-14003)
 + * Fix repair race that caused gossip to block (CASSANDRA-13849)
 + * Tracing interferes with digest requests when using RandomPartitioner 
(CASSANDRA-13964)
 + * Add flag to disable materialized views, and warnings on creation 
(CASSANDRA-13959)
 + * Don't let user drop or generally break tables in system_distributed 
(CASSANDRA-13813)
 + * Provide a JMX call to sync schema with local storage (CASSANDRA-13954)
 + * Mishandling of cells for removed/dropped columns when reading legacy files 
(CASSANDRA-13939)
 + * Deserialise sstable metadata in nodetool verify (CASSANDRA-13922)
 +Merged from 2.2:
   * Fix the inspectJvmOptions startup check (CASSANDRA-14112)
   * Fix race that prevents submitting compaction for a table when executor is 
full (CASSANDRA-13801)
   * Rely on the JVM to handle OutOfMemoryErrors (CASSANDRA-13006)

http://git-wip-us.apache.org/repos/asf/cassandra/blob/2461187c/NEWS.txt
--


-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org

[11/15] cassandra git commit: Merge branch 'cassandra-2.2' into cassandra-3.0

[aweisberg]

Merge branch 'cassandra-2.2' into cassandra-3.0


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

Branch: refs/heads/cassandra-3.11
Commit: 2461187c0e82d047e143f059124a6dc740ee853f
Parents: 890f319 08ebe82
Author: Ariel Weisberg 
Authored: Wed Feb 14 13:29:17 2018 -0500
Committer: Ariel Weisberg 
Committed: Wed Feb 14 13:32:59 2018 -0500

--
 CHANGES.txt | 4 
 NEWS.txt| 9 +
 2 files changed, 13 insertions(+)
--


http://git-wip-us.apache.org/repos/asf/cassandra/blob/2461187c/CHANGES.txt
--
diff --cc CHANGES.txt
index 90bd53f,09930ce..bbbca08
--- a/CHANGES.txt
+++ b/CHANGES.txt
@@@ -1,32 -1,8 +1,36 @@@
 -2.2.13
++3.0.17
+ Merged from 2.1:
+  * CVE-2017-5929 Security vulnerability in Logback warning in NEWS.txt 
(CASSANDRA-14183)
+ 
 -2.2.12
 +3.0.16
 + * Fix unit test failures in ViewComplexTest (CASSANDRA-14219)
 + * Add MinGW uname check to start scripts (CASSANDRA-12940)
 + * Protect against overflow of local expiration time (CASSANDRA-14092)
 + * Use the correct digest file and reload sstable metadata in nodetool verify 
(CASSANDRA-14217)
 + * Handle failure when mutating repaired status in Verifier (CASSANDRA-13933)
 + * Close socket on error during connect on OutboundTcpConnection 
(CASSANDRA-9630)
 + * Set encoding for javadoc generation (CASSANDRA-14154)
 + * Fix index target computation for dense composite tables with dropped 
compact storage (CASSANDRA-14104)
 + * Improve commit log chain marker updating (CASSANDRA-14108)
 + * Extra range tombstone bound creates double rows (CASSANDRA-14008)
 + * Fix SStable ordering by max timestamp in SinglePartitionReadCommand 
(CASSANDRA-14010)
 + * Accept role names containing forward-slash (CASSANDRA-14088)
 + * Optimize CRC check chance probability calculations (CASSANDRA-14094)
 + * Fix cleanup on keyspace with no replicas (CASSANDRA-13526)
 + * Fix updating base table rows with TTL not removing materialized view 
entries (CASSANDRA-14071)
 + * Reduce garbage created by DynamicSnitch (CASSANDRA-14091)
 + * More frequent commitlog chained markers (CASSANDRA-13987)
 + * Fix serialized size of DataLimits (CASSANDRA-14057)
 + * Add flag to allow dropping oversized read repair mutations 
(CASSANDRA-13975)
 + * Fix SSTableLoader logger message (CASSANDRA-14003)
 + * Fix repair race that caused gossip to block (CASSANDRA-13849)
 + * Tracing interferes with digest requests when using RandomPartitioner 
(CASSANDRA-13964)
 + * Add flag to disable materialized views, and warnings on creation 
(CASSANDRA-13959)
 + * Don't let user drop or generally break tables in system_distributed 
(CASSANDRA-13813)
 + * Provide a JMX call to sync schema with local storage (CASSANDRA-13954)
 + * Mishandling of cells for removed/dropped columns when reading legacy files 
(CASSANDRA-13939)
 + * Deserialise sstable metadata in nodetool verify (CASSANDRA-13922)
 +Merged from 2.2:
   * Fix the inspectJvmOptions startup check (CASSANDRA-14112)
   * Fix race that prevents submitting compaction for a table when executor is 
full (CASSANDRA-13801)
   * Rely on the JVM to handle OutOfMemoryErrors (CASSANDRA-13006)

http://git-wip-us.apache.org/repos/asf/cassandra/blob/2461187c/NEWS.txt
--


-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org

[jira] [Commented] (CASSANDRA-13396) Cassandra 3.10: ClassCastException in ThreadAwareSecurityManager

[Jason Brown (JIRA)]

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

Jason Brown commented on CASSANDRA-13396:
-

[~ehubert] 3.11.2 is up for vote & release this week, so this patch will not be 
included in that release. Do you have any test cases you can offer here? Please 
note that allowing other logging implementation seems to be used seems in 
scope, but will *not*, in any way, be supported. I'll need to reread through 
all the commentary again to get the full scope of what people are really asking 
for, but I'm at least willing to get this to completion.

> Cassandra 3.10: ClassCastException in ThreadAwareSecurityManager
> 
>
> Key: CASSANDRA-13396
> URL: https://issues.apache.org/jira/browse/CASSANDRA-13396
> Project: Cassandra
>  Issue Type: Bug
>Reporter: Edward Capriolo
>Assignee: Eugene Fedotov
>Priority: Minor
>
> https://www.mail-archive.com/user@cassandra.apache.org/msg51603.html



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org

[cassandra] Git Push Summary

[mshuler]

Repository: cassandra
Updated Tags:  refs/tags/3.11.2-tentative [created] 1d506f9d0

-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org

[jira] [Commented] (CASSANDRA-13396) Cassandra 3.10: ClassCastException in ThreadAwareSecurityManager

[Eric Hubert (JIRA)]

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

Eric Hubert commented on CASSANDRA-13396:
-

[~jasobrown], maybe you can have a glance on [my comment|#comment-16152569] as 
well. I have not started working on a patch, because I did not receive any 
feedback on my suggestion on a conceptual level. I did not want to waste time 
working on an implementation without knowing of a chance of inclusion. Because 
we faced some issues in production which are either fixed in 3.11.1 or will be 
fixed in 3.11.2 we really would like to update, but this still blocks us.

> Cassandra 3.10: ClassCastException in ThreadAwareSecurityManager
> 
>
> Key: CASSANDRA-13396
> URL: https://issues.apache.org/jira/browse/CASSANDRA-13396
> Project: Cassandra
>  Issue Type: Bug
>Reporter: Edward Capriolo
>Assignee: Eugene Fedotov
>Priority: Minor
>
> https://www.mail-archive.com/user@cassandra.apache.org/msg51603.html



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org

[cassandra] Git Push Summary

[mshuler]

Repository: cassandra
Updated Tags:  refs/tags/3.0.16-tentative [created] 890f31914

-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org

[jira] [Commented] (CASSANDRA-14055) Index redistribution breaks SASI index

[Jordan West (JIRA)]

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

Jordan West commented on CASSANDRA-14055:
-

[~lboutros], the order we release them shouldn't matter for file deletion 
because as long as one index is open, there is one sstable open, and therefore 
the global reference count for the table is > 0. But if we keep the older 
reference we are leaking the old reference (and using the old metadata) until 
the {{SSTableIndex}} is released, which is wrong.

 

Either way, sounds like we agree on the fix :). I will post a new patch once 
approved internally. 

> Index redistribution breaks SASI index
> --
>
> Key: CASSANDRA-14055
> URL: https://issues.apache.org/jira/browse/CASSANDRA-14055
> Project: Cassandra
>  Issue Type: Bug
>  Components: sasi
>Reporter: Ludovic Boutros
>Assignee: Ludovic Boutros
>Priority: Major
>  Labels: patch
> Fix For: 3.11.x, 4.x
>
> Attachments: CASSANDRA-14055-jrwest.patch, CASSANDRA-14055.patch, 
> CASSANDRA-14055.patch, CASSANDRA-14055.patch
>
>
> During index redistribution process, a new view is created.
> During this creation, old indexes should be released.
> But, new indexes are "attached" to the same SSTable as the old indexes.
> This leads to the deletion of the last SASI index file and breaks the index.
> The issue is in this function : 
> [https://github.com/apache/cassandra/blob/9ee44db49b13d4b4c91c9d6332ce06a6e2abf944/src/java/org/apache/cassandra/index/sasi/conf/view/View.java#L62]



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org

[cassandra] Git Push Summary

[mshuler]

Repository: cassandra
Updated Tags:  refs/tags/3.0.16-tentative [deleted] 91e83c72d

-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org

[cassandra] Git Push Summary

[mshuler]

Repository: cassandra
Updated Tags:  refs/tags/3.11.2-tentative [deleted] 8a5e88f63

-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org

[jira] [Commented] (CASSANDRA-14183) CVE-2017-5929 Security vulnerability and redefine default log rotation policy

[Ariel Weisberg (JIRA)]

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

Ariel Weisberg commented on CASSANDRA-14183:


+1 on Michael's patch.

> CVE-2017-5929 Security vulnerability and redefine default log rotation policy
> -
>
> Key: CASSANDRA-14183
> URL: https://issues.apache.org/jira/browse/CASSANDRA-14183
> Project: Cassandra
>  Issue Type: Improvement
>  Components: Libraries
>Reporter: Thiago Veronezi
>Assignee: Thiago Veronezi
>Priority: Major
>  Labels: patch, security
> Fix For: 3.11.x
>
> Attachments: 
> 0001-Update-to-logback-1.2.3-and-redefine-default-rotatio.patch
>
>
> Cassandra 3.11.1 is patched with logback 1.1.3, which contains the security 
> vulnerability described here. 
> [https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-5929]
> Also update to logback allows a simple date and size rotation policy to
> replace the default fixed policy, which is broken by design.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org

[jira] [Updated] (CASSANDRA-14183) CVE-2017-5929 Security vulnerability and redefine default log rotation policy

[Ariel Weisberg (JIRA)]

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

Ariel Weisberg updated CASSANDRA-14183:
---
Status: Ready to Commit  (was: Patch Available)

> CVE-2017-5929 Security vulnerability and redefine default log rotation policy
> -
>
> Key: CASSANDRA-14183
> URL: https://issues.apache.org/jira/browse/CASSANDRA-14183
> Project: Cassandra
>  Issue Type: Improvement
>  Components: Libraries
>Reporter: Thiago Veronezi
>Assignee: Thiago Veronezi
>Priority: Major
>  Labels: patch, security
> Fix For: 3.11.x
>
> Attachments: 
> 0001-Update-to-logback-1.2.3-and-redefine-default-rotatio.patch
>
>
> Cassandra 3.11.1 is patched with logback 1.1.3, which contains the security 
> vulnerability described here. 
> [https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-5929]
> Also update to logback allows a simple date and size rotation policy to
> replace the default fixed policy, which is broken by design.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org

[jira] [Commented] (CASSANDRA-14183) CVE-2017-5929 Security vulnerability and redefine default log rotation policy

[Jason Brown (JIRA)]

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

Jason Brown commented on CASSANDRA-14183:
-

I'm +1 on the NEWS.txt changes.

> CVE-2017-5929 Security vulnerability and redefine default log rotation policy
> -
>
> Key: CASSANDRA-14183
> URL: https://issues.apache.org/jira/browse/CASSANDRA-14183
> Project: Cassandra
>  Issue Type: Improvement
>  Components: Libraries
>Reporter: Thiago Veronezi
>Assignee: Thiago Veronezi
>Priority: Major
>  Labels: patch, security
> Fix For: 3.11.x
>
> Attachments: 
> 0001-Update-to-logback-1.2.3-and-redefine-default-rotatio.patch
>
>
> Cassandra 3.11.1 is patched with logback 1.1.3, which contains the security 
> vulnerability described here. 
> [https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-5929]
> Also update to logback allows a simple date and size rotation policy to
> replace the default fixed policy, which is broken by design.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org

[jira] [Comment Edited] (CASSANDRA-13396) Cassandra 3.10: ClassCastException in ThreadAwareSecurityManager

[Jason Brown (JIRA)]

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

Jason Brown edited comment on CASSANDRA-13396 at 2/14/18 5:53 PM:
--

OK, looks like this has drifted for long enough. I'm gonna look at the patches 
and review for commit.

UPDATE: I'll wait until CASSANDRA-14183 is committed before attacking this (as 
it touches logging, as well)


was (Author: jasobrown):
OK, looks like this has drifted for long enough. I'm gonna look at the patches 
and review for commit.

> Cassandra 3.10: ClassCastException in ThreadAwareSecurityManager
> 
>
> Key: CASSANDRA-13396
> URL: https://issues.apache.org/jira/browse/CASSANDRA-13396
> Project: Cassandra
>  Issue Type: Bug
>Reporter: Edward Capriolo
>Assignee: Eugene Fedotov
>Priority: Minor
>
> https://www.mail-archive.com/user@cassandra.apache.org/msg51603.html



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org

[jira] [Commented] (CASSANDRA-13396) Cassandra 3.10: ClassCastException in ThreadAwareSecurityManager

[Jason Brown (JIRA)]

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

Jason Brown commented on CASSANDRA-13396:
-

OK, looks like this has drifted for long enough. I'm gonna look at the patches 
and review for commit.

> Cassandra 3.10: ClassCastException in ThreadAwareSecurityManager
> 
>
> Key: CASSANDRA-13396
> URL: https://issues.apache.org/jira/browse/CASSANDRA-13396
> Project: Cassandra
>  Issue Type: Bug
>Reporter: Edward Capriolo
>Assignee: Eugene Fedotov
>Priority: Minor
>
> https://www.mail-archive.com/user@cassandra.apache.org/msg51603.html



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org

[jira] [Updated] (CASSANDRA-14200) NullPointerException when dumping sstable with null value for timestamp column

[Anonymous (JIRA)]

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

Anonymous updated CASSANDRA-14200:
--
Status: In Progress  (was: Ready to Commit)

> NullPointerException when dumping sstable with null value for timestamp column
> --
>
> Key: CASSANDRA-14200
> URL: https://issues.apache.org/jira/browse/CASSANDRA-14200
> Project: Cassandra
>  Issue Type: Bug
>Reporter: Simon Zhou
>Assignee: Simon Zhou
>Priority: Major
> Fix For: 3.0.x
>
>
> We have an sstable whose schema has a column of type timestamp and it's not 
> part of primary key. When dumping the sstable using sstabledump there is NPE 
> like this:
> {code:java}
> Exception in thread "main" java.lang.NullPointerException
> at java.util.Calendar.setTime(Calendar.java:1770)
> at java.text.SimpleDateFormat.format(SimpleDateFormat.java:943)
> at java.text.SimpleDateFormat.format(SimpleDateFormat.java:936)
> at java.text.DateFormat.format(DateFormat.java:345)
> at 
> org.apache.cassandra.db.marshal.TimestampType.toJSONString(TimestampType.java:93)
> at 
> org.apache.cassandra.tools.JsonTransformer.serializeCell(JsonTransformer.java:442)
> at 
> org.apache.cassandra.tools.JsonTransformer.serializeColumnData(JsonTransformer.java:376)
> at 
> org.apache.cassandra.tools.JsonTransformer.serializeRow(JsonTransformer.java:280)
> at 
> org.apache.cassandra.tools.JsonTransformer.serializePartition(JsonTransformer.java:215)
> at java.util.stream.ForEachOps$ForEachOp$OfRef.accept(ForEachOps.java:184)
> at java.util.stream.ReferencePipeline$2$1.accept(ReferencePipeline.java:175)
> at java.util.Iterator.forEachRemaining(Iterator.java:116)
> at 
> java.util.Spliterators$IteratorSpliterator.forEachRemaining(Spliterators.java:1801)
> at java.util.stream.AbstractPipeline.copyInto(AbstractPipeline.java:481)
> at 
> java.util.stream.AbstractPipeline.wrapAndCopyInto(AbstractPipeline.java:471)
> at 
> java.util.stream.ForEachOps$ForEachOp.evaluateSequential(ForEachOps.java:151)
> at 
> java.util.stream.ForEachOps$ForEachOp$OfRef.evaluateSequential(ForEachOps.java:174)
> at java.util.stream.AbstractPipeline.evaluate(AbstractPipeline.java:234)
> at java.util.stream.ReferencePipeline.forEach(ReferencePipeline.java:418)
> at org.apache.cassandra.tools.JsonTransformer.toJson(JsonTransformer.java:104)
> at org.apache.cassandra.tools.SSTableExport.main(SSTableExport.java:242){code}
> The reason is that we use a null Date when there is no value for this column:
> {code}
> public Date deserialize(ByteBuffer bytes)
> {
> return bytes.remaining() == 0 ? null : new 
> Date(ByteBufferUtil.toLong(bytes));
> }
> {code}
> It seems that we should not deserialize columns with null values.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org

[jira] [Commented] (CASSANDRA-14055) Index redistribution breaks SASI index

[Ludovic Boutros (JIRA)]

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

Ludovic Boutros commented on CASSANDRA-14055:
-

[~jrwest], 

??As I am writing this, however, I am realizing we want to keep a reference to 
the newer index, which references the newer SSTable instance and my patch does 
the opposite — keeping the old instance. I will post an updated patch along 
with my trunk patch for internal review, but the gist is to change the order we 
iterate over the old view and new indexes to favor new index instances.??

That was the point of my initial patch. But I aggree, if we can increment the 
global ref count with the new index before releasing the old one and therefore 
prevent the index file deletion, that would be better.

> Index redistribution breaks SASI index
> --
>
> Key: CASSANDRA-14055
> URL: https://issues.apache.org/jira/browse/CASSANDRA-14055
> Project: Cassandra
>  Issue Type: Bug
>  Components: sasi
>Reporter: Ludovic Boutros
>Assignee: Ludovic Boutros
>Priority: Major
>  Labels: patch
> Fix For: 3.11.x, 4.x
>
> Attachments: CASSANDRA-14055-jrwest.patch, CASSANDRA-14055.patch, 
> CASSANDRA-14055.patch, CASSANDRA-14055.patch
>
>
> During index redistribution process, a new view is created.
> During this creation, old indexes should be released.
> But, new indexes are "attached" to the same SSTable as the old indexes.
> This leads to the deletion of the last SASI index file and breaks the index.
> The issue is in this function : 
> [https://github.com/apache/cassandra/blob/9ee44db49b13d4b4c91c9d6332ce06a6e2abf944/src/java/org/apache/cassandra/index/sasi/conf/view/View.java#L62]



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org

[jira] [Comment Edited] (CASSANDRA-14055) Index redistribution breaks SASI index

[Jordan West (JIRA)]

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

Jordan West edited comment on CASSANDRA-14055 at 2/14/18 5:22 PM:
--

[~jasobrown], sorry for the trunk issues. The way {{TableMetadata}} is 
accessed/stored was changed and the test will need to be modified as a result. 
Will post a separate patch for trunk. 

[~lboutros], In my testing, the primary issue I saw was that files were removed 
from the SASI {{View}} that shouldn't be. The test writes 5 sstables (with 
sequence numbers 1-4 & 6) and during the test a compaction typically happens 
(that generates a sstable with generation 5 from sstables 1-4). The final SASI 
{{View}} when the queries are performed should contain either (1-4, 6) or (5, 
6)*. The test fails by returning 8 keys instead of 10 when the SASI {{View}} 
ends up containing only sstable 5 or by returning 0 keys instead of 10 when the 
SASI {{View}} ends up empty. 

The issue occurs when index redistribution completes. Depending on the 
interleaving* of events (the memtable flush, compaction, and redistribution), 
redistribution re-opens sstable 6, and sometimes re-opens sstable 5. This 
results in an {{SSTableListChangedNotification}}, which in turn results in the 
creation of a new {{View}},  where {{added=[6]}} (or {{added=[5,6]}}) and 
{{removed=[6]}} (or {{removed=[5,6]}}). The SASI {{View}} was written assuming 
these two sets were disjoint, which is why any reader in {{oldSSTables}} caused 
the index to be closed. This is incorrect in both cases because sstables 5 and 
6 are indeed the active data files (5 contains keys 0-8, and 6 contains keys 9 
& 10). 

Regarding the ref counting, we want to maintain one reference to sstables 5 & 6 
via their SSTableIndex instance but we’ve created a second reference and one 
needs to be closed. This is ensured by the 
{{newView.containsKey(sstable.descriptor)}} part of the conditional (so we are 
still indeed calling {{#release()}} on one instance). As I am writing this, 
however, I am realizing we want to keep a reference to the newer index, which 
references the newer SSTable instance and my patch does the opposite — keeping 
the old instance. I will post an updated patch along with my trunk patch for 
internal review, but the gist is to change the order we iterate over the old 
view and new indexes to favor new index instances.

NOTE: I've ignored https://issues.apache.org/jira/browse/CASSANDRA-14207 above

*I've found a few other interleavings by using another machine, but the general 
issue is the same.


was (Author: jrwest):
[~jasobrown], sorry for the trunk issues. The way {{TableMetadata}} is 
accessed/stored was changed and the test will need to be modified as a result. 
Will post a separate patch for trunk. 

[~lboutros], In my testing, the primary issue I saw was that files were removed 
from the SASI {{View}} that shouldn't be. The test writes 5 sstables (with 
sequence numbers 1-4 & 6) and during the test a compaction typically happens 
(that generates a sstable with generation 5 from sstables 1-4). The final SASI 
{{View}} when the queries are performed should contain either (1-4, 6) or (5, 
6)*. The test fails by returning 8 keys instead of 10 when the SASI {{View}} 
ends up containing only sstable 5 or by returning 0 keys instead of 10 when the 
SASI {{View}} ends up empty. 

The issue occurs when index redistribution completes. Depending on the 
interleaving* of events (the memtable flush, compaction, and redistribution), 
redistribution re-opens sstable 6, and sometimes re-opens sstable 5. This 
results in an {{SSTableListChangedNotification}}, which in turn results in the 
creation of a new {{View}},  where {{added=6}} (or {{added=[5,6]}}) and 
{{removed=6}} (or {{removed=[5,6]}}). The SASI {{View}} was written assuming 
these two sets were disjoint, which is why any reader in {{oldSSTables}} caused 
the index to be closed. This is incorrect in both cases because sstables 5 and 
6 are indeed the active data files (5 contains keys 0-8, and 6 contains keys 9 
& 10). 

Regarding the ref counting, we want to maintain one reference to sstables 5 & 6 
via their SSTableIndex instance but we’ve created a second reference and one 
needs to be closed. This is ensured by the 
{{newView.containsKey(sstable.descriptor)}} part of the conditional (so we are 
still indeed calling {{#release()}} on one instance). As I am writing this, 
however, I am realizing we want to keep a reference to the newer index, which 
references the newer SSTable instance and my patch does the opposite — keeping 
the old instance. I will post an updated patch along with my trunk patch for 
internal review, but the gist is to change the order we iterate over the old 
view and new indexes to favor new index instances.

NOTE: I've ignored https://issues.apache.org/jira/browse/CASSANDRA-14207 

[jira] [Commented] (CASSANDRA-14183) CVE-2017-5929 Security vulnerability and redefine default log rotation policy

[Ariel Weisberg (JIRA)]

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

Ariel Weisberg commented on CASSANDRA-14183:


Trunk updates:
https://github.com/apache/cassandra/compare/trunk...aweisberg:cassandra-14183-trunk?expand=1
https://circleci.com/gh/aweisberg/cassandra/tree/cassandra-14183-trunk

NEWS.txt update for 2.1.21 to be merged forward
https://github.com/apache/cassandra/compare/cassandra-2.1...aweisberg:cassandra-14183-2.1?expand=1

> CVE-2017-5929 Security vulnerability and redefine default log rotation policy
> -
>
> Key: CASSANDRA-14183
> URL: https://issues.apache.org/jira/browse/CASSANDRA-14183
> Project: Cassandra
>  Issue Type: Improvement
>  Components: Libraries
>Reporter: Thiago Veronezi
>Assignee: Thiago Veronezi
>Priority: Major
>  Labels: patch, security
> Fix For: 3.11.x
>
> Attachments: 
> 0001-Update-to-logback-1.2.3-and-redefine-default-rotatio.patch
>
>
> Cassandra 3.11.1 is patched with logback 1.1.3, which contains the security 
> vulnerability described here. 
> [https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-5929]
> Also update to logback allows a simple date and size rotation policy to
> replace the default fixed policy, which is broken by design.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org

[jira] [Commented] (CASSANDRA-14055) Index redistribution breaks SASI index

[Jordan West (JIRA)]

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

Jordan West commented on CASSANDRA-14055:
-

[~jasobrown], sorry for the trunk issues. The way {{TableMetadata}} is 
accessed/stored was changed and the test will need to be modified as a result. 
Will post a separate patch for trunk. 

[~lboutros], In my testing, the primary issue I saw was that files were removed 
from the SASI {{View}} that shouldn't be. The test writes 5 sstables (with 
sequence numbers 1-4 & 6) and during the test a compaction typically happens 
(that generates a sstable with generation 5 from sstables 1-4). The final SASI 
{{View}} when the queries are performed should contain either (1-4, 6) or (5, 
6)*. The test fails by returning 8 keys instead of 10 when the SASI {{View}} 
ends up containing only sstable 5 or by returning 0 keys instead of 10 when the 
SASI {{View}} ends up empty. 

The issue occurs when index redistribution completes. Depending on the 
interleaving* of events (the memtable flush, compaction, and redistribution), 
redistribution re-opens sstable 6, and sometimes re-opens sstable 5. This 
results in an {{SSTableListChangedNotification}}, which in turn results in the 
creation of a new {{View}},  where {{added=6}} (or {{added=[5,6]}}) and 
{{removed=6}} (or {{removed=[5,6]}}). The SASI {{View}} was written assuming 
these two sets were disjoint, which is why any reader in {{oldSSTables}} caused 
the index to be closed. This is incorrect in both cases because sstables 5 and 
6 are indeed the active data files (5 contains keys 0-8, and 6 contains keys 9 
& 10). 

Regarding the ref counting, we want to maintain one reference to sstables 5 & 6 
via their SSTableIndex instance but we’ve created a second reference and one 
needs to be closed. This is ensured by the 
{{newView.containsKey(sstable.descriptor)}} part of the conditional (so we are 
still indeed calling {{#release()}} on one instance). As I am writing this, 
however, I am realizing we want to keep a reference to the newer index, which 
references the newer SSTable instance and my patch does the opposite — keeping 
the old instance. I will post an updated patch along with my trunk patch for 
internal review, but the gist is to change the order we iterate over the old 
view and new indexes to favor new index instances.

NOTE: I've ignored https://issues.apache.org/jira/browse/CASSANDRA-14207 above

*I've found a few other interleavings by using another machine, but the general 
issue is the same.

> Index redistribution breaks SASI index
> --
>
> Key: CASSANDRA-14055
> URL: https://issues.apache.org/jira/browse/CASSANDRA-14055
> Project: Cassandra
>  Issue Type: Bug
>  Components: sasi
>Reporter: Ludovic Boutros
>Assignee: Ludovic Boutros
>Priority: Major
>  Labels: patch
> Fix For: 3.11.x, 4.x
>
> Attachments: CASSANDRA-14055-jrwest.patch, CASSANDRA-14055.patch, 
> CASSANDRA-14055.patch, CASSANDRA-14055.patch
>
>
> During index redistribution process, a new view is created.
> During this creation, old indexes should be released.
> But, new indexes are "attached" to the same SSTable as the old indexes.
> This leads to the deletion of the last SASI index file and breaks the index.
> The issue is in this function : 
> [https://github.com/apache/cassandra/blob/9ee44db49b13d4b4c91c9d6332ce06a6e2abf944/src/java/org/apache/cassandra/index/sasi/conf/view/View.java#L62]



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org

[jira] [Updated] (CASSANDRA-14183) CVE-2017-5929 Security vulnerability and redefine default log rotation policy

[Ariel Weisberg (JIRA)]

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

Ariel Weisberg updated CASSANDRA-14183:
---
Description: 
Cassandra 3.11.1 is patched with logback 1.1.3, which contains the security 
vulnerability described here. 
[https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-5929]

Also update to logback allows a simple date and size rotation policy to
replace the default fixed policy, which is broken by design.

  was:Cassandra 3.11.1 is patched with logback 1.1.3, which contains the 
security vulnerability described here. 
[https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-5929]


> CVE-2017-5929 Security vulnerability and redefine default log rotation policy
> -
>
> Key: CASSANDRA-14183
> URL: https://issues.apache.org/jira/browse/CASSANDRA-14183
> Project: Cassandra
>  Issue Type: Improvement
>  Components: Libraries
>Reporter: Thiago Veronezi
>Assignee: Thiago Veronezi
>Priority: Major
>  Labels: patch, security
> Fix For: 3.11.x
>
> Attachments: 
> 0001-Update-to-logback-1.2.3-and-redefine-default-rotatio.patch
>
>
> Cassandra 3.11.1 is patched with logback 1.1.3, which contains the security 
> vulnerability described here. 
> [https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-5929]
> Also update to logback allows a simple date and size rotation policy to
> replace the default fixed policy, which is broken by design.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org

[jira] [Updated] (CASSANDRA-14183) CVE-2017-5929 Security vulnerability and redefine default log rotation policy

[Ariel Weisberg (JIRA)]

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

Ariel Weisberg updated CASSANDRA-14183:
---
Summary: CVE-2017-5929 Security vulnerability and redefine default log 
rotation policy  (was: CVE-2017-5929 Security vulnerability)

> CVE-2017-5929 Security vulnerability and redefine default log rotation policy
> -
>
> Key: CASSANDRA-14183
> URL: https://issues.apache.org/jira/browse/CASSANDRA-14183
> Project: Cassandra
>  Issue Type: Improvement
>  Components: Libraries
>Reporter: Thiago Veronezi
>Assignee: Thiago Veronezi
>Priority: Major
>  Labels: patch, security
> Fix For: 3.11.x
>
> Attachments: 
> 0001-Update-to-logback-1.2.3-and-redefine-default-rotatio.patch
>
>
> Cassandra 3.11.1 is patched with logback 1.1.3, which contains the security 
> vulnerability described here. 
> [https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-5929]



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org

[jira] [Commented] (CASSANDRA-14058) Refactor read executor and response resolver, abstract read repair

[Blake Eggleston (JIRA)]

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

Blake Eggleston commented on CASSANDRA-14058:
-

I'd rebased after CASSANDRA-7544 was committed and saw some dtest failures. It 
should be committed soon, I just haven't had enough contiguous free time to get 
everything buttoned up.

> Refactor read executor and response resolver, abstract read repair
> --
>
> Key: CASSANDRA-14058
> URL: https://issues.apache.org/jira/browse/CASSANDRA-14058
> Project: Cassandra
>  Issue Type: Improvement
>Reporter: Blake Eggleston
>Assignee: Blake Eggleston
>Priority: Major
> Fix For: 4.0
>
>
> CASSANDRA-10726 is stuck right now because the state of 
> {{AbstractReadExecutor}} and {{DataResolver}} make it difficult to cleanly 
> implement. It also looks like some additional read repair strategies might be 
> added. This goal of this ticket is to clean up the structure of some of the 
> read path components to make CASSANDRA-10726 doable, and additional read 
> repair strategies possible.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org

[jira] [Commented] (CASSANDRA-13396) Cassandra 3.10: ClassCastException in ThreadAwareSecurityManager

[Claude Warren (JIRA)]

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

Claude Warren commented on CASSANDRA-13396:
---

It is unclear to me whether or not the proposed patch has been/will be accepted 
into the code base.  What is the current thinking and if it is to be added when 
might that be?

I have hit this issue when trying to run Cassandra in a unit test situation 
where I am testing an implementation of an SPI and am unable to convert product 
to logback.

> Cassandra 3.10: ClassCastException in ThreadAwareSecurityManager
> 
>
> Key: CASSANDRA-13396
> URL: https://issues.apache.org/jira/browse/CASSANDRA-13396
> Project: Cassandra
>  Issue Type: Bug
>Reporter: Edward Capriolo
>Assignee: Eugene Fedotov
>Priority: Minor
>
> https://www.mail-archive.com/user@cassandra.apache.org/msg51603.html



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org

[jira] [Updated] (CASSANDRA-14169) Trivial intellij junit run fix

[Stefan Podkowinski (JIRA)]

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

Stefan Podkowinski updated CASSANDRA-14169:
---
   Resolution: Fixed
 Reviewer: Stefan Podkowinski
Fix Version/s: 4.0
   Status: Resolved  (was: Patch Available)

Thanks Jay!
Merged as 7a424bc2a79dce98817054057dd3a479b202f09e to trunk.


> Trivial intellij junit run fix
> --
>
> Key: CASSANDRA-14169
> URL: https://issues.apache.org/jira/browse/CASSANDRA-14169
> Project: Cassandra
>  Issue Type: Bug
>Reporter: Jay Zhuang
>Assignee: Jay Zhuang
>Priority: Trivial
> Fix For: 4.0
>
>
> Unable to run 
> {{[LegacySSTableTest|https://github.com/apache/cassandra/blob/trunk/test/unit/org/apache/cassandra/io/sstable/LegacySSTableTest.java#L63]}}
>  in the Intellij, because the 
> {{[legacy-sstable-root|https://github.com/apache/cassandra/blob/trunk/test/unit/org/apache/cassandra/io/sstable/LegacySSTableTest.java#L96]}}
>  is not defined.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org

cassandra git commit: Update Intellij JUnit configuration

[spod]

Repository: cassandra
Updated Branches:
  refs/heads/trunk cf66b7ea2 -> 7a424bc2a


Update Intellij JUnit configuration

And other ninja build fixes.

patch by Jay Zhuang; reviewed by Stefan Podkowinski for CASSANDRA-14169


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

Branch: refs/heads/trunk
Commit: 7a424bc2a79dce98817054057dd3a479b202f09e
Parents: cf66b7e
Author: Jay Zhuang 
Authored: Sun Jan 14 21:43:30 2018 -0800
Committer: Stefan Podkowinski 
Committed: Wed Feb 14 16:32:24 2018 +0100

--
 build.xml   | 5 -
 ide/idea/workspace.xml  | 2 +-
 .../unit/org/apache/cassandra/io/sstable/LegacySSTableTest.java | 2 +-
 3 files changed, 2 insertions(+), 7 deletions(-)
--


http://git-wip-us.apache.org/repos/asf/cassandra/blob/7a424bc2/build.xml
--
diff --git a/build.xml b/build.xml
index e04ce18..bc9f0a7 100644
--- a/build.xml
+++ b/build.xml
@@ -1187,7 +1187,6 @@
 
   
   
-  
   
   
   
@@ -1205,7 +1204,6 @@
   
 
 
-
 
 
 
@@ -1225,7 +1223,6 @@
exclude="**/*.java" timeout="${test.timeout}" 
testtag="compression">
 
 
-
 
 
 
@@ -1245,7 +1242,6 @@
exclude="**/*.java" timeout="${test.timeout}" 
testtag="cdc">
 
 
-
 
 
 
@@ -1275,7 +1271,6 @@
   
   
   
-  
   
   
   

http://git-wip-us.apache.org/repos/asf/cassandra/blob/7a424bc2/ide/idea/workspace.xml
--
diff --git a/ide/idea/workspace.xml b/ide/idea/workspace.xml
index cdde5af..876ed58 100644
--- a/ide/idea/workspace.xml
+++ b/ide/idea/workspace.xml
@@ -167,7 +167,7 @@
   
   
   
-  
+  
   
   
   

http://git-wip-us.apache.org/repos/asf/cassandra/blob/7a424bc2/test/unit/org/apache/cassandra/io/sstable/LegacySSTableTest.java
--
diff --git a/test/unit/org/apache/cassandra/io/sstable/LegacySSTableTest.java 
b/test/unit/org/apache/cassandra/io/sstable/LegacySSTableTest.java
index f669cd7..84f7158 100644
--- a/test/unit/org/apache/cassandra/io/sstable/LegacySSTableTest.java
+++ b/test/unit/org/apache/cassandra/io/sstable/LegacySSTableTest.java
@@ -94,7 +94,7 @@ public class LegacySSTableTest
 public static void defineSchema() throws ConfigurationException
 {
 String scp = System.getProperty(LEGACY_SSTABLE_PROP);
-Assert.assertNotNull("System property " + LEGACY_SSTABLE_ROOT + " not 
set", scp);
+Assert.assertNotNull("System property " + LEGACY_SSTABLE_PROP + " not 
set", scp);
 
 LEGACY_SSTABLE_ROOT = new File(scp).getAbsoluteFile();
 Assert.assertTrue("System property " + LEGACY_SSTABLE_ROOT + " does 
not specify a directory", LEGACY_SSTABLE_ROOT.isDirectory());


-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org

[jira] [Created] (CASSANDRA-14235) ReadFailure Error -- Large Unbound Query

[Fraizier (JIRA)]

Fraizier created CASSANDRA-14235:


 Summary: ReadFailure Error -- Large Unbound Query 
 Key: CASSANDRA-14235
 URL: https://issues.apache.org/jira/browse/CASSANDRA-14235
 Project: Cassandra
  Issue Type: Bug
  Components: CQL
 Environment: My instance of Cassandra is a single local node. It was 
installed via a tar file, versus installing it as a service. All settings are 
default. 

I'm operating on a Centos 7 machine (release 7.4.1708)
Reporter: Fraizier
 Fix For: 3.11.1


Receiving ReadFailure Error when executing 'select' query with cassandra 
python-driver.  

I have a keyspace called "Documents" and a table with two columns, name and 
object. Name is the text datatype and object is the blob datatype. The blob 
objects are pickled python class instances. The description of the 
keyspace/table is as follows:

 
{code:java}
CREATE TABLE "Documents".table ( 
 name text PRIMARY KEY, 
 object blob 
) WITH bloom_filter_fp_chance = 0.01 
 AND caching = {'keys': 'ALL', 'rows_per_partition': 'NONE'} AND comment = 
'' 
 AND compaction = {'class': 
'org.apache.cassandra.db.compaction.SizeTieredCompactionStrategy', 
'max_threshold': '32', 'min_threshold': '4'} 
 AND compression = {'chunk_length_in_kb': '64', 'class': 
'org.apache.cassandra.io.compress.LZ4Compressor'} 
 AND crc_check_chance = 1.0 
 AND dclocal_read_repair_chance = 0.1 
 AND default_time_to_live = 0 AND gc_grace_seconds = 864000 
 AND max_index_interval = 2048 
 AND memtable_flush_period_in_ms = 0 AND min_index_interval = 128 
 AND read_repair_chance = 0.0 
 AND speculative_retry = '99PERCENTILE';{code}
 

There are 3509 rows contained within this table and each object is approx. 25kb 
of data. (so I'm estimating ~90Mb of data in the object column.) I'm attempting 
to run a simple line of python cassandra code :
{code:java}
rows = session.execute("SELECT name, object FROM table")
{code}
and in the log file of cassandra this is what is produced:
{code:java}
WARN  [ReadStage-4] 2018-02-13 14:53:12,319 
AbstractLocalAwareExecutorService.java:167 - Uncaught exception on thread 
Thread[ReadStage-4,10,main]: {}
java.lang.RuntimeException: java.lang.RuntimeException
at 
org.apache.cassandra.service.StorageProxy$DroppableRunnable.run(StorageProxy.java:2598)
 ~[apache-cassandra-3.11.1.jar:3.11.1]
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) 
~[na:1.8.0_151]
at 
org.apache.cassandra.concurrent.AbstractLocalAwareExecutorService$FutureTask.run(AbstractLocalAwareExecutorService.java:162)
 ~[apache-cassandra-3.11.1.jar:3.11.1]
at 
org.apache.cassandra.concurrent.AbstractLocalAwareExecutorService$LocalSessionFutureTask.run(AbstractLocalAwareExecutorService.java:134)
 [apache-cassandra-3.11.1.jar:3.11.1]
at org.apache.cassandra.concurrent.SEPWorker.run(SEPWorker.java:109) 
[apache-cassandra-3.11.1.jar:3.11.1]
at java.lang.Thread.run(Thread.java:748) [na:1.8.0_151]
Caused by: java.lang.RuntimeException: null
at 
org.apache.cassandra.io.util.DataOutputBuffer.validateReallocation(DataOutputBuffer.java:134)
 ~[apache-cassandra-3.11.1.jar:3.11.1]
at 
org.apache.cassandra.io.util.DataOutputBuffer.calculateNewSize(DataOutputBuffer.java:152)
 ~[apache-cassandra-3.11.1.jar:3.11.1]
at 
org.apache.cassandra.io.util.DataOutputBuffer.reallocate(DataOutputBuffer.java:159)
 ~[apache-cassandra-3.11.1.jar:3.11.1]
at 
org.apache.cassandra.io.util.DataOutputBuffer.doFlush(DataOutputBuffer.java:119)
 ~[apache-cassandra-3.11.1.jar:3.11.1]
at 
org.apache.cassandra.io.util.BufferedDataOutputStreamPlus.write(BufferedDataOutputStreamPlus.java:132)
 ~[apache-cassandra-3.11.1.jar:3.11.1]
at 
org.apache.cassandra.io.util.BufferedDataOutputStreamPlus.write(BufferedDataOutputStreamPlus.java:151)
 ~[apache-cassandra-3.11.1.jar:3.11.1]
at 
org.apache.cassandra.utils.ByteBufferUtil.writeWithVIntLength(ByteBufferUtil.java:296)
 ~[apache-cassandra-3.11.1.jar:3.11.1]
at 
org.apache.cassandra.db.marshal.AbstractType.writeValue(AbstractType.java:413) 
~[apache-cassandra-3.11.1.jar:3.11.1]
at org.apache.cassandra.db.rows.Cell$Serializer.serialize(Cell.java:210) 
~[apache-cassandra-3.11.1.jar:3.11.1]
at 
org.apache.cassandra.db.rows.UnfilteredSerializer.lambda$serializeRowBody$0(UnfilteredSerializer.java:248)
 ~[apache-cassandra-3.11.1.jar:3.11.1]
at org.apache.cassandra.utils.btree.BTree.applyForwards(BTree.java:1242) 
~[apache-cassandra-3.11.1.jar:3.11.1]
at org.apache.cassandra.utils.btree.BTree.apply(BTree.java:1197) 
~[apache-cassandra-3.11.1.jar:3.11.1]
at org.apache.cassandra.db.rows.BTreeRow.apply(BTreeRow.java:172) 
~[apache-cassandra-3.11.1.jar:3.11.1]
at 
org.apache.cassandra.db.rows.UnfilteredSerializer.serializeRowBody(UnfilteredSerializer.java:236)
 ~[apache-cassandra-3.11.1.jar:3.11.1]
at 

[jira] [Updated] (CASSANDRA-14234) ReadCommandTest::testCountWithNoDeletedRow broken

[Jason Brown (JIRA)]

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

Jason Brown updated CASSANDRA-14234:

Resolution: Fixed
Status: Resolved  (was: Patch Available)

+1. committed as sha {{1d506f9d09c880ff2b2693e3e27fa58c02ecf398}}

Thanks for the quick work on this, [~KurtG]. I appreciate it.

> ReadCommandTest::testCountWithNoDeletedRow broken
> -
>
> Key: CASSANDRA-14234
> URL: https://issues.apache.org/jira/browse/CASSANDRA-14234
> Project: Cassandra
>  Issue Type: Bug
>Reporter: Kurt Greaves
>Assignee: Kurt Greaves
>Priority: Major
> Fix For: 3.11.2, 4.0
>
>
> {code}junit.framework.AssertionFailedError: expected:<1> but was:<5>
>   at 
> org.apache.cassandra.db.ReadCommandTest.testCountWithNoDeletedRow(ReadCommandTest.java:336){code}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org

[2/3] cassandra git commit: Fix ReadCommandTest

[jasobrown]

Fix ReadCommandTest

patch by Kurt Greaves; reviewed by jasobrown for CASSANDRA-14234


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

Branch: refs/heads/trunk
Commit: 1d506f9d09c880ff2b2693e3e27fa58c02ecf398
Parents: d10e6ac
Author: kurt 
Authored: Wed Feb 14 01:06:24 2018 +
Committer: Jason Brown 
Committed: Wed Feb 14 05:19:48 2018 -0800

--
 CHANGES.txt |  1 +
 .../apache/cassandra/db/ReadCommandTest.java| 31 ++--
 2 files changed, 29 insertions(+), 3 deletions(-)
--


http://git-wip-us.apache.org/repos/asf/cassandra/blob/1d506f9d/CHANGES.txt
--
diff --git a/CHANGES.txt b/CHANGES.txt
index 31cee26..e2ccc53 100644
--- a/CHANGES.txt
+++ b/CHANGES.txt
@@ -1,4 +1,5 @@
 3.11.2
+ * Fix ReadCommandTest (CASSANDRA-14234)
  * Remove trailing period from latency reports at keyspace level 
(CASSANDRA-14233)
  * Backport CASSANDRA-13080: Use new token allocation for non bootstrap case 
as well (CASSANDRA-14212)
  * Remove dependencies on JVM internal classes from JMXServerUtils 
(CASSANDRA-14173) 

http://git-wip-us.apache.org/repos/asf/cassandra/blob/1d506f9d/test/unit/org/apache/cassandra/db/ReadCommandTest.java
--
diff --git a/test/unit/org/apache/cassandra/db/ReadCommandTest.java 
b/test/unit/org/apache/cassandra/db/ReadCommandTest.java
index 960539c..774645e 100644
--- a/test/unit/org/apache/cassandra/db/ReadCommandTest.java
+++ b/test/unit/org/apache/cassandra/db/ReadCommandTest.java
@@ -61,6 +61,8 @@ public class ReadCommandTest
 private static final String CF1 = "Standard1";
 private static final String CF2 = "Standard2";
 private static final String CF3 = "Standard3";
+private static final String CF4 = "Standard4";
+private static final String CF5 = "Standard5";
 
 @BeforeClass
 public static void defineSchema() throws ConfigurationException
@@ -85,12 +87,35 @@ public class ReadCommandTest
  .addRegularColumn("e", 
AsciiType.instance)
  .addRegularColumn("f", 
AsciiType.instance).build();
 
+CFMetaData metadata4 = CFMetaData.Builder.create(KEYSPACE, CF4)
+ .addPartitionKey("key", 
BytesType.instance)
+ .addClusteringColumn("col", 
AsciiType.instance)
+ .addRegularColumn("a", 
AsciiType.instance)
+ .addRegularColumn("b", 
AsciiType.instance)
+ .addRegularColumn("c", 
AsciiType.instance)
+ .addRegularColumn("d", 
AsciiType.instance)
+ .addRegularColumn("e", 
AsciiType.instance)
+ .addRegularColumn("f", 
AsciiType.instance).build();
+
+CFMetaData metadata5 = CFMetaData.Builder.create(KEYSPACE, CF5)
+ .addPartitionKey("key", 
BytesType.instance)
+ .addClusteringColumn("col", 
AsciiType.instance)
+ .addRegularColumn("a", 
AsciiType.instance)
+ .addRegularColumn("b", 
AsciiType.instance)
+ .addRegularColumn("c", 
AsciiType.instance)
+ .addRegularColumn("d", 
AsciiType.instance)
+ .addRegularColumn("e", 
AsciiType.instance)
+ .addRegularColumn("f", 
AsciiType.instance).build();
+
+
 SchemaLoader.prepareServer();
 SchemaLoader.createKeyspace(KEYSPACE,
 KeyspaceParams.simple(1),
 metadata1,
 metadata2,
-metadata3);
+metadata3,
+metadata4,
+metadata5);
 }
 
 @Test
@@ -260,7 +285,7 @@ public class ReadCommandTest
 @Test
 public void testCountDeletedRows() throws Exception
 {
-ColumnFamilyStore cfs = 

[1/3] cassandra git commit: Fix ReadCommandTest

[jasobrown]

Repository: cassandra
Updated Branches:
  refs/heads/cassandra-3.11 d10e6ac60 -> 1d506f9d0
  refs/heads/trunk 74b2013ea -> cf66b7ea2


Fix ReadCommandTest

patch by Kurt Greaves; reviewed by jasobrown for CASSANDRA-14234


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

Branch: refs/heads/cassandra-3.11
Commit: 1d506f9d09c880ff2b2693e3e27fa58c02ecf398
Parents: d10e6ac
Author: kurt 
Authored: Wed Feb 14 01:06:24 2018 +
Committer: Jason Brown 
Committed: Wed Feb 14 05:19:48 2018 -0800

--
 CHANGES.txt |  1 +
 .../apache/cassandra/db/ReadCommandTest.java| 31 ++--
 2 files changed, 29 insertions(+), 3 deletions(-)
--


http://git-wip-us.apache.org/repos/asf/cassandra/blob/1d506f9d/CHANGES.txt
--
diff --git a/CHANGES.txt b/CHANGES.txt
index 31cee26..e2ccc53 100644
--- a/CHANGES.txt
+++ b/CHANGES.txt
@@ -1,4 +1,5 @@
 3.11.2
+ * Fix ReadCommandTest (CASSANDRA-14234)
  * Remove trailing period from latency reports at keyspace level 
(CASSANDRA-14233)
  * Backport CASSANDRA-13080: Use new token allocation for non bootstrap case 
as well (CASSANDRA-14212)
  * Remove dependencies on JVM internal classes from JMXServerUtils 
(CASSANDRA-14173) 

http://git-wip-us.apache.org/repos/asf/cassandra/blob/1d506f9d/test/unit/org/apache/cassandra/db/ReadCommandTest.java
--
diff --git a/test/unit/org/apache/cassandra/db/ReadCommandTest.java 
b/test/unit/org/apache/cassandra/db/ReadCommandTest.java
index 960539c..774645e 100644
--- a/test/unit/org/apache/cassandra/db/ReadCommandTest.java
+++ b/test/unit/org/apache/cassandra/db/ReadCommandTest.java
@@ -61,6 +61,8 @@ public class ReadCommandTest
 private static final String CF1 = "Standard1";
 private static final String CF2 = "Standard2";
 private static final String CF3 = "Standard3";
+private static final String CF4 = "Standard4";
+private static final String CF5 = "Standard5";
 
 @BeforeClass
 public static void defineSchema() throws ConfigurationException
@@ -85,12 +87,35 @@ public class ReadCommandTest
  .addRegularColumn("e", 
AsciiType.instance)
  .addRegularColumn("f", 
AsciiType.instance).build();
 
+CFMetaData metadata4 = CFMetaData.Builder.create(KEYSPACE, CF4)
+ .addPartitionKey("key", 
BytesType.instance)
+ .addClusteringColumn("col", 
AsciiType.instance)
+ .addRegularColumn("a", 
AsciiType.instance)
+ .addRegularColumn("b", 
AsciiType.instance)
+ .addRegularColumn("c", 
AsciiType.instance)
+ .addRegularColumn("d", 
AsciiType.instance)
+ .addRegularColumn("e", 
AsciiType.instance)
+ .addRegularColumn("f", 
AsciiType.instance).build();
+
+CFMetaData metadata5 = CFMetaData.Builder.create(KEYSPACE, CF5)
+ .addPartitionKey("key", 
BytesType.instance)
+ .addClusteringColumn("col", 
AsciiType.instance)
+ .addRegularColumn("a", 
AsciiType.instance)
+ .addRegularColumn("b", 
AsciiType.instance)
+ .addRegularColumn("c", 
AsciiType.instance)
+ .addRegularColumn("d", 
AsciiType.instance)
+ .addRegularColumn("e", 
AsciiType.instance)
+ .addRegularColumn("f", 
AsciiType.instance).build();
+
+
 SchemaLoader.prepareServer();
 SchemaLoader.createKeyspace(KEYSPACE,
 KeyspaceParams.simple(1),
 metadata1,
 metadata2,
-metadata3);
+metadata3,
+metadata4,
+metadata5);
 }
 
 @Test
@@ -260,7 +285,7 @@ public class ReadCommandTest
 

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

[jasobrown]

Merge branch 'cassandra-3.11' into trunk


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

Branch: refs/heads/trunk
Commit: cf66b7ea2dfc296977a4fe2bdd56171ba937f48b
Parents: 74b2013 1d506f9
Author: Jason Brown 
Authored: Wed Feb 14 05:23:02 2018 -0800
Committer: Jason Brown 
Committed: Wed Feb 14 05:25:31 2018 -0800

--
 CHANGES.txt |  1 +
 .../apache/cassandra/db/ReadCommandTest.java| 39 +---
 2 files changed, 34 insertions(+), 6 deletions(-)
--


http://git-wip-us.apache.org/repos/asf/cassandra/blob/cf66b7ea/CHANGES.txt
--
diff --cc CHANGES.txt
index f5036df,e2ccc53..e932b40
--- a/CHANGES.txt
+++ b/CHANGES.txt
@@@ -1,206 -1,18 +1,207 @@@
 +4.0
 + * Use JVM default SSL validation algorithm instead of custom default 
(CASSANDRA-13259)
 + * Better document in code InetAddressAndPort usage post 7544, incorporate 
port into UUIDGen node (CASSANDRA-14226)
 + * Fix sstablemetadata date string for minLocalDeletionTime (CASSANDRA-14132)
 + * Make it possible to change neverPurgeTombstones during runtime 
(CASSANDRA-14214)
 + * Remove GossipDigestSynVerbHandler#doSort() (CASSANDRA-14174)
 + * Add nodetool clientlist (CASSANDRA-13665)
 + * Revert ProtocolVersion changes from CASSANDRA-7544 (CASSANDRA-14211)
 + * Non-disruptive seed node list reload (CASSANDRA-14190)
 + * Nodetool tablehistograms to print statics for all the tables 
(CASSANDRA-14185)
 + * Migrate dtests to use pytest and python3 (CASSANDRA-14134)
 + * Allow storage port to be configurable per node (CASSANDRA-7544)
 + * Make sub-range selection for non-frozen collections return null instead of 
empty (CASSANDRA-14182)
 + * BloomFilter serialization format should not change byte ordering 
(CASSANDRA-9067)
 + * Remove unused on-heap BloomFilter implementation (CASSANDRA-14152)
 + * Delete temp test files on exit (CASSANDRA-14153)
 + * Make PartitionUpdate and Mutation immutable (CASSANDRA-13867)
 + * Fix CommitLogReplayer exception for CDC data (CASSANDRA-14066)
 + * Fix cassandra-stress startup failure (CASSANDRA-14106)
 + * Remove initialDirectories from CFS (CASSANDRA-13928)
 + * Fix trivial log format error (CASSANDRA-14015)
 + * Allow sstabledump to do a json object per partition (CASSANDRA-13848)
 + * Add option to optimise merkle tree comparison across replicas 
(CASSANDRA-3200)
 + * Remove unused and deprecated methods from AbstractCompactionStrategy 
(CASSANDRA-14081)
 + * Fix Distribution.average in cassandra-stress (CASSANDRA-14090)
 + * Support a means of logging all queries as they were invoked 
(CASSANDRA-13983)
 + * Presize collections (CASSANDRA-13760)
 + * Add GroupCommitLogService (CASSANDRA-13530)
 + * Parallelize initial materialized view build (CASSANDRA-12245)
 + * Fix flaky SecondaryIndexManagerTest.assert[Not]MarkedAsBuilt 
(CASSANDRA-13965)
 + * Make LWTs send resultset metadata on every request (CASSANDRA-13992)
 + * Fix flaky indexWithFailedInitializationIsNotQueryableAfterPartialRebuild 
(CASSANDRA-13963)
 + * Introduce leaf-only iterator (CASSANDRA-9988)
 + * Upgrade Guava to 23.3 and Airline to 0.8 (CASSANDRA-13997)
 + * Allow only one concurrent call to StatusLogger (CASSANDRA-12182)
 + * Refactoring to specialised functional interfaces (CASSANDRA-13982)
 + * Speculative retry should allow more friendly params (CASSANDRA-13876)
 + * Throw exception if we send/receive repair messages to incompatible nodes 
(CASSANDRA-13944)
 + * Replace usages of MessageDigest with Guava's Hasher (CASSANDRA-13291)
 + * Add nodetool cmd to print hinted handoff window (CASSANDRA-13728)
 + * Fix some alerts raised by static analysis (CASSANDRA-13799)
 + * Checksum sstable metadata (CASSANDRA-13321, CASSANDRA-13593)
 + * Add result set metadata to prepared statement MD5 hash calculation 
(CASSANDRA-10786)
 + * Refactor GcCompactionTest to avoid boxing (CASSANDRA-13941)
 + * Expose recent histograms in JmxHistograms (CASSANDRA-13642)
 + * Fix buffer length comparison when decompressing in netty-based streaming 
(CASSANDRA-13899)
 + * Properly close StreamCompressionInputStream to release any ByteBuf 
(CASSANDRA-13906)
 + * Add SERIAL and LOCAL_SERIAL support for cassandra-stress (CASSANDRA-13925)
 + * LCS needlessly checks for L0 STCS candidates multiple times 
(CASSANDRA-12961)
 + * Correctly close netty channels when a stream session ends (CASSANDRA-13905)
 + * Update lz4 to 1.4.0 (CASSANDRA-13741)
 + * Optimize Paxos prepare and propose stage for local requests 
(CASSANDRA-13862)
 + * Throttle base partitions during MV 

[jira] [Updated] (CASSANDRA-14209) group by select queries query results differ when using select * vs select fields

[JIRA]

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

Andrés de la Peña updated CASSANDRA-14209:
--
Status: Ready to Commit  (was: Patch Available)

> group by select queries query results differ when using select * vs select 
> fields
> -
>
> Key: CASSANDRA-14209
> URL: https://issues.apache.org/jira/browse/CASSANDRA-14209
> Project: Cassandra
>  Issue Type: Bug
>Reporter: Digant Modha
>Assignee: Benjamin Lerer
>Priority: Minor
> Attachments: Re group by select queries.txt
>
>
> {{I get two different out with these 2 queries.  The only difference between 
> the 2 queries is that one does ‘select *’ and other does ‘select specific 
> fields’ without any aggregate functions.}}
> {{I am using Apache Cassandra 3.10.}}
> {{Consistency level set to LOCAL_QUORUM.}}
> {{cassandra@cqlsh> select * from wp.position where account_id = 'user_1';}}
> {{ account_id | security_id | counter | avg_exec_price | pending_quantity | 
> quantity | transaction_id | update_time}}
> {{+-+-++--+--++-}}
> {{ user_1 | AMZN | 2 | 1239.2 | 0 | 1011 | null | 2018-01-25 
> 17:18:07.158000+}}
> {{ user_1 | AMZN | 1 | 1239.2 | 0 | 1010 | null | 2018-01-25 
> 17:18:07.158000+}}
> {{(2 rows)}}
> {{cassandra@cqlsh> select * from wp.position where account_id = 'user_1' 
> group by security_id;}}
> {{ account_id | security_id | counter | avg_exec_price | pending_quantity | 
> quantity | transaction_id | update_time}}
> {{+-+-++--+--++-}}
> {{ user_1 | AMZN | 1 | 1239.2 | 0 | 1010 | null | 2018-01-25 
> 17:18:07.158000+}}
> {{(1 rows)}}
> {{cassandra@cqlsh> select account_id,security_id, counter, 
> avg_exec_price,quantity, update_time from wp.position where account_id = 
> 'user_1' group by security_id ;}}
> {{ account_id | security_id | counter | avg_exec_price | quantity | 
> update_time}}
> {{+-+-++--+-}}
> {{ user_1 | AMZN | 2 | 1239.2 | 1011 | 2018-01-25 17:18:07.158000+}}
> {{(1 rows)}}
> {{Table Description:}}
> {{CREATE TABLE wp.position (}}
> {{ account_id text,}}
> {{ security_id text,}}
> {{ counter bigint,}}
> {{ avg_exec_price double,}}
> {{ pending_quantity double,}}
> {{ quantity double,}}
> {{ transaction_id uuid,}}
> {{ update_time timestamp,}}
> {{ PRIMARY KEY (account_id, security_id, counter)}}
> {{) WITH CLUSTERING ORDER BY (security_id ASC, counter DESC)}}{{ }}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org

[jira] [Commented] (CASSANDRA-13929) BTree$Builder / io.netty.util.Recycler$Stack leaking memory

[Norman Maurer (JIRA)]

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

Norman Maurer commented on CASSANDRA-13929:
---

[~tsteinmaurer] yeah thanks I see... So looks more like a misusage for me then 
a netty bug. Cassandra may also consider to configure the `Recycler` with a 
more sane default value for this use-case (via the constructor).

> BTree$Builder / io.netty.util.Recycler$Stack leaking memory
> ---
>
> Key: CASSANDRA-13929
> URL: https://issues.apache.org/jira/browse/CASSANDRA-13929
> Project: Cassandra
>  Issue Type: Bug
>  Components: Core
>Reporter: Thomas Steinmaurer
>Assignee: Jay Zhuang
>Priority: Major
> Fix For: 3.11.x
>
> Attachments: cassandra_3.11.0_min_memory_utilization.jpg, 
> cassandra_3.11.1_NORECYCLE_memory_utilization.jpg, 
> cassandra_3.11.1_mat_dominator_classes.png, 
> cassandra_3.11.1_mat_dominator_classes_FIXED.png, 
> cassandra_3.11.1_snapshot_heaputilization.png, 
> cassandra_3.11.1_vs_3.11.2recyclernullingpatch.png, 
> dtest_example_80_request.png, dtest_example_80_request_fix.png, 
> dtest_example_heap.png, memleak_heapdump_recyclerstack.png
>
>
> Different to CASSANDRA-13754, there seems to be another memory leak in 
> 3.11.0+ in BTree$Builder / io.netty.util.Recycler$Stack.
> * heap utilization increase after upgrading to 3.11.0 => 
> cassandra_3.11.0_min_memory_utilization.jpg
> * No difference after upgrading to 3.11.1 (snapshot build) => 
> cassandra_3.11.1_snapshot_heaputilization.png; thus most likely after fixing 
> CASSANDRA-13754, more visible now
> * MAT shows io.netty.util.Recycler$Stack as top contributing class => 
> cassandra_3.11.1_mat_dominator_classes.png
> * With -Xmx8G (CMS) and our load pattern, we have to do a rolling restart 
> after ~ 72 hours
> Verified the following fix, namely explicitly unreferencing the 
> _recycleHandle_ member (making it non-final). In 
> _org.apache.cassandra.utils.btree.BTree.Builder.recycle()_
> {code}
> public void recycle()
> {
> if (recycleHandle != null)
> {
> this.cleanup();
> builderRecycler.recycle(this, recycleHandle);
> recycleHandle = null; // ADDED
> }
> }
> {code}
> Patched a single node in our loadtest cluster with this change and after ~ 10 
> hours uptime, no sign of the previously offending class in MAT anymore => 
> cassandra_3.11.1_mat_dominator_classes_FIXED.png
> Can' say if this has any other side effects etc., but I doubt.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org

[jira] [Commented] (CASSANDRA-14209) group by select queries query results differ when using select * vs select fields

[JIRA]

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

Andrés de la Peña commented on CASSANDRA-14209:
---

The patch with the thorough tests looks good to me, +1

> group by select queries query results differ when using select * vs select 
> fields
> -
>
> Key: CASSANDRA-14209
> URL: https://issues.apache.org/jira/browse/CASSANDRA-14209
> Project: Cassandra
>  Issue Type: Bug
>Reporter: Digant Modha
>Assignee: Benjamin Lerer
>Priority: Minor
> Attachments: Re group by select queries.txt
>
>
> {{I get two different out with these 2 queries.  The only difference between 
> the 2 queries is that one does ‘select *’ and other does ‘select specific 
> fields’ without any aggregate functions.}}
> {{I am using Apache Cassandra 3.10.}}
> {{Consistency level set to LOCAL_QUORUM.}}
> {{cassandra@cqlsh> select * from wp.position where account_id = 'user_1';}}
> {{ account_id | security_id | counter | avg_exec_price | pending_quantity | 
> quantity | transaction_id | update_time}}
> {{+-+-++--+--++-}}
> {{ user_1 | AMZN | 2 | 1239.2 | 0 | 1011 | null | 2018-01-25 
> 17:18:07.158000+}}
> {{ user_1 | AMZN | 1 | 1239.2 | 0 | 1010 | null | 2018-01-25 
> 17:18:07.158000+}}
> {{(2 rows)}}
> {{cassandra@cqlsh> select * from wp.position where account_id = 'user_1' 
> group by security_id;}}
> {{ account_id | security_id | counter | avg_exec_price | pending_quantity | 
> quantity | transaction_id | update_time}}
> {{+-+-++--+--++-}}
> {{ user_1 | AMZN | 1 | 1239.2 | 0 | 1010 | null | 2018-01-25 
> 17:18:07.158000+}}
> {{(1 rows)}}
> {{cassandra@cqlsh> select account_id,security_id, counter, 
> avg_exec_price,quantity, update_time from wp.position where account_id = 
> 'user_1' group by security_id ;}}
> {{ account_id | security_id | counter | avg_exec_price | quantity | 
> update_time}}
> {{+-+-++--+-}}
> {{ user_1 | AMZN | 2 | 1239.2 | 1011 | 2018-01-25 17:18:07.158000+}}
> {{(1 rows)}}
> {{Table Description:}}
> {{CREATE TABLE wp.position (}}
> {{ account_id text,}}
> {{ security_id text,}}
> {{ counter bigint,}}
> {{ avg_exec_price double,}}
> {{ pending_quantity double,}}
> {{ quantity double,}}
> {{ transaction_id uuid,}}
> {{ update_time timestamp,}}
> {{ PRIMARY KEY (account_id, security_id, counter)}}
> {{) WITH CLUSTERING ORDER BY (security_id ASC, counter DESC)}}{{ }}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org

[jira] [Comment Edited] (CASSANDRA-13929) BTree$Builder / io.netty.util.Recycler$Stack leaking memory

[Thomas Steinmaurer (JIRA)]

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

Thomas Steinmaurer edited comment on CASSANDRA-13929 at 2/14/18 1:07 PM:
-

[~norman], a concrete example for a *single* Recycler$Stack instance from our 
loadtest.
!memleak_heapdump_recyclerstack.png!

Looks like we have a lot of largish 32K object arrays, which seem to be empty 
as shallow heap = retained heap for this object arrays. So, a quick look on the 
patch of [~jay.zhuang], this might help. [~jjirsa], will re-patch a single node 
and report back after a considerable uptime.


was (Author: tsteinmaurer):
[~norman], a concrete example for a *single* Recycler$Stack instance from our 
loadtest.
!memleak_heapdump_recyclerstack.png|width=300!

Looks like we have a lot of largish 32K object arrays, which seem to be empty 
as shallow heap = retained heap for this object arrays. So, a quick look on the 
patch of [~jay.zhuang], this might help. [~jjirsa], will re-patch a single node 
and report back after a considerable uptime.

> BTree$Builder / io.netty.util.Recycler$Stack leaking memory
> ---
>
> Key: CASSANDRA-13929
> URL: https://issues.apache.org/jira/browse/CASSANDRA-13929
> Project: Cassandra
>  Issue Type: Bug
>  Components: Core
>Reporter: Thomas Steinmaurer
>Assignee: Jay Zhuang
>Priority: Major
> Fix For: 3.11.x
>
> Attachments: cassandra_3.11.0_min_memory_utilization.jpg, 
> cassandra_3.11.1_NORECYCLE_memory_utilization.jpg, 
> cassandra_3.11.1_mat_dominator_classes.png, 
> cassandra_3.11.1_mat_dominator_classes_FIXED.png, 
> cassandra_3.11.1_snapshot_heaputilization.png, 
> cassandra_3.11.1_vs_3.11.2recyclernullingpatch.png, 
> dtest_example_80_request.png, dtest_example_80_request_fix.png, 
> dtest_example_heap.png, memleak_heapdump_recyclerstack.png
>
>
> Different to CASSANDRA-13754, there seems to be another memory leak in 
> 3.11.0+ in BTree$Builder / io.netty.util.Recycler$Stack.
> * heap utilization increase after upgrading to 3.11.0 => 
> cassandra_3.11.0_min_memory_utilization.jpg
> * No difference after upgrading to 3.11.1 (snapshot build) => 
> cassandra_3.11.1_snapshot_heaputilization.png; thus most likely after fixing 
> CASSANDRA-13754, more visible now
> * MAT shows io.netty.util.Recycler$Stack as top contributing class => 
> cassandra_3.11.1_mat_dominator_classes.png
> * With -Xmx8G (CMS) and our load pattern, we have to do a rolling restart 
> after ~ 72 hours
> Verified the following fix, namely explicitly unreferencing the 
> _recycleHandle_ member (making it non-final). In 
> _org.apache.cassandra.utils.btree.BTree.Builder.recycle()_
> {code}
> public void recycle()
> {
> if (recycleHandle != null)
> {
> this.cleanup();
> builderRecycler.recycle(this, recycleHandle);
> recycleHandle = null; // ADDED
> }
> }
> {code}
> Patched a single node in our loadtest cluster with this change and after ~ 10 
> hours uptime, no sign of the previously offending class in MAT anymore => 
> cassandra_3.11.1_mat_dominator_classes_FIXED.png
> Can' say if this has any other side effects etc., but I doubt.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org

[jira] [Updated] (CASSANDRA-14233) nodetool tablestats/cfstats output has inconsistent formatting for latency

[Jason Brown (JIRA)]

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

Jason Brown updated CASSANDRA-14233:

   Resolution: Fixed
Fix Version/s: 4.0
   3.11.2
   Status: Resolved  (was: Awaiting Feedback)

+1. committed as sha {{d10e6ac606c6b484c75bb850de7a754b75ad5eca}}.

Thanks for the patch!

> nodetool tablestats/cfstats output has inconsistent formatting for latency
> --
>
> Key: CASSANDRA-14233
> URL: https://issues.apache.org/jira/browse/CASSANDRA-14233
> Project: Cassandra
>  Issue Type: Bug
>Reporter: Samuel Roberts
>Assignee: Samuel Roberts
>Priority: Trivial
> Fix For: 3.11.2, 4.0
>
>   Original Estimate: 10m
>  Remaining Estimate: 10m
>
> Latencies are reported at keyspace level with `ms.` and at table level with 
> `ms`.
> There should be no trailing `.` as it is not a sentence and `.` is not part 
> of the abbreviation.
> This is also present in 2.x with `nodetool cfstats`.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org

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

[jasobrown]

Merge branch 'cassandra-3.11' into trunk


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

Branch: refs/heads/trunk
Commit: 74b2013ea264d64e49c4bd52bd265fbcad8942fa
Parents: bb9aa09 d10e6ac
Author: Jason Brown 
Authored: Wed Feb 14 05:01:03 2018 -0800
Committer: Jason Brown 
Committed: Wed Feb 14 05:02:15 2018 -0800

--
 CHANGES.txt  | 1 +
 .../apache/cassandra/tools/nodetool/stats/TableStatsPrinter.java | 4 ++--
 2 files changed, 3 insertions(+), 2 deletions(-)
--


http://git-wip-us.apache.org/repos/asf/cassandra/blob/74b2013e/CHANGES.txt
--
diff --cc CHANGES.txt
index d69c631,31cee26..f5036df
--- a/CHANGES.txt
+++ b/CHANGES.txt
@@@ -1,205 -1,17 +1,206 @@@
 +4.0
 + * Use JVM default SSL validation algorithm instead of custom default 
(CASSANDRA-13259)
 + * Better document in code InetAddressAndPort usage post 7544, incorporate 
port into UUIDGen node (CASSANDRA-14226)
 + * Fix sstablemetadata date string for minLocalDeletionTime (CASSANDRA-14132)
 + * Make it possible to change neverPurgeTombstones during runtime 
(CASSANDRA-14214)
 + * Remove GossipDigestSynVerbHandler#doSort() (CASSANDRA-14174)
 + * Add nodetool clientlist (CASSANDRA-13665)
 + * Revert ProtocolVersion changes from CASSANDRA-7544 (CASSANDRA-14211)
 + * Non-disruptive seed node list reload (CASSANDRA-14190)
 + * Nodetool tablehistograms to print statics for all the tables 
(CASSANDRA-14185)
 + * Migrate dtests to use pytest and python3 (CASSANDRA-14134)
 + * Allow storage port to be configurable per node (CASSANDRA-7544)
 + * Make sub-range selection for non-frozen collections return null instead of 
empty (CASSANDRA-14182)
 + * BloomFilter serialization format should not change byte ordering 
(CASSANDRA-9067)
 + * Remove unused on-heap BloomFilter implementation (CASSANDRA-14152)
 + * Delete temp test files on exit (CASSANDRA-14153)
 + * Make PartitionUpdate and Mutation immutable (CASSANDRA-13867)
 + * Fix CommitLogReplayer exception for CDC data (CASSANDRA-14066)
 + * Fix cassandra-stress startup failure (CASSANDRA-14106)
 + * Remove initialDirectories from CFS (CASSANDRA-13928)
 + * Fix trivial log format error (CASSANDRA-14015)
 + * Allow sstabledump to do a json object per partition (CASSANDRA-13848)
 + * Add option to optimise merkle tree comparison across replicas 
(CASSANDRA-3200)
 + * Remove unused and deprecated methods from AbstractCompactionStrategy 
(CASSANDRA-14081)
 + * Fix Distribution.average in cassandra-stress (CASSANDRA-14090)
 + * Support a means of logging all queries as they were invoked 
(CASSANDRA-13983)
 + * Presize collections (CASSANDRA-13760)
 + * Add GroupCommitLogService (CASSANDRA-13530)
 + * Parallelize initial materialized view build (CASSANDRA-12245)
 + * Fix flaky SecondaryIndexManagerTest.assert[Not]MarkedAsBuilt 
(CASSANDRA-13965)
 + * Make LWTs send resultset metadata on every request (CASSANDRA-13992)
 + * Fix flaky indexWithFailedInitializationIsNotQueryableAfterPartialRebuild 
(CASSANDRA-13963)
 + * Introduce leaf-only iterator (CASSANDRA-9988)
 + * Upgrade Guava to 23.3 and Airline to 0.8 (CASSANDRA-13997)
 + * Allow only one concurrent call to StatusLogger (CASSANDRA-12182)
 + * Refactoring to specialised functional interfaces (CASSANDRA-13982)
 + * Speculative retry should allow more friendly params (CASSANDRA-13876)
 + * Throw exception if we send/receive repair messages to incompatible nodes 
(CASSANDRA-13944)
 + * Replace usages of MessageDigest with Guava's Hasher (CASSANDRA-13291)
 + * Add nodetool cmd to print hinted handoff window (CASSANDRA-13728)
 + * Fix some alerts raised by static analysis (CASSANDRA-13799)
 + * Checksum sstable metadata (CASSANDRA-13321, CASSANDRA-13593)
 + * Add result set metadata to prepared statement MD5 hash calculation 
(CASSANDRA-10786)
 + * Refactor GcCompactionTest to avoid boxing (CASSANDRA-13941)
 + * Expose recent histograms in JmxHistograms (CASSANDRA-13642)
 + * Fix buffer length comparison when decompressing in netty-based streaming 
(CASSANDRA-13899)
 + * Properly close StreamCompressionInputStream to release any ByteBuf 
(CASSANDRA-13906)
 + * Add SERIAL and LOCAL_SERIAL support for cassandra-stress (CASSANDRA-13925)
 + * LCS needlessly checks for L0 STCS candidates multiple times 
(CASSANDRA-12961)
 + * Correctly close netty channels when a stream session ends (CASSANDRA-13905)
 + * Update lz4 to 1.4.0 (CASSANDRA-13741)
 + * Optimize Paxos prepare and propose stage for local requests 
(CASSANDRA-13862)
 + * Throttle base 

[1/3] cassandra git commit: Remove trailing period from latency reports at keyspace level

[jasobrown]

Repository: cassandra
Updated Branches:
  refs/heads/cassandra-3.11 30c35dd8a -> d10e6ac60
  refs/heads/trunk bb9aa0988 -> 74b2013ea


Remove trailing period from latency reports at keyspace level

patch by Samuel Roberts; reviewed by Chris Lohfink for CASSANDRA-14233


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

Branch: refs/heads/cassandra-3.11
Commit: d10e6ac606c6b484c75bb850de7a754b75ad5eca
Parents: 30c35dd
Author: Samuel Roberts 
Authored: Wed Feb 14 07:44:50 2018 +0100
Committer: Jason Brown 
Committed: Wed Feb 14 04:59:45 2018 -0800

--
 CHANGES.txt  | 1 +
 .../apache/cassandra/tools/nodetool/stats/TableStatsPrinter.java | 4 ++--
 2 files changed, 3 insertions(+), 2 deletions(-)
--


http://git-wip-us.apache.org/repos/asf/cassandra/blob/d10e6ac6/CHANGES.txt
--
diff --git a/CHANGES.txt b/CHANGES.txt
index ba72406..31cee26 100644
--- a/CHANGES.txt
+++ b/CHANGES.txt
@@ -1,4 +1,5 @@
 3.11.2
+ * Remove trailing period from latency reports at keyspace level 
(CASSANDRA-14233)
  * Backport CASSANDRA-13080: Use new token allocation for non bootstrap case 
as well (CASSANDRA-14212)
  * Remove dependencies on JVM internal classes from JMXServerUtils 
(CASSANDRA-14173) 
  * Add DEFAULT, UNSET, MBEAN and MBEANS to `ReservedKeywords` (CASSANDRA-14205)

http://git-wip-us.apache.org/repos/asf/cassandra/blob/d10e6ac6/src/java/org/apache/cassandra/tools/nodetool/stats/TableStatsPrinter.java
--
diff --git 
a/src/java/org/apache/cassandra/tools/nodetool/stats/TableStatsPrinter.java 
b/src/java/org/apache/cassandra/tools/nodetool/stats/TableStatsPrinter.java
index 7c76e44..9f7ecd0 100644
--- a/src/java/org/apache/cassandra/tools/nodetool/stats/TableStatsPrinter.java
+++ b/src/java/org/apache/cassandra/tools/nodetool/stats/TableStatsPrinter.java
@@ -50,9 +50,9 @@ public class TableStatsPrinter
 // print each keyspace's information
 out.println("Keyspace : " + keyspace.name);
 out.println("\tRead Count: " + keyspace.readCount);
-out.println("\tRead Latency: " + keyspace.readLatency() + " 
ms.");
+out.println("\tRead Latency: " + keyspace.readLatency() + " 
ms");
 out.println("\tWrite Count: " + keyspace.writeCount);
-out.println("\tWrite Latency: " + keyspace.writeLatency() + " 
ms.");
+out.println("\tWrite Latency: " + keyspace.writeLatency() + " 
ms");
 out.println("\tPending Flushes: " + keyspace.pendingFlushes);
 
 // print each table's information


-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org

[2/3] cassandra git commit: Remove trailing period from latency reports at keyspace level

[jasobrown]

Remove trailing period from latency reports at keyspace level

patch by Samuel Roberts; reviewed by Chris Lohfink for CASSANDRA-14233


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

Branch: refs/heads/trunk
Commit: d10e6ac606c6b484c75bb850de7a754b75ad5eca
Parents: 30c35dd
Author: Samuel Roberts 
Authored: Wed Feb 14 07:44:50 2018 +0100
Committer: Jason Brown 
Committed: Wed Feb 14 04:59:45 2018 -0800

--
 CHANGES.txt  | 1 +
 .../apache/cassandra/tools/nodetool/stats/TableStatsPrinter.java | 4 ++--
 2 files changed, 3 insertions(+), 2 deletions(-)
--


http://git-wip-us.apache.org/repos/asf/cassandra/blob/d10e6ac6/CHANGES.txt
--
diff --git a/CHANGES.txt b/CHANGES.txt
index ba72406..31cee26 100644
--- a/CHANGES.txt
+++ b/CHANGES.txt
@@ -1,4 +1,5 @@
 3.11.2
+ * Remove trailing period from latency reports at keyspace level 
(CASSANDRA-14233)
  * Backport CASSANDRA-13080: Use new token allocation for non bootstrap case 
as well (CASSANDRA-14212)
  * Remove dependencies on JVM internal classes from JMXServerUtils 
(CASSANDRA-14173) 
  * Add DEFAULT, UNSET, MBEAN and MBEANS to `ReservedKeywords` (CASSANDRA-14205)

http://git-wip-us.apache.org/repos/asf/cassandra/blob/d10e6ac6/src/java/org/apache/cassandra/tools/nodetool/stats/TableStatsPrinter.java
--
diff --git 
a/src/java/org/apache/cassandra/tools/nodetool/stats/TableStatsPrinter.java 
b/src/java/org/apache/cassandra/tools/nodetool/stats/TableStatsPrinter.java
index 7c76e44..9f7ecd0 100644
--- a/src/java/org/apache/cassandra/tools/nodetool/stats/TableStatsPrinter.java
+++ b/src/java/org/apache/cassandra/tools/nodetool/stats/TableStatsPrinter.java
@@ -50,9 +50,9 @@ public class TableStatsPrinter
 // print each keyspace's information
 out.println("Keyspace : " + keyspace.name);
 out.println("\tRead Count: " + keyspace.readCount);
-out.println("\tRead Latency: " + keyspace.readLatency() + " 
ms.");
+out.println("\tRead Latency: " + keyspace.readLatency() + " 
ms");
 out.println("\tWrite Count: " + keyspace.writeCount);
-out.println("\tWrite Latency: " + keyspace.writeLatency() + " 
ms.");
+out.println("\tWrite Latency: " + keyspace.writeLatency() + " 
ms");
 out.println("\tPending Flushes: " + keyspace.pendingFlushes);
 
 // print each table's information


-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org

[jira] [Resolved] (CASSANDRA-14193) Two TTLTest failures caused by CASSANDRA-14071

[ZhaoYang (JIRA)]

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

ZhaoYang resolved CASSANDRA-14193.
--
Resolution: Duplicate

Marked as duplicate of CASSANDRA-14092

> Two TTLTest failures caused by CASSANDRA-14071
> --
>
> Key: CASSANDRA-14193
> URL: https://issues.apache.org/jira/browse/CASSANDRA-14193
> Project: Cassandra
>  Issue Type: Bug
>  Components: Core, Testing
>Reporter: Ariel Weisberg
>Assignee: ZhaoYang
>Priority: Major
> Attachments: 0001-fix-ttl-test.patch
>
>
> This is reproducible by running "ant test -Dtest.name=TTLTest" on a MacOS 
> laptop.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org

[jira] [Comment Edited] (CASSANDRA-13929) BTree$Builder / io.netty.util.Recycler$Stack leaking memory

[Thomas Steinmaurer (JIRA)]

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

Thomas Steinmaurer edited comment on CASSANDRA-13929 at 2/14/18 12:51 PM:
--

[~norman], a concrete example for a *single* Recycler$Stack instance from our 
loadtest.
!memleak_heapdump_recyclerstack.png|width=300!

Looks like we have a lot of largish 32K object arrays, which seem to be empty 
as shallow heap = retained heap for this object arrays. So, a quick look on the 
patch of [~jay.zhuang], this might help. [~jjirsa], will re-patch a single node 
and report back after a considerable uptime.


was (Author: tsteinmaurer):
[~norman], a concrete example for a single Recycler$Stack instance:
!memleak_heapdump_recyclerstack.png|width=300!

Looks like we have a lot of largish 32K object arrays, which seem to be empty 
as shallow heap = retained heap for this object arrays. So, a quick look on the 
patch of [~jay.zhuang], this might help. [~jjirsa], will re-patch a single node 
and report back after a considerable uptime.

> BTree$Builder / io.netty.util.Recycler$Stack leaking memory
> ---
>
> Key: CASSANDRA-13929
> URL: https://issues.apache.org/jira/browse/CASSANDRA-13929
> Project: Cassandra
>  Issue Type: Bug
>  Components: Core
>Reporter: Thomas Steinmaurer
>Assignee: Jay Zhuang
>Priority: Major
> Fix For: 3.11.x
>
> Attachments: cassandra_3.11.0_min_memory_utilization.jpg, 
> cassandra_3.11.1_NORECYCLE_memory_utilization.jpg, 
> cassandra_3.11.1_mat_dominator_classes.png, 
> cassandra_3.11.1_mat_dominator_classes_FIXED.png, 
> cassandra_3.11.1_snapshot_heaputilization.png, 
> cassandra_3.11.1_vs_3.11.2recyclernullingpatch.png, 
> dtest_example_80_request.png, dtest_example_80_request_fix.png, 
> dtest_example_heap.png, memleak_heapdump_recyclerstack.png
>
>
> Different to CASSANDRA-13754, there seems to be another memory leak in 
> 3.11.0+ in BTree$Builder / io.netty.util.Recycler$Stack.
> * heap utilization increase after upgrading to 3.11.0 => 
> cassandra_3.11.0_min_memory_utilization.jpg
> * No difference after upgrading to 3.11.1 (snapshot build) => 
> cassandra_3.11.1_snapshot_heaputilization.png; thus most likely after fixing 
> CASSANDRA-13754, more visible now
> * MAT shows io.netty.util.Recycler$Stack as top contributing class => 
> cassandra_3.11.1_mat_dominator_classes.png
> * With -Xmx8G (CMS) and our load pattern, we have to do a rolling restart 
> after ~ 72 hours
> Verified the following fix, namely explicitly unreferencing the 
> _recycleHandle_ member (making it non-final). In 
> _org.apache.cassandra.utils.btree.BTree.Builder.recycle()_
> {code}
> public void recycle()
> {
> if (recycleHandle != null)
> {
> this.cleanup();
> builderRecycler.recycle(this, recycleHandle);
> recycleHandle = null; // ADDED
> }
> }
> {code}
> Patched a single node in our loadtest cluster with this change and after ~ 10 
> hours uptime, no sign of the previously offending class in MAT anymore => 
> cassandra_3.11.1_mat_dominator_classes_FIXED.png
> Can' say if this has any other side effects etc., but I doubt.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org

[jira] [Commented] (CASSANDRA-13929) BTree$Builder / io.netty.util.Recycler$Stack leaking memory

[Thomas Steinmaurer (JIRA)]

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

Thomas Steinmaurer commented on CASSANDRA-13929:


[~norman], a concrete example for a single Recycler$Stack instance:
!memleak_heapdump_recyclerstack.png|width=300!

Looks like we have a lot of largish 32K object arrays, which seem to be empty 
as shallow heap = retained heap for this object arrays. So, a quick look on the 
patch of [~jay.zhuang], this might help. [~jjirsa], will re-patch a single node 
and report back after a considerable uptime.

> BTree$Builder / io.netty.util.Recycler$Stack leaking memory
> ---
>
> Key: CASSANDRA-13929
> URL: https://issues.apache.org/jira/browse/CASSANDRA-13929
> Project: Cassandra
>  Issue Type: Bug
>  Components: Core
>Reporter: Thomas Steinmaurer
>Assignee: Jay Zhuang
>Priority: Major
> Fix For: 3.11.x
>
> Attachments: cassandra_3.11.0_min_memory_utilization.jpg, 
> cassandra_3.11.1_NORECYCLE_memory_utilization.jpg, 
> cassandra_3.11.1_mat_dominator_classes.png, 
> cassandra_3.11.1_mat_dominator_classes_FIXED.png, 
> cassandra_3.11.1_snapshot_heaputilization.png, 
> cassandra_3.11.1_vs_3.11.2recyclernullingpatch.png, 
> dtest_example_80_request.png, dtest_example_80_request_fix.png, 
> dtest_example_heap.png, memleak_heapdump_recyclerstack.png
>
>
> Different to CASSANDRA-13754, there seems to be another memory leak in 
> 3.11.0+ in BTree$Builder / io.netty.util.Recycler$Stack.
> * heap utilization increase after upgrading to 3.11.0 => 
> cassandra_3.11.0_min_memory_utilization.jpg
> * No difference after upgrading to 3.11.1 (snapshot build) => 
> cassandra_3.11.1_snapshot_heaputilization.png; thus most likely after fixing 
> CASSANDRA-13754, more visible now
> * MAT shows io.netty.util.Recycler$Stack as top contributing class => 
> cassandra_3.11.1_mat_dominator_classes.png
> * With -Xmx8G (CMS) and our load pattern, we have to do a rolling restart 
> after ~ 72 hours
> Verified the following fix, namely explicitly unreferencing the 
> _recycleHandle_ member (making it non-final). In 
> _org.apache.cassandra.utils.btree.BTree.Builder.recycle()_
> {code}
> public void recycle()
> {
> if (recycleHandle != null)
> {
> this.cleanup();
> builderRecycler.recycle(this, recycleHandle);
> recycleHandle = null; // ADDED
> }
> }
> {code}
> Patched a single node in our loadtest cluster with this change and after ~ 10 
> hours uptime, no sign of the previously offending class in MAT anymore => 
> cassandra_3.11.1_mat_dominator_classes_FIXED.png
> Can' say if this has any other side effects etc., but I doubt.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org

[jira] [Updated] (CASSANDRA-13929) BTree$Builder / io.netty.util.Recycler$Stack leaking memory

[Thomas Steinmaurer (JIRA)]

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

Thomas Steinmaurer updated CASSANDRA-13929:
---
Attachment: memleak_heapdump_recyclerstack.png

> BTree$Builder / io.netty.util.Recycler$Stack leaking memory
> ---
>
> Key: CASSANDRA-13929
> URL: https://issues.apache.org/jira/browse/CASSANDRA-13929
> Project: Cassandra
>  Issue Type: Bug
>  Components: Core
>Reporter: Thomas Steinmaurer
>Assignee: Jay Zhuang
>Priority: Major
> Fix For: 3.11.x
>
> Attachments: cassandra_3.11.0_min_memory_utilization.jpg, 
> cassandra_3.11.1_NORECYCLE_memory_utilization.jpg, 
> cassandra_3.11.1_mat_dominator_classes.png, 
> cassandra_3.11.1_mat_dominator_classes_FIXED.png, 
> cassandra_3.11.1_snapshot_heaputilization.png, 
> cassandra_3.11.1_vs_3.11.2recyclernullingpatch.png, 
> dtest_example_80_request.png, dtest_example_80_request_fix.png, 
> dtest_example_heap.png, memleak_heapdump_recyclerstack.png
>
>
> Different to CASSANDRA-13754, there seems to be another memory leak in 
> 3.11.0+ in BTree$Builder / io.netty.util.Recycler$Stack.
> * heap utilization increase after upgrading to 3.11.0 => 
> cassandra_3.11.0_min_memory_utilization.jpg
> * No difference after upgrading to 3.11.1 (snapshot build) => 
> cassandra_3.11.1_snapshot_heaputilization.png; thus most likely after fixing 
> CASSANDRA-13754, more visible now
> * MAT shows io.netty.util.Recycler$Stack as top contributing class => 
> cassandra_3.11.1_mat_dominator_classes.png
> * With -Xmx8G (CMS) and our load pattern, we have to do a rolling restart 
> after ~ 72 hours
> Verified the following fix, namely explicitly unreferencing the 
> _recycleHandle_ member (making it non-final). In 
> _org.apache.cassandra.utils.btree.BTree.Builder.recycle()_
> {code}
> public void recycle()
> {
> if (recycleHandle != null)
> {
> this.cleanup();
> builderRecycler.recycle(this, recycleHandle);
> recycleHandle = null; // ADDED
> }
> }
> {code}
> Patched a single node in our loadtest cluster with this change and after ~ 10 
> hours uptime, no sign of the previously offending class in MAT anymore => 
> cassandra_3.11.1_mat_dominator_classes_FIXED.png
> Can' say if this has any other side effects etc., but I doubt.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org

[jira] [Updated] (CASSANDRA-14209) group by select queries query results differ when using select * vs select fields

[JIRA]

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

Andrés de la Peña updated CASSANDRA-14209:
--
Reviewer: Andrés de la Peña

> group by select queries query results differ when using select * vs select 
> fields
> -
>
> Key: CASSANDRA-14209
> URL: https://issues.apache.org/jira/browse/CASSANDRA-14209
> Project: Cassandra
>  Issue Type: Bug
>Reporter: Digant Modha
>Assignee: Benjamin Lerer
>Priority: Minor
> Attachments: Re group by select queries.txt
>
>
> {{I get two different out with these 2 queries.  The only difference between 
> the 2 queries is that one does ‘select *’ and other does ‘select specific 
> fields’ without any aggregate functions.}}
> {{I am using Apache Cassandra 3.10.}}
> {{Consistency level set to LOCAL_QUORUM.}}
> {{cassandra@cqlsh> select * from wp.position where account_id = 'user_1';}}
> {{ account_id | security_id | counter | avg_exec_price | pending_quantity | 
> quantity | transaction_id | update_time}}
> {{+-+-++--+--++-}}
> {{ user_1 | AMZN | 2 | 1239.2 | 0 | 1011 | null | 2018-01-25 
> 17:18:07.158000+}}
> {{ user_1 | AMZN | 1 | 1239.2 | 0 | 1010 | null | 2018-01-25 
> 17:18:07.158000+}}
> {{(2 rows)}}
> {{cassandra@cqlsh> select * from wp.position where account_id = 'user_1' 
> group by security_id;}}
> {{ account_id | security_id | counter | avg_exec_price | pending_quantity | 
> quantity | transaction_id | update_time}}
> {{+-+-++--+--++-}}
> {{ user_1 | AMZN | 1 | 1239.2 | 0 | 1010 | null | 2018-01-25 
> 17:18:07.158000+}}
> {{(1 rows)}}
> {{cassandra@cqlsh> select account_id,security_id, counter, 
> avg_exec_price,quantity, update_time from wp.position where account_id = 
> 'user_1' group by security_id ;}}
> {{ account_id | security_id | counter | avg_exec_price | quantity | 
> update_time}}
> {{+-+-++--+-}}
> {{ user_1 | AMZN | 2 | 1239.2 | 1011 | 2018-01-25 17:18:07.158000+}}
> {{(1 rows)}}
> {{Table Description:}}
> {{CREATE TABLE wp.position (}}
> {{ account_id text,}}
> {{ security_id text,}}
> {{ counter bigint,}}
> {{ avg_exec_price double,}}
> {{ pending_quantity double,}}
> {{ quantity double,}}
> {{ transaction_id uuid,}}
> {{ update_time timestamp,}}
> {{ PRIMARY KEY (account_id, security_id, counter)}}
> {{) WITH CLUSTERING ORDER BY (security_id ASC, counter DESC)}}{{ }}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org

[jira] [Updated] (CASSANDRA-13259) Use platform specific X.509 default algorithm

[Stefan Podkowinski (JIRA)]

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

Stefan Podkowinski updated CASSANDRA-13259:
---
   Resolution: Fixed
Fix Version/s: (was: 4.x)
   4.0
   Status: Resolved  (was: Ready to Commit)

Merged as bb9aa098813b7f047f450086e18a78b149bb5349 on trunk

> Use platform specific X.509 default algorithm
> -
>
> Key: CASSANDRA-13259
> URL: https://issues.apache.org/jira/browse/CASSANDRA-13259
> Project: Cassandra
>  Issue Type: Improvement
>  Components: Configuration
>Reporter: Stefan Podkowinski
>Assignee: Stefan Podkowinski
>Priority: Minor
> Fix For: 4.0
>
>
> We should replace the hardcoded "SunX509" default algorithm and use the JRE 
> default instead. This implementation will currently not work on less popular 
> platforms (e.g. IBM) and won't get any further updates.
> See also:
> https://bugs.openjdk.java.net/browse/JDK-8169745



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org

cassandra git commit: Use JRE default key store algorithm instead of SunX509

[spod]

Repository: cassandra
Updated Branches:
  refs/heads/trunk 0bc2164df -> bb9aa0988


Use JRE default key store algorithm instead of SunX509

patch by Stefan Podkowinski; reviewed by Jason Brown for CASSANRA-13259


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

Branch: refs/heads/trunk
Commit: bb9aa098813b7f047f450086e18a78b149bb5349
Parents: 0bc2164
Author: Stefan Podkowinski 
Authored: Thu Feb 23 13:17:39 2017 +0100
Committer: Stefan Podkowinski 
Committed: Wed Feb 14 11:29:59 2018 +0100

--
 CHANGES.txt| 1 +
 conf/cassandra.yaml| 2 --
 src/java/org/apache/cassandra/config/EncryptionOptions.java| 2 +-
 src/java/org/apache/cassandra/security/SSLFactory.java | 6 --
 src/java/org/apache/cassandra/tools/LoaderOptions.java | 2 +-
 .../src/org/apache/cassandra/stress/settings/Legacy.java   | 2 +-
 .../apache/cassandra/stress/settings/SettingsTransport.java| 2 +-
 7 files changed, 9 insertions(+), 8 deletions(-)
--


http://git-wip-us.apache.org/repos/asf/cassandra/blob/bb9aa098/CHANGES.txt
--
diff --git a/CHANGES.txt b/CHANGES.txt
index 54b587d..d69c631 100644
--- a/CHANGES.txt
+++ b/CHANGES.txt
@@ -1,4 +1,5 @@
 4.0
+ * Use JVM default SSL validation algorithm instead of custom default 
(CASSANDRA-13259)
  * Better document in code InetAddressAndPort usage post 7544, incorporate 
port into UUIDGen node (CASSANDRA-14226)
  * Fix sstablemetadata date string for minLocalDeletionTime (CASSANDRA-14132)
  * Make it possible to change neverPurgeTombstones during runtime 
(CASSANDRA-14214)

http://git-wip-us.apache.org/repos/asf/cassandra/blob/bb9aa098/conf/cassandra.yaml
--
diff --git a/conf/cassandra.yaml b/conf/cassandra.yaml
index 9acc6d6..0a954b4 100644
--- a/conf/cassandra.yaml
+++ b/conf/cassandra.yaml
@@ -961,7 +961,6 @@ server_encryption_options:
 truststore_password: cassandra
 # More advanced defaults below:
 # protocol: TLS
-# algorithm: SunX509
 # store_type: JKS
 # cipher_suites: 
[TLS_RSA_WITH_AES_128_CBC_SHA,TLS_RSA_WITH_AES_256_CBC_SHA,TLS_DHE_RSA_WITH_AES_128_CBC_SHA,TLS_DHE_RSA_WITH_AES_256_CBC_SHA,TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA,TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA]
 # require_client_auth: false
@@ -980,7 +979,6 @@ client_encryption_options:
 # truststore_password: cassandra
 # More advanced defaults below:
 # protocol: TLS
-# algorithm: SunX509
 # store_type: JKS
 # cipher_suites: 
[TLS_RSA_WITH_AES_128_CBC_SHA,TLS_RSA_WITH_AES_256_CBC_SHA,TLS_DHE_RSA_WITH_AES_128_CBC_SHA,TLS_DHE_RSA_WITH_AES_256_CBC_SHA,TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA,TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA]
 

http://git-wip-us.apache.org/repos/asf/cassandra/blob/bb9aa098/src/java/org/apache/cassandra/config/EncryptionOptions.java
--
diff --git a/src/java/org/apache/cassandra/config/EncryptionOptions.java 
b/src/java/org/apache/cassandra/config/EncryptionOptions.java
index aecbfca..5260dff 100644
--- a/src/java/org/apache/cassandra/config/EncryptionOptions.java
+++ b/src/java/org/apache/cassandra/config/EncryptionOptions.java
@@ -25,7 +25,7 @@ public class EncryptionOptions
 public String truststore_password = "cassandra";
 public String[] cipher_suites = {};
 public String protocol = "TLS";
-public String algorithm = "SunX509";
+public String algorithm = null;
 public String store_type = "JKS";
 public boolean require_client_auth = false;
 public boolean require_endpoint_verification = false;

http://git-wip-us.apache.org/repos/asf/cassandra/blob/bb9aa098/src/java/org/apache/cassandra/security/SSLFactory.java
--
diff --git a/src/java/org/apache/cassandra/security/SSLFactory.java 
b/src/java/org/apache/cassandra/security/SSLFactory.java
index 0bf769c..395ea42 100644
--- a/src/java/org/apache/cassandra/security/SSLFactory.java
+++ b/src/java/org/apache/cassandra/security/SSLFactory.java
@@ -171,7 +171,8 @@ public final class SSLFactory
 {
 try (InputStream tsf = 
Files.newInputStream(Paths.get(options.truststore)))
 {
-TrustManagerFactory tmf = 
TrustManagerFactory.getInstance(options.algorithm);
+TrustManagerFactory tmf = TrustManagerFactory.getInstance(
+options.algorithm == null ? 

[jira] [Commented] (CASSANDRA-14165) execute_prepared_cql3_query with LIKE not working

[Benjamin Lerer (JIRA)]

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

Benjamin Lerer commented on CASSANDRA-14165:


I am not really able to reproduce the problem. Could you provide your table an 
index schema?

> execute_prepared_cql3_query with LIKE not working
> -
>
> Key: CASSANDRA-14165
> URL: https://issues.apache.org/jira/browse/CASSANDRA-14165
> Project: Cassandra
>  Issue Type: Bug
>Reporter: Alexandr Gorbachev
>Assignee: Benjamin Lerer
>Priority: Major
>
> Hello ,
> I have faced up with following issue.
>  Seems like LIKE is not supported by 'execute_prepared_cql3_query'.
>  Is it by desing or somehow it is possible to find a workaroud or to fix this 
> issue?
> More details. Query looks like :
>  SELECT * FROM tabke WHERE a= ? AND b = ? AND c IN (?,?,?,?,?,?,?) AND column 
> LIKE ? ALLOW FILTERING;
>  Is not working.
> If I send directly query in prepare statement.
>  So actully wihout passing parameters in preare statement, just like plain 
> query, then this is working:
>  SELECT * FROM tabke WHERE a= '1' AND b = '2' AND c IN ('3','4') AND column 
> LIKE '%A%' ALLOW FILTERING;
> Could you please suggest also where it is possible to find 
> description/definition of 'execute_prepared_cql3_query'.
>  
> Thank you for help.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org

[jira] [Commented] (CASSANDRA-14209) group by select queries query results differ when using select * vs select fields

[Benjamin Lerer (JIRA)]

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

Benjamin Lerer commented on CASSANDRA-14209:


The problem is that the {{Selection}} used for building the result set is not 
the good one for wildcard queries with {{GROUP BY}}.  

I pushed some patches for 
[3.11|https://github.com/apache/cassandra/compare/cassandra-3.11...blerer:14209-3.11]
 and 
[trunk|https://github.com/apache/cassandra/compare/trunk...blerer:14209-trunk] 
to fix that problem and add some testing for it.

[~adelapena] Could you review?

> group by select queries query results differ when using select * vs select 
> fields
> -
>
> Key: CASSANDRA-14209
> URL: https://issues.apache.org/jira/browse/CASSANDRA-14209
> Project: Cassandra
>  Issue Type: Bug
>Reporter: Digant Modha
>Assignee: Benjamin Lerer
>Priority: Minor
> Attachments: Re group by select queries.txt
>
>
> {{I get two different out with these 2 queries.  The only difference between 
> the 2 queries is that one does ‘select *’ and other does ‘select specific 
> fields’ without any aggregate functions.}}
> {{I am using Apache Cassandra 3.10.}}
> {{Consistency level set to LOCAL_QUORUM.}}
> {{cassandra@cqlsh> select * from wp.position where account_id = 'user_1';}}
> {{ account_id | security_id | counter | avg_exec_price | pending_quantity | 
> quantity | transaction_id | update_time}}
> {{+-+-++--+--++-}}
> {{ user_1 | AMZN | 2 | 1239.2 | 0 | 1011 | null | 2018-01-25 
> 17:18:07.158000+}}
> {{ user_1 | AMZN | 1 | 1239.2 | 0 | 1010 | null | 2018-01-25 
> 17:18:07.158000+}}
> {{(2 rows)}}
> {{cassandra@cqlsh> select * from wp.position where account_id = 'user_1' 
> group by security_id;}}
> {{ account_id | security_id | counter | avg_exec_price | pending_quantity | 
> quantity | transaction_id | update_time}}
> {{+-+-++--+--++-}}
> {{ user_1 | AMZN | 1 | 1239.2 | 0 | 1010 | null | 2018-01-25 
> 17:18:07.158000+}}
> {{(1 rows)}}
> {{cassandra@cqlsh> select account_id,security_id, counter, 
> avg_exec_price,quantity, update_time from wp.position where account_id = 
> 'user_1' group by security_id ;}}
> {{ account_id | security_id | counter | avg_exec_price | quantity | 
> update_time}}
> {{+-+-++--+-}}
> {{ user_1 | AMZN | 2 | 1239.2 | 1011 | 2018-01-25 17:18:07.158000+}}
> {{(1 rows)}}
> {{Table Description:}}
> {{CREATE TABLE wp.position (}}
> {{ account_id text,}}
> {{ security_id text,}}
> {{ counter bigint,}}
> {{ avg_exec_price double,}}
> {{ pending_quantity double,}}
> {{ quantity double,}}
> {{ transaction_id uuid,}}
> {{ update_time timestamp,}}
> {{ PRIMARY KEY (account_id, security_id, counter)}}
> {{) WITH CLUSTERING ORDER BY (security_id ASC, counter DESC)}}{{ }}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org

[jira] [Updated] (CASSANDRA-14209) group by select queries query results differ when using select * vs select fields

[Benjamin Lerer (JIRA)]

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

Benjamin Lerer updated CASSANDRA-14209:
---
Status: Patch Available  (was: Open)

> group by select queries query results differ when using select * vs select 
> fields
> -
>
> Key: CASSANDRA-14209
> URL: https://issues.apache.org/jira/browse/CASSANDRA-14209
> Project: Cassandra
>  Issue Type: Bug
>Reporter: Digant Modha
>Assignee: Benjamin Lerer
>Priority: Minor
> Attachments: Re group by select queries.txt
>
>
> {{I get two different out with these 2 queries.  The only difference between 
> the 2 queries is that one does ‘select *’ and other does ‘select specific 
> fields’ without any aggregate functions.}}
> {{I am using Apache Cassandra 3.10.}}
> {{Consistency level set to LOCAL_QUORUM.}}
> {{cassandra@cqlsh> select * from wp.position where account_id = 'user_1';}}
> {{ account_id | security_id | counter | avg_exec_price | pending_quantity | 
> quantity | transaction_id | update_time}}
> {{+-+-++--+--++-}}
> {{ user_1 | AMZN | 2 | 1239.2 | 0 | 1011 | null | 2018-01-25 
> 17:18:07.158000+}}
> {{ user_1 | AMZN | 1 | 1239.2 | 0 | 1010 | null | 2018-01-25 
> 17:18:07.158000+}}
> {{(2 rows)}}
> {{cassandra@cqlsh> select * from wp.position where account_id = 'user_1' 
> group by security_id;}}
> {{ account_id | security_id | counter | avg_exec_price | pending_quantity | 
> quantity | transaction_id | update_time}}
> {{+-+-++--+--++-}}
> {{ user_1 | AMZN | 1 | 1239.2 | 0 | 1010 | null | 2018-01-25 
> 17:18:07.158000+}}
> {{(1 rows)}}
> {{cassandra@cqlsh> select account_id,security_id, counter, 
> avg_exec_price,quantity, update_time from wp.position where account_id = 
> 'user_1' group by security_id ;}}
> {{ account_id | security_id | counter | avg_exec_price | quantity | 
> update_time}}
> {{+-+-++--+-}}
> {{ user_1 | AMZN | 2 | 1239.2 | 1011 | 2018-01-25 17:18:07.158000+}}
> {{(1 rows)}}
> {{Table Description:}}
> {{CREATE TABLE wp.position (}}
> {{ account_id text,}}
> {{ security_id text,}}
> {{ counter bigint,}}
> {{ avg_exec_price double,}}
> {{ pending_quantity double,}}
> {{ quantity double,}}
> {{ transaction_id uuid,}}
> {{ update_time timestamp,}}
> {{ PRIMARY KEY (account_id, security_id, counter)}}
> {{) WITH CLUSTERING ORDER BY (security_id ASC, counter DESC)}}{{ }}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org

[jira] [Updated] (CASSANDRA-9332) NPE when creating column family via thrift

[Jeff Jirsa (JIRA)]

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

Jeff Jirsa updated CASSANDRA-9332:
--
Labels: thrift  (was: proposed-cantrepro thrift)

> NPE when creating column family via thrift
> --
>
> Key: CASSANDRA-9332
> URL: https://issues.apache.org/jira/browse/CASSANDRA-9332
> Project: Cassandra
>  Issue Type: Bug
> Environment: Oracle JDK 1.7.0_79
> Casandra 2.0.6 in single node
> Ubuntu 14.04
>Reporter: Colin Kuo
>Assignee: Ryan McGuire
>Priority: Minor
>  Labels: thrift
> Fix For: 3.0.x
>
>
> When triggering unit test "testAddDropColumnFamily()" in 
> https://github.com/hector-client/hector/blob/master/core/src/test/java/me/prettyprint/cassandra/service/CassandraClusterTest.java
>  
> It occurs NPE when using *Cassandra 2.0.6* or later version.
> {noformat}
> 11:42:39,173 [Thrift:1] ERROR CustomTThreadPoolServer:212 - Error occurred 
> during processing of message.
> java.lang.NullPointerException
>   at org.apache.cassandra.db.RowMutation.add(RowMutation.java:112)
>   at 
> org.apache.cassandra.service.MigrationManager.addSerializedKeyspace(MigrationManager.java:265)
>   at 
> org.apache.cassandra.service.MigrationManager.announceNewColumnFamily(MigrationManager.java:213)
>   at 
> org.apache.cassandra.thrift.CassandraServer.system_add_column_family(CassandraServer.java:1521)
>   at 
> org.apache.cassandra.thrift.Cassandra$Processor$system_add_column_family.getResult(Cassandra.java:4300)
>   at 
> org.apache.cassandra.thrift.Cassandra$Processor$system_add_column_family.getResult(Cassandra.java:4284)
>   at org.apache.thrift.ProcessFunction.process(ProcessFunction.java:39)
>   at org.apache.thrift.TBaseProcessor.process(TBaseProcessor.java:39)
>   at 
> org.apache.cassandra.thrift.CustomTThreadPoolServer$WorkerProcess.run(CustomTThreadPoolServer.java:194)
>   at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
>   at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
>   at java.lang.Thread.run(Thread.java:745)
> {noformat}
> It seems that was introduced by fix of CASSANDRA-5631.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org

[jira] [Updated] (CASSANDRA-10499) ConcurrentModificationException in Background read repair

[Jeff Jirsa (JIRA)]

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

Jeff Jirsa updated CASSANDRA-10499:
---
Labels:   (was: proposed-cantrepro)

>  ConcurrentModificationException in Background read repair
> --
>
> Key: CASSANDRA-10499
> URL: https://issues.apache.org/jira/browse/CASSANDRA-10499
> Project: Cassandra
>  Issue Type: Bug
>Reporter: sankalp kohli
>Priority: Minor
>
> We are seeing the below exception in 2.0.14. While looking at the code, it 
> looks like it is happening due to ColumnFamily object being modified in SQF. 
> trim method.
> Exception in thread Thread[ReadRepairStage:4441,5,main]
> java.util.ConcurrentModificationException
>   at java.util.ArrayList$Itr.checkForComodification(ArrayList.java:859)
>   at java.util.ArrayList$Itr.next(ArrayList.java:831)
>   at 
> org.apache.cassandra.db.ColumnFamily.updateDigest(ColumnFamily.java:394)
>   at org.apache.cassandra.db.ColumnFamily.digest(ColumnFamily.java:388)
>   at 
> org.apache.cassandra.service.RowDigestResolver.resolve(RowDigestResolver.java:84)
>   at 
> org.apache.cassandra.service.RowDigestResolver.resolve(RowDigestResolver.java:28)
>   at 
> org.apache.cassandra.service.ReadCallback$AsyncRepairRunner.run(ReadCallback.java:173)
>   at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
>   at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
>   at java.lang.Thread.run(Thread.java:745)



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org

[jira] [Updated] (CASSANDRA-10393) LEAK DETECTED: a reference (org.apache.cassandra.utils.concurrent.Ref)

[Jeff Jirsa (JIRA)]

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

Jeff Jirsa updated CASSANDRA-10393:
---
Labels: memory-leak sstable  (was: memory-leak proposed-cantrepro sstable)

> LEAK DETECTED: a reference (org.apache.cassandra.utils.concurrent.Ref)
> --
>
> Key: CASSANDRA-10393
> URL: https://issues.apache.org/jira/browse/CASSANDRA-10393
> Project: Cassandra
>  Issue Type: Bug
> Environment: v 2.2.1 (from apt)
> -> lsb_release -a
> No LSB modules are available.
> Distributor ID:   Debian
> Description:  Debian GNU/Linux 7.8 (wheezy)
> Release:  7.8
> Codename: wheezy
> -> java -version
> java version "1.8.0_60"
> Java(TM) SE Runtime Environment (build 1.8.0_60-b27)
> Java HotSpot(TM) 64-Bit Server VM (build 25.60-b23, mixed mode)
>Reporter: Christian Winther
>Priority: Major
>  Labels: memory-leak, sstable
> Fix For: 2.2.x
>
>
> When trying to repair full on a table with the following schema my nodes 
> stall 
> and end up with spamming this 
> I've recently changed the table from SizeTieredCompactionStrategy to 
> LeveledCompactionStrategy.
> Coming from 2.1.9 -> 2.2.0 -> 2.2.1 i ran upgradesstable without issue as well
> When trying to full repair post compaction change, I got "out of order" 
> errors. A few google searches later, I was told to "scrub" the keyspace - did 
> that during the night (no problems logged, and no data lost)
> Now a repair just stalls and output memory leaks all over the place 
> {code}
> CREATE KEYSPACE sessions WITH replication = {'class': 'SimpleStrategy', 
> 'replication_factor': '3'}  AND durable_writes = true;
> CREATE TABLE sessions.sessions (
> id text PRIMARY KEY,
> client_ip text,
> controller text,
> controller_action text,
> created timestamp,
> data text,
> expires timestamp,
> http_host text,
> modified timestamp,
> request_agent text,
> request_agent_bot boolean,
> request_path text,
> site_id int,
> user_id int
> ) WITH bloom_filter_fp_chance = 0.01
> AND caching = '{"keys":"NONE", "rows_per_partition":"NONE"}'
> AND comment = ''
> AND compaction = {'class': 
> 'org.apache.cassandra.db.compaction.LeveledCompactionStrategy'}
> AND compression = {'sstable_compression': 
> 'org.apache.cassandra.io.compress.LZ4Compressor'}
> AND dclocal_read_repair_chance = 0.1
> AND default_time_to_live = 0
> AND gc_grace_seconds = 864000
> AND max_index_interval = 2048
> AND memtable_flush_period_in_ms = 0
> AND min_index_interval = 128
> AND read_repair_chance = 0.0
> AND speculative_retry = '99.0PERCENTILE';
> {code}
> {code}
> ERROR [Reference-Reaper:1] 2015-09-24 10:25:28,475 Ref.java:187 - LEAK 
> DETECTED: a reference 
> (org.apache.cassandra.utils.concurrent.Ref$State@4428a373) to class 
> org.apache.cassandra.io.sstable.format.SSTableReader$InstanceTidier@184765:/data/1/cassandra/sessions/sessions-77dd22f0ab9711e49cbc410c6b6f53a6/la-104037-big
>  was not released before the reference was garbage collected
> ERROR [Reference-Reaper:1] 2015-09-24 10:25:28,475 Ref.java:187 - LEAK 
> DETECTED: a reference 
> (org.apache.cassandra.utils.concurrent.Ref$State@368dd97) to class 
> org.apache.cassandra.io.sstable.format.SSTableReader$InstanceTidier@184765:/data/1/cassandra/sessions/sessions-77dd22f0ab9711e49cbc410c6b6f53a6/la-104037-big
>  was not released before the reference was garbage collected
> ERROR [Reference-Reaper:1] 2015-09-24 10:25:28,475 Ref.java:187 - LEAK 
> DETECTED: a reference 
> (org.apache.cassandra.utils.concurrent.Ref$State@66fb78be) to class 
> org.apache.cassandra.io.sstable.format.SSTableReader$InstanceTidier@184765:/data/1/cassandra/sessions/sessions-77dd22f0ab9711e49cbc410c6b6f53a6/la-104037-big
>  was not released before the reference was garbage collected
> ERROR [Reference-Reaper:1] 2015-09-24 10:25:28,475 Ref.java:187 - LEAK 
> DETECTED: a reference 
> (org.apache.cassandra.utils.concurrent.Ref$State@9fdd2e6) to class 
> org.apache.cassandra.io.sstable.format.SSTableReader$InstanceTidier@1460906269:/data/1/cassandra/sessions/sessions-77dd22f0ab9711e49cbc410c6b6f53a6/la-104788-big
>  was not released before the reference was garbage collected
> ERROR [Reference-Reaper:1] 2015-09-24 10:25:28,475 Ref.java:187 - LEAK 
> DETECTED: a reference 
> (org.apache.cassandra.utils.concurrent.Ref$State@84fcb91) to class 
> org.apache.cassandra.io.sstable.format.SSTableReader$InstanceTidier@1460906269:/data/1/cassandra/sessions/sessions-77dd22f0ab9711e49cbc410c6b6f53a6/la-104788-big
>  was not released before the reference was garbage collected
> {code}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (CASSANDRA-14229) Separate data drive for Index.db files

[Jeff Jirsa (JIRA)]

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

Jeff Jirsa commented on CASSANDRA-14229:


Sorta dove-tails in with CASSANDRA-8460 - similar purpose, different selection 
criteria, but could potentially use some of the same concepts.


> Separate data drive for Index.db files
> --
>
> Key: CASSANDRA-14229
> URL: https://issues.apache.org/jira/browse/CASSANDRA-14229
> Project: Cassandra
>  Issue Type: New Feature
>  Components: Local Write-Read Paths
>Reporter: Dan Kinder
>Priority: Minor
>
> For datasets with an active set of keys that well exceeds ram, it would be 
> quite useful to be able to put certain sstable files (e.g. *-Index.db) on a 
> separate, faster drive(s) than the data. E.g. put the indexes on SSD and data 
> on HDD. Particularly valuable when keys are much smaller than values. Also as 
> ram continues to get more expensive, users that currently optimize by having 
> large key caches may not need to buy as much of it.
> Our use case is a large dataset like this one. Storing all the data on SSD is 
> cost-prohibitive, and the reads are extremely random (effectively every key 
> is in the active set), so we don't have enough ram to cache it. (I did try 
> using a massive key cache, 64GB, and was seeing strange behavior anyway... 
> irqbalancer process pegged the cpu and the whole thing way underperformed. An 
> investigation for another day.)
> At the moment our only resolution is to buy enough HDD to handle 2 seeks per 
> read, 1 for the index and 1 for the data. But having indexes on SSD would 
> speed this way up, and practically require us to purchase a small number of 
> SSDs and about 1/2 the number of HDD.
> One user suggested lvmcache, which could work. I'd like to hear if this will 
> really work optimally and if lvmcache will really keep the right blocks on 
> the faster volume, and how reliable it is at the task.
> Note: asked about this on the mailing list and it was suggested I create a 
> JIRA.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org

[jira] [Comment Edited] (CASSANDRA-14233) nodetool tablestats/cfstats output has inconsistent formatting for latency

[Samuel Roberts (JIRA)]

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

Samuel Roberts edited comment on CASSANDRA-14233 at 2/14/18 8:17 AM:
-

Very simple to fix:

-[https://github.com/sproberts92/cassandra/commit/05ccb4851bf2ab1f35237ec901e1426a9bda]-

but I am confused about which branch to commit to - docs state start with the 
oldest branch? As the file has been moved around a lot and names changed, I'm 
not sure if this will propagate to 3.x cleanly.


was (Author: sproberts92):
Very simple to fix:

[https://github.com/sproberts92/cassandra/commit/05ccb4851bf2ab1f35237ec901e1426a9bda]

but I am confused about which branch to commit to - docs state start with the 
oldest branch? As the file has been moved around a lot and names changed, I'm 
not sure if this will propagate to 3.x cleanly.

> nodetool tablestats/cfstats output has inconsistent formatting for latency
> --
>
> Key: CASSANDRA-14233
> URL: https://issues.apache.org/jira/browse/CASSANDRA-14233
> Project: Cassandra
>  Issue Type: Bug
>Reporter: Samuel Roberts
>Assignee: Samuel Roberts
>Priority: Trivial
>   Original Estimate: 10m
>  Remaining Estimate: 10m
>
> Latencies are reported at keyspace level with `ms.` and at table level with 
> `ms`.
> There should be no trailing `.` as it is not a sentence and `.` is not part 
> of the abbreviation.
> This is also present in 2.x with `nodetool cfstats`.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org

[jira] [Resolved] (CASSANDRA-10393) LEAK DETECTED: a reference (org.apache.cassandra.utils.concurrent.Ref)

[Jeff Jirsa (JIRA)]

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

Jeff Jirsa resolved CASSANDRA-10393.

Resolution: Cannot Reproduce

Closing as cant-repro; reopen if you can repro reliably. 

> LEAK DETECTED: a reference (org.apache.cassandra.utils.concurrent.Ref)
> --
>
> Key: CASSANDRA-10393
> URL: https://issues.apache.org/jira/browse/CASSANDRA-10393
> Project: Cassandra
>  Issue Type: Bug
> Environment: v 2.2.1 (from apt)
> -> lsb_release -a
> No LSB modules are available.
> Distributor ID:   Debian
> Description:  Debian GNU/Linux 7.8 (wheezy)
> Release:  7.8
> Codename: wheezy
> -> java -version
> java version "1.8.0_60"
> Java(TM) SE Runtime Environment (build 1.8.0_60-b27)
> Java HotSpot(TM) 64-Bit Server VM (build 25.60-b23, mixed mode)
>Reporter: Christian Winther
>Priority: Major
>  Labels: memory-leak, proposed-cantrepro, sstable
> Fix For: 2.2.x
>
>
> When trying to repair full on a table with the following schema my nodes 
> stall 
> and end up with spamming this 
> I've recently changed the table from SizeTieredCompactionStrategy to 
> LeveledCompactionStrategy.
> Coming from 2.1.9 -> 2.2.0 -> 2.2.1 i ran upgradesstable without issue as well
> When trying to full repair post compaction change, I got "out of order" 
> errors. A few google searches later, I was told to "scrub" the keyspace - did 
> that during the night (no problems logged, and no data lost)
> Now a repair just stalls and output memory leaks all over the place 
> {code}
> CREATE KEYSPACE sessions WITH replication = {'class': 'SimpleStrategy', 
> 'replication_factor': '3'}  AND durable_writes = true;
> CREATE TABLE sessions.sessions (
> id text PRIMARY KEY,
> client_ip text,
> controller text,
> controller_action text,
> created timestamp,
> data text,
> expires timestamp,
> http_host text,
> modified timestamp,
> request_agent text,
> request_agent_bot boolean,
> request_path text,
> site_id int,
> user_id int
> ) WITH bloom_filter_fp_chance = 0.01
> AND caching = '{"keys":"NONE", "rows_per_partition":"NONE"}'
> AND comment = ''
> AND compaction = {'class': 
> 'org.apache.cassandra.db.compaction.LeveledCompactionStrategy'}
> AND compression = {'sstable_compression': 
> 'org.apache.cassandra.io.compress.LZ4Compressor'}
> AND dclocal_read_repair_chance = 0.1
> AND default_time_to_live = 0
> AND gc_grace_seconds = 864000
> AND max_index_interval = 2048
> AND memtable_flush_period_in_ms = 0
> AND min_index_interval = 128
> AND read_repair_chance = 0.0
> AND speculative_retry = '99.0PERCENTILE';
> {code}
> {code}
> ERROR [Reference-Reaper:1] 2015-09-24 10:25:28,475 Ref.java:187 - LEAK 
> DETECTED: a reference 
> (org.apache.cassandra.utils.concurrent.Ref$State@4428a373) to class 
> org.apache.cassandra.io.sstable.format.SSTableReader$InstanceTidier@184765:/data/1/cassandra/sessions/sessions-77dd22f0ab9711e49cbc410c6b6f53a6/la-104037-big
>  was not released before the reference was garbage collected
> ERROR [Reference-Reaper:1] 2015-09-24 10:25:28,475 Ref.java:187 - LEAK 
> DETECTED: a reference 
> (org.apache.cassandra.utils.concurrent.Ref$State@368dd97) to class 
> org.apache.cassandra.io.sstable.format.SSTableReader$InstanceTidier@184765:/data/1/cassandra/sessions/sessions-77dd22f0ab9711e49cbc410c6b6f53a6/la-104037-big
>  was not released before the reference was garbage collected
> ERROR [Reference-Reaper:1] 2015-09-24 10:25:28,475 Ref.java:187 - LEAK 
> DETECTED: a reference 
> (org.apache.cassandra.utils.concurrent.Ref$State@66fb78be) to class 
> org.apache.cassandra.io.sstable.format.SSTableReader$InstanceTidier@184765:/data/1/cassandra/sessions/sessions-77dd22f0ab9711e49cbc410c6b6f53a6/la-104037-big
>  was not released before the reference was garbage collected
> ERROR [Reference-Reaper:1] 2015-09-24 10:25:28,475 Ref.java:187 - LEAK 
> DETECTED: a reference 
> (org.apache.cassandra.utils.concurrent.Ref$State@9fdd2e6) to class 
> org.apache.cassandra.io.sstable.format.SSTableReader$InstanceTidier@1460906269:/data/1/cassandra/sessions/sessions-77dd22f0ab9711e49cbc410c6b6f53a6/la-104788-big
>  was not released before the reference was garbage collected
> ERROR [Reference-Reaper:1] 2015-09-24 10:25:28,475 Ref.java:187 - LEAK 
> DETECTED: a reference 
> (org.apache.cassandra.utils.concurrent.Ref$State@84fcb91) to class 
> org.apache.cassandra.io.sstable.format.SSTableReader$InstanceTidier@1460906269:/data/1/cassandra/sessions/sessions-77dd22f0ab9711e49cbc410c6b6f53a6/la-104788-big
>  was not released before the reference was garbage collected
> {code}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Resolved] (CASSANDRA-9332) NPE when creating column family via thrift

[Jeff Jirsa (JIRA)]

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

Jeff Jirsa resolved CASSANDRA-9332.
---
   Resolution: Cannot Reproduce
Reproduced In: 2.0.14, 2.0.6  (was: 2.0.6, 2.0.14)

Closing as cant-repro; reopen if you can repro reliably. 

> NPE when creating column family via thrift
> --
>
> Key: CASSANDRA-9332
> URL: https://issues.apache.org/jira/browse/CASSANDRA-9332
> Project: Cassandra
>  Issue Type: Bug
> Environment: Oracle JDK 1.7.0_79
> Casandra 2.0.6 in single node
> Ubuntu 14.04
>Reporter: Colin Kuo
>Assignee: Ryan McGuire
>Priority: Minor
>  Labels: proposed-cantrepro, thrift
> Fix For: 3.0.x
>
>
> When triggering unit test "testAddDropColumnFamily()" in 
> https://github.com/hector-client/hector/blob/master/core/src/test/java/me/prettyprint/cassandra/service/CassandraClusterTest.java
>  
> It occurs NPE when using *Cassandra 2.0.6* or later version.
> {noformat}
> 11:42:39,173 [Thrift:1] ERROR CustomTThreadPoolServer:212 - Error occurred 
> during processing of message.
> java.lang.NullPointerException
>   at org.apache.cassandra.db.RowMutation.add(RowMutation.java:112)
>   at 
> org.apache.cassandra.service.MigrationManager.addSerializedKeyspace(MigrationManager.java:265)
>   at 
> org.apache.cassandra.service.MigrationManager.announceNewColumnFamily(MigrationManager.java:213)
>   at 
> org.apache.cassandra.thrift.CassandraServer.system_add_column_family(CassandraServer.java:1521)
>   at 
> org.apache.cassandra.thrift.Cassandra$Processor$system_add_column_family.getResult(Cassandra.java:4300)
>   at 
> org.apache.cassandra.thrift.Cassandra$Processor$system_add_column_family.getResult(Cassandra.java:4284)
>   at org.apache.thrift.ProcessFunction.process(ProcessFunction.java:39)
>   at org.apache.thrift.TBaseProcessor.process(TBaseProcessor.java:39)
>   at 
> org.apache.cassandra.thrift.CustomTThreadPoolServer$WorkerProcess.run(CustomTThreadPoolServer.java:194)
>   at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
>   at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
>   at java.lang.Thread.run(Thread.java:745)
> {noformat}
> It seems that was introduced by fix of CASSANDRA-5631.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org

[jira] [Resolved] (CASSANDRA-10499) ConcurrentModificationException in Background read repair

[Jeff Jirsa (JIRA)]

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

Jeff Jirsa resolved CASSANDRA-10499.

Resolution: Cannot Reproduce

Closing as cant-repro; reopen if you can repro reliably. 

>  ConcurrentModificationException in Background read repair
> --
>
> Key: CASSANDRA-10499
> URL: https://issues.apache.org/jira/browse/CASSANDRA-10499
> Project: Cassandra
>  Issue Type: Bug
>Reporter: sankalp kohli
>Priority: Minor
>  Labels: proposed-cantrepro
>
> We are seeing the below exception in 2.0.14. While looking at the code, it 
> looks like it is happening due to ColumnFamily object being modified in SQF. 
> trim method.
> Exception in thread Thread[ReadRepairStage:4441,5,main]
> java.util.ConcurrentModificationException
>   at java.util.ArrayList$Itr.checkForComodification(ArrayList.java:859)
>   at java.util.ArrayList$Itr.next(ArrayList.java:831)
>   at 
> org.apache.cassandra.db.ColumnFamily.updateDigest(ColumnFamily.java:394)
>   at org.apache.cassandra.db.ColumnFamily.digest(ColumnFamily.java:388)
>   at 
> org.apache.cassandra.service.RowDigestResolver.resolve(RowDigestResolver.java:84)
>   at 
> org.apache.cassandra.service.RowDigestResolver.resolve(RowDigestResolver.java:28)
>   at 
> org.apache.cassandra.service.ReadCallback$AsyncRepairRunner.run(ReadCallback.java:173)
>   at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
>   at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
>   at java.lang.Thread.run(Thread.java:745)



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org

[jira] [Updated] (CASSANDRA-10937) OOM on multiple nodes on write load (v. 3.0.0), problem also present on DSE-4.8.3, but there it survives more time

[Jeff Jirsa (JIRA)]

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

Jeff Jirsa updated CASSANDRA-10937:
---
Labels:   (was: proposed-wontfix)

> OOM on multiple nodes on write load (v. 3.0.0), problem also present on 
> DSE-4.8.3, but there it survives more time
> --
>
> Key: CASSANDRA-10937
> URL: https://issues.apache.org/jira/browse/CASSANDRA-10937
> Project: Cassandra
>  Issue Type: Bug
> Environment: Cassandra : 3.0.0
> Installed as open archive, no connection to any OS specific installer.
> Java:
> Java(TM) SE Runtime Environment (build 1.8.0_65-b17)
> OS :
> Linux version 2.6.32-431.el6.x86_64 
> (mockbu...@x86-023.build.eng.bos.redhat.com) (gcc version 4.4.7 20120313 (Red 
> Hat 4.4.7-4) (GCC) ) #1 SMP Sun Nov 10 22:19:54 EST 2013
> We have:
> 8 guests ( Linux OS as above) on 2 (VMWare managed) physical hosts. Each 
> physical host keeps 4 guests.
> Physical host parameters(shared by all 4 guests):
> Model: HP ProLiant DL380 Gen9
> Intel(R) Xeon(R) CPU E5-2690 v3 @ 2.60GHz
> 46 logical processors.
> Hyperthreading - enabled
> Each guest assigned to have:
> 1 disk 300 Gb for seq. log (NOT SSD)
> 1 disk 4T for data (NOT SSD)
> 11 CPU cores
> Disks are local, not shared.
> Memory on each host -  24 Gb total.
> 8 (or 6, tested both) Gb - cassandra heap
> (lshw and cpuinfo attached in file test2.rar)
>Reporter: Peter Kovgan
>Priority: Critical
> Attachments: cassandra-to-jack-krupansky.docx, gc-stat.txt, 
> more-logs.rar, some-heap-stats.rar, test2.rar, test3.rar, test4.rar, 
> test5.rar, test_2.1.rar, test_2.1_logs_older.rar, 
> test_2.1_restart_attempt_log.rar
>
>
> 8 cassandra nodes.
> Load test started with 4 clients(different and not equal machines), each 
> running 1000 threads.
> Each thread assigned in round-robin way to run one of 4 different inserts. 
> Consistency->ONE.
> I attach the full CQL schema of tables and the query of insert.
> Replication factor - 2:
> create keyspace OBLREPOSITORY_NY with replication = 
> {'class':'NetworkTopologyStrategy','NY':2};
> Initiall throughput is:
> 215.000  inserts /sec
> or
> 54Mb/sec, considering single insert size a bit larger than 256byte.
> Data:
> all fields(5-6) are short strings, except one is BLOB of 256 bytes.
> After about a 2-3 hours of work, I was forced to increase timeout from 2000 
> to 5000ms, for some requests failed for short timeout.
> Later on(after aprox. 12 hous of work) OOM happens on multiple nodes.
> (all failed nodes logs attached)
> I attach also java load client and instructions how set-up and use 
> it.(test2.rar)
> Update:
> Later on test repeated with lesser load (10 mes/sec) with more relaxed 
> CPU (idle 25%), with only 2 test clients, but anyway test failed.
> Update:
> DSE-4.8.3 also failed on OOM (3 nodes from 8), but here it survived 48 hours, 
> not 10-12.
> Attachments:
> test2.rar -contains most of material
> more-logs.rar - contains additional nodes logs



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org

[jira] [Updated] (CASSANDRA-11171) conditional update without paxos

[Jeff Jirsa (JIRA)]

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

Jeff Jirsa updated CASSANDRA-11171:
---
Labels:   (was: proposed-wontfix)

> conditional update without paxos
> 
>
> Key: CASSANDRA-11171
> URL: https://issues.apache.org/jira/browse/CASSANDRA-11171
> Project: Cassandra
>  Issue Type: Wish
>Reporter: stuart
>Priority: Minor
>
> I realise that currently conditional updates use lightweight transactions to 
> provide an atomic check and set operation but that this comes at a non 
> trivial performance cost. I have a solution where synchronised access is 
> ensured by an external mechanism therefore I don't think paxos would be 
> required. It would be nice to be able to run an update command or script that 
> could conditionally update without the performance hit. Currently I'd have to 
> retrieve each row first at the application level before deciding whether or 
> not to perform the update. Would it be possible to add a switch for the 
> conditional updates to turn paxos on or off? Thanks.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org

[jira] [Updated] (CASSANDRA-11460) memory leak

[Jeff Jirsa (JIRA)]

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

Jeff Jirsa updated CASSANDRA-11460:
---
Labels:   (was: proposed-wontfix)

> memory leak
> ---
>
> Key: CASSANDRA-11460
> URL: https://issues.apache.org/jira/browse/CASSANDRA-11460
> Project: Cassandra
>  Issue Type: Bug
>Reporter: stone
>Priority: Critical
> Attachments: aaa.jpg
>
>
> env:
> cassandra3.3
> jdk8
> 8G Ram
> so set
> MAX_HEAP_SIZE="2G"
> HEAP_NEWSIZE="400M"
> 1.met same problem about this:
> https://issues.apache.org/jira/browse/CASSANDRA-9549
> I confuse about that this was fixed in release 3.3 according this page:
> https://github.com/apache/cassandra/blob/trunk/CHANGES.txt
> so I change to 3.4,and also have  found this problem again 
> I think this fix should be included in 3.3.3.4
> can you explain about this?
> 2.our write rate exceed the value that our cassandra env can support,
> but i think it should descrese the write rate,or block.consumer the writed 
> data,keep the memory down,then go on writing,not cause out-of-memory instead.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org

[jira] [Updated] (CASSANDRA-13093) 2.2.8 Node goes down with MUTATION messages were dropped in last 5000 ms: 29 for internal timeout

[Jeff Jirsa (JIRA)]

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

Jeff Jirsa updated CASSANDRA-13093:
---
Labels:   (was: proposed-wontfix)

> 2.2.8 Node goes down with MUTATION messages were dropped in last 5000 ms: 29 
> for internal timeout
> -
>
> Key: CASSANDRA-13093
> URL: https://issues.apache.org/jira/browse/CASSANDRA-13093
> Project: Cassandra
>  Issue Type: Bug
>  Components: Core
> Environment: 2.2.8 Cassandra on 4 Nodes with Red Hat Linux 6.2 64 Bit
>Reporter: sutanu das
>Priority: Critical
>
> Issue: 1st Node of 4 Node in Cluster keeps aborting (jvm crashing) with 
> following messages:
> - ReadTimeoutException: Operation timed out - received only 0 responses
> - MUTATION messages were dropped in last 5000 ms: 29 for internal timeout and 
> 0 for cross node timeout
> - Spark Jobs getting Q'd up when opening Channels, followed up Read Time Outs:
>   ERROR [SharedPool-Worker-207] 2017-01-03 16:39:00,493 Message.java:611 
> - Unexpected exception during request; channel = [id: 0xd0b0d36d, 
> /216.12.229.180:41896 :> /172.17.30.47:9042]
>   java.lang.RuntimeException: 
> org.apache.cassandra.exceptions.ReadTimeoutException: Operation timed out - 
> received only 0 responses.
>   
> What has been done so far?
>  - Host Reboot node 01
>  - Mutiple C* restarts
>  - Increased read_request_timeout_in_ms from 1 to 5
>  - Increased request_timeout_in_ms from 1 to 5
>  - Changed following:
>   concurrent_reads: 128
>   concurrent_writes: 128
>   concurrent_counter_writes: 128
>  - Upgrade to 2.2.8 - All Nodes Sync with 2.2.8
>  - All nodes have same Pass Auth Scheme (Node 03 was a mis-match and was 
> fixed)
>   - authenticator: org.apache.cassandra.auth.PasswordAuthenticator
>   - authorizer: org.apache.cassandra.auth.CassandraAuthorizer
> Full exception stack:
> DEBUG [SharedPool-Worker-10] 2017-01-03 16:32:43,983 StorageProxy.java:1898 - 
> Range slice timeout; received 0 of 1 responses for range 1 of 1
> INFO  [Service Thread] 2017-01-03 16:32:43,983 GCInspector.java:284 - ParNew 
> GC in 247ms.  CMS Old Gen: 3768220776 -> 3996971216; Par Eden Space: 
> 1718091776 -> 0;
> INFO  [Service Thread] 2017-01-03 16:32:43,983 StatusLogger.java:52 - Pool 
> NameActive   Pending  Completed   Blocked  All Time 
> Blocked
> DEBUG [SharedPool-Worker-26] 2017-01-03 16:32:43,984 
> FileCacheService.java:102 - Evicting cold readers for 
> /cassandra/data/system_auth/roles-5bc52802de2535edaeab188eecebb090/la-51-big-Data.db
> DEBUG [SharedPool-Worker-28] 2017-01-03 16:32:43,986 
> AbstractQueryPager.java:89 - Got empty set of rows, considering pager 
> exhausted
> INFO  [ScheduledTasks:1] 2017-01-03 16:39:00,473 MessagingService.java:946 - 
> RANGE_SLICE messages were dropped in last 5000 ms: 2 for internal timeout and 
> 0 for cross node timeout
> INFO  [Service Thread] 2017-01-03 16:39:00,476 StatusLogger.java:106 - 
> sales.airwave_dwell_time_det_hr 0,0
> ERROR [SharedPool-Worker-207] 2017-01-03 16:39:00,493 Message.java:611 - 
> Unexpected exception during request; channel = [id: 0xd0b0d36d, 
> /216.12.229.180:41896 :> /172.17.30.47:9042]
> java.lang.RuntimeException: 
> org.apache.cassandra.exceptions.ReadTimeoutException: Operation timed out - 
> received only 0 responses.
> at 
> org.apache.cassandra.auth.CassandraRoleManager.getRole(CassandraRoleManager.java:497)
>  ~[apache-cassandra-2.2.8.jar:2.2.8]
> at 
> org.apache.cassandra.auth.CassandraRoleManager.canLogin(CassandraRoleManager.java:306)
>  ~[apache-cassandra-2.2.8.jar:2.2.8]
> at 
> org.apache.cassandra.service.ClientState.login(ClientState.java:269) 
> ~[apache-cassandra-2.2.8.jar:2.2.8]
> at 
> org.apache.cassandra.transport.messages.AuthResponse.execute(AuthResponse.java:79)
>  ~[apache-cassandra-2.2.8.jar:2.2.8]
> at 
> org.apache.cassandra.transport.Message$Dispatcher.channelRead0(Message.java:507)
>  [apache-cassandra-2.2.8.jar:2.2.8]
> at 
> org.apache.cassandra.transport.Message$Dispatcher.channelRead0(Message.java:401)
>  [apache-cassandra-2.2.8.jar:2.2.8]
> at 
> io.netty.channel.SimpleChannelInboundHandler.channelRead(SimpleChannelInboundHandler.java:105)
>  [netty-all-4.0.23.Final.jar:4.0.23.Final]
> at 
> io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:333)
>  [netty-all-4.0.23.Final.jar:4.0.23.Final]
> at 
> io.netty.channel.AbstractChannelHandlerContext.access$700(AbstractChannelHandlerContext.java:32)
>  [netty-all-4.0.23.Final.jar:4.0.23.Final]
> at 
> 

[jira] [Updated] (CASSANDRA-11955) Impossibly large value displayed for data "load" and "Space used (*):"

[Jeff Jirsa (JIRA)]

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

Jeff Jirsa updated CASSANDRA-11955:
---
Labels:   (was: proposed-cantrepro)

> Impossibly large value displayed for data "load" and "Space used (*):"
> --
>
> Key: CASSANDRA-11955
> URL: https://issues.apache.org/jira/browse/CASSANDRA-11955
> Project: Cassandra
>  Issue Type: Bug
>  Components: Compaction
>Reporter: Nate McCall
>Priority: Major
>
> The data load as reported by nodetool views looks like it is not getting 
> updated correctly (from compaction?):
> {noformat}
> # nodetool status
> Datacenter: dc1
> ==
> Status=Up/Down
> |/ State=Normal/Leaving/Joining/Moving
> --  Address Load   Tokens   Owns (effective)  Host ID 
>   Rack
> UJ  [redacted]   1.1 GB 256  ? 
> 0dfd164c-b874-4e90-be2c-3fea8e12d78e  a
> UN  [redacted]   14.96 TB   256  49.0% 
> 02821ddb-a463-4845-b2ca-bed1da141e81  a
> UN  [redacted] 31.94 TB   256  51.2% 
> 30531bfe-fe0e-4360-a22b-36bf200a9679  e
> UN  [redacted]   1.81 TB256  54.0% 
> 17a93464-41c4-49f8-8042-b2741c5e3256  d
> UN  [redacted]   22.2 TB256  46.0% 
> f35b4aeb-33e5-4f53-bc9d-49de3a157e3e  d
> UN  [redacted]28.53 TB   256  51.0% 
> 74e04517-de70-4754-82fc-2dc867a14ae7  a
> UN  [redacted]  39.25 TB   256  48.8% 
> 3a271443-db02-4487-be52-d6c35b66da40  e
> {noformat}
> NOTE: unknown if the join is related as the "TB" vs. "GB" discrepancy was 
> only noticed after the join started.
> And same for {{nodetool tablestats}} details of the {{30531bfe...}} node: 
> {noformat}
> # nodetool tablestats
> Keyspace: myks
> Read Count: 1306765640
> Read Latency: 0.22125289495291597 ms.
> Write Count: 3375354023
> Write Latency: 0.017621884565795665 ms.
> Pending Flushes: 0
> Table: mytable
> SSTable count: 110
> Space used (live): 31374649977187
> Space used (total): 31374649977187
> Space used by snapshots (total): 0
> ...
> {noformat}
> Nothing fancy on this table (there is only one active table on this cluster): 
> STCS with defaults, no MVs, no indexes just text and int columns with a 
> single value partition key. 
> NOTE: once restarted, the values then display as correct, creeping up from 
> there (thus my thinking that this is a compaction issue). 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org

[jira] [Updated] (CASSANDRA-12857) Upgrade procedure between 2.1.x and 3.0.x is broken

[Jeff Jirsa (JIRA)]

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

Jeff Jirsa updated CASSANDRA-12857:
---
Labels:   (was: proposed-wontfix)

> Upgrade procedure between 2.1.x and 3.0.x is broken
> ---
>
> Key: CASSANDRA-12857
> URL: https://issues.apache.org/jira/browse/CASSANDRA-12857
> Project: Cassandra
>  Issue Type: Bug
>Reporter: Alexander Yasnogor
>Priority: Critical
> Attachments: cassandra.schema
>
>
> It is not possible safely to do Cassandra in place upgrade from 2.1.14 to 
> 3.0.9.
> Distribution: deb packages from datastax community repo.
> The upgrade was performed according to procedure from this docu: 
> https://docs.datastax.com/en/upgrade/doc/upgrade/cassandra/upgrdCassandraDetails.html
> Potential reason: The upgrade procedure creates corrupted system_schema and 
> this keyspace get populated in the cluster and kills it.
> We started with one datacenter which contains 19 nodes divided to two racks.
> First rack was successfully upgraded and nodetool describecluster reported 
> two schema versions. One for upgraded nodes, another for non-upgraded nodes.
> On starting new version on a first node from the second rack:
> {code:java}
> INFO  [main] 2016-10-25 13:06:12,103 LegacySchemaMigrator.java:87 - Moving 11 
> keyspaces from legacy schema tables to the new schema keyspace (system_schema)
> INFO  [main] 2016-10-25 13:06:12,104 LegacySchemaMigrator.java:148 - 
> Migrating keyspace 
> org.apache.cassandra.schema.LegacySchemaMigrator$Keyspace@7505e6ac
> INFO  [main] 2016-10-25 13:06:12,200 LegacySchemaMigrator.java:148 - 
> Migrating keyspace 
> org.apache.cassandra.schema.LegacySchemaMigrator$Keyspace@64414574
> INFO  [main] 2016-10-25 13:06:12,204 LegacySchemaMigrator.java:148 - 
> Migrating keyspace 
> org.apache.cassandra.schema.LegacySchemaMigrator$Keyspace@3f2c5f45
> INFO  [main] 2016-10-25 13:06:12,207 LegacySchemaMigrator.java:148 - 
> Migrating keyspace 
> org.apache.cassandra.schema.LegacySchemaMigrator$Keyspace@2bc2d64d
> INFO  [main] 2016-10-25 13:06:12,301 LegacySchemaMigrator.java:148 - 
> Migrating keyspace 
> org.apache.cassandra.schema.LegacySchemaMigrator$Keyspace@77343846
> INFO  [main] 2016-10-25 13:06:12,305 LegacySchemaMigrator.java:148 - 
> Migrating keyspace 
> org.apache.cassandra.schema.LegacySchemaMigrator$Keyspace@19b0b931
> INFO  [main] 2016-10-25 13:06:12,308 LegacySchemaMigrator.java:148 - 
> Migrating keyspace 
> org.apache.cassandra.schema.LegacySchemaMigrator$Keyspace@44bb0b35
> INFO  [main] 2016-10-25 13:06:12,311 LegacySchemaMigrator.java:148 - 
> Migrating keyspace 
> org.apache.cassandra.schema.LegacySchemaMigrator$Keyspace@79f6cd51
> INFO  [main] 2016-10-25 13:06:12,319 LegacySchemaMigrator.java:148 - 
> Migrating keyspace 
> org.apache.cassandra.schema.LegacySchemaMigrator$Keyspace@2fcd363b
> INFO  [main] 2016-10-25 13:06:12,356 LegacySchemaMigrator.java:148 - 
> Migrating keyspace 
> org.apache.cassandra.schema.LegacySchemaMigrator$Keyspace@609eead6
> INFO  [main] 2016-10-25 13:06:12,358 LegacySchemaMigrator.java:148 - 
> Migrating keyspace 
> org.apache.cassandra.schema.LegacySchemaMigrator$Keyspace@7eb7f5d0
> INFO  [main] 2016-10-25 13:06:13,958 LegacySchemaMigrator.java:97 - 
> Truncating legacy schema tables
> INFO  [main] 2016-10-25 13:06:26,474 LegacySchemaMigrator.java:103 - 
> Completed migration of legacy schema tables
> INFO  [main] 2016-10-25 13:06:26,474 StorageService.java:521 - Populating 
> token metadata from system tables
> INFO  [main] 2016-10-25 13:06:26,796 StorageService.java:528 - Token 
> metadata: Normal Tokens: [HUGE LIST of tokens]
> INFO  [main] 2016-10-25 13:06:29,066 ColumnFamilyStore.java:389 - 
> Initializing ...
> INFO  [main] 2016-10-25 13:06:29,066 ColumnFamilyStore.java:389 - 
> Initializing ...
> INFO  [main] 2016-10-25 13:06:45,894 AutoSavingCache.java:165 - Completed 
> loading (2 ms; 460 keys) KeyCache cache
> INFO  [main] 2016-10-25 13:06:46,982 StorageService.java:521 - Populating 
> token metadata from system tables
> INFO  [main] 2016-10-25 13:06:47,394 StorageService.java:528 - Token 
> metadata: Normal Tokens:[HUGE LIST of tokens]
> INFO  [main] 2016-10-25 13:06:47,420 LegacyHintsMigrator.java:88 - Migrating 
> legacy hints to new storage
> INFO  [main] 2016-10-25 13:06:47,420 LegacyHintsMigrator.java:91 - Forcing a 
> major compaction of system.hints table
> INFO  [main] 2016-10-25 13:06:50,587 LegacyHintsMigrator.java:95 - Writing 
> legacy hints to the new storage
> INFO  [main] 2016-10-25 13:06:53,927 LegacyHintsMigrator.java:99 - Truncating 
> system.hints table
> 
> INFO  [main] 2016-10-25 13:06:56,572 MigrationManager.java:342 - Create new 
> table: 
> 

[jira] [Updated] (CASSANDRA-11821) nodetool cfhistograms throws java.lang.ArrayIndexOutOfBoundsException and reset the cfhistograms

[Jeff Jirsa (JIRA)]

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

Jeff Jirsa updated CASSANDRA-11821:
---
Labels:   (was: proposed-wontfix)

> nodetool cfhistograms throws java.lang.ArrayIndexOutOfBoundsException and 
> reset the cfhistograms
> 
>
> Key: CASSANDRA-11821
> URL: https://issues.apache.org/jira/browse/CASSANDRA-11821
> Project: Cassandra
>  Issue Type: Bug
>  Components: Tools
> Environment: 2.0.17, rhel6.4
>Reporter: Benoit Perroud
>Priority: Minor
>
> I had nodes running for a decent amount of time (like 3 months).
> {code}
> nodetool cfhistograms keyspace table
> {code}
> did throw and {{ArrayIndexOutOfBoundsException}} in the read latency section:
> {code}
> Read Latency (microseconds)
> Exception in thread "main" java.lang.ArrayIndexOutOfBoundsException: 90
>   at org.apache.cassandra.tools.NodeCmd.printHistogram(NodeCmd.java:1086)
>   at 
> org.apache.cassandra.tools.NodeCmd.printCfHistograms(NodeCmd.java:1138)
>   at org.apache.cassandra.tools.NodeCmd.main(NodeCmd.java:1472)
> {code}
> Surprisingly, the running the same cmd a second time did succeeded, but the 
> histograms seem to be reset:
> first call:
> {code}
> SSTables per Read
>1 sstables: 183026
>2 sstables: 176538
>3 sstables: 49159
>4 sstables: 23034
>5 sstables: 16380
> ...
> Write Latency (microseconds)
>   3 us: 4
>   4 us: 33
>   5 us: 237
>   6 us: 1193
>   7 us: 4055
>   8 us: 14357
>  10 us: 146728
>  12 us: 565588
>  14 us: 1907616
>  17 us: 8468503
>  20 us: 16218034
> ...
> {code}
> After:
> {code}
> SSTables per Read
> 2 sstables: 52
> 3 sstables: 4
> Write Latency (microseconds)
>   6 us: 1
>   7 us: 3
>   8 us: 5
>  10 us: 53
>  12 us: 133
>  14 us: 379
>  17 us: 1190
>  20 us: 1605
> {code}
> I didn't find anything on the logs, and I wasn't able to have the exception 
> popping out more than once per servers.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org

[jira] [Updated] (CASSANDRA-10173) Compaction isn't cleaning out tombstones between hint deliveries

[Jeff Jirsa (JIRA)]

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

Jeff Jirsa updated CASSANDRA-10173:
---
Labels:   (was: proposed-wontfix)

> Compaction isn't cleaning out tombstones between hint deliveries
> 
>
> Key: CASSANDRA-10173
> URL: https://issues.apache.org/jira/browse/CASSANDRA-10173
> Project: Cassandra
>  Issue Type: Bug
>Reporter: Jonathan Ellis
>Priority: Major
> Fix For: 2.2.x
>
> Attachments: system (3).log
>
>
> 3 node cluster, 100M writes.  Same scenario as 10172:
> Test Start: 00:00:00
> Node 1 Killed: 00:05:48
> Node 2 Killed: 00:13:33
> Node 1 Started: 00:24:20
> Node 2 Started: 00:32:23
> Test Done: 00:38:33
> Node 1 hints replay finished: 00:56:16
> Node 2 hints replay finished: 01:00:16
> Node 3 hints replay finished: 02:08:00
> Log attached.  Note the tombstone_failure_threshold errors.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org

[jira] [Updated] (CASSANDRA-12103) Cassandra is hang and cqlsh was not able to login with OperationTimeout error

[Jeff Jirsa (JIRA)]

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

Jeff Jirsa updated CASSANDRA-12103:
---
Labels:   (was: proposed-wontfix)

> Cassandra is hang and cqlsh was not able to login with OperationTimeout error
> -
>
> Key: CASSANDRA-12103
> URL: https://issues.apache.org/jira/browse/CASSANDRA-12103
> Project: Cassandra
>  Issue Type: Bug
>  Components: Core, Local Write-Read Paths
> Environment: centos 6.5 cassandra 2.1.9
>Reporter: peng xiao
>Priority: Critical
> Attachments: system.log.2016-06-28_1257.gz
>
>
> Hi,
> We have two DCs(DC1 and DC2) with DC1 3 nodes and DC2 9 nodes.
> And we experienced a Timeout error today,all applications connected to DC1 
> were hang and no response,even cqlsh was not able to log into any node in DC1.
> I restarted the 3 nodes in DC1,the problem was not resolved.
> Then we switched to DC2,then applications back to normal.
> Could you please help to take a look?
> Thanks
> many errors like below:
> ERROR [SharedPool-Worker-43] 2016-06-28 11:58:49,705 Message.java:538 - 
> Unexpected exception during request; channel = [id: 0x87e315d6, 
> /172.16.10.198:13604 => /172.16.11.13:9042]
> java.lang.RuntimeException: 
> org.apache.cassandra.exceptions.ReadTimeoutException: Operation timed out - 
> received only 0 responses.
> at org.apache.cassandra.auth.Auth.selectUser(Auth.java:276) 
> ~[apache-cassandra-2.1.9.jar:2.1.9]
> at org.apache.cassandra.auth.Auth.isExistingUser(Auth.java:86) 
> ~[apache-cassandra-2.1.9.jar:2.1.9]
> at 
> org.apache.cassandra.service.ClientState.login(ClientState.java:206) 
> ~[apache-cassandra-2.1.9.jar:2.1.9]
> at 
> org.apache.cassandra.transport.messages.AuthResponse.execute(AuthResponse.java:82)
>  ~[apache-cassandra-2.1.9.jar:2.1.9]
> at 
> org.apache.cassandra.transport.Message$Dispatcher.channelRead0(Message.java:439)
>  [apache-cassandra-2.1.9.jar:2.1.9]
> at 
> org.apache.cassandra.transport.Message$Dispatcher.channelRead0(Message.java:335)
>  [apache-cassandra-2.1.9.jar:2.1.9]
> at 
> io.netty.channel.SimpleChannelInboundHandler.channelRead(SimpleChannelInboundHandler.java:105)
>  [netty-all-4.0.23.Final.jar:4.0.23.Final]
> at 
> io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:333)
>  [netty-all-4.0.23.Final.jar:4.0.23.Final]
> at 
> io.netty.channel.AbstractChannelHandlerContext.access$700(AbstractChannelHandlerContext.java:32)
>  [netty-all-4.0.23.Final.jar:4.0.23.Final]
> at 
> io.netty.channel.AbstractChannelHandlerContext$8.run(AbstractChannelHandlerContext.java:324)
>  [netty-all-4.0.23.Final.jar:4.0.23.Final]
> at 
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) 
> [na:1.8.0]
> at 
> org.apache.cassandra.concurrent.AbstractTracingAwareExecutorService$FutureTask.run(AbstractTracingAwareExecutorService.java:164)
>  [apache-cassandra-2.1.9.jar:2.1.9]
> at org.apache.cassandra.concurrent.SEPWorker.run(SEPWorker.java:105) 
> [apache-cassandra-2.1.9.jar:2.1.9]
> at java.lang.Thread.run(Thread.java:744) [na:1.8.0]



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org

[jira] [Updated] (CASSANDRA-10864) Dropped mutations high until cluster restart

[Jeff Jirsa (JIRA)]

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

Jeff Jirsa updated CASSANDRA-10864:
---
Labels:   (was: proposed-wontfix)

> Dropped mutations high until cluster restart
> 
>
> Key: CASSANDRA-10864
> URL: https://issues.apache.org/jira/browse/CASSANDRA-10864
> Project: Cassandra
>  Issue Type: Bug
>Reporter: Jeff Ferland
>Priority: Major
>
> Originally raised and investigated in 
> https://www.mail-archive.com/user@cassandra.apache.org/msg44586.html
> Cause is still unclear, but a rolling restart has on two occasions since been 
> performed to cope with dropped mutations and timed-out reads.
> Pattern is indicative of some kind of code quality issue possibly involving 
> locking operations. Stack flame graphs do not show a clear difference between 
> restarts.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org

[jira] [Updated] (CASSANDRA-7057) Add ability to adjust number of vnodes on a node

[Jeff Jirsa (JIRA)]

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

Jeff Jirsa updated CASSANDRA-7057:
--
Labels:   (was: proposed-wontfix)

> Add ability to adjust number of vnodes on a node
> 
>
> Key: CASSANDRA-7057
> URL: https://issues.apache.org/jira/browse/CASSANDRA-7057
> Project: Cassandra
>  Issue Type: Improvement
>  Components: Configuration
>Reporter: Michael Shuler
>Priority: Minor
>
> Currently, once a vnode server is configured with a num_tokens value, there 
> is no defined process to to change the number of vnodes a node is responsible 
> for.
> This could be useful for load adjustments when upgrading hardware in a 
> server, or adjusting the number of vnodes to affect node data balance.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org

[jira] [Updated] (CASSANDRA-6758) Measure data consistency in the cluster

[Jeff Jirsa (JIRA)]

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

Jeff Jirsa updated CASSANDRA-6758:
--
Labels:   (was: proposed-wontfix)

> Measure data consistency in the cluster
> ---
>
> Key: CASSANDRA-6758
> URL: https://issues.apache.org/jira/browse/CASSANDRA-6758
> Project: Cassandra
>  Issue Type: New Feature
>Reporter: Jimmy Mårdell
>Priority: Minor
>
> Running multi-DC Cassandra can be a challenge as the cluster easily tends to 
> get out-of-sync. We have been thinking it would be nice to measure how out of 
> sync a cluster is and expose those metrics somehow.
> One idea would be to just run the first half of the repair process and output 
> the result of the differencer. If you use Random or the Murmur3 partitioner, 
> it should be enough to calculate the merkle tree over a small subset of the 
> ring as the result can be extrapolated.
> This could be exposed in nodetool. Either a separate command or perhaps a 
> dry-run flag to repair?
> Not sure about the output format. I think it would be nice to have one value 
> ("% consistent"?) within a DC, and also one value for every pair of DC's 
> perhaps?



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org

[jira] [Resolved] (CASSANDRA-7057) Add ability to adjust number of vnodes on a node

[Jeff Jirsa (JIRA)]

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

Jeff Jirsa resolved CASSANDRA-7057.
---
Resolution: Won't Fix

Closing for now, as a lot of the foundation for this sorta disappeared, and 
nobody made an argument to keep it open. We can re-open later if someone 
decides it's useful.

> Add ability to adjust number of vnodes on a node
> 
>
> Key: CASSANDRA-7057
> URL: https://issues.apache.org/jira/browse/CASSANDRA-7057
> Project: Cassandra
>  Issue Type: Improvement
>  Components: Configuration
>Reporter: Michael Shuler
>Priority: Minor
>
> Currently, once a vnode server is configured with a num_tokens value, there 
> is no defined process to to change the number of vnodes a node is responsible 
> for.
> This could be useful for load adjustments when upgrading hardware in a 
> server, or adjusting the number of vnodes to affect node data balance.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org

[jira] [Updated] (CASSANDRA-7377) Should be an option to fail startup if corrupt SSTable found

[Jeff Jirsa (JIRA)]

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

Jeff Jirsa updated CASSANDRA-7377:
--
Labels:   (was: proposed-wontfix)

> Should be an option to fail startup if corrupt SSTable found
> 
>
> Key: CASSANDRA-7377
> URL: https://issues.apache.org/jira/browse/CASSANDRA-7377
> Project: Cassandra
>  Issue Type: Improvement
>Reporter: Richard Low
>Priority: Major
>
> We had a server that crashed and when it came back, some SSTables were 
> corrupted. Cassandra happily started, but we then realised the corrupt 
> SSTable contained some tombstones and a few keys were resurrected. This means 
> corruption on a single replica can bring back data even if you run repairs at 
> least every gc_grace.
> There should be an option, probably controlled by the disk failure policy, to 
> catch this and stop node startup.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org

[jira] [Resolved] (CASSANDRA-6758) Measure data consistency in the cluster

[Jeff Jirsa (JIRA)]

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

Jeff Jirsa resolved CASSANDRA-6758.
---
Resolution: Fixed

Calling this fixed, as the requirements are mostly done, just by other tickets. 

> Measure data consistency in the cluster
> ---
>
> Key: CASSANDRA-6758
> URL: https://issues.apache.org/jira/browse/CASSANDRA-6758
> Project: Cassandra
>  Issue Type: New Feature
>Reporter: Jimmy Mårdell
>Priority: Minor
>
> Running multi-DC Cassandra can be a challenge as the cluster easily tends to 
> get out-of-sync. We have been thinking it would be nice to measure how out of 
> sync a cluster is and expose those metrics somehow.
> One idea would be to just run the first half of the repair process and output 
> the result of the differencer. If you use Random or the Murmur3 partitioner, 
> it should be enough to calculate the merkle tree over a small subset of the 
> ring as the result can be extrapolated.
> This could be exposed in nodetool. Either a separate command or perhaps a 
> dry-run flag to repair?
> Not sure about the output format. I think it would be nice to have one value 
> ("% consistent"?) within a DC, and also one value for every pair of DC's 
> perhaps?



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org

[jira] [Resolved] (CASSANDRA-10173) Compaction isn't cleaning out tombstones between hint deliveries

[Jeff Jirsa (JIRA)]

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

Jeff Jirsa resolved CASSANDRA-10173.

Resolution: Won't Fix

Hints rewritten, nobody making an argument this needs to be fixed in 2.2. 
Closing.


> Compaction isn't cleaning out tombstones between hint deliveries
> 
>
> Key: CASSANDRA-10173
> URL: https://issues.apache.org/jira/browse/CASSANDRA-10173
> Project: Cassandra
>  Issue Type: Bug
>Reporter: Jonathan Ellis
>Priority: Major
>  Labels: proposed-wontfix
> Fix For: 2.2.x
>
> Attachments: system (3).log
>
>
> 3 node cluster, 100M writes.  Same scenario as 10172:
> Test Start: 00:00:00
> Node 1 Killed: 00:05:48
> Node 2 Killed: 00:13:33
> Node 1 Started: 00:24:20
> Node 2 Started: 00:32:23
> Test Done: 00:38:33
> Node 1 hints replay finished: 00:56:16
> Node 2 hints replay finished: 01:00:16
> Node 3 hints replay finished: 02:08:00
> Log attached.  Note the tombstone_failure_threshold errors.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org

[jira] [Resolved] (CASSANDRA-10864) Dropped mutations high until cluster restart

[Jeff Jirsa (JIRA)]

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

Jeff Jirsa resolved CASSANDRA-10864.

Resolution: Won't Fix

Closing as wont-fix; reopen if you can repro reliably. 

> Dropped mutations high until cluster restart
> 
>
> Key: CASSANDRA-10864
> URL: https://issues.apache.org/jira/browse/CASSANDRA-10864
> Project: Cassandra
>  Issue Type: Bug
>Reporter: Jeff Ferland
>Priority: Major
>  Labels: proposed-wontfix
>
> Originally raised and investigated in 
> https://www.mail-archive.com/user@cassandra.apache.org/msg44586.html
> Cause is still unclear, but a rolling restart has on two occasions since been 
> performed to cope with dropped mutations and timed-out reads.
> Pattern is indicative of some kind of code quality issue possibly involving 
> locking operations. Stack flame graphs do not show a clear difference between 
> restarts.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org

[jira] [Resolved] (CASSANDRA-10937) OOM on multiple nodes on write load (v. 3.0.0), problem also present on DSE-4.8.3, but there it survives more time

[Jeff Jirsa (JIRA)]

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

Jeff Jirsa resolved CASSANDRA-10937.

Resolution: Won't Fix

Closing as wont-fix; reopen if you can repro reliably. 

> OOM on multiple nodes on write load (v. 3.0.0), problem also present on 
> DSE-4.8.3, but there it survives more time
> --
>
> Key: CASSANDRA-10937
> URL: https://issues.apache.org/jira/browse/CASSANDRA-10937
> Project: Cassandra
>  Issue Type: Bug
> Environment: Cassandra : 3.0.0
> Installed as open archive, no connection to any OS specific installer.
> Java:
> Java(TM) SE Runtime Environment (build 1.8.0_65-b17)
> OS :
> Linux version 2.6.32-431.el6.x86_64 
> (mockbu...@x86-023.build.eng.bos.redhat.com) (gcc version 4.4.7 20120313 (Red 
> Hat 4.4.7-4) (GCC) ) #1 SMP Sun Nov 10 22:19:54 EST 2013
> We have:
> 8 guests ( Linux OS as above) on 2 (VMWare managed) physical hosts. Each 
> physical host keeps 4 guests.
> Physical host parameters(shared by all 4 guests):
> Model: HP ProLiant DL380 Gen9
> Intel(R) Xeon(R) CPU E5-2690 v3 @ 2.60GHz
> 46 logical processors.
> Hyperthreading - enabled
> Each guest assigned to have:
> 1 disk 300 Gb for seq. log (NOT SSD)
> 1 disk 4T for data (NOT SSD)
> 11 CPU cores
> Disks are local, not shared.
> Memory on each host -  24 Gb total.
> 8 (or 6, tested both) Gb - cassandra heap
> (lshw and cpuinfo attached in file test2.rar)
>Reporter: Peter Kovgan
>Priority: Critical
>  Labels: proposed-wontfix
> Attachments: cassandra-to-jack-krupansky.docx, gc-stat.txt, 
> more-logs.rar, some-heap-stats.rar, test2.rar, test3.rar, test4.rar, 
> test5.rar, test_2.1.rar, test_2.1_logs_older.rar, 
> test_2.1_restart_attempt_log.rar
>
>
> 8 cassandra nodes.
> Load test started with 4 clients(different and not equal machines), each 
> running 1000 threads.
> Each thread assigned in round-robin way to run one of 4 different inserts. 
> Consistency->ONE.
> I attach the full CQL schema of tables and the query of insert.
> Replication factor - 2:
> create keyspace OBLREPOSITORY_NY with replication = 
> {'class':'NetworkTopologyStrategy','NY':2};
> Initiall throughput is:
> 215.000  inserts /sec
> or
> 54Mb/sec, considering single insert size a bit larger than 256byte.
> Data:
> all fields(5-6) are short strings, except one is BLOB of 256 bytes.
> After about a 2-3 hours of work, I was forced to increase timeout from 2000 
> to 5000ms, for some requests failed for short timeout.
> Later on(after aprox. 12 hous of work) OOM happens on multiple nodes.
> (all failed nodes logs attached)
> I attach also java load client and instructions how set-up and use 
> it.(test2.rar)
> Update:
> Later on test repeated with lesser load (10 mes/sec) with more relaxed 
> CPU (idle 25%), with only 2 test clients, but anyway test failed.
> Update:
> DSE-4.8.3 also failed on OOM (3 nodes from 8), but here it survived 48 hours, 
> not 10-12.
> Attachments:
> test2.rar -contains most of material
> more-logs.rar - contains additional nodes logs



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org

[jira] [Commented] (CASSANDRA-14233) nodetool tablestats/cfstats output has inconsistent formatting for latency

[Samuel Roberts (JIRA)]

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

Samuel Roberts commented on CASSANDRA-14233:


Ok, I've done it against trunk.

Also, Gary Stewart from NL wants the world to know that he was the one who 
noticed the inconstancy, so let that be recorded here for posterity.

> nodetool tablestats/cfstats output has inconsistent formatting for latency
> --
>
> Key: CASSANDRA-14233
> URL: https://issues.apache.org/jira/browse/CASSANDRA-14233
> Project: Cassandra
>  Issue Type: Bug
>Reporter: Samuel Roberts
>Assignee: Samuel Roberts
>Priority: Trivial
>   Original Estimate: 10m
>  Remaining Estimate: 10m
>
> Latencies are reported at keyspace level with `ms.` and at table level with 
> `ms`.
> There should be no trailing `.` as it is not a sentence and `.` is not part 
> of the abbreviation.
> This is also present in 2.x with `nodetool cfstats`.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org

[jira] [Resolved] (CASSANDRA-11171) conditional update without paxos

[Jeff Jirsa (JIRA)]

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

Jeff Jirsa resolved CASSANDRA-11171.

Resolution: Won't Fix

Lot of opinions that this won't happen, and nobody arguing that it should. 
Re-open if you have a patch, or a compelling argument it should happen. 

> conditional update without paxos
> 
>
> Key: CASSANDRA-11171
> URL: https://issues.apache.org/jira/browse/CASSANDRA-11171
> Project: Cassandra
>  Issue Type: Wish
>Reporter: stuart
>Priority: Minor
>  Labels: proposed-wontfix
>
> I realise that currently conditional updates use lightweight transactions to 
> provide an atomic check and set operation but that this comes at a non 
> trivial performance cost. I have a solution where synchronised access is 
> ensured by an external mechanism therefore I don't think paxos would be 
> required. It would be nice to be able to run an update command or script that 
> could conditionally update without the performance hit. Currently I'd have to 
> retrieve each row first at the application level before deciding whether or 
> not to perform the update. Would it be possible to add a switch for the 
> conditional updates to turn paxos on or off? Thanks.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org

[jira] [Updated] (CASSANDRA-11460) memory leak

[Jeff Jirsa (JIRA)]

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

Jeff Jirsa updated CASSANDRA-11460:
---
Resolution: Won't Fix
Status: Resolved  (was: Awaiting Feedback)

Closing as wont-fix; reopen if you can repro reliably. 

> memory leak
> ---
>
> Key: CASSANDRA-11460
> URL: https://issues.apache.org/jira/browse/CASSANDRA-11460
> Project: Cassandra
>  Issue Type: Bug
>Reporter: stone
>Priority: Critical
>  Labels: proposed-wontfix
> Attachments: aaa.jpg
>
>
> env:
> cassandra3.3
> jdk8
> 8G Ram
> so set
> MAX_HEAP_SIZE="2G"
> HEAP_NEWSIZE="400M"
> 1.met same problem about this:
> https://issues.apache.org/jira/browse/CASSANDRA-9549
> I confuse about that this was fixed in release 3.3 according this page:
> https://github.com/apache/cassandra/blob/trunk/CHANGES.txt
> so I change to 3.4,and also have  found this problem again 
> I think this fix should be included in 3.3.3.4
> can you explain about this?
> 2.our write rate exceed the value that our cassandra env can support,
> but i think it should descrese the write rate,or block.consumer the writed 
> data,keep the memory down,then go on writing,not cause out-of-memory instead.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org

[jira] [Resolved] (CASSANDRA-13093) 2.2.8 Node goes down with MUTATION messages were dropped in last 5000 ms: 29 for internal timeout

[Jeff Jirsa (JIRA)]

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

Jeff Jirsa resolved CASSANDRA-13093.

Resolution: Won't Fix

Closing as wont-fix; reopen if you can repro reliably. 

> 2.2.8 Node goes down with MUTATION messages were dropped in last 5000 ms: 29 
> for internal timeout
> -
>
> Key: CASSANDRA-13093
> URL: https://issues.apache.org/jira/browse/CASSANDRA-13093
> Project: Cassandra
>  Issue Type: Bug
>  Components: Core
> Environment: 2.2.8 Cassandra on 4 Nodes with Red Hat Linux 6.2 64 Bit
>Reporter: sutanu das
>Priority: Critical
>  Labels: proposed-wontfix
>
> Issue: 1st Node of 4 Node in Cluster keeps aborting (jvm crashing) with 
> following messages:
> - ReadTimeoutException: Operation timed out - received only 0 responses
> - MUTATION messages were dropped in last 5000 ms: 29 for internal timeout and 
> 0 for cross node timeout
> - Spark Jobs getting Q'd up when opening Channels, followed up Read Time Outs:
>   ERROR [SharedPool-Worker-207] 2017-01-03 16:39:00,493 Message.java:611 
> - Unexpected exception during request; channel = [id: 0xd0b0d36d, 
> /216.12.229.180:41896 :> /172.17.30.47:9042]
>   java.lang.RuntimeException: 
> org.apache.cassandra.exceptions.ReadTimeoutException: Operation timed out - 
> received only 0 responses.
>   
> What has been done so far?
>  - Host Reboot node 01
>  - Mutiple C* restarts
>  - Increased read_request_timeout_in_ms from 1 to 5
>  - Increased request_timeout_in_ms from 1 to 5
>  - Changed following:
>   concurrent_reads: 128
>   concurrent_writes: 128
>   concurrent_counter_writes: 128
>  - Upgrade to 2.2.8 - All Nodes Sync with 2.2.8
>  - All nodes have same Pass Auth Scheme (Node 03 was a mis-match and was 
> fixed)
>   - authenticator: org.apache.cassandra.auth.PasswordAuthenticator
>   - authorizer: org.apache.cassandra.auth.CassandraAuthorizer
> Full exception stack:
> DEBUG [SharedPool-Worker-10] 2017-01-03 16:32:43,983 StorageProxy.java:1898 - 
> Range slice timeout; received 0 of 1 responses for range 1 of 1
> INFO  [Service Thread] 2017-01-03 16:32:43,983 GCInspector.java:284 - ParNew 
> GC in 247ms.  CMS Old Gen: 3768220776 -> 3996971216; Par Eden Space: 
> 1718091776 -> 0;
> INFO  [Service Thread] 2017-01-03 16:32:43,983 StatusLogger.java:52 - Pool 
> NameActive   Pending  Completed   Blocked  All Time 
> Blocked
> DEBUG [SharedPool-Worker-26] 2017-01-03 16:32:43,984 
> FileCacheService.java:102 - Evicting cold readers for 
> /cassandra/data/system_auth/roles-5bc52802de2535edaeab188eecebb090/la-51-big-Data.db
> DEBUG [SharedPool-Worker-28] 2017-01-03 16:32:43,986 
> AbstractQueryPager.java:89 - Got empty set of rows, considering pager 
> exhausted
> INFO  [ScheduledTasks:1] 2017-01-03 16:39:00,473 MessagingService.java:946 - 
> RANGE_SLICE messages were dropped in last 5000 ms: 2 for internal timeout and 
> 0 for cross node timeout
> INFO  [Service Thread] 2017-01-03 16:39:00,476 StatusLogger.java:106 - 
> sales.airwave_dwell_time_det_hr 0,0
> ERROR [SharedPool-Worker-207] 2017-01-03 16:39:00,493 Message.java:611 - 
> Unexpected exception during request; channel = [id: 0xd0b0d36d, 
> /216.12.229.180:41896 :> /172.17.30.47:9042]
> java.lang.RuntimeException: 
> org.apache.cassandra.exceptions.ReadTimeoutException: Operation timed out - 
> received only 0 responses.
> at 
> org.apache.cassandra.auth.CassandraRoleManager.getRole(CassandraRoleManager.java:497)
>  ~[apache-cassandra-2.2.8.jar:2.2.8]
> at 
> org.apache.cassandra.auth.CassandraRoleManager.canLogin(CassandraRoleManager.java:306)
>  ~[apache-cassandra-2.2.8.jar:2.2.8]
> at 
> org.apache.cassandra.service.ClientState.login(ClientState.java:269) 
> ~[apache-cassandra-2.2.8.jar:2.2.8]
> at 
> org.apache.cassandra.transport.messages.AuthResponse.execute(AuthResponse.java:79)
>  ~[apache-cassandra-2.2.8.jar:2.2.8]
> at 
> org.apache.cassandra.transport.Message$Dispatcher.channelRead0(Message.java:507)
>  [apache-cassandra-2.2.8.jar:2.2.8]
> at 
> org.apache.cassandra.transport.Message$Dispatcher.channelRead0(Message.java:401)
>  [apache-cassandra-2.2.8.jar:2.2.8]
> at 
> io.netty.channel.SimpleChannelInboundHandler.channelRead(SimpleChannelInboundHandler.java:105)
>  [netty-all-4.0.23.Final.jar:4.0.23.Final]
> at 
> io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:333)
>  [netty-all-4.0.23.Final.jar:4.0.23.Final]
> at 
> io.netty.channel.AbstractChannelHandlerContext.access$700(AbstractChannelHandlerContext.java:32)
>  [netty-all-4.0.23.Final.jar:4.0.23.Final]
> at 

[jira] [Resolved] (CASSANDRA-11821) nodetool cfhistograms throws java.lang.ArrayIndexOutOfBoundsException and reset the cfhistograms

[Jeff Jirsa (JIRA)]

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

Jeff Jirsa resolved CASSANDRA-11821.

Resolution: Won't Fix

Closing as wont-fix; reopen if you can repro reliably on a supported version. 

> nodetool cfhistograms throws java.lang.ArrayIndexOutOfBoundsException and 
> reset the cfhistograms
> 
>
> Key: CASSANDRA-11821
> URL: https://issues.apache.org/jira/browse/CASSANDRA-11821
> Project: Cassandra
>  Issue Type: Bug
>  Components: Tools
> Environment: 2.0.17, rhel6.4
>Reporter: Benoit Perroud
>Priority: Minor
>  Labels: proposed-wontfix
>
> I had nodes running for a decent amount of time (like 3 months).
> {code}
> nodetool cfhistograms keyspace table
> {code}
> did throw and {{ArrayIndexOutOfBoundsException}} in the read latency section:
> {code}
> Read Latency (microseconds)
> Exception in thread "main" java.lang.ArrayIndexOutOfBoundsException: 90
>   at org.apache.cassandra.tools.NodeCmd.printHistogram(NodeCmd.java:1086)
>   at 
> org.apache.cassandra.tools.NodeCmd.printCfHistograms(NodeCmd.java:1138)
>   at org.apache.cassandra.tools.NodeCmd.main(NodeCmd.java:1472)
> {code}
> Surprisingly, the running the same cmd a second time did succeeded, but the 
> histograms seem to be reset:
> first call:
> {code}
> SSTables per Read
>1 sstables: 183026
>2 sstables: 176538
>3 sstables: 49159
>4 sstables: 23034
>5 sstables: 16380
> ...
> Write Latency (microseconds)
>   3 us: 4
>   4 us: 33
>   5 us: 237
>   6 us: 1193
>   7 us: 4055
>   8 us: 14357
>  10 us: 146728
>  12 us: 565588
>  14 us: 1907616
>  17 us: 8468503
>  20 us: 16218034
> ...
> {code}
> After:
> {code}
> SSTables per Read
> 2 sstables: 52
> 3 sstables: 4
> Write Latency (microseconds)
>   6 us: 1
>   7 us: 3
>   8 us: 5
>  10 us: 53
>  12 us: 133
>  14 us: 379
>  17 us: 1190
>  20 us: 1605
> {code}
> I didn't find anything on the logs, and I wasn't able to have the exception 
> popping out more than once per servers.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org