[jira] [Commented] (CASSANDRA-11866) nodetool repair does not obey the column family parameter when -st and -et are provided (subrange repair)

[sankalp kohli (JIRA)]

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

sankalp kohli commented on CASSANDRA-11866:
---

We should add a Dtest for this if possible. 

> nodetool repair does not obey the column family parameter when -st and -et 
> are provided (subrange repair)
> -
>
> Key: CASSANDRA-11866
> URL: https://issues.apache.org/jira/browse/CASSANDRA-11866
> Project: Cassandra
>  Issue Type: Bug
>  Components: Tools
> Environment: Red Hat Enterprise Linux Server release 6.7 (Santiago) 
> x86_64
>Reporter: Shiva Venkateswaran
>  Labels: newbie
> Fix For: 2.1.x
>
> Attachments: 11866-2.1.txt
>
>
> Command 1: Repairs all the CFs in ADL_GLOBAL keyspace and ignores the 
> parameter AssetModifyTimes_data used to restrict the CFs
> Executing: /aladdin/local/apps/apache-cassandra-2.1.8a/bin/nodetool -h 
> localhost -p 7199 -u user-pw ** repair ADL_GLOBAL AssetModifyTimes_data 
> -st 205279477618143669 -et 230991685737746901 -par
> [2016-05-20 17:31:39,116] Starting repair command #9, repairing 1 ranges for 
> keyspace ADL_GLOBAL (parallelism=PARALLEL, full=true)
> [2016-05-20 17:32:21,568] Repair session 3cae2530-1ed2-11e6-b490-d9df6932c7cf 
> for range (205279477618143669,230991685737746901] finished
> Command 2: Repairs all the CFs in ADL_GLOBAL keyspace and ignores the 
> parameter AssetModifyTimes_data used to restrict the CFs
> Executing: /aladdin/local/apps/apache-cassandra-2.1.8a/bin/nodetool -h 
> localhost -p 7199 -u controlRole -pw ** repair -st 205279477618143669 -et 
> 230991685737746901 -par -- ADL_GLOBAL AssetModifyTimes_data
> [2016-05-20 17:36:34,473] Starting repair command #10, repairing 1 ranges for 
> keyspace ADL_GLOBAL (parallelism=PARALLEL, full=true)
> [2016-05-20 17:37:15,365] Repair session ecb996d0-1ed2-11e6-b490-d9df6932c7cf 
> for range (205279477618143669,230991685737746901] finished
> [2016-05-20 17:37:15,365] Repair command #10 finished
> Command 3: Repairs only the CF ADL3Test1_data in keyspace ADL_GLOBAL
> Executing: /aladdin/local/apps/apache-cassandra-2.1.8a/bin/nodetool -h 
> localhost -p 7199 -u controlRole -pw ** repair -- ADL_GLOBAL 
> ADL3Test1_data
> [2016-05-20 17:38:35,781] Starting repair command #11, repairing 1043 ranges 
> for keyspace ADL_GLOBAL (parallelism=SEQUENTIAL, full=true)
> [2016-05-20 17:42:32,682] Repair session 3c8af050-1ed3-11e6-b490-d9df6932c7cf 
> for range (6241639152751626129,6241693909092643958] finished
> [2016-05-20 17:42:32,683] Repair session 3caf1a20-1ed3-11e6-b490-d9df6932c7cf 
> for range (-7096993048358106082,-7095000706885780850] finished
> [2016-05-20 17:42:32,683] Repair session 3ccfc180-1ed3-11e6-b490-d9df6932c7cf 
> for range (-7218939248114487080,-7218289345961492809] finished
> [2016-05-20 17:42:32,683] Repair session 3cf21690-1ed3-11e6-b490-d9df6932c7cf 
> for range (-5244794756638190874,-5190307341355030282] finished
> [2016-05-20 17:42:32,683] Repair session 3d126fd0-1ed3-11e6-b490-d9df6932c7cf 
> for range (3551629701277971766,321736534916502] finished
> [2016-05-20 17:42:32,683] Repair session 3d32f020-1ed3-11e6-b490-d9df6932c7cf 
> for range (-8139355591560661944,-8127928369093576603] finished
> [2016-05-20 17:42:32,683] Repair session 3d537070-1ed3-11e6-b490-d9df6932c7cf 
> for range (7098010153980465751,7100863011896759020] finished
> [2016-05-20 17:42:32,683] Repair session 3d73f0c0-1ed3-11e6-b490-d9df6932c7cf 
> for range (1004538726866173536,1008586133746764703] finished
> [2016-05-20 17:42:32,683] Repair session 3d947110-1ed3-11e6-b490-d9df6932c7cf 
> for range (5770817093573726645,5771418910784831587] finished
> .
> .
> .
> [2016-05-20 17:42:32,732] Repair command #11 finished



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (CASSANDRA-9318) Bound the number of in-flight requests at the coordinator

[Stefania (JIRA)]

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

Stefania commented on CASSANDRA-9318:
-

The current implementation is still not that generic:

* If we removed {{MessagingService.getBackPressurePerHost()}}, which doesn't 
seem to be used, then we can at least remove {{getBackPressureRateLimit}} and 
{{getHost}} from {{BackPressureState}}, leaving it with only {{onMessageSent}} 
and {{onMessageReceived}}.

* We can also consider moving the states internally to the strategy, at the 
cost of an O(1) lookup, or at least encapsulate 
{{MessagingService.updateBackPressureState}} so that the states become opaque. 
Eventually we could have an update type (message received, memory threshold 
reached, etc) and so that strategies can only deal with the type of updates 
they require.

* The apply method doesn't leave much room in terms of what to do, we can 
basically sleep after a set of replicas has been selected by SP or throw an 
exception. We are also applying backpressure _after sending the messages_, is 
this intentional?

Some other nits:

* In RateBasedBackPressure some fields can have a package based access rather 
than public/protected and the static in the flow enum declaration is redundant.

* We may want to add the flow to the logger.info message "Initialized 
back-pressure..." in the constructor of RateBasedBackPressure.

* In {{RateBasedBackPressure.apply(Iterable 
states)}}, casting the lambda to {{Comparator}} is 
unnecessary.

* In the very same comparator lambda, if 2 states are not equal but have the 
exact same rate limit, then I assume it is intentional to compare them by hash 
code in order to get a stable sort? If so we should add a comment since tree 
set only requires the items to be mutually comparable and therefore returning 
zero would have been allowed as well I believe.

* {{RateBasedBackPressureState}} can be package local, {{windowSize}} can be 
private and {{getLastAcquire()}} can be package local.

* {{sortOrder}} in {{MockBackPressureState}} is not used.

* Several trailing spaces.

One 
[failure|https://cassci.datastax.com/view/Dev/view/sbtourist/job/sbtourist-CASSANDRA-9318-3.0-dtest/lastCompletedBuild/testReport/cqlsh_tests.cqlsh_copy_tests/CqlshCopyTest/test_bulk_round_trip_with_timeouts_2/]
 that needs to be looked at:

{code}
ERROR [SharedPool-Worker-1] 2016-07-19 12:40:38,257 QueryMessage.java:128 - 
Unexpected error during query
java.lang.IllegalArgumentException: Size should be greater than precision.
at 
com.google.common.base.Preconditions.checkArgument(Preconditions.java:122) 
~[guava-18.0.jar:na]
at 
org.apache.cassandra.utils.SlidingTimeRate.(SlidingTimeRate.java:51) 
~[main/:na]
at 
org.apache.cassandra.net.RateBasedBackPressureState.(RateBasedBackPressureState.java:65)
 ~[main/:na]
at 
org.apache.cassandra.net.RateBasedBackPressure.newState(RateBasedBackPressure.java:205)
 ~[main/:na]
at 
org.apache.cassandra.net.RateBasedBackPressure.newState(RateBasedBackPressure.java:43)
 ~[main/:na]
at 
org.apache.cassandra.net.MessagingService.getConnectionPool(MessagingService.java:649)
 ~[main/:na]
at 
org.apache.cassandra.net.MessagingService.getConnection(MessagingService.java:663)
 ~[main/:na]
at 
org.apache.cassandra.net.MessagingService.sendOneWay(MessagingService.java:812) 
~[main/:na]
at 
org.apache.cassandra.net.MessagingService.sendRR(MessagingService.java:755) 
~[main/:na]
at 
org.apache.cassandra.net.MessagingService.sendRR(MessagingService.java:733) 
~[main/:na]
at 
org.apache.cassandra.service.StorageProxy.truncateBlocking(StorageProxy.java:2380)
 ~[main/:na]
at 
org.apache.cassandra.cql3.statements.TruncateStatement.execute(TruncateStatement.java:71)
 ~[main/:na]
at 
org.apache.cassandra.cql3.QueryProcessor.processStatement(QueryProcessor.java:206)
 ~[main/:na]
{code}

bq. Metrics can be added in this ticket once we settle on the core algorithm, 
but then yes any reporting mechanism to clients should be probably dealt with 
separately as it would probably involve changes to the native protocol (and I'm 
not sure what's the usual procedure in such case).

Let's test the strategy first, then metrics can be added later on. Let's not 
worry about native protocol changes for now, since we are no longer throwing 
exceptions.

bq. Regarding the memory-threshold strategy, I would like to stress once again 
the fact it's a coordinator-only back-pressure mechanism which wouldn't 
directly benefit replicas; also, Ariel Weisberg showed in his tests that such 
strategy isn't even needed given the local hints back-pressure/overflowing 
mechanisms already implemented. So my vote goes against it, but if you/others 
really want it, I'm perfectly fine implementing it, but it will have to be in 
this ticket, as it requires some 

[jira] [Updated] (CASSANDRA-12214) cqlshlib test failure: cqlshlib.test.remove_test_db

[Stefania (JIRA)]

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

Stefania updated CASSANDRA-12214:
-
   Resolution: Fixed
Fix Version/s: 3.9
   3.0.9
   2.2.8
   Status: Resolved  (was: Patch Available)

>  cqlshlib test failure: cqlshlib.test.remove_test_db
> 
>
> Key: CASSANDRA-12214
> URL: https://issues.apache.org/jira/browse/CASSANDRA-12214
> Project: Cassandra
>  Issue Type: Bug
>  Components: Testing
>Reporter: Craig Kodman
>Assignee: Stefania
>  Labels: cqlsh
> Fix For: 2.2.8, 3.0.9, 3.9
>
>
> [~Stefania]  
> http://cassci.datastax.com/job/cassandra-3.9_cqlsh_tests/lastCompletedBuild/testReport/
> Hello, these three tests are failing:
> cqlshlib.test.remove_test_db
> cqlshlib.test.test_cqlsh_completion.TestCqlshCompletion.test_complete_in_create_columnfamily
> cqlshlib.test.test_cqlsh_completion.TestCqlshCompletion.test_complete_in_create_table
> Can you look at them, please?  Thank you!



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (CASSANDRA-12214) cqlshlib test failure: cqlshlib.test.remove_test_db

[Stefania (JIRA)]

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

Stefania updated CASSANDRA-12214:
-
Component/s: Testing

>  cqlshlib test failure: cqlshlib.test.remove_test_db
> 
>
> Key: CASSANDRA-12214
> URL: https://issues.apache.org/jira/browse/CASSANDRA-12214
> Project: Cassandra
>  Issue Type: Bug
>  Components: Testing
>Reporter: Craig Kodman
>Assignee: Stefania
>  Labels: cqlsh
> Fix For: 2.2.8, 3.0.9, 3.9
>
>
> [~Stefania]  
> http://cassci.datastax.com/job/cassandra-3.9_cqlsh_tests/lastCompletedBuild/testReport/
> Hello, these three tests are failing:
> cqlshlib.test.remove_test_db
> cqlshlib.test.test_cqlsh_completion.TestCqlshCompletion.test_complete_in_create_columnfamily
> cqlshlib.test.test_cqlsh_completion.TestCqlshCompletion.test_complete_in_create_table
> Can you look at them, please?  Thank you!



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (CASSANDRA-12214) cqlshlib test failure: cqlshlib.test.remove_test_db

[Stefania (JIRA)]

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

Stefania commented on CASSANDRA-12214:
--

Thank you for the review.

You're correct, the change at that line is not related but it is intentional as 
it seems a much safer approach.

Committed to 2.2 as e8186fe390073f5d7ea11057c5bc842db86d95d2 and merged upwards.

>  cqlshlib test failure: cqlshlib.test.remove_test_db
> 
>
> Key: CASSANDRA-12214
> URL: https://issues.apache.org/jira/browse/CASSANDRA-12214
> Project: Cassandra
>  Issue Type: Bug
>Reporter: Craig Kodman
>Assignee: Stefania
>  Labels: cqlsh
>
> [~Stefania]  
> http://cassci.datastax.com/job/cassandra-3.9_cqlsh_tests/lastCompletedBuild/testReport/
> Hello, these three tests are failing:
> cqlshlib.test.remove_test_db
> cqlshlib.test.test_cqlsh_completion.TestCqlshCompletion.test_complete_in_create_columnfamily
> cqlshlib.test.test_cqlsh_completion.TestCqlshCompletion.test_complete_in_create_table
> Can you look at them, please?  Thank you!



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[01/10] cassandra git commit: Fixed cqlshlib.test.remove_test_db

[stefania]

Repository: cassandra
Updated Branches:
  refs/heads/cassandra-2.2 f0d1d75eb -> e8186fe39
  refs/heads/cassandra-3.0 0297cbe97 -> dce453741
  refs/heads/cassandra-3.9 4bd4be867 -> 8df6d4d4c
  refs/heads/trunk cc582855e -> f129dea86


Fixed cqlshlib.test.remove_test_db

patch by Stefania Alborghetti; reviewed by Philip Thompson for CASSANDRA-12214


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

Branch: refs/heads/cassandra-2.2
Commit: e8186fe390073f5d7ea11057c5bc842db86d95d2
Parents: f0d1d75
Author: Stefania Alborghetti 
Authored: Tue Jul 19 11:15:46 2016 +0800
Committer: Stefania Alborghetti 
Committed: Wed Jul 20 09:54:53 2016 +0800

--
 CHANGES.txt  |  1 +
 pylib/cqlshlib/test/__init__.py  |  6 +++---
 pylib/cqlshlib/test/cassconnect.py   | 22 +++---
 pylib/cqlshlib/test/test_cqlsh_output.py | 14 +++---
 4 files changed, 22 insertions(+), 21 deletions(-)
--


http://git-wip-us.apache.org/repos/asf/cassandra/blob/e8186fe3/CHANGES.txt
--
diff --git a/CHANGES.txt b/CHANGES.txt
index 837c3fb..ffd92b5 100644
--- a/CHANGES.txt
+++ b/CHANGES.txt
@@ -1,4 +1,5 @@
 2.2.8
+ * Fixed cqlshlib.test.remove_test_db (CASSANDRA-12214)
  * Synchronize ThriftServer::stop() (CASSANDRA-12105)
  * Use dedicated thread for JMX notifications (CASSANDRA-12146)
  * NPE when trying to remove purgable tombstones from result (CASSANDRA-12143)

http://git-wip-us.apache.org/repos/asf/cassandra/blob/e8186fe3/pylib/cqlshlib/test/__init__.py
--
diff --git a/pylib/cqlshlib/test/__init__.py b/pylib/cqlshlib/test/__init__.py
index 31f66f3..ba8f373 100644
--- a/pylib/cqlshlib/test/__init__.py
+++ b/pylib/cqlshlib/test/__init__.py
@@ -14,7 +14,7 @@
 # See the License for the specific language governing permissions and
 # limitations under the License.
 
-from .cassconnect import create_test_db, remove_test_db
+from .cassconnect import create_db, remove_db
 
-setUp = create_test_db
-tearDown = remove_test_db
+setUp = create_db
+tearDown = remove_db

http://git-wip-us.apache.org/repos/asf/cassandra/blob/e8186fe3/pylib/cqlshlib/test/cassconnect.py
--
diff --git a/pylib/cqlshlib/test/cassconnect.py 
b/pylib/cqlshlib/test/cassconnect.py
index 94910a6..4a1311e 100644
--- a/pylib/cqlshlib/test/cassconnect.py
+++ b/pylib/cqlshlib/test/cassconnect.py
@@ -37,15 +37,15 @@ def get_cassandra_cursor(cql_version=cqlsh.DEFAULT_CQLVER):
 
 TEST_KEYSPACES_CREATED = []
 
-def get_test_keyspace():
-return TEST_KEYSPACES_CREATED[-1]
+def get_keyspace():
+return None if len(TEST_KEYSPACES_CREATED) == 0 else 
TEST_KEYSPACES_CREATED[-1]
 
-def make_test_ks_name():
+def make_ks_name():
 # abuse mktemp to get a quick random-ish name
 return os.path.basename(tempfile.mktemp(prefix='CqlshTests_'))
 
-def create_test_keyspace(cursor):
-ksname = make_test_ks_name()
+def create_keyspace(cursor):
+ksname = make_ks_name()
 qksname = quote_name(ksname)
 cursor.execute('''
 CREATE KEYSPACE %s WITH replication =
@@ -72,13 +72,13 @@ def execute_cql_file(cursor, fname):
 with open(fname) as f:
 return execute_cql_commands(cursor, f.read())
 
-def create_test_db():
+def create_db():
 with cassandra_cursor(ks=None) as c:
-k = create_test_keyspace(c)
+k = create_keyspace(c)
 execute_cql_file(c, test_keyspace_init)
 return k
 
-def remove_test_db():
+def remove_db():
 with cassandra_cursor(ks=None) as c:
 c.execute('DROP KEYSPACE %s' % 
quote_name(TEST_KEYSPACES_CREATED.pop(-1)))
 
@@ -112,7 +112,7 @@ def cassandra_cursor(cql_version=None, ks=''):
 """
 
 if ks == '':
-ks = get_test_keyspace()
+ks = get_keyspace()
 conn = get_cassandra_connection(cql_version=cql_version)
 try:
 c = conn.connect(ks)
@@ -131,10 +131,10 @@ def testrun_cqlsh(keyspace=DEFAULTVAL, **kwargs):
 # use a positive default sentinel so that keyspace=None can be used
 # to override the default behavior
 if keyspace is DEFAULTVAL:
-keyspace = get_test_keyspace()
+keyspace = get_keyspace()
 return run_cqlsh(keyspace=keyspace, **kwargs)
 
 def testcall_cqlsh(keyspace=None, **kwargs):
 if keyspace is None:
-keyspace = get_test_keyspace()
+keyspace = get_keyspace()
 return call_cqlsh(keyspace=keyspace, **kwargs)

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

[stefania]

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/dce45374
Tree: http://git-wip-us.apache.org/repos/asf/cassandra/tree/dce45374
Diff: http://git-wip-us.apache.org/repos/asf/cassandra/diff/dce45374

Branch: refs/heads/cassandra-3.0
Commit: dce4537410d66a3cbd24b2e581737b849e011917
Parents: 0297cbe e8186fe
Author: Stefania Alborghetti 
Authored: Wed Jul 20 09:56:12 2016 +0800
Committer: Stefania Alborghetti 
Committed: Wed Jul 20 09:56:12 2016 +0800

--
 CHANGES.txt  |  1 +
 pylib/cqlshlib/test/__init__.py  |  6 +++---
 pylib/cqlshlib/test/cassconnect.py   | 22 +++---
 pylib/cqlshlib/test/test_cqlsh_output.py | 14 +++---
 4 files changed, 22 insertions(+), 21 deletions(-)
--


http://git-wip-us.apache.org/repos/asf/cassandra/blob/dce45374/CHANGES.txt
--
diff --cc CHANGES.txt
index f205e0b,ffd92b5..739c095
--- a/CHANGES.txt
+++ b/CHANGES.txt
@@@ -1,21 -1,8 +1,22 @@@
 -2.2.8
 +3.0.9
 + * Fix problem with undeleteable rows on upgrade to new sstable format 
(CASSANDRA-12144)
 + * Fix paging logic for deleted partitions with static columns 
(CASSANDRA-12107)
 + * Wait until the message is being send to decide which serializer must be 
used (CASSANDRA-11393)
 + * Fix migration of static thrift column names with non-text comparators 
(CASSANDRA-12147)
 + * Fix upgrading sparse tables that are incorrectly marked as dense 
(CASSANDRA-11315)
 + * Fix reverse queries ignoring range tombstones (CASSANDRA-11733)
 + * Avoid potential race when rebuilding CFMetaData (CASSANDRA-12098)
 + * Avoid missing sstables when getting the canonical sstables 
(CASSANDRA-11996)
 + * Always select the live sstables when getting sstables in bounds 
(CASSANDRA-11944)
 + * Fix column ordering of results with static columns for Thrift requests in
 +   a mixed 2.x/3.x cluster, also fix potential non-resolved duplication of
 +   those static columns in query results (CASSANDRA-12123)
 + * Avoid digest mismatch with empty but static rows (CASSANDRA-12090)
 + * Fix EOF exception when altering column type (CASSANDRA-11820)
 +Merged from 2.2:
+  * Fixed cqlshlib.test.remove_test_db (CASSANDRA-12214)
   * Synchronize ThriftServer::stop() (CASSANDRA-12105)
   * Use dedicated thread for JMX notifications (CASSANDRA-12146)
 - * NPE when trying to remove purgable tombstones from result (CASSANDRA-12143)
   * Improve streaming synchronization and fault tolerance (CASSANDRA-11414)
   * MemoryUtil.getShort() should return an unsigned short also for 
architectures not supporting unaligned memory accesses (CASSANDRA-11973)
  Merged from 2.1:

http://git-wip-us.apache.org/repos/asf/cassandra/blob/dce45374/pylib/cqlshlib/test/test_cqlsh_output.py
--
diff --cc pylib/cqlshlib/test/test_cqlsh_output.py
index f867312,60699f3..85ce626
--- a/pylib/cqlshlib/test/test_cqlsh_output.py
+++ b/pylib/cqlshlib/test/test_cqlsh_output.py
@@@ -631,9 -630,9 +631,9 @@@ class TestCqlshOutput(BaseTestCase)
  AND memtable_flush_period_in_ms = 0
  AND min_index_interval = 128
  AND read_repair_chance = 0.0
 -AND speculative_retry = '99.0PERCENTILE';
 +AND speculative_retry = '99PERCENTILE';
  
- """ % quote_name(get_test_keyspace()))
+ """ % quote_name(get_keyspace()))
  
  with testrun_cqlsh(tty=True, cqlver=cqlsh.DEFAULT_CQLVER) as c:
  for cmdword in ('describe table', 'desc columnfamily'):

[08/10] cassandra git commit: Merge branch 'cassandra-3.0' into cassandra-3.9

[stefania]

Merge branch 'cassandra-3.0' into cassandra-3.9


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

Branch: refs/heads/cassandra-3.9
Commit: 8df6d4d4c60f865a09a93ff678ea5f6417465c29
Parents: 4bd4be8 dce4537
Author: Stefania Alborghetti 
Authored: Wed Jul 20 09:58:14 2016 +0800
Committer: Stefania Alborghetti 
Committed: Wed Jul 20 09:58:40 2016 +0800

--
 CHANGES.txt  |  2 ++
 pylib/cqlshlib/test/__init__.py  |  6 +++---
 pylib/cqlshlib/test/cassconnect.py   | 22 +++---
 pylib/cqlshlib/test/test_cqlsh_output.py | 14 +++---
 4 files changed, 23 insertions(+), 21 deletions(-)
--


http://git-wip-us.apache.org/repos/asf/cassandra/blob/8df6d4d4/CHANGES.txt
--
diff --cc CHANGES.txt
index 780ea96,739c095..dac46ab
--- a/CHANGES.txt
+++ b/CHANGES.txt
@@@ -1,36 -1,5 +1,38 @@@
 -3.0.9
 +3.9
 +Merged from 3.0:
   * Fix problem with undeleteable rows on upgrade to new sstable format 
(CASSANDRA-12144)
++Merged from 2.2:
++ * Fixed cqlshlib.test.remove_test_db (CASSANDRA-12214)
 +
 +3.8
 + * Fix hdr logging for single operation workloads (CASSANDRA-12145)
 + * Fix SASI PREFIX search in CONTAINS mode with partial terms 
(CASSANDRA-12073)
 + * Increase size of flushExecutor thread pool (CASSANDRA-12071)
 + * Partial revert of CASSANDRA-11971, cannot recycle buffer in 
SP.sendMessagesToNonlocalDC (CASSANDRA-11950)
 + * Upgrade netty to 4.0.39 (CASSANDRA-12032, CASSANDRA-12034)
 + * Improve details in compaction log message (CASSANDRA-12080)
 + * Allow unset values in CQLSSTableWriter (CASSANDRA-11911)
 + * Chunk cache to request compressor-compatible buffers if pool space is 
exhausted (CASSANDRA-11993)
 + * Remove DatabaseDescriptor dependencies from SequentialWriter 
(CASSANDRA-11579)
 + * Move skip_stop_words filter before stemming (CASSANDRA-12078)
 + * Support seek() in EncryptedFileSegmentInputStream (CASSANDRA-11957)
 + * SSTable tools mishandling LocalPartitioner (CASSANDRA-12002)
 + * When SEPWorker assigned work, set thread name to match pool 
(CASSANDRA-11966)
 + * Add cross-DC latency metrics (CASSANDRA-11596)
 + * Allow terms in selection clause (CASSANDRA-10783)
 + * Add bind variables to trace (CASSANDRA-11719)
 + * Switch counter shards' clock to timestamps (CASSANDRA-9811)
 + * Introduce HdrHistogram and response/service/wait separation to stress tool 
(CASSANDRA-11853)
 + * entry-weighers in QueryProcessor should respect partitionKeyBindIndexes 
field (CASSANDRA-11718)
 + * Support older ant versions (CASSANDRA-11807)
 + * Estimate compressed on disk size when deciding if sstable size limit 
reached (CASSANDRA-11623)
 + * cassandra-stress profiles should support case sensitive schemas 
(CASSANDRA-11546)
 + * Remove DatabaseDescriptor dependency from FileUtils (CASSANDRA-11578)
 + * Faster streaming (CASSANDRA-9766)
 + * Add prepared query parameter to trace for "Execute CQL3 prepared query" 
session (CASSANDRA-11425)
 + * Add repaired percentage metric (CASSANDRA-11503)
 + * Add Change-Data-Capture (CASSANDRA-8844)
 +Merged from 3.0:
   * Fix paging logic for deleted partitions with static columns 
(CASSANDRA-12107)
   * Wait until the message is being send to decide which serializer must be 
used (CASSANDRA-11393)
   * Fix migration of static thrift column names with non-text comparators 
(CASSANDRA-12147)

http://git-wip-us.apache.org/repos/asf/cassandra/blob/8df6d4d4/pylib/cqlshlib/test/test_cqlsh_output.py
--

[03/10] cassandra git commit: Fixed cqlshlib.test.remove_test_db

[stefania]

Fixed cqlshlib.test.remove_test_db

patch by Stefania Alborghetti; reviewed by Philip Thompson for CASSANDRA-12214


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

Branch: refs/heads/cassandra-3.9
Commit: e8186fe390073f5d7ea11057c5bc842db86d95d2
Parents: f0d1d75
Author: Stefania Alborghetti 
Authored: Tue Jul 19 11:15:46 2016 +0800
Committer: Stefania Alborghetti 
Committed: Wed Jul 20 09:54:53 2016 +0800

--
 CHANGES.txt  |  1 +
 pylib/cqlshlib/test/__init__.py  |  6 +++---
 pylib/cqlshlib/test/cassconnect.py   | 22 +++---
 pylib/cqlshlib/test/test_cqlsh_output.py | 14 +++---
 4 files changed, 22 insertions(+), 21 deletions(-)
--


http://git-wip-us.apache.org/repos/asf/cassandra/blob/e8186fe3/CHANGES.txt
--
diff --git a/CHANGES.txt b/CHANGES.txt
index 837c3fb..ffd92b5 100644
--- a/CHANGES.txt
+++ b/CHANGES.txt
@@ -1,4 +1,5 @@
 2.2.8
+ * Fixed cqlshlib.test.remove_test_db (CASSANDRA-12214)
  * Synchronize ThriftServer::stop() (CASSANDRA-12105)
  * Use dedicated thread for JMX notifications (CASSANDRA-12146)
  * NPE when trying to remove purgable tombstones from result (CASSANDRA-12143)

http://git-wip-us.apache.org/repos/asf/cassandra/blob/e8186fe3/pylib/cqlshlib/test/__init__.py
--
diff --git a/pylib/cqlshlib/test/__init__.py b/pylib/cqlshlib/test/__init__.py
index 31f66f3..ba8f373 100644
--- a/pylib/cqlshlib/test/__init__.py
+++ b/pylib/cqlshlib/test/__init__.py
@@ -14,7 +14,7 @@
 # See the License for the specific language governing permissions and
 # limitations under the License.
 
-from .cassconnect import create_test_db, remove_test_db
+from .cassconnect import create_db, remove_db
 
-setUp = create_test_db
-tearDown = remove_test_db
+setUp = create_db
+tearDown = remove_db

http://git-wip-us.apache.org/repos/asf/cassandra/blob/e8186fe3/pylib/cqlshlib/test/cassconnect.py
--
diff --git a/pylib/cqlshlib/test/cassconnect.py 
b/pylib/cqlshlib/test/cassconnect.py
index 94910a6..4a1311e 100644
--- a/pylib/cqlshlib/test/cassconnect.py
+++ b/pylib/cqlshlib/test/cassconnect.py
@@ -37,15 +37,15 @@ def get_cassandra_cursor(cql_version=cqlsh.DEFAULT_CQLVER):
 
 TEST_KEYSPACES_CREATED = []
 
-def get_test_keyspace():
-return TEST_KEYSPACES_CREATED[-1]
+def get_keyspace():
+return None if len(TEST_KEYSPACES_CREATED) == 0 else 
TEST_KEYSPACES_CREATED[-1]
 
-def make_test_ks_name():
+def make_ks_name():
 # abuse mktemp to get a quick random-ish name
 return os.path.basename(tempfile.mktemp(prefix='CqlshTests_'))
 
-def create_test_keyspace(cursor):
-ksname = make_test_ks_name()
+def create_keyspace(cursor):
+ksname = make_ks_name()
 qksname = quote_name(ksname)
 cursor.execute('''
 CREATE KEYSPACE %s WITH replication =
@@ -72,13 +72,13 @@ def execute_cql_file(cursor, fname):
 with open(fname) as f:
 return execute_cql_commands(cursor, f.read())
 
-def create_test_db():
+def create_db():
 with cassandra_cursor(ks=None) as c:
-k = create_test_keyspace(c)
+k = create_keyspace(c)
 execute_cql_file(c, test_keyspace_init)
 return k
 
-def remove_test_db():
+def remove_db():
 with cassandra_cursor(ks=None) as c:
 c.execute('DROP KEYSPACE %s' % 
quote_name(TEST_KEYSPACES_CREATED.pop(-1)))
 
@@ -112,7 +112,7 @@ def cassandra_cursor(cql_version=None, ks=''):
 """
 
 if ks == '':
-ks = get_test_keyspace()
+ks = get_keyspace()
 conn = get_cassandra_connection(cql_version=cql_version)
 try:
 c = conn.connect(ks)
@@ -131,10 +131,10 @@ def testrun_cqlsh(keyspace=DEFAULTVAL, **kwargs):
 # use a positive default sentinel so that keyspace=None can be used
 # to override the default behavior
 if keyspace is DEFAULTVAL:
-keyspace = get_test_keyspace()
+keyspace = get_keyspace()
 return run_cqlsh(keyspace=keyspace, **kwargs)
 
 def testcall_cqlsh(keyspace=None, **kwargs):
 if keyspace is None:
-keyspace = get_test_keyspace()
+keyspace = get_keyspace()
 return call_cqlsh(keyspace=keyspace, **kwargs)

http://git-wip-us.apache.org/repos/asf/cassandra/blob/e8186fe3/pylib/cqlshlib/test/test_cqlsh_output.py
--
diff --git a/pylib/cqlshlib/test/test_cqlsh_output.py 

[10/10] cassandra git commit: Merge branch 'cassandra-3.9' into trunk

[stefania]

Merge branch 'cassandra-3.9' into trunk


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

Branch: refs/heads/trunk
Commit: f129dea8694ba2a7822748722294da40c9fc0de3
Parents: cc58285 8df6d4d
Author: Stefania Alborghetti 
Authored: Wed Jul 20 10:00:12 2016 +0800
Committer: Stefania Alborghetti 
Committed: Wed Jul 20 10:00:12 2016 +0800

--
 CHANGES.txt  |  2 ++
 pylib/cqlshlib/test/__init__.py  |  6 +++---
 pylib/cqlshlib/test/cassconnect.py   | 22 +++---
 pylib/cqlshlib/test/test_cqlsh_output.py | 14 +++---
 4 files changed, 23 insertions(+), 21 deletions(-)
--


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

http://git-wip-us.apache.org/repos/asf/cassandra/blob/f129dea8/pylib/cqlshlib/test/cassconnect.py
--

http://git-wip-us.apache.org/repos/asf/cassandra/blob/f129dea8/pylib/cqlshlib/test/test_cqlsh_output.py
--
diff --cc pylib/cqlshlib/test/test_cqlsh_output.py
index a6290ff,9936f50..8c19e62
--- a/pylib/cqlshlib/test/test_cqlsh_output.py
+++ b/pylib/cqlshlib/test/test_cqlsh_output.py
@@@ -552,8 -559,9 +552,8 @@@ class TestCqlshOutput(BaseTestCase)
   
"RR")
  
  def test_describe_keyspace_output(self):
 -fullcqlver = cqlsh.DEFAULT_CQLVER
 -with testrun_cqlsh(tty=True, cqlver=fullcqlver) as c:
 +with testrun_cqlsh(tty=True) as c:
- ks = get_test_keyspace()
+ ks = get_keyspace()
  qks = quote_name(ks)
  for cmd in ('describe keyspace', 'desc keyspace'):
  for givename in ('system', '', qks):
@@@ -625,9 -633,9 +625,9 @@@
  AND read_repair_chance = 0.0
  AND speculative_retry = '99PERCENTILE';
  
- """ % quote_name(get_test_keyspace()))
+ """ % quote_name(get_keyspace()))
  
 -with testrun_cqlsh(tty=True, cqlver=cqlsh.DEFAULT_CQLVER) as c:
 +with testrun_cqlsh(tty=True) as c:
  for cmdword in ('describe table', 'desc columnfamily'):
  for semicolon in (';', ''):
  output = c.cmd_and_response('%s has_all_types%s' % 
(cmdword, semicolon))
@@@ -643,9 -651,9 +643,9 @@@
  \n
  '''
  
- ks = get_test_keyspace()
+ ks = get_keyspace()
  
 -with testrun_cqlsh(tty=True, keyspace=None, 
cqlver=cqlsh.DEFAULT_CQLVER) as c:
 +with testrun_cqlsh(tty=True, keyspace=None) as c:
  
  # when not in a keyspace
  for cmdword in ('DESCRIBE COLUMNFAMILIES', 'desc tables'):

[02/10] cassandra git commit: Fixed cqlshlib.test.remove_test_db

[stefania]

Fixed cqlshlib.test.remove_test_db

patch by Stefania Alborghetti; reviewed by Philip Thompson for CASSANDRA-12214


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

Branch: refs/heads/cassandra-3.0
Commit: e8186fe390073f5d7ea11057c5bc842db86d95d2
Parents: f0d1d75
Author: Stefania Alborghetti 
Authored: Tue Jul 19 11:15:46 2016 +0800
Committer: Stefania Alborghetti 
Committed: Wed Jul 20 09:54:53 2016 +0800

--
 CHANGES.txt  |  1 +
 pylib/cqlshlib/test/__init__.py  |  6 +++---
 pylib/cqlshlib/test/cassconnect.py   | 22 +++---
 pylib/cqlshlib/test/test_cqlsh_output.py | 14 +++---
 4 files changed, 22 insertions(+), 21 deletions(-)
--


http://git-wip-us.apache.org/repos/asf/cassandra/blob/e8186fe3/CHANGES.txt
--
diff --git a/CHANGES.txt b/CHANGES.txt
index 837c3fb..ffd92b5 100644
--- a/CHANGES.txt
+++ b/CHANGES.txt
@@ -1,4 +1,5 @@
 2.2.8
+ * Fixed cqlshlib.test.remove_test_db (CASSANDRA-12214)
  * Synchronize ThriftServer::stop() (CASSANDRA-12105)
  * Use dedicated thread for JMX notifications (CASSANDRA-12146)
  * NPE when trying to remove purgable tombstones from result (CASSANDRA-12143)

http://git-wip-us.apache.org/repos/asf/cassandra/blob/e8186fe3/pylib/cqlshlib/test/__init__.py
--
diff --git a/pylib/cqlshlib/test/__init__.py b/pylib/cqlshlib/test/__init__.py
index 31f66f3..ba8f373 100644
--- a/pylib/cqlshlib/test/__init__.py
+++ b/pylib/cqlshlib/test/__init__.py
@@ -14,7 +14,7 @@
 # See the License for the specific language governing permissions and
 # limitations under the License.
 
-from .cassconnect import create_test_db, remove_test_db
+from .cassconnect import create_db, remove_db
 
-setUp = create_test_db
-tearDown = remove_test_db
+setUp = create_db
+tearDown = remove_db

http://git-wip-us.apache.org/repos/asf/cassandra/blob/e8186fe3/pylib/cqlshlib/test/cassconnect.py
--
diff --git a/pylib/cqlshlib/test/cassconnect.py 
b/pylib/cqlshlib/test/cassconnect.py
index 94910a6..4a1311e 100644
--- a/pylib/cqlshlib/test/cassconnect.py
+++ b/pylib/cqlshlib/test/cassconnect.py
@@ -37,15 +37,15 @@ def get_cassandra_cursor(cql_version=cqlsh.DEFAULT_CQLVER):
 
 TEST_KEYSPACES_CREATED = []
 
-def get_test_keyspace():
-return TEST_KEYSPACES_CREATED[-1]
+def get_keyspace():
+return None if len(TEST_KEYSPACES_CREATED) == 0 else 
TEST_KEYSPACES_CREATED[-1]
 
-def make_test_ks_name():
+def make_ks_name():
 # abuse mktemp to get a quick random-ish name
 return os.path.basename(tempfile.mktemp(prefix='CqlshTests_'))
 
-def create_test_keyspace(cursor):
-ksname = make_test_ks_name()
+def create_keyspace(cursor):
+ksname = make_ks_name()
 qksname = quote_name(ksname)
 cursor.execute('''
 CREATE KEYSPACE %s WITH replication =
@@ -72,13 +72,13 @@ def execute_cql_file(cursor, fname):
 with open(fname) as f:
 return execute_cql_commands(cursor, f.read())
 
-def create_test_db():
+def create_db():
 with cassandra_cursor(ks=None) as c:
-k = create_test_keyspace(c)
+k = create_keyspace(c)
 execute_cql_file(c, test_keyspace_init)
 return k
 
-def remove_test_db():
+def remove_db():
 with cassandra_cursor(ks=None) as c:
 c.execute('DROP KEYSPACE %s' % 
quote_name(TEST_KEYSPACES_CREATED.pop(-1)))
 
@@ -112,7 +112,7 @@ def cassandra_cursor(cql_version=None, ks=''):
 """
 
 if ks == '':
-ks = get_test_keyspace()
+ks = get_keyspace()
 conn = get_cassandra_connection(cql_version=cql_version)
 try:
 c = conn.connect(ks)
@@ -131,10 +131,10 @@ def testrun_cqlsh(keyspace=DEFAULTVAL, **kwargs):
 # use a positive default sentinel so that keyspace=None can be used
 # to override the default behavior
 if keyspace is DEFAULTVAL:
-keyspace = get_test_keyspace()
+keyspace = get_keyspace()
 return run_cqlsh(keyspace=keyspace, **kwargs)
 
 def testcall_cqlsh(keyspace=None, **kwargs):
 if keyspace is None:
-keyspace = get_test_keyspace()
+keyspace = get_keyspace()
 return call_cqlsh(keyspace=keyspace, **kwargs)

http://git-wip-us.apache.org/repos/asf/cassandra/blob/e8186fe3/pylib/cqlshlib/test/test_cqlsh_output.py
--
diff --git a/pylib/cqlshlib/test/test_cqlsh_output.py 

[04/10] cassandra git commit: Fixed cqlshlib.test.remove_test_db

[stefania]

Fixed cqlshlib.test.remove_test_db

patch by Stefania Alborghetti; reviewed by Philip Thompson for CASSANDRA-12214


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

Branch: refs/heads/trunk
Commit: e8186fe390073f5d7ea11057c5bc842db86d95d2
Parents: f0d1d75
Author: Stefania Alborghetti 
Authored: Tue Jul 19 11:15:46 2016 +0800
Committer: Stefania Alborghetti 
Committed: Wed Jul 20 09:54:53 2016 +0800

--
 CHANGES.txt  |  1 +
 pylib/cqlshlib/test/__init__.py  |  6 +++---
 pylib/cqlshlib/test/cassconnect.py   | 22 +++---
 pylib/cqlshlib/test/test_cqlsh_output.py | 14 +++---
 4 files changed, 22 insertions(+), 21 deletions(-)
--


http://git-wip-us.apache.org/repos/asf/cassandra/blob/e8186fe3/CHANGES.txt
--
diff --git a/CHANGES.txt b/CHANGES.txt
index 837c3fb..ffd92b5 100644
--- a/CHANGES.txt
+++ b/CHANGES.txt
@@ -1,4 +1,5 @@
 2.2.8
+ * Fixed cqlshlib.test.remove_test_db (CASSANDRA-12214)
  * Synchronize ThriftServer::stop() (CASSANDRA-12105)
  * Use dedicated thread for JMX notifications (CASSANDRA-12146)
  * NPE when trying to remove purgable tombstones from result (CASSANDRA-12143)

http://git-wip-us.apache.org/repos/asf/cassandra/blob/e8186fe3/pylib/cqlshlib/test/__init__.py
--
diff --git a/pylib/cqlshlib/test/__init__.py b/pylib/cqlshlib/test/__init__.py
index 31f66f3..ba8f373 100644
--- a/pylib/cqlshlib/test/__init__.py
+++ b/pylib/cqlshlib/test/__init__.py
@@ -14,7 +14,7 @@
 # See the License for the specific language governing permissions and
 # limitations under the License.
 
-from .cassconnect import create_test_db, remove_test_db
+from .cassconnect import create_db, remove_db
 
-setUp = create_test_db
-tearDown = remove_test_db
+setUp = create_db
+tearDown = remove_db

http://git-wip-us.apache.org/repos/asf/cassandra/blob/e8186fe3/pylib/cqlshlib/test/cassconnect.py
--
diff --git a/pylib/cqlshlib/test/cassconnect.py 
b/pylib/cqlshlib/test/cassconnect.py
index 94910a6..4a1311e 100644
--- a/pylib/cqlshlib/test/cassconnect.py
+++ b/pylib/cqlshlib/test/cassconnect.py
@@ -37,15 +37,15 @@ def get_cassandra_cursor(cql_version=cqlsh.DEFAULT_CQLVER):
 
 TEST_KEYSPACES_CREATED = []
 
-def get_test_keyspace():
-return TEST_KEYSPACES_CREATED[-1]
+def get_keyspace():
+return None if len(TEST_KEYSPACES_CREATED) == 0 else 
TEST_KEYSPACES_CREATED[-1]
 
-def make_test_ks_name():
+def make_ks_name():
 # abuse mktemp to get a quick random-ish name
 return os.path.basename(tempfile.mktemp(prefix='CqlshTests_'))
 
-def create_test_keyspace(cursor):
-ksname = make_test_ks_name()
+def create_keyspace(cursor):
+ksname = make_ks_name()
 qksname = quote_name(ksname)
 cursor.execute('''
 CREATE KEYSPACE %s WITH replication =
@@ -72,13 +72,13 @@ def execute_cql_file(cursor, fname):
 with open(fname) as f:
 return execute_cql_commands(cursor, f.read())
 
-def create_test_db():
+def create_db():
 with cassandra_cursor(ks=None) as c:
-k = create_test_keyspace(c)
+k = create_keyspace(c)
 execute_cql_file(c, test_keyspace_init)
 return k
 
-def remove_test_db():
+def remove_db():
 with cassandra_cursor(ks=None) as c:
 c.execute('DROP KEYSPACE %s' % 
quote_name(TEST_KEYSPACES_CREATED.pop(-1)))
 
@@ -112,7 +112,7 @@ def cassandra_cursor(cql_version=None, ks=''):
 """
 
 if ks == '':
-ks = get_test_keyspace()
+ks = get_keyspace()
 conn = get_cassandra_connection(cql_version=cql_version)
 try:
 c = conn.connect(ks)
@@ -131,10 +131,10 @@ def testrun_cqlsh(keyspace=DEFAULTVAL, **kwargs):
 # use a positive default sentinel so that keyspace=None can be used
 # to override the default behavior
 if keyspace is DEFAULTVAL:
-keyspace = get_test_keyspace()
+keyspace = get_keyspace()
 return run_cqlsh(keyspace=keyspace, **kwargs)
 
 def testcall_cqlsh(keyspace=None, **kwargs):
 if keyspace is None:
-keyspace = get_test_keyspace()
+keyspace = get_keyspace()
 return call_cqlsh(keyspace=keyspace, **kwargs)

http://git-wip-us.apache.org/repos/asf/cassandra/blob/e8186fe3/pylib/cqlshlib/test/test_cqlsh_output.py
--
diff --git a/pylib/cqlshlib/test/test_cqlsh_output.py 

[09/10] cassandra git commit: Merge branch 'cassandra-3.0' into cassandra-3.9

[stefania]

Merge branch 'cassandra-3.0' into cassandra-3.9


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

Branch: refs/heads/trunk
Commit: 8df6d4d4c60f865a09a93ff678ea5f6417465c29
Parents: 4bd4be8 dce4537
Author: Stefania Alborghetti 
Authored: Wed Jul 20 09:58:14 2016 +0800
Committer: Stefania Alborghetti 
Committed: Wed Jul 20 09:58:40 2016 +0800

--
 CHANGES.txt  |  2 ++
 pylib/cqlshlib/test/__init__.py  |  6 +++---
 pylib/cqlshlib/test/cassconnect.py   | 22 +++---
 pylib/cqlshlib/test/test_cqlsh_output.py | 14 +++---
 4 files changed, 23 insertions(+), 21 deletions(-)
--


http://git-wip-us.apache.org/repos/asf/cassandra/blob/8df6d4d4/CHANGES.txt
--
diff --cc CHANGES.txt
index 780ea96,739c095..dac46ab
--- a/CHANGES.txt
+++ b/CHANGES.txt
@@@ -1,36 -1,5 +1,38 @@@
 -3.0.9
 +3.9
 +Merged from 3.0:
   * Fix problem with undeleteable rows on upgrade to new sstable format 
(CASSANDRA-12144)
++Merged from 2.2:
++ * Fixed cqlshlib.test.remove_test_db (CASSANDRA-12214)
 +
 +3.8
 + * Fix hdr logging for single operation workloads (CASSANDRA-12145)
 + * Fix SASI PREFIX search in CONTAINS mode with partial terms 
(CASSANDRA-12073)
 + * Increase size of flushExecutor thread pool (CASSANDRA-12071)
 + * Partial revert of CASSANDRA-11971, cannot recycle buffer in 
SP.sendMessagesToNonlocalDC (CASSANDRA-11950)
 + * Upgrade netty to 4.0.39 (CASSANDRA-12032, CASSANDRA-12034)
 + * Improve details in compaction log message (CASSANDRA-12080)
 + * Allow unset values in CQLSSTableWriter (CASSANDRA-11911)
 + * Chunk cache to request compressor-compatible buffers if pool space is 
exhausted (CASSANDRA-11993)
 + * Remove DatabaseDescriptor dependencies from SequentialWriter 
(CASSANDRA-11579)
 + * Move skip_stop_words filter before stemming (CASSANDRA-12078)
 + * Support seek() in EncryptedFileSegmentInputStream (CASSANDRA-11957)
 + * SSTable tools mishandling LocalPartitioner (CASSANDRA-12002)
 + * When SEPWorker assigned work, set thread name to match pool 
(CASSANDRA-11966)
 + * Add cross-DC latency metrics (CASSANDRA-11596)
 + * Allow terms in selection clause (CASSANDRA-10783)
 + * Add bind variables to trace (CASSANDRA-11719)
 + * Switch counter shards' clock to timestamps (CASSANDRA-9811)
 + * Introduce HdrHistogram and response/service/wait separation to stress tool 
(CASSANDRA-11853)
 + * entry-weighers in QueryProcessor should respect partitionKeyBindIndexes 
field (CASSANDRA-11718)
 + * Support older ant versions (CASSANDRA-11807)
 + * Estimate compressed on disk size when deciding if sstable size limit 
reached (CASSANDRA-11623)
 + * cassandra-stress profiles should support case sensitive schemas 
(CASSANDRA-11546)
 + * Remove DatabaseDescriptor dependency from FileUtils (CASSANDRA-11578)
 + * Faster streaming (CASSANDRA-9766)
 + * Add prepared query parameter to trace for "Execute CQL3 prepared query" 
session (CASSANDRA-11425)
 + * Add repaired percentage metric (CASSANDRA-11503)
 + * Add Change-Data-Capture (CASSANDRA-8844)
 +Merged from 3.0:
   * Fix paging logic for deleted partitions with static columns 
(CASSANDRA-12107)
   * Wait until the message is being send to decide which serializer must be 
used (CASSANDRA-11393)
   * Fix migration of static thrift column names with non-text comparators 
(CASSANDRA-12147)

http://git-wip-us.apache.org/repos/asf/cassandra/blob/8df6d4d4/pylib/cqlshlib/test/test_cqlsh_output.py
--

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

[stefania]

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/dce45374
Tree: http://git-wip-us.apache.org/repos/asf/cassandra/tree/dce45374
Diff: http://git-wip-us.apache.org/repos/asf/cassandra/diff/dce45374

Branch: refs/heads/cassandra-3.9
Commit: dce4537410d66a3cbd24b2e581737b849e011917
Parents: 0297cbe e8186fe
Author: Stefania Alborghetti 
Authored: Wed Jul 20 09:56:12 2016 +0800
Committer: Stefania Alborghetti 
Committed: Wed Jul 20 09:56:12 2016 +0800

--
 CHANGES.txt  |  1 +
 pylib/cqlshlib/test/__init__.py  |  6 +++---
 pylib/cqlshlib/test/cassconnect.py   | 22 +++---
 pylib/cqlshlib/test/test_cqlsh_output.py | 14 +++---
 4 files changed, 22 insertions(+), 21 deletions(-)
--


http://git-wip-us.apache.org/repos/asf/cassandra/blob/dce45374/CHANGES.txt
--
diff --cc CHANGES.txt
index f205e0b,ffd92b5..739c095
--- a/CHANGES.txt
+++ b/CHANGES.txt
@@@ -1,21 -1,8 +1,22 @@@
 -2.2.8
 +3.0.9
 + * Fix problem with undeleteable rows on upgrade to new sstable format 
(CASSANDRA-12144)
 + * Fix paging logic for deleted partitions with static columns 
(CASSANDRA-12107)
 + * Wait until the message is being send to decide which serializer must be 
used (CASSANDRA-11393)
 + * Fix migration of static thrift column names with non-text comparators 
(CASSANDRA-12147)
 + * Fix upgrading sparse tables that are incorrectly marked as dense 
(CASSANDRA-11315)
 + * Fix reverse queries ignoring range tombstones (CASSANDRA-11733)
 + * Avoid potential race when rebuilding CFMetaData (CASSANDRA-12098)
 + * Avoid missing sstables when getting the canonical sstables 
(CASSANDRA-11996)
 + * Always select the live sstables when getting sstables in bounds 
(CASSANDRA-11944)
 + * Fix column ordering of results with static columns for Thrift requests in
 +   a mixed 2.x/3.x cluster, also fix potential non-resolved duplication of
 +   those static columns in query results (CASSANDRA-12123)
 + * Avoid digest mismatch with empty but static rows (CASSANDRA-12090)
 + * Fix EOF exception when altering column type (CASSANDRA-11820)
 +Merged from 2.2:
+  * Fixed cqlshlib.test.remove_test_db (CASSANDRA-12214)
   * Synchronize ThriftServer::stop() (CASSANDRA-12105)
   * Use dedicated thread for JMX notifications (CASSANDRA-12146)
 - * NPE when trying to remove purgable tombstones from result (CASSANDRA-12143)
   * Improve streaming synchronization and fault tolerance (CASSANDRA-11414)
   * MemoryUtil.getShort() should return an unsigned short also for 
architectures not supporting unaligned memory accesses (CASSANDRA-11973)
  Merged from 2.1:

http://git-wip-us.apache.org/repos/asf/cassandra/blob/dce45374/pylib/cqlshlib/test/test_cqlsh_output.py
--
diff --cc pylib/cqlshlib/test/test_cqlsh_output.py
index f867312,60699f3..85ce626
--- a/pylib/cqlshlib/test/test_cqlsh_output.py
+++ b/pylib/cqlshlib/test/test_cqlsh_output.py
@@@ -631,9 -630,9 +631,9 @@@ class TestCqlshOutput(BaseTestCase)
  AND memtable_flush_period_in_ms = 0
  AND min_index_interval = 128
  AND read_repair_chance = 0.0
 -AND speculative_retry = '99.0PERCENTILE';
 +AND speculative_retry = '99PERCENTILE';
  
- """ % quote_name(get_test_keyspace()))
+ """ % quote_name(get_keyspace()))
  
  with testrun_cqlsh(tty=True, cqlver=cqlsh.DEFAULT_CQLVER) as c:
  for cmdword in ('describe table', 'desc columnfamily'):

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

[stefania]

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/dce45374
Tree: http://git-wip-us.apache.org/repos/asf/cassandra/tree/dce45374
Diff: http://git-wip-us.apache.org/repos/asf/cassandra/diff/dce45374

Branch: refs/heads/trunk
Commit: dce4537410d66a3cbd24b2e581737b849e011917
Parents: 0297cbe e8186fe
Author: Stefania Alborghetti 
Authored: Wed Jul 20 09:56:12 2016 +0800
Committer: Stefania Alborghetti 
Committed: Wed Jul 20 09:56:12 2016 +0800

--
 CHANGES.txt  |  1 +
 pylib/cqlshlib/test/__init__.py  |  6 +++---
 pylib/cqlshlib/test/cassconnect.py   | 22 +++---
 pylib/cqlshlib/test/test_cqlsh_output.py | 14 +++---
 4 files changed, 22 insertions(+), 21 deletions(-)
--


http://git-wip-us.apache.org/repos/asf/cassandra/blob/dce45374/CHANGES.txt
--
diff --cc CHANGES.txt
index f205e0b,ffd92b5..739c095
--- a/CHANGES.txt
+++ b/CHANGES.txt
@@@ -1,21 -1,8 +1,22 @@@
 -2.2.8
 +3.0.9
 + * Fix problem with undeleteable rows on upgrade to new sstable format 
(CASSANDRA-12144)
 + * Fix paging logic for deleted partitions with static columns 
(CASSANDRA-12107)
 + * Wait until the message is being send to decide which serializer must be 
used (CASSANDRA-11393)
 + * Fix migration of static thrift column names with non-text comparators 
(CASSANDRA-12147)
 + * Fix upgrading sparse tables that are incorrectly marked as dense 
(CASSANDRA-11315)
 + * Fix reverse queries ignoring range tombstones (CASSANDRA-11733)
 + * Avoid potential race when rebuilding CFMetaData (CASSANDRA-12098)
 + * Avoid missing sstables when getting the canonical sstables 
(CASSANDRA-11996)
 + * Always select the live sstables when getting sstables in bounds 
(CASSANDRA-11944)
 + * Fix column ordering of results with static columns for Thrift requests in
 +   a mixed 2.x/3.x cluster, also fix potential non-resolved duplication of
 +   those static columns in query results (CASSANDRA-12123)
 + * Avoid digest mismatch with empty but static rows (CASSANDRA-12090)
 + * Fix EOF exception when altering column type (CASSANDRA-11820)
 +Merged from 2.2:
+  * Fixed cqlshlib.test.remove_test_db (CASSANDRA-12214)
   * Synchronize ThriftServer::stop() (CASSANDRA-12105)
   * Use dedicated thread for JMX notifications (CASSANDRA-12146)
 - * NPE when trying to remove purgable tombstones from result (CASSANDRA-12143)
   * Improve streaming synchronization and fault tolerance (CASSANDRA-11414)
   * MemoryUtil.getShort() should return an unsigned short also for 
architectures not supporting unaligned memory accesses (CASSANDRA-11973)
  Merged from 2.1:

http://git-wip-us.apache.org/repos/asf/cassandra/blob/dce45374/pylib/cqlshlib/test/test_cqlsh_output.py
--
diff --cc pylib/cqlshlib/test/test_cqlsh_output.py
index f867312,60699f3..85ce626
--- a/pylib/cqlshlib/test/test_cqlsh_output.py
+++ b/pylib/cqlshlib/test/test_cqlsh_output.py
@@@ -631,9 -630,9 +631,9 @@@ class TestCqlshOutput(BaseTestCase)
  AND memtable_flush_period_in_ms = 0
  AND min_index_interval = 128
  AND read_repair_chance = 0.0
 -AND speculative_retry = '99.0PERCENTILE';
 +AND speculative_retry = '99PERCENTILE';
  
- """ % quote_name(get_test_keyspace()))
+ """ % quote_name(get_keyspace()))
  
  with testrun_cqlsh(tty=True, cqlver=cqlsh.DEFAULT_CQLVER) as c:
  for cmdword in ('describe table', 'desc columnfamily'):

[jira] [Commented] (CASSANDRA-12179) Make DynamicEndpointSnitch dynamic_snitch_update_interval_in_ms a JMX Prop

[Robert Stupp (JIRA)]

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

Robert Stupp commented on CASSANDRA-12179:
--

Looks good so far. Let me play with that a bit.

> Make DynamicEndpointSnitch dynamic_snitch_update_interval_in_ms a JMX Prop 
> ---
>
> Key: CASSANDRA-12179
> URL: https://issues.apache.org/jira/browse/CASSANDRA-12179
> Project: Cassandra
>  Issue Type: Improvement
>Reporter: sankalp kohli
>Assignee: sankalp kohli
>Priority: Trivial
> Fix For: 3.0.x
>
> Attachments: CASSANDRA-12179-3.0_v2.txt, CASSANDRA-12179_3.0.txt, 
> CASSANDRA-12179_3.0_v3.txt
>
>
> Need to expose dynamic_snitch_update_interval_in_ms so that it does not 
> require a bounce. This is useful for large clusters where we can change this 
> value and see the impact. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (CASSANDRA-11866) nodetool repair does not obey the column family parameter when -st and -et are provided (subrange repair)

[Vinay Chella (JIRA)]

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

Vinay Chella updated CASSANDRA-11866:
-
Status: Patch Available  (was: Open)

> nodetool repair does not obey the column family parameter when -st and -et 
> are provided (subrange repair)
> -
>
> Key: CASSANDRA-11866
> URL: https://issues.apache.org/jira/browse/CASSANDRA-11866
> Project: Cassandra
>  Issue Type: Bug
>  Components: Tools
> Environment: Red Hat Enterprise Linux Server release 6.7 (Santiago) 
> x86_64
>Reporter: Shiva Venkateswaran
>  Labels: newbie
> Fix For: 2.1.x
>
> Attachments: 11866-2.1.txt
>
>
> Command 1: Repairs all the CFs in ADL_GLOBAL keyspace and ignores the 
> parameter AssetModifyTimes_data used to restrict the CFs
> Executing: /aladdin/local/apps/apache-cassandra-2.1.8a/bin/nodetool -h 
> localhost -p 7199 -u user-pw ** repair ADL_GLOBAL AssetModifyTimes_data 
> -st 205279477618143669 -et 230991685737746901 -par
> [2016-05-20 17:31:39,116] Starting repair command #9, repairing 1 ranges for 
> keyspace ADL_GLOBAL (parallelism=PARALLEL, full=true)
> [2016-05-20 17:32:21,568] Repair session 3cae2530-1ed2-11e6-b490-d9df6932c7cf 
> for range (205279477618143669,230991685737746901] finished
> Command 2: Repairs all the CFs in ADL_GLOBAL keyspace and ignores the 
> parameter AssetModifyTimes_data used to restrict the CFs
> Executing: /aladdin/local/apps/apache-cassandra-2.1.8a/bin/nodetool -h 
> localhost -p 7199 -u controlRole -pw ** repair -st 205279477618143669 -et 
> 230991685737746901 -par -- ADL_GLOBAL AssetModifyTimes_data
> [2016-05-20 17:36:34,473] Starting repair command #10, repairing 1 ranges for 
> keyspace ADL_GLOBAL (parallelism=PARALLEL, full=true)
> [2016-05-20 17:37:15,365] Repair session ecb996d0-1ed2-11e6-b490-d9df6932c7cf 
> for range (205279477618143669,230991685737746901] finished
> [2016-05-20 17:37:15,365] Repair command #10 finished
> Command 3: Repairs only the CF ADL3Test1_data in keyspace ADL_GLOBAL
> Executing: /aladdin/local/apps/apache-cassandra-2.1.8a/bin/nodetool -h 
> localhost -p 7199 -u controlRole -pw ** repair -- ADL_GLOBAL 
> ADL3Test1_data
> [2016-05-20 17:38:35,781] Starting repair command #11, repairing 1043 ranges 
> for keyspace ADL_GLOBAL (parallelism=SEQUENTIAL, full=true)
> [2016-05-20 17:42:32,682] Repair session 3c8af050-1ed3-11e6-b490-d9df6932c7cf 
> for range (6241639152751626129,6241693909092643958] finished
> [2016-05-20 17:42:32,683] Repair session 3caf1a20-1ed3-11e6-b490-d9df6932c7cf 
> for range (-7096993048358106082,-7095000706885780850] finished
> [2016-05-20 17:42:32,683] Repair session 3ccfc180-1ed3-11e6-b490-d9df6932c7cf 
> for range (-7218939248114487080,-7218289345961492809] finished
> [2016-05-20 17:42:32,683] Repair session 3cf21690-1ed3-11e6-b490-d9df6932c7cf 
> for range (-5244794756638190874,-5190307341355030282] finished
> [2016-05-20 17:42:32,683] Repair session 3d126fd0-1ed3-11e6-b490-d9df6932c7cf 
> for range (3551629701277971766,321736534916502] finished
> [2016-05-20 17:42:32,683] Repair session 3d32f020-1ed3-11e6-b490-d9df6932c7cf 
> for range (-8139355591560661944,-8127928369093576603] finished
> [2016-05-20 17:42:32,683] Repair session 3d537070-1ed3-11e6-b490-d9df6932c7cf 
> for range (7098010153980465751,7100863011896759020] finished
> [2016-05-20 17:42:32,683] Repair session 3d73f0c0-1ed3-11e6-b490-d9df6932c7cf 
> for range (1004538726866173536,1008586133746764703] finished
> [2016-05-20 17:42:32,683] Repair session 3d947110-1ed3-11e6-b490-d9df6932c7cf 
> for range (5770817093573726645,5771418910784831587] finished
> .
> .
> .
> [2016-05-20 17:42:32,732] Repair command #11 finished



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (CASSANDRA-11866) nodetool repair does not obey the column family parameter when -st and -et are provided (subrange repair)

[Vinay Chella (JIRA)]

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

Vinay Chella updated CASSANDRA-11866:
-
Attachment: 11866-2.1.txt

> nodetool repair does not obey the column family parameter when -st and -et 
> are provided (subrange repair)
> -
>
> Key: CASSANDRA-11866
> URL: https://issues.apache.org/jira/browse/CASSANDRA-11866
> Project: Cassandra
>  Issue Type: Bug
>  Components: Tools
> Environment: Red Hat Enterprise Linux Server release 6.7 (Santiago) 
> x86_64
>Reporter: Shiva Venkateswaran
>  Labels: newbie
> Fix For: 2.1.x
>
> Attachments: 11866-2.1.txt
>
>
> Command 1: Repairs all the CFs in ADL_GLOBAL keyspace and ignores the 
> parameter AssetModifyTimes_data used to restrict the CFs
> Executing: /aladdin/local/apps/apache-cassandra-2.1.8a/bin/nodetool -h 
> localhost -p 7199 -u user-pw ** repair ADL_GLOBAL AssetModifyTimes_data 
> -st 205279477618143669 -et 230991685737746901 -par
> [2016-05-20 17:31:39,116] Starting repair command #9, repairing 1 ranges for 
> keyspace ADL_GLOBAL (parallelism=PARALLEL, full=true)
> [2016-05-20 17:32:21,568] Repair session 3cae2530-1ed2-11e6-b490-d9df6932c7cf 
> for range (205279477618143669,230991685737746901] finished
> Command 2: Repairs all the CFs in ADL_GLOBAL keyspace and ignores the 
> parameter AssetModifyTimes_data used to restrict the CFs
> Executing: /aladdin/local/apps/apache-cassandra-2.1.8a/bin/nodetool -h 
> localhost -p 7199 -u controlRole -pw ** repair -st 205279477618143669 -et 
> 230991685737746901 -par -- ADL_GLOBAL AssetModifyTimes_data
> [2016-05-20 17:36:34,473] Starting repair command #10, repairing 1 ranges for 
> keyspace ADL_GLOBAL (parallelism=PARALLEL, full=true)
> [2016-05-20 17:37:15,365] Repair session ecb996d0-1ed2-11e6-b490-d9df6932c7cf 
> for range (205279477618143669,230991685737746901] finished
> [2016-05-20 17:37:15,365] Repair command #10 finished
> Command 3: Repairs only the CF ADL3Test1_data in keyspace ADL_GLOBAL
> Executing: /aladdin/local/apps/apache-cassandra-2.1.8a/bin/nodetool -h 
> localhost -p 7199 -u controlRole -pw ** repair -- ADL_GLOBAL 
> ADL3Test1_data
> [2016-05-20 17:38:35,781] Starting repair command #11, repairing 1043 ranges 
> for keyspace ADL_GLOBAL (parallelism=SEQUENTIAL, full=true)
> [2016-05-20 17:42:32,682] Repair session 3c8af050-1ed3-11e6-b490-d9df6932c7cf 
> for range (6241639152751626129,6241693909092643958] finished
> [2016-05-20 17:42:32,683] Repair session 3caf1a20-1ed3-11e6-b490-d9df6932c7cf 
> for range (-7096993048358106082,-7095000706885780850] finished
> [2016-05-20 17:42:32,683] Repair session 3ccfc180-1ed3-11e6-b490-d9df6932c7cf 
> for range (-7218939248114487080,-7218289345961492809] finished
> [2016-05-20 17:42:32,683] Repair session 3cf21690-1ed3-11e6-b490-d9df6932c7cf 
> for range (-5244794756638190874,-5190307341355030282] finished
> [2016-05-20 17:42:32,683] Repair session 3d126fd0-1ed3-11e6-b490-d9df6932c7cf 
> for range (3551629701277971766,321736534916502] finished
> [2016-05-20 17:42:32,683] Repair session 3d32f020-1ed3-11e6-b490-d9df6932c7cf 
> for range (-8139355591560661944,-8127928369093576603] finished
> [2016-05-20 17:42:32,683] Repair session 3d537070-1ed3-11e6-b490-d9df6932c7cf 
> for range (7098010153980465751,7100863011896759020] finished
> [2016-05-20 17:42:32,683] Repair session 3d73f0c0-1ed3-11e6-b490-d9df6932c7cf 
> for range (1004538726866173536,1008586133746764703] finished
> [2016-05-20 17:42:32,683] Repair session 3d947110-1ed3-11e6-b490-d9df6932c7cf 
> for range (5770817093573726645,5771418910784831587] finished
> .
> .
> .
> [2016-05-20 17:42:32,732] Repair command #11 finished



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (CASSANDRA-11465) dtest failure in cql_tracing_test.TestCqlTracing.tracing_unknown_impl_test

[Stefania (JIRA)]

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

Stefania commented on CASSANDRA-11465:
--

Thanks for running the tests.

I've backported the patch to 2.2 and 3.0 as well, since {{tracing_simple_test}} 
may fail there too. Here is a recap:

||2.2||3.0||3.9||trunk||
|[patch|https://github.com/stef1927/cassandra/commits/11465-cqlsh-2.2]|[patch|https://github.com/stef1927/cassandra/commits/11465-cqlsh-3.0]|[patch|https://github.com/stef1927/cassandra/commits/11465-cqlsh-3.9]|[patch|https://github.com/stef1927/cassandra/commits/11465-cqlsh]|
|[testall|http://cassci.datastax.com/view/Dev/view/stef1927/job/stef1927-11465-cqlsh-2.2-testall/]|[testall|http://cassci.datastax.com/view/Dev/view/stef1927/job/stef1927-11465-cqlsh-3.0-testall/]|[testall|http://cassci.datastax.com/view/Dev/view/stef1927/job/stef1927-11465-cqlsh-3.9-testall/]|[testall|http://cassci.datastax.com/view/Dev/view/stef1927/job/stef1927-11465-cqlsh-testall/]|
|[dtest|http://cassci.datastax.com/view/Dev/view/stef1927/job/stef1927-11465-cqlsh-2.2-dtest/]|[dtest|http://cassci.datastax.com/view/Dev/view/stef1927/job/stef1927-11465-cqlsh-3.0-dtest/]|[dtest|http://cassci.datastax.com/view/Dev/view/stef1927/job/stef1927-11465-cqlsh-3.9-dtest/]|[dtest|http://cassci.datastax.com/view/Dev/view/stef1927/job/stef1927-11465-cqlsh-dtest/]|

Here are the [dtest 
changes|https://github.com/stef1927/cassandra-dtest/commits/11465].

Both dtest and c* patches are based on the CASSANDRA-11850 patch.


> dtest failure in cql_tracing_test.TestCqlTracing.tracing_unknown_impl_test
> --
>
> Key: CASSANDRA-11465
> URL: https://issues.apache.org/jira/browse/CASSANDRA-11465
> Project: Cassandra
>  Issue Type: Bug
>Reporter: Philip Thompson
>Assignee: Stefania
>  Labels: dtest
>
> Failing on the following assert, on trunk only: 
> {{self.assertEqual(len(errs[0]), 1)}}
> Is not failing consistently.
> example failure:
> http://cassci.datastax.com/job/trunk_dtest/1087/testReport/cql_tracing_test/TestCqlTracing/tracing_unknown_impl_test
> Failed on CassCI build trunk_dtest #1087



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (CASSANDRA-11465) dtest failure in cql_tracing_test.TestCqlTracing.tracing_unknown_impl_test

[Stefania (JIRA)]

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

Stefania updated CASSANDRA-11465:
-
Status: Patch Available  (was: Open)

> dtest failure in cql_tracing_test.TestCqlTracing.tracing_unknown_impl_test
> --
>
> Key: CASSANDRA-11465
> URL: https://issues.apache.org/jira/browse/CASSANDRA-11465
> Project: Cassandra
>  Issue Type: Bug
>Reporter: Philip Thompson
>Assignee: Stefania
>  Labels: dtest
>
> Failing on the following assert, on trunk only: 
> {{self.assertEqual(len(errs[0]), 1)}}
> Is not failing consistently.
> example failure:
> http://cassci.datastax.com/job/trunk_dtest/1087/testReport/cql_tracing_test/TestCqlTracing/tracing_unknown_impl_test
> Failed on CassCI build trunk_dtest #1087



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (CASSANDRA-12235) dtest failure in bootstrap_test.TestBootstrap.consistent_range_movement_true_with_ks_rf1_should_succeed_test

[Philip Thompson (JIRA)]

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

Philip Thompson updated CASSANDRA-12235:

Attachment: node4.log
node4_gc.log
node3.log
node3_gc.log
node3_debug.log
node2.log
node2_gc.log
node2_debug.log
node1.log
node1_gc.log
node1_debug.log

There isn't really much useful in the logs, other than the fact that node2 died 
about ten minutes before the test ended. Gc.log and debug.log don't really show 
a cause of death. I have to assume the oom killer? 

> dtest failure in 
> bootstrap_test.TestBootstrap.consistent_range_movement_true_with_ks_rf1_should_succeed_test
> 
>
> Key: CASSANDRA-12235
> URL: https://issues.apache.org/jira/browse/CASSANDRA-12235
> Project: Cassandra
>  Issue Type: Test
>Reporter: Philip Thompson
>Assignee: DS Test Eng
>  Labels: dtest
> Attachments: node1.log, node1_debug.log, node1_gc.log, node2.log, 
> node2_debug.log, node2_gc.log, node3.log, node3_debug.log, node3_gc.log, 
> node4.log, node4_gc.log
>
>
> example failure:
> http://cassci.datastax.com/job/cassandra-3.8_novnode_dtest/5/testReport/bootstrap_test/TestBootstrap/consistent_range_movement_true_with_ks_rf1_should_succeed_test
> Failed on CassCI build cassandra-3.8_novnode_dtest #5



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (CASSANDRA-11850) cannot use cql since upgrading python to 2.7.11+

[Paulo Motta (JIRA)]

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

Paulo Motta commented on CASSANDRA-11850:
-

Thanks for the patch and detailed explanation! Overall it looks good, see 
follow-up:
* The 2.1 patch looks, can you just update to use the 2.7.2 zip now that 
[#606|https://github.com/datastax/python-driver/pull/606] got in?
* Similarly, can you regenerate the 2.2+ cassandra-driver libs after 
[#617|https://github.com/datastax/python-driver/pull/617] was merged?
* I didn't get [this 
change|https://github.com/apache/cassandra/compare/trunk...stef1927:11850-cqlsh-2.2#diff-27e394435c04a60c58ec9d5c34397341R739],
 is this related to this patch? won't {{prev_worker_no=-1}} and thus {{i=0}} 
always?
* +1 to dtest and cdc-related changes (afaic)
* The original intent of {{test_refresh_schema_on_timeout_error}} on 
CASSANDRA-9689 was to make sure a newly created keyspace/table will show up if 
there is a down node during the {{DDL}} statement, but since down nodes no 
longer causes schema mismatches after 
[PYTHON-531|https://datastax-oss.atlassian.net/browse/PYTHON-531] the schema 
mismatch assertions are no longer necessary (even though we still need to keep 
the {{--request-timeout}} option on 2.1 dtest to avoid flakiness - see 
CASSANDRA-10686), so I renamed the test to 
{{test_update_schema_with_down_node}}. Here is the [dtest 
branch|https://github.com/pauloricardomg/cassandra-dtest/tree/11850] with these 
changes.
* I also added a [new 
commit|https://github.com/pauloricardomg/cassandra/commit/02c3c25f92e395e09c66ba36010abb8e38f23d0b]
 with the following changes:
** Refactor {{perform_simple_statement}} to always [try to reload the 
schema|https://github.com/pauloricardomg/cassandra/commit/02c3c25f92e395e09c66ba36010abb8e38f23d0b#diff-1cce67f7d76864f07aaf4d986d6fc051R1272]
 if there's a mismatch in order to cover both CASSANDRA-9689 and 
CASSANDRA-10686.
** 
[Remove|https://github.com/pauloricardomg/cassandra/commit/02c3c25f92e395e09c66ba36010abb8e38f23d0b#diff-1cce67f7d76864f07aaf4d986d6fc051L724]
 the schema mismatch check on startup, since this is no longer necessary after 
[PYTHON-303|https://github.com/datastax/python-driver/pull/349].
** Update the schema mismatch warning 
[message|https://github.com/pauloricardomg/cassandra/commit/02c3c25f92e395e09c66ba36010abb8e38f23d0b#diff-1cce67f7d76864f07aaf4d986d6fc051R1276]
* It would be nice to add a dtest to verify that the schema mismatch warning is 
being print on a proper schema mismatch but I didn't find a simple way to 
induce a schema mismatch without adding a special test flag on C* which is not 
an ideal solution. I tested manually by disabling the {{schema_version}} update 
on the {{system.peers}} table, and the warning is being printed correctly. We 
could probably achieve that easily with byteman but since that is not yet 
integrated with dtests let's maybe leave it for another ticket.
* Submitted multiplexer 100x runs for 
[2.1|https://cassci.datastax.com/view/Parameterized/job/parameterized_dtest_multiplexer/176/]
 and 
[trunk|https://cassci.datastax.com/view/Parameterized/job/parameterized_dtest_multiplexer/173/]
 so we can remove the {{@known_failure}} annotations and close CASSANDRA-11999 
and CASSANDRA-10884.
* It would be nice if you could maybe extract CASSANDRA-11979 to a separate 
commit to improve traceability?

Submitted tests with updates below:
||2.1||2.2||3.0||3.9||trunk||dtest||
|[branch|https://github.com/apache/cassandra/compare/cassandra-2.1...pauloricardomg:11850-cqlsh-2.1]|[branch|https://github.com/apache/cassandra/compare/cassandra-2.2...pauloricardomg:11850-cqlsh-2.2]|[branch|https://github.com/apache/cassandra/compare/cassandra-3.0...pauloricardomg:11850-cqlsh-3.0]|[branch|https://github.com/apache/cassandra/compare/cassandra-3.9...pauloricardomg:11850-cqlsh-3.9]|[branch|https://github.com/apache/cassandra/compare/trunk...pauloricardomg:11850-cqlsh]|[branch|https://github.com/riptano/cassandra-dtest/compare/master...pauloricardomg:11850]|
|[dtest|http://cassci.datastax.com/view/Dev/view/paulomotta/job/pauloricardomg-11850-cqlsh-2.1-dtest/lastCompletedBuild/testReport/]|[dtest|http://cassci.datastax.com/view/Dev/view/paulomotta/job/pauloricardomg-11850-cqlsh-2.2-dtest/lastCompletedBuild/testReport/]|[dtest|http://cassci.datastax.com/view/Dev/view/paulomotta/job/pauloricardomg-11850-cqlsh-3.0-dtest/lastCompletedBuild/testReport/]|[dtest|http://cassci.datastax.com/view/Dev/view/paulomotta/job/pauloricardomg-11850-cqlsh-3.9-dtest/lastCompletedBuild/testReport/]|[dtest|http://cassci.datastax.com/view/Dev/view/paulomotta/job/pauloricardomg-11850-cqlsh-dtest/lastCompletedBuild/testReport/]|

> cannot use cql since upgrading python to 2.7.11+
> 
>
> Key: CASSANDRA-11850
> URL: 

[jira] [Commented] (CASSANDRA-9507) range metrics are not updated for timeout and unavailable in StorageProxy

[Nachiket Patil (JIRA)]

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

Nachiket Patil commented on CASSANDRA-9507:
---

New patches attached with changes accommodating feedback.

> range metrics are not updated for timeout and unavailable in StorageProxy
> -
>
> Key: CASSANDRA-9507
> URL: https://issues.apache.org/jira/browse/CASSANDRA-9507
> Project: Cassandra
>  Issue Type: Bug
>  Components: Observability
>Reporter: sankalp kohli
>Assignee: Nachiket Patil
>Priority: Minor
> Attachments: CASANDRA-9507 trunk.diff, CASSANDRA-9507 v2.1.diff, 
> CASSANDRA-9507 v2.2.diff, CASSANDRA-9507 v3.0.diff
>
>
> Looking at the code, it looks like range metrics are not updated for timeouts 
> and unavailable. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (CASSANDRA-12241) Error connecting to cqlsh

[Tyler Hobbs (JIRA)]

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

Tyler Hobbs commented on CASSANDRA-12241:
-

It looks like {{rpc_address}} is set to the public IP, so connecting to 
127.0.0.1 (your first example) won't work.  Regarding the second connection 
attempt, I'm not sure why you're getting that error.  Do you have a firewall or 
iptables rules that could be causing problems?

> Error connecting to cqlsh
> -
>
> Key: CASSANDRA-12241
> URL: https://issues.apache.org/jira/browse/CASSANDRA-12241
> Project: Cassandra
>  Issue Type: Bug
>  Components: CQL
> Environment: Oracle Linux Server release 6.5
> Cassandra 3.0.8
> cqlsh 5.0.1
>Reporter: Eric Pedregosa
> Attachments: cassandra.log, cassandra.yaml.txt
>
>
> During Cassandra install we are experiencing this issue - "unable to connect 
> to servers" when running cqlsh.  Attached is the yaml config and log file.
> server 100.114.116.100
> [root@ushaplp00312la bin]# nodetool status
> Datacenter: USH
> ===
> Status=Up/Down
> |/ State=Normal/Leaving/Joining/Moving
> --  Address  Load   Tokens   Owns (effective)  Host ID
>Rack
> UN  100.114.116.102  125.17 KB  256  32.1% 
> b3366714-ecb3-46af-a3a1-f3b12648e358  RAC1
> UN  100.114.116.100  345.64 KB  256  33.4% 
> 83dfbd38-9233-41db-812d-7cd1aa34401b  RAC1
> UN  100.114.116.101  152.55 KB  256  34.5% 
> b8011e64-266f-4f18-a381-5f6dd5816af0  RAC1
> [root@ushaplp00312la bin]# cqlsh
> Connection error: ('Unable to connect to any servers', {'127.0.0.1': 
> error(111, "Tried connecting to [('127.0.0.1', 9042)]. Last error: Connection 
> refused")})
> [root@ushaplp00312la ~]# cqlsh 100.114.116.100 9160
> Connection error: ('Unable to connect to any servers', {'100.114.116.100': 
> ConnectionShutdown('Connection  100.114.116.100:9160 (closed)> is already closed',)})
> [root@ushaplp00312la ~]# lsof -i :9160
> COMMAND   PID USER   FD   TYPE  DEVICE SIZE/OFF NODE NAME
> java42158 openplatform   66u  IPv4 1889424  0t0  TCP 
> ushaplp00312la.tfayd.com:apani1 (LISTEN)



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (CASSANDRA-12106) Add ability to blacklist a CQL partition so all requests are ignored

[Joshua McKenzie (JIRA)]

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

Joshua McKenzie updated CASSANDRA-12106:

Reviewer: Benjamin Lerer

> Add ability to blacklist a CQL partition so all requests are ignored
> 
>
> Key: CASSANDRA-12106
> URL: https://issues.apache.org/jira/browse/CASSANDRA-12106
> Project: Cassandra
>  Issue Type: New Feature
>Reporter: Geoffrey Yu
>Assignee: Geoffrey Yu
>Priority: Minor
> Fix For: 4.x
>
> Attachments: 12106-trunk.txt
>
>
> Sometimes reads/writes to a given partition may cause problems due to the 
> data present. It would be useful to have a manual way to blacklist such 
> partitions so all read and write requests to them are rejected.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (CASSANDRA-9507) range metrics are not updated for timeout and unavailable in StorageProxy

[Nachiket Patil (JIRA)]

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

Nachiket Patil updated CASSANDRA-9507:
--
Status: Patch Available  (was: Open)

> range metrics are not updated for timeout and unavailable in StorageProxy
> -
>
> Key: CASSANDRA-9507
> URL: https://issues.apache.org/jira/browse/CASSANDRA-9507
> Project: Cassandra
>  Issue Type: Bug
>  Components: Observability
>Reporter: sankalp kohli
>Assignee: Nachiket Patil
>Priority: Minor
> Attachments: CASANDRA-9507 trunk.diff, CASSANDRA-9507 v2.1.diff, 
> CASSANDRA-9507 v2.2.diff, CASSANDRA-9507 v3.0.diff
>
>
> Looking at the code, it looks like range metrics are not updated for timeouts 
> and unavailable. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (CASSANDRA-10496) Make DTCS split partitions based on time during compaction

[Jeff Jirsa (JIRA)]

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

Jeff Jirsa commented on CASSANDRA-10496:


This ticket still needs to be done, but it's FAR less important for TWCS than 
it was for DTCS. I'll update the title, though. 

> Make DTCS split partitions based on time during compaction
> --
>
> Key: CASSANDRA-10496
> URL: https://issues.apache.org/jira/browse/CASSANDRA-10496
> Project: Cassandra
>  Issue Type: Improvement
>Reporter: Marcus Eriksson
>  Labels: dtcs
> Fix For: 3.x
>
>
> To avoid getting old data in new time windows with DTCS (or related, like 
> [TWCS|CASSANDRA-9666]), we need to split out old data into its own sstable 
> during compaction.
> My initial idea is to just create two sstables, when we create the compaction 
> task we state the start and end times for the window, and any data older than 
> the window will be put in its own sstable.
> By creating a single sstable with old data, we will incrementally get the 
> windows correct - say we have an sstable with these timestamps:
> {{[100, 99, 98, 97, 75, 50, 10]}}
> and we are compacting in window {{[100, 80]}} - we would create two sstables:
> {{[100, 99, 98, 97]}}, {{[75, 50, 10]}}, and the first window is now 
> 'correct'. The next compaction would compact in window {{[80, 60]}} and 
> create sstables {{[75]}}, {{[50, 10]}} etc.
> We will probably also want to base the windows on the newest data in the 
> sstables so that we actually have older data than the window.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (CASSANDRA-10496) Make DTCS/TWCS split partitions based on time during compaction

[Jeff Jirsa (JIRA)]

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

Jeff Jirsa updated CASSANDRA-10496:
---
Summary: Make DTCS/TWCS split partitions based on time during compaction  
(was: Make DTCS split partitions based on time during compaction)

> Make DTCS/TWCS split partitions based on time during compaction
> ---
>
> Key: CASSANDRA-10496
> URL: https://issues.apache.org/jira/browse/CASSANDRA-10496
> Project: Cassandra
>  Issue Type: Improvement
>Reporter: Marcus Eriksson
>  Labels: dtcs
> Fix For: 3.x
>
>
> To avoid getting old data in new time windows with DTCS (or related, like 
> [TWCS|CASSANDRA-9666]), we need to split out old data into its own sstable 
> during compaction.
> My initial idea is to just create two sstables, when we create the compaction 
> task we state the start and end times for the window, and any data older than 
> the window will be put in its own sstable.
> By creating a single sstable with old data, we will incrementally get the 
> windows correct - say we have an sstable with these timestamps:
> {{[100, 99, 98, 97, 75, 50, 10]}}
> and we are compacting in window {{[100, 80]}} - we would create two sstables:
> {{[100, 99, 98, 97]}}, {{[75, 50, 10]}}, and the first window is now 
> 'correct'. The next compaction would compact in window {{[80, 60]}} and 
> create sstables {{[75]}}, {{[50, 10]}} etc.
> We will probably also want to base the windows on the newest data in the 
> sstables so that we actually have older data than the window.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (CASSANDRA-12106) Add ability to blacklist a CQL partition so all requests are ignored

[Geoffrey Yu (JIRA)]

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

Geoffrey Yu updated CASSANDRA-12106:

Fix Version/s: 4.x
   Status: Patch Available  (was: Open)

I’ve attached a patch that implements this. There are a lot of changes, so I 
thought I’d highlight the high level approach I took to make it easier to 
understand what is going on.

This patch will let us blacklist any particular CQL partition, scoped by 
keyspace and table. Any reads/writes to a blacklisted partition will be 
rejected, and the client will receive a Read/WriteRejectedException 
accordingly. The mechanism for blacklisting a partition is exposed through a 
node tool command.

The approach to implementing this is to perform the rejection at the data 
replica level. This is so each node only needs to be aware of blacklisted 
partitions for ranges that it owns, allowing this to scale to larger clusters. 
The blacklist is stored in a new table under the {{system_distributed}} 
keyspace. Each node then maintains an in memory cache to store blacklist 
entries corresponding to its token ranges.

For single partition reads and writes, we reject the request as long as one 
replica responds with a rejection.

For partition range reads, we reject the request if there is a blacklisted 
partition within the range. 

CAS writes are rejected by the data nodes only on the prepare/promise step, and 
potentially when the coordinator performs the read before the propose/accept 
step. If the write proceeds past these places, the mutation will be allowed to 
be applied. 

A mutation in a batch log that is rejected will not be considered a "failure" 
in the replay. This means if all mutations were either applied successfully or 
rejected, then the replay would be considered successful and the batch log 
would be deleted.

Mutations that are rejected are not hinted. Any hints that are rejected when 
they are attempted to be applied will still be considered "successful" and 
deleted.

There are also changes included to help cover cache consistency when a node 
starts up, undergoes a range movement, and if it is decommissioned.

> Add ability to blacklist a CQL partition so all requests are ignored
> 
>
> Key: CASSANDRA-12106
> URL: https://issues.apache.org/jira/browse/CASSANDRA-12106
> Project: Cassandra
>  Issue Type: New Feature
>Reporter: Geoffrey Yu
>Assignee: Geoffrey Yu
>Priority: Minor
> Fix For: 4.x
>
> Attachments: 12106-trunk.txt
>
>
> Sometimes reads/writes to a given partition may cause problems due to the 
> data present. It would be useful to have a manual way to blacklist such 
> partitions so all read and write requests to them are rejected.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (CASSANDRA-12241) Error connecting to cqlsh

[Eric Pedregosa (JIRA)]

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

Eric Pedregosa updated CASSANDRA-12241:
---
Environment: 
Oracle Linux Server release 6.5
Cassandra 3.0.8
cqlsh 5.0.1


  was:
Oracle Linux Server release 6.5



> Error connecting to cqlsh
> -
>
> Key: CASSANDRA-12241
> URL: https://issues.apache.org/jira/browse/CASSANDRA-12241
> Project: Cassandra
>  Issue Type: Bug
>  Components: CQL
> Environment: Oracle Linux Server release 6.5
> Cassandra 3.0.8
> cqlsh 5.0.1
>Reporter: Eric Pedregosa
> Attachments: cassandra.log, cassandra.yaml.txt
>
>
> During Cassandra install we are experiencing this issue - "unable to connect 
> to servers" when running cqlsh.  Attached is the yaml config and log file.
> server 100.114.116.100
> [root@ushaplp00312la bin]# nodetool status
> Datacenter: USH
> ===
> Status=Up/Down
> |/ State=Normal/Leaving/Joining/Moving
> --  Address  Load   Tokens   Owns (effective)  Host ID
>Rack
> UN  100.114.116.102  125.17 KB  256  32.1% 
> b3366714-ecb3-46af-a3a1-f3b12648e358  RAC1
> UN  100.114.116.100  345.64 KB  256  33.4% 
> 83dfbd38-9233-41db-812d-7cd1aa34401b  RAC1
> UN  100.114.116.101  152.55 KB  256  34.5% 
> b8011e64-266f-4f18-a381-5f6dd5816af0  RAC1
> [root@ushaplp00312la bin]# cqlsh
> Connection error: ('Unable to connect to any servers', {'127.0.0.1': 
> error(111, "Tried connecting to [('127.0.0.1', 9042)]. Last error: Connection 
> refused")})
> [root@ushaplp00312la ~]# cqlsh 100.114.116.100 9160
> Connection error: ('Unable to connect to any servers', {'100.114.116.100': 
> ConnectionShutdown('Connection  100.114.116.100:9160 (closed)> is already closed',)})
> [root@ushaplp00312la ~]# lsof -i :9160
> COMMAND   PID USER   FD   TYPE  DEVICE SIZE/OFF NODE NAME
> java42158 openplatform   66u  IPv4 1889424  0t0  TCP 
> ushaplp00312la.tfayd.com:apani1 (LISTEN)



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (CASSANDRA-12106) Add ability to blacklist a CQL partition so all requests are ignored

[Geoffrey Yu (JIRA)]

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

Geoffrey Yu updated CASSANDRA-12106:

Attachment: 12106-trunk.txt

> Add ability to blacklist a CQL partition so all requests are ignored
> 
>
> Key: CASSANDRA-12106
> URL: https://issues.apache.org/jira/browse/CASSANDRA-12106
> Project: Cassandra
>  Issue Type: New Feature
>Reporter: Geoffrey Yu
>Assignee: Geoffrey Yu
>Priority: Minor
> Attachments: 12106-trunk.txt
>
>
> Sometimes reads/writes to a given partition may cause problems due to the 
> data present. It would be useful to have a manual way to blacklist such 
> partitions so all read and write requests to them are rejected.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (CASSANDRA-12241) Error connecting to cqlsh

[Eric Pedregosa (JIRA)]

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

Eric Pedregosa updated CASSANDRA-12241:
---
Description: 
During Cassandra install we are experiencing this issue - "unable to connect to 
servers" when running cqlsh.  Attached is the yaml config and log file.

server 100.114.116.100

[root@ushaplp00312la bin]# nodetool status
Datacenter: USH
===
Status=Up/Down
|/ State=Normal/Leaving/Joining/Moving
--  Address  Load   Tokens   Owns (effective)  Host ID  
 Rack
UN  100.114.116.102  125.17 KB  256  32.1% 
b3366714-ecb3-46af-a3a1-f3b12648e358  RAC1
UN  100.114.116.100  345.64 KB  256  33.4% 
83dfbd38-9233-41db-812d-7cd1aa34401b  RAC1
UN  100.114.116.101  152.55 KB  256  34.5% 
b8011e64-266f-4f18-a381-5f6dd5816af0  RAC1

[root@ushaplp00312la bin]# cqlsh
Connection error: ('Unable to connect to any servers', {'127.0.0.1': error(111, 
"Tried connecting to [('127.0.0.1', 9042)]. Last error: Connection refused")})

[root@ushaplp00312la ~]# cqlsh 100.114.116.100 9160
Connection error: ('Unable to connect to any servers', {'100.114.116.100': 
ConnectionShutdown('Connection  is already closed',)})

[root@ushaplp00312la ~]# lsof -i :9160
COMMAND   PID USER   FD   TYPE  DEVICE SIZE/OFF NODE NAME
java42158 openplatform   66u  IPv4 1889424  0t0  TCP 
ushaplp00312la.tfayd.com:apani1 (LISTEN)

  was:
"unable to connect to servers" when running cqlsh.  Attached is the yaml config 
and log file.

server 100.114.116.100

[root@ushaplp00312la bin]# nodetool status
Datacenter: USH
===
Status=Up/Down
|/ State=Normal/Leaving/Joining/Moving
--  Address  Load   Tokens   Owns (effective)  Host ID  
 Rack
UN  100.114.116.102  125.17 KB  256  32.1% 
b3366714-ecb3-46af-a3a1-f3b12648e358  RAC1
UN  100.114.116.100  345.64 KB  256  33.4% 
83dfbd38-9233-41db-812d-7cd1aa34401b  RAC1
UN  100.114.116.101  152.55 KB  256  34.5% 
b8011e64-266f-4f18-a381-5f6dd5816af0  RAC1

[root@ushaplp00312la bin]# cqlsh
Connection error: ('Unable to connect to any servers', {'127.0.0.1': error(111, 
"Tried connecting to [('127.0.0.1', 9042)]. Last error: Connection refused")})

[root@ushaplp00312la ~]# cqlsh 100.114.116.100 9160
Connection error: ('Unable to connect to any servers', {'100.114.116.100': 
ConnectionShutdown('Connection  is already closed',)})

[root@ushaplp00312la ~]# lsof -i :9160
COMMAND   PID USER   FD   TYPE  DEVICE SIZE/OFF NODE NAME
java42158 openplatform   66u  IPv4 1889424  0t0  TCP 
ushaplp00312la.tfayd.com:apani1 (LISTEN)


> Error connecting to cqlsh
> -
>
> Key: CASSANDRA-12241
> URL: https://issues.apache.org/jira/browse/CASSANDRA-12241
> Project: Cassandra
>  Issue Type: Bug
>  Components: CQL
> Environment: Oracle Linux Server release 6.5
>Reporter: Eric Pedregosa
> Attachments: cassandra.log, cassandra.yaml.txt
>
>
> During Cassandra install we are experiencing this issue - "unable to connect 
> to servers" when running cqlsh.  Attached is the yaml config and log file.
> server 100.114.116.100
> [root@ushaplp00312la bin]# nodetool status
> Datacenter: USH
> ===
> Status=Up/Down
> |/ State=Normal/Leaving/Joining/Moving
> --  Address  Load   Tokens   Owns (effective)  Host ID
>Rack
> UN  100.114.116.102  125.17 KB  256  32.1% 
> b3366714-ecb3-46af-a3a1-f3b12648e358  RAC1
> UN  100.114.116.100  345.64 KB  256  33.4% 
> 83dfbd38-9233-41db-812d-7cd1aa34401b  RAC1
> UN  100.114.116.101  152.55 KB  256  34.5% 
> b8011e64-266f-4f18-a381-5f6dd5816af0  RAC1
> [root@ushaplp00312la bin]# cqlsh
> Connection error: ('Unable to connect to any servers', {'127.0.0.1': 
> error(111, "Tried connecting to [('127.0.0.1', 9042)]. Last error: Connection 
> refused")})
> [root@ushaplp00312la ~]# cqlsh 100.114.116.100 9160
> Connection error: ('Unable to connect to any servers', {'100.114.116.100': 
> ConnectionShutdown('Connection  100.114.116.100:9160 (closed)> is already closed',)})
> [root@ushaplp00312la ~]# lsof -i :9160
> COMMAND   PID USER   FD   TYPE  DEVICE SIZE/OFF NODE NAME
> java42158 openplatform   66u  IPv4 1889424  0t0  TCP 
> ushaplp00312la.tfayd.com:apani1 (LISTEN)



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (CASSANDRA-9054) Break DatabaseDescriptor up into multiple classes.

[Blake Eggleston (JIRA)]

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

Blake Eggleston commented on CASSANDRA-9054:


bq. We can (and should) take an incremental approach to changes like this 
instead of Big-Banging it.

Agreed.

So the refactor in general seems good, but there are things that could be 
cleaned up a bit: 

AuthSetup:
* I think AuthConfig would be a more descriptive name for this class
* Instead of explaining where it was refactored from, could you explain the 
purpose of the class, and use the javadoc format?
* there are empty '//' comments in applyAuthz method

StorageService:
* You've added a todo in the constructor about only registering verb handlers 
in daemon mode. Although the messaging service will be instantiated here, 
nothing important gets started as far as I can tell. I think you can just leave 
this as is.

Misc:
* FBUtilities / DatabaseDescriptor: Could you explain the reasoning behind the 
class level comment, and use the javadoc format?
* There are unused {{Config}} or {{DatabaseDescriptor}} imports in the 
following classes: CacheService, CompactionManager, CQLSSTableWriterLongTest, 
SSTableExpiredBlockers, SSTableLevelResetter, SSTableLoaderTest, 
SSTableOfflineRelevel, StandaloneScrubber, StandaloneSplitter, & 
StandaloneVerifier, StorageService

> Break DatabaseDescriptor up into multiple classes.
> --
>
> Key: CASSANDRA-9054
> URL: https://issues.apache.org/jira/browse/CASSANDRA-9054
> Project: Cassandra
>  Issue Type: Improvement
>Reporter: Jeremiah Jordan
>Assignee: Robert Stupp
> Fix For: 3.x
>
>
> Right now to get at Config stuff you go through DatabaseDescriptor.  But when 
> you instantiate DatabaseDescriptor it actually opens system tables and such, 
> which triggers commit log replays, and other things if the right flags aren't 
> set ahead of time.  This makes getting at config stuff from tools annoying, 
> as you have to be very careful about instantiation orders.
> It would be nice if we could break DatabaseDescriptor up into multiple 
> classes, so that getting at config stuff from tools wasn't such a pain.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (CASSANDRA-12241) Error connecting to cqlsh

[Eric Pedregosa (JIRA)]

Eric Pedregosa created CASSANDRA-12241:
--

 Summary: Error connecting to cqlsh
 Key: CASSANDRA-12241
 URL: https://issues.apache.org/jira/browse/CASSANDRA-12241
 Project: Cassandra
  Issue Type: Bug
  Components: CQL
 Environment: Oracle Linux Server release 6.5

Reporter: Eric Pedregosa
 Attachments: cassandra.log, cassandra.yaml.txt

"unable to connect to servers" when running cqlsh.  Attached is the yaml config 
and log file.

server 100.114.116.100

[root@ushaplp00312la bin]# nodetool status
Datacenter: USH
===
Status=Up/Down
|/ State=Normal/Leaving/Joining/Moving
--  Address  Load   Tokens   Owns (effective)  Host ID  
 Rack
UN  100.114.116.102  125.17 KB  256  32.1% 
b3366714-ecb3-46af-a3a1-f3b12648e358  RAC1
UN  100.114.116.100  345.64 KB  256  33.4% 
83dfbd38-9233-41db-812d-7cd1aa34401b  RAC1
UN  100.114.116.101  152.55 KB  256  34.5% 
b8011e64-266f-4f18-a381-5f6dd5816af0  RAC1

[root@ushaplp00312la bin]# cqlsh
Connection error: ('Unable to connect to any servers', {'127.0.0.1': error(111, 
"Tried connecting to [('127.0.0.1', 9042)]. Last error: Connection refused")})

[root@ushaplp00312la ~]# cqlsh 100.114.116.100 9160
Connection error: ('Unable to connect to any servers', {'100.114.116.100': 
ConnectionShutdown('Connection  is already closed',)})

[root@ushaplp00312la ~]# lsof -i :9160
COMMAND   PID USER   FD   TYPE  DEVICE SIZE/OFF NODE NAME
java42158 openplatform   66u  IPv4 1889424  0t0  TCP 
ushaplp00312la.tfayd.com:apani1 (LISTEN)



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (CASSANDRA-12240) Broken materialized view compatibility

[JIRA]

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

Gábor Auth commented on CASSANDRA-12240:


I think, the root cause is same in the case of the 
https://issues.apache.org/jira/browse/CASSANDRA-12224 upgrade issue.

> Broken materialized view compatibility
> --
>
> Key: CASSANDRA-12240
> URL: https://issues.apache.org/jira/browse/CASSANDRA-12240
> Project: Cassandra
>  Issue Type: Bug
> Environment: datastax-ddc-3.7.0, Centos 7, x86_64
>Reporter: Gábor Auth
>Priority: Blocker
>
> The behavior of the materialized view is not compatible with the previous 
> versions of Cassandra, here is the simple test case, it is works from 3.3.0 
> to 3.6.0. I've reproduced the issue with a single node installation and our 
> eight node test environment too of the 3.7.0 version:
> {code}
> CREATE KEYSPACE test WITH replication = {'class': 'SimpleStrategy', 
> 'replication_factor' : 1};
> USE test;
> CREATE TABLE test (id timeuuid PRIMARY KEY, segment text, xy text);
> CREATE MATERIALIZED VIEW test_by_segment AS SELECT * FROM test WHERE segment 
> IS NOT NULL PRIMARY KEY (segment, id);
> CREATE MATERIALIZED VIEW test_by_xy AS SELECT * FROM test WHERE xy IS NOT 
> NULL PRIMARY KEY (xy, id);
> UPDATE test SET segment=null, xy='{"x":0,"y":0}' WHERE 
> id=8868dd90-fa48-11e3-afc8-c53da2f1a8ef;
> UPDATE test SET xy='{"x":0,"y":0}' WHERE 
> id=8868dd90-fa48-11e3-afc8-c53da2f1a8ef;
> {code}
> The result of the `cqlsh` console:
> {code}
> WriteTimeout: code=1100 [Coordinator node timed out waiting for replica 
> nodes' responses] message="Operation timed out - received only 0 responses." 
> info={'received_responses': 0, 'required_responses': 1, 'consistency': 'ONE'}
> {code}
> The stack trace in the server log:
> {code}
> ERROR 19:40:19 Unknown exception caught while attempting to update 
> MaterializedView! test
> java.lang.AssertionError: We shouldn't have got there is the base row had no 
> associated entry
> at 
> org.apache.cassandra.db.view.ViewUpdateGenerator.computeLivenessInfoForEntry(ViewUpdateGenerator.java:455)
>  ~[apache-cassandra-3.7.0.jar:3.7.0]
> at 
> org.apache.cassandra.db.view.ViewUpdateGenerator.updateEntry(ViewUpdateGenerator.java:273)
>  ~[apache-cassandra-3.7.0.jar:3.7.0]
> at 
> org.apache.cassandra.db.view.ViewUpdateGenerator.addBaseTableUpdate(ViewUpdateGenerator.java:127)
>  ~[apache-cassandra-3.7.0.jar:3.7.0]
> at 
> org.apache.cassandra.db.view.TableViews.addToViewUpdateGenerators(TableViews.java:403)
>  ~[apache-cassandra-3.7.0.jar:3.7.0]
> at 
> org.apache.cassandra.db.view.TableViews.generateViewUpdates(TableViews.java:236)
>  ~[apache-cassandra-3.7.0.jar:3.7.0]
> at 
> org.apache.cassandra.db.view.TableViews.pushViewReplicaUpdates(TableViews.java:140)
>  ~[apache-cassandra-3.7.0.jar:3.7.0]
> at org.apache.cassandra.db.Keyspace.apply(Keyspace.java:514) 
> [apache-cassandra-3.7.0.jar:3.7.0]
> at org.apache.cassandra.db.Keyspace.apply(Keyspace.java:399) 
> [apache-cassandra-3.7.0.jar:3.7.0]
> at org.apache.cassandra.db.Mutation.applyFuture(Mutation.java:202) 
> [apache-cassandra-3.7.0.jar:3.7.0]
> at org.apache.cassandra.db.Mutation.apply(Mutation.java:214) 
> [apache-cassandra-3.7.0.jar:3.7.0]
> at org.apache.cassandra.db.Mutation.apply(Mutation.java:228) 
> [apache-cassandra-3.7.0.jar:3.7.0]
> at 
> org.apache.cassandra.service.StorageProxy$8.runMayThrow(StorageProxy.java:1343)
>  ~[apache-cassandra-3.7.0.jar:3.7.0]
> at 
> org.apache.cassandra.service.StorageProxy$LocalMutationRunnable.run(StorageProxy.java:2519)
>  ~[apache-cassandra-3.7.0.jar:3.7.0]
> at 
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) 
> ~[na:1.8.0_91]
> at 
> org.apache.cassandra.concurrent.AbstractLocalAwareExecutorService$FutureTask.run(AbstractLocalAwareExecutorService.java:164)
>  ~[apache-cassandra-3.7.0.jar:3.7.0]
> at 
> org.apache.cassandra.concurrent.AbstractLocalAwareExecutorService$LocalSessionFutureTask.run(AbstractLocalAwareExecutorService.java:136)
>  ~[apache-cassandra-3.7.0.jar:3.7.0]
> at org.apache.cassandra.concurrent.SEPWorker.run(SEPWorker.java:105) 
> ~[apache-cassandra-3.7.0.jar:3.7.0]
> at java.lang.Thread.run(Thread.java:745) ~[na:1.8.0_91]
> WARN  19:40:19 Uncaught exception on thread 
> Thread[SharedPool-Worker-2,5,main]: {}
> java.lang.AssertionError: We shouldn't have got there is the base row had no 
> associated entry
> at 
> org.apache.cassandra.db.view.ViewUpdateGenerator.computeLivenessInfoForEntry(ViewUpdateGenerator.java:455)
>  ~[apache-cassandra-3.7.0.jar:3.7.0]
> at 
> 

[jira] [Commented] (CASSANDRA-10496) Make DTCS split partitions based on time during compaction

[Wei Deng (JIRA)]

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

Wei Deng commented on CASSANDRA-10496:
--

A lot of things have changed in the last couple of months. Now that TWCS is the 
official compaction strategy for time-series data going forward (and DTCS going 
obsolete), shall we update the title of this JIRA to "Make TWCS split 
partitions based on time during compaction" and revisit the priority of this 
JIRA? I'm sure we might want to review a few other outstanding enhancement 
JIRAs that were originally intended for DTCS as well.

> Make DTCS split partitions based on time during compaction
> --
>
> Key: CASSANDRA-10496
> URL: https://issues.apache.org/jira/browse/CASSANDRA-10496
> Project: Cassandra
>  Issue Type: Improvement
>Reporter: Marcus Eriksson
>  Labels: dtcs
> Fix For: 3.x
>
>
> To avoid getting old data in new time windows with DTCS (or related, like 
> [TWCS|CASSANDRA-9666]), we need to split out old data into its own sstable 
> during compaction.
> My initial idea is to just create two sstables, when we create the compaction 
> task we state the start and end times for the window, and any data older than 
> the window will be put in its own sstable.
> By creating a single sstable with old data, we will incrementally get the 
> windows correct - say we have an sstable with these timestamps:
> {{[100, 99, 98, 97, 75, 50, 10]}}
> and we are compacting in window {{[100, 80]}} - we would create two sstables:
> {{[100, 99, 98, 97]}}, {{[75, 50, 10]}}, and the first window is now 
> 'correct'. The next compaction would compact in window {{[80, 60]}} and 
> create sstables {{[75]}}, {{[50, 10]}} etc.
> We will probably also want to base the windows on the newest data in the 
> sstables so that we actually have older data than the window.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Comment Edited] (CASSANDRA-11465) dtest failure in cql_tracing_test.TestCqlTracing.tracing_unknown_impl_test

[Jim Witschey (JIRA)]

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

Jim Witschey edited comment on CASSANDRA-11465 at 7/19/16 8:02 PM:
---

I ran the following script:

{code}
for i in `seq 30` ; do
echo iteration $i
PRINT_DEBUG=true DEBUG=true 
CASSANDRA_VERSION=github:stef1927/11465-cqlsh-3.9 
TRACE=org.apache.cassandra.tracing.TraceStateImpl nosetests cql_tracing_test.py
killall -9 java
done

for i in `seq 30` ; do
echo iteration $i
PRINT_DEBUG=true DEBUG=true 
CASSANDRA_VERSION=github:stef1927/11465-cqlsh 
TRACE=org.apache.cassandra.tracing.TraceStateImpl nosetests cql_tracing_test.py
killall -9 java
done
{code}

and saw no failures:

https://gist.github.com/072692334800285afc8d362165cb37a6

EDIT: I did so on an {{m3.xlarge}} instance on openstack.


was (Author: mambocab):
I ran the following script:

{code}
for i in `seq 30` ; do
echo iteration $i
PRINT_DEBUG=true DEBUG=true 
CASSANDRA_VERSION=github:stef1927/11465-cqlsh-3.9 
TRACE=org.apache.cassandra.tracing.TraceStateImpl nosetests cql_tracing_test.py
killall -9 java
done

for i in `seq 30` ; do
echo iteration $i
PRINT_DEBUG=true DEBUG=true 
CASSANDRA_VERSION=github:stef1927/11465-cqlsh 
TRACE=org.apache.cassandra.tracing.TraceStateImpl nosetests cql_tracing_test.py
killall -9 java
done
{code}

and saw no failures:

https://gist.github.com/072692334800285afc8d362165cb37a6

> dtest failure in cql_tracing_test.TestCqlTracing.tracing_unknown_impl_test
> --
>
> Key: CASSANDRA-11465
> URL: https://issues.apache.org/jira/browse/CASSANDRA-11465
> Project: Cassandra
>  Issue Type: Bug
>Reporter: Philip Thompson
>Assignee: Stefania
>  Labels: dtest
>
> Failing on the following assert, on trunk only: 
> {{self.assertEqual(len(errs[0]), 1)}}
> Is not failing consistently.
> example failure:
> http://cassci.datastax.com/job/trunk_dtest/1087/testReport/cql_tracing_test/TestCqlTracing/tracing_unknown_impl_test
> Failed on CassCI build trunk_dtest #1087



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (CASSANDRA-11465) dtest failure in cql_tracing_test.TestCqlTracing.tracing_unknown_impl_test

[Jim Witschey (JIRA)]

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

Jim Witschey commented on CASSANDRA-11465:
--

I ran the following script:

{code}
for i in `seq 30` ; do
echo iteration $i
PRINT_DEBUG=true DEBUG=true 
CASSANDRA_VERSION=github:stef1927/11465-cqlsh-3.9 
TRACE=org.apache.cassandra.tracing.TraceStateImpl nosetests cql_tracing_test.py
killall -9 java
done

for i in `seq 30` ; do
echo iteration $i
PRINT_DEBUG=true DEBUG=true 
CASSANDRA_VERSION=github:stef1927/11465-cqlsh 
TRACE=org.apache.cassandra.tracing.TraceStateImpl nosetests cql_tracing_test.py
killall -9 java
done
{code}

and saw no failures:

https://gist.github.com/072692334800285afc8d362165cb37a6

> dtest failure in cql_tracing_test.TestCqlTracing.tracing_unknown_impl_test
> --
>
> Key: CASSANDRA-11465
> URL: https://issues.apache.org/jira/browse/CASSANDRA-11465
> Project: Cassandra
>  Issue Type: Bug
>Reporter: Philip Thompson
>Assignee: Stefania
>  Labels: dtest
>
> Failing on the following assert, on trunk only: 
> {{self.assertEqual(len(errs[0]), 1)}}
> Is not failing consistently.
> example failure:
> http://cassci.datastax.com/job/trunk_dtest/1087/testReport/cql_tracing_test/TestCqlTracing/tracing_unknown_impl_test
> Failed on CassCI build trunk_dtest #1087



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (CASSANDRA-12240) Broken materialized view compatibility

[JIRA]

Gábor Auth created CASSANDRA-12240:
--

 Summary: Broken materialized view compatibility
 Key: CASSANDRA-12240
 URL: https://issues.apache.org/jira/browse/CASSANDRA-12240
 Project: Cassandra
  Issue Type: Bug
 Environment: datastax-ddc-3.7.0, Centos 7, x86_64
Reporter: Gábor Auth
Priority: Blocker


The behavior of the materialized view is not compatible with the previous 
versions of Cassandra, here is the simple test case, it is works from 3.3.0 to 
3.6.0. I've reproduced the issue with a single node installation and our eight 
node test environment too of the 3.7.0 version:
{code}
CREATE KEYSPACE test WITH replication = {'class': 'SimpleStrategy', 
'replication_factor' : 1};
USE test;

CREATE TABLE test (id timeuuid PRIMARY KEY, segment text, xy text);
CREATE MATERIALIZED VIEW test_by_segment AS SELECT * FROM test WHERE segment IS 
NOT NULL PRIMARY KEY (segment, id);
CREATE MATERIALIZED VIEW test_by_xy AS SELECT * FROM test WHERE xy IS NOT NULL 
PRIMARY KEY (xy, id);

UPDATE test SET segment=null, xy='{"x":0,"y":0}' WHERE 
id=8868dd90-fa48-11e3-afc8-c53da2f1a8ef;
UPDATE test SET xy='{"x":0,"y":0}' WHERE 
id=8868dd90-fa48-11e3-afc8-c53da2f1a8ef;
{code}

The result of the `cqlsh` console:
{code}
WriteTimeout: code=1100 [Coordinator node timed out waiting for replica nodes' 
responses] message="Operation timed out - received only 0 responses." 
info={'received_responses': 0, 'required_responses': 1, 'consistency': 'ONE'}
{code}

The stack trace in the server log:
{code}
ERROR 19:40:19 Unknown exception caught while attempting to update 
MaterializedView! test
java.lang.AssertionError: We shouldn't have got there is the base row had no 
associated entry
at 
org.apache.cassandra.db.view.ViewUpdateGenerator.computeLivenessInfoForEntry(ViewUpdateGenerator.java:455)
 ~[apache-cassandra-3.7.0.jar:3.7.0]
at 
org.apache.cassandra.db.view.ViewUpdateGenerator.updateEntry(ViewUpdateGenerator.java:273)
 ~[apache-cassandra-3.7.0.jar:3.7.0]
at 
org.apache.cassandra.db.view.ViewUpdateGenerator.addBaseTableUpdate(ViewUpdateGenerator.java:127)
 ~[apache-cassandra-3.7.0.jar:3.7.0]
at 
org.apache.cassandra.db.view.TableViews.addToViewUpdateGenerators(TableViews.java:403)
 ~[apache-cassandra-3.7.0.jar:3.7.0]
at 
org.apache.cassandra.db.view.TableViews.generateViewUpdates(TableViews.java:236)
 ~[apache-cassandra-3.7.0.jar:3.7.0]
at 
org.apache.cassandra.db.view.TableViews.pushViewReplicaUpdates(TableViews.java:140)
 ~[apache-cassandra-3.7.0.jar:3.7.0]
at org.apache.cassandra.db.Keyspace.apply(Keyspace.java:514) 
[apache-cassandra-3.7.0.jar:3.7.0]
at org.apache.cassandra.db.Keyspace.apply(Keyspace.java:399) 
[apache-cassandra-3.7.0.jar:3.7.0]
at org.apache.cassandra.db.Mutation.applyFuture(Mutation.java:202) 
[apache-cassandra-3.7.0.jar:3.7.0]
at org.apache.cassandra.db.Mutation.apply(Mutation.java:214) 
[apache-cassandra-3.7.0.jar:3.7.0]
at org.apache.cassandra.db.Mutation.apply(Mutation.java:228) 
[apache-cassandra-3.7.0.jar:3.7.0]
at 
org.apache.cassandra.service.StorageProxy$8.runMayThrow(StorageProxy.java:1343) 
~[apache-cassandra-3.7.0.jar:3.7.0]
at 
org.apache.cassandra.service.StorageProxy$LocalMutationRunnable.run(StorageProxy.java:2519)
 ~[apache-cassandra-3.7.0.jar:3.7.0]
at 
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) 
~[na:1.8.0_91]
at 
org.apache.cassandra.concurrent.AbstractLocalAwareExecutorService$FutureTask.run(AbstractLocalAwareExecutorService.java:164)
 ~[apache-cassandra-3.7.0.jar:3.7.0]
at 
org.apache.cassandra.concurrent.AbstractLocalAwareExecutorService$LocalSessionFutureTask.run(AbstractLocalAwareExecutorService.java:136)
 ~[apache-cassandra-3.7.0.jar:3.7.0]
at org.apache.cassandra.concurrent.SEPWorker.run(SEPWorker.java:105) 
~[apache-cassandra-3.7.0.jar:3.7.0]
at java.lang.Thread.run(Thread.java:745) ~[na:1.8.0_91]
WARN  19:40:19 Uncaught exception on thread Thread[SharedPool-Worker-2,5,main]: 
{}
java.lang.AssertionError: We shouldn't have got there is the base row had no 
associated entry
at 
org.apache.cassandra.db.view.ViewUpdateGenerator.computeLivenessInfoForEntry(ViewUpdateGenerator.java:455)
 ~[apache-cassandra-3.7.0.jar:3.7.0]
at 
org.apache.cassandra.db.view.ViewUpdateGenerator.updateEntry(ViewUpdateGenerator.java:273)
 ~[apache-cassandra-3.7.0.jar:3.7.0]
at 
org.apache.cassandra.db.view.ViewUpdateGenerator.addBaseTableUpdate(ViewUpdateGenerator.java:127)
 ~[apache-cassandra-3.7.0.jar:3.7.0]
at 
org.apache.cassandra.db.view.TableViews.addToViewUpdateGenerators(TableViews.java:403)
 ~[apache-cassandra-3.7.0.jar:3.7.0]
at 
org.apache.cassandra.db.view.TableViews.generateViewUpdates(TableViews.java:236)
 ~[apache-cassandra-3.7.0.jar:3.7.0]
at 

[jira] [Commented] (CASSANDRA-12039) Add an index callback to be notified post bootstrap and before joining the ring

[Sergio Bossa (JIRA)]

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

Sergio Bossa commented on CASSANDRA-12039:
--

[~beobal],

thanks for your comments, see my answers below:

bq. Pre-join tasks are not executed if a node is started in write survey mode 
and then fully joins the ring later.

Good point, I can fix this.

bq. If bootstrap fails and is subsequently resumed, pre-join tasks are not 
executed on its completion.

I think this is ok, as the node will have already joined the ring, and this is 
mainly a pre-join callback.

bq. Index::getPreJoinTask should have a default no-op implementation

I'm not sure I get this: I provided an inline "null" implementation similar to 
what happens with other {{get*Task}} methods, what should I do differently?

bq. I think it would be sufficient to add some debug logging to 
StorageService::executePreJoinTasks and check for that in the node logs.

Sure I can do that.

> Add an index callback to be notified post bootstrap and before joining the 
> ring
> ---
>
> Key: CASSANDRA-12039
> URL: https://issues.apache.org/jira/browse/CASSANDRA-12039
> Project: Cassandra
>  Issue Type: New Feature
>Reporter: Sergio Bossa
>Assignee: Sergio Bossa
>
> Custom index implementations might need to be notified when the node finishes 
> bootstrapping in order to execute some blocking tasks before the node itself 
> goes into NORMAL state.
> This is a proposal to add such functionality, which should roughly require 
> the following:
> 1) Add a {{getPostBootstrapTask}} callback to the {{Index}} interface.
> 2) Add an {{executePostBootstrapBlockingTasks}} method to 
> {{SecondaryIndexManager}} calling into the previously mentioned callback.
> 3) Hook that into {{StorageService#joinTokenRing}}.
> Thoughts?



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (CASSANDRA-12161) dtest failure in counter_tests.TestCounters.upgrade_test

[Alex Petrov (JIRA)]

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

Alex Petrov commented on CASSANDRA-12161:
-

I can see no correlation between the error log (with timestamp {{02:45:08,632}} 
and node logs with timestamps around {{21:05:29,735}}. 
Moreover, it seems that error log is unrelated node dir {{dtest-HnE_0O}} and 
error log has {{dtest-0jFLWr}}.
I've tried running the test several dozen times locally and could not reproduce 
it.

> dtest failure in counter_tests.TestCounters.upgrade_test
> 
>
> Key: CASSANDRA-12161
> URL: https://issues.apache.org/jira/browse/CASSANDRA-12161
> Project: Cassandra
>  Issue Type: Bug
>Reporter: Sean McCarthy
>Assignee: Alex Petrov
>  Labels: dtest
> Attachments: node1.log, node2.log
>
>
> example failure:
> http://cassci.datastax.com/job/cassandra-2.1_dtest_jdk8/244/testReport/counter_tests/TestCounters/upgrade_test
> Failed on CassCI build cassandra-2.1_dtest_jdk8 #244
> {code}
> Standard Output
> Unexpected error in node2 log, error: 
> ERROR [Reference-Reaper:1] 2016-07-07 02:45:08,632 Ref.java:199 - LEAK 
> DETECTED: a reference 
> (org.apache.cassandra.utils.concurrent.Ref$State@25829106) to class 
> org.apache.cassandra.utils.concurrent.WrappedSharedCloseable$1@725969862:[Memory@[0..4),
>  Memory@[0..e)] was not released before the reference was garbage collected
> Unexpected error in node2 log, error: 
> ERROR [Reference-Reaper:1] 2016-07-07 02:45:08,633 Ref.java:199 - LEAK 
> DETECTED: a reference 
> (org.apache.cassandra.utils.concurrent.Ref$State@2f7afa76) to class 
> org.apache.cassandra.utils.concurrent.WrappedSharedCloseable$1@1786274301:[[OffHeapBitSet]]
>  was not released before the reference was garbage collected
> Unexpected error in node2 log, error: 
> ERROR [Reference-Reaper:1] 2016-07-07 02:45:08,634 Ref.java:199 - LEAK 
> DETECTED: a reference 
> (org.apache.cassandra.utils.concurrent.Ref$State@5b43d715) to class 
> org.apache.cassandra.io.sstable.SSTableReader$DescriptorTypeTidy@1540918496:/tmp/dtest-0jFLWr/test/node2/data0/system/schema_keyspaces-b0f2235744583cdb9631c43e59ce3676/system-schema_keyspaces-ka-1
>  was not released before the reference was garbage collected
> Unexpected error in node2 log, error: 
> ERROR [Reference-Reaper:1] 2016-07-07 02:45:08,634 Ref.java:199 - LEAK 
> DETECTED: a reference 
> (org.apache.cassandra.utils.concurrent.Ref$State@230964a7) to class 
> org.apache.cassandra.io.util.CompressedPoolingSegmentedFile$Cleanup@173514418:/tmp/dtest-0jFLWr/test/node2/data0/system/schema_keyspaces-b0f2235744583cdb9631c43e59ce3676/system-schema_keyspaces-ka-1-Data.db
>  was not released before the reference was garbage collected
> Unexpected error in node2 log, error: 
> ERROR [Reference-Reaper:1] 2016-07-07 02:45:08,634 Ref.java:199 - LEAK 
> DETECTED: a reference 
> (org.apache.cassandra.utils.concurrent.Ref$State@4f691b92) to class 
> org.apache.cassandra.io.util.MmappedSegmentedFile$Cleanup@1346973971:/tmp/dtest-0jFLWr/test/node2/data0/system/schema_keyspaces-b0f2235744583cdb9631c43e59ce3676/system-schema_keyspaces-ka-1-Index.db
>  was not released before the reference was garbage collected
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (CASSANDRA-12236) RTE from new CDC column breaks in flight queries.

[Philip Thompson (JIRA)]

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

Philip Thompson commented on CASSANDRA-12236:
-

I'm unsure, but looking at CASSANDRA-12192, it seems we get this error in a 
mixed version cluster that has no schema changes during the upgrade.

> RTE from new CDC column breaks in flight queries.
> -
>
> Key: CASSANDRA-12236
> URL: https://issues.apache.org/jira/browse/CASSANDRA-12236
> Project: Cassandra
>  Issue Type: Bug
>Reporter: Jeremiah Jordan
>Priority: Blocker
> Fix For: 3.8
>
>
> This RTE is not harmless. It will cause the internode connection to break 
> which will cause all in flight requests between these nodes to die/timeout.
> {noformat}
> - Due to changes in schema migration handling and the storage format 
> after 3.0, you will
>   see error messages such as:
>  "java.lang.RuntimeException: Unknown column cdc during 
> deserialization"
>   in your system logs on a mixed-version cluster during upgrades. This 
> error message
>   is harmless and due to the 3.8 nodes having cdc added to their schema 
> tables while
>   the <3.8 nodes do not. This message should cease once all nodes are 
> upgraded to 3.8.
>   As always, refrain from schema changes during cluster upgrades.
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

cassandra git commit: Ninja: update cqlsh completion tests for CASSANDRA-8844

[tylerhobbs]

Repository: cassandra
Updated Branches:
  refs/heads/trunk d14052e99 -> cc582855e


Ninja: update cqlsh completion tests for CASSANDRA-8844

In CASSANDRA-8844, a new 'cdc' table option was added.  The python
driver added this as a recognized option, which caused it to show up in
cqlsh autocomplete suggestions.  However, the cqlsh tests were not
updated to match this.

This should fix the following failing tests:
 - test_complete_in_create_table
 - test_complete_in_create_columnfamily


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

Branch: refs/heads/trunk
Commit: cc582855ea95789c0761ddb6ab7837573eab2938
Parents: d14052e
Author: Tyler Hobbs 
Authored: Tue Jul 19 14:40:55 2016 -0500
Committer: Tyler Hobbs 
Committed: Tue Jul 19 14:40:55 2016 -0500

--
 pylib/cqlshlib/test/test_cqlsh_completion.py | 7 +++
 1 file changed, 3 insertions(+), 4 deletions(-)
--


http://git-wip-us.apache.org/repos/asf/cassandra/blob/cc582855/pylib/cqlshlib/test/test_cqlsh_completion.py
--
diff --git a/pylib/cqlshlib/test/test_cqlsh_completion.py 
b/pylib/cqlshlib/test/test_cqlsh_completion.py
index 33fe07c..df4f7e8 100644
--- a/pylib/cqlshlib/test/test_cqlsh_completion.py
+++ b/pylib/cqlshlib/test/test_cqlsh_completion.py
@@ -595,7 +595,7 @@ class TestCqlshCompletion(CqlshCompletionCase):
  'memtable_flush_period_in_ms',
  'read_repair_chance', 'CLUSTERING',
  'COMPACT', 'caching', 'comment',
- 'min_index_interval', 
'speculative_retry'])
+ 'min_index_interval', 
'speculative_retry', 'cdc'])
 self.trycompletions(prefix + ' new_table (col_a int PRIMARY KEY) WITH 
',
 choices=['bloom_filter_fp_chance', 'compaction',
  'compression',
@@ -605,7 +605,7 @@ class TestCqlshCompletion(CqlshCompletionCase):
  'memtable_flush_period_in_ms',
  'read_repair_chance', 'CLUSTERING',
  'COMPACT', 'caching', 'comment',
- 'min_index_interval', 
'speculative_retry'])
+ 'min_index_interval', 
'speculative_retry', 'cdc'])
 self.trycompletions(prefix + ' new_table (col_a int PRIMARY KEY) WITH 
bloom_filter_fp_chance ',
 immediate='= ')
 self.trycompletions(prefix + ' new_table (col_a int PRIMARY KEY) WITH 
bloom_filter_fp_chance = ',
@@ -653,7 +653,7 @@ class TestCqlshCompletion(CqlshCompletionCase):
  'memtable_flush_period_in_ms',
  'read_repair_chance', 'CLUSTERING',
  'COMPACT', 'caching', 'comment',
- 'min_index_interval', 
'speculative_retry'])
+ 'min_index_interval', 
'speculative_retry', 'cdc'])
 self.trycompletions(prefix + " new_table (col_a int PRIMARY KEY) WITH 
compaction = "
 + "{'class': 'DateTieredCompactionStrategy', '",
 choices=['base_time_seconds', 
'max_sstable_age_days',
@@ -669,7 +669,6 @@ class TestCqlshCompletion(CqlshCompletionCase):
  'enabled', 
'unchecked_tombstone_compaction',
  'only_purge_repaired_tombstones'])
 
-
 def test_complete_in_create_columnfamily(self):
 self.trycompletions('CREATE C', choices=['COLUMNFAMILY', 'CUSTOM'])
 self.trycompletions('CREATE CO', immediate='LUMNFAMILY ')

[jira] [Updated] (CASSANDRA-11951) dtest failure in user_functions_test.TestUserFunctions.test_migration

[Philip Thompson (JIRA)]

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

Philip Thompson updated CASSANDRA-11951:

   Resolution: Fixed
 Reviewer: Jim Witschey  (was: Russ Hatch)
Fix Version/s: (was: 3.9)
   Status: Resolved  (was: Patch Available)

> dtest failure in user_functions_test.TestUserFunctions.test_migration
> -
>
> Key: CASSANDRA-11951
> URL: https://issues.apache.org/jira/browse/CASSANDRA-11951
> Project: Cassandra
>  Issue Type: Test
>Reporter: Sean McCarthy
>Assignee: Philip Thompson
>  Labels: dtest
> Attachments: node1.log, node1_debug.log, node2.log, node2_debug.log, 
> node3.log, node3_debug.log
>
>
> example failure:
> http://cassci.datastax.com/job/trunk_offheap_dtest/234/testReport/user_functions_test/TestUserFunctions/test_migration
> Failed on CassCI build trunk_offheap_dtest #234
> Logs are attached.
> {code}
> Stacktrace
>   File "/usr/lib/python2.7/unittest/case.py", line 329, in run
> testMethod()
>   File "/home/automaton/cassandra-dtest/user_functions_test.py", line 50, in 
> test_migration
> session2.execute("use ks")
>   File "cassandra/cluster.py", line 1706, in 
> cassandra.cluster.Session.execute (cassandra/cluster.c:28532)
> return self.execute_async(query, parameters, trace, custom_payload, 
> timeout).result()
>   File "cassandra/cluster.py", line 3339, in 
> cassandra.cluster.ResponseFuture.result (cassandra/cluster.c:62978)
> raise self._final_exception
> 'Error from server: code=2200 [Invalid query] message="Keyspace \'ks\' does 
> not exist"\n >> begin captured logging << 
> \ndtest: DEBUG: cluster ccm directory: 
> /mnt/tmp/dtest-1nvamN\ndtest: DEBUG: Custom init_config not found. Setting 
> defaults.\ndtest: DEBUG: Done setting configuration options:\n{   
> \'enable_scripted_user_defined_functions\': \'true\',\n
> \'enable_user_defined_functions\': \'true\',\n\'initial_token\': None,\n  
>   \'memtable_allocation_type\': \'offheap_objects\',\n\'num_tokens\': 
> \'32\',\n\'phi_convict_threshold\': 5}\n- >> end 
> captured logging << -'
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (CASSANDRA-12239) Add mshuler's key FE4B2BDA to dist/cassandra/KEYS

[Michael Shuler (JIRA)]

Michael Shuler created CASSANDRA-12239:
--

 Summary: Add mshuler's key FE4B2BDA to dist/cassandra/KEYS
 Key: CASSANDRA-12239
 URL: https://issues.apache.org/jira/browse/CASSANDRA-12239
 Project: Cassandra
  Issue Type: Task
  Components: Packaging
Reporter: Michael Shuler
Assignee: Michael Shuler
 Fix For: 3.x
 Attachments: KEYS+mshuler.diff.txt

I've started working on packaging with the 3.8 release and signed the staging 
artifacts with FE4B2BDA. This key will need to be added for the debian 
repository signature to function correctly, if it's released as-is, or perhaps 
[~tjake] will need to re-sign the release. Users will need to also fetch this 
new key and add to {{apt-key}}.

{{KEYS}} patch attached.

Assigned to myself, but I am not sure exactly where {{KEYS}} lives - in svn 
somewhere or a direct upload? :)



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (CASSANDRA-4650) RangeStreamer should be smarter when picking endpoints for streaming in case of N >=3 in each DC.

[sankalp kohli (JIRA)]

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

sankalp kohli commented on CASSANDRA-4650:
--

Capacity b/w rangeVertex and connected endpointVertex is always infinite 
(Integer.MAX_VALUE)
Capacity b/w sourceVertex and Rangevertex is always 1
Capacity b/w endpointVertex and destinationVertex is what gets calculated by 
getDestinationLinkCapacity which is 
(int) Math.ceil(Number of rangeVertices / Number of endpointVertices)
If we are not able to find a flow, we increment the capacity by 1 b/w 
endpointVertex and destinationVertex 

> RangeStreamer should be smarter when picking endpoints for streaming in case 
> of N >=3 in each DC.  
> ---
>
> Key: CASSANDRA-4650
> URL: https://issues.apache.org/jira/browse/CASSANDRA-4650
> Project: Cassandra
>  Issue Type: Improvement
>Affects Versions: 1.1.5
>Reporter: sankalp kohli
>Assignee: sankalp kohli
>Priority: Minor
>  Labels: streaming
> Attachments: CASSANDRA-4650_trunk.txt, photo-1.JPG
>
>   Original Estimate: 24h
>  Remaining Estimate: 24h
>
> getRangeFetchMap method in RangeStreamer should pick unique nodes to stream 
> data from when number of replicas in each DC is three or more. 
> When N>=3 in a DC, there are two options for streaming a range. Consider an 
> example of 4 nodes in one datacenter and replication factor of 3. 
> If a node goes down, it needs to recover 3 ranges of data. With current code, 
> two nodes could get selected as it orders the node by proximity. 
> We ideally will want to select 3 nodes for streaming the data. We can do this 
> by selecting unique nodes for each range.  
> Advantages:
> This will increase the performance of bootstrapping a node and will also put 
> less pressure on nodes serving the data. 
> Note: This does not affect if N < 3 in each DC as then it streams data from 
> only 2 nodes. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (CASSANDRA-12162) dtest failure in repair_tests.repair_test.TestRepair.simple_sequential_repair_test

[Jim Witschey (JIRA)]

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

Jim Witschey commented on CASSANDRA-12162:
--

Filed [PR 1110|https://github.com/riptano/cassandra-dtest/pull/1110] to attempt 
to address this by increasing the number of retries during insertion.

> dtest failure in 
> repair_tests.repair_test.TestRepair.simple_sequential_repair_test
> --
>
> Key: CASSANDRA-12162
> URL: https://issues.apache.org/jira/browse/CASSANDRA-12162
> Project: Cassandra
>  Issue Type: Test
>Reporter: Sean McCarthy
>Assignee: DS Test Eng
>  Labels: dtest
> Attachments: node1.log, node1_debug.log, node1_gc.log, node2.log, 
> node2_debug.log, node2_gc.log, node3.log, node3_debug.log, node3_gc.log
>
>
> example failure:
> http://cassci.datastax.com/job/cassandra-2.2_dtest_win32/267/testReport/repair_tests.repair_test/TestRepair/simple_sequential_repair_test
> Failed on CassCI build cassandra-2.2_dtest_win32 #267
> {code}
> Stacktrace
>   File "C:\tools\python2\lib\unittest\case.py", line 329, in run
> testMethod()
>   File 
> "D:\jenkins\workspace\cassandra-2.2_dtest_win32\cassandra-dtest\repair_tests\repair_test.py",
>  line 241, in simple_sequential_repair_test
> self._simple_repair(sequential=True)
>   File 
> "D:\jenkins\workspace\cassandra-2.2_dtest_win32\cassandra-dtest\repair_tests\repair_test.py",
>  line 295, in _simple_repair
> self._populate_cluster()
>   File 
> "D:\jenkins\workspace\cassandra-2.2_dtest_win32\cassandra-dtest\repair_tests\repair_test.py",
>  line 98, in _populate_cluster
> insert_c1c2(session, n=1000, consistency=ConsistencyLevel.ALL)
>   File 
> "D:\jenkins\workspace\cassandra-2.2_dtest_win32\cassandra-dtest\tools.py", 
> line 78, in insert_c1c2
> execute_concurrent_with_args(session, statement, [['k{}'.format(k)] for k 
> in keys])
>   File "cassandra\concurrent.py", line 224, in 
> cassandra.concurrent.execute_concurrent_with_args 
> (cassandra/concurrent.c:5996)
> return execute_concurrent(session, zip(cycle((statement,)), parameters), 
> *args, **kwargs)
>   File "cassandra\concurrent.py", line 92, in 
> cassandra.concurrent.execute_concurrent (cassandra/concurrent.c:1455)
> return executor.execute(concurrency, raise_on_first_error)
>   File "cassandra\concurrent.py", line 187, in 
> cassandra.concurrent.ConcurrentExecutorListResults.execute 
> (cassandra/concurrent.c:4824)
> return super(ConcurrentExecutorListResults, self).execute(concurrency, 
> fail_fast)
>   File "cassandra\concurrent.py", line 115, in 
> cassandra.concurrent._ConcurrentExecutor.execute (cassandra/concurrent.c:2120)
> return self._results()
>   File "cassandra\concurrent.py", line 201, in 
> cassandra.concurrent.ConcurrentExecutorListResults._results 
> (cassandra/concurrent.c:5617)
> with self._condition:
>   File "cassandra\concurrent.py", line 205, in 
> cassandra.concurrent.ConcurrentExecutorListResults._results 
> (cassandra/concurrent.c:5549)
> self._raise(self._exception)
>   File "cassandra\concurrent.py", line 153, in 
> cassandra.concurrent._ConcurrentExecutor._raise (cassandra/concurrent.c:3498)
> raise exc
> 'Error from server: code=1500 [Replica(s) failed to execute write] 
> message="Operation failed - received 2 responses and 1 failures" 
> info={\'failures\': 1, \'received_responses\': 2, \'required_responses\': 3, 
> \'consistency\': \'ALL\'}
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (CASSANDRA-2848) Make the Client API support passing down timeouts

[sankalp kohli (JIRA)]

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

sankalp kohli commented on CASSANDRA-2848:
--

I agree that we should fix issues by putting upper bound on the timeouts. 
However I dont think we should block this feature for it since it is off by 
default. Considering it took 5 years for someone to come up with a patch for 
this, I would vote to get it committed. 

Also this is strictly better than what we have now. 

> Make the Client API support passing down timeouts
> -
>
> Key: CASSANDRA-2848
> URL: https://issues.apache.org/jira/browse/CASSANDRA-2848
> Project: Cassandra
>  Issue Type: Improvement
>Reporter: Chris Goffinet
>Assignee: Geoffrey Yu
>Priority: Minor
> Fix For: 3.x
>
> Attachments: 2848-trunk.txt
>
>
> Having a max server RPC timeout is good for worst case, but many applications 
> that have middleware in front of Cassandra, might have higher timeout 
> requirements. In a fail fast environment, if my application starting at say 
> the front-end, only has 20ms to process a request, and it must connect to X 
> services down the stack, by the time it hits Cassandra, we might only have 
> 10ms. I propose we provide the ability to specify the timeout on each call we 
> do optionally.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (CASSANDRA-12236) RTE from new CDC column breaks in flight queries.

[Joshua McKenzie (JIRA)]

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

Joshua McKenzie commented on CASSANDRA-12236:
-

Two ways to approach this have come up in offline discussions. The first and 
less invasive method would be to suppress sending schema information about the 
cdc param status on versions >= 3.8 unless cdc_enabled:true is set in the 
cassandra.yaml. Specifically, removing the addition of the cdc param 
[here|https://github.com/apache/cassandra/blob/cassandra-3.8/src/java/org/apache/cassandra/schema/SchemaKeyspace.java#L514]
 and instead adding it conditionally 
[here|https://github.com/apache/cassandra/blob/cassandra-3.8/src/java/org/apache/cassandra/schema/SchemaKeyspace.java#L476].
 The upgrade path for users that want to enable cdc would be: don't enable CDC 
until your entire cluster is updated to a version >= 3.8. Then enable it and 
bounce your cluster. Since schema information is hard-coded in 
SchemaKeyspace.java and we don't actually care about the value in that param if 
cdc is not enabled on the cluster, it seems a reasonable workaround until we 
get to versioned sub-systems in Cassandra.

The second and more invasive method (at least from the perspective of the # of 
versions it touches and potential side-effects) would be to allow null columns 
during deserialization in 
[Columns.java|https://github.com/apache/cassandra/blob/cassandra-3.8/src/java/org/apache/cassandra/db/Columns.java#L433]
 if the mutation is for a schema table. This would apply to 3.0.x and 3.8+. 
This would get us back to a functionality somewhat similar to 
pre-CASSANDRA-8099, in that mutations for schema tables on different versions 
would no longer interrupt inter-node communication during an upgrade process 
via RTE.

I'm by no means an expert on schema dissemination - [~iamaleksey] / 
[~slebresne]: either of you have any feedback on the above two or other, better 
ideas on this front?

> RTE from new CDC column breaks in flight queries.
> -
>
> Key: CASSANDRA-12236
> URL: https://issues.apache.org/jira/browse/CASSANDRA-12236
> Project: Cassandra
>  Issue Type: Bug
>Reporter: Jeremiah Jordan
>Priority: Blocker
> Fix For: 3.8
>
>
> This RTE is not harmless. It will cause the internode connection to break 
> which will cause all in flight requests between these nodes to die/timeout.
> {noformat}
> - Due to changes in schema migration handling and the storage format 
> after 3.0, you will
>   see error messages such as:
>  "java.lang.RuntimeException: Unknown column cdc during 
> deserialization"
>   in your system logs on a mixed-version cluster during upgrades. This 
> error message
>   is harmless and due to the 3.8 nodes having cdc added to their schema 
> tables while
>   the <3.8 nodes do not. This message should cease once all nodes are 
> upgraded to 3.8.
>   As always, refrain from schema changes during cluster upgrades.
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (CASSANDRA-12209) Make Level compaction default

[Daniel Cohen (JIRA)]

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

Daniel Cohen commented on CASSANDRA-12209:
--

Please do not change established, working defaults if not necessary. There is 
no need whatsoever for this change. It will cause trouble. An advanced user 
knows how and why to change the compaction strategy. A novice user must be kept 
safe.

> Make Level compaction default
> -
>
> Key: CASSANDRA-12209
> URL: https://issues.apache.org/jira/browse/CASSANDRA-12209
> Project: Cassandra
>  Issue Type: Wish
>Reporter: sankalp kohli
>Priority: Minor
>
>  Level Compaction has come a long way since it was added. I think it is time 
> to make it default. We can debate which version we can do this. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[3/6] cassandra git commit: Ninja - add debug log statement to mv builder scheduled at startup

[samt]

Ninja - add debug log statement to mv builder scheduled at startup


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

Branch: refs/heads/trunk
Commit: 0297cbe97f73c3de9f10154f7ade72d8470ffa73
Parents: c481e8d
Author: Sam Tunnicliffe 
Authored: Tue Jul 19 18:48:09 2016 +0100
Committer: Sam Tunnicliffe 
Committed: Tue Jul 19 18:48:09 2016 +0100

--
 src/java/org/apache/cassandra/service/CassandraDaemon.java | 1 +
 1 file changed, 1 insertion(+)
--


http://git-wip-us.apache.org/repos/asf/cassandra/blob/0297cbe9/src/java/org/apache/cassandra/service/CassandraDaemon.java
--
diff --git a/src/java/org/apache/cassandra/service/CassandraDaemon.java 
b/src/java/org/apache/cassandra/service/CassandraDaemon.java
index 4e36fee..d7a90f0 100644
--- a/src/java/org/apache/cassandra/service/CassandraDaemon.java
+++ b/src/java/org/apache/cassandra/service/CassandraDaemon.java
@@ -324,6 +324,7 @@ public class CassandraDaemon
 {
 keyspace.viewManager.buildAllViews();
 }
+logger.debug("Completed submission of build tasks for any 
materialized views defined at startup");
 }
 };
 

[2/6] cassandra git commit: Ninja - add debug log statement to mv builder scheduled at startup

[samt]

Ninja - add debug log statement to mv builder scheduled at startup


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

Branch: refs/heads/cassandra-3.9
Commit: 0297cbe97f73c3de9f10154f7ade72d8470ffa73
Parents: c481e8d
Author: Sam Tunnicliffe 
Authored: Tue Jul 19 18:48:09 2016 +0100
Committer: Sam Tunnicliffe 
Committed: Tue Jul 19 18:48:09 2016 +0100

--
 src/java/org/apache/cassandra/service/CassandraDaemon.java | 1 +
 1 file changed, 1 insertion(+)
--


http://git-wip-us.apache.org/repos/asf/cassandra/blob/0297cbe9/src/java/org/apache/cassandra/service/CassandraDaemon.java
--
diff --git a/src/java/org/apache/cassandra/service/CassandraDaemon.java 
b/src/java/org/apache/cassandra/service/CassandraDaemon.java
index 4e36fee..d7a90f0 100644
--- a/src/java/org/apache/cassandra/service/CassandraDaemon.java
+++ b/src/java/org/apache/cassandra/service/CassandraDaemon.java
@@ -324,6 +324,7 @@ public class CassandraDaemon
 {
 keyspace.viewManager.buildAllViews();
 }
+logger.debug("Completed submission of build tasks for any 
materialized views defined at startup");
 }
 };
 

[6/6] cassandra git commit: Merge branch 'cassandra-3.9' into trunk

[samt]

Merge branch 'cassandra-3.9' into trunk


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

Branch: refs/heads/trunk
Commit: d14052e99c742985402fa1c8c392ae6de64f4680
Parents: 3163793 4bd4be8
Author: Sam Tunnicliffe 
Authored: Tue Jul 19 18:57:32 2016 +0100
Committer: Sam Tunnicliffe 
Committed: Tue Jul 19 18:57:32 2016 +0100

--

--

[5/6] cassandra git commit: Merge branch 'cassandra-3.0' into cassandra-3.9

[samt]

Merge branch 'cassandra-3.0' into cassandra-3.9


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

Branch: refs/heads/cassandra-3.9
Commit: 4bd4be867ebeecfd7bd0a67ebeb122923d5ff850
Parents: 9ed4877 0297cbe
Author: Sam Tunnicliffe 
Authored: Tue Jul 19 18:52:15 2016 +0100
Committer: Sam Tunnicliffe 
Committed: Tue Jul 19 18:52:15 2016 +0100

--

--

[1/6] cassandra git commit: Ninja - add debug log statement to mv builder scheduled at startup

[samt]

Repository: cassandra
Updated Branches:
  refs/heads/cassandra-3.0 c481e8dc8 -> 0297cbe97
  refs/heads/cassandra-3.9 9ed487776 -> 4bd4be867
  refs/heads/trunk 31637939e -> d14052e99


Ninja - add debug log statement to mv builder scheduled at startup


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

Branch: refs/heads/cassandra-3.0
Commit: 0297cbe97f73c3de9f10154f7ade72d8470ffa73
Parents: c481e8d
Author: Sam Tunnicliffe 
Authored: Tue Jul 19 18:48:09 2016 +0100
Committer: Sam Tunnicliffe 
Committed: Tue Jul 19 18:48:09 2016 +0100

--
 src/java/org/apache/cassandra/service/CassandraDaemon.java | 1 +
 1 file changed, 1 insertion(+)
--


http://git-wip-us.apache.org/repos/asf/cassandra/blob/0297cbe9/src/java/org/apache/cassandra/service/CassandraDaemon.java
--
diff --git a/src/java/org/apache/cassandra/service/CassandraDaemon.java 
b/src/java/org/apache/cassandra/service/CassandraDaemon.java
index 4e36fee..d7a90f0 100644
--- a/src/java/org/apache/cassandra/service/CassandraDaemon.java
+++ b/src/java/org/apache/cassandra/service/CassandraDaemon.java
@@ -324,6 +324,7 @@ public class CassandraDaemon
 {
 keyspace.viewManager.buildAllViews();
 }
+logger.debug("Completed submission of build tasks for any 
materialized views defined at startup");
 }
 };
 

[4/6] cassandra git commit: Merge branch 'cassandra-3.0' into cassandra-3.9

[samt]

Merge branch 'cassandra-3.0' into cassandra-3.9


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

Branch: refs/heads/trunk
Commit: 4bd4be867ebeecfd7bd0a67ebeb122923d5ff850
Parents: 9ed4877 0297cbe
Author: Sam Tunnicliffe 
Authored: Tue Jul 19 18:52:15 2016 +0100
Committer: Sam Tunnicliffe 
Committed: Tue Jul 19 18:52:15 2016 +0100

--

--

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

[samt]

Merge branch 'cassandra-3.9' into trunk


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

Branch: refs/heads/trunk
Commit: 31637939e7fce91a3146daf64ff0eb102680a1ea
Parents: 614eebd 9ed4877
Author: Sam Tunnicliffe 
Authored: Tue Jul 19 18:30:43 2016 +0100
Committer: Sam Tunnicliffe 
Committed: Tue Jul 19 18:30:43 2016 +0100

--
 src/java/org/apache/cassandra/service/CassandraDaemon.java | 1 +
 1 file changed, 1 insertion(+)
--


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

[1/3] cassandra git commit: Ninja - add debug log statement to mv builder scheduled at startup

[samt]

Repository: cassandra
Updated Branches:
  refs/heads/cassandra-3.9 8049bc886 -> 9ed487776
  refs/heads/trunk 614eebdff -> 31637939e


Ninja - add debug log statement to mv builder scheduled at startup


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

Branch: refs/heads/cassandra-3.9
Commit: 9ed4877760b3b8acacac2dea833477ec14ba1d28
Parents: 8049bc8
Author: Sam Tunnicliffe 
Authored: Tue Jul 19 18:30:31 2016 +0100
Committer: Sam Tunnicliffe 
Committed: Tue Jul 19 18:30:31 2016 +0100

--
 src/java/org/apache/cassandra/service/CassandraDaemon.java | 1 +
 1 file changed, 1 insertion(+)
--


http://git-wip-us.apache.org/repos/asf/cassandra/blob/9ed48777/src/java/org/apache/cassandra/service/CassandraDaemon.java
--
diff --git a/src/java/org/apache/cassandra/service/CassandraDaemon.java 
b/src/java/org/apache/cassandra/service/CassandraDaemon.java
index 2d21bff..88b3c88 100644
--- a/src/java/org/apache/cassandra/service/CassandraDaemon.java
+++ b/src/java/org/apache/cassandra/service/CassandraDaemon.java
@@ -384,6 +384,7 @@ public class CassandraDaemon
 {
 keyspace.viewManager.buildAllViews();
 }
+logger.debug("Completed submission of build tasks for any 
materialized views defined at startup");
 };
 
 ScheduledExecutors.optionalTasks.schedule(viewRebuild, 
StorageService.RING_DELAY, TimeUnit.MILLISECONDS);

[2/3] cassandra git commit: Ninja - add debug log statement to mv builder scheduled at startup

[samt]

Ninja - add debug log statement to mv builder scheduled at startup


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

Branch: refs/heads/trunk
Commit: 9ed4877760b3b8acacac2dea833477ec14ba1d28
Parents: 8049bc8
Author: Sam Tunnicliffe 
Authored: Tue Jul 19 18:30:31 2016 +0100
Committer: Sam Tunnicliffe 
Committed: Tue Jul 19 18:30:31 2016 +0100

--
 src/java/org/apache/cassandra/service/CassandraDaemon.java | 1 +
 1 file changed, 1 insertion(+)
--


http://git-wip-us.apache.org/repos/asf/cassandra/blob/9ed48777/src/java/org/apache/cassandra/service/CassandraDaemon.java
--
diff --git a/src/java/org/apache/cassandra/service/CassandraDaemon.java 
b/src/java/org/apache/cassandra/service/CassandraDaemon.java
index 2d21bff..88b3c88 100644
--- a/src/java/org/apache/cassandra/service/CassandraDaemon.java
+++ b/src/java/org/apache/cassandra/service/CassandraDaemon.java
@@ -384,6 +384,7 @@ public class CassandraDaemon
 {
 keyspace.viewManager.buildAllViews();
 }
+logger.debug("Completed submission of build tasks for any 
materialized views defined at startup");
 };
 
 ScheduledExecutors.optionalTasks.schedule(viewRebuild, 
StorageService.RING_DELAY, TimeUnit.MILLISECONDS);

[jira] [Commented] (CASSANDRA-10368) Support Restricting non-PK Cols in Materialized View Select Statements

[Jochen Niebuhr (JIRA)]

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

Jochen Niebuhr commented on CASSANDRA-10368:


Thanks for the feedback [~thobbs]. I'll try to put some tests together 
tomorrow. I think i'll be able to write the normal tests about filtering on non 
primary columns, I'm not sure about the timestamp ones though, as I'm pretty 
new to using Cassandra.

> Support Restricting non-PK Cols in Materialized View Select Statements
> --
>
> Key: CASSANDRA-10368
> URL: https://issues.apache.org/jira/browse/CASSANDRA-10368
> Project: Cassandra
>  Issue Type: Improvement
>  Components: CQL
>Reporter: Tyler Hobbs
>Priority: Minor
> Fix For: 3.x
>
> Attachments: 10368-3.8.txt
>
>
> CASSANDRA-9664 allows materialized views to restrict primary key columns in 
> the select statement.  Due to CASSANDRA-10261, the patch did not include 
> support for restricting non-PK columns.  Now that the timestamp issue has 
> been resolved, we can add support for this.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (CASSANDRA-12216) TTL Reading And Writing is Asymmetric

[Russell Spitzer (JIRA)]

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

Russell Spitzer commented on CASSANDRA-12216:
-

Currently the latest version states
{quote}
TTL: allows to specify an optional Time To Live (in seconds) for the inserted 
values. If set, the inserted values are automatically removed from the database 
after the specified time. Note that the TTL concerns the inserted values, not 
the column themselves. This means that any subsequent update of the column will 
also reset the TTL (to whatever TTL is specified in that update). By default, 
values never expire. A TTL of 0 or a negative one is equivalent to no TTL.
{quote}

Which actually also is incorrect since a negative TTL is not allowed

{code}
  if (ttl < 0)
throw new InvalidRequestException("A TTL must be greater or equal 
to 0, but was " + ttl);
{code}

> TTL Reading And Writing is Asymmetric 
> --
>
> Key: CASSANDRA-12216
> URL: https://issues.apache.org/jira/browse/CASSANDRA-12216
> Project: Cassandra
>  Issue Type: Bug
>  Components: CQL
>Reporter: Russell Spitzer
>Assignee: Russell Spitzer
>Priority: Minor
> Attachments: 12216-3.7-2.txt, 12216-3.7.txt
>
>
> There is an inherent asymmetry in the way TTL's are read and Written. 
> An `TTL` of 0 when written becomes a `null` in C*
> When read, this `TTL` becomes a `null` 
> The `null` cannot be written back to C* as `TTL`
> This means that end users attempting to copy tables with TTL have to do 
> manual mapping of the null TTL values to 0 to avoid NPE. This is a bit 
> onerous when C* seems to have an internal logic that 0 == NULL. I don't think 
> C* should return values which are not directly insertable back to C*. 
> Even with the advent CASSANDRA-7304 this still remains a problem that the 
> User needs to be aware of and take care of.
> The following prepared statement
> {code}
> INSERT INTO test.table2 (k,v) (?,?) USING TTL: ? 
> {code}
> Will throw NPEs unless we specifically check that the value to be bound to 
> TTL is not null.
> I think we should discuss whether `null` should be treated as 0 in TTL for 
> prepared statements. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (CASSANDRA-12216) TTL Reading And Writing is Asymmetric

[Brian Hess (JIRA)]

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

 Brian Hess commented on CASSANDRA-12216:
-

This looks like it should apply to previous versions, going back to 2.1 even.  
The only behavior change is an undocumented behavior of throwing an 
InvalidQueryException when providing a null TTL.

> TTL Reading And Writing is Asymmetric 
> --
>
> Key: CASSANDRA-12216
> URL: https://issues.apache.org/jira/browse/CASSANDRA-12216
> Project: Cassandra
>  Issue Type: Bug
>  Components: CQL
>Reporter: Russell Spitzer
>Assignee: Russell Spitzer
>Priority: Minor
> Attachments: 12216-3.7-2.txt, 12216-3.7.txt
>
>
> There is an inherent asymmetry in the way TTL's are read and Written. 
> An `TTL` of 0 when written becomes a `null` in C*
> When read, this `TTL` becomes a `null` 
> The `null` cannot be written back to C* as `TTL`
> This means that end users attempting to copy tables with TTL have to do 
> manual mapping of the null TTL values to 0 to avoid NPE. This is a bit 
> onerous when C* seems to have an internal logic that 0 == NULL. I don't think 
> C* should return values which are not directly insertable back to C*. 
> Even with the advent CASSANDRA-7304 this still remains a problem that the 
> User needs to be aware of and take care of.
> The following prepared statement
> {code}
> INSERT INTO test.table2 (k,v) (?,?) USING TTL: ? 
> {code}
> Will throw NPEs unless we specifically check that the value to be bound to 
> TTL is not null.
> I think we should discuss whether `null` should be treated as 0 in TTL for 
> prepared statements. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (CASSANDRA-10368) Support Restricting non-PK Cols in Materialized View Select Statements

[Tyler Hobbs (JIRA)]

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

Tyler Hobbs updated CASSANDRA-10368:

Reproduced In:   (was: 3.8, 3.10)
   Status: Awaiting Feedback  (was: Open)

> Support Restricting non-PK Cols in Materialized View Select Statements
> --
>
> Key: CASSANDRA-10368
> URL: https://issues.apache.org/jira/browse/CASSANDRA-10368
> Project: Cassandra
>  Issue Type: Improvement
>  Components: CQL
>Reporter: Tyler Hobbs
>Priority: Minor
> Fix For: 3.x
>
> Attachments: 10368-3.8.txt
>
>
> CASSANDRA-9664 allows materialized views to restrict primary key columns in 
> the select statement.  Due to CASSANDRA-10261, the patch did not include 
> support for restricting non-PK columns.  Now that the timestamp issue has 
> been resolved, we can add support for this.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (CASSANDRA-10368) Support Restricting non-PK Cols in Materialized View Select Statements

[Tyler Hobbs (JIRA)]

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

Tyler Hobbs updated CASSANDRA-10368:

Status: Open  (was: Patch Available)

> Support Restricting non-PK Cols in Materialized View Select Statements
> --
>
> Key: CASSANDRA-10368
> URL: https://issues.apache.org/jira/browse/CASSANDRA-10368
> Project: Cassandra
>  Issue Type: Improvement
>  Components: CQL
>Reporter: Tyler Hobbs
>Priority: Minor
> Fix For: 3.x
>
> Attachments: 10368-3.8.txt
>
>
> CASSANDRA-9664 allows materialized views to restrict primary key columns in 
> the select statement.  Due to CASSANDRA-10261, the patch did not include 
> support for restricting non-PK columns.  Now that the timestamp issue has 
> been resolved, we can add support for this.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (CASSANDRA-10368) Support Restricting non-PK Cols in Materialized View Select Statements

[Tyler Hobbs (JIRA)]

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

Tyler Hobbs commented on CASSANDRA-10368:
-

Hi [~jniebuhr], thanks for the patch!  I've gone back over CASSANDRA-9664 and 
CASSANDRA-10261 to refresh my memory, and I think you are correct that this is 
all that we need to do.

However, we do need to add a lot of tests before this can be merged.  The best 
place to add new tests would be 
{{test/unit/org/apache/cassandra/cql3/ViewFilteringTest.java}}.

Specifically, we want to test cases like the one in [this 
comment|https://issues.apache.org/jira/browse/CASSANDRA-9664?focusedCommentId=14724150=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-14724150]
 where we could have potential timestamp issues.  You could also use a couple 
of test cases in {{test/unit/org/apache/cassandra/cql3/ViewTest.java}} as 
examples: {{complexTimestampUpdateTest}}, 
{{testRegularColumnTimestampUpdates}}, and {{testOldTimestamps}}.

Let me know if you need assistance with this.

> Support Restricting non-PK Cols in Materialized View Select Statements
> --
>
> Key: CASSANDRA-10368
> URL: https://issues.apache.org/jira/browse/CASSANDRA-10368
> Project: Cassandra
>  Issue Type: Improvement
>  Components: CQL
>Reporter: Tyler Hobbs
>Priority: Minor
> Fix For: 3.x
>
> Attachments: 10368-3.8.txt
>
>
> CASSANDRA-9664 allows materialized views to restrict primary key columns in 
> the select statement.  Due to CASSANDRA-10261, the patch did not include 
> support for restricting non-PK columns.  Now that the timestamp issue has 
> been resolved, we can add support for this.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[Cassandra Wiki] Trivial Update of "Committers" by MichaelShuler

[Apache Wiki]

Dear Wiki user,

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

The "Committers" page has been changed by MichaelShuler:
https://wiki.apache.org/cassandra/Committers?action=diff=60=61

  ||Benjamin Lerer ||Jul 2015 ||Datastax || ||
  ||Carl Yeksigian ||Jan 2016 ||Datastax ||Also a 
[[http://thrift.apache.org|Thrift]] committer ||
  ||Stefania Alborghetti ||Apr 2016 ||Datastax || ||
- ||Jeff Jirsa ||June 2016 ||CrowdStrike || ||
+ ||Jeff Jirsa ||June 2016 ||!CrowdStrike || ||
  ||Michael Shuler ||June 2016 ||Datastax || ||
  
  

[jira] [Commented] (CASSANDRA-12192) dtest failure in upgrade_tests.cql_tests.TestCQLNodes3RF3_Upgrade_current_3_0_x_To_head_trunk.map_keys_indexing_test

[Philip Thompson (JIRA)]

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

Philip Thompson commented on CASSANDRA-12192:
-

This could just be CASSANDRA-12236

> dtest failure in 
> upgrade_tests.cql_tests.TestCQLNodes3RF3_Upgrade_current_3_0_x_To_head_trunk.map_keys_indexing_test
> 
>
> Key: CASSANDRA-12192
> URL: https://issues.apache.org/jira/browse/CASSANDRA-12192
> Project: Cassandra
>  Issue Type: Bug
>Reporter: Sean McCarthy
>Assignee: Sam Tunnicliffe
>  Labels: dtest
> Attachments: node1.log, node1_debug.log, node1_gc.log, node2.log, 
> node2_debug.log, node2_gc.log, node3.log, node3_debug.log, node3_gc.log
>
>
> example failure:
> http://cassci.datastax.com/job/upgrade_tests-all/59/testReport/upgrade_tests.cql_tests/TestCQLNodes3RF3_Upgrade_current_3_0_x_To_head_trunk/map_keys_indexing_test
> Failed on CassCI build upgrade_tests-all #59
> {code}
> Stacktrace
>   File "/usr/lib/python2.7/unittest/case.py", line 329, in run
> testMethod()
>   File "/home/automaton/cassandra-dtest/tools.py", line 290, in wrapped
> f(obj)
>   File "/home/automaton/cassandra-dtest/upgrade_tests/cql_tests.py", line 
> 3668, in map_keys_indexing_test
> cursor.execute("TRUNCATE test")
>   File "cassandra/cluster.py", line 1941, in 
> cassandra.cluster.Session.execute (cassandra/cluster.c:33642)
> return self.execute_async(query, parameters, trace, custom_payload, 
> timeout, execution_profile).result()
>   File "cassandra/cluster.py", line 3629, in 
> cassandra.cluster.ResponseFuture.result (cassandra/cluster.c:69369)
> raise self._final_exception
> '
> {code}
> Related failure: 
> http://cassci.datastax.com/job/upgrade_tests-all/59/testReport/upgrade_tests.cql_tests/TestCQLNodes2RF1_Upgrade_current_3_0_x_To_head_trunk/map_keys_indexing_test/



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[Cassandra Wiki] Update of "Committers" by MichaelShuler

[Apache Wiki]

Dear Wiki user,

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

The "Committers" page has been changed by MichaelShuler:
https://wiki.apache.org/cassandra/Committers?action=diff=59=60

Comment:
Update June PMC member additions, add committers jeffj and mshuler

  ||Sylvain Lebresne ||Mar 2011 ||Datastax ||PMC member, Release manager ||
  ||Pavel Yaskevich ||Aug 2011 ||Apple ||PMC member ||
  ||Vijay Parthasarathy ||Jan 2012 ||Apple || ||
- ||Aaron Morton ||Jan 2012 ||Independent || ||
+ ||Aaron Morton ||Jan 2012 ||Independent ||PMC member ||
  ||Peter Schuller ||Feb 2012 ||Twitter || ||
- ||Dave Brosius ||May 2012 ||Independent ||Also a 
[[http://commons.apache.org|Commons]] committer ||
+ ||Dave Brosius ||May 2012 ||Independent ||PMC member, also a 
[[http://commons.apache.org|Commons]] committer ||
  ||Yuki Morishita ||May 2012 ||Datastax || ||
  ||Aleksey Yeschenko ||Nov 2012 ||Datastax ||PMC member ||
  ||Jason Brown ||Feb 2013 ||Apple || ||
@@ -31, +31 @@

  ||Benjamin Lerer ||Jul 2015 ||Datastax || ||
  ||Carl Yeksigian ||Jan 2016 ||Datastax ||Also a 
[[http://thrift.apache.org|Thrift]] committer ||
  ||Stefania Alborghetti ||Apr 2016 ||Datastax || ||
+ ||Jeff Jirsa ||June 2016 ||CrowdStrike || ||
+ ||Michael Shuler ||June 2016 ||Datastax || ||
  
  
  {{https://c.statcounter.com/9397521/0/fe557aad/1/|stats}}

[jira] [Comment Edited] (CASSANDRA-11687) dtest failure in rebuild_test.TestRebuild.simple_rebuild_test

[Jim Witschey (JIRA)]

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

Jim Witschey edited comment on CASSANDRA-11687 at 7/19/16 4:55 PM:
---

That PR also improved error handling, and here's the error I get running 
locally:

{code}
==
ERROR: rebuild_test.py:TestRebuild.simple_rebuild_test
--
Traceback (most recent call last):
  File "/home/mambocab/cstar_src/cassandra-dtest/rebuild_test.py", line 96, in 
simple_rebuild_test
rebuild()
  File "/home/mambocab/cstar_src/cassandra-dtest/rebuild_test.py", line 88, in 
rebuild
raise e
NodetoolError: Nodetool command 
'/home/mambocab/.ccm/repository/gitCOLONtrunk/bin/nodetool -h localhost -p 7200 
rebuild dc1' failed; exit status: 1; stdout: nodetool: Unable to find 
sufficient sources for streaming range 
(-3287869951390391138,-1624006824486474209] in keyspace system_auth with 
RF=1.If you want to ignore this, consider using system property 
-Dcassandra.consistent.rangemovement=false.
See 'nodetool help' or 'nodetool help '.

 >> begin captured logging << 
ccm: INFO: Fetching Cassandra updates...
dtest: DEBUG: cluster ccm directory: /tmp/dtest-QDgw0_
ccm: INFO: Fetching Cassandra updates...
dtest: DEBUG: Done setting configuration options:
{   'num_tokens': None, 'phi_convict_threshold': 5, 'start_rpc': 'true'}
cassandra.cluster: INFO: New Cassandra host  discovered
cassandra.cluster: WARNING: Host 127.0.0.1 has been marked down
cassandra.pool: INFO: Successful reconnection to 127.0.0.1, marking node up if 
it isn't already
cassandra.cluster: INFO: Host 127.0.0.1 may be up; will prepare queries and 
open connection pool
cassandra.cluster: INFO: New Cassandra host  discovered
- >> end captured logging << -

--
{code}

-So, looks like we're calling {{rebuild}} incorrectly.- This shouldn't fail 
this way. The thing to do here, as the error says, may be to set 
{{cassandra.consistent.rangemovement}} to {{false}}.

EDIT: for the record, this was the PR:

https://github.com/riptano/cassandra-dtest/pull/1106


was (Author: mambocab):
That PR also improved error handling, and here's the error I get running 
locally:

{code}
==
ERROR: rebuild_test.py:TestRebuild.simple_rebuild_test
--
Traceback (most recent call last):
  File "/home/mambocab/cstar_src/cassandra-dtest/rebuild_test.py", line 96, in 
simple_rebuild_test
rebuild()
  File "/home/mambocab/cstar_src/cassandra-dtest/rebuild_test.py", line 88, in 
rebuild
raise e
NodetoolError: Nodetool command 
'/home/mambocab/.ccm/repository/gitCOLONtrunk/bin/nodetool -h localhost -p 7200 
rebuild dc1' failed; exit status: 1; stdout: nodetool: Unable to find 
sufficient sources for streaming range 
(-3287869951390391138,-1624006824486474209] in keyspace system_auth with 
RF=1.If you want to ignore this, consider using system property 
-Dcassandra.consistent.rangemovement=false.
See 'nodetool help' or 'nodetool help '.

 >> begin captured logging << 
ccm: INFO: Fetching Cassandra updates...
dtest: DEBUG: cluster ccm directory: /tmp/dtest-QDgw0_
ccm: INFO: Fetching Cassandra updates...
dtest: DEBUG: Done setting configuration options:
{   'num_tokens': None, 'phi_convict_threshold': 5, 'start_rpc': 'true'}
cassandra.cluster: INFO: New Cassandra host  discovered
cassandra.cluster: WARNING: Host 127.0.0.1 has been marked down
cassandra.pool: INFO: Successful reconnection to 127.0.0.1, marking node up if 
it isn't already
cassandra.cluster: INFO: Host 127.0.0.1 may be up; will prepare queries and 
open connection pool
cassandra.cluster: INFO: New Cassandra host  discovered
- >> end captured logging << -

--
{code}

So, looks like we're calling {{rebuild}} incorrectly.

EDIT: for the record, this was the PR:

https://github.com/riptano/cassandra-dtest/pull/1106

> dtest failure in rebuild_test.TestRebuild.simple_rebuild_test
> -
>
> Key: CASSANDRA-11687
> URL: https://issues.apache.org/jira/browse/CASSANDRA-11687
> Project: Cassandra
>  Issue Type: Test
>Reporter: Russ Hatch
>Assignee: DS Test Eng
>  Labels: dtest
>
> single failure on most recent run (3.0 no-vnode)
> {noformat}
> concurrent rebuild should not be allowed, but one rebuild command should have 
> 

[jira] [Comment Edited] (CASSANDRA-11687) dtest failure in rebuild_test.TestRebuild.simple_rebuild_test

[Jim Witschey (JIRA)]

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

Jim Witschey edited comment on CASSANDRA-11687 at 7/19/16 4:50 PM:
---

That PR also improved error handling, and here's the error I get running 
locally:

{code}
==
ERROR: rebuild_test.py:TestRebuild.simple_rebuild_test
--
Traceback (most recent call last):
  File "/home/mambocab/cstar_src/cassandra-dtest/rebuild_test.py", line 96, in 
simple_rebuild_test
rebuild()
  File "/home/mambocab/cstar_src/cassandra-dtest/rebuild_test.py", line 88, in 
rebuild
raise e
NodetoolError: Nodetool command 
'/home/mambocab/.ccm/repository/gitCOLONtrunk/bin/nodetool -h localhost -p 7200 
rebuild dc1' failed; exit status: 1; stdout: nodetool: Unable to find 
sufficient sources for streaming range 
(-3287869951390391138,-1624006824486474209] in keyspace system_auth with 
RF=1.If you want to ignore this, consider using system property 
-Dcassandra.consistent.rangemovement=false.
See 'nodetool help' or 'nodetool help '.

 >> begin captured logging << 
ccm: INFO: Fetching Cassandra updates...
dtest: DEBUG: cluster ccm directory: /tmp/dtest-QDgw0_
ccm: INFO: Fetching Cassandra updates...
dtest: DEBUG: Done setting configuration options:
{   'num_tokens': None, 'phi_convict_threshold': 5, 'start_rpc': 'true'}
cassandra.cluster: INFO: New Cassandra host  discovered
cassandra.cluster: WARNING: Host 127.0.0.1 has been marked down
cassandra.pool: INFO: Successful reconnection to 127.0.0.1, marking node up if 
it isn't already
cassandra.cluster: INFO: Host 127.0.0.1 may be up; will prepare queries and 
open connection pool
cassandra.cluster: INFO: New Cassandra host  discovered
- >> end captured logging << -

--
{code}

So, looks like we're calling {{rebuild}} incorrectly.

EDIT: for the record, this was the PR:

https://github.com/riptano/cassandra-dtest/pull/1106


was (Author: mambocab):
That PR also improved error handling, and here's the error I get running 
locally:

{code}
==
ERROR: rebuild_test.py:TestRebuild.simple_rebuild_test
--
Traceback (most recent call last):
  File "/home/mambocab/cstar_src/cassandra-dtest/rebuild_test.py", line 96, in 
simple_rebuild_test
rebuild()
  File "/home/mambocab/cstar_src/cassandra-dtest/rebuild_test.py", line 88, in 
rebuild
raise e
NodetoolError: Nodetool command 
'/home/mambocab/.ccm/repository/gitCOLONtrunk/bin/nodetool -h localhost -p 7200 
rebuild dc1' failed; exit status: 1; stdout: nodetool: Unable to find 
sufficient sources for streaming range 
(-3287869951390391138,-1624006824486474209] in keyspace system_auth with 
RF=1.If you want to ignore this, consider using system property 
-Dcassandra.consistent.rangemovement=false.
See 'nodetool help' or 'nodetool help '.

 >> begin captured logging << 
ccm: INFO: Fetching Cassandra updates...
dtest: DEBUG: cluster ccm directory: /tmp/dtest-QDgw0_
ccm: INFO: Fetching Cassandra updates...
dtest: DEBUG: Done setting configuration options:
{   'num_tokens': None, 'phi_convict_threshold': 5, 'start_rpc': 'true'}
cassandra.cluster: INFO: New Cassandra host  discovered
cassandra.cluster: WARNING: Host 127.0.0.1 has been marked down
cassandra.pool: INFO: Successful reconnection to 127.0.0.1, marking node up if 
it isn't already
cassandra.cluster: INFO: Host 127.0.0.1 may be up; will prepare queries and 
open connection pool
cassandra.cluster: INFO: New Cassandra host  discovered
- >> end captured logging << -

--
{code}

So, looks like we're calling {{rebuild}} incorrectly.

> dtest failure in rebuild_test.TestRebuild.simple_rebuild_test
> -
>
> Key: CASSANDRA-11687
> URL: https://issues.apache.org/jira/browse/CASSANDRA-11687
> Project: Cassandra
>  Issue Type: Test
>Reporter: Russ Hatch
>Assignee: DS Test Eng
>  Labels: dtest
>
> single failure on most recent run (3.0 no-vnode)
> {noformat}
> concurrent rebuild should not be allowed, but one rebuild command should have 
> succeeded.
> {noformat}
> http://cassci.datastax.com/job/cassandra-3.0_novnode_dtest/217/testReport/rebuild_test/TestRebuild/simple_rebuild_test
> Failed on CassCI build cassandra-3.0_novnode_dtest #217



--
This message was sent by 

[jira] [Commented] (CASSANDRA-11687) dtest failure in rebuild_test.TestRebuild.simple_rebuild_test

[Jim Witschey (JIRA)]

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

Jim Witschey commented on CASSANDRA-11687:
--

That PR also improved error handling, and here's the error I get running 
locally:

{code}
==
ERROR: rebuild_test.py:TestRebuild.simple_rebuild_test
--
Traceback (most recent call last):
  File "/home/mambocab/cstar_src/cassandra-dtest/rebuild_test.py", line 96, in 
simple_rebuild_test
rebuild()
  File "/home/mambocab/cstar_src/cassandra-dtest/rebuild_test.py", line 88, in 
rebuild
raise e
NodetoolError: Nodetool command 
'/home/mambocab/.ccm/repository/gitCOLONtrunk/bin/nodetool -h localhost -p 7200 
rebuild dc1' failed; exit status: 1; stdout: nodetool: Unable to find 
sufficient sources for streaming range 
(-3287869951390391138,-1624006824486474209] in keyspace system_auth with 
RF=1.If you want to ignore this, consider using system property 
-Dcassandra.consistent.rangemovement=false.
See 'nodetool help' or 'nodetool help '.

 >> begin captured logging << 
ccm: INFO: Fetching Cassandra updates...
dtest: DEBUG: cluster ccm directory: /tmp/dtest-QDgw0_
ccm: INFO: Fetching Cassandra updates...
dtest: DEBUG: Done setting configuration options:
{   'num_tokens': None, 'phi_convict_threshold': 5, 'start_rpc': 'true'}
cassandra.cluster: INFO: New Cassandra host  discovered
cassandra.cluster: WARNING: Host 127.0.0.1 has been marked down
cassandra.pool: INFO: Successful reconnection to 127.0.0.1, marking node up if 
it isn't already
cassandra.cluster: INFO: Host 127.0.0.1 may be up; will prepare queries and 
open connection pool
cassandra.cluster: INFO: New Cassandra host  discovered
- >> end captured logging << -

--
{code}

So, looks like we're calling {{rebuild}} incorrectly.

> dtest failure in rebuild_test.TestRebuild.simple_rebuild_test
> -
>
> Key: CASSANDRA-11687
> URL: https://issues.apache.org/jira/browse/CASSANDRA-11687
> Project: Cassandra
>  Issue Type: Test
>Reporter: Russ Hatch
>Assignee: DS Test Eng
>  Labels: dtest
>
> single failure on most recent run (3.0 no-vnode)
> {noformat}
> concurrent rebuild should not be allowed, but one rebuild command should have 
> succeeded.
> {noformat}
> http://cassci.datastax.com/job/cassandra-3.0_novnode_dtest/217/testReport/rebuild_test/TestRebuild/simple_rebuild_test
> Failed on CassCI build cassandra-3.0_novnode_dtest #217



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Resolved] (CASSANDRA-12165) dtest failure in commitlog_test.TestCommitLog.test_commitlog_replay_on_startup

[Tyler Hobbs (JIRA)]

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

Tyler Hobbs resolved CASSANDRA-12165.
-
Resolution: Fixed

Yes, this is a dupe, so I've resolved it as such.

> dtest failure in commitlog_test.TestCommitLog.test_commitlog_replay_on_startup
> --
>
> Key: CASSANDRA-12165
> URL: https://issues.apache.org/jira/browse/CASSANDRA-12165
> Project: Cassandra
>  Issue Type: Bug
>Reporter: Sean McCarthy
>  Labels: dtest
> Attachments: node1.log, node1_debug.log, node1_gc.log
>
>
> example failure:
> http://cassci.datastax.com/job/trunk_offheap_dtest/312/testReport/commitlog_test/TestCommitLog/test_commitlog_replay_on_startup
> Failed on CassCI build trunk_offheap_dtest #312
> {code}
> Stacktrace
>   File "/usr/lib/python2.7/unittest/case.py", line 329, in run
> testMethod()
>   File "/home/automaton/cassandra-dtest/commitlog_test.py", line 273, in 
> test_commitlog_replay_on_startup
> node1.watch_log_for("Log replay complete")
>   File "/home/automaton/ccm/ccmlib/node.py", line 449, in watch_log_for
> raise TimeoutError(time.strftime("%d %b %Y %H:%M:%S", time.gmtime()) + " 
> [" + self.name + "] Missing: " + str([e.pattern for e in tofind]) + ":\n" + 
> reads[:50] + ".\nSee {} for remainder".format(filename))
> "08 Jul 2016 04:56:21 [node1] Missing: ['Log replay complete']:\nINFO  [main] 
> 2016-07-08 04:46:13,102 YamlConfigura.\nSee system.log for remainder
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (CASSANDRA-11998) dtest failure in offline_tools_test.TestOfflineTools.sstableofflinerelevel_test

[Tyler Hobbs (JIRA)]

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

Tyler Hobbs commented on CASSANDRA-11998:
-

+1 on bumping the size, but as Philip notes, we should specify a thread count 
for the stress call.  When making that change, I would make sure that we still 
write enough data with a fixed thread count before merging.

> dtest failure in 
> offline_tools_test.TestOfflineTools.sstableofflinerelevel_test
> ---
>
> Key: CASSANDRA-11998
> URL: https://issues.apache.org/jira/browse/CASSANDRA-11998
> Project: Cassandra
>  Issue Type: Test
>Reporter: Craig Kodman
>Assignee: Carl Yeksigian
>  Labels: dtest
>
> example failure:
> http://cassci.datastax.com/job/cassandra-2.2_dtest/635/testReport/offline_tools_test/TestOfflineTools/sstableofflinerelevel_test
> Failed on CassCI build cassandra-2.2_dtest #635



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (CASSANDRA-12238) Unexpected exception during request java.lang.IndexOutOfBoundsException: null

[JIRA]

Gábor Auth created CASSANDRA-12238:
--

 Summary: Unexpected exception during request 
java.lang.IndexOutOfBoundsException: null
 Key: CASSANDRA-12238
 URL: https://issues.apache.org/jira/browse/CASSANDRA-12238
 Project: Cassandra
  Issue Type: Bug
 Environment: datastax-ddc-3.7.0, CentOS 7, x86, JDK 1.8.0u91
Reporter: Gábor Auth


Our two DCs and eight nodes cluster throws sometimes:
{code}
ERROR [SharedPool-Worker-25] 2016-07-19 16:22:14,643 ErrorMessage.java:338 - 
Unexpected exception during request
java.lang.IndexOutOfBoundsException: null
at java.nio.Buffer.checkIndex(Buffer.java:546) ~[na:1.8.0_91]
at java.nio.HeapByteBuffer.getShort(HeapByteBuffer.java:314) 
~[na:1.8.0_91]
at 
org.apache.cassandra.db.context.CounterContext.headerLength(CounterContext.java:141)
 ~[apache-cassandra-3.7.0.jar:3.7.0]
at 
org.apache.cassandra.db.context.CounterContext.access$100(CounterContext.java:76)
 ~[apache-cassandra-3.7.0.jar:3.7.0]
at 
org.apache.cassandra.db.context.CounterContext$ContextState.(CounterContext.java:758)
 ~[apache-cassandra-3.7.0.jar:3.7.0]
at 
org.apache.cassandra.db.context.CounterContext$ContextState.wrap(CounterContext.java:765)
 ~[apache-cassandra-3.7.0.jar:3.7.0]
at 
org.apache.cassandra.db.context.CounterContext.merge(CounterContext.java:271) 
~[apache-cassandra-3.7.0.jar:3.7.0]
at 
org.apache.cassandra.db.Conflicts.mergeCounterValues(Conflicts.java:76) 
~[apache-cassandra-3.7.0.jar:3.7.0]
at org.apache.cassandra.db.rows.Cells.reconcile(Cells.java:143) 
~[apache-cassandra-3.7.0.jar:3.7.0]
at 
org.apache.cassandra.db.rows.Row$Merger$ColumnDataReducer.getReduced(Row.java:614)
 ~[apache-cassandra-3.7.0.jar:3.7.0]
at 
org.apache.cassandra.db.rows.Row$Merger$ColumnDataReducer.getReduced(Row.java:572)
 ~[apache-cassandra-3.7.0.jar:3.7.0]
at 
org.apache.cassandra.utils.MergeIterator$ManyToOne.consume(MergeIterator.java:217)
 ~[apache-cassandra-3.7.0.jar:3.7.0]
at 
org.apache.cassandra.utils.MergeIterator$ManyToOne.computeNext(MergeIterator.java:156)
 ~[apache-cassandra-3.7.0.jar:3.7.0]
at 
org.apache.cassandra.utils.AbstractIterator.hasNext(AbstractIterator.java:47) 
~[apache-cassandra-3.7.0.jar:3.7.0]
at org.apache.cassandra.db.rows.Row$Merger.merge(Row.java:549) 
~[apache-cassandra-3.7.0.jar:3.7.0]
at 
org.apache.cassandra.db.rows.UnfilteredRowIterators$UnfilteredRowMergeIterator$MergeReducer.getReduced(UnfilteredRowIterators.java:473)
 ~[apache-cassandra-3.7.0.jar:3.7.0]
at 
org.apache.cassandra.db.rows.UnfilteredRowIterators$UnfilteredRowMergeIterator$MergeReducer.getReduced(UnfilteredRowIterators.java:437)
 ~[apache-cassandra-3.7.0.jar:3.7.0]
at 
org.apache.cassandra.utils.MergeIterator$ManyToOne.consume(MergeIterator.java:217)
 ~[apache-cassandra-3.7.0.jar:3.7.0]
at 
org.apache.cassandra.utils.MergeIterator$ManyToOne.computeNext(MergeIterator.java:156)
 ~[apache-cassandra-3.7.0.jar:3.7.0]
at 
org.apache.cassandra.utils.AbstractIterator.hasNext(AbstractIterator.java:47) 
~[apache-cassandra-3.7.0.jar:3.7.0]
at 
org.apache.cassandra.db.rows.UnfilteredRowIterators$UnfilteredRowMergeIterator.computeNext(UnfilteredRowIterators.java:419)
 ~[apache-cassandra-3.7.0.jar:3.7.0]
at 
org.apache.cassandra.db.rows.UnfilteredRowIterators$UnfilteredRowMergeIterator.computeNext(UnfilteredRowIterators.java:279)
 ~[apache-cassandra-3.7.0.jar:3.7.0]
at 
org.apache.cassandra.utils.AbstractIterator.hasNext(AbstractIterator.java:47) 
~[apache-cassandra-3.7.0.jar:3.7.0]
at 
org.apache.cassandra.db.transform.BaseRows.hasNext(BaseRows.java:112) 
~[apache-cassandra-3.7.0.jar:3.7.0]
at 
org.apache.cassandra.db.transform.FilteredRows.isEmpty(FilteredRows.java:30) 
~[apache-cassandra-3.7.0.jar:3.7.0]
at 
org.apache.cassandra.db.transform.Filter.closeIfEmpty(Filter.java:49) 
~[apache-cassandra-3.7.0.jar:3.7.0]
at 
org.apache.cassandra.db.transform.Filter.applyToPartition(Filter.java:22) 
~[apache-cassandra-3.7.0.jar:3.7.0]
at 
org.apache.cassandra.db.transform.Filter.applyToPartition(Filter.java:6) 
~[apache-cassandra-3.7.0.jar:3.7.0]
at 
org.apache.cassandra.db.transform.BasePartitions.hasNext(BasePartitions.java:76)
 ~[apache-cassandra-3.7.0.jar:3.7.0]
at 
org.apache.cassandra.cql3.statements.SelectStatement.process(SelectStatement.java:735)
 ~[apache-cassandra-3.7.0.jar:3.7.0]
at 
org.apache.cassandra.cql3.statements.SelectStatement.processResults(SelectStatement.java:410)
 ~[apache-cassandra-3.7.0.jar:3.7.0]
at 
org.apache.cassandra.cql3.statements.SelectStatement.execute(SelectStatement.java:363)
 ~[apache-cassandra-3.7.0.jar:3.7.0]
at 
org.apache.cassandra.cql3.statements.SelectStatement.execute(SelectStatement.java:237)
 

[jira] [Comment Edited] (CASSANDRA-12218) IndexSummaryManagerTest.testCancelIndex is flaky

[Sam Tunnicliffe (JIRA)]

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

Sam Tunnicliffe edited comment on CASSANDRA-12218 at 7/19/16 4:05 PM:
--

The problem is that there is only a single point in 
{{IndexSummaryRedistribution::redistributeSummaries}} which checks the flag to 
see if it should halt. On occasion, this point is passed before the stop is 
actually requested, the redistribution completes normally and no 
{{CompactionInterruptedException}} is thrown. 

With the linked branch, I haven't been able to repro the failure in over 150 
runs (without it I couldn't get above ~50 iterations without a failure). 

The patch may seem quite large, but it's really just a refactoring. The 
significant change is an extension of {{IndexSummaryRedistribution}} that 
pauses until signaled before running. Only {{testCancelIndex}} makes use of 
this, all other tests are unchanged.

||branch||testall||
|[12218-3.9|https://github.com/beobal/cassandra/tree/12218-3.9]|[testall|http://cassci.datastax.com/view/Dev/view/beobal/job/beobal-12218-3.9-testall]|



was (Author: beobal):
The problem is that there is only a single point in 
{{IndexSummaryRedistribution::redistributeSummaries}} which checks the flag to 
see if it should halt. On occasion, this point is passed before the stop is 
actually requested, the redistribution completes normally and no 
{{CompactionInterruptedException}} is thrown. 

With the linked branch, I haven't been able to repro the failure in over 150 
runs (without it I couldn't get above ~50 iterations without a failure). 

The patch may seem quite large, but it's really just a refactoring. The 
significant change is an extension of {{IndexSummaryRedistribution}} that 
pauses until signaled before running. Only {{testCancelIndex}} makes use of 
this, all other tests are unchanged.

||branch||testall||dtest||
|[12218-3.9|https://github.com/beobal/cassandra/tree/12218-3.9]|[testall|http://cassci.datastax.com/view/Dev/view/beobal/job/beobal-12218-3.9-testall]|[dtest|http://cassci.datastax.com/view/Dev/view/beobal/job/beobal-12218-3.9-dtest]|


> IndexSummaryManagerTest.testCancelIndex is flaky
> 
>
> Key: CASSANDRA-12218
> URL: https://issues.apache.org/jira/browse/CASSANDRA-12218
> Project: Cassandra
>  Issue Type: Test
>Reporter: Joshua McKenzie
>Assignee: Sam Tunnicliffe
>  Labels: unittest
>
> Test appears to be flaky given the history:
> [History|http://cassci.datastax.com/job/cassandra-3.9_testall/25/testReport/org.apache.cassandra.io.sstable/IndexSummaryManagerTest/testCancelIndex/history/]
> {noformat}
> Error Message
> Expected compaction interrupted exception
> Stacktrace
> junit.framework.AssertionFailedError: Expected compaction interrupted 
> exception
>   at 
> org.apache.cassandra.io.sstable.IndexSummaryManagerTest.testCancelIndex(IndexSummaryManagerTest.java:655)
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (CASSANDRA-12236) RTE from new CDC column breaks in flight queries.

[Joshua McKenzie (JIRA)]

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

Joshua McKenzie commented on CASSANDRA-12236:
-

To clarify, this has nothing to do with CDC other than it being the first 
feature that's changed system tables since 3.0 hit. In a post CASSANDRA-8099 
world, the fact that we send across all system tables and reject queries with 
unknown columns means that any changes to the system schema would cause this. 
CDC just happens to be the first feature we've added since then that changes 
schema.

 Also - at the time that I added that message to NEWS.txt, from discussion 
offline we didn't realize those exceptions would lead to internode 
communication breaks.

> RTE from new CDC column breaks in flight queries.
> -
>
> Key: CASSANDRA-12236
> URL: https://issues.apache.org/jira/browse/CASSANDRA-12236
> Project: Cassandra
>  Issue Type: Bug
>Reporter: Jeremiah Jordan
>Priority: Blocker
> Fix For: 3.8
>
>
> This RTE is not harmless. It will cause the internode connection to break 
> which will cause all in flight requests between these nodes to die/timeout.
> {noformat}
> - Due to changes in schema migration handling and the storage format 
> after 3.0, you will
>   see error messages such as:
>  "java.lang.RuntimeException: Unknown column cdc during 
> deserialization"
>   in your system logs on a mixed-version cluster during upgrades. This 
> error message
>   is harmless and due to the 3.8 nodes having cdc added to their schema 
> tables while
>   the <3.8 nodes do not. This message should cease once all nodes are 
> upgraded to 3.8.
>   As always, refrain from schema changes during cluster upgrades.
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (CASSANDRA-12237) Cassandra stress graphing is broken

[Christopher Batey (JIRA)]

Christopher Batey created CASSANDRA-12237:
-

 Summary: Cassandra stress graphing is broken
 Key: CASSANDRA-12237
 URL: https://issues.apache.org/jira/browse/CASSANDRA-12237
 Project: Cassandra
  Issue Type: Bug
  Components: Tools
Reporter: Christopher Batey
Assignee: Christopher Batey


Cassandra stress relies on a tmp file with the stress output so it can parse it 
and put it the the graph html.

However the contents of this file is now broken:

{code}
Sleeping 2s...Sleeping 2s...
Sleeping 2s...
Warming up WRITE with 5 iterations...Warming up WRITE with 5 
iterations...
Warming up WRITE with 5 iterations...
Running WRITE with 500 threads 10 secondsRunning WRITE with 500 threads 10 
seconds
Running WRITE with 500 threads 10 seconds

...
{code}

This is as we create a {code}MultiPrintStream{code} that inherits from 
{code}PrintWriter{code} and then delegate the call to super as well as a list 
of other PrintWriters

The call to super for println comes back into our print method so every line 
gets logged multiple times as we do the for (PrintStream s: newStreams) many 
times.

We can change this to use composition and use our own interface if we want to 
use a composite for logging the results

This results in the parsing of this file not quite working and the aggregate 
stats not working in produced graphs.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (CASSANDRA-12236) RTE from new CDC column breaks in flight queries.

[Jeremiah Jordan (JIRA)]

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

Jeremiah Jordan updated CASSANDRA-12236:

Fix Version/s: 3.8

> RTE from new CDC column breaks in flight queries.
> -
>
> Key: CASSANDRA-12236
> URL: https://issues.apache.org/jira/browse/CASSANDRA-12236
> Project: Cassandra
>  Issue Type: Bug
>Reporter: Jeremiah Jordan
>Priority: Blocker
> Fix For: 3.8
>
>
> This RTE is not harmless. It will cause the internode connection to break 
> which will cause all in flight requests between these nodes to die/timeout.
> {noformat}
> - Due to changes in schema migration handling and the storage format 
> after 3.0, you will
>   see error messages such as:
>  "java.lang.RuntimeException: Unknown column cdc during 
> deserialization"
>   in your system logs on a mixed-version cluster during upgrades. This 
> error message
>   is harmless and due to the 3.8 nodes having cdc added to their schema 
> tables while
>   the <3.8 nodes do not. This message should cease once all nodes are 
> upgraded to 3.8.
>   As always, refrain from schema changes during cluster upgrades.
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (CASSANDRA-12236) RTE from new CDC column breaks in flight queries.

[Jeremiah Jordan (JIRA)]

Jeremiah Jordan created CASSANDRA-12236:
---

 Summary: RTE from new CDC column breaks in flight queries.
 Key: CASSANDRA-12236
 URL: https://issues.apache.org/jira/browse/CASSANDRA-12236
 Project: Cassandra
  Issue Type: Bug
Reporter: Jeremiah Jordan
Priority: Blocker


This RTE is not harmless. It will cause the internode connection to break which 
will cause all in flight requests between these nodes to die/timeout.


{noformat}

- Due to changes in schema migration handling and the storage format after 
3.0, you will
  see error messages such as:
 "java.lang.RuntimeException: Unknown column cdc during deserialization"
  in your system logs on a mixed-version cluster during upgrades. This 
error message
  is harmless and due to the 3.8 nodes having cdc added to their schema 
tables while
  the <3.8 nodes do not. This message should cease once all nodes are 
upgraded to 3.8.
  As always, refrain from schema changes during cluster upgrades.
{noformat}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (CASSANDRA-12218) IndexSummaryManagerTest.testCancelIndex is flaky

[Sam Tunnicliffe (JIRA)]

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

Sam Tunnicliffe updated CASSANDRA-12218:


The problem is that there is only a single point in 
{{IndexSummaryRedistribution::redistributeSummaries}} which checks the flag to 
see if it should halt. On occasion, this point is passed before the stop is 
actually requested, the redistribution completes normally and no 
{{CompactionInterruptedException}} is thrown. 

With the linked branch, I haven't been able to repro the failure in over 150 
runs (without it I couldn't get above ~50 iterations without a failure). 

The patch may seem quite large, but it's really just a refactoring. The 
significant change is an extension of {{IndexSummaryRedistribution}} that 
pauses until signaled before running. Only {{testCancelIndex}} makes use of 
this, all other tests are unchanged.

||branch||testall||dtest||
|[12218-3.9|https://github.com/beobal/cassandra/tree/12218-3.9]|[testall|http://cassci.datastax.com/view/Dev/view/beobal/job/beobal-12218-3.9-testall]|[dtest|http://cassci.datastax.com/view/Dev/view/beobal/job/beobal-12218-3.9-dtest]|


> IndexSummaryManagerTest.testCancelIndex is flaky
> 
>
> Key: CASSANDRA-12218
> URL: https://issues.apache.org/jira/browse/CASSANDRA-12218
> Project: Cassandra
>  Issue Type: Test
>Reporter: Joshua McKenzie
>Assignee: Sam Tunnicliffe
>  Labels: unittest
>
> Test appears to be flaky given the history:
> [History|http://cassci.datastax.com/job/cassandra-3.9_testall/25/testReport/org.apache.cassandra.io.sstable/IndexSummaryManagerTest/testCancelIndex/history/]
> {noformat}
> Error Message
> Expected compaction interrupted exception
> Stacktrace
> junit.framework.AssertionFailedError: Expected compaction interrupted 
> exception
>   at 
> org.apache.cassandra.io.sstable.IndexSummaryManagerTest.testCancelIndex(IndexSummaryManagerTest.java:655)
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (CASSANDRA-10202) simplify CommitLogSegmentManager

[Branimir Lambov (JIRA)]

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

Branimir Lambov commented on CASSANDRA-10202:
-

Rebased and rerun tests, same location:
|[code|https://github.com/blambov/cassandra/tree/10202-commitlog]|[utest|http://cassci.datastax.com/job/blambov-10202-commitlog-testall/]|[dtest|http://cassci.datastax.com/job/blambov-10202-commitlog-dtest/]|
Tests appear ok: dtests improve; there are new unit test failures, one of them 
failing and the other flaky on trunk.

> simplify CommitLogSegmentManager
> 
>
> Key: CASSANDRA-10202
> URL: https://issues.apache.org/jira/browse/CASSANDRA-10202
> Project: Cassandra
>  Issue Type: Improvement
>  Components: Local Write-Read Paths
>Reporter: Jonathan Ellis
>Assignee: Branimir Lambov
>Priority: Minor
>
> Now that we only keep one active segment around we can simplify this from the 
> old recycling design.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (CASSANDRA-12235) dtest failure in bootstrap_test.TestBootstrap.consistent_range_movement_true_with_ks_rf1_should_succeed_test

[Philip Thompson (JIRA)]

Philip Thompson created CASSANDRA-12235:
---

 Summary: dtest failure in 
bootstrap_test.TestBootstrap.consistent_range_movement_true_with_ks_rf1_should_succeed_test
 Key: CASSANDRA-12235
 URL: https://issues.apache.org/jira/browse/CASSANDRA-12235
 Project: Cassandra
  Issue Type: Test
Reporter: Philip Thompson
Assignee: DS Test Eng


example failure:

http://cassci.datastax.com/job/cassandra-3.8_novnode_dtest/5/testReport/bootstrap_test/TestBootstrap/consistent_range_movement_true_with_ks_rf1_should_succeed_test

Failed on CassCI build cassandra-3.8_novnode_dtest #5



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (CASSANDRA-12180) Should be able to override compaction space check

[Carl Yeksigian (JIRA)]

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

Carl Yeksigian commented on CASSANDRA-12180:


Makes sense. I'm running CI on this now; if it's clean, I'll commit.

> Should be able to override compaction space check
> -
>
> Key: CASSANDRA-12180
> URL: https://issues.apache.org/jira/browse/CASSANDRA-12180
> Project: Cassandra
>  Issue Type: Improvement
>Reporter: sankalp kohli
>Assignee: sankalp kohli
>Priority: Trivial
> Attachments: CASSANDRA-12180_3.0.txt
>
>
> If there's not enough space for a compaction it won't do it and print the 
> exception below. Sometimes we know compaction will free up lot of space since 
> an ETL job could have inserted a lot of deletes. This override helps in this 
> case. 
> ERROR [CompactionExecutor:17] CassandraDaemon.java (line 258) Exception in 
> thread Thread
> [CompactionExecutor:17,1,main]
> java.lang.RuntimeException: Not enough space for compaction, estimated 
> sstables = 1552, expected
> write size = 260540558535
> at org.apache.cassandra.db.compaction.CompactionTask.checkAvailableDiskSpace
> (CompactionTask.java:306)
> at 
> org.apache.cassandra.db.compaction.CompactionTask.runMayThrow(CompactionTask.
> java:106)
> at org.apache.cassandra.utils.WrappedRunnable.run(WrappedRunnable.java:28)
> at 
> org.apache.cassandra.db.compaction.CompactionTask.executeInternal(CompactionTask.
> java:60)
> at 
> org.apache.cassandra.db.compaction.AbstractCompactionTask.execute(AbstractCompactionTask.
> java:59)
> at 
> org.apache.cassandra.db.compaction.CompactionManager$BackgroundCompactionTask.run
> (CompactionManager.java:198)
> at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
> at java.util.concurrent.FutureTask.run(FutureTask.java:262)
> 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
(v6.3.4#6332)

[jira] [Commented] (CASSANDRA-12214) cqlshlib test failure: cqlshlib.test.remove_test_db

[Philip Thompson (JIRA)]

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

Philip Thompson commented on CASSANDRA-12214:
-

The change at line 
https://github.com/stef1927/cassandra/commit/d921695f9f8a588f1e78cf7a42260d74065e45aa#diff-efd78e3bd026e3c9d12ae822f1eb1497R39
 seems correct, but isn't mentioned in this ticket (unless I'm missing 
something). +1 if that's intentional.

>  cqlshlib test failure: cqlshlib.test.remove_test_db
> 
>
> Key: CASSANDRA-12214
> URL: https://issues.apache.org/jira/browse/CASSANDRA-12214
> Project: Cassandra
>  Issue Type: Bug
>Reporter: Craig Kodman
>Assignee: Stefania
>  Labels: cqlsh
>
> [~Stefania]  
> http://cassci.datastax.com/job/cassandra-3.9_cqlsh_tests/lastCompletedBuild/testReport/
> Hello, these three tests are failing:
> cqlshlib.test.remove_test_db
> cqlshlib.test.test_cqlsh_completion.TestCqlshCompletion.test_complete_in_create_columnfamily
> cqlshlib.test.test_cqlsh_completion.TestCqlshCompletion.test_complete_in_create_table
> Can you look at them, please?  Thank you!



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Assigned] (CASSANDRA-12218) IndexSummaryManagerTest.testCancelIndex is flaky

[Sam Tunnicliffe (JIRA)]

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

Sam Tunnicliffe reassigned CASSANDRA-12218:
---

Assignee: Sam Tunnicliffe

> IndexSummaryManagerTest.testCancelIndex is flaky
> 
>
> Key: CASSANDRA-12218
> URL: https://issues.apache.org/jira/browse/CASSANDRA-12218
> Project: Cassandra
>  Issue Type: Test
>Reporter: Joshua McKenzie
>Assignee: Sam Tunnicliffe
>  Labels: unittest
>
> Test appears to be flaky given the history:
> [History|http://cassci.datastax.com/job/cassandra-3.9_testall/25/testReport/org.apache.cassandra.io.sstable/IndexSummaryManagerTest/testCancelIndex/history/]
> {noformat}
> Error Message
> Expected compaction interrupted exception
> Stacktrace
> junit.framework.AssertionFailedError: Expected compaction interrupted 
> exception
>   at 
> org.apache.cassandra.io.sstable.IndexSummaryManagerTest.testCancelIndex(IndexSummaryManagerTest.java:655)
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[1/3] cassandra git commit: Attempt to fix flaky CommitLogTest

[jmckenzie]

Repository: cassandra
Updated Branches:
  refs/heads/cassandra-3.9 d4ced2453 -> 8049bc886
  refs/heads/trunk 12911352d -> 614eebdff


Attempt to fix flaky CommitLogTest

Patch by jmckenzie; reviewed by slebresne for CASSANDRA-12206


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

Branch: refs/heads/cassandra-3.9
Commit: 8049bc8869939a0b083377cf4c38f1274e9e1f3a
Parents: d4ced24
Author: Josh McKenzie 
Authored: Fri Jul 15 12:40:39 2016 -0400
Committer: Josh McKenzie 
Committed: Tue Jul 19 10:58:38 2016 -0400

--
 .../cassandra/db/commitlog/CommitLogTest.java   | 22 +---
 1 file changed, 15 insertions(+), 7 deletions(-)
--


http://git-wip-us.apache.org/repos/asf/cassandra/blob/8049bc88/test/unit/org/apache/cassandra/db/commitlog/CommitLogTest.java
--
diff --git a/test/unit/org/apache/cassandra/db/commitlog/CommitLogTest.java 
b/test/unit/org/apache/cassandra/db/commitlog/CommitLogTest.java
index eff972d..23ec58b 100644
--- a/test/unit/org/apache/cassandra/db/commitlog/CommitLogTest.java
+++ b/test/unit/org/apache/cassandra/db/commitlog/CommitLogTest.java
@@ -35,6 +35,7 @@ import org.junit.runners.Parameterized.Parameters;
 
 import org.apache.cassandra.SchemaLoader;
 import org.apache.cassandra.Util;
+import org.apache.cassandra.config.CFMetaData;
 import org.apache.cassandra.config.DatabaseDescriptor;
 import org.apache.cassandra.config.ParameterizedClass;
 import org.apache.cassandra.db.ColumnFamilyStore;
@@ -608,7 +609,7 @@ public class CommitLogTest
 
 CommitLog.instance.sync(true);
 
-SimpleCountingReplayer replayer = new 
SimpleCountingReplayer(CommitLog.instance, CommitLogPosition.NONE);
+SimpleCountingReplayer replayer = new 
SimpleCountingReplayer(CommitLog.instance, CommitLogPosition.NONE, 
cfs.metadata);
 List activeSegments = 
CommitLog.instance.getActiveSegmentNames();
 Assert.assertFalse(activeSegments.isEmpty());
 
@@ -645,7 +646,7 @@ public class CommitLogTest
 
 CommitLog.instance.sync(true);
 
-SimpleCountingReplayer replayer = new 
SimpleCountingReplayer(CommitLog.instance, commitLogPosition);
+SimpleCountingReplayer replayer = new 
SimpleCountingReplayer(CommitLog.instance, commitLogPosition, cfs.metadata);
 List activeSegments = 
CommitLog.instance.getActiveSegmentNames();
 Assert.assertFalse(activeSegments.isEmpty());
 
@@ -658,15 +659,15 @@ public class CommitLogTest
 class SimpleCountingReplayer extends CommitLogReplayer
 {
 private final CommitLogPosition filterPosition;
-private CommitLogReader reader;
+private final CFMetaData metadata;
 int cells;
 int skipped;
 
-SimpleCountingReplayer(CommitLog commitLog, CommitLogPosition 
filterPosition)
+SimpleCountingReplayer(CommitLog commitLog, CommitLogPosition 
filterPosition, CFMetaData cfm)
 {
 super(commitLog, filterPosition, Collections.emptyMap(), 
ReplayFilter.create());
 this.filterPosition = filterPosition;
-this.reader = new CommitLogReader();
+this.metadata = cfm;
 }
 
 @SuppressWarnings("resource")
@@ -680,8 +681,15 @@ public class CommitLogTest
 return;
 }
 for (PartitionUpdate partitionUpdate : m.getPartitionUpdates())
-for (Row row : partitionUpdate)
-cells += Iterables.size(row.cells());
+{
+// Only process mutations for the CF's we're testing against, 
since we can't deterministically predict
+// whether or not system keyspaces will be mutated during a 
test.
+if (partitionUpdate.metadata().cfName.equals(metadata.cfName))
+{
+for (Row row : partitionUpdate)
+cells += Iterables.size(row.cells());
+}
+}
 }
 }
 }

[jira] [Commented] (CASSANDRA-12226) Nodetool tpstats output could benefit from "events since" information

[Wei Deng (JIRA)]

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

Wei Deng commented on CASSANDRA-12226:
--

All of the dropped message counts start at the JVM start, so you can get the 
information (on this additional line you suggested) indirectly from "nodetool 
info" uptime, or a JMX metrics. Are you saying you want that information to be 
directly displayed in "nodetool tpstats" output?

> Nodetool tpstats output could benefit from "events since" information
> -
>
> Key: CASSANDRA-12226
> URL: https://issues.apache.org/jira/browse/CASSANDRA-12226
> Project: Cassandra
>  Issue Type: Improvement
>  Components: Tools
>Reporter: Mark Curtis
>Priority: Minor
>
> The output of tools like {{nodetool tpstats}} are very useful for seeing 
> historical counters of things like dropped mutations etc.
> What would be very useful (if possible of course) is something above these to 
> say "since " to help the user understand how long these stats apply and 
> when we started collecting them.
> This might extend to other outputs like histograms, even if these are more 
> like "since you last run this" it might still be useful.
> Here's an example:
> {code}
> Pool NameActive   Pending  Completed   Blocked  All 
> time blocked
> CounterMutationStage  0 0  0 0
>  0
> ReadStage 0 0  111284390 0
>  0
> RequestResponseStage  0 0  297011175 0
>  0
> MutationStage 0 0  134532012 0
>  0
> ReadRepairStage   0 0 742114 0
>  0
> GossipStage   0 05639150 0
>  0
> CacheCleanupExecutor  0 0  0 0
>  0
> MigrationStage0 0315 0
>  0
> ValidationExecutor0 0 482844 0
>  0
> Sampler   0 0  0 0
>  0
> MemtableReclaimMemory 0 0 164619 0
>  0
> InternalResponseStage 0 0 792376 0
>  0
> AntiEntropyStage  0 05402052 0
>  0
> MiscStage 0 0   1197 0
>  0
> CommitLogArchiver 0 0  0 0
>  0
> MemtableFlushWriter   0 0 164564 0
>  0
> PendingRangeCalculator0 0 70 0
>  0
> MemtablePostFlush 0 0 811892 0
>  0
> CompactionExecutor7113250908 0
>  0
> AntiEntropySessions   4   218 142144 0
>  0
> HintedHandoff 2 7602 0
>  0
> Native-Transport-Requests 0 0   97372556 0
> 34
> Dropped messages since 2016-07-18 01:00:04
> Message type   Dropped
> RANGE_SLICE  0
> READ_REPAIR  0
> PAGED_RANGE  0
> BINARY   0
> READ 0
> MUTATION 0
> _TRACE  179705
> REQUEST_RESPONSE 0
> COUNTER_MUTATION 0
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[2/3] cassandra git commit: Attempt to fix flaky CommitLogTest

[jmckenzie]

Attempt to fix flaky CommitLogTest

Patch by jmckenzie; reviewed by slebresne for CASSANDRA-12206


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

Branch: refs/heads/trunk
Commit: 8049bc8869939a0b083377cf4c38f1274e9e1f3a
Parents: d4ced24
Author: Josh McKenzie 
Authored: Fri Jul 15 12:40:39 2016 -0400
Committer: Josh McKenzie 
Committed: Tue Jul 19 10:58:38 2016 -0400

--
 .../cassandra/db/commitlog/CommitLogTest.java   | 22 +---
 1 file changed, 15 insertions(+), 7 deletions(-)
--


http://git-wip-us.apache.org/repos/asf/cassandra/blob/8049bc88/test/unit/org/apache/cassandra/db/commitlog/CommitLogTest.java
--
diff --git a/test/unit/org/apache/cassandra/db/commitlog/CommitLogTest.java 
b/test/unit/org/apache/cassandra/db/commitlog/CommitLogTest.java
index eff972d..23ec58b 100644
--- a/test/unit/org/apache/cassandra/db/commitlog/CommitLogTest.java
+++ b/test/unit/org/apache/cassandra/db/commitlog/CommitLogTest.java
@@ -35,6 +35,7 @@ import org.junit.runners.Parameterized.Parameters;
 
 import org.apache.cassandra.SchemaLoader;
 import org.apache.cassandra.Util;
+import org.apache.cassandra.config.CFMetaData;
 import org.apache.cassandra.config.DatabaseDescriptor;
 import org.apache.cassandra.config.ParameterizedClass;
 import org.apache.cassandra.db.ColumnFamilyStore;
@@ -608,7 +609,7 @@ public class CommitLogTest
 
 CommitLog.instance.sync(true);
 
-SimpleCountingReplayer replayer = new 
SimpleCountingReplayer(CommitLog.instance, CommitLogPosition.NONE);
+SimpleCountingReplayer replayer = new 
SimpleCountingReplayer(CommitLog.instance, CommitLogPosition.NONE, 
cfs.metadata);
 List activeSegments = 
CommitLog.instance.getActiveSegmentNames();
 Assert.assertFalse(activeSegments.isEmpty());
 
@@ -645,7 +646,7 @@ public class CommitLogTest
 
 CommitLog.instance.sync(true);
 
-SimpleCountingReplayer replayer = new 
SimpleCountingReplayer(CommitLog.instance, commitLogPosition);
+SimpleCountingReplayer replayer = new 
SimpleCountingReplayer(CommitLog.instance, commitLogPosition, cfs.metadata);
 List activeSegments = 
CommitLog.instance.getActiveSegmentNames();
 Assert.assertFalse(activeSegments.isEmpty());
 
@@ -658,15 +659,15 @@ public class CommitLogTest
 class SimpleCountingReplayer extends CommitLogReplayer
 {
 private final CommitLogPosition filterPosition;
-private CommitLogReader reader;
+private final CFMetaData metadata;
 int cells;
 int skipped;
 
-SimpleCountingReplayer(CommitLog commitLog, CommitLogPosition 
filterPosition)
+SimpleCountingReplayer(CommitLog commitLog, CommitLogPosition 
filterPosition, CFMetaData cfm)
 {
 super(commitLog, filterPosition, Collections.emptyMap(), 
ReplayFilter.create());
 this.filterPosition = filterPosition;
-this.reader = new CommitLogReader();
+this.metadata = cfm;
 }
 
 @SuppressWarnings("resource")
@@ -680,8 +681,15 @@ public class CommitLogTest
 return;
 }
 for (PartitionUpdate partitionUpdate : m.getPartitionUpdates())
-for (Row row : partitionUpdate)
-cells += Iterables.size(row.cells());
+{
+// Only process mutations for the CF's we're testing against, 
since we can't deterministically predict
+// whether or not system keyspaces will be mutated during a 
test.
+if (partitionUpdate.metadata().cfName.equals(metadata.cfName))
+{
+for (Row row : partitionUpdate)
+cells += Iterables.size(row.cells());
+}
+}
 }
 }
 }

[jira] [Comment Edited] (CASSANDRA-12206) CommitLogTest.replaySimple failure

[Joshua McKenzie (JIRA)]

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

Joshua McKenzie edited comment on CASSANDRA-12206 at 7/19/16 3:02 PM:
--

Swapped to cfId comparison and committed. Thanks.

Edit: looks like I didn't -a my amend locally so it's still comparing name. 
Should be fine for the utest, but I'll keep that in mind for anything in the 
future.


was (Author: joshuamckenzie):
Swapped to cfId comparison and committed. Thanks.

> CommitLogTest.replaySimple failure
> --
>
> Key: CASSANDRA-12206
> URL: https://issues.apache.org/jira/browse/CASSANDRA-12206
> Project: Cassandra
>  Issue Type: Test
> Environment: cassandra-3.9 CI
>Reporter: Joshua McKenzie
>Assignee: Joshua McKenzie
> Fix For: 3.9
>
>
> Fails on both regular and compression runs.
> {noformat}
> Error Message
> expected:<2> but was:<8>
> Stacktrace
> junit.framework.AssertionFailedError: expected:<2> but was:<8>
>   at 
> org.apache.cassandra.db.commitlog.CommitLogTest.replaySimple(CommitLogTest.java:618)
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (CASSANDRA-12206) CommitLogTest.replaySimple failure

[Joshua McKenzie (JIRA)]

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

Joshua McKenzie updated CASSANDRA-12206:

Reviewer: Sylvain Lebresne  (was: Benjamin Lerer)

> CommitLogTest.replaySimple failure
> --
>
> Key: CASSANDRA-12206
> URL: https://issues.apache.org/jira/browse/CASSANDRA-12206
> Project: Cassandra
>  Issue Type: Test
> Environment: cassandra-3.9 CI
>Reporter: Joshua McKenzie
>Assignee: Joshua McKenzie
> Fix For: 3.9
>
>
> Fails on both regular and compression runs.
> {noformat}
> Error Message
> expected:<2> but was:<8>
> Stacktrace
> junit.framework.AssertionFailedError: expected:<2> but was:<8>
>   at 
> org.apache.cassandra.db.commitlog.CommitLogTest.replaySimple(CommitLogTest.java:618)
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (CASSANDRA-12206) CommitLogTest.replaySimple failure

[Joshua McKenzie (JIRA)]

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

Joshua McKenzie updated CASSANDRA-12206:

   Resolution: Fixed
Fix Version/s: 3.9
   Status: Resolved  (was: Patch Available)

Swapped to cfId comparison and committed. Thanks.

> CommitLogTest.replaySimple failure
> --
>
> Key: CASSANDRA-12206
> URL: https://issues.apache.org/jira/browse/CASSANDRA-12206
> Project: Cassandra
>  Issue Type: Test
> Environment: cassandra-3.9 CI
>Reporter: Joshua McKenzie
>Assignee: Joshua McKenzie
> Fix For: 3.9
>
>
> Fails on both regular and compression runs.
> {noformat}
> Error Message
> expected:<2> but was:<8>
> Stacktrace
> junit.framework.AssertionFailedError: expected:<2> but was:<8>
>   at 
> org.apache.cassandra.db.commitlog.CommitLogTest.replaySimple(CommitLogTest.java:618)
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

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

[jmckenzie]

Merge branch 'cassandra-3.9' into trunk


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

Branch: refs/heads/trunk
Commit: 614eebdff679318ae6c2c0a716b1c6d52f6a
Parents: 1291135 8049bc8
Author: Josh McKenzie 
Authored: Tue Jul 19 10:59:00 2016 -0400
Committer: Josh McKenzie 
Committed: Tue Jul 19 10:59:00 2016 -0400

--
 .../cassandra/db/commitlog/CommitLogTest.java   | 22 +---
 1 file changed, 15 insertions(+), 7 deletions(-)
--


http://git-wip-us.apache.org/repos/asf/cassandra/blob/614eebdf/test/unit/org/apache/cassandra/db/commitlog/CommitLogTest.java
--

[jira] [Commented] (CASSANDRA-4650) RangeStreamer should be smarter when picking endpoints for streaming in case of N >=3 in each DC.

[T Jake Luciani (JIRA)]

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

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

bq. I am not sure which capacity are you talking about. Capacity of edges in 
the graph. If yes which ones.

Yes. All of them.

You are using this "Ford Fulkerson Algorithm" but I don't understand how you 
are defining capacity.  Perhaps some better comments on this in the code as 
well would help regarding this.

> RangeStreamer should be smarter when picking endpoints for streaming in case 
> of N >=3 in each DC.  
> ---
>
> Key: CASSANDRA-4650
> URL: https://issues.apache.org/jira/browse/CASSANDRA-4650
> Project: Cassandra
>  Issue Type: Improvement
>Affects Versions: 1.1.5
>Reporter: sankalp kohli
>Assignee: sankalp kohli
>Priority: Minor
>  Labels: streaming
> Attachments: CASSANDRA-4650_trunk.txt, photo-1.JPG
>
>   Original Estimate: 24h
>  Remaining Estimate: 24h
>
> getRangeFetchMap method in RangeStreamer should pick unique nodes to stream 
> data from when number of replicas in each DC is three or more. 
> When N>=3 in a DC, there are two options for streaming a range. Consider an 
> example of 4 nodes in one datacenter and replication factor of 3. 
> If a node goes down, it needs to recover 3 ranges of data. With current code, 
> two nodes could get selected as it orders the node by proximity. 
> We ideally will want to select 3 nodes for streaming the data. We can do this 
> by selecting unique nodes for each range.  
> Advantages:
> This will increase the performance of bootstrapping a node and will also put 
> less pressure on nodes serving the data. 
> Note: This does not affect if N < 3 in each DC as then it streams data from 
> only 2 nodes. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (CASSANDRA-11988) NullPointerExpception when reading/compacting table

[Carl Yeksigian (JIRA)]

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

Carl Yeksigian commented on CASSANDRA-11988:


That does look like a better way to fix it.

+1 once CI is clean

> NullPointerExpception when reading/compacting table
> ---
>
> Key: CASSANDRA-11988
> URL: https://issues.apache.org/jira/browse/CASSANDRA-11988
> Project: Cassandra
>  Issue Type: Bug
>Reporter: Nimi Wariboko Jr.
>Assignee: Carl Yeksigian
> Fix For: 3.x
>
>
> I have a table that suddenly refuses to be read or compacted. Issuing a read 
> on the table causes a NPE.
> On compaction, it returns the error
> {code}
> ERROR [CompactionExecutor:6] 2016-06-09 17:10:15,724 CassandraDaemon.java:213 
> - Exception in thread Thread[CompactionExecutor:6,1,main]
> java.lang.NullPointerException: null
>   at 
> org.apache.cassandra.db.transform.UnfilteredRows.isEmpty(UnfilteredRows.java:38)
>  ~[apache-cassandra-3.6.jar:3.6]
>   at 
> org.apache.cassandra.db.partitions.PurgeFunction.applyToPartition(PurgeFunction.java:64)
>  ~[apache-cassandra-3.6.jar:3.6]
>   at 
> org.apache.cassandra.db.partitions.PurgeFunction.applyToPartition(PurgeFunction.java:24)
>  ~[apache-cassandra-3.6.jar:3.6]
>   at 
> org.apache.cassandra.db.transform.BasePartitions.hasNext(BasePartitions.java:76)
>  ~[apache-cassandra-3.6.jar:3.6]
>   at 
> org.apache.cassandra.db.compaction.CompactionIterator.hasNext(CompactionIterator.java:226)
>  ~[apache-cassandra-3.6.jar:3.6]
>   at 
> org.apache.cassandra.db.compaction.CompactionTask.runMayThrow(CompactionTask.java:182)
>  ~[apache-cassandra-3.6.jar:3.6]
>   at 
> org.apache.cassandra.utils.WrappedRunnable.run(WrappedRunnable.java:28) 
> ~[apache-cassandra-3.6.jar:3.6]
>   at 
> org.apache.cassandra.db.compaction.CompactionTask.executeInternal(CompactionTask.java:82)
>  ~[apache-cassandra-3.6.jar:3.6]
>   at 
> org.apache.cassandra.db.compaction.AbstractCompactionTask.execute(AbstractCompactionTask.java:60)
>  ~[apache-cassandra-3.6.jar:3.6]
>   at 
> org.apache.cassandra.db.compaction.CompactionManager$BackgroundCompactionCandidate.run(CompactionManager.java:264)
>  ~[apache-cassandra-3.6.jar:3.6]
>   at 
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) 
> ~[na:1.8.0_45]
>   at java.util.concurrent.FutureTask.run(FutureTask.java:266) 
> ~[na:1.8.0_45]
>   at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
>  ~[na:1.8.0_45]
>   at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
>  [na:1.8.0_45]
>   at java.lang.Thread.run(Thread.java:745) [na:1.8.0_45]
> {code}
> Schema:
> {code}
> CREATE TABLE cmpayments.report_payments (
> reportid timeuuid,
> userid timeuuid,
> adjustedearnings decimal,
> deleted set static,
> earnings map,
> gross map,
> organizationid text,
> payall timestamp static,
> status text,
> PRIMARY KEY (reportid, userid)
> ) WITH CLUSTERING ORDER BY (userid ASC)
> AND 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}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (CASSANDRA-9054) Break DatabaseDescriptor up into multiple classes.

[Joshua McKenzie (JIRA)]

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

Joshua McKenzie commented on CASSANDRA-9054:


bq. but that's an even more intrusive patch
Just wanted to point out: there's no reason we'd have to do all of that at 
once. We can (and should) take an incremental approach to changes like this 
instead of Big-Banging it.

> Break DatabaseDescriptor up into multiple classes.
> --
>
> Key: CASSANDRA-9054
> URL: https://issues.apache.org/jira/browse/CASSANDRA-9054
> Project: Cassandra
>  Issue Type: Improvement
>Reporter: Jeremiah Jordan
>Assignee: Robert Stupp
> Fix For: 3.x
>
>
> Right now to get at Config stuff you go through DatabaseDescriptor.  But when 
> you instantiate DatabaseDescriptor it actually opens system tables and such, 
> which triggers commit log replays, and other things if the right flags aren't 
> set ahead of time.  This makes getting at config stuff from tools annoying, 
> as you have to be very careful about instantiation orders.
> It would be nice if we could break DatabaseDescriptor up into multiple 
> classes, so that getting at config stuff from tools wasn't such a pain.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (CASSANDRA-12234) dtest failure in sstable_generation_loading_test.TestSSTableGenerationAndLoading.sstableloader_uppercase_keyspace_name_test

[Sean McCarthy (JIRA)]

Sean McCarthy created CASSANDRA-12234:
-

 Summary: dtest failure in 
sstable_generation_loading_test.TestSSTableGenerationAndLoading.sstableloader_uppercase_keyspace_name_test
 Key: CASSANDRA-12234
 URL: https://issues.apache.org/jira/browse/CASSANDRA-12234
 Project: Cassandra
  Issue Type: Test
Reporter: Sean McCarthy
Assignee: DS Test Eng
 Attachments: node1.log, node1_debug.log, node1_gc.log, node2.log, 
node2_debug.log, node2_gc.log

example failure:

http://cassci.datastax.com/job/trunk_novnode_dtest/430/testReport/sstable_generation_loading_test/TestSSTableGenerationAndLoading/sstableloader_uppercase_keyspace_name_test

Failed on CassCI build trunk_novnode_dtest #430

{code}
Stacktrace

  File "/usr/lib/python2.7/unittest/case.py", line 329, in run
testMethod()
  File "/home/automaton/cassandra-dtest/sstable_generation_loading_test.py", 
line 229, in sstableloader_uppercase_keyspace_name_test
self.load_sstable_with_configuration(ks='"Keyspace1"')
  File "/home/automaton/cassandra-dtest/sstable_generation_loading_test.py", 
line 187, in load_sstable_with_configuration
"sstableloader exited with a non-zero status: {}".format(exit_status))
  File "/usr/lib/python2.7/unittest/case.py", line 513, in assertEqual
assertion_func(first, second, msg=msg)
  File "/usr/lib/python2.7/unittest/case.py", line 506, in _baseAssertEqual
raise self.failureException(msg)
"sstableloader exited with a non-zero status: 1
{code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (CASSANDRA-12192) dtest failure in upgrade_tests.cql_tests.TestCQLNodes3RF3_Upgrade_current_3_0_x_To_head_trunk.map_keys_indexing_test

[Joshua McKenzie (JIRA)]

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

Joshua McKenzie updated CASSANDRA-12192:

Assignee: Sam Tunnicliffe

> dtest failure in 
> upgrade_tests.cql_tests.TestCQLNodes3RF3_Upgrade_current_3_0_x_To_head_trunk.map_keys_indexing_test
> 
>
> Key: CASSANDRA-12192
> URL: https://issues.apache.org/jira/browse/CASSANDRA-12192
> Project: Cassandra
>  Issue Type: Bug
>Reporter: Sean McCarthy
>Assignee: Sam Tunnicliffe
>  Labels: dtest
> Attachments: node1.log, node1_debug.log, node1_gc.log, node2.log, 
> node2_debug.log, node2_gc.log, node3.log, node3_debug.log, node3_gc.log
>
>
> example failure:
> http://cassci.datastax.com/job/upgrade_tests-all/59/testReport/upgrade_tests.cql_tests/TestCQLNodes3RF3_Upgrade_current_3_0_x_To_head_trunk/map_keys_indexing_test
> Failed on CassCI build upgrade_tests-all #59
> {code}
> Stacktrace
>   File "/usr/lib/python2.7/unittest/case.py", line 329, in run
> testMethod()
>   File "/home/automaton/cassandra-dtest/tools.py", line 290, in wrapped
> f(obj)
>   File "/home/automaton/cassandra-dtest/upgrade_tests/cql_tests.py", line 
> 3668, in map_keys_indexing_test
> cursor.execute("TRUNCATE test")
>   File "cassandra/cluster.py", line 1941, in 
> cassandra.cluster.Session.execute (cassandra/cluster.c:33642)
> return self.execute_async(query, parameters, trace, custom_payload, 
> timeout, execution_profile).result()
>   File "cassandra/cluster.py", line 3629, in 
> cassandra.cluster.ResponseFuture.result (cassandra/cluster.c:69369)
> raise self._final_exception
> '
> {code}
> Related failure: 
> http://cassci.datastax.com/job/upgrade_tests-all/59/testReport/upgrade_tests.cql_tests/TestCQLNodes2RF1_Upgrade_current_3_0_x_To_head_trunk/map_keys_indexing_test/



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (CASSANDRA-11902) dtest failure in hintedhandoff_test.TestHintedHandoffConfig.hintedhandoff_dc_reenabled_test

[Joshua McKenzie (JIRA)]

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

Joshua McKenzie updated CASSANDRA-11902:

Assignee: Aleksey Yeschenko

> dtest failure in 
> hintedhandoff_test.TestHintedHandoffConfig.hintedhandoff_dc_reenabled_test
> ---
>
> Key: CASSANDRA-11902
> URL: https://issues.apache.org/jira/browse/CASSANDRA-11902
> Project: Cassandra
>  Issue Type: Bug
>Reporter: Philip Thompson
>Assignee: Aleksey Yeschenko
>  Labels: dtest
> Fix For: 3.9
>
> Attachments: node1.log, node1_debug.log, node2.log, node2_debug.log
>
>
> Failure occurred on trunk here:
> http://cassci.datastax.com/job/trunk_dtest/1239/testReport/hintedhandoff_test/TestHintedHandoffConfig/hintedhandoff_dc_reenabled_test/
> Logs are attached
> We re-enable HH on a DC, but we aren't seeing hints move in the logs, so this 
> does worry me a bit. I'm not sure quite how flaky it is. It's only failed 
> once.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (CASSANDRA-12161) dtest failure in counter_tests.TestCounters.upgrade_test

[Joshua McKenzie (JIRA)]

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

Joshua McKenzie updated CASSANDRA-12161:

Assignee: Alex Petrov

> dtest failure in counter_tests.TestCounters.upgrade_test
> 
>
> Key: CASSANDRA-12161
> URL: https://issues.apache.org/jira/browse/CASSANDRA-12161
> Project: Cassandra
>  Issue Type: Bug
>Reporter: Sean McCarthy
>Assignee: Alex Petrov
>  Labels: dtest
> Attachments: node1.log, node2.log
>
>
> example failure:
> http://cassci.datastax.com/job/cassandra-2.1_dtest_jdk8/244/testReport/counter_tests/TestCounters/upgrade_test
> Failed on CassCI build cassandra-2.1_dtest_jdk8 #244
> {code}
> Standard Output
> Unexpected error in node2 log, error: 
> ERROR [Reference-Reaper:1] 2016-07-07 02:45:08,632 Ref.java:199 - LEAK 
> DETECTED: a reference 
> (org.apache.cassandra.utils.concurrent.Ref$State@25829106) to class 
> org.apache.cassandra.utils.concurrent.WrappedSharedCloseable$1@725969862:[Memory@[0..4),
>  Memory@[0..e)] was not released before the reference was garbage collected
> Unexpected error in node2 log, error: 
> ERROR [Reference-Reaper:1] 2016-07-07 02:45:08,633 Ref.java:199 - LEAK 
> DETECTED: a reference 
> (org.apache.cassandra.utils.concurrent.Ref$State@2f7afa76) to class 
> org.apache.cassandra.utils.concurrent.WrappedSharedCloseable$1@1786274301:[[OffHeapBitSet]]
>  was not released before the reference was garbage collected
> Unexpected error in node2 log, error: 
> ERROR [Reference-Reaper:1] 2016-07-07 02:45:08,634 Ref.java:199 - LEAK 
> DETECTED: a reference 
> (org.apache.cassandra.utils.concurrent.Ref$State@5b43d715) to class 
> org.apache.cassandra.io.sstable.SSTableReader$DescriptorTypeTidy@1540918496:/tmp/dtest-0jFLWr/test/node2/data0/system/schema_keyspaces-b0f2235744583cdb9631c43e59ce3676/system-schema_keyspaces-ka-1
>  was not released before the reference was garbage collected
> Unexpected error in node2 log, error: 
> ERROR [Reference-Reaper:1] 2016-07-07 02:45:08,634 Ref.java:199 - LEAK 
> DETECTED: a reference 
> (org.apache.cassandra.utils.concurrent.Ref$State@230964a7) to class 
> org.apache.cassandra.io.util.CompressedPoolingSegmentedFile$Cleanup@173514418:/tmp/dtest-0jFLWr/test/node2/data0/system/schema_keyspaces-b0f2235744583cdb9631c43e59ce3676/system-schema_keyspaces-ka-1-Data.db
>  was not released before the reference was garbage collected
> Unexpected error in node2 log, error: 
> ERROR [Reference-Reaper:1] 2016-07-07 02:45:08,634 Ref.java:199 - LEAK 
> DETECTED: a reference 
> (org.apache.cassandra.utils.concurrent.Ref$State@4f691b92) to class 
> org.apache.cassandra.io.util.MmappedSegmentedFile$Cleanup@1346973971:/tmp/dtest-0jFLWr/test/node2/data0/system/schema_keyspaces-b0f2235744583cdb9631c43e59ce3676/system-schema_keyspaces-ka-1-Index.db
>  was not released before the reference was garbage collected
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (CASSANDRA-12125) ERROR [MemtableFlushWriter:4] 2016-07-01 06:20:41,137 CassandraDaemon.java:185 - Exception in thread Thread[MemtableFlushWriter:4,5,main] java.lang.RuntimeException

[Joshua McKenzie (JIRA)]

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

Joshua McKenzie updated CASSANDRA-12125:

Status: Open  (was: Awaiting Feedback)

> ERROR [MemtableFlushWriter:4] 2016-07-01 06:20:41,137 
> CassandraDaemon.java:185 - Exception in thread 
> Thread[MemtableFlushWriter:4,5,main]  java.lang.RuntimeException: Last 
> written key DecoratedKey(.XX, X) >= current key DecoratedKey
> 
>
> Key: CASSANDRA-12125
> URL: https://issues.apache.org/jira/browse/CASSANDRA-12125
> Project: Cassandra
>  Issue Type: Bug
>  Components: Core
> Environment: RHEL-6.5 64-bit Apache Cassandra 2.2.5v
>Reporter: Relish Chackochan
> Fix For: 2.2.x
>
>
> We are running on RHEL-6.5 64-bit with Apache Cassandra 2.2.5v on 4 node 
> cluster and getting the following error on multiple node while running the 
> repair job and when getting the error repair job is hang.
> Can some one help to identify the issue.
> {code}
> ERROR [MemtableFlushWriter:4] 2016-07-01 06:20:41,137 
> CassandraDaemon.java:185 - Exception in thread 
> Thread[MemtableFlushWriter:4,5,main]
> java.lang.RuntimeException: Last written key DecoratedKey(1467371986.8870, 
> 313436373337313938362e38383730) >= current key DecoratedKey(, 
> 313436373337323030312e38383730) writing into 
> /opt/cassandra/data/proddb/log_data1-0a5092a0a4fa11e5872fc1ce0a46dc27/.maxdatetimeindex_idx/tmp-la-470-big-Data.db
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)