[jira] [Updated] (CASSANDRA-13809) Make BatchlogManagerMBean.forceBatchlogReplay() blocking

[Aleksey Yeschenko (JIRA)]

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

Aleksey Yeschenko updated CASSANDRA-13809:
--
Priority: Trivial  (was: Minor)

> Make BatchlogManagerMBean.forceBatchlogReplay() blocking
> 
>
> Key: CASSANDRA-13809
> URL: https://issues.apache.org/jira/browse/CASSANDRA-13809
> Project: Cassandra
>  Issue Type: Improvement
>  Components: Coordination
>Reporter: Aleksey Yeschenko
>Assignee: Aleksey Yeschenko
>Priority: Trivial
> Fix For: 2.2.11
>
>
> In 3.0, {{BatchlogManagerMBean.forceBatchlogReplay()}} blocks until 
> completion. In 2.2 it just submits a runnable and instaexits, which makes it 
> impossible to create non-flaky dtests that rely on batchlog replay.
> [here|https://github.com/iamaleksey/cassandra/commits/13809-2.2] is a small 
> 2.2-only commit that make the behaviour consistent between 2.2 and 3.0.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

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

[jira] [Updated] (CASSANDRA-13809) Make BatchlogManagerMBean.forceBatchlogReplay() blocking

[Aleksey Yeschenko (JIRA)]

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

Aleksey Yeschenko updated CASSANDRA-13809:
--
   Resolution: Fixed
Fix Version/s: (was: 2.2.x)
   2.2.11
   Status: Resolved  (was: Ready to Commit)

> Make BatchlogManagerMBean.forceBatchlogReplay() blocking
> 
>
> Key: CASSANDRA-13809
> URL: https://issues.apache.org/jira/browse/CASSANDRA-13809
> Project: Cassandra
>  Issue Type: Bug
>  Components: Coordination
>Reporter: Aleksey Yeschenko
>Assignee: Aleksey Yeschenko
>Priority: Minor
> Fix For: 2.2.11
>
>
> In 3.0, {{BatchlogManagerMBean.forceBatchlogReplay()}} blocks until 
> completion. In 2.2 it just submits a runnable and instaexits, which makes it 
> impossible to create non-flaky dtests that rely on batchlog replay.
> [here|https://github.com/iamaleksey/cassandra/commits/13809-2.2] is a small 
> 2.2-only commit that make the behaviour consistent between 2.2 and 3.0.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

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

[jira] [Commented] (CASSANDRA-13809) Make BatchlogManagerMBean.forceBatchlogReplay() blocking

[Aleksey Yeschenko (JIRA)]

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

Aleksey Yeschenko commented on CASSANDRA-13809:
---

Thanks. Committed as 
[c6dec2f0e02eb3ae9b9d070ec09cf822eda6bd2a|https://github.com/apache/cassandra/commit/c6dec2f0e02eb3ae9b9d070ec09cf822eda6bd2a]
 to 2.2. And the dtest too.

> Make BatchlogManagerMBean.forceBatchlogReplay() blocking
> 
>
> Key: CASSANDRA-13809
> URL: https://issues.apache.org/jira/browse/CASSANDRA-13809
> Project: Cassandra
>  Issue Type: Bug
>  Components: Coordination
>Reporter: Aleksey Yeschenko
>Assignee: Aleksey Yeschenko
>Priority: Minor
> Fix For: 2.2.11
>
>
> In 3.0, {{BatchlogManagerMBean.forceBatchlogReplay()}} blocks until 
> completion. In 2.2 it just submits a runnable and instaexits, which makes it 
> impossible to create non-flaky dtests that rely on batchlog replay.
> [here|https://github.com/iamaleksey/cassandra/commits/13809-2.2] is a small 
> 2.2-only commit that make the behaviour consistent between 2.2 and 3.0.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

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

[jira] [Updated] (CASSANDRA-13809) Make BatchlogManagerMBean.forceBatchlogReplay() blocking

[Aleksey Yeschenko (JIRA)]

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

Aleksey Yeschenko updated CASSANDRA-13809:
--
Issue Type: Improvement  (was: Bug)

> Make BatchlogManagerMBean.forceBatchlogReplay() blocking
> 
>
> Key: CASSANDRA-13809
> URL: https://issues.apache.org/jira/browse/CASSANDRA-13809
> Project: Cassandra
>  Issue Type: Improvement
>  Components: Coordination
>Reporter: Aleksey Yeschenko
>Assignee: Aleksey Yeschenko
>Priority: Minor
> Fix For: 2.2.11
>
>
> In 3.0, {{BatchlogManagerMBean.forceBatchlogReplay()}} blocks until 
> completion. In 2.2 it just submits a runnable and instaexits, which makes it 
> impossible to create non-flaky dtests that rely on batchlog replay.
> [here|https://github.com/iamaleksey/cassandra/commits/13809-2.2] is a small 
> 2.2-only commit that make the behaviour consistent between 2.2 and 3.0.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

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

cassandra-dtest git commit: Add tests for mixed version batchlog replay

[aleksey]

Repository: cassandra-dtest
Updated Branches:
  refs/heads/master 6d5ee3792 -> ac9c95607


Add tests for mixed version batchlog replay

Patch by Jeff Jirsa; reviewed by Aleksey Yeschenko


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

Branch: refs/heads/master
Commit: ac9c95607ce439de596da41c368d79c67d6dcdda
Parents: 6d5ee37
Author: Jeff Jirsa 
Authored: Mon Aug 14 12:55:17 2017 -0700
Committer: Aleksey Yeschenko 
Committed: Sat Aug 26 01:21:00 2017 +0100

--
 batch_test.py | 96 +++---
 byteman/fail_after_batchlog_write.btm | 19 ++
 2 files changed, 94 insertions(+), 21 deletions(-)
--


http://git-wip-us.apache.org/repos/asf/cassandra-dtest/blob/ac9c9560/batch_test.py
--
diff --git a/batch_test.py b/batch_test.py
index 4194f10..5c25c46 100644
--- a/batch_test.py
+++ b/batch_test.py
@@ -1,6 +1,7 @@
 import sys
 import time
 from unittest import skipIf
+from nose.tools import assert_greater_equal
 
 from cassandra import ConsistencyLevel, Timeout, Unavailable
 from cassandra.query import SimpleStatement
@@ -9,6 +10,8 @@ from dtest import Tester, create_ks, debug
 from tools.assertions import (assert_all, assert_invalid, assert_one,
   assert_unavailable)
 from tools.decorators import since
+from tools.jmxutils import (JolokiaAgent, make_mbean,
+remove_perf_disable_shared_mem)
 
 
 class TestBatch(Tester):
@@ -295,6 +298,15 @@ class TestBatch(Tester):
 self._logged_batch_compatibility_test(0, 1, 
'github:apache/cassandra-2.2', 2, 4)
 
 @since('3.0', max_version='3.x')
+def batchlog_replay_compatibility_1_test(self):
+"""
+@jira_ticket CASSANDRA-9673, test that logged batches still work with 
a mixed version cluster.
+
+Here we have one 3.0/3.x node and two 2.2 nodes and we send the batch 
request to the 3.0 node.
+"""
+self._batchlog_replay_compatibility_test(0, 1, 
'github:apache/cassandra-2.2', 2, 4)
+
+@since('3.0', max_version='3.x')
 @skipIf(sys.platform == 'win32', 'Windows production support only on 2.2+')
 def logged_batch_compatibility_2_test(self):
 """
@@ -324,6 +336,15 @@ class TestBatch(Tester):
 self._logged_batch_compatibility_test(2, 2, 
'github:apache/cassandra-2.2', 1, 4)
 
 @since('3.0', max_version='3.x')
+def batchlog_replay_compatibility_4_test(self):
+"""
+@jira_ticket CASSANDRA-9673, test that logged batches still work with 
a mixed version cluster.
+
+Here we have two 3.0/3.x nodes and one 2.2 node and we send the batch 
request to the 2.2 node.
+"""
+self._batchlog_replay_compatibility_test(2, 2, 
'github:apache/cassandra-2.2', 1, 4)
+
+@since('3.0', max_version='3.x')
 @skipIf(sys.platform == 'win32', 'Windows production support only on 2.2+')
 def logged_batch_compatibility_5_test(self):
 """
@@ -346,6 +367,43 @@ class TestBatch(Tester):
 res = sorted(rows)
 self.assertEquals([[0, 'Jack', 'Sparrow'], [1, 'Will', 'Turner']], 
[list(res[0]), list(res[1])])
 
+def _batchlog_replay_compatibility_test(self, coordinator_idx, 
current_nodes, previous_version, previous_nodes, protocol_version):
+session = self.prepare_mixed(coordinator_idx, current_nodes, 
previous_version, previous_nodes,
+ protocol_version=protocol_version, 
install_byteman=True)
+
+coordinator = self.cluster.nodelist()[coordinator_idx]
+coordinator.byteman_submit(['./byteman/fail_after_batchlog_write.btm'])
+debug("Injected byteman scripts to enable batchlog replay 
{}".format(coordinator.name))
+
+query = """
+BEGIN BATCH
+INSERT INTO users (id, firstname, lastname) VALUES (0, 'Jack', 
'Sparrow')
+INSERT INTO users (id, firstname, lastname) VALUES (1, 'Will', 
'Turner')
+APPLY BATCH
+"""
+session.execute(query)
+
+total_batches_replayed = 0
+blm = make_mbean('db', type='BatchlogManager')
+
+for n in self.cluster.nodelist():
+if n == coordinator:
+continue
+
+with JolokiaAgent(n) as jmx:
+debug('Forcing batchlog replay for {}'.format(n.name))
+jmx.execute_method(blm, 'forceBatchlogReplay')
+batches_replayed = jmx.read_attribute(blm, 
'TotalBatchesReplayed')
+debug('{} batches replayed on node 

[01/10] cassandra git commit: Make BatchlogManagerMBean.forceBatchlogReplay() blocking

[aleksey]

Repository: cassandra
Updated Branches:
  refs/heads/cassandra-2.2 e1aa7d32c -> c6dec2f0e
  refs/heads/cassandra-3.0 cf0b6d107 -> 95f1b23bf
  refs/heads/cassandra-3.11 6b7d73a49 -> 26fedcd0b
  refs/heads/trunk 6bea7de50 -> 7bea74b76


Make BatchlogManagerMBean.forceBatchlogReplay() blocking

patch by Aleksey Yeschenko; reviewed by Jeff Jirsa for CASSANDRA-13809


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

Branch: refs/heads/cassandra-2.2
Commit: c6dec2f0e02eb3ae9b9d070ec09cf822eda6bd2a
Parents: e1aa7d3
Author: Aleksey Yeschenko 
Authored: Fri Aug 25 17:30:49 2017 +0100
Committer: Aleksey Yeschenko 
Committed: Fri Aug 25 17:35:53 2017 +0100

--
 CHANGES.txt| 1 +
 src/java/org/apache/cassandra/db/BatchlogManager.java  | 4 ++--
 src/java/org/apache/cassandra/db/BatchlogManagerMBean.java | 4 ++--
 3 files changed, 5 insertions(+), 4 deletions(-)
--


http://git-wip-us.apache.org/repos/asf/cassandra/blob/c6dec2f0/CHANGES.txt
--
diff --git a/CHANGES.txt b/CHANGES.txt
index 2fbb7e9..4e68ddc 100644
--- a/CHANGES.txt
+++ b/CHANGES.txt
@@ -1,4 +1,5 @@
 2.2.11
+ * Make BatchlogManagerMBean.forceBatchlogReplay() blocking (CASSANDRA-13809)
  * Uncaught exceptions in Netty pipeline (CASSANDRA-13649)
  * Prevent integer overflow on exabyte filesystems (CASSANDRA-13067) 
  * Fix queries with LIMIT and filtering on clustering columns (CASSANDRA-11223)

http://git-wip-us.apache.org/repos/asf/cassandra/blob/c6dec2f0/src/java/org/apache/cassandra/db/BatchlogManager.java
--
diff --git a/src/java/org/apache/cassandra/db/BatchlogManager.java 
b/src/java/org/apache/cassandra/db/BatchlogManager.java
index ba56f0d..9a2d1f6 100644
--- a/src/java/org/apache/cassandra/db/BatchlogManager.java
+++ b/src/java/org/apache/cassandra/db/BatchlogManager.java
@@ -112,9 +112,9 @@ public class BatchlogManager implements BatchlogManagerMBean
 return totalBatchesReplayed.longValue();
 }
 
-public void forceBatchlogReplay()
+public void forceBatchlogReplay() throws Exception
 {
-startBatchlogReplay();
+startBatchlogReplay().get();
 }
 
 public Future startBatchlogReplay()

http://git-wip-us.apache.org/repos/asf/cassandra/blob/c6dec2f0/src/java/org/apache/cassandra/db/BatchlogManagerMBean.java
--
diff --git a/src/java/org/apache/cassandra/db/BatchlogManagerMBean.java 
b/src/java/org/apache/cassandra/db/BatchlogManagerMBean.java
index 2e60ba4..5ddf232 100644
--- a/src/java/org/apache/cassandra/db/BatchlogManagerMBean.java
+++ b/src/java/org/apache/cassandra/db/BatchlogManagerMBean.java
@@ -32,7 +32,7 @@ public interface BatchlogManagerMBean
 public long getTotalBatchesReplayed();
 
 /**
- * Forces batchlog replay. Returns immediately if replay is already in 
progress.
+ * Forces batchlog replay. Blocks until completion.
  */
-public void forceBatchlogReplay();
+public void forceBatchlogReplay() throws Exception;
 }


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

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

[aleksey]

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

Branch: refs/heads/cassandra-3.0
Commit: 95f1b23bf0405ffdee1d4372980b0106d0c83071
Parents: cf0b6d1 c6dec2f
Author: Aleksey Yeschenko 
Authored: Sat Aug 26 01:25:39 2017 +0100
Committer: Aleksey Yeschenko 
Committed: Sat Aug 26 01:25:39 2017 +0100

--
 src/java/org/apache/cassandra/batchlog/BatchlogManagerMBean.java | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
--


http://git-wip-us.apache.org/repos/asf/cassandra/blob/95f1b23b/src/java/org/apache/cassandra/batchlog/BatchlogManagerMBean.java
--
diff --cc src/java/org/apache/cassandra/batchlog/BatchlogManagerMBean.java
index 4dcc9f2,000..371b6a8
mode 100644,00..100644
--- a/src/java/org/apache/cassandra/batchlog/BatchlogManagerMBean.java
+++ b/src/java/org/apache/cassandra/batchlog/BatchlogManagerMBean.java
@@@ -1,38 -1,0 +1,38 @@@
 +/*
 + * Licensed to the Apache Software Foundation (ASF) under one
 + * or more contributor license agreements.  See the NOTICE file
 + * distributed with this work for additional information
 + * regarding copyright ownership.  The ASF licenses this file
 + * to you under the Apache License, Version 2.0 (the
 + * "License"); you may not use this file except in compliance
 + * with the License.  You may obtain a copy of the License at
 + *
 + * http://www.apache.org/licenses/LICENSE-2.0
 + *
 + * Unless required by applicable law or agreed to in writing, software
 + * distributed under the License is distributed on an "AS IS" BASIS,
 + * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
 + * See the License for the specific language governing permissions and
 + * limitations under the License.
 + */
 +package org.apache.cassandra.batchlog;
 +
 +public interface BatchlogManagerMBean
 +{
 +/**
 + * Counts all batches currently in the batchlog.
 + *
 + * @return total batch count
 + */
 +public int countAllBatches();
 +
 +/**
 + * @return total count of batches replayed since node start
 + */
 +public long getTotalBatchesReplayed();
 +
 +/**
-  * Forces batchlog replay. Returns immediately if replay is already in 
progress.
++ * Forces batchlog replay. Blocks until completion.
 + */
 +public void forceBatchlogReplay() throws Exception;
 +}


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

[04/10] cassandra git commit: Make BatchlogManagerMBean.forceBatchlogReplay() blocking

[aleksey]

Make BatchlogManagerMBean.forceBatchlogReplay() blocking

patch by Aleksey Yeschenko; reviewed by Jeff Jirsa for CASSANDRA-13809


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

Branch: refs/heads/trunk
Commit: c6dec2f0e02eb3ae9b9d070ec09cf822eda6bd2a
Parents: e1aa7d3
Author: Aleksey Yeschenko 
Authored: Fri Aug 25 17:30:49 2017 +0100
Committer: Aleksey Yeschenko 
Committed: Fri Aug 25 17:35:53 2017 +0100

--
 CHANGES.txt| 1 +
 src/java/org/apache/cassandra/db/BatchlogManager.java  | 4 ++--
 src/java/org/apache/cassandra/db/BatchlogManagerMBean.java | 4 ++--
 3 files changed, 5 insertions(+), 4 deletions(-)
--


http://git-wip-us.apache.org/repos/asf/cassandra/blob/c6dec2f0/CHANGES.txt
--
diff --git a/CHANGES.txt b/CHANGES.txt
index 2fbb7e9..4e68ddc 100644
--- a/CHANGES.txt
+++ b/CHANGES.txt
@@ -1,4 +1,5 @@
 2.2.11
+ * Make BatchlogManagerMBean.forceBatchlogReplay() blocking (CASSANDRA-13809)
  * Uncaught exceptions in Netty pipeline (CASSANDRA-13649)
  * Prevent integer overflow on exabyte filesystems (CASSANDRA-13067) 
  * Fix queries with LIMIT and filtering on clustering columns (CASSANDRA-11223)

http://git-wip-us.apache.org/repos/asf/cassandra/blob/c6dec2f0/src/java/org/apache/cassandra/db/BatchlogManager.java
--
diff --git a/src/java/org/apache/cassandra/db/BatchlogManager.java 
b/src/java/org/apache/cassandra/db/BatchlogManager.java
index ba56f0d..9a2d1f6 100644
--- a/src/java/org/apache/cassandra/db/BatchlogManager.java
+++ b/src/java/org/apache/cassandra/db/BatchlogManager.java
@@ -112,9 +112,9 @@ public class BatchlogManager implements BatchlogManagerMBean
 return totalBatchesReplayed.longValue();
 }
 
-public void forceBatchlogReplay()
+public void forceBatchlogReplay() throws Exception
 {
-startBatchlogReplay();
+startBatchlogReplay().get();
 }
 
 public Future startBatchlogReplay()

http://git-wip-us.apache.org/repos/asf/cassandra/blob/c6dec2f0/src/java/org/apache/cassandra/db/BatchlogManagerMBean.java
--
diff --git a/src/java/org/apache/cassandra/db/BatchlogManagerMBean.java 
b/src/java/org/apache/cassandra/db/BatchlogManagerMBean.java
index 2e60ba4..5ddf232 100644
--- a/src/java/org/apache/cassandra/db/BatchlogManagerMBean.java
+++ b/src/java/org/apache/cassandra/db/BatchlogManagerMBean.java
@@ -32,7 +32,7 @@ public interface BatchlogManagerMBean
 public long getTotalBatchesReplayed();
 
 /**
- * Forces batchlog replay. Returns immediately if replay is already in 
progress.
+ * Forces batchlog replay. Blocks until completion.
  */
-public void forceBatchlogReplay();
+public void forceBatchlogReplay() throws Exception;
 }


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

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

[aleksey]

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

Branch: refs/heads/trunk
Commit: 95f1b23bf0405ffdee1d4372980b0106d0c83071
Parents: cf0b6d1 c6dec2f
Author: Aleksey Yeschenko 
Authored: Sat Aug 26 01:25:39 2017 +0100
Committer: Aleksey Yeschenko 
Committed: Sat Aug 26 01:25:39 2017 +0100

--
 src/java/org/apache/cassandra/batchlog/BatchlogManagerMBean.java | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
--


http://git-wip-us.apache.org/repos/asf/cassandra/blob/95f1b23b/src/java/org/apache/cassandra/batchlog/BatchlogManagerMBean.java
--
diff --cc src/java/org/apache/cassandra/batchlog/BatchlogManagerMBean.java
index 4dcc9f2,000..371b6a8
mode 100644,00..100644
--- a/src/java/org/apache/cassandra/batchlog/BatchlogManagerMBean.java
+++ b/src/java/org/apache/cassandra/batchlog/BatchlogManagerMBean.java
@@@ -1,38 -1,0 +1,38 @@@
 +/*
 + * Licensed to the Apache Software Foundation (ASF) under one
 + * or more contributor license agreements.  See the NOTICE file
 + * distributed with this work for additional information
 + * regarding copyright ownership.  The ASF licenses this file
 + * to you under the Apache License, Version 2.0 (the
 + * "License"); you may not use this file except in compliance
 + * with the License.  You may obtain a copy of the License at
 + *
 + * http://www.apache.org/licenses/LICENSE-2.0
 + *
 + * Unless required by applicable law or agreed to in writing, software
 + * distributed under the License is distributed on an "AS IS" BASIS,
 + * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
 + * See the License for the specific language governing permissions and
 + * limitations under the License.
 + */
 +package org.apache.cassandra.batchlog;
 +
 +public interface BatchlogManagerMBean
 +{
 +/**
 + * Counts all batches currently in the batchlog.
 + *
 + * @return total batch count
 + */
 +public int countAllBatches();
 +
 +/**
 + * @return total count of batches replayed since node start
 + */
 +public long getTotalBatchesReplayed();
 +
 +/**
-  * Forces batchlog replay. Returns immediately if replay is already in 
progress.
++ * Forces batchlog replay. Blocks until completion.
 + */
 +public void forceBatchlogReplay() throws Exception;
 +}


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

[02/10] cassandra git commit: Make BatchlogManagerMBean.forceBatchlogReplay() blocking

[aleksey]

Make BatchlogManagerMBean.forceBatchlogReplay() blocking

patch by Aleksey Yeschenko; reviewed by Jeff Jirsa for CASSANDRA-13809


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

Branch: refs/heads/cassandra-3.0
Commit: c6dec2f0e02eb3ae9b9d070ec09cf822eda6bd2a
Parents: e1aa7d3
Author: Aleksey Yeschenko 
Authored: Fri Aug 25 17:30:49 2017 +0100
Committer: Aleksey Yeschenko 
Committed: Fri Aug 25 17:35:53 2017 +0100

--
 CHANGES.txt| 1 +
 src/java/org/apache/cassandra/db/BatchlogManager.java  | 4 ++--
 src/java/org/apache/cassandra/db/BatchlogManagerMBean.java | 4 ++--
 3 files changed, 5 insertions(+), 4 deletions(-)
--


http://git-wip-us.apache.org/repos/asf/cassandra/blob/c6dec2f0/CHANGES.txt
--
diff --git a/CHANGES.txt b/CHANGES.txt
index 2fbb7e9..4e68ddc 100644
--- a/CHANGES.txt
+++ b/CHANGES.txt
@@ -1,4 +1,5 @@
 2.2.11
+ * Make BatchlogManagerMBean.forceBatchlogReplay() blocking (CASSANDRA-13809)
  * Uncaught exceptions in Netty pipeline (CASSANDRA-13649)
  * Prevent integer overflow on exabyte filesystems (CASSANDRA-13067) 
  * Fix queries with LIMIT and filtering on clustering columns (CASSANDRA-11223)

http://git-wip-us.apache.org/repos/asf/cassandra/blob/c6dec2f0/src/java/org/apache/cassandra/db/BatchlogManager.java
--
diff --git a/src/java/org/apache/cassandra/db/BatchlogManager.java 
b/src/java/org/apache/cassandra/db/BatchlogManager.java
index ba56f0d..9a2d1f6 100644
--- a/src/java/org/apache/cassandra/db/BatchlogManager.java
+++ b/src/java/org/apache/cassandra/db/BatchlogManager.java
@@ -112,9 +112,9 @@ public class BatchlogManager implements BatchlogManagerMBean
 return totalBatchesReplayed.longValue();
 }
 
-public void forceBatchlogReplay()
+public void forceBatchlogReplay() throws Exception
 {
-startBatchlogReplay();
+startBatchlogReplay().get();
 }
 
 public Future startBatchlogReplay()

http://git-wip-us.apache.org/repos/asf/cassandra/blob/c6dec2f0/src/java/org/apache/cassandra/db/BatchlogManagerMBean.java
--
diff --git a/src/java/org/apache/cassandra/db/BatchlogManagerMBean.java 
b/src/java/org/apache/cassandra/db/BatchlogManagerMBean.java
index 2e60ba4..5ddf232 100644
--- a/src/java/org/apache/cassandra/db/BatchlogManagerMBean.java
+++ b/src/java/org/apache/cassandra/db/BatchlogManagerMBean.java
@@ -32,7 +32,7 @@ public interface BatchlogManagerMBean
 public long getTotalBatchesReplayed();
 
 /**
- * Forces batchlog replay. Returns immediately if replay is already in 
progress.
+ * Forces batchlog replay. Blocks until completion.
  */
-public void forceBatchlogReplay();
+public void forceBatchlogReplay() throws Exception;
 }


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

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

[aleksey]

Merge branch 'cassandra-3.0' into cassandra-3.11


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

Branch: refs/heads/cassandra-3.11
Commit: 26fedcd0bb181b3e3b54fd90d663fb06a256b46a
Parents: 6b7d73a 95f1b23
Author: Aleksey Yeschenko 
Authored: Sat Aug 26 01:25:54 2017 +0100
Committer: Aleksey Yeschenko 
Committed: Sat Aug 26 01:25:54 2017 +0100

--
 src/java/org/apache/cassandra/batchlog/BatchlogManagerMBean.java | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
--



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

[03/10] cassandra git commit: Make BatchlogManagerMBean.forceBatchlogReplay() blocking

[aleksey]

Make BatchlogManagerMBean.forceBatchlogReplay() blocking

patch by Aleksey Yeschenko; reviewed by Jeff Jirsa for CASSANDRA-13809


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

Branch: refs/heads/cassandra-3.11
Commit: c6dec2f0e02eb3ae9b9d070ec09cf822eda6bd2a
Parents: e1aa7d3
Author: Aleksey Yeschenko 
Authored: Fri Aug 25 17:30:49 2017 +0100
Committer: Aleksey Yeschenko 
Committed: Fri Aug 25 17:35:53 2017 +0100

--
 CHANGES.txt| 1 +
 src/java/org/apache/cassandra/db/BatchlogManager.java  | 4 ++--
 src/java/org/apache/cassandra/db/BatchlogManagerMBean.java | 4 ++--
 3 files changed, 5 insertions(+), 4 deletions(-)
--


http://git-wip-us.apache.org/repos/asf/cassandra/blob/c6dec2f0/CHANGES.txt
--
diff --git a/CHANGES.txt b/CHANGES.txt
index 2fbb7e9..4e68ddc 100644
--- a/CHANGES.txt
+++ b/CHANGES.txt
@@ -1,4 +1,5 @@
 2.2.11
+ * Make BatchlogManagerMBean.forceBatchlogReplay() blocking (CASSANDRA-13809)
  * Uncaught exceptions in Netty pipeline (CASSANDRA-13649)
  * Prevent integer overflow on exabyte filesystems (CASSANDRA-13067) 
  * Fix queries with LIMIT and filtering on clustering columns (CASSANDRA-11223)

http://git-wip-us.apache.org/repos/asf/cassandra/blob/c6dec2f0/src/java/org/apache/cassandra/db/BatchlogManager.java
--
diff --git a/src/java/org/apache/cassandra/db/BatchlogManager.java 
b/src/java/org/apache/cassandra/db/BatchlogManager.java
index ba56f0d..9a2d1f6 100644
--- a/src/java/org/apache/cassandra/db/BatchlogManager.java
+++ b/src/java/org/apache/cassandra/db/BatchlogManager.java
@@ -112,9 +112,9 @@ public class BatchlogManager implements BatchlogManagerMBean
 return totalBatchesReplayed.longValue();
 }
 
-public void forceBatchlogReplay()
+public void forceBatchlogReplay() throws Exception
 {
-startBatchlogReplay();
+startBatchlogReplay().get();
 }
 
 public Future startBatchlogReplay()

http://git-wip-us.apache.org/repos/asf/cassandra/blob/c6dec2f0/src/java/org/apache/cassandra/db/BatchlogManagerMBean.java
--
diff --git a/src/java/org/apache/cassandra/db/BatchlogManagerMBean.java 
b/src/java/org/apache/cassandra/db/BatchlogManagerMBean.java
index 2e60ba4..5ddf232 100644
--- a/src/java/org/apache/cassandra/db/BatchlogManagerMBean.java
+++ b/src/java/org/apache/cassandra/db/BatchlogManagerMBean.java
@@ -32,7 +32,7 @@ public interface BatchlogManagerMBean
 public long getTotalBatchesReplayed();
 
 /**
- * Forces batchlog replay. Returns immediately if replay is already in 
progress.
+ * Forces batchlog replay. Blocks until completion.
  */
-public void forceBatchlogReplay();
+public void forceBatchlogReplay() throws Exception;
 }


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

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

[aleksey]

Merge branch 'cassandra-3.0' into cassandra-3.11


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

Branch: refs/heads/trunk
Commit: 26fedcd0bb181b3e3b54fd90d663fb06a256b46a
Parents: 6b7d73a 95f1b23
Author: Aleksey Yeschenko 
Authored: Sat Aug 26 01:25:54 2017 +0100
Committer: Aleksey Yeschenko 
Committed: Sat Aug 26 01:25:54 2017 +0100

--
 src/java/org/apache/cassandra/batchlog/BatchlogManagerMBean.java | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
--



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

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

[aleksey]

Merge branch 'cassandra-3.11' into trunk


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

Branch: refs/heads/trunk
Commit: 7bea74b76b61e8baacd36b7bc315b7c0eba2e204
Parents: 6bea7de 26fedcd
Author: Aleksey Yeschenko 
Authored: Sat Aug 26 01:26:04 2017 +0100
Committer: Aleksey Yeschenko 
Committed: Sat Aug 26 01:26:04 2017 +0100

--
 src/java/org/apache/cassandra/batchlog/BatchlogManagerMBean.java | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
--



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

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

[aleksey]

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

Branch: refs/heads/cassandra-3.11
Commit: 95f1b23bf0405ffdee1d4372980b0106d0c83071
Parents: cf0b6d1 c6dec2f
Author: Aleksey Yeschenko 
Authored: Sat Aug 26 01:25:39 2017 +0100
Committer: Aleksey Yeschenko 
Committed: Sat Aug 26 01:25:39 2017 +0100

--
 src/java/org/apache/cassandra/batchlog/BatchlogManagerMBean.java | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
--


http://git-wip-us.apache.org/repos/asf/cassandra/blob/95f1b23b/src/java/org/apache/cassandra/batchlog/BatchlogManagerMBean.java
--
diff --cc src/java/org/apache/cassandra/batchlog/BatchlogManagerMBean.java
index 4dcc9f2,000..371b6a8
mode 100644,00..100644
--- a/src/java/org/apache/cassandra/batchlog/BatchlogManagerMBean.java
+++ b/src/java/org/apache/cassandra/batchlog/BatchlogManagerMBean.java
@@@ -1,38 -1,0 +1,38 @@@
 +/*
 + * Licensed to the Apache Software Foundation (ASF) under one
 + * or more contributor license agreements.  See the NOTICE file
 + * distributed with this work for additional information
 + * regarding copyright ownership.  The ASF licenses this file
 + * to you under the Apache License, Version 2.0 (the
 + * "License"); you may not use this file except in compliance
 + * with the License.  You may obtain a copy of the License at
 + *
 + * http://www.apache.org/licenses/LICENSE-2.0
 + *
 + * Unless required by applicable law or agreed to in writing, software
 + * distributed under the License is distributed on an "AS IS" BASIS,
 + * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
 + * See the License for the specific language governing permissions and
 + * limitations under the License.
 + */
 +package org.apache.cassandra.batchlog;
 +
 +public interface BatchlogManagerMBean
 +{
 +/**
 + * Counts all batches currently in the batchlog.
 + *
 + * @return total batch count
 + */
 +public int countAllBatches();
 +
 +/**
 + * @return total count of batches replayed since node start
 + */
 +public long getTotalBatchesReplayed();
 +
 +/**
-  * Forces batchlog replay. Returns immediately if replay is already in 
progress.
++ * Forces batchlog replay. Blocks until completion.
 + */
 +public void forceBatchlogReplay() throws Exception;
 +}


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

[jira] [Updated] (CASSANDRA-13809) Make BatchlogManagerMBean.forceBatchlogReplay() blocking

[Jeff Jirsa (JIRA)]

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

Jeff Jirsa updated CASSANDRA-13809:
---
Status: Ready to Commit  (was: Patch Available)

> Make BatchlogManagerMBean.forceBatchlogReplay() blocking
> 
>
> Key: CASSANDRA-13809
> URL: https://issues.apache.org/jira/browse/CASSANDRA-13809
> Project: Cassandra
>  Issue Type: Bug
>  Components: Coordination
>Reporter: Aleksey Yeschenko
>Assignee: Aleksey Yeschenko
>Priority: Minor
> Fix For: 2.2.x
>
>
> In 3.0, {{BatchlogManagerMBean.forceBatchlogReplay()}} blocks until 
> completion. In 2.2 it just submits a runnable and instaexits, which makes it 
> impossible to create non-flaky dtests that rely on batchlog replay.
> [here|https://github.com/iamaleksey/cassandra/commits/13809-2.2] is a small 
> 2.2-only commit that make the behaviour consistent between 2.2 and 3.0.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

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

[jira] [Commented] (CASSANDRA-13809) Make BatchlogManagerMBean.forceBatchlogReplay() blocking

[Jeff Jirsa (JIRA)]

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

Jeff Jirsa commented on CASSANDRA-13809:


+1



> Make BatchlogManagerMBean.forceBatchlogReplay() blocking
> 
>
> Key: CASSANDRA-13809
> URL: https://issues.apache.org/jira/browse/CASSANDRA-13809
> Project: Cassandra
>  Issue Type: Bug
>  Components: Coordination
>Reporter: Aleksey Yeschenko
>Assignee: Aleksey Yeschenko
>Priority: Minor
> Fix For: 2.2.x
>
>
> In 3.0, {{BatchlogManagerMBean.forceBatchlogReplay()}} blocks until 
> completion. In 2.2 it just submits a runnable and instaexits, which makes it 
> impossible to create non-flaky dtests that rely on batchlog replay.
> [here|https://github.com/iamaleksey/cassandra/commits/13809-2.2] is a small 
> 2.2-only commit that make the behaviour consistent between 2.2 and 3.0.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

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

[jira] [Issue Comment Deleted] (CASSANDRA-13809) Make BatchlogManagerMBean.forceBatchlogReplay() blocking

[Patrick McFadin (JIRA)]

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

Patrick McFadin updated CASSANDRA-13809:

Comment: was deleted

(was: Placeholder reply to [~iamaleksey])

> Make BatchlogManagerMBean.forceBatchlogReplay() blocking
> 
>
> Key: CASSANDRA-13809
> URL: https://issues.apache.org/jira/browse/CASSANDRA-13809
> Project: Cassandra
>  Issue Type: Bug
>  Components: Coordination
>Reporter: Aleksey Yeschenko
>Assignee: Aleksey Yeschenko
>Priority: Minor
> Fix For: 2.2.x
>
>
> In 3.0, {{BatchlogManagerMBean.forceBatchlogReplay()}} blocks until 
> completion. In 2.2 it just submits a runnable and instaexits, which makes it 
> impossible to create non-flaky dtests that rely on batchlog replay.
> [here|https://github.com/iamaleksey/cassandra/commits/13809-2.2] is a small 
> 2.2-only commit that make the behaviour consistent between 2.2 and 3.0.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

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

[jira] [Commented] (CASSANDRA-13809) Make BatchlogManagerMBean.forceBatchlogReplay() blocking

[Aleksey Yeschenko (JIRA)]

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

Aleksey Yeschenko commented on CASSANDRA-13809:
---

Dtests in question [here|https://github.com/apache/cassandra-dtest/pull/7].

> Make BatchlogManagerMBean.forceBatchlogReplay() blocking
> 
>
> Key: CASSANDRA-13809
> URL: https://issues.apache.org/jira/browse/CASSANDRA-13809
> Project: Cassandra
>  Issue Type: Bug
>  Components: Coordination
>Reporter: Aleksey Yeschenko
>Assignee: Aleksey Yeschenko
>Priority: Minor
> Fix For: 2.2.x
>
>
> In 3.0, {{BatchlogManagerMBean.forceBatchlogReplay()}} blocks until 
> completion. In 2.2 it just submits a runnable and instaexits, which makes it 
> impossible to create non-flaky dtests that rely on batchlog replay.
> [here|https://github.com/iamaleksey/cassandra/commits/13809-2.2] is a small 
> 2.2-only commit that make the behaviour consistent between 2.2 and 3.0.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

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

[jira] [Commented] (CASSANDRA-13809) Make BatchlogManagerMBean.forceBatchlogReplay() blocking

[Patrick McFadin (JIRA)]

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

Patrick McFadin commented on CASSANDRA-13809:
-

Placeholder reply to [~iamaleksey]

> Make BatchlogManagerMBean.forceBatchlogReplay() blocking
> 
>
> Key: CASSANDRA-13809
> URL: https://issues.apache.org/jira/browse/CASSANDRA-13809
> Project: Cassandra
>  Issue Type: Bug
>  Components: Coordination
>Reporter: Aleksey Yeschenko
>Assignee: Aleksey Yeschenko
>Priority: Minor
> Fix For: 2.2.x
>
>
> In 3.0, {{BatchlogManagerMBean.forceBatchlogReplay()}} blocks until 
> completion. In 2.2 it just submits a runnable and instaexits, which makes it 
> impossible to create non-flaky dtests that rely on batchlog replay.
> [here|https://github.com/iamaleksey/cassandra/commits/13809-2.2] is a small 
> 2.2-only commit that make the behaviour consistent between 2.2 and 3.0.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

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

[jira] [Issue Comment Deleted] (CASSANDRA-13809) Make BatchlogManagerMBean.forceBatchlogReplay() blocking

[Aleksey Yeschenko (JIRA)]

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

Aleksey Yeschenko updated CASSANDRA-13809:
--
Comment: was deleted

(was: You guys need to get a life or something.)

> Make BatchlogManagerMBean.forceBatchlogReplay() blocking
> 
>
> Key: CASSANDRA-13809
> URL: https://issues.apache.org/jira/browse/CASSANDRA-13809
> Project: Cassandra
>  Issue Type: Bug
>  Components: Coordination
>Reporter: Aleksey Yeschenko
>Assignee: Aleksey Yeschenko
>Priority: Minor
> Fix For: 2.2.x
>
>
> In 3.0, {{BatchlogManagerMBean.forceBatchlogReplay()}} blocks until 
> completion. In 2.2 it just submits a runnable and instaexits, which makes it 
> impossible to create non-flaky dtests that rely on batchlog replay.
> [here|https://github.com/iamaleksey/cassandra/commits/13809-2.2] is a small 
> 2.2-only commit that make the behaviour consistent between 2.2 and 3.0.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

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

[jira] [Updated] (CASSANDRA-13809) Make BatchlogManagerMBean.forceBatchlogReplay() blocking

[Aleksey Yeschenko (JIRA)]

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

Aleksey Yeschenko updated CASSANDRA-13809:
--
Fix Version/s: 2.2.x
   Status: Patch Available  (was: Open)

> Make BatchlogManagerMBean.forceBatchlogReplay() blocking
> 
>
> Key: CASSANDRA-13809
> URL: https://issues.apache.org/jira/browse/CASSANDRA-13809
> Project: Cassandra
>  Issue Type: Bug
>  Components: Coordination
>Reporter: Aleksey Yeschenko
>Assignee: Aleksey Yeschenko
>Priority: Minor
> Fix For: 2.2.x
>
>
> In 3.0, {{BatchlogManagerMBean.forceBatchlogReplay()}} blocks until 
> completion. In 2.2 it just submits a runnable and instaexits, which makes it 
> impossible to create non-flaky dtests that rely on batchlog replay.
> [here|https://github.com/iamaleksey/cassandra/commits/13809-2.2] is a small 
> 2.2-only commit that make the behaviour consistent between 2.2 and 3.0.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

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

[jira] [Issue Comment Deleted] (CASSANDRA-13809) Make BatchlogManagerMBean.forceBatchlogReplay() blocking

[Aleksey Yeschenko (JIRA)]

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

Aleksey Yeschenko updated CASSANDRA-13809:
--
Comment: was deleted

(was: Placeholder comment)

> Make BatchlogManagerMBean.forceBatchlogReplay() blocking
> 
>
> Key: CASSANDRA-13809
> URL: https://issues.apache.org/jira/browse/CASSANDRA-13809
> Project: Cassandra
>  Issue Type: Bug
>  Components: Coordination
>Reporter: Aleksey Yeschenko
>Assignee: Aleksey Yeschenko
>Priority: Minor
> Fix For: 2.2.x
>
>
> In 3.0, {{BatchlogManagerMBean.forceBatchlogReplay()}} blocks until 
> completion. In 2.2 it just submits a runnable and instaexits, which makes it 
> impossible to create non-flaky dtests that rely on batchlog replay.
> [here|https://github.com/iamaleksey/cassandra/commits/13809-2.2] is a small 
> 2.2-only commit that make the behaviour consistent between 2.2 and 3.0.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

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

[jira] [Updated] (CASSANDRA-13809) Make BatchlogManagerMBean.forceBatchlogReplay() blocking

[Aleksey Yeschenko (JIRA)]

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

Aleksey Yeschenko updated CASSANDRA-13809:
--
Attachment: (was: placeholder_patch.txt)

> Make BatchlogManagerMBean.forceBatchlogReplay() blocking
> 
>
> Key: CASSANDRA-13809
> URL: https://issues.apache.org/jira/browse/CASSANDRA-13809
> Project: Cassandra
>  Issue Type: Bug
>  Components: Coordination
>Reporter: Aleksey Yeschenko
>Assignee: Aleksey Yeschenko
>Priority: Minor
>
> In 3.0, {{BatchlogManagerMBean.forceBatchlogReplay()}} blocks until 
> completion. In 2.2 it just submits a runnable and instaexits, which makes it 
> impossible to create non-flaky dtests that rely on batchlog replay.
> [here|https://github.com/iamaleksey/cassandra/commits/13809-2.2] is a small 
> 2.2-only commit that make the behaviour consistent between 2.2 and 3.0.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

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

[jira] [Updated] (CASSANDRA-13809) Make BatchlogManagerMBean.forceBatchlogReplay() blocking

[Aleksey Yeschenko (JIRA)]

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

Aleksey Yeschenko updated CASSANDRA-13809:
--
 Labels:   (was: placeholder_label)
Summary: Make BatchlogManagerMBean.forceBatchlogReplay() blocking  
(was: Placeholder summary)
Description: 
In 3.0, {{BatchlogManagerMBean.forceBatchlogReplay()}} blocks until completion. 
In 2.2 it just submits a runnable and instaexits, which makes it impossible to 
create non-flaky dtests that rely on batchlog replay.

[here|https://github.com/iamaleksey/cassandra/commits/13809-2.2] is a small 
2.2-only commit that make the behaviour consistent between 2.2 and 3.0.

  was:Placeholder description


> Make BatchlogManagerMBean.forceBatchlogReplay() blocking
> 
>
> Key: CASSANDRA-13809
> URL: https://issues.apache.org/jira/browse/CASSANDRA-13809
> Project: Cassandra
>  Issue Type: Bug
>  Components: Coordination
>Reporter: Aleksey Yeschenko
>Assignee: Aleksey Yeschenko
>Priority: Minor
>
> In 3.0, {{BatchlogManagerMBean.forceBatchlogReplay()}} blocks until 
> completion. In 2.2 it just submits a runnable and instaexits, which makes it 
> impossible to create non-flaky dtests that rely on batchlog replay.
> [here|https://github.com/iamaleksey/cassandra/commits/13809-2.2] is a small 
> 2.2-only commit that make the behaviour consistent between 2.2 and 3.0.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

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

[jira] [Commented] (CASSANDRA-13809) Placeholder summary

[Aleksey Yeschenko (JIRA)]

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

Aleksey Yeschenko commented on CASSANDRA-13809:
---

You guys need to get a life or something.

> Placeholder summary
> ---
>
> Key: CASSANDRA-13809
> URL: https://issues.apache.org/jira/browse/CASSANDRA-13809
> Project: Cassandra
>  Issue Type: Bug
>  Components: Coordination
>Reporter: Aleksey Yeschenko
>Assignee: Aleksey Yeschenko
>Priority: Minor
>  Labels: placeholder_label
> Attachments: placeholder_patch.txt
>
>
> Placeholder description



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

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

[jira] [Updated] (CASSANDRA-13809) Placeholder summary

[Joshua McKenzie (JIRA)]

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

Joshua McKenzie updated CASSANDRA-13809:

Labels: placeholder_label  (was: )

> Placeholder summary
> ---
>
> Key: CASSANDRA-13809
> URL: https://issues.apache.org/jira/browse/CASSANDRA-13809
> Project: Cassandra
>  Issue Type: Bug
>  Components: Coordination
>Reporter: Aleksey Yeschenko
>Assignee: Aleksey Yeschenko
>Priority: Minor
>  Labels: placeholder_label
> Attachments: placeholder_patch.txt
>
>
> Placeholder description



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

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

[jira] [Commented] (CASSANDRA-13753) The documentation website can be fitted well on device width.

[Ashish Tomer (JIRA)]

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

Ashish Tomer commented on CASSANDRA-13753:
--

I'm sorry I bothered both of you. Also, thanks for helping me out.

> The documentation website can be fitted well on device width.
> -
>
> Key: CASSANDRA-13753
> URL: https://issues.apache.org/jira/browse/CASSANDRA-13753
> Project: Cassandra
>  Issue Type: Improvement
>  Components: Documentation and Website
> Environment: *Operating System : *Ubuntu
> *Browsers: *
> * Firefox
> * Google Chrome
>Reporter: Ashish Tomer
>Assignee: Ashish Tomer
>Priority: Minor
>  Labels: Responsive, UI, documentation, website
>   Original Estimate: 240h
>  Remaining Estimate: 240h
>
> The following shortcomings/ issues are noticed on the pages of cassandra 
> documentation website ([http://cassandra.apache.org/doc/latest/])
> *1.* On laptop screen with resolution 1366  768 the width of the 
> webpage is more than the width of the screen. The content of the website is 
> going left and user has to scroll horizontally to read the lines. The 
> horizontal scrollbar at the bottom needs to be removed.
> *2.* When some pages are scrolled down the whole page fluctuate and jump back 
> to top of the page. {color:red}Example link - 
> {color}[http://cassandra.apache.org/doc/latest/architecture/overview.html]
> *3.* The website is not mobile friendly and can be made responsive.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

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

[jira] [Updated] (CASSANDRA-13753) The documentation website can be fitted well on device width.

[Jeff Jirsa (JIRA)]

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

Jeff Jirsa updated CASSANDRA-13753:
---
Fix Version/s: (was: 4.x)

> The documentation website can be fitted well on device width.
> -
>
> Key: CASSANDRA-13753
> URL: https://issues.apache.org/jira/browse/CASSANDRA-13753
> Project: Cassandra
>  Issue Type: Improvement
>  Components: Documentation and Website
> Environment: *Operating System : *Ubuntu
> *Browsers: *
> * Firefox
> * Google Chrome
>Reporter: Ashish Tomer
>Assignee: Ashish Tomer
>Priority: Minor
>  Labels: Responsive, UI, documentation, website
>   Original Estimate: 240h
>  Remaining Estimate: 240h
>
> The following shortcomings/ issues are noticed on the pages of cassandra 
> documentation website ([http://cassandra.apache.org/doc/latest/])
> *1.* On laptop screen with resolution 1366  768 the width of the 
> webpage is more than the width of the screen. The content of the website is 
> going left and user has to scroll horizontally to read the lines. The 
> horizontal scrollbar at the bottom needs to be removed.
> *2.* When some pages are scrolled down the whole page fluctuate and jump back 
> to top of the page. {color:red}Example link - 
> {color}[http://cassandra.apache.org/doc/latest/architecture/overview.html]
> *3.* The website is not mobile friendly and can be made responsive.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

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

[jira] [Assigned] (CASSANDRA-13753) The documentation website can be fitted well on device width.

[Jeff Jirsa (JIRA)]

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

Jeff Jirsa reassigned CASSANDRA-13753:
--

Assignee: Ashish Tomer

> The documentation website can be fitted well on device width.
> -
>
> Key: CASSANDRA-13753
> URL: https://issues.apache.org/jira/browse/CASSANDRA-13753
> Project: Cassandra
>  Issue Type: Improvement
>  Components: Documentation and Website
> Environment: *Operating System : *Ubuntu
> *Browsers: *
> * Firefox
> * Google Chrome
>Reporter: Ashish Tomer
>Assignee: Ashish Tomer
>Priority: Minor
>  Labels: Responsive, UI, documentation, website
> Fix For: 4.x
>
>   Original Estimate: 240h
>  Remaining Estimate: 240h
>
> The following shortcomings/ issues are noticed on the pages of cassandra 
> documentation website ([http://cassandra.apache.org/doc/latest/])
> *1.* On laptop screen with resolution 1366  768 the width of the 
> webpage is more than the width of the screen. The content of the website is 
> going left and user has to scroll horizontally to read the lines. The 
> horizontal scrollbar at the bottom needs to be removed.
> *2.* When some pages are scrolled down the whole page fluctuate and jump back 
> to top of the page. {color:red}Example link - 
> {color}[http://cassandra.apache.org/doc/latest/architecture/overview.html]
> *3.* The website is not mobile friendly and can be made responsive.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

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

[jira] [Updated] (CASSANDRA-13753) The documentation website can be fitted well on device width.

[Ashish Tomer (JIRA)]

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

Ashish Tomer updated CASSANDRA-13753:
-
Fix Version/s: 4.x

> The documentation website can be fitted well on device width.
> -
>
> Key: CASSANDRA-13753
> URL: https://issues.apache.org/jira/browse/CASSANDRA-13753
> Project: Cassandra
>  Issue Type: Improvement
>  Components: Documentation and Website
> Environment: *Operating System : *Ubuntu
> *Browsers: *
> * Firefox
> * Google Chrome
>Reporter: Ashish Tomer
>Priority: Minor
>  Labels: Responsive, UI, documentation, website
> Fix For: 4.x
>
>   Original Estimate: 240h
>  Remaining Estimate: 240h
>
> The following shortcomings/ issues are noticed on the pages of cassandra 
> documentation website ([http://cassandra.apache.org/doc/latest/])
> *1.* On laptop screen with resolution 1366  768 the width of the 
> webpage is more than the width of the screen. The content of the website is 
> going left and user has to scroll horizontally to read the lines. The 
> horizontal scrollbar at the bottom needs to be removed.
> *2.* When some pages are scrolled down the whole page fluctuate and jump back 
> to top of the page. {color:red}Example link - 
> {color}[http://cassandra.apache.org/doc/latest/architecture/overview.html]
> *3.* The website is not mobile friendly and can be made responsive.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

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

[jira] [Comment Edited] (CASSANDRA-13753) The documentation website can be fitted well on device width.

[Emmanuel Lecharny (JIRA)]

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

Emmanuel Lecharny edited comment on CASSANDRA-13753 at 8/25/17 9:39 PM:


The first thing to do is not to pick random people. I'm not part of the 
Cassandra project, so you just made me a recipient of mails I don't really care 
about (each action on a JIRA ticket will resut in a mail sent to me if you make 
me a reviewer of this ticket).
If you are interested in participating to Cassandra, the very first step would 
be to read this page, I guess : 
http://cassandra.apache.org/doc/latest/development/index.html


was (Author: elecharny):
The first thing to do is not to pick random people. I'm not part of the 
Cassandra project, so you just made me a recipient of mails I don't really care 
about (each action on a JIRA ticket will resut in a mail sent to me if you make 
me a reviewer of this ticket).
If you are interested in participating to Cassandra, the very first step would 
be to reac this page, I guess : 
http://cassandra.apache.org/doc/latest/development/index.html

> The documentation website can be fitted well on device width.
> -
>
> Key: CASSANDRA-13753
> URL: https://issues.apache.org/jira/browse/CASSANDRA-13753
> Project: Cassandra
>  Issue Type: Improvement
>  Components: Documentation and Website
> Environment: *Operating System : *Ubuntu
> *Browsers: *
> * Firefox
> * Google Chrome
>Reporter: Ashish Tomer
>Priority: Minor
>  Labels: Responsive, UI, documentation, website
>   Original Estimate: 240h
>  Remaining Estimate: 240h
>
> The following shortcomings/ issues are noticed on the pages of cassandra 
> documentation website ([http://cassandra.apache.org/doc/latest/])
> *1.* On laptop screen with resolution 1366  768 the width of the 
> webpage is more than the width of the screen. The content of the website is 
> going left and user has to scroll horizontally to read the lines. The 
> horizontal scrollbar at the bottom needs to be removed.
> *2.* When some pages are scrolled down the whole page fluctuate and jump back 
> to top of the page. {color:red}Example link - 
> {color}[http://cassandra.apache.org/doc/latest/architecture/overview.html]
> *3.* The website is not mobile friendly and can be made responsive.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

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

[jira] [Commented] (CASSANDRA-13753) The documentation website can be fitted well on device width.

[Jeff Jirsa (JIRA)]

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

Jeff Jirsa commented on CASSANDRA-13753:


Please do not pick people randomly, there are far too many people in JIRA for 
that to be an effective strategy.

The normal database committers are also able to commit to the website. The 
source code for the site is 
[here|https://svn.apache.org/repos/asf/cassandra/site/] . If you create a 
change, please upload the diff to the JIRA and set the status to 
patch-available.



> The documentation website can be fitted well on device width.
> -
>
> Key: CASSANDRA-13753
> URL: https://issues.apache.org/jira/browse/CASSANDRA-13753
> Project: Cassandra
>  Issue Type: Improvement
>  Components: Documentation and Website
> Environment: *Operating System : *Ubuntu
> *Browsers: *
> * Firefox
> * Google Chrome
>Reporter: Ashish Tomer
>Priority: Minor
>  Labels: Responsive, UI, documentation, website
>   Original Estimate: 240h
>  Remaining Estimate: 240h
>
> The following shortcomings/ issues are noticed on the pages of cassandra 
> documentation website ([http://cassandra.apache.org/doc/latest/])
> *1.* On laptop screen with resolution 1366  768 the width of the 
> webpage is more than the width of the screen. The content of the website is 
> going left and user has to scroll horizontally to read the lines. The 
> horizontal scrollbar at the bottom needs to be removed.
> *2.* When some pages are scrolled down the whole page fluctuate and jump back 
> to top of the page. {color:red}Example link - 
> {color}[http://cassandra.apache.org/doc/latest/architecture/overview.html]
> *3.* The website is not mobile friendly and can be made responsive.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

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

[jira] [Commented] (CASSANDRA-13753) The documentation website can be fitted well on device width.

[Emmanuel Lecharny (JIRA)]

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

Emmanuel Lecharny commented on CASSANDRA-13753:
---

The first thing to do is not to pick random people. I'm not part of the 
Cassandra project, so you just made me a recipient of mails I don't really care 
about (each action on a JIRA ticket will resut in a mail sent to me if you make 
me a reviewer of this ticket).
If you are interested in participating to Cassandra, the very first step would 
be to reac this page, I guess : 
http://cassandra.apache.org/doc/latest/development/index.html

> The documentation website can be fitted well on device width.
> -
>
> Key: CASSANDRA-13753
> URL: https://issues.apache.org/jira/browse/CASSANDRA-13753
> Project: Cassandra
>  Issue Type: Improvement
>  Components: Documentation and Website
> Environment: *Operating System : *Ubuntu
> *Browsers: *
> * Firefox
> * Google Chrome
>Reporter: Ashish Tomer
>Priority: Minor
>  Labels: Responsive, UI, documentation, website
>   Original Estimate: 240h
>  Remaining Estimate: 240h
>
> The following shortcomings/ issues are noticed on the pages of cassandra 
> documentation website ([http://cassandra.apache.org/doc/latest/])
> *1.* On laptop screen with resolution 1366  768 the width of the 
> webpage is more than the width of the screen. The content of the website is 
> going left and user has to scroll horizontally to read the lines. The 
> horizontal scrollbar at the bottom needs to be removed.
> *2.* When some pages are scrolled down the whole page fluctuate and jump back 
> to top of the page. {color:red}Example link - 
> {color}[http://cassandra.apache.org/doc/latest/architecture/overview.html]
> *3.* The website is not mobile friendly and can be made responsive.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

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

[jira] [Commented] (CASSANDRA-13418) Allow TWCS to ignore overlaps when dropping fully expired sstables

[mck (JIRA)]

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

mck commented on CASSANDRA-13418:
-

{quote}N.B: I tried to apply the syle guide found in 
.idea/codeStyleSettings.xml but it is changing me a lot of things. Do you know 
if it is up to date ?{quote}
I don't use IntelliJ so I can't answer that for you, sry. [~krummas]?
Otherwise you can ask on irc #cassandra or on the user mailing list.

{quote}I enable uncheckedTombstoneCompaction when ignoreOverlaps is 
activated{quote}
I'm -1 on this for the moment. While it holds a logic argument, as you explain, 
it's not intuitive for the user. The user has to know that this happens (via 
docs or via code). I'd be more comfortable expecting the users using an 
advanced toggle like this (requires system properties and table option) to 
appreciate the difference between {{uncheckedTombstoneCompaction}} and 
{{unsafe_aggressive_sstable_expiration}} and to enable both. Any smarts can be 
added latter on with further user feedback and experience.

> Allow TWCS to ignore overlaps when dropping fully expired sstables
> --
>
> Key: CASSANDRA-13418
> URL: https://issues.apache.org/jira/browse/CASSANDRA-13418
> Project: Cassandra
>  Issue Type: Improvement
>  Components: Compaction
>Reporter: Corentin Chary
>  Labels: twcs
> Attachments: twcs-cleanup.png
>
>
> http://thelastpickle.com/blog/2016/12/08/TWCS-part1.html explains it well. If 
> you really want read-repairs you're going to have sstables blocking the 
> expiration of other fully expired SSTables because they overlap.
> You can set unchecked_tombstone_compaction = true or tombstone_threshold to a 
> very low value and that will purge the blockers of old data that should 
> already have expired, thus removing the overlaps and allowing the other 
> SSTables to expire.
> The thing is that this is rather CPU intensive and not optimal. If you have 
> time series, you might not care if all your data doesn't exactly expire at 
> the right time, or if data re-appears for some time, as long as it gets 
> deleted as soon as it can. And in this situation I believe it would be really 
> beneficial to allow users to simply ignore overlapping SSTables when looking 
> for fully expired ones.
> To the question: why would you need read-repairs ?
> - Full repairs basically take longer than the TTL of the data on my dataset, 
> so this isn't really effective.
> - Even with a 10% chances of doing a repair, we found out that this would be 
> enough to greatly reduce entropy of the most used data (and if you have 
> timeseries, you're likely to have a dashboard doing the same important 
> queries over and over again).
> - LOCAL_QUORUM is too expensive (need >3 replicas), QUORUM is too slow.
> I'll try to come up with a patch demonstrating how this would work, try it on 
> our system and report the effects.
> cc: [~adejanovski], [~rgerard] as I know you worked on similar issues already.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

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

[jira] [Comment Edited] (CASSANDRA-13753) The documentation website can be fitted well on device width.

[Ashish Tomer (JIRA)]

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

Ashish Tomer edited comment on CASSANDRA-13753 at 8/25/17 9:28 PM:
---

[~agoundao] I didn't know who could review the UI part of the website. So, I 
picked people randomly. Can you help me out how I can make changes in this 
website and who can review those changes? Actually, I am looking for my first 
OS contribution and it would be awesome if I could help the OS community. I 
know how to use Git and create pull requests. 


was (Author: ashish1269):
[~agoundao] I didn't know who could review the UI part of the website. So, I 
picked people randomly. Can you help me out how I can make changes in this 
website and who can review those changes? Actually, I am looking for my first 
OS contribution and it would be awesome if I could help the OS community .

> The documentation website can be fitted well on device width.
> -
>
> Key: CASSANDRA-13753
> URL: https://issues.apache.org/jira/browse/CASSANDRA-13753
> Project: Cassandra
>  Issue Type: Improvement
>  Components: Documentation and Website
> Environment: *Operating System : *Ubuntu
> *Browsers: *
> * Firefox
> * Google Chrome
>Reporter: Ashish Tomer
>Priority: Minor
>  Labels: Responsive, UI, documentation, website
>   Original Estimate: 240h
>  Remaining Estimate: 240h
>
> The following shortcomings/ issues are noticed on the pages of cassandra 
> documentation website ([http://cassandra.apache.org/doc/latest/])
> *1.* On laptop screen with resolution 1366  768 the width of the 
> webpage is more than the width of the screen. The content of the website is 
> going left and user has to scroll horizontally to read the lines. The 
> horizontal scrollbar at the bottom needs to be removed.
> *2.* When some pages are scrolled down the whole page fluctuate and jump back 
> to top of the page. {color:red}Example link - 
> {color}[http://cassandra.apache.org/doc/latest/architecture/overview.html]
> *3.* The website is not mobile friendly and can be made responsive.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

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

[jira] [Commented] (CASSANDRA-13753) The documentation website can be fitted well on device width.

[Ashish Tomer (JIRA)]

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

Ashish Tomer commented on CASSANDRA-13753:
--

[~agoundao] I didn't know who could review the UI part of the website. So, I 
picked people randomly. Can you help me out how I can make changes in this 
website and who can review those changes? Actually, I am looking for my first 
OS contribution and it would be awesome if I could help the OS community .

> The documentation website can be fitted well on device width.
> -
>
> Key: CASSANDRA-13753
> URL: https://issues.apache.org/jira/browse/CASSANDRA-13753
> Project: Cassandra
>  Issue Type: Improvement
>  Components: Documentation and Website
> Environment: *Operating System : *Ubuntu
> *Browsers: *
> * Firefox
> * Google Chrome
>Reporter: Ashish Tomer
>Priority: Minor
>  Labels: Responsive, UI, documentation, website
>   Original Estimate: 240h
>  Remaining Estimate: 240h
>
> The following shortcomings/ issues are noticed on the pages of cassandra 
> documentation website ([http://cassandra.apache.org/doc/latest/])
> *1.* On laptop screen with resolution 1366  768 the width of the 
> webpage is more than the width of the screen. The content of the website is 
> going left and user has to scroll horizontally to read the lines. The 
> horizontal scrollbar at the bottom needs to be removed.
> *2.* When some pages are scrolled down the whole page fluctuate and jump back 
> to top of the page. {color:red}Example link - 
> {color}[http://cassandra.apache.org/doc/latest/architecture/overview.html]
> *3.* The website is not mobile friendly and can be made responsive.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

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

[jira] [Updated] (CASSANDRA-13753) The documentation website can be fitted well on device width.

[Jeff Jirsa (JIRA)]

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

Jeff Jirsa updated CASSANDRA-13753:
---
Fix Version/s: (was: 4.x)

> The documentation website can be fitted well on device width.
> -
>
> Key: CASSANDRA-13753
> URL: https://issues.apache.org/jira/browse/CASSANDRA-13753
> Project: Cassandra
>  Issue Type: Improvement
>  Components: Documentation and Website
> Environment: *Operating System : *Ubuntu
> *Browsers: *
> * Firefox
> * Google Chrome
>Reporter: Ashish Tomer
>Priority: Minor
>  Labels: Responsive, UI, documentation, website
>   Original Estimate: 240h
>  Remaining Estimate: 240h
>
> The following shortcomings/ issues are noticed on the pages of cassandra 
> documentation website ([http://cassandra.apache.org/doc/latest/])
> *1.* On laptop screen with resolution 1366  768 the width of the 
> webpage is more than the width of the screen. The content of the website is 
> going left and user has to scroll horizontally to read the lines. The 
> horizontal scrollbar at the bottom needs to be removed.
> *2.* When some pages are scrolled down the whole page fluctuate and jump back 
> to top of the page. {color:red}Example link - 
> {color}[http://cassandra.apache.org/doc/latest/architecture/overview.html]
> *3.* The website is not mobile friendly and can be made responsive.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

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

[jira] [Updated] (CASSANDRA-13753) The documentation website can be fitted well on device width.

[Jeff Jirsa (JIRA)]

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

Jeff Jirsa updated CASSANDRA-13753:
---
Flags:   (was: Patch,Important)

> The documentation website can be fitted well on device width.
> -
>
> Key: CASSANDRA-13753
> URL: https://issues.apache.org/jira/browse/CASSANDRA-13753
> Project: Cassandra
>  Issue Type: Improvement
>  Components: Documentation and Website
> Environment: *Operating System : *Ubuntu
> *Browsers: *
> * Firefox
> * Google Chrome
>Reporter: Ashish Tomer
>Priority: Minor
>  Labels: Responsive, UI, documentation, website
>   Original Estimate: 240h
>  Remaining Estimate: 240h
>
> The following shortcomings/ issues are noticed on the pages of cassandra 
> documentation website ([http://cassandra.apache.org/doc/latest/])
> *1.* On laptop screen with resolution 1366  768 the width of the 
> webpage is more than the width of the screen. The content of the website is 
> going left and user has to scroll horizontally to read the lines. The 
> horizontal scrollbar at the bottom needs to be removed.
> *2.* When some pages are scrolled down the whole page fluctuate and jump back 
> to top of the page. {color:red}Example link - 
> {color}[http://cassandra.apache.org/doc/latest/architecture/overview.html]
> *3.* The website is not mobile friendly and can be made responsive.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

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

[jira] [Commented] (CASSANDRA-13753) The documentation website can be fitted well on device width.

[Jeff Jirsa (JIRA)]

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

Jeff Jirsa commented on CASSANDRA-13753:


Removed you (not sure how you got set as reviewer, either, but you're not 
reviewer anymore)

> The documentation website can be fitted well on device width.
> -
>
> Key: CASSANDRA-13753
> URL: https://issues.apache.org/jira/browse/CASSANDRA-13753
> Project: Cassandra
>  Issue Type: Improvement
>  Components: Documentation and Website
> Environment: *Operating System : *Ubuntu
> *Browsers: *
> * Firefox
> * Google Chrome
>Reporter: Ashish Tomer
>Priority: Minor
>  Labels: Responsive, UI, documentation, website
> Fix For: 4.x
>
>   Original Estimate: 240h
>  Remaining Estimate: 240h
>
> The following shortcomings/ issues are noticed on the pages of cassandra 
> documentation website ([http://cassandra.apache.org/doc/latest/])
> *1.* On laptop screen with resolution 1366  768 the width of the 
> webpage is more than the width of the screen. The content of the website is 
> going left and user has to scroll horizontally to read the lines. The 
> horizontal scrollbar at the bottom needs to be removed.
> *2.* When some pages are scrolled down the whole page fluctuate and jump back 
> to top of the page. {color:red}Example link - 
> {color}[http://cassandra.apache.org/doc/latest/architecture/overview.html]
> *3.* The website is not mobile friendly and can be made responsive.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

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

[jira] [Updated] (CASSANDRA-13753) The documentation website can be fitted well on device width.

[Jeff Jirsa (JIRA)]

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

Jeff Jirsa updated CASSANDRA-13753:
---
Reviewer:   (was: Emmanuel Lecharny)

> The documentation website can be fitted well on device width.
> -
>
> Key: CASSANDRA-13753
> URL: https://issues.apache.org/jira/browse/CASSANDRA-13753
> Project: Cassandra
>  Issue Type: Improvement
>  Components: Documentation and Website
> Environment: *Operating System : *Ubuntu
> *Browsers: *
> * Firefox
> * Google Chrome
>Reporter: Ashish Tomer
>Priority: Minor
>  Labels: Responsive, UI, documentation, website
> Fix For: 4.x
>
>   Original Estimate: 240h
>  Remaining Estimate: 240h
>
> The following shortcomings/ issues are noticed on the pages of cassandra 
> documentation website ([http://cassandra.apache.org/doc/latest/])
> *1.* On laptop screen with resolution 1366  768 the width of the 
> webpage is more than the width of the screen. The content of the website is 
> going left and user has to scroll horizontally to read the lines. The 
> horizontal scrollbar at the bottom needs to be removed.
> *2.* When some pages are scrolled down the whole page fluctuate and jump back 
> to top of the page. {color:red}Example link - 
> {color}[http://cassandra.apache.org/doc/latest/architecture/overview.html]
> *3.* The website is not mobile friendly and can be made responsive.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

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

[jira] [Commented] (CASSANDRA-13753) The documentation website can be fitted well on device width.

[Emmanuel Lecharny (JIRA)]

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

Emmanuel Lecharny commented on CASSANDRA-13753:
---

I have no idea why I'm set as reviewer for this issue... Can I be removed ?
Thanks !

> The documentation website can be fitted well on device width.
> -
>
> Key: CASSANDRA-13753
> URL: https://issues.apache.org/jira/browse/CASSANDRA-13753
> Project: Cassandra
>  Issue Type: Improvement
>  Components: Documentation and Website
> Environment: *Operating System : *Ubuntu
> *Browsers: *
> * Firefox
> * Google Chrome
>Reporter: Ashish Tomer
>Priority: Minor
>  Labels: Responsive, UI, documentation, website
> Fix For: 4.x
>
>   Original Estimate: 240h
>  Remaining Estimate: 240h
>
> The following shortcomings/ issues are noticed on the pages of cassandra 
> documentation website ([http://cassandra.apache.org/doc/latest/])
> *1.* On laptop screen with resolution 1366  768 the width of the 
> webpage is more than the width of the screen. The content of the website is 
> going left and user has to scroll horizontally to read the lines. The 
> horizontal scrollbar at the bottom needs to be removed.
> *2.* When some pages are scrolled down the whole page fluctuate and jump back 
> to top of the page. {color:red}Example link - 
> {color}[http://cassandra.apache.org/doc/latest/architecture/overview.html]
> *3.* The website is not mobile friendly and can be made responsive.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

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

[jira] [Issue Comment Deleted] (CASSANDRA-13809) Placeholder summary

[Ariel Weisberg (JIRA)]

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

Ariel Weisberg updated CASSANDRA-13809:
---
Comment: was deleted

(was: Placeholder bikeshed.)

> Placeholder summary
> ---
>
> Key: CASSANDRA-13809
> URL: https://issues.apache.org/jira/browse/CASSANDRA-13809
> Project: Cassandra
>  Issue Type: Bug
>  Components: Coordination
>Reporter: Aleksey Yeschenko
>Assignee: Aleksey Yeschenko
>Priority: Minor
> Attachments: placeholder_patch.txt
>
>
> Placeholder description



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

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

[jira] [Commented] (CASSANDRA-13809) Placeholder summary

[Ariel Weisberg (JIRA)]

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

Ariel Weisberg commented on CASSANDRA-13809:


Placeholder bikeshed.

> Placeholder summary
> ---
>
> Key: CASSANDRA-13809
> URL: https://issues.apache.org/jira/browse/CASSANDRA-13809
> Project: Cassandra
>  Issue Type: Bug
>  Components: Coordination
>Reporter: Aleksey Yeschenko
>Assignee: Aleksey Yeschenko
>Priority: Minor
> Attachments: placeholder_patch.txt
>
>
> Placeholder description



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

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

[jira] [Updated] (CASSANDRA-13809) Placeholder summary

[Robert Stupp (JIRA)]

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

Robert Stupp updated CASSANDRA-13809:
-
Attachment: placeholder_patch.txt

> Placeholder summary
> ---
>
> Key: CASSANDRA-13809
> URL: https://issues.apache.org/jira/browse/CASSANDRA-13809
> Project: Cassandra
>  Issue Type: Bug
>  Components: Coordination
>Reporter: Aleksey Yeschenko
>Assignee: Aleksey Yeschenko
>Priority: Minor
> Attachments: placeholder_patch.txt
>
>
> Placeholder description



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

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

[jira] [Commented] (CASSANDRA-13809) Placeholder summary

[Jeremy Hanna (JIRA)]

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

Jeremy Hanna commented on CASSANDRA-13809:
--

Placeholder comment

> Placeholder summary
> ---
>
> Key: CASSANDRA-13809
> URL: https://issues.apache.org/jira/browse/CASSANDRA-13809
> Project: Cassandra
>  Issue Type: Bug
>  Components: Coordination
>Reporter: Aleksey Yeschenko
>Assignee: Aleksey Yeschenko
>Priority: Minor
>
> Placeholder description



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

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

[jira] [Updated] (CASSANDRA-13753) The documentation website can be fitted well on device width.

[Ashish Tomer (JIRA)]

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

Ashish Tomer updated CASSANDRA-13753:
-
Priority: Minor  (was: Major)

> The documentation website can be fitted well on device width.
> -
>
> Key: CASSANDRA-13753
> URL: https://issues.apache.org/jira/browse/CASSANDRA-13753
> Project: Cassandra
>  Issue Type: Improvement
>  Components: Documentation and Website
> Environment: *Operating System : *Ubuntu
> *Browsers: *
> * Firefox
> * Google Chrome
>Reporter: Ashish Tomer
>Priority: Minor
>  Labels: Responsive, UI, documentation, website
> Fix For: 4.x
>
>   Original Estimate: 240h
>  Remaining Estimate: 240h
>
> The following shortcomings/ issues are noticed on the pages of cassandra 
> documentation website ([http://cassandra.apache.org/doc/latest/])
> *1.* On laptop screen with resolution 1366  768 the width of the 
> webpage is more than the width of the screen. The content of the website is 
> going left and user has to scroll horizontally to read the lines. The 
> horizontal scrollbar at the bottom needs to be removed.
> *2.* When some pages are scrolled down the whole page fluctuate and jump back 
> to top of the page. {color:red}Example link - 
> {color}[http://cassandra.apache.org/doc/latest/architecture/overview.html]
> *3.* The website is not mobile friendly and can be made responsive.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

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

[jira] [Updated] (CASSANDRA-12704) snapshot build never be able to publish to mvn artifactory

[Jay Zhuang (JIRA)]

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

Jay Zhuang updated CASSANDRA-12704:
---
Fix Version/s: (was: 3.7)

> snapshot build never be able to publish to mvn artifactory
> --
>
> Key: CASSANDRA-12704
> URL: https://issues.apache.org/jira/browse/CASSANDRA-12704
> Project: Cassandra
>  Issue Type: Bug
>  Components: Packaging
>Reporter: Jay Zhuang
>Assignee: Jay Zhuang
>Priority: Minor
> Attachments: 12704-trunk.txt
>
>
> {code}
> $ ant publish
> {code}
> works fine when property "release" is set, which publishes the binaries to 
> release Artifactory.
> But for daily snapshot build, if "release" is set, it won't be snapshot build:
> https://github.com/apache/cassandra/blob/cassandra-3.7/build.xml#L74
> if "release" is not set, it doesn't publish to snapshot Artifactory:
> https://github.com/apache/cassandra/blob/cassandra-3.7/build.xml#L1888
> I would suggest just removing the "if check" for target "publish".



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

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

[jira] [Updated] (CASSANDRA-12704) snapshot build never be able to publish to mvn artifactory

[Jay Zhuang (JIRA)]

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

Jay Zhuang updated CASSANDRA-12704:
---
Reviewer:   (was: Eric Evans)

> snapshot build never be able to publish to mvn artifactory
> --
>
> Key: CASSANDRA-12704
> URL: https://issues.apache.org/jira/browse/CASSANDRA-12704
> Project: Cassandra
>  Issue Type: Bug
>  Components: Packaging
>Reporter: Jay Zhuang
>Assignee: Jay Zhuang
>Priority: Minor
> Attachments: 12704-trunk.txt
>
>
> {code}
> $ ant publish
> {code}
> works fine when property "release" is set, which publishes the binaries to 
> release Artifactory.
> But for daily snapshot build, if "release" is set, it won't be snapshot build:
> https://github.com/apache/cassandra/blob/cassandra-3.7/build.xml#L74
> if "release" is not set, it doesn't publish to snapshot Artifactory:
> https://github.com/apache/cassandra/blob/cassandra-3.7/build.xml#L1888
> I would suggest just removing the "if check" for target "publish".



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

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

[jira] [Updated] (CASSANDRA-13809) Placeholder summary

[Jeff Jirsa (JIRA)]

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

Jeff Jirsa updated CASSANDRA-13809:
---
Reviewer: Jeff Jirsa

> Placeholder summary
> ---
>
> Key: CASSANDRA-13809
> URL: https://issues.apache.org/jira/browse/CASSANDRA-13809
> Project: Cassandra
>  Issue Type: Bug
>  Components: Coordination
>Reporter: Aleksey Yeschenko
>Assignee: Aleksey Yeschenko
>Priority: Minor
>
> Placeholder description



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

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

[jira] [Created] (CASSANDRA-13809) Placeholder summary

[Aleksey Yeschenko (JIRA)]

Aleksey Yeschenko created CASSANDRA-13809:
-

 Summary: Placeholder summary
 Key: CASSANDRA-13809
 URL: https://issues.apache.org/jira/browse/CASSANDRA-13809
 Project: Cassandra
  Issue Type: Bug
  Components: Coordination
Reporter: Aleksey Yeschenko
Assignee: Aleksey Yeschenko
Priority: Minor


Placeholder description



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

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

[jira] [Updated] (CASSANDRA-13808) Integer overflows with Amazon Elastic File System (EFS)

[Vitalii Ishchenko (JIRA)]

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

Vitalii Ishchenko updated CASSANDRA-13808:
--
Description: 
Integer overflow issue was fixed for cassandra 2.2, but since then new property 
was introduced in config that also derives from disk size  
{{cdc_total_space_in_mb}}

It should be updated too 
https://github.com/apache/cassandra/blob/6b7d73a49695c0ceb78bc7a003ace606a806c13a/src/java/org/apache/cassandra/config/DatabaseDescriptor.java#L484

  was:
Integer overflow issue was fixed for cassandra 2.2, but since then new property 
was introduced in config that also derives from disk size  
{{cdc_total_space_in_mb}}

It should be updated too 
https://github.com/apache/cassandra/blob/6b7d73a49695c0ceb78bc7a003ace606a806c13a/src/java/org/apache/cassandra/config/DatabaseDescriptor.java#L484

Related to CASSANDRA-13067


> Integer overflows with Amazon Elastic File System (EFS)
> ---
>
> Key: CASSANDRA-13808
> URL: https://issues.apache.org/jira/browse/CASSANDRA-13808
> Project: Cassandra
>  Issue Type: Bug
>  Components: Core
>Reporter: Vitalii Ishchenko
>
> Integer overflow issue was fixed for cassandra 2.2, but since then new 
> property was introduced in config that also derives from disk size  
> {{cdc_total_space_in_mb}}
> It should be updated too 
> https://github.com/apache/cassandra/blob/6b7d73a49695c0ceb78bc7a003ace606a806c13a/src/java/org/apache/cassandra/config/DatabaseDescriptor.java#L484



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

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

[jira] [Updated] (CASSANDRA-13808) Integer overflows with Amazon Elastic File System (EFS)

[Vitalii Ishchenko (JIRA)]

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

Vitalii Ishchenko updated CASSANDRA-13808:
--
Description: 
Integer overflow issue was fixed for cassandra 2.2, but since then new property 
was introduced in config that also derives from disk size  
{{cdc_total_space_in_mb}}

It should be updated too 
https://github.com/apache/cassandra/blob/6b7d73a49695c0ceb78bc7a003ace606a806c13a/src/java/org/apache/cassandra/config/DatabaseDescriptor.java#L484

Related to CASSANDRA-13067

  was:
Integer overflow issue was fixed for cassandra 2.2, but since then new property 
was introduced in config that also derives from disk size  
{{cdc_total_space_in_mb}}

It should be updated too

https://github.com/apache/cassandra/blob/6b7d73a49695c0ceb78bc7a003ace606a806c13a/src/java/org/apache/cassandra/config/DatabaseDescriptor.java#L484


> Integer overflows with Amazon Elastic File System (EFS)
> ---
>
> Key: CASSANDRA-13808
> URL: https://issues.apache.org/jira/browse/CASSANDRA-13808
> Project: Cassandra
>  Issue Type: Bug
>  Components: Core
>Reporter: Vitalii Ishchenko
>
> Integer overflow issue was fixed for cassandra 2.2, but since then new 
> property was introduced in config that also derives from disk size  
> {{cdc_total_space_in_mb}}
> It should be updated too 
> https://github.com/apache/cassandra/blob/6b7d73a49695c0ceb78bc7a003ace606a806c13a/src/java/org/apache/cassandra/config/DatabaseDescriptor.java#L484
> Related to CASSANDRA-13067



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

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

[jira] [Created] (CASSANDRA-13808) Integer overflows with Amazon Elastic File System (EFS)

[Vitalii Ishchenko (JIRA)]

Vitalii Ishchenko created CASSANDRA-13808:
-

 Summary: Integer overflows with Amazon Elastic File System (EFS)
 Key: CASSANDRA-13808
 URL: https://issues.apache.org/jira/browse/CASSANDRA-13808
 Project: Cassandra
  Issue Type: Bug
  Components: Core
Reporter: Vitalii Ishchenko


Integer overflow issue was fixed for cassandra 2.2, but since then new property 
was introduced in config that also derives from disk size  
{{cdc_total_space_in_mb}}

It should be updated too

https://github.com/apache/cassandra/blob/6b7d73a49695c0ceb78bc7a003ace606a806c13a/src/java/org/apache/cassandra/config/DatabaseDescriptor.java#L484



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

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

[jira] [Commented] (CASSANDRA-13798) Disallow filtering on non-primary-key base column for MV

[ZhaoYang (JIRA)]

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

ZhaoYang commented on CASSANDRA-13798:
--

This ticket is to block creating new table with non-pk base column filtering.

All internal filter related logic are still there for supporting filter 
conditions on base pk. (existed even before CASSANDRA-10368)

Existing users of 3.10/3.11 with non-pk base column should still be able to 
successfully upgrade and use the broken non-pk base column filtering.( 
probably, we should give them an option to avoid filtering as well..). 

> Disallow filtering on non-primary-key base column for MV
> 
>
> Key: CASSANDRA-13798
> URL: https://issues.apache.org/jira/browse/CASSANDRA-13798
> Project: Cassandra
>  Issue Type: Bug
>  Components: Materialized Views
>Reporter: ZhaoYang
>Assignee: ZhaoYang
>
> We should probably consider disallow filtering conditions on non-primary-key 
> base column for Materialized View which is introduced in CASSANDRA-10368.
> The main problem is that the liveness of view row is now depending on 
> multiple base columns (multiple filtered non-pk base column + base column 
> used in view pk) and this semantic could not be properly support without 
> drastic storage format changes. (SEE CASSANDRA-11500, 
> [background|https://issues.apache.org/jira/browse/CASSANDRA-11500?focusedCommentId=16119823=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-16119823])
> We should step back and re-consider the non-primary-key filtering feature 
> together with supporting multiple non-PK cols in MV clustering key in 
> CASSANDRA-10226.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

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

[jira] [Comment Edited] (CASSANDRA-13798) Disallow filtering on non-primary-key base column for MV

[Paulo Motta (JIRA)]

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

Paulo Motta edited comment on CASSANDRA-13798 at 8/25/17 3:43 PM:
--

bq.  If I was affected (I really have to check this) this would either force me 
to change my schema or to be blocked on updates. Both is not viable if the 
current solution works for my needs. For example I am not really affected if I 
have an insert-only payload or if my data does not expire.

It seems from a quick peek at the patch that this just forbids creation of new 
tables with non-PK conditions, but does not break existing tables. So this just 
changes the UX to prevent news users from shooting themselves in the foot, but 
keeps the underlying machinery to support it (which will probably be reused 
when the feature is fully supported). Perhaps we can even have a hidden system 
flag to allow table creation if you "know what you are doing"© and you can 
guarantee there are no column updates. In any case, we should explain the 
reasoning behind the revert and maybe expose the system flag for append-only 
workloads on NEWS.txt.


was (Author: pauloricardomg):
bq.  If I was affected (I really have to check this) this would either force me 
to change my schema or to be blocked on updates. Both is not viable if the 
current solution works for my needs. For example I am not really affected if I 
have an insert-only payload or if my data does not expire.

It seems from a quick peek at the patch that this just forbids creation of new 
tables with non-PK conditions, but does not break existing tables. So this just 
changes the UX to prevent users from shooting themselves in the foot, but keeps 
the underlying machinery to support it (which will probably be reused when the 
feature is fully supported). Perhaps we can even have a hidden system flag to 
allow table creation if you "know what you are doing"© and you can guarantee 
there are no column updates. In any case, we should explain the reasoning 
behind the revert and maybe expose the system flag for append-only workloads on 
NEWS.txt.

> Disallow filtering on non-primary-key base column for MV
> 
>
> Key: CASSANDRA-13798
> URL: https://issues.apache.org/jira/browse/CASSANDRA-13798
> Project: Cassandra
>  Issue Type: Bug
>  Components: Materialized Views
>Reporter: ZhaoYang
>Assignee: ZhaoYang
>
> We should probably consider disallow filtering conditions on non-primary-key 
> base column for Materialized View which is introduced in CASSANDRA-10368.
> The main problem is that the liveness of view row is now depending on 
> multiple base columns (multiple filtered non-pk base column + base column 
> used in view pk) and this semantic could not be properly support without 
> drastic storage format changes. (SEE CASSANDRA-11500, 
> [background|https://issues.apache.org/jira/browse/CASSANDRA-11500?focusedCommentId=16119823=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-16119823])
> We should step back and re-consider the non-primary-key filtering feature 
> together with supporting multiple non-PK cols in MV clustering key in 
> CASSANDRA-10226.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

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

[jira] [Commented] (CASSANDRA-13798) Disallow filtering on non-primary-key base column for MV

[Paulo Motta (JIRA)]

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

Paulo Motta commented on CASSANDRA-13798:
-

bq.  If I was affected (I really have to check this) this would either force me 
to change my schema or to be blocked on updates. Both is not viable if the 
current solution works for my needs. For example I am not really affected if I 
have an insert-only payload or if my data does not expire.

It seems from a quick peek at the patch that this just forbids creation of new 
tables with non-PK conditions, but does not break existing tables. So this just 
changes the UX to prevent users from shooting themselves in the foot, but keeps 
the underlying machinery to support it (which will probably be reused when the 
feature is fully supported). Perhaps we can even have a hidden system flag to 
allow table creation if you "know what you are doing"© and you can guarantee 
there are no column updates. In any case, we should explain the reasoning 
behind the revert and maybe expose the system flag for append-only workloads on 
NEWS.txt.

> Disallow filtering on non-primary-key base column for MV
> 
>
> Key: CASSANDRA-13798
> URL: https://issues.apache.org/jira/browse/CASSANDRA-13798
> Project: Cassandra
>  Issue Type: Bug
>  Components: Materialized Views
>Reporter: ZhaoYang
>Assignee: ZhaoYang
>
> We should probably consider disallow filtering conditions on non-primary-key 
> base column for Materialized View which is introduced in CASSANDRA-10368.
> The main problem is that the liveness of view row is now depending on 
> multiple base columns (multiple filtered non-pk base column + base column 
> used in view pk) and this semantic could not be properly support without 
> drastic storage format changes. (SEE CASSANDRA-11500, 
> [background|https://issues.apache.org/jira/browse/CASSANDRA-11500?focusedCommentId=16119823=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-16119823])
> We should step back and re-consider the non-primary-key filtering feature 
> together with supporting multiple non-PK cols in MV clustering key in 
> CASSANDRA-10226.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

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

[jira] [Updated] (CASSANDRA-13807) CircleCI fix - only collect the xml file from containers where it exists

[Marcus Eriksson (JIRA)]

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

Marcus Eriksson updated CASSANDRA-13807:

Description: 
Followup from CASSANDRA-13775 - my fix with {{ant eclipse-warnings}} obviously 
does not work since it doesn't generate any xml files

Push a new fix here: 
https://github.com/krummas/cassandra/commits/marcuse/fix_circle_3.0 which only 
collects the xml file from the first 3 containers
Test running here: https://circleci.com/gh/krummas/cassandra/86

  was:
{color:red}colored text{color}Followup from CASSANDRA-13775 - my fix with {{ant 
eclipse-warnings}} obviously does not work since it doesn't generate any xml 
files

Push a new fix here: 
https://github.com/krummas/cassandra/commits/marcuse/fix_circle_3.0 which only 
collects the xml file from the first 3 containers
Test running here: https://circleci.com/gh/krummas/cassandra/86


> CircleCI fix - only collect the xml file from containers where it exists
> 
>
> Key: CASSANDRA-13807
> URL: https://issues.apache.org/jira/browse/CASSANDRA-13807
> Project: Cassandra
>  Issue Type: Bug
>Reporter: Marcus Eriksson
>
> Followup from CASSANDRA-13775 - my fix with {{ant eclipse-warnings}} 
> obviously does not work since it doesn't generate any xml files
> Push a new fix here: 
> https://github.com/krummas/cassandra/commits/marcuse/fix_circle_3.0 which 
> only collects the xml file from the first 3 containers
> Test running here: https://circleci.com/gh/krummas/cassandra/86



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

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

[jira] [Commented] (CASSANDRA-13775) CircleCI tests fail because *stress-test* isn't a valid target

[Marcus Eriksson (JIRA)]

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

Marcus Eriksson commented on CASSANDRA-13775:
-

created CASSANDRA-13807 as another follow-up

> CircleCI tests fail because *stress-test* isn't a valid target
> --
>
> Key: CASSANDRA-13775
> URL: https://issues.apache.org/jira/browse/CASSANDRA-13775
> Project: Cassandra
>  Issue Type: Bug
>  Components: Build
>Reporter: Eduard Tudenhoefner
>Assignee: Eduard Tudenhoefner
>  Labels: CI
> Fix For: 2.2.11, 3.0.15, 2.1.19
>
>
> *stress-test* was added to CircleCI in CASSANDRA-13413 (2.1+) but the target 
> itself got introduced in CASSANDRA-11638 (3.10).



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

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

[jira] [Updated] (CASSANDRA-13807) CircleCI fix - only collect the xml file from containers where it exists

[Marcus Eriksson (JIRA)]

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

Marcus Eriksson updated CASSANDRA-13807:

Description: 
{color:red}colored text{color}Followup from CASSANDRA-13775 - my fix with {{ant 
eclipse-warnings}} obviously does not work since it doesn't generate any xml 
files

Push a new fix here: 
https://github.com/krummas/cassandra/commits/marcuse/fix_circle_3.0 which only 
collects the xml file from the first 3 containers
Test running here: https://circleci.com/gh/krummas/cassandra/86

  was:
Followup from CASSANDRA-13775 - my fix with {{ant eclipse-warnings}} obviously 
does not work since it doesn't generate any xml files

Push a new fix here: 
https://github.com/krummas/cassandra/commits/marcuse/fix_circle_3.0 which only 
collects the xml file from the first 3 containers
Test running here: https://circleci.com/gh/krummas/cassandra/86


> CircleCI fix - only collect the xml file from containers where it exists
> 
>
> Key: CASSANDRA-13807
> URL: https://issues.apache.org/jira/browse/CASSANDRA-13807
> Project: Cassandra
>  Issue Type: Bug
>Reporter: Marcus Eriksson
>
> {color:red}colored text{color}Followup from CASSANDRA-13775 - my fix with 
> {{ant eclipse-warnings}} obviously does not work since it doesn't generate 
> any xml files
> Push a new fix here: 
> https://github.com/krummas/cassandra/commits/marcuse/fix_circle_3.0 which 
> only collects the xml file from the first 3 containers
> Test running here: https://circleci.com/gh/krummas/cassandra/86



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

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

[jira] [Created] (CASSANDRA-13807) CircleCI fix - only collect the xml file from containers where it exists

[Marcus Eriksson (JIRA)]

Marcus Eriksson created CASSANDRA-13807:
---

 Summary: CircleCI fix - only collect the xml file from containers 
where it exists
 Key: CASSANDRA-13807
 URL: https://issues.apache.org/jira/browse/CASSANDRA-13807
 Project: Cassandra
  Issue Type: Bug
Reporter: Marcus Eriksson


Followup from CASSANDRA-13775 - my fix with {{ant eclipse-warnings}} obviously 
does not work since it doesn't generate any xml files

Push a new fix here: 
https://github.com/krummas/cassandra/commits/marcuse/fix_circle_3.0 which only 
collects the xml file from the first 3 containers
Test running here: https://circleci.com/gh/krummas/cassandra/86



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

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

[jira] [Assigned] (CASSANDRA-13801) CompactionManager sometimes wrongly determines that a background compaction is running for a particular table

[Dimitar Dimitrov (JIRA)]

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

Dimitar Dimitrov reassigned CASSANDRA-13801:


Assignee: Dimitar Dimitrov

> CompactionManager sometimes wrongly determines that a background compaction 
> is running for a particular table
> -
>
> Key: CASSANDRA-13801
> URL: https://issues.apache.org/jira/browse/CASSANDRA-13801
> Project: Cassandra
>  Issue Type: Bug
>  Components: Compaction
>Reporter: Dimitar Dimitrov
>Assignee: Dimitar Dimitrov
>
> Sometimes after writing different rows to a table, then doing a blocking 
> flush, if you alter the compaction strategy, then run background compaction 
> and wait for it to finish, {{CompactionManager}} may decide that there's an 
> ongoing compaction for that same table.
> This may happen even though logs don't indicate that to be the case 
> (compaction may still be running for system_schema tables).



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

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

[jira] [Comment Edited] (CASSANDRA-13797) RepairJob blocks on syncTasks

[Marcus Eriksson (JIRA)]

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

Marcus Eriksson edited comment on CASSANDRA-13797 at 8/25/17 2:34 PM:
--

+1 (if the tests pass, I restarted the dtests)


was (Author: krummas):
+1

> RepairJob blocks on syncTasks
> -
>
> Key: CASSANDRA-13797
> URL: https://issues.apache.org/jira/browse/CASSANDRA-13797
> Project: Cassandra
>  Issue Type: Bug
>Reporter: Blake Eggleston
>Assignee: Blake Eggleston
> Fix For: 4.0
>
>
> The thread running {{RepairJob}} blocks while it waits for the validations it 
> starts to complete ([see 
> here|https://github.com/bdeggleston/cassandra/blob/9fdec0a82851f5c35cd21d02e8c4da8fc685edb2/src/java/org/apache/cassandra/repair/RepairJob.java#L185]).
>  However, the downstream callbacks (ie: the post-repair cleanup stuff) aren't 
> waiting for {{RepairJob#run}} to return, they're waiting for a result to be 
> set on RepairJob the future, which happens after the sync tasks have 
> completed. This post repair cleanup stuff also immediately shuts down the 
> executor {{RepairJob#run}} is running in. So in noop repair sessions, where 
> there's nothing to stream, I'm seeing the callbacks sometimes fire before 
> {{RepairJob#run}} wakes up, and causing an {{InterruptedException}} is thrown.
> I'm pretty sure this can just be removed, but I'd like a second opinion. This 
> appears to just be a holdover from before repair coordination became async. I 
> thought it might be doing some throttling by blocking, but each repair 
> session gets it's own executor, and validation is  throttled by the fixed 
> size executors doing the actual work of validation, so I don't think we need 
> to keep this around.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

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

[jira] [Commented] (CASSANDRA-13797) RepairJob blocks on syncTasks

[Marcus Eriksson (JIRA)]

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

Marcus Eriksson commented on CASSANDRA-13797:
-

+1

> RepairJob blocks on syncTasks
> -
>
> Key: CASSANDRA-13797
> URL: https://issues.apache.org/jira/browse/CASSANDRA-13797
> Project: Cassandra
>  Issue Type: Bug
>Reporter: Blake Eggleston
>Assignee: Blake Eggleston
> Fix For: 4.0
>
>
> The thread running {{RepairJob}} blocks while it waits for the validations it 
> starts to complete ([see 
> here|https://github.com/bdeggleston/cassandra/blob/9fdec0a82851f5c35cd21d02e8c4da8fc685edb2/src/java/org/apache/cassandra/repair/RepairJob.java#L185]).
>  However, the downstream callbacks (ie: the post-repair cleanup stuff) aren't 
> waiting for {{RepairJob#run}} to return, they're waiting for a result to be 
> set on RepairJob the future, which happens after the sync tasks have 
> completed. This post repair cleanup stuff also immediately shuts down the 
> executor {{RepairJob#run}} is running in. So in noop repair sessions, where 
> there's nothing to stream, I'm seeing the callbacks sometimes fire before 
> {{RepairJob#run}} wakes up, and causing an {{InterruptedException}} is thrown.
> I'm pretty sure this can just be removed, but I'd like a second opinion. This 
> appears to just be a holdover from before repair coordination became async. I 
> thought it might be doing some throttling by blocking, but each repair 
> session gets it's own executor, and validation is  throttled by the fixed 
> size executors doing the actual work of validation, so I don't think we need 
> to keep this around.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

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

[jira] [Commented] (CASSANDRA-13798) Disallow filtering on non-primary-key base column for MV

[Benjamin Roth (JIRA)]

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

Benjamin Roth commented on CASSANDRA-13798:
---

Even if the current implementation has known issues, you cannot kill that (or 
any other) feature just like that. As [~JoshuaMcKenzie] mentioned, how do you 
treat existing installations + schemas?
If I was affected (I really have to check this) this would either force me to 
change my schema or to be blocked on updates. Both is not viable if the current 
solution works for my needs. For example I am not really affected if I have an 
insert-only payload or if my data does not expire.

What you of course can do: 
Spit our a warning in the logs on bootstrap if the schema is affected and on 
schema changes that are affected and refer to a JIRA. So one can decide to stay 
with it or to migrate the schema / model to be not affected any more.

My 2 cents.

> Disallow filtering on non-primary-key base column for MV
> 
>
> Key: CASSANDRA-13798
> URL: https://issues.apache.org/jira/browse/CASSANDRA-13798
> Project: Cassandra
>  Issue Type: Bug
>  Components: Materialized Views
>Reporter: ZhaoYang
>Assignee: ZhaoYang
>
> We should probably consider disallow filtering conditions on non-primary-key 
> base column for Materialized View which is introduced in CASSANDRA-10368.
> The main problem is that the liveness of view row is now depending on 
> multiple base columns (multiple filtered non-pk base column + base column 
> used in view pk) and this semantic could not be properly support without 
> drastic storage format changes. (SEE CASSANDRA-11500, 
> [background|https://issues.apache.org/jira/browse/CASSANDRA-11500?focusedCommentId=16119823=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-16119823])
> We should step back and re-consider the non-primary-key filtering feature 
> together with supporting multiple non-PK cols in MV clustering key in 
> CASSANDRA-10226.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

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

[jira] [Created] (CASSANDRA-13806) dtest failure: jmx_test.TestJMX.table_metric_mbeans_test

[Marcus Eriksson (JIRA)]

Marcus Eriksson created CASSANDRA-13806:
---

 Summary: dtest failure: jmx_test.TestJMX.table_metric_mbeans_test
 Key: CASSANDRA-13806
 URL: https://issues.apache.org/jira/browse/CASSANDRA-13806
 Project: Cassandra
  Issue Type: Bug
Reporter: Marcus Eriksson


http://cassci.datastax.com/job/trunk_dtest/1623/testReport/jmx_test/TestJMX/table_metric_mbeans_test



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

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

[jira] [Updated] (CASSANDRA-13804) dtest failure: paging_test.TestPagingWithModifiers.test_with_allow_filtering

[Marcus Eriksson (JIRA)]

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

Marcus Eriksson updated CASSANDRA-13804:

Description: 
http://cassci.datastax.com/job/cassandra-3.11_dtest/151/testReport/paging_test/TestPagingWithModifiers/test_with_allow_filtering
  (was: 
http://cassci.datastax.com/job/cassandra-3.11_dtest/156/testReport/topology_test/TestTopology/do_not_join_ring_test)

> dtest failure: paging_test.TestPagingWithModifiers.test_with_allow_filtering
> 
>
> Key: CASSANDRA-13804
> URL: https://issues.apache.org/jira/browse/CASSANDRA-13804
> Project: Cassandra
>  Issue Type: Bug
>Reporter: Marcus Eriksson
>  Labels: dtest
>
> http://cassci.datastax.com/job/cassandra-3.11_dtest/151/testReport/paging_test/TestPagingWithModifiers/test_with_allow_filtering



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

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

[jira] [Comment Edited] (CASSANDRA-13043) UnavailabeException caused by counter writes forwarded to leaders without complete cluster view

[Stefano Ortolani (JIRA)]

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

Stefano Ortolani edited comment on CASSANDRA-13043 at 8/25/17 1:16 PM:
---

Hi [~iamaleksey], I am having some difficulties reproducing it.

I am bootstrapping 3 nodes via cassandra-dtest, and updating the same counter 
3 times in three different phases.
During each phase I pick a node, stop it, and start it without waiting 
({{no_wait=True, wait_other_notice=False}}).
This while I keep inserting. Unfortunately no luck.

I have also been trying byteman as well, with the idea of slowing down how 
quickly the starting node becomes aware of the topology.
Unfortunately it seems I am either able to start the node without waiting, or 
submit a rule with byteman.
If I don't want wait for the node to start, the rule submission fails; while if 
I wait, the rule doesn't trigger because the node is already up and running.

Any suggestion how to proceed?


was (Author: ostefano):
Hi [~iamaleksey], I am having some difficulties reproducing it.

I am bootstrapping 3 nodes via cassandra-dtest, and updating the same counter 
3 times in three different phases.
During each phase I pick a node, stop it, and start it without waiting 
(`no_wait=True, wait_other_notice=False`).
This while I keep inserting. Unfortunately no luck.

I have also been trying byteman as well, with the idea of slowing down how 
quickly the starting node becomes aware of the topology.
Unfortunately it seems I am either able to start the node without waiting, or 
submit a rule with byteman.
If I don't want wait for the node to start, the rule submission fails; while if 
I wait, the rule doesn't trigger because the node is already up and running.

Any suggestion how to proceed?

> UnavailabeException caused by counter writes forwarded to leaders without 
> complete cluster view
> ---
>
> Key: CASSANDRA-13043
> URL: https://issues.apache.org/jira/browse/CASSANDRA-13043
> Project: Cassandra
>  Issue Type: Bug
>  Components: Core
> Environment: Debian
>Reporter: Catalin Alexandru Zamfir
>
> In version 3.9 of Cassandra, we get the following exceptions on the 
> system.log whenever booting an agent. They seem to grow in number with each 
> reboot. Any idea where they come from or what can we do about them? Note that 
> the cluster is healthy (has sufficient live nodes).
> {noformat}
> 2/14/2016 12:39:47 PMINFO  10:39:47 Updating topology for /10.136.64.120
> 12/14/2016 12:39:47 PMINFO  10:39:47 Updating topology for /10.136.64.120
> 12/14/2016 12:39:47 PMWARN  10:39:47 Uncaught exception on thread 
> Thread[CounterMutationStage-111,5,main]: {}
> 12/14/2016 12:39:47 PMorg.apache.cassandra.exceptions.UnavailableException: 
> Cannot achieve consistency level LOCAL_QUORUM
> 12/14/2016 12:39:47 PMat 
> org.apache.cassandra.db.ConsistencyLevel.assureSufficientLiveNodes(ConsistencyLevel.java:313)
>  ~[apache-cassandra-3.9.jar:3.9]
> 12/14/2016 12:39:47 PMat 
> org.apache.cassandra.service.AbstractWriteResponseHandler.assureSufficientLiveNodes(AbstractWriteResponseHandler.java:146)
>  ~[apache-cassandra-3.9.jar:3.9]
> 12/14/2016 12:39:47 PMat 
> org.apache.cassandra.service.StorageProxy.performWrite(StorageProxy.java:1054)
>  ~[apache-cassandra-3.9.jar:3.9]
> 12/14/2016 12:39:47 PMat 
> org.apache.cassandra.service.StorageProxy.applyCounterMutationOnLeader(StorageProxy.java:1450)
>  ~[apache-cassandra-3.9.jar:3.9]
> 12/14/2016 12:39:47 PMat 
> org.apache.cassandra.db.CounterMutationVerbHandler.doVerb(CounterMutationVerbHandler.java:48)
>  ~[apache-cassandra-3.9.jar:3.9]
> 12/14/2016 12:39:47 PMat 
> org.apache.cassandra.net.MessageDeliveryTask.run(MessageDeliveryTask.java:64) 
> ~[apache-cassandra-3.9.jar:3.9]
> 12/14/2016 12:39:47 PMat 
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) 
> ~[na:1.8.0_111]
> 12/14/2016 12:39:47 PMat 
> org.apache.cassandra.concurrent.AbstractLocalAwareExecutorService$FutureTask.run(AbstractLocalAwareExecutorService.java:164)
>  ~[apache-cassandra-3.9.jar:3.9]
> 12/14/2016 12:39:47 PMat 
> org.apache.cassandra.concurrent.AbstractLocalAwareExecutorService$LocalSessionFutureTask.run(AbstractLocalAwareExecutorService.java:136)
>  [apache-cassandra-3.9.jar:3.9]
> 12/14/2016 12:39:47 PMat 
> org.apache.cassandra.concurrent.SEPWorker.run(SEPWorker.java:109) 
> [apache-cassandra-3.9.jar:3.9]
> 12/14/2016 12:39:47 PMat java.lang.Thread.run(Thread.java:745) 
> [na:1.8.0_111]
> 12/14/2016 12:39:47 PMWARN  10:39:47 Uncaught exception on thread 
> Thread[CounterMutationStage-118,5,main]: {}
> 12/14/2016 12:39:47 

[jira] [Created] (CASSANDRA-13805) dtest failure: repair_tests.repair_test.TestRepair.simple_parallel_repair_test

[Marcus Eriksson (JIRA)]

Marcus Eriksson created CASSANDRA-13805:
---

 Summary: dtest failure: 
repair_tests.repair_test.TestRepair.simple_parallel_repair_test
 Key: CASSANDRA-13805
 URL: https://issues.apache.org/jira/browse/CASSANDRA-13805
 Project: Cassandra
  Issue Type: Bug
Reporter: Marcus Eriksson


http://cassci.datastax.com/job/trunk_dtest/1621/testReport/repair_tests/repair_test/TestRepair/simple_parallel_repair_test



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

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

[jira] [Commented] (CASSANDRA-13043) UnavailabeException caused by counter writes forwarded to leaders without complete cluster view

[Stefano Ortolani (JIRA)]

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

Stefano Ortolani commented on CASSANDRA-13043:
--

Hi [~iamaleksey], I am having some difficulties reproducing it.

I am bootstrapping 3 nodes via cassandra-dtest, and updating the same counter 
3 times in three different phases.
During each phase I pick a node, stop it, and start it without waiting 
(`no_wait=True, wait_other_notice=False`).
This while I keep inserting. Unfortunately no luck.

I have also been trying byteman as well, with the idea of slowing down how 
quickly the starting node becomes aware of the topology.
Unfortunately it seems I am either able to start the node without waiting, or 
submit a rule with byteman.
If I don't want wait for the node to start, the rule submission fails; while if 
I wait, the rule doesn't trigger because the node is already up and running.

Any suggestion how to proceed?

> UnavailabeException caused by counter writes forwarded to leaders without 
> complete cluster view
> ---
>
> Key: CASSANDRA-13043
> URL: https://issues.apache.org/jira/browse/CASSANDRA-13043
> Project: Cassandra
>  Issue Type: Bug
>  Components: Core
> Environment: Debian
>Reporter: Catalin Alexandru Zamfir
>
> In version 3.9 of Cassandra, we get the following exceptions on the 
> system.log whenever booting an agent. They seem to grow in number with each 
> reboot. Any idea where they come from or what can we do about them? Note that 
> the cluster is healthy (has sufficient live nodes).
> {noformat}
> 2/14/2016 12:39:47 PMINFO  10:39:47 Updating topology for /10.136.64.120
> 12/14/2016 12:39:47 PMINFO  10:39:47 Updating topology for /10.136.64.120
> 12/14/2016 12:39:47 PMWARN  10:39:47 Uncaught exception on thread 
> Thread[CounterMutationStage-111,5,main]: {}
> 12/14/2016 12:39:47 PMorg.apache.cassandra.exceptions.UnavailableException: 
> Cannot achieve consistency level LOCAL_QUORUM
> 12/14/2016 12:39:47 PMat 
> org.apache.cassandra.db.ConsistencyLevel.assureSufficientLiveNodes(ConsistencyLevel.java:313)
>  ~[apache-cassandra-3.9.jar:3.9]
> 12/14/2016 12:39:47 PMat 
> org.apache.cassandra.service.AbstractWriteResponseHandler.assureSufficientLiveNodes(AbstractWriteResponseHandler.java:146)
>  ~[apache-cassandra-3.9.jar:3.9]
> 12/14/2016 12:39:47 PMat 
> org.apache.cassandra.service.StorageProxy.performWrite(StorageProxy.java:1054)
>  ~[apache-cassandra-3.9.jar:3.9]
> 12/14/2016 12:39:47 PMat 
> org.apache.cassandra.service.StorageProxy.applyCounterMutationOnLeader(StorageProxy.java:1450)
>  ~[apache-cassandra-3.9.jar:3.9]
> 12/14/2016 12:39:47 PMat 
> org.apache.cassandra.db.CounterMutationVerbHandler.doVerb(CounterMutationVerbHandler.java:48)
>  ~[apache-cassandra-3.9.jar:3.9]
> 12/14/2016 12:39:47 PMat 
> org.apache.cassandra.net.MessageDeliveryTask.run(MessageDeliveryTask.java:64) 
> ~[apache-cassandra-3.9.jar:3.9]
> 12/14/2016 12:39:47 PMat 
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) 
> ~[na:1.8.0_111]
> 12/14/2016 12:39:47 PMat 
> org.apache.cassandra.concurrent.AbstractLocalAwareExecutorService$FutureTask.run(AbstractLocalAwareExecutorService.java:164)
>  ~[apache-cassandra-3.9.jar:3.9]
> 12/14/2016 12:39:47 PMat 
> org.apache.cassandra.concurrent.AbstractLocalAwareExecutorService$LocalSessionFutureTask.run(AbstractLocalAwareExecutorService.java:136)
>  [apache-cassandra-3.9.jar:3.9]
> 12/14/2016 12:39:47 PMat 
> org.apache.cassandra.concurrent.SEPWorker.run(SEPWorker.java:109) 
> [apache-cassandra-3.9.jar:3.9]
> 12/14/2016 12:39:47 PMat java.lang.Thread.run(Thread.java:745) 
> [na:1.8.0_111]
> 12/14/2016 12:39:47 PMWARN  10:39:47 Uncaught exception on thread 
> Thread[CounterMutationStage-118,5,main]: {}
> 12/14/2016 12:39:47 PMorg.apache.cassandra.exceptions.UnavailableException: 
> Cannot achieve consistency level LOCAL_QUORUM
> 12/14/2016 12:39:47 PMat 
> org.apache.cassandra.db.ConsistencyLevel.assureSufficientLiveNodes(ConsistencyLevel.java:313)
>  ~[apache-cassandra-3.9.jar:3.9]
> 12/14/2016 12:39:47 PMat 
> org.apache.cassandra.service.AbstractWriteResponseHandler.assureSufficientLiveNodes(AbstractWriteResponseHandler.java:146)
>  ~[apache-cassandra-3.9.jar:3.9]
> 12/14/2016 12:39:47 PMat 
> org.apache.cassandra.service.StorageProxy.performWrite(StorageProxy.java:1054)
>  ~[apache-cassandra-3.9.jar:3.9]
> 12/14/2016 12:39:47 PMat 
> org.apache.cassandra.service.StorageProxy.applyCounterMutationOnLeader(StorageProxy.java:1450)
>  ~[apache-cassandra-3.9.jar:3.9]
> 12/14/2016 12:39:47 PMat 
> 

[jira] [Commented] (CASSANDRA-13752) Corrupted SSTables created in 3.11

[JIRA]

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

Hannu Kröger commented on CASSANDRA-13752:
--

[~jjirsa] Could downgrade to 3.10 help as a quick fix?

> Corrupted SSTables created in 3.11
> --
>
> Key: CASSANDRA-13752
> URL: https://issues.apache.org/jira/browse/CASSANDRA-13752
> Project: Cassandra
>  Issue Type: Bug
>Reporter: Hannu Kröger
>Assignee: Hannu Kröger
>Priority: Blocker
>
> We have discovered issues with corrupted SSTables. 
> {code}
> ERROR [SSTableBatchOpen:22] 2017-08-03 20:19:53,195 SSTableReader.java:577 - 
> Cannot read sstable 
> /cassandra/data/mykeyspace/mytable-7a4992800d5611e7b782cb90016f2d17/mc-35556-big=[Data.db,
>  Statistics.db, Summary.db, Digest.crc32, CompressionInfo.db, TOC.txt, 
> Index.db, Filter.db]; other IO error, skipping table
> java.io.EOFException: EOF after 1898 bytes out of 21093
> at 
> org.apache.cassandra.io.util.RebufferingInputStream.readFully(RebufferingInputStream.java:68)
>  ~[apache-cassandra-3.11.0.jar:3.11.0]
> at 
> org.apache.cassandra.io.util.RebufferingInputStream.readFully(RebufferingInputStream.java:60)
>  ~[apache-cassandra-3.11.0.jar:3.11.0]
> at 
> org.apache.cassandra.utils.ByteBufferUtil.read(ByteBufferUtil.java:402) 
> ~[apache-cassandra-3.11.0.jar:3.11.0]
> at 
> org.apache.cassandra.utils.ByteBufferUtil.readWithShortLength(ByteBufferUtil.java:377)
>  ~[apache-cassandra-3.11.0.jar:3.11.0]
> at 
> org.apache.cassandra.io.sstable.metadata.StatsMetadata$StatsMetadataSerializer.deserialize(StatsMetadata.java:325)
>  ~[apache-cassandra-3.11.0.jar:3.11.0]
> at 
> org.apache.cassandra.io.sstable.metadata.StatsMetadata$StatsMetadataSerializer.deserialize(StatsMetadata.java:231)
>  ~[apache-cassandra-3.11.0.jar:3.11.0]
> at 
> org.apache.cassandra.io.sstable.metadata.MetadataSerializer.deserialize(MetadataSerializer.java:122)
>  ~[apache-cassandra-3.11.0.jar:3.11.0]
> at 
> org.apache.cassandra.io.sstable.metadata.MetadataSerializer.deserialize(MetadataSerializer.java:93)
>  ~[apache-cassandra-3.11.0.jar:3.11.0]
> at 
> org.apache.cassandra.io.sstable.format.SSTableReader.open(SSTableReader.java:488)
>  ~[apache-cassandra-3.11.0.jar:3.11.0]
> at 
> org.apache.cassandra.io.sstable.format.SSTableReader.open(SSTableReader.java:396)
>  ~[apache-cassandra-3.11.0.jar:3.11.0]
> at 
> org.apache.cassandra.io.sstable.format.SSTableReader$5.run(SSTableReader.java:561)
>  ~[apache-cassandra-3.11.0.jar:3.11.0]
> at 
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) 
> [na:1.8.0_111]
> at java.util.concurrent.FutureTask.run(FutureTask.java:266) 
> [na:1.8.0_111]
> at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
>  [na:1.8.0_111]
> at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
>  [na:1.8.0_111]
> at 
> org.apache.cassandra.concurrent.NamedThreadFactory.lambda$threadLocalDeallocator$0(NamedThreadFactory.java:81)
>  [apache-cassandra-3.11.0.jar:3.11.0]
> {code}
> Files look like this:
> {code}
> -rw-r--r--. 1 cassandra cassandra 3899251 Aug  7 08:37 
> mc-6166-big-CompressionInfo.db
> -rw-r--r--. 1 cassandra cassandra 16874421686 Aug  7 08:37 mc-6166-big-Data.db
> -rw-r--r--. 1 cassandra cassandra  10 Aug  7 08:37 
> mc-6166-big-Digest.crc32
> -rw-r--r--. 1 cassandra cassandra 2930904 Aug  7 08:37 
> mc-6166-big-Filter.db
> -rw-r--r--. 1 cassandra cassandra   75880 Aug  7 08:37 
> mc-6166-big-Index.db
> -rw-r--r--. 1 cassandra cassandra   13762 Aug  7 08:37 
> mc-6166-big-Statistics.db
> -rw-r--r--. 1 cassandra cassandra  882008 Aug  7 08:37 
> mc-6166-big-Summary.db
> -rw-r--r--. 1 cassandra cassandra  92 Aug  7 08:37 mc-6166-big-TOC.txt
> {code}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

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

[jira] [Created] (CASSANDRA-13804) dtest failure: paging_test.TestPagingWithModifiers.test_with_allow_filtering

[Marcus Eriksson (JIRA)]

Marcus Eriksson created CASSANDRA-13804:
---

 Summary: dtest failure: 
paging_test.TestPagingWithModifiers.test_with_allow_filtering
 Key: CASSANDRA-13804
 URL: https://issues.apache.org/jira/browse/CASSANDRA-13804
 Project: Cassandra
  Issue Type: Bug
Reporter: Marcus Eriksson


http://cassci.datastax.com/job/cassandra-3.11_dtest/156/testReport/topology_test/TestTopology/do_not_join_ring_test



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

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

[jira] [Created] (CASSANDRA-13803) dtest failure: compaction_test.TestCompaction_with_LeveledCompactionStrategy.sstable_deletion_test

[Marcus Eriksson (JIRA)]

Marcus Eriksson created CASSANDRA-13803:
---

 Summary: dtest failure: 
compaction_test.TestCompaction_with_LeveledCompactionStrategy.sstable_deletion_test
 Key: CASSANDRA-13803
 URL: https://issues.apache.org/jira/browse/CASSANDRA-13803
 Project: Cassandra
  Issue Type: Bug
Reporter: Marcus Eriksson


http://cassci.datastax.com/job/cassandra-3.0_dtest/977/testReport/compaction_test/TestCompaction_with_LeveledCompactionStrategy/sstable_deletion_test



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

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

cassandra-dtest git commit: Bump CCM version to 2.8.1

[mshuler]

Repository: cassandra-dtest
Updated Branches:
  refs/heads/master da6ad8317 -> 6d5ee3792


Bump CCM version to 2.8.1


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

Branch: refs/heads/master
Commit: 6d5ee3792dd226b0eea5afaadf8489b150ea4b18
Parents: da6ad83
Author: Michael Shuler 
Authored: Fri Aug 25 07:56:20 2017 -0500
Committer: Michael Shuler 
Committed: Fri Aug 25 07:56:20 2017 -0500

--
 requirements.txt | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
--


http://git-wip-us.apache.org/repos/asf/cassandra-dtest/blob/6d5ee379/requirements.txt
--
diff --git a/requirements.txt b/requirements.txt
index 9be7094..058ea38 100644
--- a/requirements.txt
+++ b/requirements.txt
@@ -4,7 +4,7 @@
 futures
 six
 -e 
git+https://github.com/datastax/python-driver.git@cassandra-test#egg=cassandra-driver
-ccm==2.6.3
+ccm==2.8.1
 cql
 decorator
 docopt


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

[jira] [Commented] (CASSANDRA-13798) Disallow filtering on non-primary-key base column for MV

[Joshua McKenzie (JIRA)]

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

Joshua McKenzie commented on CASSANDRA-13798:
-

bq. The feature was added in 3.10
bq. revert it in 3.x/trunk, before more users start using it.
What, if anything, do we want to do for the theoretical user on 3.10/3.11 
that's created an MV w/this schema?

> Disallow filtering on non-primary-key base column for MV
> 
>
> Key: CASSANDRA-13798
> URL: https://issues.apache.org/jira/browse/CASSANDRA-13798
> Project: Cassandra
>  Issue Type: Bug
>  Components: Materialized Views
>Reporter: ZhaoYang
>Assignee: ZhaoYang
>
> We should probably consider disallow filtering conditions on non-primary-key 
> base column for Materialized View which is introduced in CASSANDRA-10368.
> The main problem is that the liveness of view row is now depending on 
> multiple base columns (multiple filtered non-pk base column + base column 
> used in view pk) and this semantic could not be properly support without 
> drastic storage format changes. (SEE CASSANDRA-11500, 
> [background|https://issues.apache.org/jira/browse/CASSANDRA-11500?focusedCommentId=16119823=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-16119823])
> We should step back and re-consider the non-primary-key filtering feature 
> together with supporting multiple non-PK cols in MV clustering key in 
> CASSANDRA-10226.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

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

[jira] [Commented] (CASSANDRA-13780) ADD Node streaming throughput performance

[Kevin Rivait (JIRA)]

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

Kevin Rivait commented on CASSANDRA-13780:
--

netcat tests on our dev environment between 2 of our cassandra nodes shows 9600 
Mb/s throughput

our test approach
create a 4 node cassandra cluster
one Keyspace with replication 2
one table 
load a few million rows,  load on each node ~ 5GB
add a fifth node
this test was repeated 3 times

TEST1- with streamingthroughput left with the default settings (200 Mb/s) - we 
observe 26 Mb/s from the sending nodes
TEST2 - throttle streamingthroughput to 10 Mb/s all nodes - we observe 10 Mb/s 
from the sending nodes
TEST3 - set streamingthroughput to 50 Mb/s all nodes - we observe 26 Mb/s from 
the sending nodes
Ideally we would like to utilize 10% of our bandwidth for streaming but cannot 
even come close to the default 200 Mb/s (seems capped at 26 Mb/s)

> ADD Node streaming throughput performance
> -
>
> Key: CASSANDRA-13780
> URL: https://issues.apache.org/jira/browse/CASSANDRA-13780
> Project: Cassandra
>  Issue Type: Improvement
>  Components: Core
> Environment: Linux 2.6.32-696.3.2.el6.x86_64 #1 SMP Mon Jun 19 
> 11:55:55 PDT 2017 x86_64 x86_64 x86_64 GNU/Linux
> Architecture:  x86_64
> CPU op-mode(s):32-bit, 64-bit
> Byte Order:Little Endian
> CPU(s):40
> On-line CPU(s) list:   0-39
> Thread(s) per core:2
> Core(s) per socket:10
> Socket(s): 2
> NUMA node(s):  2
> Vendor ID: GenuineIntel
> CPU family:6
> Model: 79
> Model name:Intel(R) Xeon(R) CPU E5-2630 v4 @ 2.20GHz
> Stepping:  1
> CPU MHz:   2199.869
> BogoMIPS:  4399.36
> Virtualization:VT-x
> L1d cache: 32K
> L1i cache: 32K
> L2 cache:  256K
> L3 cache:  25600K
> NUMA node0 CPU(s): 0,2,4,6,8,10,12,14,16,18,20,22,24,26,28,30,32,34,36,38
> NUMA node1 CPU(s): 1,3,5,7,9,11,13,15,17,19,21,23,25,27,29,31,33,35,37,39
>  total   used   free sharedbuffers cached
> Mem:  252G   217G34G   708K   308M   149G
> -/+ buffers/cache:67G   185G
> Swap:  16G 0B16G
>Reporter: Kevin Rivait
>Priority: Blocker
> Fix For: 3.0.9
>
>
> Problem: Adding a new node to a large cluster runs at least 1000x slower than 
> what the network and node hardware capacity can support, taking several days 
> per new node.  Adjusting stream throughput and other YAML parameters seems to 
> have no effect on performance.  Essentially, it appears that Cassandra has an 
> architecture scalability growth problem when adding new nodes to a moderate 
> to high data ingestion cluster because Cassandra cannot add new node capacity 
> fast enough to keep up with increasing data ingestion volumes and growth.
> Initial Configuration: 
> Running 3.0.9 and have implemented TWCS on one of our largest table.
> Largest table partitioned on (ID, MM)  using 1 day buckets with a TTL of 
> 60 days.
> Next release will change partitioning to (ID, MMDD) so that partitions 
> are aligned with daily TWCS buckets.
> Each node is currently creating roughly a 30GB SSTable per day.
> TWCS working as expected,  daily SSTables are dropping off daily after 70 
> days ( 60 + 10 day grace)
> Current deployment is a 28 node 2 datacenter cluster, 14 nodes in each DC , 
> replication factor 3
> Data directories are backed with 4 - 2TB SSDs on each node  and a 1 800GB SSD 
> for commit logs.
> Requirement is to double cluster size, capacity, and ingestion volume within 
> a few weeks.
> Observed Behavior:
> 1. streaming throughput during add node – we observed maximum 6 Mb/s 
> streaming from each of the 14 nodes on a 20Gb/s switched network, taking at 
> least 106 hours for each node to join cluster and each node is only about 2.2 
> TB is size.
> 2. compaction on the newly added node - compaction has fallen behind, with 
> anywhere from 4,000 to 10,000 SSTables at any given time.  It took 3 weeks 
> for compaction to finish on each newly added node.   Increasing number of 
> compaction threads to match number of CPU (40)  and increasing compaction 
> throughput to 32MB/s seemed to be the sweet spot. 
> 3. TWCS buckets on new node, data streamed to this node over 4 1/2 days.  
> Compaction correctly placed the data in daily files, but the problem is the 
> file dates reflect when compaction created the file and not the date of the 
> last record written in the TWCS bucket, which will cause the files to remain 
> around much longer than necessary.  
> Two Questions:
> 1. What can be done to substantially improve 

[jira] [Resolved] (CASSANDRA-12275) dtest failure in offline_tools_test.TestOfflineTools.sstableofflinerelevel_test

[Marcus Eriksson (JIRA)]

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

Marcus Eriksson resolved CASSANDRA-12275.
-
Resolution: Duplicate

> dtest failure in 
> offline_tools_test.TestOfflineTools.sstableofflinerelevel_test
> ---
>
> Key: CASSANDRA-12275
> URL: https://issues.apache.org/jira/browse/CASSANDRA-12275
> Project: Cassandra
>  Issue Type: Test
>Reporter: Craig Kodman
>Assignee: DS Test Eng
>  Labels: dtest, windows
> Attachments: node1_debug.log, node1_gc.log, node1.log
>
>
> example failure:
> http://cassci.datastax.com/job/cassandra-2.2_dtest_win32/271/testReport/offline_tools_test/TestOfflineTools/sstableofflinerelevel_test



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

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

[jira] [Resolved] (CASSANDRA-12797) dtest failure in offline_tools_test.TestOfflineTools.sstableofflinerelevel_test

[Marcus Eriksson (JIRA)]

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

Marcus Eriksson resolved CASSANDRA-12797.
-
Resolution: Duplicate

> dtest failure in 
> offline_tools_test.TestOfflineTools.sstableofflinerelevel_test
> ---
>
> Key: CASSANDRA-12797
> URL: https://issues.apache.org/jira/browse/CASSANDRA-12797
> Project: Cassandra
>  Issue Type: Test
>Reporter: Sean McCarthy
>Assignee: DS Test Eng
> Attachments: node1_debug.log, node1_gc.log, node1.log
>
>
> example failure:
> http://cassci.datastax.com/job/cassandra-3.0_dtest/832/testReport/offline_tools_test/TestOfflineTools/sstableofflinerelevel_test/
> {code}
> Error Message
> 'L0=1' not found in 'New leveling: \nL0=0\nL1 10\n'
> {code}
> {code}
> Stacktrace
>   File "/usr/lib/python2.7/unittest/case.py", line 329, in run
> testMethod()
>   File "/home/automaton/cassandra-dtest/offline_tools_test.py", line 162, in 
> sstableofflinerelevel_test
> self.assertIn("L0=1", output)
>   File "/usr/lib/python2.7/unittest/case.py", line 803, in assertIn
> self.fail(self._formatMessage(msg, standardMsg))
>   File "/usr/lib/python2.7/unittest/case.py", line 410, in fail
> raise self.failureException(msg)
> {code}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

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

[jira] [Commented] (CASSANDRA-13802) dtest failure: counter_tests.TestCounters.test_13691

[Aleksey Yeschenko (JIRA)]

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

Aleksey Yeschenko commented on CASSANDRA-13802:
---

I think it's failing because the boxes are missing the latest ccmlib. Need 
[this 
fix|https://github.com/pcmanus/ccm/commit/a0f1a8625b6a540e6a36be4f8305b76160712ceb]
 to work properly.

> dtest failure: counter_tests.TestCounters.test_13691
> 
>
> Key: CASSANDRA-13802
> URL: https://issues.apache.org/jira/browse/CASSANDRA-13802
> Project: Cassandra
>  Issue Type: Bug
>Reporter: Marcus Eriksson
>  Labels: dtest
>
> http://cassci.datastax.com/job/cassandra-3.11_dtest/159/testReport/counter_tests/TestCounters/test_13691/
> http://cassci.datastax.com/job/cassandra-3.11_dtest/158/testReport/counter_tests/TestCounters/test_13691/
> http://cassci.datastax.com/job/cassandra-3.11_dtest/157/testReport/counter_tests/TestCounters/test_13691/



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

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

[jira] [Created] (CASSANDRA-13802) dtest failure: counter_tests.TestCounters.test_13691

[Marcus Eriksson (JIRA)]

Marcus Eriksson created CASSANDRA-13802:
---

 Summary: dtest failure: counter_tests.TestCounters.test_13691
 Key: CASSANDRA-13802
 URL: https://issues.apache.org/jira/browse/CASSANDRA-13802
 Project: Cassandra
  Issue Type: Bug
Reporter: Marcus Eriksson


http://cassci.datastax.com/job/cassandra-3.11_dtest/159/testReport/counter_tests/TestCounters/test_13691/
http://cassci.datastax.com/job/cassandra-3.11_dtest/158/testReport/counter_tests/TestCounters/test_13691/
http://cassci.datastax.com/job/cassandra-3.11_dtest/157/testReport/counter_tests/TestCounters/test_13691/



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

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

[jira] [Assigned] (CASSANDRA-13800) dtest failure: native_transport_ssl_test.NativeTransportSSL.connect_to_ssl_test

[Jason Brown (JIRA)]

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

Jason Brown reassigned CASSANDRA-13800:
---

Assignee: Jason Brown

> dtest failure: 
> native_transport_ssl_test.NativeTransportSSL.connect_to_ssl_test 
> 
>
> Key: CASSANDRA-13800
> URL: https://issues.apache.org/jira/browse/CASSANDRA-13800
> Project: Cassandra
>  Issue Type: Bug
>Reporter: Marcus Eriksson
>Assignee: Jason Brown
>  Labels: dtest
>
> http://cassci.datastax.com/job/trunk_dtest/1623/testReport/native_transport_ssl_test/NativeTransportSSL/connect_to_ssl_test
> http://cassci.datastax.com/job/trunk_dtest/1619/testReport/native_transport_ssl_test/NativeTransportSSL/connect_to_ssl_test
> http://cassci.datastax.com/job/trunk_dtest/1612/testReport/native_transport_ssl_test/NativeTransportSSL/connect_to_ssl_test



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

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

[jira] [Commented] (CASSANDRA-13800) dtest failure: native_transport_ssl_test.NativeTransportSSL.connect_to_ssl_test

[Jason Brown (JIRA)]

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

Jason Brown commented on CASSANDRA-13800:
-

not caused by CASSANDRA-8457 (whew), but I'll take a look at this.

> dtest failure: 
> native_transport_ssl_test.NativeTransportSSL.connect_to_ssl_test 
> 
>
> Key: CASSANDRA-13800
> URL: https://issues.apache.org/jira/browse/CASSANDRA-13800
> Project: Cassandra
>  Issue Type: Bug
>Reporter: Marcus Eriksson
>  Labels: dtest
>
> http://cassci.datastax.com/job/trunk_dtest/1623/testReport/native_transport_ssl_test/NativeTransportSSL/connect_to_ssl_test
> http://cassci.datastax.com/job/trunk_dtest/1619/testReport/native_transport_ssl_test/NativeTransportSSL/connect_to_ssl_test
> http://cassci.datastax.com/job/trunk_dtest/1612/testReport/native_transport_ssl_test/NativeTransportSSL/connect_to_ssl_test



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

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

[jira] [Created] (CASSANDRA-13801) CompactionManager sometimes wrongly determines that a background compaction is running for a particular table

[Dimitar Dimitrov (JIRA)]

Dimitar Dimitrov created CASSANDRA-13801:


 Summary: CompactionManager sometimes wrongly determines that a 
background compaction is running for a particular table
 Key: CASSANDRA-13801
 URL: https://issues.apache.org/jira/browse/CASSANDRA-13801
 Project: Cassandra
  Issue Type: Bug
  Components: Compaction
Reporter: Dimitar Dimitrov


Sometimes after writing different rows to a table, then doing a blocking flush, 
if you alter the compaction strategy, then run background compaction and wait 
for it to finish, {{CompactionManager}} may decide that there's an ongoing 
compaction for that same table.
This may happen even though logs don't indicate that to be the case (compaction 
may still be running for system_schema tables).



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

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

[jira] [Created] (CASSANDRA-13800) dtest failure: native_transport_ssl_test.NativeTransportSSL.connect_to_ssl_test

[Marcus Eriksson (JIRA)]

Marcus Eriksson created CASSANDRA-13800:
---

 Summary: dtest failure: 
native_transport_ssl_test.NativeTransportSSL.connect_to_ssl_test 
 Key: CASSANDRA-13800
 URL: https://issues.apache.org/jira/browse/CASSANDRA-13800
 Project: Cassandra
  Issue Type: Bug
Reporter: Marcus Eriksson


http://cassci.datastax.com/job/trunk_dtest/1623/testReport/native_transport_ssl_test/NativeTransportSSL/connect_to_ssl_test
http://cassci.datastax.com/job/trunk_dtest/1619/testReport/native_transport_ssl_test/NativeTransportSSL/connect_to_ssl_test
http://cassci.datastax.com/job/trunk_dtest/1612/testReport/native_transport_ssl_test/NativeTransportSSL/connect_to_ssl_test



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

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

[jira] [Comment Edited] (CASSANDRA-13798) Disallow filtering on non-primary-key base column for MV

[ZhaoYang (JIRA)]

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

ZhaoYang edited comment on CASSANDRA-13798 at 8/25/17 11:34 AM:


| [trunk|https://github.com/jasonstack/cassandra/commits/CASSANDRA-13798-trunk] 
|
| [3.11|https://github.com/jasonstack/cassandra/commits/CASSANDRA-13798-3.11] |
| [dtest|https://github.com/riptano/cassandra-dtest/commits/CASSANDRA-13798] |

The patch is to revert supporting non-pk base column filtering on MV on 3.11 & 
trunk.  The feature was added in 3.10 and the consequence may have been 
overlooked. It's better to revert it in 3.x/trunk, before more users start 
using it.

At the same time, I will work on a proper design (eg. multi-timestamp approach 
discussed in CASSANDRA-11500 and CASSANDRA-10226) for non-pk base column 
filtering and multiple non-pk base column in view pk.

[~pauloricardomg] [~brstgt] [~KurtG] what do you think?


was (Author: jasonstack):
| [trunk|https://github.com/jasonstack/cassandra/commits/CASSANDRA-13798-trunk] 
|
| [3.11|https://github.com/jasonstack/cassandra/commits/CASSANDRA-13798-3.11] |
| [dtest|https://github.com/riptano/cassandra-dtest/commits/CASSANDRA-13798] |

The patch is to revert supporting non-pk base column filtering on MV on 3.11 & 
trunk.  The feature was added in 3.10 and the consequence may have been 
overlooked. It's better to revert it in 3.x/trunk, before more users start 
using it.

At the same time, I will work on a proper design (eg. multi-timestamp approach 
discussed in CASSANDRA-11500 and CASSANDRA-10226) for non-pk base column 
filtering and multiple non-pk base column in view pk.

> Disallow filtering on non-primary-key base column for MV
> 
>
> Key: CASSANDRA-13798
> URL: https://issues.apache.org/jira/browse/CASSANDRA-13798
> Project: Cassandra
>  Issue Type: Bug
>  Components: Materialized Views
>Reporter: ZhaoYang
>Assignee: ZhaoYang
>
> We should probably consider disallow filtering conditions on non-primary-key 
> base column for Materialized View which is introduced in CASSANDRA-10368.
> The main problem is that the liveness of view row is now depending on 
> multiple base columns (multiple filtered non-pk base column + base column 
> used in view pk) and this semantic could not be properly support without 
> drastic storage format changes. (SEE CASSANDRA-11500, 
> [background|https://issues.apache.org/jira/browse/CASSANDRA-11500?focusedCommentId=16119823=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-16119823])
> We should step back and re-consider the non-primary-key filtering feature 
> together with supporting multiple non-PK cols in MV clustering key in 
> CASSANDRA-10226.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

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

[jira] [Commented] (CASSANDRA-11469) dtest failure in upgrade_internal_auth_test.TestAuthUpgrade.upgrade_to_22_test

[Marcus Eriksson (JIRA)]

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

Marcus Eriksson commented on CASSANDRA-11469:
-

Most of the recent failures of this (on trunk) seem to be due to github being 
down:
http://cassci.datastax.com/job/trunk_dtest/1611/testReport/upgrade_internal_auth_test/TestAuthUpgrade/upgrade_to_22_test/

> dtest failure in upgrade_internal_auth_test.TestAuthUpgrade.upgrade_to_22_test
> --
>
> Key: CASSANDRA-11469
> URL: https://issues.apache.org/jira/browse/CASSANDRA-11469
> Project: Cassandra
>  Issue Type: Bug
>Reporter: Philip Thompson
>Assignee: Sam Tunnicliffe
>  Labels: dtest
> Fix For: 2.2.x
>
>
> Upgrading from 2.1 to 2.2, we are seeing failures in 
> upgrade_internal_auth_test.py. I have seen a variety of stack traces, but the 
> most common is:
> {code}
> java.lang.IllegalArgumentException: Unknown keyspace/cf pair 
> (system_auth.credentials)
>   at 
> org.apache.cassandra.db.Keyspace.getColumnFamilyStore(Keyspace.java:169) 
> ~[main/:na]
>   at 
> org.apache.cassandra.service.StorageProxy.readRegular(StorageProxy.java:1383) 
> ~[main/:na]
>   at 
> org.apache.cassandra.service.StorageProxy.read(StorageProxy.java:1277) 
> ~[main/:na]
>   at 
> org.apache.cassandra.cql3.statements.SelectStatement.execute(SelectStatement.java:221)
>  ~[main/:na]
>   at 
> org.apache.cassandra.cql3.statements.SelectStatement.execute(SelectStatement.java:176)
>  ~[main/:na]
>   at 
> org.apache.cassandra.auth.PasswordAuthenticator.doAuthenticate(PasswordAuthenticator.java:143)
>  ~[main/:na]
>   at 
> org.apache.cassandra.auth.PasswordAuthenticator.authenticate(PasswordAuthenticator.java:85)
>  ~[main/:na]
>   at 
> org.apache.cassandra.auth.PasswordAuthenticator.access$100(PasswordAuthenticator.java:53)
>  ~[main/:na]
>   at 
> org.apache.cassandra.auth.PasswordAuthenticator$PlainTextSaslAuthenticator.getAuthenticatedUser(PasswordAuthenticator.java:181)
>  ~[main/:na]
>   at 
> org.apache.cassandra.transport.messages.AuthResponse.execute(AuthResponse.java:78)
>  ~[main/:na]
>   at 
> org.apache.cassandra.transport.Message$Dispatcher.channelRead0(Message.java:507)
>  [main/:na]
>   at 
> org.apache.cassandra.transport.Message$Dispatcher.channelRead0(Message.java:401)
>  [main/:na]
>   at 
> io.netty.channel.SimpleChannelInboundHandler.channelRead(SimpleChannelInboundHandler.java:105)
>  [netty-all-4.0.23.Final.jar:4.0.23.Final]
>   at 
> io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:333)
>  [netty-all-4.0.23.Final.jar:4.0.23.Final]
>   at 
> io.netty.channel.AbstractChannelHandlerContext.access$700(AbstractChannelHandlerContext.java:32)
>  [netty-all-4.0.23.Final.jar:4.0.23.Final]
>   at 
> io.netty.channel.AbstractChannelHandlerContext$8.run(AbstractChannelHandlerContext.java:324)
>  [netty-all-4.0.23.Final.jar:4.0.23.Final]
>   at 
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) 
> [na:1.8.0_51]
>   at 
> org.apache.cassandra.concurrent.AbstractLocalAwareExecutorService$FutureTask.run(AbstractLocalAwareExecutorService.java:164)
>  [main/:na]
>   at org.apache.cassandra.concurrent.SEPWorker.run(SEPWorker.java:105) 
> [main/:na]
>   at java.lang.Thread.run(Thread.java:745) [na:1.8.0_51]
> {code}
> This failure is flaky, but not uncommon. I ran it 300 times here, and saw 
> about 100 failures on CI:
> http://cassci.datastax.com/view/Parameterized/job/parameterized_dtest_multiplexer/53/testReport/
> This is a recent failure, and given the type of failure, it seems like 
> potentially a bug and not a test issue. [~beobal], you may be most interested 
> in looking at this?



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

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

[jira] [Comment Edited] (CASSANDRA-13798) Disallow filtering on non-primary-key base column for MV

[ZhaoYang (JIRA)]

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

ZhaoYang edited comment on CASSANDRA-13798 at 8/25/17 11:17 AM:


| [trunk|https://github.com/jasonstack/cassandra/commits/CASSANDRA-13798-trunk] 
|
| [3.11|https://github.com/jasonstack/cassandra/commits/CASSANDRA-13798-3.11] |
| [dtest|https://github.com/riptano/cassandra-dtest/commits/CASSANDRA-13798] |

The patch is to revert supporting non-pk base column filtering on MV on 3.11 & 
trunk.  The feature was added in 3.10 and the consequence may have been 
overlooked. It's better to revert it in 3.x/trunk, before more users start 
using it.

At the same time, I will work on a proper design (eg. multi-timestamp approach 
discussed in CASSANDRA-11500 and CASSANDRA-10226) for non-pk base column 
filtering and multiple non-pk base column in view pk.


was (Author: jasonstack):
| [trunk|https://github.com/jasonstack/cassandra/commits/CASSANDRA-13798-trunk] 
|
| [3.11|https://github.com/jasonstack/cassandra/commits/CASSANDRA-13798-3.11] |
| [dtest|https://github.com/riptano/cassandra-dtest/commits/CASSANDRA-13798] |

The patch is to revert supporting non-pk base column filtering on MV on 3.11 & 
trunk. I will work on a proper design (eg. multi-timestamp approach) for non-pk 
base column filtering and multiple non-pk base column in view pk.

> Disallow filtering on non-primary-key base column for MV
> 
>
> Key: CASSANDRA-13798
> URL: https://issues.apache.org/jira/browse/CASSANDRA-13798
> Project: Cassandra
>  Issue Type: Bug
>  Components: Materialized Views
>Reporter: ZhaoYang
>Assignee: ZhaoYang
>
> We should probably consider disallow filtering conditions on non-primary-key 
> base column for Materialized View which is introduced in CASSANDRA-10368.
> The main problem is that the liveness of view row is now depending on 
> multiple base columns (multiple filtered non-pk base column + base column 
> used in view pk) and this semantic could not be properly support without 
> drastic storage format changes. (SEE CASSANDRA-11500, 
> [background|https://issues.apache.org/jira/browse/CASSANDRA-11500?focusedCommentId=16119823=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-16119823])
> We should step back and re-consider the non-primary-key filtering feature 
> together with supporting multiple non-PK cols in MV clustering key in 
> CASSANDRA-10226.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

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

[jira] [Assigned] (CASSANDRA-13798) Disallow filtering on non-primary-key base column for MV

[ZhaoYang (JIRA)]

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

ZhaoYang reassigned CASSANDRA-13798:


Assignee: ZhaoYang

> Disallow filtering on non-primary-key base column for MV
> 
>
> Key: CASSANDRA-13798
> URL: https://issues.apache.org/jira/browse/CASSANDRA-13798
> Project: Cassandra
>  Issue Type: Bug
>  Components: Materialized Views
>Reporter: ZhaoYang
>Assignee: ZhaoYang
>
> We should probably consider disallow filtering conditions on non-primary-key 
> base column for Materialized View which is introduced in CASSANDRA-10368.
> The main problem is that the liveness of view row is now depending on 
> multiple base columns (multiple filtered non-pk base column + base column 
> used in view pk) and this semantic could not be properly support without 
> drastic storage format changes. (SEE CASSANDRA-11500, 
> [background|https://issues.apache.org/jira/browse/CASSANDRA-11500?focusedCommentId=16119823=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-16119823])
> We should step back and re-consider the non-primary-key filtering feature 
> together with supporting multiple non-PK cols in MV clustering key in 
> CASSANDRA-10226.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

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

[jira] [Commented] (CASSANDRA-13798) Disallow filtering on non-primary-key base column for MV

[ZhaoYang (JIRA)]

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

ZhaoYang commented on CASSANDRA-13798:
--

| [trunk|https://github.com/jasonstack/cassandra/commits/CASSANDRA-13798-trunk] 
|
| [3.11|https://github.com/jasonstack/cassandra/commits/CASSANDRA-13798-3.11] |
| [dtest|https://github.com/riptano/cassandra-dtest/commits/CASSANDRA-13798] |

The patch is to revert supporting non-pk base column filtering on MV on 3.11 & 
trunk. I will work on a proper design (eg. multi-timestamp approach) for non-pk 
base column filtering and multiple non-pk base column in view pk.

> Disallow filtering on non-primary-key base column for MV
> 
>
> Key: CASSANDRA-13798
> URL: https://issues.apache.org/jira/browse/CASSANDRA-13798
> Project: Cassandra
>  Issue Type: Bug
>  Components: Materialized Views
>Reporter: ZhaoYang
>
> We should probably consider disallow filtering conditions on non-primary-key 
> base column for Materialized View which is introduced in CASSANDRA-10368.
> The main problem is that the liveness of view row is now depending on 
> multiple base columns (multiple filtered non-pk base column + base column 
> used in view pk) and this semantic could not be properly support without 
> drastic storage format changes. (SEE CASSANDRA-11500, 
> [background|https://issues.apache.org/jira/browse/CASSANDRA-11500?focusedCommentId=16119823=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-16119823])
> We should step back and re-consider the non-primary-key filtering feature 
> together with supporting multiple non-PK cols in MV clustering key in 
> CASSANDRA-10226.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

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

[jira] [Created] (CASSANDRA-13799) Fix some alerts raised by lgtm.com

[Malcolm Taylor (JIRA)]

Malcolm Taylor created CASSANDRA-13799:
--

 Summary: Fix some alerts raised by lgtm.com
 Key: CASSANDRA-13799
 URL: https://issues.apache.org/jira/browse/CASSANDRA-13799
 Project: Cassandra
  Issue Type: Improvement
Reporter: Malcolm Taylor
Assignee: Malcolm Taylor


lgtm.com has identified a number of issues  where there may be scope for 
improving the code 
([https://lgtm.com/projects/g/apache/cassandra/alerts/?mode=tree=error]).
 This issue is to address some of the more straightforward cases.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

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

[jira] [Comment Edited] (CASSANDRA-13418) Allow TWCS to ignore overlaps when dropping fully expired sstables

[Romain GERARD (JIRA)]

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

Romain GERARD edited comment on CASSANDRA-13418 at 8/25/17 9:41 AM:


{quote}looks just like a flakey test to me. {quote}
Ok

{quote}you can let me know if you agree{quote}
I am at peace with that :)


was (Author: rgerard):
I am at peace with that :)


> Allow TWCS to ignore overlaps when dropping fully expired sstables
> --
>
> Key: CASSANDRA-13418
> URL: https://issues.apache.org/jira/browse/CASSANDRA-13418
> Project: Cassandra
>  Issue Type: Improvement
>  Components: Compaction
>Reporter: Corentin Chary
>  Labels: twcs
> Attachments: twcs-cleanup.png
>
>
> http://thelastpickle.com/blog/2016/12/08/TWCS-part1.html explains it well. If 
> you really want read-repairs you're going to have sstables blocking the 
> expiration of other fully expired SSTables because they overlap.
> You can set unchecked_tombstone_compaction = true or tombstone_threshold to a 
> very low value and that will purge the blockers of old data that should 
> already have expired, thus removing the overlaps and allowing the other 
> SSTables to expire.
> The thing is that this is rather CPU intensive and not optimal. If you have 
> time series, you might not care if all your data doesn't exactly expire at 
> the right time, or if data re-appears for some time, as long as it gets 
> deleted as soon as it can. And in this situation I believe it would be really 
> beneficial to allow users to simply ignore overlapping SSTables when looking 
> for fully expired ones.
> To the question: why would you need read-repairs ?
> - Full repairs basically take longer than the TTL of the data on my dataset, 
> so this isn't really effective.
> - Even with a 10% chances of doing a repair, we found out that this would be 
> enough to greatly reduce entropy of the most used data (and if you have 
> timeseries, you're likely to have a dashboard doing the same important 
> queries over and over again).
> - LOCAL_QUORUM is too expensive (need >3 replicas), QUORUM is too slow.
> I'll try to come up with a patch demonstrating how this would work, try it on 
> our system and report the effects.
> cc: [~adejanovski], [~rgerard] as I know you worked on similar issues already.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

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

[jira] [Commented] (CASSANDRA-13418) Allow TWCS to ignore overlaps when dropping fully expired sstables

[Romain GERARD (JIRA)]

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

Romain GERARD commented on CASSANDRA-13418:
---

I am at peace with that :)


> Allow TWCS to ignore overlaps when dropping fully expired sstables
> --
>
> Key: CASSANDRA-13418
> URL: https://issues.apache.org/jira/browse/CASSANDRA-13418
> Project: Cassandra
>  Issue Type: Improvement
>  Components: Compaction
>Reporter: Corentin Chary
>  Labels: twcs
> Attachments: twcs-cleanup.png
>
>
> http://thelastpickle.com/blog/2016/12/08/TWCS-part1.html explains it well. If 
> you really want read-repairs you're going to have sstables blocking the 
> expiration of other fully expired SSTables because they overlap.
> You can set unchecked_tombstone_compaction = true or tombstone_threshold to a 
> very low value and that will purge the blockers of old data that should 
> already have expired, thus removing the overlaps and allowing the other 
> SSTables to expire.
> The thing is that this is rather CPU intensive and not optimal. If you have 
> time series, you might not care if all your data doesn't exactly expire at 
> the right time, or if data re-appears for some time, as long as it gets 
> deleted as soon as it can. And in this situation I believe it would be really 
> beneficial to allow users to simply ignore overlapping SSTables when looking 
> for fully expired ones.
> To the question: why would you need read-repairs ?
> - Full repairs basically take longer than the TTL of the data on my dataset, 
> so this isn't really effective.
> - Even with a 10% chances of doing a repair, we found out that this would be 
> enough to greatly reduce entropy of the most used data (and if you have 
> timeseries, you're likely to have a dashboard doing the same important 
> queries over and over again).
> - LOCAL_QUORUM is too expensive (need >3 replicas), QUORUM is too slow.
> I'll try to come up with a patch demonstrating how this would work, try it on 
> our system and report the effects.
> cc: [~adejanovski], [~rgerard] as I know you worked on similar issues already.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

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

[jira] [Commented] (CASSANDRA-13785) Compaction fails for SSTables with large number of keys

[Romain Hardouin (JIRA)]

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

Romain Hardouin commented on CASSANDRA-13785:
-

Thanks!

> Compaction fails for SSTables with large number of keys
> ---
>
> Key: CASSANDRA-13785
> URL: https://issues.apache.org/jira/browse/CASSANDRA-13785
> Project: Cassandra
>  Issue Type: Bug
>  Components: Compaction
>Reporter: Jay Zhuang
>Assignee: Jay Zhuang
>
> Every a few minutes there're "LEAK DTECTED" messages in the log:
> {noformat}
> ERROR [Reference-Reaper:1] 2017-08-18 17:18:40,357 Ref.java:223 - LEAK 
> DETECTED: a reference 
> (org.apache.cassandra.utils.concurrent.Ref$State@3ed22d7) to class 
> org.apache.cassandra.utils.concurrent.WrappedSharedCloseable$Tidy@1022568824:[Memory@[0..159b6ba4),
>  Memory@[0..d8123468)] was not released before the reference was garbage 
> collected
> ERROR [Reference-Reaper:1] 2017-08-18 17:20:49,693 Ref.java:223 - LEAK 
> DETECTED: a reference 
> (org.apache.cassandra.utils.concurrent.Ref$State@6470405b) to class 
> org.apache.cassandra.utils.concurrent.WrappedSharedCloseable$Tidy@97898152:[Memory@[0..159b6ba4),
>  Memory@[0..d8123468)] was not released before the reference was garbage 
> collected
> ERROR [Reference-Reaper:1] 2017-08-18 17:22:38,519 Ref.java:223 - LEAK 
> DETECTED: a reference 
> (org.apache.cassandra.utils.concurrent.Ref$State@6fc4af5f) to class 
> org.apache.cassandra.utils.concurrent.WrappedSharedCloseable$Tidy@1247404854:[Memory@[0..159b6ba4),
>  Memory@[0..d8123468)] was not released before the reference was garbage 
> collected
> {noformat}
> Debugged the issue and found it's triggered by failed compactions, if the 
> compacted SSTable has more than 51m {{Integer.MAX_VALUE / 40}}) keys, it will 
> fail to create the IndexSummary: 
> [IndexSummary:84|https://github.com/apache/cassandra/blob/cassandra-3.0/src/java/org/apache/cassandra/io/sstable/IndexSummary.java#L84].
> Cassandra compaction tried to compact every a few minutes and keeps failing.
> The root cause is while [creating 
> SafeMemoryWriter|https://github.com/apache/cassandra/blob/cassandra-3.0/src/java/org/apache/cassandra/io/sstable/IndexSummaryBuilder.java#L112]
>  with {{> Integer.MAX_VALUE}} space, it returns the tailing 
> {{Integer.MAX_VALUE}} space 
> [SafeMemoryWriter.java:83|https://github.com/apache/cassandra/blob/6a1b1f26b7174e8c9bf86a96514ab626ce2a4117/src/java/org/apache/cassandra/io/util/SafeMemoryWriter.java#L83],
>  which makes the first 
> [entries.length()|https://github.com/apache/cassandra/blob/6a1b1f26b7174e8c9bf86a96514ab626ce2a4117/src/java/org/apache/cassandra/io/sstable/IndexSummaryBuilder.java#L173]
>  not 0. So the assert fails here: 
> [IndexSummary:84|https://github.com/apache/cassandra/blob/cassandra-3.0/src/java/org/apache/cassandra/io/sstable/IndexSummary.java#L84]



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

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

[jira] [Commented] (CASSANDRA-13600) sstabledump possible problem

[Varun Barala (JIRA)]

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

Varun Barala commented on CASSANDRA-13600:
--


This part has problem:- 
https://github.com/apache/cassandra/blob/cassandra-3.10/src/java/org/apache/cassandra/tools/JsonTransformer.java#L189
Since partition will have one position but can have multiple statuses(live info 
and delete info). I'll provide the patch.

> sstabledump possible problem
> 
>
> Key: CASSANDRA-13600
> URL: https://issues.apache.org/jira/browse/CASSANDRA-13600
> Project: Cassandra
>  Issue Type: Bug
> Environment: Official cassandra docker image (last) under Win10
>Reporter: a8775
> Fix For: 3.10
>
>
> h2. Possible bug in sstabledump
> {noformat}
> cqlsh> show version
> [cqlsh 5.0.1 | Cassandra 3.10 | CQL spec 3.4.4 | Native protocol v4]
> {noformat}
> h2. Execute script in cqlsh in new keyspace
> {noformat}
> CREATE TABLE IF NOT EXISTS test_data (   
> // partitioning key
> PK TEXT, 
> // data
> Data TEXT,
> 
> PRIMARY KEY (PK)
> );
> insert into test_data(PK,Data) values('0','');
> insert into test_data(PK,Data) values('1','');
> insert into test_data(PK,Data) values('2','');
> delete from test_data where PK='1';
> insert into test_data(PK,Data) values('1','');
> {noformat}
> h2. Execute the following commands
> {noformat}
> nodetool flush
> nodetool compact
> sstabledump mc-2-big-Data.db
> sstabledump -d mc-2-big-Data.db
> {noformat}
> h3. default dump - missing data for partiotion key = "1"
> {noformat}
> [
>   {
> "partition" : {
>   "key" : [ "0" ],
>   "position" : 0
> },
> "rows" : [
>   {
> "type" : "row",
> "position" : 15,
> "liveness_info" : { "tstamp" : "2017-06-14T12:23:13.529389Z" },
> "cells" : [
>   { "name" : "data", "value" : "" }
> ]
>   }
> ]
>   },
>   {
> "partition" : {
>   "key" : [ "2" ],
>   "position" : 26
> },
> "rows" : [
>   {
> "type" : "row",
> "position" : 41,
> "liveness_info" : { "tstamp" : "2017-06-14T12:23:13.544132Z" },
> "cells" : [
>   { "name" : "data", "value" : "" }
> ]
>   }
> ]
>   },
>   {
> "partition" : {
>   "key" : [ "1" ],
>   "position" : 53,
>   "deletion_info" : { "marked_deleted" : "2017-06-14T12:23:13.545988Z", 
> "local_delete_time" : "2017-06-14T12:23:13Z" }
> }
>   }
> ]
> {noformat}
> h3. dump with -d option - correct data for partiotion key = "1"
> {noformat}
> [0]@0 Row[info=[ts=1497442993529389] ]:  | [data= ts=1497442993529389]
> [2]@26 Row[info=[ts=1497442993544132] ]:  | [data= ts=1497442993544132]
> [1]@53 deletedAt=1497442993545988, localDeletion=1497442993
> [1]@53 Row[info=[ts=1497442993550159] ]:  | [data= ts=1497442993550159]
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

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

[jira] [Issue Comment Deleted] (CASSANDRA-13363) java.lang.ArrayIndexOutOfBoundsException: null

[zhaoyan (JIRA)]

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

zhaoyan updated CASSANDRA-13363:

Comment: was deleted

(was: use the Command.Index as the "USING INDEX"。 （for CASSANDRA-10214 ） and  
make sure the field never changes and is only set once at construction time。 

without a protocol change.

I think it is a good idea. 

And add one another cache field  （that do not participate in serialization， 
only use as cache local） to save  the index cassandra lookup?  )

> java.lang.ArrayIndexOutOfBoundsException: null
> --
>
> Key: CASSANDRA-13363
> URL: https://issues.apache.org/jira/browse/CASSANDRA-13363
> Project: Cassandra
>  Issue Type: Bug
> Environment: CentOS 6, Cassandra 3.10
>Reporter: Artem Rokhin
>Assignee: Aleksey Yeschenko
>Priority: Critical
> Fix For: 3.0.x, 3.11.x, 4.x
>
>
> Constantly see this error in the log without any additional information or a 
> stack trace.
> {code}
> Exception in thread Thread[MessagingService-Incoming-/10.0.1.26,5,main]
> {code}
> {code}
> java.lang.ArrayIndexOutOfBoundsException: null
> {code}
> Logger: org.apache.cassandra.service.CassandraDaemon
> Thrdead: MessagingService-Incoming-/10.0.1.12
> Method: uncaughtException
> File: CassandraDaemon.java
> Line: 229



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

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

[jira] [Commented] (CASSANDRA-13620) Don't skip corrupt sstables on startup

[Marcus Eriksson (JIRA)]

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

Marcus Eriksson commented on CASSANDRA-13620:
-

yeah, the suspicious tests pass locally multiple times

> Don't skip corrupt sstables on startup
> --
>
> Key: CASSANDRA-13620
> URL: https://issues.apache.org/jira/browse/CASSANDRA-13620
> Project: Cassandra
>  Issue Type: Bug
>Reporter: Marcus Eriksson
>Assignee: Marcus Eriksson
> Fix For: 3.0.x, 3.11.x, 4.x
>
> Attachments: 13620-3.0.png, 13620-3.11.png, 13620-trunk.png
>
>
> If we get an IOException when opening an sstable on startup, we just 
> [skip|https://github.com/apache/cassandra/blob/trunk/src/java/org/apache/cassandra/io/sstable/format/SSTableReader.java#L563-L567]
>  it and continue starting
> we should use the DiskFailurePolicy and never explicitly catch an IOException 
> here



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

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

[jira] [Updated] (CASSANDRA-13792) unable to connect apache-cassandra-3.11.0 after place 4.2.2 JNA jar

[rajasekhar (JIRA)]

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

rajasekhar updated CASSANDRA-13792:
---
Environment: Linux(RHEL 6.8)  (was: Linux)

> unable to connect apache-cassandra-3.11.0 after place 4.2.2 JNA jar 
> 
>
> Key: CASSANDRA-13792
> URL: https://issues.apache.org/jira/browse/CASSANDRA-13792
> Project: Cassandra
>  Issue Type: Bug
>  Components: Configuration
> Environment: Linux(RHEL 6.8)
>Reporter: rajasekhar
>Priority: Critical
> Fix For: 3.11.0
>
> Attachments: log_cassdb.txt
>
>
> After apply work around below solution, installled the pache-cassandra-3.11 
> but i am not connect server status and cqlsh. please find attached log for 
> more information  and let us know the instatllion completed successfully
> "Jeff Jirsa resolved CASSANDRA-13791.
> 
> Resolution: Duplicate
> This was caused (and resolved) by CASSANDRA-13072 , where JNA was upgraded to 
> {{4.4.0}}. That 4.4.0 JNA library was linked against a different version of 
> glibc ( {{GLIBC_2.14}} ), which causes this error. This is fixed in 
> {{3.11.1}}, but you can work around the issue by downloading the 4.2.2 JNA 
> jar from 
> [here|https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_apache_cassandra_raw_00a777ec8ab701b843172e23a6cbdc4d6cf48f8d_lib_jna-2D4.2.2.jar=DwICaQ=eIGjsITfXP_y-DLLX0uEHXJvU8nOHrUK8IrwNKOtkVU=zSydaPm_PKES-H2mB46-9X-iWMDIIymvQCfY02eRW-Q=cSmoTlLQJTt32Gb257uuaz6_WHE6UeXOV5XjO7GTcxk=yieYJ2V_ND3saGBjGH3O-DEwQdfkA44B9yBqtjIU8bE=
>  ] and placing it into the classpath ({{lib/}}), removing {{jna-4.4.0.jar}} 
> in the process.
> > unable to install apache-cassandra-3.11.0 in linux  box
> > ---
> "
> [cassdb@alsc_dev_db bin]$ nodetool status
> -bash: nodetool: command not found
> [cassdb@alsc_dev_db bin]$ pwd
> /u01/Cassandra_home/apache-cassandra-3.11.0/bin
> [cassdb@alsc_dev_db bin]$ sh 
> /u01/Cassandra_home/apache-cassandra-3.11.0/bin/cqlsh
> No appropriate python interpreter found.
> [cassdb@alsc_dev_db bin]$ service cassandra status



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

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

[jira] [Commented] (CASSANDRA-13784) mismatched input 'default' expecting for CREATE TABLE

[timur (JIRA)]

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

timur commented on CASSANDRA-13784:
---

Super

> mismatched input 'default' expecting for CREATE TABLE
> -
>
> Key: CASSANDRA-13784
> URL: https://issues.apache.org/jira/browse/CASSANDRA-13784
> Project: Cassandra
>  Issue Type: Bug
>  Components: CQL
> Environment: {code}
> [root@localhost config]# cat /etc/os-release
> NAME="CentOS Linux"
> VERSION="7 (Core)"
> ID="centos"
> ID_LIKE="rhel fedora"
> VERSION_ID="7"
> PRETTY_NAME="CentOS Linux 7 (Core)"
> ANSI_COLOR="0;31"
> CPE_NAME="cpe:/o:centos:centos:7"
> HOME_URL="https://www.centos.org/;
> BUG_REPORT_URL="https://bugs.centos.org/;
> CENTOS_MANTISBT_PROJECT="CentOS-7"
> CENTOS_MANTISBT_PROJECT_VERSION="7"
> REDHAT_SUPPORT_PRODUCT="centos"
> REDHAT_SUPPORT_PRODUCT_VERSION="7"
> [root@localhost config]# rpm -qa | grep cassandra
> cassandra-3.11.0-1.noarch
> [root@localhost config]# cassandra -v
> 3.11.0
> {code}
>Reporter: timur
>
> Got following error for table create if column name is "default" on 3.11. If 
> I change column name for  example to "defaults" table successfully creates.
> For 3.9 version table with "default" column name successfully creates.  
> {code:sql}
> cqlsh:api_production> CREATE TABLE tasks (id uuid PRIMARY KEY, default 
> boolean, name text, tenant_id uuid) ;
> SyntaxException: line 1:41 mismatched input 'default' expecting ')' (...(id 
> uuid PRIMARY KEY, [default]...)
> {code}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

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