[jira] [Updated] (CASSANDRA-12385) Disk failure policy should not be invoked on out of space
[ https://issues.apache.org/jira/browse/CASSANDRA-12385?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marcus Eriksson updated CASSANDRA-12385: Fix Version/s: 3.x 3.0.x > Disk failure policy should not be invoked on out of space > - > > Key: CASSANDRA-12385 > URL: https://issues.apache.org/jira/browse/CASSANDRA-12385 > Project: Cassandra > Issue Type: Improvement >Reporter: sankalp kohli >Assignee: sankalp kohli >Priority: Minor > Fix For: 3.0.x, 3.x > > Attachments: CASSANDRA-12385_v2.txt > > > If a node fills up temporarily due to compaction the disk failure policy may > be invoked. We > use stop, so the node will be disabled. This leaves the node down even though > it recovers from this > failure by aborting the compaction. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CASSANDRA-12385) Disk failure policy should not be invoked on out of space
[ https://issues.apache.org/jira/browse/CASSANDRA-12385?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15432249#comment-15432249 ] Marcus Eriksson commented on CASSANDRA-12385: - LGTM, will commit once tests have finished: https://cassci.datastax.com/view/Dev/view/krummas/job/krummas-sankalp-12385-dtest/ https://cassci.datastax.com/view/Dev/view/krummas/job/krummas-sankalp-12385-testall/ > Disk failure policy should not be invoked on out of space > - > > Key: CASSANDRA-12385 > URL: https://issues.apache.org/jira/browse/CASSANDRA-12385 > Project: Cassandra > Issue Type: Improvement >Reporter: sankalp kohli >Assignee: sankalp kohli >Priority: Minor > Attachments: CASSANDRA-12385_v2.txt > > > If a node fills up temporarily due to compaction the disk failure policy may > be invoked. We > use stop, so the node will be disabled. This leaves the node down even though > it recovers from this > failure by aborting the compaction. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CASSANDRA-6216) Level Compaction should persist last compacted key per level
[ https://issues.apache.org/jira/browse/CASSANDRA-6216?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marcus Eriksson updated CASSANDRA-6216: --- Fix Version/s: 3.x 3.0.x > Level Compaction should persist last compacted key per level > > > Key: CASSANDRA-6216 > URL: https://issues.apache.org/jira/browse/CASSANDRA-6216 > Project: Cassandra > Issue Type: Sub-task >Reporter: sankalp kohli >Assignee: Dikang Gu >Priority: Minor > Labels: compaction, lcs > Fix For: 3.0.x, 3.x > > Attachments: JIRA-6216.diff > > > Level compaction does not persist the last compacted key per level. This is > important for higher levels. > The sstables with higher token and in higher levels wont get a chance to > compact as the last compacted key will get reset after a restart. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CASSANDRA-6216) Level Compaction should persist last compacted key per level
[ https://issues.apache.org/jira/browse/CASSANDRA-6216?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marcus Eriksson updated CASSANDRA-6216: --- Status: Patch Available (was: Open) > Level Compaction should persist last compacted key per level > > > Key: CASSANDRA-6216 > URL: https://issues.apache.org/jira/browse/CASSANDRA-6216 > Project: Cassandra > Issue Type: Sub-task >Reporter: sankalp kohli >Assignee: Dikang Gu >Priority: Minor > Labels: compaction, lcs > Attachments: JIRA-6216.diff > > > Level compaction does not persist the last compacted key per level. This is > important for higher levels. > The sstables with higher token and in higher levels wont get a chance to > compact as the last compacted key will get reset after a restart. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CASSANDRA-6216) Level Compaction should persist last compacted key per level
[ https://issues.apache.org/jira/browse/CASSANDRA-6216?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15432238#comment-15432238 ] Marcus Eriksson commented on CASSANDRA-6216: this lgtm with a small change - we should call super.startup() after calculating the last compacted keys - otherwise (i think) we could start compactions before it has been calculated I did that and rebased on 3.0 [here|https://github.com/krummas/cassandra/commits/dikang/6216] tests: https://cassci.datastax.com/view/Dev/view/krummas/job/krummas-dikang-6216-testall/ https://cassci.datastax.com/view/Dev/view/krummas/job/krummas-dikang-6216-dtest/ will commit when tests have finished successfully > Level Compaction should persist last compacted key per level > > > Key: CASSANDRA-6216 > URL: https://issues.apache.org/jira/browse/CASSANDRA-6216 > Project: Cassandra > Issue Type: Sub-task >Reporter: sankalp kohli >Assignee: Dikang Gu >Priority: Minor > Labels: compaction, lcs > Attachments: JIRA-6216.diff > > > Level compaction does not persist the last compacted key per level. This is > important for higher levels. > The sstables with higher token and in higher levels wont get a chance to > compact as the last compacted key will get reset after a restart. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Comment Edited] (CASSANDRA-12504) BatchlogManager is shut down twice during drain
[
https://issues.apache.org/jira/browse/CASSANDRA-12504?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15432211#comment-15432211
]
Stefania edited comment on CASSANDRA-12504 at 8/23/16 6:17 AM:
---
I agree, the first call
[here|https://github.com/stef1927/cassandra/commit/218206434d66cbe1d00191d2248474745d132eed#diff-b76a607445d53f18a98c9df14323c7ddR3951]
looks like the correct place.
[~iamaleksey], this looks like an oversight from CASSANDRA-9673, so I am
assigning you as a reviewer in case your memory is better of mine and can
recall a reason why we wanted to move it to the end.
Here is the patch for 3.0, I'm not wasting cycles repeating CI on 3.9 and trunk
for this unless you feel we should:
|[patch|https://github.com/stef1927/cassandra/commits/12504-3.0]|[testall|http://cassci.datastax.com/view/Dev/view/stef1927/job/stef1927-12504-3.0-testall/]|[dtest|http://cassci.datastax.com/view/Dev/view/stef1927/job/stef1927-12504-3.0-dtest/]|
was (Author: stefania):
I agree, the first call
[here|https://github.com/stef1927/cassandra/commit/218206434d66cbe1d00191d2248474745d132eed#diff-b76a607445d53f18a98c9df14323c7ddR3951]
looks like the correct place.
[~iamaleksey], this looks like an oversight from CASSANDRA-9673, so I am
assigning you as a reviewer in case your memory is better of mine and can find
a reason why we wanted to move it to the end.
Here is the patch for 3.0, I'm not wasting cycles repeating CI on 3.9 and trunk
for this unless you feel we should:
|[patch|https://github.com/stef1927/cassandra/commits/12504-3.0]|[testall|http://cassci.datastax.com/view/Dev/view/stef1927/job/stef1927-12504-3.0-testall/]|[dtest|http://cassci.datastax.com/view/Dev/view/stef1927/job/stef1927-12504-3.0-dtest/]|
> BatchlogManager is shut down twice during drain
> ---
>
> Key: CASSANDRA-12504
> URL: https://issues.apache.org/jira/browse/CASSANDRA-12504
> Project: Cassandra
> Issue Type: Bug
>Reporter: Alex Petrov
>Assignee: Stefania
>Priority: Minor
> Fix For: 3.0.x, 3.x
>
>
> {{BatchlogManager}} is shut down twice during in the {{StorageService}}, once
> [here|https://github.com/apache/cassandra/blob/trunk/src/java/org/apache/cassandra/service/StorageService.java#L4216]
> and once
> [here|https://github.com/apache/cassandra/blob/trunk/src/java/org/apache/cassandra/service/StorageService.java#L4285].
> The first shutdown was already there but the last one seems to have been
> added
> [here|https://github.com/apache/cassandra/commit/53a177a9150586e56408f25c959f75110a2997e7#diff-b76a607445d53f18a98c9df14323c7ddR3913].
> It seems to be harmless, as it’s not required in stages in-between, so
> second run would be a no-op.
> Following the logic of other shutdown hook, the first one is the good place
> for it to be (right before {{HintsService}}).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (CASSANDRA-12504) BatchlogManager is shut down twice during drain
[
https://issues.apache.org/jira/browse/CASSANDRA-12504?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stefania updated CASSANDRA-12504:
-
Reviewer: Aleksey Yeschenko
Fix Version/s: 3.x
3.0.x
Status: Patch Available (was: In Progress)
> BatchlogManager is shut down twice during drain
> ---
>
> Key: CASSANDRA-12504
> URL: https://issues.apache.org/jira/browse/CASSANDRA-12504
> Project: Cassandra
> Issue Type: Bug
>Reporter: Alex Petrov
>Assignee: Stefania
>Priority: Minor
> Fix For: 3.0.x, 3.x
>
>
> {{BatchlogManager}} is shut down twice during in the {{StorageService}}, once
> [here|https://github.com/apache/cassandra/blob/trunk/src/java/org/apache/cassandra/service/StorageService.java#L4216]
> and once
> [here|https://github.com/apache/cassandra/blob/trunk/src/java/org/apache/cassandra/service/StorageService.java#L4285].
> The first shutdown was already there but the last one seems to have been
> added
> [here|https://github.com/apache/cassandra/commit/53a177a9150586e56408f25c959f75110a2997e7#diff-b76a607445d53f18a98c9df14323c7ddR3913].
> It seems to be harmless, as it’s not required in stages in-between, so
> second run would be a no-op.
> Following the logic of other shutdown hook, the first one is the good place
> for it to be (right before {{HintsService}}).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (CASSANDRA-12504) BatchlogManager is shut down twice during drain
[
https://issues.apache.org/jira/browse/CASSANDRA-12504?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15432211#comment-15432211
]
Stefania commented on CASSANDRA-12504:
--
I agree, the first call
[here|https://github.com/stef1927/cassandra/commit/218206434d66cbe1d00191d2248474745d132eed#diff-b76a607445d53f18a98c9df14323c7ddR3951]
looks like the correct place.
[~iamaleksey], this looks like an oversight from CASSANDRA-9673, so I am
assigning you as a reviewer in case your memory is better of mine and can find
a reason why we wanted to move it to the end.
Here is the patch for 3.0, I'm not wasting cycles repeating CI on 3.9 and trunk
for this unless you feel we should:
|[patch|https://github.com/stef1927/cassandra/commits/12504-3.0]|[testall|http://cassci.datastax.com/view/Dev/view/stef1927/job/stef1927-12504-3.0-testall/]|[dtest|http://cassci.datastax.com/view/Dev/view/stef1927/job/stef1927-12504-3.0-dtest/]|
> BatchlogManager is shut down twice during drain
> ---
>
> Key: CASSANDRA-12504
> URL: https://issues.apache.org/jira/browse/CASSANDRA-12504
> Project: Cassandra
> Issue Type: Bug
>Reporter: Alex Petrov
>Assignee: Stefania
>Priority: Minor
> Fix For: 3.0.x, 3.x
>
>
> {{BatchlogManager}} is shut down twice during in the {{StorageService}}, once
> [here|https://github.com/apache/cassandra/blob/trunk/src/java/org/apache/cassandra/service/StorageService.java#L4216]
> and once
> [here|https://github.com/apache/cassandra/blob/trunk/src/java/org/apache/cassandra/service/StorageService.java#L4285].
> The first shutdown was already there but the last one seems to have been
> added
> [here|https://github.com/apache/cassandra/commit/53a177a9150586e56408f25c959f75110a2997e7#diff-b76a607445d53f18a98c9df14323c7ddR3913].
> It seems to be harmless, as it’s not required in stages in-between, so
> second run would be a no-op.
> Following the logic of other shutdown hook, the first one is the good place
> for it to be (right before {{HintsService}}).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (CASSANDRA-12094) dtest failure in consistency_test.TestAccuracy.test_network_topology_strategy_each_quorum_counters
[
https://issues.apache.org/jira/browse/CASSANDRA-12094?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15432194#comment-15432194
]
Stefania commented on CASSANDRA-12094:
--
This might have been fixed by the [pull
request|https://github.com/riptano/cassandra-dtest/pull/1269] for
CASSANDRA-12092, we need to multiplex once the PR is merged to be sure.
> dtest failure in
> consistency_test.TestAccuracy.test_network_topology_strategy_each_quorum_counters
> --
>
> Key: CASSANDRA-12094
> URL: https://issues.apache.org/jira/browse/CASSANDRA-12094
> Project: Cassandra
> Issue Type: Test
>Reporter: Sean McCarthy
>Assignee: DS Test Eng
> Labels: dtest, windows
> Attachments: node1.log, node1_debug.log, node1_gc.log, node2.log,
> node2_debug.log, node2_gc.log, node3.log, node3_debug.log, node3_gc.log,
> node4.log, node4_debug.log, node4_gc.log, node5.log, node5_debug.log,
> node5_gc.log, node6.log, node6_debug.log, node6_gc.log
>
>
> example failure:
> http://cassci.datastax.com/job/trunk_dtest_win32/445/testReport/consistency_test/TestAccuracy/test_network_topology_strategy_each_quorum_counters
> Failed on CassCI build trunk_dtest_win32 #445
> {code}
> Stacktrace
> File "C:\tools\python2\lib\unittest\case.py", line 329, in run
> testMethod()
> File "D:\jenkins\workspace\trunk_dtest_win32\cassandra-dtest\tools.py",
> line 288, in wrapped
> f(obj)
> File
> "D:\jenkins\workspace\trunk_dtest_win32\cassandra-dtest\consistency_test.py",
> line 738, in test_network_topology_strategy_each_quorum_counters
>
> self._run_test_function_in_parallel(TestAccuracy.Validation.validate_counters,
> self.nodes, self.rf.values(), combinations),
> File
> "D:\jenkins\workspace\trunk_dtest_win32\cassandra-dtest\consistency_test.py",
> line 543, in _run_test_function_in_parallel
> assert False, err.message
> "Failed to read value from sufficient number of nodes, required 4 nodes to
> have a counter value of 6 at key 56, instead got these values: [7, 7, 7, 7,
> 7, 7]
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (CASSANDRA-12093) dtest failure in consistency_test.TestAccuracy.test_network_topology_strategy_counters
[
https://issues.apache.org/jira/browse/CASSANDRA-12093?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15432193#comment-15432193
]
Stefania commented on CASSANDRA-12093:
--
This might have been fixed by the [pull
request|https://github.com/riptano/cassandra-dtest/pull/1269] for
CASSANDRA-12092, we need to multiplex once the PR is merged to be sure.
> dtest failure in
> consistency_test.TestAccuracy.test_network_topology_strategy_counters
> --
>
> Key: CASSANDRA-12093
> URL: https://issues.apache.org/jira/browse/CASSANDRA-12093
> Project: Cassandra
> Issue Type: Test
>Reporter: Sean McCarthy
>Assignee: DS Test Eng
> Labels: dtest, windows
> Attachments: node1.log, node1_debug.log, node1_gc.log, node2.log,
> node2_debug.log, node2_gc.log, node3.log, node3_debug.log, node3_gc.log,
> node4.log, node4_debug.log, node4_gc.log, node5.log, node5_debug.log,
> node5_gc.log, node6.log, node6_debug.log, node6_gc.log
>
>
> example failure:
> http://cassci.datastax.com/job/trunk_dtest_win32/445/testReport/consistency_test/TestAccuracy/test_network_topology_strategy_counters
> Failed on CassCI build trunk_dtest_win32 #445
> {code}
> Stacktrace
> File "C:\tools\python2\lib\unittest\case.py", line 329, in run
> testMethod()
> File
> "D:\jenkins\workspace\trunk_dtest_win32\cassandra-dtest\consistency_test.py",
> line 720, in test_network_topology_strategy_counters
>
> self._run_test_function_in_parallel(TestAccuracy.Validation.validate_counters,
> self.nodes, self.rf.values(), combinations),
> File
> "D:\jenkins\workspace\trunk_dtest_win32\cassandra-dtest\consistency_test.py",
> line 543, in _run_test_function_in_parallel
> assert False, err.message
> "Got 4 from ['127.0.0.1'], expected 3 at ONE
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (CASSANDRA-12092) dtest failure in consistency_test.TestAccuracy.test_simple_strategy_counters
[
https://issues.apache.org/jira/browse/CASSANDRA-12092?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stefania updated CASSANDRA-12092:
-
Reviewer: DS Test Eng
Status: Patch Available (was: In Progress)
> dtest failure in consistency_test.TestAccuracy.test_simple_strategy_counters
>
>
> Key: CASSANDRA-12092
> URL: https://issues.apache.org/jira/browse/CASSANDRA-12092
> Project: Cassandra
> Issue Type: Test
>Reporter: Sean McCarthy
>Assignee: Stefania
> Labels: dtest
> Attachments: jenkins-stef1927-dtest-multiplex-23_logs.000.tar.gz,
> node1.log, node2.log, node3.log
>
>
> example failure:
> http://cassci.datastax.com/job/cassandra-2.1_dtest/484/testReport/consistency_test/TestAccuracy/test_simple_strategy_counters
> Failed on CassCI build cassandra-2.1_dtest #484
> {code}
> Standard Error
> Traceback (most recent call last):
> File "/home/automaton/cassandra-dtest/consistency_test.py", line 514, in run
> valid_fcn(v)
> File "/home/automaton/cassandra-dtest/consistency_test.py", line 497, in
> validate_counters
> check_all_sessions(s, n, c)
> File "/home/automaton/cassandra-dtest/consistency_test.py", line 490, in
> check_all_sessions
> "value of %s at key %d, instead got these values: %s" % (write_nodes,
> val, n, results)
> AssertionError: Failed to read value from sufficient number of nodes,
> required 2 nodes to have a counter value of 1 at key 200, instead got these
> values: [0, 0, 1]
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (CASSANDRA-12092) dtest failure in consistency_test.TestAccuracy.test_simple_strategy_counters
[
https://issues.apache.org/jira/browse/CASSANDRA-12092?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15432191#comment-15432191
]
Stefania commented on CASSANDRA-12092:
--
I traced the remaining rare failures down to a speculative retry. It was not
the async repair digest mismatch that caused problems, rather in some rare
cases a speculative retry (which is sent after a sleep period) arrives before
the local read. I've disabled speculative retry and I got two 5x200 builds
without any failures, running a modified test that repeated QUORUM/ONE 10
times, see
[here|http://cassci.datastax.com/view/Dev/view/stef1927/job/stef1927-dtest-multiplex/26/]
and
[here|http://cassci.datastax.com/view/Dev/view/stef1927/job/stef1927-dtest-multiplex/28/].
[Pull request|https://github.com/riptano/cassandra-dtest/pull/1269].
> dtest failure in consistency_test.TestAccuracy.test_simple_strategy_counters
>
>
> Key: CASSANDRA-12092
> URL: https://issues.apache.org/jira/browse/CASSANDRA-12092
> Project: Cassandra
> Issue Type: Test
>Reporter: Sean McCarthy
>Assignee: Stefania
> Labels: dtest
> Attachments: jenkins-stef1927-dtest-multiplex-23_logs.000.tar.gz,
> node1.log, node2.log, node3.log
>
>
> example failure:
> http://cassci.datastax.com/job/cassandra-2.1_dtest/484/testReport/consistency_test/TestAccuracy/test_simple_strategy_counters
> Failed on CassCI build cassandra-2.1_dtest #484
> {code}
> Standard Error
> Traceback (most recent call last):
> File "/home/automaton/cassandra-dtest/consistency_test.py", line 514, in run
> valid_fcn(v)
> File "/home/automaton/cassandra-dtest/consistency_test.py", line 497, in
> validate_counters
> check_all_sessions(s, n, c)
> File "/home/automaton/cassandra-dtest/consistency_test.py", line 490, in
> check_all_sessions
> "value of %s at key %d, instead got these values: %s" % (write_nodes,
> val, n, results)
> AssertionError: Failed to read value from sufficient number of nodes,
> required 2 nodes to have a counter value of 1 at key 200, instead got these
> values: [0, 0, 1]
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (CASSANDRA-12486) Structure for compactionhistory output (JSON, YAML)
[ https://issues.apache.org/jira/browse/CASSANDRA-12486?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Masataka Yamaguchi updated CASSANDRA-12486: --- Status: Patch Available (was: Open) > Structure for compactionhistory output (JSON, YAML) > --- > > Key: CASSANDRA-12486 > URL: https://issues.apache.org/jira/browse/CASSANDRA-12486 > Project: Cassandra > Issue Type: Improvement > Components: Tools >Reporter: Masataka Yamaguchi >Assignee: Masataka Yamaguchi >Priority: Minor > Fix For: 3.x > > Attachments: CASSANDRA-12486-trunk.patch, > CASSANDRA-12486-v2-git-format-patch.patch, compactionhistory_result-v2.json, > compactionhistory_result-v2.txt, compactionhistory_result-v2.yaml, > compactionhistory_result.json, compactionhistory_result.txt, > compactionhistory_result.yaml > > > As with nodetool tpstats and tablestats (CASSANDRA-12035), nodetool > compactionhistory should also support useful output formats such as JSON or > YAML, so we implemented it. > Please review the attached patch. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CASSANDRA-12486) Structure for compactionhistory output (JSON, YAML)
[ https://issues.apache.org/jira/browse/CASSANDRA-12486?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Masataka Yamaguchi updated CASSANDRA-12486: --- Attachment: compactionhistory_result-v2.yaml compactionhistory_result-v2.txt compactionhistory_result-v2.json CASSANDRA-12486-v2-git-format-patch.patch First, printing out compactionhistory as a list sorted by compacted_at sounds better for me than an associative array whose key is each compaction’s id, so I rewrote the patch so as to print it as a list sorted by compacted_at. Second, I also think that we should print it in the same way as default printer. So I changed the way of printing compacted_at in the patch. I attached the new patch and new output files, so please review it when you have time. Please note that the new patch was generated with git format-patch, while the previous patch was generated by patch command. Thank you. > Structure for compactionhistory output (JSON, YAML) > --- > > Key: CASSANDRA-12486 > URL: https://issues.apache.org/jira/browse/CASSANDRA-12486 > Project: Cassandra > Issue Type: Improvement > Components: Tools >Reporter: Masataka Yamaguchi >Assignee: Masataka Yamaguchi >Priority: Minor > Fix For: 3.x > > Attachments: CASSANDRA-12486-trunk.patch, > CASSANDRA-12486-v2-git-format-patch.patch, compactionhistory_result-v2.json, > compactionhistory_result-v2.txt, compactionhistory_result-v2.yaml, > compactionhistory_result.json, compactionhistory_result.txt, > compactionhistory_result.yaml > > > As with nodetool tpstats and tablestats (CASSANDRA-12035), nodetool > compactionhistory should also support useful output formats such as JSON or > YAML, so we implemented it. > Please review the attached patch. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CASSANDRA-12330) Unreleased Resource: Sockets
[
https://issues.apache.org/jira/browse/CASSANDRA-12330?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Arunkumar M updated CASSANDRA-12330:
Attachment: 12330-3.0.txt
> Unreleased Resource: Sockets
>
>
> Key: CASSANDRA-12330
> URL: https://issues.apache.org/jira/browse/CASSANDRA-12330
> Project: Cassandra
> Issue Type: Sub-task
>Reporter: Eduardo Aguinaga
>Assignee: Arunkumar M
> Labels: easyfix, newbie, patch
> Fix For: 3.x
>
> Attachments: 12330-3.0.txt, 12330-3.0.txt
>
>
> Overview:
> In May through June of 2016 a static analysis was performed on version 3.0.5
> of the Cassandra source code. The analysis included an automated analysis
> using HP Fortify v4.21 SCA and a manual analysis utilizing SciTools
> Understand v4. The results of that analysis includes the issue below.
> Issue:
> Sockets are low level resources that must be explicitly released so
> subsequent callers will have access to previously used sockets. In the file
> DefaultConnectionFactory.java on line 52 a socket is acquired and eventually
> returned to the caller on line 55.
> If an exception is thrown by any of the code between lines 52 and 55 the
> socket acquired on line 52 will not be released for subsequent reuse.
> DefaultConnectionFactory.java, lines 50-73:
> {code:java}
> 50 try
> 51 {
> 52 Socket socket = OutboundTcpConnectionPool.newSocket(peer);
> 53
> socket.setSoTimeout(DatabaseDescriptor.getStreamingSocketTimeout());
> 54 socket.setKeepAlive(true);
> 55 return socket;
> 56 }
> 57 catch (IOException e)
> 58 {
> 59 if (++attempts >= MAX_CONNECT_ATTEMPTS)
> 60 throw e;
> 61
> 62 long waitms = DatabaseDescriptor.getRpcTimeout() *
> (long)Math.pow(2, attempts);
> 63 logger.warn("Failed attempt {} to connect to {}. Retrying in {}
> ms. ({})", attempts, peer, waitms, e);
> 64 try
> 65 {
> 66 Thread.sleep(waitms);
> 67 }
> 68 catch (InterruptedException wtf)
> 69 {
> 70 throw new IOException("interrupted", wtf);
> 71 }
> 72 }
> 73 }
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (CASSANDRA-12330) Unreleased Resource: Sockets
[
https://issues.apache.org/jira/browse/CASSANDRA-12330?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15432130#comment-15432130
]
Arunkumar M commented on CASSANDRA-12330:
-
Yes, there is a way for doing this. The SocketException is already caught by
IOException.
Attached another patch.
> Unreleased Resource: Sockets
>
>
> Key: CASSANDRA-12330
> URL: https://issues.apache.org/jira/browse/CASSANDRA-12330
> Project: Cassandra
> Issue Type: Sub-task
>Reporter: Eduardo Aguinaga
>Assignee: Arunkumar M
> Labels: easyfix, newbie, patch
> Fix For: 3.x
>
> Attachments: 12330-3.0.txt, 12330-3.0.txt
>
>
> Overview:
> In May through June of 2016 a static analysis was performed on version 3.0.5
> of the Cassandra source code. The analysis included an automated analysis
> using HP Fortify v4.21 SCA and a manual analysis utilizing SciTools
> Understand v4. The results of that analysis includes the issue below.
> Issue:
> Sockets are low level resources that must be explicitly released so
> subsequent callers will have access to previously used sockets. In the file
> DefaultConnectionFactory.java on line 52 a socket is acquired and eventually
> returned to the caller on line 55.
> If an exception is thrown by any of the code between lines 52 and 55 the
> socket acquired on line 52 will not be released for subsequent reuse.
> DefaultConnectionFactory.java, lines 50-73:
> {code:java}
> 50 try
> 51 {
> 52 Socket socket = OutboundTcpConnectionPool.newSocket(peer);
> 53
> socket.setSoTimeout(DatabaseDescriptor.getStreamingSocketTimeout());
> 54 socket.setKeepAlive(true);
> 55 return socket;
> 56 }
> 57 catch (IOException e)
> 58 {
> 59 if (++attempts >= MAX_CONNECT_ATTEMPTS)
> 60 throw e;
> 61
> 62 long waitms = DatabaseDescriptor.getRpcTimeout() *
> (long)Math.pow(2, attempts);
> 63 logger.warn("Failed attempt {} to connect to {}. Retrying in {}
> ms. ({})", attempts, peer, waitms, e);
> 64 try
> 65 {
> 66 Thread.sleep(waitms);
> 67 }
> 68 catch (InterruptedException wtf)
> 69 {
> 70 throw new IOException("interrupted", wtf);
> 71 }
> 72 }
> 73 }
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
cassandra git commit: presize collection and fix duplicate assignment typo
Repository: cassandra
Updated Branches:
refs/heads/trunk 54ae900a5 -> 48d4f6080
presize collection and fix duplicate assignment typo
Project: http://git-wip-us.apache.org/repos/asf/cassandra/repo
Commit: http://git-wip-us.apache.org/repos/asf/cassandra/commit/48d4f608
Tree: http://git-wip-us.apache.org/repos/asf/cassandra/tree/48d4f608
Diff: http://git-wip-us.apache.org/repos/asf/cassandra/diff/48d4f608
Branch: refs/heads/trunk
Commit: 48d4f6080d882f9d08561f64fdbb5ab91dea080d
Parents: 54ae900
Author: Dave Brosius
Authored: Tue Aug 23 00:38:47 2016 -0400
Committer: Dave Brosius
Committed: Tue Aug 23 00:38:47 2016 -0400
--
src/java/org/apache/cassandra/db/SystemKeyspace.java | 5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)
--
http://git-wip-us.apache.org/repos/asf/cassandra/blob/48d4f608/src/java/org/apache/cassandra/db/SystemKeyspace.java
--
diff --git a/src/java/org/apache/cassandra/db/SystemKeyspace.java
b/src/java/org/apache/cassandra/db/SystemKeyspace.java
index c204e0a..b23729e 100644
--- a/src/java/org/apache/cassandra/db/SystemKeyspace.java
+++ b/src/java/org/apache/cassandra/db/SystemKeyspace.java
@@ -33,6 +33,7 @@ import com.google.common.collect.HashMultimap;
import com.google.common.collect.ImmutableMap;
import com.google.common.collect.ImmutableSet;
import com.google.common.collect.SetMultimap;
+import com.google.common.collect.Sets;
import com.google.common.io.ByteStreams;
import org.slf4j.Logger;
import org.slf4j.LoggerFactory;
@@ -1331,8 +1332,8 @@ public final class SystemKeyspace
for (UntypedResultSet.Row row : rs)
{
InetAddress peer = row.getInetAddress("peer");
-Set rawRanges = rawRanges = row.getSet("ranges",
BytesType.instance);
-Set> ranges = new HashSet<>();
+Set rawRanges = row.getSet("ranges",
BytesType.instance);
+Set> ranges =
Sets.newHashSetWithExpectedSize(rawRanges.size());
for (ByteBuffer rawRange : rawRanges)
{
ranges.add(byteBufferToRange(rawRange, partitioner));
[jira] [Commented] (CASSANDRA-12490) Add sequence distribution type to cassandra stress
[ https://issues.apache.org/jira/browse/CASSANDRA-12490?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15432105#comment-15432105 ] Ben Slater commented on CASSANDRA-12490: Nits look good to me. I think the example is sufficient - the ones I've used don't really illustrate anything additional. Thanks! > Add sequence distribution type to cassandra stress > -- > > Key: CASSANDRA-12490 > URL: https://issues.apache.org/jira/browse/CASSANDRA-12490 > Project: Cassandra > Issue Type: Improvement > Components: Tools >Reporter: Ben Slater >Assignee: Ben Slater >Priority: Minor > Fix For: 3.x > > Attachments: 12490-trunk.patch, cqlstress-seq-example.yaml > > > When using the write command, cassandra stress sequentially generates seeds. > This ensures generated values don't overlap (unless the sequence wraps) > providing more predictable number of inserted records (and generating a base > set of data without wasted writes). > When using a yaml stress spec there is no sequenced distribution available. > It think it would be useful to have this for doing initial load of data for > testing -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CASSANDRA-12490) Add sequence distribution type to cassandra stress
[ https://issues.apache.org/jira/browse/CASSANDRA-12490?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15432083#comment-15432083 ] Stefania commented on CASSANDRA-12490: -- Thanks for the updated patch, LGTM. I've created a branch with your patch and some nits. I've also started the CI jobs for trunk but they are still in a queue at the moment: |[patch|https://github.com/stef1927/cassandra/commits/12490]|[testall|http://cassci.datastax.com/view/Dev/view/stef1927/job/stef1927-12490-testall/]|[dtest|http://cassci.datastax.com/view/Dev/view/stef1927/job/stef1927-12490-dtest/]| If you are happy with the nits, and the CI results are good, I'll squash and commit. Do you think we should add a sample stress profile, I've used [this one|^cqlstress-seq-example.yaml] for testing, do you have a more realistic sample or is this one good enough? > Add sequence distribution type to cassandra stress > -- > > Key: CASSANDRA-12490 > URL: https://issues.apache.org/jira/browse/CASSANDRA-12490 > Project: Cassandra > Issue Type: Improvement > Components: Tools >Reporter: Ben Slater >Assignee: Ben Slater >Priority: Minor > Fix For: 3.x > > Attachments: 12490-trunk.patch, cqlstress-seq-example.yaml > > > When using the write command, cassandra stress sequentially generates seeds. > This ensures generated values don't overlap (unless the sequence wraps) > providing more predictable number of inserted records (and generating a base > set of data without wasted writes). > When using a yaml stress spec there is no sequenced distribution available. > It think it would be useful to have this for doing initial load of data for > testing -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CASSANDRA-12490) Add sequence distribution type to cassandra stress
[ https://issues.apache.org/jira/browse/CASSANDRA-12490?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefania updated CASSANDRA-12490: - Attachment: cqlstress-seq-example.yaml > Add sequence distribution type to cassandra stress > -- > > Key: CASSANDRA-12490 > URL: https://issues.apache.org/jira/browse/CASSANDRA-12490 > Project: Cassandra > Issue Type: Improvement > Components: Tools >Reporter: Ben Slater >Assignee: Ben Slater >Priority: Minor > Fix For: 3.x > > Attachments: 12490-trunk.patch, cqlstress-seq-example.yaml > > > When using the write command, cassandra stress sequentially generates seeds. > This ensures generated values don't overlap (unless the sequence wraps) > providing more predictable number of inserted records (and generating a base > set of data without wasted writes). > When using a yaml stress spec there is no sequenced distribution available. > It think it would be useful to have this for doing initial load of data for > testing -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CASSANDRA-12476) SyntaxException when COPY FROM Counter Table with Null value
[
https://issues.apache.org/jira/browse/CASSANDRA-12476?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15431974#comment-15431974
]
Stefania commented on CASSANDRA-12476:
--
Thank you Philip, all CI jobs have completed successfully now.
Just waiting for a reviewer and a +1 from [~ashraful] regarding inserting zeros
for unset counter values.
> SyntaxException when COPY FROM Counter Table with Null value
>
>
> Key: CASSANDRA-12476
> URL: https://issues.apache.org/jira/browse/CASSANDRA-12476
> Project: Cassandra
> Issue Type: Bug
> Components: Tools
>Reporter: Ashraful Islam
>Assignee: Stefania
>Priority: Minor
> Labels: cqlsh
> Fix For: 2.2.x, 3.0.x, 3.x
>
> Attachments:
> Fix_issue___CASSANDRA_12476__SyntaxException_when_COPY_FROM_Counter_Table_with_Null_value.patch
>
>
> I have a simple counter table
> {noformat}
> CREATE TABLE test (
> a int PRIMARY KEY,
> b counter,
> c counter
> ) ;
> {noformat}
> I have updated b column value with
> {noformat}
> UPDATE test SET b = b + 1 WHERE a = 1;
> {noformat}
> Now I have export the data with
> {noformat}
> COPY test TO 'test.csv';
> {noformat}
> And Import it with
> {noformat}
> COPY test FROM 'test.csv';
> {noformat}
> I get this Error
> {noformat}
> Failed to import 1 rows: SyntaxException - line 1:34 no viable alternative at
> input 'WHERE' (...=b+1,c=c+ [WHERE]...) - will retry later, attempt 1 of 5
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (CASSANDRA-11594) Too many open files on directories
[
https://issues.apache.org/jira/browse/CASSANDRA-11594?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15431966#comment-15431966
]
Stefania commented on CASSANDRA-11594:
--
Thanks, I don't think we need to bump any other ticket for now.
[~sean.mccarthy] is already working on CASSANDRA-11906, and there is a good
chance that it might be the same root cause. I left a comment on that ticket
with more details. So let's continue with 11906 for now and see what that gives.
I should also be able to start working on this myself in the next few days.
> Too many open files on directories
> --
>
> Key: CASSANDRA-11594
> URL: https://issues.apache.org/jira/browse/CASSANDRA-11594
> Project: Cassandra
> Issue Type: Bug
> Components: Core
>Reporter: n0rad
>Assignee: Stefania
>Priority: Critical
> Attachments: openfiles.zip, screenshot.png
>
>
> I have a 6 nodes cluster in prod in 3 racks.
> each node :
> - 4Gb commitlogs on 343 files
> - 275Gb data on 504 files
> On saturday, 1 node in each rack crash with with too many open files (seems
> to be the similar node in each rack).
> {code}
> lsof -n -p $PID give me 66899 out of 65826 max
> {code}
> it contains 64527 open directories (2371 uniq)
> a part of the list :
> {code}
> java19076 root 2140r DIR 8,17 143360 4386718705
> /opt/stage2/pod-cassandra-aci-cassandra/rootfs/data/keyspaces/email_logs_query/emails-2d4abd00e9ea11e591199d740e07bd95
> java19076 root 2141r DIR 8,17 143360 4386718705
> /opt/stage2/pod-cassandra-aci-cassandra/rootfs/data/keyspaces/email_logs_query/emails-2d4abd00e9ea11e591199d740e07bd95
> java19076 root 2142r DIR 8,17 143360 4386718705
> /opt/stage2/pod-cassandra-aci-cassandra/rootfs/data/keyspaces/email_logs_query/emails-2d4abd00e9ea11e591199d740e07bd95
> java19076 root 2143r DIR 8,17 143360 4386718705
> /opt/stage2/pod-cassandra-aci-cassandra/rootfs/data/keyspaces/email_logs_query/emails-2d4abd00e9ea11e591199d740e07bd95
> java19076 root 2144r DIR 8,17 143360 4386718705
> /opt/stage2/pod-cassandra-aci-cassandra/rootfs/data/keyspaces/email_logs_query/emails-2d4abd00e9ea11e591199d740e07bd95
> java19076 root 2145r DIR 8,17 143360 4386718705
> /opt/stage2/pod-cassandra-aci-cassandra/rootfs/data/keyspaces/email_logs_query/emails-2d4abd00e9ea11e591199d740e07bd95
> java19076 root 2146r DIR 8,17 143360 4386718705
> /opt/stage2/pod-cassandra-aci-cassandra/rootfs/data/keyspaces/email_logs_query/emails-2d4abd00e9ea11e591199d740e07bd95
> java19076 root 2147r DIR 8,17 143360 4386718705
> /opt/stage2/pod-cassandra-aci-cassandra/rootfs/data/keyspaces/email_logs_query/emails-2d4abd00e9ea11e591199d740e07bd95
> java19076 root 2148r DIR 8,17 143360 4386718705
> /opt/stage2/pod-cassandra-aci-cassandra/rootfs/data/keyspaces/email_logs_query/emails-2d4abd00e9ea11e591199d740e07bd95
> java19076 root 2149r DIR 8,17 143360 4386718705
> /opt/stage2/pod-cassandra-aci-cassandra/rootfs/data/keyspaces/email_logs_query/emails-2d4abd00e9ea11e591199d740e07bd95
> java19076 root 2150r DIR 8,17 143360 4386718705
> /opt/stage2/pod-cassandra-aci-cassandra/rootfs/data/keyspaces/email_logs_query/emails-2d4abd00e9ea11e591199d740e07bd95
> java19076 root 2151r DIR 8,17 143360 4386718705
> /opt/stage2/pod-cassandra-aci-cassandra/rootfs/data/keyspaces/email_logs_query/emails-2d4abd00e9ea11e591199d740e07bd95
> java19076 root 2152r DIR 8,17 143360 4386718705
> /opt/stage2/pod-cassandra-aci-cassandra/rootfs/data/keyspaces/email_logs_query/emails-2d4abd00e9ea11e591199d740e07bd95
> java19076 root 2153r DIR 8,17 143360 4386718705
> /opt/stage2/pod-cassandra-aci-cassandra/rootfs/data/keyspaces/email_logs_query/emails-2d4abd00e9ea11e591199d740e07bd95
> java19076 root 2154r DIR 8,17 143360 4386718705
> /opt/stage2/pod-cassandra-aci-cassandra/rootfs/data/keyspaces/email_logs_query/emails-2d4abd00e9ea11e591199d740e07bd95
> java19076 root 2155r DIR 8,17 143360 4386718705
> /opt/stage2/pod-cassandra-aci-cassandra/rootfs/data/keyspaces/email_logs_query/emails-2d4abd00e9ea11e591199d740e07bd95
> {code}
> The 3 others nodes crashes 4 hours later
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (CASSANDRA-12471) Allow for some form of "unset" in CQL's COPY command.
[
https://issues.apache.org/jira/browse/CASSANDRA-12471?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15431961#comment-15431961
]
Stefania commented on CASSANDRA-12471:
--
Thanks for the clarification.
UNSET values were introduced by CASSANDRA-7304 and
[PYTHON-317|https://datastax-oss.atlassian.net/browse/PYTHON-317].
I checked the cqlsh COPY code, and it is passing {{None}} for prepared
statements, and {{None}} does not get converted to {{Query.UNSET}} by the
driver. So we should be able to change this, by adding a new option. If this
option is set, it should be sufficient to change the return value for prepared
statements of [this
method|https://github.com/stef1927/cassandra/blob/cassandra-2.2/pylib/cqlshlib/copyutil.py#L1977].
> Allow for some form of "unset" in CQL's COPY command.
> -
>
> Key: CASSANDRA-12471
> URL: https://issues.apache.org/jira/browse/CASSANDRA-12471
> Project: Cassandra
> Issue Type: New Feature
> Components: CQL
>Reporter: Nate Sanders
>Priority: Minor
> Fix For: 2.2.0
>
>
> Currently, it looks like there's no way to get "unset" values via the COPY
> command, say, for example with empty string fields. Instead, these create
> tombstones.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Assigned] (CASSANDRA-12471) Allow for some form of "unset" in CQL's COPY command.
[ https://issues.apache.org/jira/browse/CASSANDRA-12471?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefania reassigned CASSANDRA-12471: Assignee: Stefania > Allow for some form of "unset" in CQL's COPY command. > - > > Key: CASSANDRA-12471 > URL: https://issues.apache.org/jira/browse/CASSANDRA-12471 > Project: Cassandra > Issue Type: New Feature > Components: CQL >Reporter: Nate Sanders >Assignee: Stefania >Priority: Minor > Fix For: 2.2.0 > > > Currently, it looks like there's no way to get "unset" values via the COPY > command, say, for example with empty string fields. Instead, these create > tombstones. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CASSANDRA-10797) Bootstrap new node fails with OOM when streaming nodes contains thousands of sstables
[
https://issues.apache.org/jira/browse/CASSANDRA-10797?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15431882#comment-15431882
]
Paulo Motta commented on CASSANDRA-10797:
-
no, because the implementation has a dependency (transactional system) which is
just present on 3.0+, so you probably need to upgrade to fix this (or perhaps
port the 2.1 patch to 2.2 if you're feeling adventurous).
> Bootstrap new node fails with OOM when streaming nodes contains thousands of
> sstables
> -
>
> Key: CASSANDRA-10797
> URL: https://issues.apache.org/jira/browse/CASSANDRA-10797
> Project: Cassandra
> Issue Type: Bug
> Components: Streaming and Messaging
> Environment: Cassandra 2.1.8.621 w/G1GC
>Reporter: Jose Martinez Poblete
>Assignee: Paulo Motta
> Fix For: 3.0.3, 3.2
>
> Attachments: 10797-nonpatched.png, 10797-patched.png,
> 10798-nonpatched-500M.png, 10798-patched-500M.png, 112415_system.log,
> Heapdump_OOM.zip, Screen Shot 2015-12-01 at 7.34.40 PM.png, dtest.tar.gz
>
>
> When adding a new node to an existing DC, it runs OOM after 25-45 minutes
> Upon heapdump revision, it is found the sending nodes are streaming thousands
> of sstables which in turns blows the bootstrapping node heap
> {noformat}
> ERROR [RMI Scheduler(0)] 2015-11-24 10:10:44,585
> JVMStabilityInspector.java:94 - JVM state determined to be unstable. Exiting
> forcefully due to:
> java.lang.OutOfMemoryError: Java heap space
> ERROR [STREAM-IN-/173.36.28.148] 2015-11-24 10:10:44,585
> StreamSession.java:502 - [Stream #0bb13f50-92cb-11e5-bc8d-f53b7528ffb4]
> Streaming error occurred
> java.lang.IllegalStateException: Shutdown in progress
> at
> java.lang.ApplicationShutdownHooks.remove(ApplicationShutdownHooks.java:82)
> ~[na:1.8.0_65]
> at java.lang.Runtime.removeShutdownHook(Runtime.java:239)
> ~[na:1.8.0_65]
> at
> org.apache.cassandra.service.StorageService.removeShutdownHook(StorageService.java:747)
> ~[cassandra-all-2.1.8.621.jar:2.1.8.621]
> at
> org.apache.cassandra.utils.JVMStabilityInspector$Killer.killCurrentJVM(JVMStabilityInspector.java:95)
> ~[cassandra-all-2.1.8.621.jar:2.1.8.621]
> at
> org.apache.cassandra.utils.JVMStabilityInspector.inspectThrowable(JVMStabilityInspector.java:64)
> ~[cassandra-all-2.1.8.621.jar:2.1.8.621]
> at
> org.apache.cassandra.streaming.messages.IncomingFileMessage$1.deserialize(IncomingFileMessage.java:66)
> ~[cassandra-all-2.1.8.621.jar:2.1.8.621]
> at
> org.apache.cassandra.streaming.messages.IncomingFileMessage$1.deserialize(IncomingFileMessage.java:38)
> ~[cassandra-all-2.1.8.621.jar:2.1.8.621]
> at
> org.apache.cassandra.streaming.messages.StreamMessage.deserialize(StreamMessage.java:55)
> ~[cassandra-all-2.1.8.621.jar:2.1.8.621]
> at
> org.apache.cassandra.streaming.ConnectionHandler$IncomingMessageHandler.run(ConnectionHandler.java:250)
> ~[cassandra-all-2.1.8.621.jar:2.1.8.621]
> at java.lang.Thread.run(Thread.java:745) [na:1.8.0_65]
> ERROR [RMI TCP Connection(idle)] 2015-11-24 10:10:44,585
> JVMStabilityInspector.java:94 - JVM state determined to be unstable. Exiting
> forcefully due to:
> java.lang.OutOfMemoryError: Java heap space
> ERROR [OptionalTasks:1] 2015-11-24 10:10:44,585 CassandraDaemon.java:223 -
> Exception in thread Thread[OptionalTasks:1,5,main]
> java.lang.IllegalStateException: Shutdown in progress
> {noformat}
> Attached is the Eclipse MAT report as a zipped web page
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Comment Edited] (CASSANDRA-10797) Bootstrap new node fails with OOM when streaming nodes contains thousands of sstables
[
https://issues.apache.org/jira/browse/CASSANDRA-10797?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15431861#comment-15431861
]
Simon Zhou edited comment on CASSANDRA-10797 at 8/23/16 12:29 AM:
--
[~pauloricardomg], we hit the issue in 2.2.5. You said you're going to fix that
in Cassandra 2.2. Is this still the plan? Thanks.
was (Author: szhou):
[~pauloricardomg], you said you're going to fix that in Cassandra 2.2. Is this
still the plan? Thanks.
> Bootstrap new node fails with OOM when streaming nodes contains thousands of
> sstables
> -
>
> Key: CASSANDRA-10797
> URL: https://issues.apache.org/jira/browse/CASSANDRA-10797
> Project: Cassandra
> Issue Type: Bug
> Components: Streaming and Messaging
> Environment: Cassandra 2.1.8.621 w/G1GC
>Reporter: Jose Martinez Poblete
>Assignee: Paulo Motta
> Fix For: 3.0.3, 3.2
>
> Attachments: 10797-nonpatched.png, 10797-patched.png,
> 10798-nonpatched-500M.png, 10798-patched-500M.png, 112415_system.log,
> Heapdump_OOM.zip, Screen Shot 2015-12-01 at 7.34.40 PM.png, dtest.tar.gz
>
>
> When adding a new node to an existing DC, it runs OOM after 25-45 minutes
> Upon heapdump revision, it is found the sending nodes are streaming thousands
> of sstables which in turns blows the bootstrapping node heap
> {noformat}
> ERROR [RMI Scheduler(0)] 2015-11-24 10:10:44,585
> JVMStabilityInspector.java:94 - JVM state determined to be unstable. Exiting
> forcefully due to:
> java.lang.OutOfMemoryError: Java heap space
> ERROR [STREAM-IN-/173.36.28.148] 2015-11-24 10:10:44,585
> StreamSession.java:502 - [Stream #0bb13f50-92cb-11e5-bc8d-f53b7528ffb4]
> Streaming error occurred
> java.lang.IllegalStateException: Shutdown in progress
> at
> java.lang.ApplicationShutdownHooks.remove(ApplicationShutdownHooks.java:82)
> ~[na:1.8.0_65]
> at java.lang.Runtime.removeShutdownHook(Runtime.java:239)
> ~[na:1.8.0_65]
> at
> org.apache.cassandra.service.StorageService.removeShutdownHook(StorageService.java:747)
> ~[cassandra-all-2.1.8.621.jar:2.1.8.621]
> at
> org.apache.cassandra.utils.JVMStabilityInspector$Killer.killCurrentJVM(JVMStabilityInspector.java:95)
> ~[cassandra-all-2.1.8.621.jar:2.1.8.621]
> at
> org.apache.cassandra.utils.JVMStabilityInspector.inspectThrowable(JVMStabilityInspector.java:64)
> ~[cassandra-all-2.1.8.621.jar:2.1.8.621]
> at
> org.apache.cassandra.streaming.messages.IncomingFileMessage$1.deserialize(IncomingFileMessage.java:66)
> ~[cassandra-all-2.1.8.621.jar:2.1.8.621]
> at
> org.apache.cassandra.streaming.messages.IncomingFileMessage$1.deserialize(IncomingFileMessage.java:38)
> ~[cassandra-all-2.1.8.621.jar:2.1.8.621]
> at
> org.apache.cassandra.streaming.messages.StreamMessage.deserialize(StreamMessage.java:55)
> ~[cassandra-all-2.1.8.621.jar:2.1.8.621]
> at
> org.apache.cassandra.streaming.ConnectionHandler$IncomingMessageHandler.run(ConnectionHandler.java:250)
> ~[cassandra-all-2.1.8.621.jar:2.1.8.621]
> at java.lang.Thread.run(Thread.java:745) [na:1.8.0_65]
> ERROR [RMI TCP Connection(idle)] 2015-11-24 10:10:44,585
> JVMStabilityInspector.java:94 - JVM state determined to be unstable. Exiting
> forcefully due to:
> java.lang.OutOfMemoryError: Java heap space
> ERROR [OptionalTasks:1] 2015-11-24 10:10:44,585 CassandraDaemon.java:223 -
> Exception in thread Thread[OptionalTasks:1,5,main]
> java.lang.IllegalStateException: Shutdown in progress
> {noformat}
> Attached is the Eclipse MAT report as a zipped web page
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (CASSANDRA-10797) Bootstrap new node fails with OOM when streaming nodes contains thousands of sstables
[
https://issues.apache.org/jira/browse/CASSANDRA-10797?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15431861#comment-15431861
]
Simon Zhou commented on CASSANDRA-10797:
[~pauloricardomg], you said you're going to fix that in Cassandra 2.2. Is this
still the plan? Thanks.
> Bootstrap new node fails with OOM when streaming nodes contains thousands of
> sstables
> -
>
> Key: CASSANDRA-10797
> URL: https://issues.apache.org/jira/browse/CASSANDRA-10797
> Project: Cassandra
> Issue Type: Bug
> Components: Streaming and Messaging
> Environment: Cassandra 2.1.8.621 w/G1GC
>Reporter: Jose Martinez Poblete
>Assignee: Paulo Motta
> Fix For: 3.0.3, 3.2
>
> Attachments: 10797-nonpatched.png, 10797-patched.png,
> 10798-nonpatched-500M.png, 10798-patched-500M.png, 112415_system.log,
> Heapdump_OOM.zip, Screen Shot 2015-12-01 at 7.34.40 PM.png, dtest.tar.gz
>
>
> When adding a new node to an existing DC, it runs OOM after 25-45 minutes
> Upon heapdump revision, it is found the sending nodes are streaming thousands
> of sstables which in turns blows the bootstrapping node heap
> {noformat}
> ERROR [RMI Scheduler(0)] 2015-11-24 10:10:44,585
> JVMStabilityInspector.java:94 - JVM state determined to be unstable. Exiting
> forcefully due to:
> java.lang.OutOfMemoryError: Java heap space
> ERROR [STREAM-IN-/173.36.28.148] 2015-11-24 10:10:44,585
> StreamSession.java:502 - [Stream #0bb13f50-92cb-11e5-bc8d-f53b7528ffb4]
> Streaming error occurred
> java.lang.IllegalStateException: Shutdown in progress
> at
> java.lang.ApplicationShutdownHooks.remove(ApplicationShutdownHooks.java:82)
> ~[na:1.8.0_65]
> at java.lang.Runtime.removeShutdownHook(Runtime.java:239)
> ~[na:1.8.0_65]
> at
> org.apache.cassandra.service.StorageService.removeShutdownHook(StorageService.java:747)
> ~[cassandra-all-2.1.8.621.jar:2.1.8.621]
> at
> org.apache.cassandra.utils.JVMStabilityInspector$Killer.killCurrentJVM(JVMStabilityInspector.java:95)
> ~[cassandra-all-2.1.8.621.jar:2.1.8.621]
> at
> org.apache.cassandra.utils.JVMStabilityInspector.inspectThrowable(JVMStabilityInspector.java:64)
> ~[cassandra-all-2.1.8.621.jar:2.1.8.621]
> at
> org.apache.cassandra.streaming.messages.IncomingFileMessage$1.deserialize(IncomingFileMessage.java:66)
> ~[cassandra-all-2.1.8.621.jar:2.1.8.621]
> at
> org.apache.cassandra.streaming.messages.IncomingFileMessage$1.deserialize(IncomingFileMessage.java:38)
> ~[cassandra-all-2.1.8.621.jar:2.1.8.621]
> at
> org.apache.cassandra.streaming.messages.StreamMessage.deserialize(StreamMessage.java:55)
> ~[cassandra-all-2.1.8.621.jar:2.1.8.621]
> at
> org.apache.cassandra.streaming.ConnectionHandler$IncomingMessageHandler.run(ConnectionHandler.java:250)
> ~[cassandra-all-2.1.8.621.jar:2.1.8.621]
> at java.lang.Thread.run(Thread.java:745) [na:1.8.0_65]
> ERROR [RMI TCP Connection(idle)] 2015-11-24 10:10:44,585
> JVMStabilityInspector.java:94 - JVM state determined to be unstable. Exiting
> forcefully due to:
> java.lang.OutOfMemoryError: Java heap space
> ERROR [OptionalTasks:1] 2015-11-24 10:10:44,585 CassandraDaemon.java:223 -
> Exception in thread Thread[OptionalTasks:1,5,main]
> java.lang.IllegalStateException: Shutdown in progress
> {noformat}
> Attached is the Eclipse MAT report as a zipped web page
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (CASSANDRA-6216) Level Compaction should persist last compacted key per level
[ https://issues.apache.org/jira/browse/CASSANDRA-6216?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15431816#comment-15431816 ] Dikang Gu commented on CASSANDRA-6216: -- [~krummas], thanks for the review! Addressed your comments and here are the latest patch, https://github.com/DikangGu/cassandra/commit/928a9ea5621c1405c5ac07f4dc26c616206277cf. I also manually tested it, seems fine. > Level Compaction should persist last compacted key per level > > > Key: CASSANDRA-6216 > URL: https://issues.apache.org/jira/browse/CASSANDRA-6216 > Project: Cassandra > Issue Type: Sub-task >Reporter: sankalp kohli >Assignee: Dikang Gu >Priority: Minor > Labels: compaction, lcs > Attachments: JIRA-6216.diff > > > Level compaction does not persist the last compacted key per level. This is > important for higher levels. > The sstables with higher token and in higher levels wont get a chance to > compact as the last compacted key will get reset after a restart. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CASSANDRA-12330) Unreleased Resource: Sockets
[
https://issues.apache.org/jira/browse/CASSANDRA-12330?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15431708#comment-15431708
]
Yuki Morishita commented on CASSANDRA-12330:
Isn't it better to handle closing socket in the same {{catch}} block as
{{IOException}}?
> Unreleased Resource: Sockets
>
>
> Key: CASSANDRA-12330
> URL: https://issues.apache.org/jira/browse/CASSANDRA-12330
> Project: Cassandra
> Issue Type: Sub-task
>Reporter: Eduardo Aguinaga
>Assignee: Arunkumar M
> Labels: easyfix, newbie, patch
> Fix For: 3.x
>
> Attachments: 12330-3.0.txt
>
>
> Overview:
> In May through June of 2016 a static analysis was performed on version 3.0.5
> of the Cassandra source code. The analysis included an automated analysis
> using HP Fortify v4.21 SCA and a manual analysis utilizing SciTools
> Understand v4. The results of that analysis includes the issue below.
> Issue:
> Sockets are low level resources that must be explicitly released so
> subsequent callers will have access to previously used sockets. In the file
> DefaultConnectionFactory.java on line 52 a socket is acquired and eventually
> returned to the caller on line 55.
> If an exception is thrown by any of the code between lines 52 and 55 the
> socket acquired on line 52 will not be released for subsequent reuse.
> DefaultConnectionFactory.java, lines 50-73:
> {code:java}
> 50 try
> 51 {
> 52 Socket socket = OutboundTcpConnectionPool.newSocket(peer);
> 53
> socket.setSoTimeout(DatabaseDescriptor.getStreamingSocketTimeout());
> 54 socket.setKeepAlive(true);
> 55 return socket;
> 56 }
> 57 catch (IOException e)
> 58 {
> 59 if (++attempts >= MAX_CONNECT_ATTEMPTS)
> 60 throw e;
> 61
> 62 long waitms = DatabaseDescriptor.getRpcTimeout() *
> (long)Math.pow(2, attempts);
> 63 logger.warn("Failed attempt {} to connect to {}. Retrying in {}
> ms. ({})", attempts, peer, waitms, e);
> 64 try
> 65 {
> 66 Thread.sleep(waitms);
> 67 }
> 68 catch (InterruptedException wtf)
> 69 {
> 70 throw new IOException("interrupted", wtf);
> 71 }
> 72 }
> 73 }
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (CASSANDRA-11866) nodetool repair does not obey the column family parameter when -st and -et are provided (subrange repair)
[
https://issues.apache.org/jira/browse/CASSANDRA-11866?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yuki Morishita updated CASSANDRA-11866:
---
Resolution: Fixed
Fix Version/s: (was: 2.1.x)
2.1.16
Status: Resolved (was: Ready to Commit)
Committed to 2.1 as {{95b2d0241c114fdb37f9b3e30c981ce7aa39e177}}.
> nodetool repair does not obey the column family parameter when -st and -et
> are provided (subrange repair)
> -
>
> Key: CASSANDRA-11866
> URL: https://issues.apache.org/jira/browse/CASSANDRA-11866
> Project: Cassandra
> Issue Type: Bug
> Components: Tools
> Environment: Red Hat Enterprise Linux Server release 6.7 (Santiago)
> x86_64
>Reporter: Shiva Venkateswaran
>Assignee: Vinay Chella
> Labels: newbie
> Fix For: 2.1.16
>
> Attachments: 0001-CASSANDRA-11866-dtest.patch, 11866-2.1.txt
>
>
> Command 1: Repairs all the CFs in ADL_GLOBAL keyspace and ignores the
> parameter AssetModifyTimes_data used to restrict the CFs
> Executing: /aladdin/local/apps/apache-cassandra-2.1.8a/bin/nodetool -h
> localhost -p 7199 -u user-pw ** repair ADL_GLOBAL AssetModifyTimes_data
> -st 205279477618143669 -et 230991685737746901 -par
> [2016-05-20 17:31:39,116] Starting repair command #9, repairing 1 ranges for
> keyspace ADL_GLOBAL (parallelism=PARALLEL, full=true)
> [2016-05-20 17:32:21,568] Repair session 3cae2530-1ed2-11e6-b490-d9df6932c7cf
> for range (205279477618143669,230991685737746901] finished
> Command 2: Repairs all the CFs in ADL_GLOBAL keyspace and ignores the
> parameter AssetModifyTimes_data used to restrict the CFs
> Executing: /aladdin/local/apps/apache-cassandra-2.1.8a/bin/nodetool -h
> localhost -p 7199 -u controlRole -pw ** repair -st 205279477618143669 -et
> 230991685737746901 -par -- ADL_GLOBAL AssetModifyTimes_data
> [2016-05-20 17:36:34,473] Starting repair command #10, repairing 1 ranges for
> keyspace ADL_GLOBAL (parallelism=PARALLEL, full=true)
> [2016-05-20 17:37:15,365] Repair session ecb996d0-1ed2-11e6-b490-d9df6932c7cf
> for range (205279477618143669,230991685737746901] finished
> [2016-05-20 17:37:15,365] Repair command #10 finished
> Command 3: Repairs only the CF ADL3Test1_data in keyspace ADL_GLOBAL
> Executing: /aladdin/local/apps/apache-cassandra-2.1.8a/bin/nodetool -h
> localhost -p 7199 -u controlRole -pw ** repair -- ADL_GLOBAL
> ADL3Test1_data
> [2016-05-20 17:38:35,781] Starting repair command #11, repairing 1043 ranges
> for keyspace ADL_GLOBAL (parallelism=SEQUENTIAL, full=true)
> [2016-05-20 17:42:32,682] Repair session 3c8af050-1ed3-11e6-b490-d9df6932c7cf
> for range (6241639152751626129,6241693909092643958] finished
> [2016-05-20 17:42:32,683] Repair session 3caf1a20-1ed3-11e6-b490-d9df6932c7cf
> for range (-7096993048358106082,-7095000706885780850] finished
> [2016-05-20 17:42:32,683] Repair session 3ccfc180-1ed3-11e6-b490-d9df6932c7cf
> for range (-7218939248114487080,-7218289345961492809] finished
> [2016-05-20 17:42:32,683] Repair session 3cf21690-1ed3-11e6-b490-d9df6932c7cf
> for range (-5244794756638190874,-5190307341355030282] finished
> [2016-05-20 17:42:32,683] Repair session 3d126fd0-1ed3-11e6-b490-d9df6932c7cf
> for range (3551629701277971766,321736534916502] finished
> [2016-05-20 17:42:32,683] Repair session 3d32f020-1ed3-11e6-b490-d9df6932c7cf
> for range (-8139355591560661944,-8127928369093576603] finished
> [2016-05-20 17:42:32,683] Repair session 3d537070-1ed3-11e6-b490-d9df6932c7cf
> for range (7098010153980465751,7100863011896759020] finished
> [2016-05-20 17:42:32,683] Repair session 3d73f0c0-1ed3-11e6-b490-d9df6932c7cf
> for range (1004538726866173536,1008586133746764703] finished
> [2016-05-20 17:42:32,683] Repair session 3d947110-1ed3-11e6-b490-d9df6932c7cf
> for range (5770817093573726645,5771418910784831587] finished
> .
> .
> .
> [2016-05-20 17:42:32,732] Repair command #11 finished
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[05/21] cassandra git commit: Include column family parameter when -st and -et are provided - subrange repair
Include column family parameter when -st and -et are provided - subrange repair Patch by Vinay Chella; Reviewed by Paulo Motta for CASSANDRA-11866 Project: http://git-wip-us.apache.org/repos/asf/cassandra/repo Commit: http://git-wip-us.apache.org/repos/asf/cassandra/commit/95b2d024 Tree: http://git-wip-us.apache.org/repos/asf/cassandra/tree/95b2d024 Diff: http://git-wip-us.apache.org/repos/asf/cassandra/diff/95b2d024 Branch: refs/heads/cassandra-3.8 Commit: 95b2d0241c114fdb37f9b3e30c981ce7aa39e177 Parents: 527d189 Author: vchella Authored: Tue Jul 19 18:47:01 2016 -0700 Committer: Yuki Morishita Committed: Mon Aug 22 16:36:54 2016 -0500 -- CHANGES.txt | 1 + src/java/org/apache/cassandra/tools/NodeTool.java | 2 +- 2 files changed, 2 insertions(+), 1 deletion(-) -- http://git-wip-us.apache.org/repos/asf/cassandra/blob/95b2d024/CHANGES.txt -- diff --git a/CHANGES.txt b/CHANGES.txt index dee669a..c1c6c78 100644 --- a/CHANGES.txt +++ b/CHANGES.txt @@ -1,4 +1,5 @@ 2.1.16 + * Include column family parameter when -st and -et are provided (CASSANDRA-11866) * Fix queries with empty ByteBuffer values in clustering column restrictions (CASSANDRA-12127) * Disable passing control to post-flush after flush failure to prevent data loss (CASSANDRA-11828) * Allow STCS-in-L0 compactions to reduce scope with LCS (CASSANDRA-12040) http://git-wip-us.apache.org/repos/asf/cassandra/blob/95b2d024/src/java/org/apache/cassandra/tools/NodeTool.java -- diff --git a/src/java/org/apache/cassandra/tools/NodeTool.java b/src/java/org/apache/cassandra/tools/NodeTool.java index 5af8240..d1afb6f 100644 --- a/src/java/org/apache/cassandra/tools/NodeTool.java +++ b/src/java/org/apache/cassandra/tools/NodeTool.java @@ -1947,7 +1947,7 @@ public class NodeTool else if(!specificHosts.isEmpty()) hosts = newArrayList(specificHosts); if (!startToken.isEmpty() || !endToken.isEmpty()) -probe.forceRepairRangeAsync(System.out, keyspace, parallelismDegree, dataCenters,hosts, startToken, endToken, !incrementalRepair); +probe.forceRepairRangeAsync(System.out, keyspace, parallelismDegree, dataCenters,hosts, startToken, endToken, !incrementalRepair, cfnames); else probe.forceRepairAsync(System.out, keyspace, parallelismDegree, dataCenters, hosts, primaryRange, !incrementalRepair, cfnames); } catch (Exception e)
[21/21] cassandra git commit: Merge branch 'cassandra-3.9' into trunk
Merge branch 'cassandra-3.9' into trunk Project: http://git-wip-us.apache.org/repos/asf/cassandra/repo Commit: http://git-wip-us.apache.org/repos/asf/cassandra/commit/54ae900a Tree: http://git-wip-us.apache.org/repos/asf/cassandra/tree/54ae900a Diff: http://git-wip-us.apache.org/repos/asf/cassandra/diff/54ae900a Branch: refs/heads/trunk Commit: 54ae900a5eba7c9de9f42cb18968d05caf17056c Parents: 4c84d40 a592693 Author: Yuki Morishita Authored: Mon Aug 22 17:04:14 2016 -0500 Committer: Yuki Morishita Committed: Mon Aug 22 17:04:14 2016 -0500 -- --
[19/21] cassandra git commit: Merge branch 'cassandra-3.8' into cassandra-3.9
Merge branch 'cassandra-3.8' into cassandra-3.9 Project: http://git-wip-us.apache.org/repos/asf/cassandra/repo Commit: http://git-wip-us.apache.org/repos/asf/cassandra/commit/a592693d Tree: http://git-wip-us.apache.org/repos/asf/cassandra/tree/a592693d Diff: http://git-wip-us.apache.org/repos/asf/cassandra/diff/a592693d Branch: refs/heads/cassandra-3.9 Commit: a592693dd0fed2d6b2f18ec3fa0164b2cd4178d7 Parents: bd2b73b 027400c Author: Yuki Morishita Authored: Mon Aug 22 17:04:07 2016 -0500 Committer: Yuki Morishita Committed: Mon Aug 22 17:04:07 2016 -0500 -- --
[14/21] cassandra git commit: Merge branch 'cassandra-2.2' into cassandra-3.0
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/f255370f Tree: http://git-wip-us.apache.org/repos/asf/cassandra/tree/f255370f Diff: http://git-wip-us.apache.org/repos/asf/cassandra/diff/f255370f Branch: refs/heads/cassandra-3.0 Commit: f255370f316e3c19bfbb99649f9dcd5a4bd39c22 Parents: a86ddac 93ad056 Author: Yuki Morishita Authored: Mon Aug 22 16:40:05 2016 -0500 Committer: Yuki Morishita Committed: Mon Aug 22 16:40:05 2016 -0500 -- --
[11/21] cassandra git commit: Merge branch 'cassandra-2.1' into cassandra-2.2
Merge branch 'cassandra-2.1' into cassandra-2.2 Project: http://git-wip-us.apache.org/repos/asf/cassandra/repo Commit: http://git-wip-us.apache.org/repos/asf/cassandra/commit/93ad056e Tree: http://git-wip-us.apache.org/repos/asf/cassandra/tree/93ad056e Diff: http://git-wip-us.apache.org/repos/asf/cassandra/diff/93ad056e Branch: refs/heads/cassandra-3.8 Commit: 93ad056ede2e5d573d12eb9d51a0e18ab2c4762f Parents: 59da275 95b2d02 Author: Yuki Morishita Authored: Mon Aug 22 16:39:53 2016 -0500 Committer: Yuki Morishita Committed: Mon Aug 22 16:39:53 2016 -0500 -- --
[02/21] cassandra git commit: Include column family parameter when -st and -et are provided - subrange repair
Include column family parameter when -st and -et are provided - subrange repair Patch by Vinay Chella; Reviewed by Paulo Motta for CASSANDRA-11866 Project: http://git-wip-us.apache.org/repos/asf/cassandra/repo Commit: http://git-wip-us.apache.org/repos/asf/cassandra/commit/95b2d024 Tree: http://git-wip-us.apache.org/repos/asf/cassandra/tree/95b2d024 Diff: http://git-wip-us.apache.org/repos/asf/cassandra/diff/95b2d024 Branch: refs/heads/cassandra-2.2 Commit: 95b2d0241c114fdb37f9b3e30c981ce7aa39e177 Parents: 527d189 Author: vchella Authored: Tue Jul 19 18:47:01 2016 -0700 Committer: Yuki Morishita Committed: Mon Aug 22 16:36:54 2016 -0500 -- CHANGES.txt | 1 + src/java/org/apache/cassandra/tools/NodeTool.java | 2 +- 2 files changed, 2 insertions(+), 1 deletion(-) -- http://git-wip-us.apache.org/repos/asf/cassandra/blob/95b2d024/CHANGES.txt -- diff --git a/CHANGES.txt b/CHANGES.txt index dee669a..c1c6c78 100644 --- a/CHANGES.txt +++ b/CHANGES.txt @@ -1,4 +1,5 @@ 2.1.16 + * Include column family parameter when -st and -et are provided (CASSANDRA-11866) * Fix queries with empty ByteBuffer values in clustering column restrictions (CASSANDRA-12127) * Disable passing control to post-flush after flush failure to prevent data loss (CASSANDRA-11828) * Allow STCS-in-L0 compactions to reduce scope with LCS (CASSANDRA-12040) http://git-wip-us.apache.org/repos/asf/cassandra/blob/95b2d024/src/java/org/apache/cassandra/tools/NodeTool.java -- diff --git a/src/java/org/apache/cassandra/tools/NodeTool.java b/src/java/org/apache/cassandra/tools/NodeTool.java index 5af8240..d1afb6f 100644 --- a/src/java/org/apache/cassandra/tools/NodeTool.java +++ b/src/java/org/apache/cassandra/tools/NodeTool.java @@ -1947,7 +1947,7 @@ public class NodeTool else if(!specificHosts.isEmpty()) hosts = newArrayList(specificHosts); if (!startToken.isEmpty() || !endToken.isEmpty()) -probe.forceRepairRangeAsync(System.out, keyspace, parallelismDegree, dataCenters,hosts, startToken, endToken, !incrementalRepair); +probe.forceRepairRangeAsync(System.out, keyspace, parallelismDegree, dataCenters,hosts, startToken, endToken, !incrementalRepair, cfnames); else probe.forceRepairAsync(System.out, keyspace, parallelismDegree, dataCenters, hosts, primaryRange, !incrementalRepair, cfnames); } catch (Exception e)
[09/21] cassandra git commit: Merge branch 'cassandra-2.1' into cassandra-2.2
Merge branch 'cassandra-2.1' into cassandra-2.2 Project: http://git-wip-us.apache.org/repos/asf/cassandra/repo Commit: http://git-wip-us.apache.org/repos/asf/cassandra/commit/93ad056e Tree: http://git-wip-us.apache.org/repos/asf/cassandra/tree/93ad056e Diff: http://git-wip-us.apache.org/repos/asf/cassandra/diff/93ad056e Branch: refs/heads/trunk Commit: 93ad056ede2e5d573d12eb9d51a0e18ab2c4762f Parents: 59da275 95b2d02 Author: Yuki Morishita Authored: Mon Aug 22 16:39:53 2016 -0500 Committer: Yuki Morishita Committed: Mon Aug 22 16:39:53 2016 -0500 -- --
[13/21] cassandra git commit: Merge branch 'cassandra-2.2' into cassandra-3.0
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/f255370f Tree: http://git-wip-us.apache.org/repos/asf/cassandra/tree/f255370f Diff: http://git-wip-us.apache.org/repos/asf/cassandra/diff/f255370f Branch: refs/heads/cassandra-3.9 Commit: f255370f316e3c19bfbb99649f9dcd5a4bd39c22 Parents: a86ddac 93ad056 Author: Yuki Morishita Authored: Mon Aug 22 16:40:05 2016 -0500 Committer: Yuki Morishita Committed: Mon Aug 22 16:40:05 2016 -0500 -- --
[16/21] cassandra git commit: Merge branch 'cassandra-3.0' into cassandra-3.8
Merge branch 'cassandra-3.0' into cassandra-3.8 Project: http://git-wip-us.apache.org/repos/asf/cassandra/repo Commit: http://git-wip-us.apache.org/repos/asf/cassandra/commit/027400ce Tree: http://git-wip-us.apache.org/repos/asf/cassandra/tree/027400ce Diff: http://git-wip-us.apache.org/repos/asf/cassandra/diff/027400ce Branch: refs/heads/cassandra-3.8 Commit: 027400ceb5ccd5f97b8f71e36e4f2b0f2518ad46 Parents: 2b8672d f255370 Author: Yuki Morishita Authored: Mon Aug 22 17:03:57 2016 -0500 Committer: Yuki Morishita Committed: Mon Aug 22 17:03:57 2016 -0500 -- --
[04/21] cassandra git commit: Include column family parameter when -st and -et are provided - subrange repair
Include column family parameter when -st and -et are provided - subrange repair Patch by Vinay Chella; Reviewed by Paulo Motta for CASSANDRA-11866 Project: http://git-wip-us.apache.org/repos/asf/cassandra/repo Commit: http://git-wip-us.apache.org/repos/asf/cassandra/commit/95b2d024 Tree: http://git-wip-us.apache.org/repos/asf/cassandra/tree/95b2d024 Diff: http://git-wip-us.apache.org/repos/asf/cassandra/diff/95b2d024 Branch: refs/heads/cassandra-3.0 Commit: 95b2d0241c114fdb37f9b3e30c981ce7aa39e177 Parents: 527d189 Author: vchella Authored: Tue Jul 19 18:47:01 2016 -0700 Committer: Yuki Morishita Committed: Mon Aug 22 16:36:54 2016 -0500 -- CHANGES.txt | 1 + src/java/org/apache/cassandra/tools/NodeTool.java | 2 +- 2 files changed, 2 insertions(+), 1 deletion(-) -- http://git-wip-us.apache.org/repos/asf/cassandra/blob/95b2d024/CHANGES.txt -- diff --git a/CHANGES.txt b/CHANGES.txt index dee669a..c1c6c78 100644 --- a/CHANGES.txt +++ b/CHANGES.txt @@ -1,4 +1,5 @@ 2.1.16 + * Include column family parameter when -st and -et are provided (CASSANDRA-11866) * Fix queries with empty ByteBuffer values in clustering column restrictions (CASSANDRA-12127) * Disable passing control to post-flush after flush failure to prevent data loss (CASSANDRA-11828) * Allow STCS-in-L0 compactions to reduce scope with LCS (CASSANDRA-12040) http://git-wip-us.apache.org/repos/asf/cassandra/blob/95b2d024/src/java/org/apache/cassandra/tools/NodeTool.java -- diff --git a/src/java/org/apache/cassandra/tools/NodeTool.java b/src/java/org/apache/cassandra/tools/NodeTool.java index 5af8240..d1afb6f 100644 --- a/src/java/org/apache/cassandra/tools/NodeTool.java +++ b/src/java/org/apache/cassandra/tools/NodeTool.java @@ -1947,7 +1947,7 @@ public class NodeTool else if(!specificHosts.isEmpty()) hosts = newArrayList(specificHosts); if (!startToken.isEmpty() || !endToken.isEmpty()) -probe.forceRepairRangeAsync(System.out, keyspace, parallelismDegree, dataCenters,hosts, startToken, endToken, !incrementalRepair); +probe.forceRepairRangeAsync(System.out, keyspace, parallelismDegree, dataCenters,hosts, startToken, endToken, !incrementalRepair, cfnames); else probe.forceRepairAsync(System.out, keyspace, parallelismDegree, dataCenters, hosts, primaryRange, !incrementalRepair, cfnames); } catch (Exception e)
[10/21] cassandra git commit: Merge branch 'cassandra-2.1' into cassandra-2.2
Merge branch 'cassandra-2.1' into cassandra-2.2 Project: http://git-wip-us.apache.org/repos/asf/cassandra/repo Commit: http://git-wip-us.apache.org/repos/asf/cassandra/commit/93ad056e Tree: http://git-wip-us.apache.org/repos/asf/cassandra/tree/93ad056e Diff: http://git-wip-us.apache.org/repos/asf/cassandra/diff/93ad056e Branch: refs/heads/cassandra-2.2 Commit: 93ad056ede2e5d573d12eb9d51a0e18ab2c4762f Parents: 59da275 95b2d02 Author: Yuki Morishita Authored: Mon Aug 22 16:39:53 2016 -0500 Committer: Yuki Morishita Committed: Mon Aug 22 16:39:53 2016 -0500 -- --
[03/21] cassandra git commit: Include column family parameter when -st and -et are provided - subrange repair
Include column family parameter when -st and -et are provided - subrange repair Patch by Vinay Chella; Reviewed by Paulo Motta for CASSANDRA-11866 Project: http://git-wip-us.apache.org/repos/asf/cassandra/repo Commit: http://git-wip-us.apache.org/repos/asf/cassandra/commit/95b2d024 Tree: http://git-wip-us.apache.org/repos/asf/cassandra/tree/95b2d024 Diff: http://git-wip-us.apache.org/repos/asf/cassandra/diff/95b2d024 Branch: refs/heads/cassandra-3.9 Commit: 95b2d0241c114fdb37f9b3e30c981ce7aa39e177 Parents: 527d189 Author: vchella Authored: Tue Jul 19 18:47:01 2016 -0700 Committer: Yuki Morishita Committed: Mon Aug 22 16:36:54 2016 -0500 -- CHANGES.txt | 1 + src/java/org/apache/cassandra/tools/NodeTool.java | 2 +- 2 files changed, 2 insertions(+), 1 deletion(-) -- http://git-wip-us.apache.org/repos/asf/cassandra/blob/95b2d024/CHANGES.txt -- diff --git a/CHANGES.txt b/CHANGES.txt index dee669a..c1c6c78 100644 --- a/CHANGES.txt +++ b/CHANGES.txt @@ -1,4 +1,5 @@ 2.1.16 + * Include column family parameter when -st and -et are provided (CASSANDRA-11866) * Fix queries with empty ByteBuffer values in clustering column restrictions (CASSANDRA-12127) * Disable passing control to post-flush after flush failure to prevent data loss (CASSANDRA-11828) * Allow STCS-in-L0 compactions to reduce scope with LCS (CASSANDRA-12040) http://git-wip-us.apache.org/repos/asf/cassandra/blob/95b2d024/src/java/org/apache/cassandra/tools/NodeTool.java -- diff --git a/src/java/org/apache/cassandra/tools/NodeTool.java b/src/java/org/apache/cassandra/tools/NodeTool.java index 5af8240..d1afb6f 100644 --- a/src/java/org/apache/cassandra/tools/NodeTool.java +++ b/src/java/org/apache/cassandra/tools/NodeTool.java @@ -1947,7 +1947,7 @@ public class NodeTool else if(!specificHosts.isEmpty()) hosts = newArrayList(specificHosts); if (!startToken.isEmpty() || !endToken.isEmpty()) -probe.forceRepairRangeAsync(System.out, keyspace, parallelismDegree, dataCenters,hosts, startToken, endToken, !incrementalRepair); +probe.forceRepairRangeAsync(System.out, keyspace, parallelismDegree, dataCenters,hosts, startToken, endToken, !incrementalRepair, cfnames); else probe.forceRepairAsync(System.out, keyspace, parallelismDegree, dataCenters, hosts, primaryRange, !incrementalRepair, cfnames); } catch (Exception e)
[01/21] cassandra git commit: Include column family parameter when -st and -et are provided - subrange repair
Repository: cassandra Updated Branches: refs/heads/cassandra-2.1 527d1897c -> 95b2d0241 refs/heads/cassandra-2.2 59da27560 -> 93ad056ed refs/heads/cassandra-3.0 a86ddac34 -> f255370f3 refs/heads/cassandra-3.8 2b8672d2a -> 027400ceb refs/heads/cassandra-3.9 bd2b73b29 -> a592693dd refs/heads/trunk 4c84d4097 -> 54ae900a5 Include column family parameter when -st and -et are provided - subrange repair Patch by Vinay Chella; Reviewed by Paulo Motta for CASSANDRA-11866 Project: http://git-wip-us.apache.org/repos/asf/cassandra/repo Commit: http://git-wip-us.apache.org/repos/asf/cassandra/commit/95b2d024 Tree: http://git-wip-us.apache.org/repos/asf/cassandra/tree/95b2d024 Diff: http://git-wip-us.apache.org/repos/asf/cassandra/diff/95b2d024 Branch: refs/heads/cassandra-2.1 Commit: 95b2d0241c114fdb37f9b3e30c981ce7aa39e177 Parents: 527d189 Author: vchella Authored: Tue Jul 19 18:47:01 2016 -0700 Committer: Yuki Morishita Committed: Mon Aug 22 16:36:54 2016 -0500 -- CHANGES.txt | 1 + src/java/org/apache/cassandra/tools/NodeTool.java | 2 +- 2 files changed, 2 insertions(+), 1 deletion(-) -- http://git-wip-us.apache.org/repos/asf/cassandra/blob/95b2d024/CHANGES.txt -- diff --git a/CHANGES.txt b/CHANGES.txt index dee669a..c1c6c78 100644 --- a/CHANGES.txt +++ b/CHANGES.txt @@ -1,4 +1,5 @@ 2.1.16 + * Include column family parameter when -st and -et are provided (CASSANDRA-11866) * Fix queries with empty ByteBuffer values in clustering column restrictions (CASSANDRA-12127) * Disable passing control to post-flush after flush failure to prevent data loss (CASSANDRA-11828) * Allow STCS-in-L0 compactions to reduce scope with LCS (CASSANDRA-12040) http://git-wip-us.apache.org/repos/asf/cassandra/blob/95b2d024/src/java/org/apache/cassandra/tools/NodeTool.java -- diff --git a/src/java/org/apache/cassandra/tools/NodeTool.java b/src/java/org/apache/cassandra/tools/NodeTool.java index 5af8240..d1afb6f 100644 --- a/src/java/org/apache/cassandra/tools/NodeTool.java +++ b/src/java/org/apache/cassandra/tools/NodeTool.java @@ -1947,7 +1947,7 @@ public class NodeTool else if(!specificHosts.isEmpty()) hosts = newArrayList(specificHosts); if (!startToken.isEmpty() || !endToken.isEmpty()) -probe.forceRepairRangeAsync(System.out, keyspace, parallelismDegree, dataCenters,hosts, startToken, endToken, !incrementalRepair); +probe.forceRepairRangeAsync(System.out, keyspace, parallelismDegree, dataCenters,hosts, startToken, endToken, !incrementalRepair, cfnames); else probe.forceRepairAsync(System.out, keyspace, parallelismDegree, dataCenters, hosts, primaryRange, !incrementalRepair, cfnames); } catch (Exception e)
[20/21] cassandra git commit: Merge branch 'cassandra-3.8' into cassandra-3.9
Merge branch 'cassandra-3.8' into cassandra-3.9 Project: http://git-wip-us.apache.org/repos/asf/cassandra/repo Commit: http://git-wip-us.apache.org/repos/asf/cassandra/commit/a592693d Tree: http://git-wip-us.apache.org/repos/asf/cassandra/tree/a592693d Diff: http://git-wip-us.apache.org/repos/asf/cassandra/diff/a592693d Branch: refs/heads/trunk Commit: a592693dd0fed2d6b2f18ec3fa0164b2cd4178d7 Parents: bd2b73b 027400c Author: Yuki Morishita Authored: Mon Aug 22 17:04:07 2016 -0500 Committer: Yuki Morishita Committed: Mon Aug 22 17:04:07 2016 -0500 -- --
[17/21] cassandra git commit: Merge branch 'cassandra-3.0' into cassandra-3.8
Merge branch 'cassandra-3.0' into cassandra-3.8 Project: http://git-wip-us.apache.org/repos/asf/cassandra/repo Commit: http://git-wip-us.apache.org/repos/asf/cassandra/commit/027400ce Tree: http://git-wip-us.apache.org/repos/asf/cassandra/tree/027400ce Diff: http://git-wip-us.apache.org/repos/asf/cassandra/diff/027400ce Branch: refs/heads/trunk Commit: 027400ceb5ccd5f97b8f71e36e4f2b0f2518ad46 Parents: 2b8672d f255370 Author: Yuki Morishita Authored: Mon Aug 22 17:03:57 2016 -0500 Committer: Yuki Morishita Committed: Mon Aug 22 17:03:57 2016 -0500 -- --
[15/21] cassandra git commit: Merge branch 'cassandra-2.2' into cassandra-3.0
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/f255370f Tree: http://git-wip-us.apache.org/repos/asf/cassandra/tree/f255370f Diff: http://git-wip-us.apache.org/repos/asf/cassandra/diff/f255370f Branch: refs/heads/cassandra-3.8 Commit: f255370f316e3c19bfbb99649f9dcd5a4bd39c22 Parents: a86ddac 93ad056 Author: Yuki Morishita Authored: Mon Aug 22 16:40:05 2016 -0500 Committer: Yuki Morishita Committed: Mon Aug 22 16:40:05 2016 -0500 -- --
[08/21] cassandra git commit: Merge branch 'cassandra-2.1' into cassandra-2.2
Merge branch 'cassandra-2.1' into cassandra-2.2 Project: http://git-wip-us.apache.org/repos/asf/cassandra/repo Commit: http://git-wip-us.apache.org/repos/asf/cassandra/commit/93ad056e Tree: http://git-wip-us.apache.org/repos/asf/cassandra/tree/93ad056e Diff: http://git-wip-us.apache.org/repos/asf/cassandra/diff/93ad056e Branch: refs/heads/cassandra-3.0 Commit: 93ad056ede2e5d573d12eb9d51a0e18ab2c4762f Parents: 59da275 95b2d02 Author: Yuki Morishita Authored: Mon Aug 22 16:39:53 2016 -0500 Committer: Yuki Morishita Committed: Mon Aug 22 16:39:53 2016 -0500 -- --
[06/21] cassandra git commit: Include column family parameter when -st and -et are provided - subrange repair
Include column family parameter when -st and -et are provided - subrange repair Patch by Vinay Chella; Reviewed by Paulo Motta for CASSANDRA-11866 Project: http://git-wip-us.apache.org/repos/asf/cassandra/repo Commit: http://git-wip-us.apache.org/repos/asf/cassandra/commit/95b2d024 Tree: http://git-wip-us.apache.org/repos/asf/cassandra/tree/95b2d024 Diff: http://git-wip-us.apache.org/repos/asf/cassandra/diff/95b2d024 Branch: refs/heads/trunk Commit: 95b2d0241c114fdb37f9b3e30c981ce7aa39e177 Parents: 527d189 Author: vchella Authored: Tue Jul 19 18:47:01 2016 -0700 Committer: Yuki Morishita Committed: Mon Aug 22 16:36:54 2016 -0500 -- CHANGES.txt | 1 + src/java/org/apache/cassandra/tools/NodeTool.java | 2 +- 2 files changed, 2 insertions(+), 1 deletion(-) -- http://git-wip-us.apache.org/repos/asf/cassandra/blob/95b2d024/CHANGES.txt -- diff --git a/CHANGES.txt b/CHANGES.txt index dee669a..c1c6c78 100644 --- a/CHANGES.txt +++ b/CHANGES.txt @@ -1,4 +1,5 @@ 2.1.16 + * Include column family parameter when -st and -et are provided (CASSANDRA-11866) * Fix queries with empty ByteBuffer values in clustering column restrictions (CASSANDRA-12127) * Disable passing control to post-flush after flush failure to prevent data loss (CASSANDRA-11828) * Allow STCS-in-L0 compactions to reduce scope with LCS (CASSANDRA-12040) http://git-wip-us.apache.org/repos/asf/cassandra/blob/95b2d024/src/java/org/apache/cassandra/tools/NodeTool.java -- diff --git a/src/java/org/apache/cassandra/tools/NodeTool.java b/src/java/org/apache/cassandra/tools/NodeTool.java index 5af8240..d1afb6f 100644 --- a/src/java/org/apache/cassandra/tools/NodeTool.java +++ b/src/java/org/apache/cassandra/tools/NodeTool.java @@ -1947,7 +1947,7 @@ public class NodeTool else if(!specificHosts.isEmpty()) hosts = newArrayList(specificHosts); if (!startToken.isEmpty() || !endToken.isEmpty()) -probe.forceRepairRangeAsync(System.out, keyspace, parallelismDegree, dataCenters,hosts, startToken, endToken, !incrementalRepair); +probe.forceRepairRangeAsync(System.out, keyspace, parallelismDegree, dataCenters,hosts, startToken, endToken, !incrementalRepair, cfnames); else probe.forceRepairAsync(System.out, keyspace, parallelismDegree, dataCenters, hosts, primaryRange, !incrementalRepair, cfnames); } catch (Exception e)
[18/21] cassandra git commit: Merge branch 'cassandra-3.0' into cassandra-3.8
Merge branch 'cassandra-3.0' into cassandra-3.8 Project: http://git-wip-us.apache.org/repos/asf/cassandra/repo Commit: http://git-wip-us.apache.org/repos/asf/cassandra/commit/027400ce Tree: http://git-wip-us.apache.org/repos/asf/cassandra/tree/027400ce Diff: http://git-wip-us.apache.org/repos/asf/cassandra/diff/027400ce Branch: refs/heads/cassandra-3.9 Commit: 027400ceb5ccd5f97b8f71e36e4f2b0f2518ad46 Parents: 2b8672d f255370 Author: Yuki Morishita Authored: Mon Aug 22 17:03:57 2016 -0500 Committer: Yuki Morishita Committed: Mon Aug 22 17:03:57 2016 -0500 -- --
[07/21] cassandra git commit: Merge branch 'cassandra-2.1' into cassandra-2.2
Merge branch 'cassandra-2.1' into cassandra-2.2 Project: http://git-wip-us.apache.org/repos/asf/cassandra/repo Commit: http://git-wip-us.apache.org/repos/asf/cassandra/commit/93ad056e Tree: http://git-wip-us.apache.org/repos/asf/cassandra/tree/93ad056e Diff: http://git-wip-us.apache.org/repos/asf/cassandra/diff/93ad056e Branch: refs/heads/cassandra-3.9 Commit: 93ad056ede2e5d573d12eb9d51a0e18ab2c4762f Parents: 59da275 95b2d02 Author: Yuki Morishita Authored: Mon Aug 22 16:39:53 2016 -0500 Committer: Yuki Morishita Committed: Mon Aug 22 16:39:53 2016 -0500 -- --
[12/21] cassandra git commit: Merge branch 'cassandra-2.2' into cassandra-3.0
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/f255370f Tree: http://git-wip-us.apache.org/repos/asf/cassandra/tree/f255370f Diff: http://git-wip-us.apache.org/repos/asf/cassandra/diff/f255370f Branch: refs/heads/trunk Commit: f255370f316e3c19bfbb99649f9dcd5a4bd39c22 Parents: a86ddac 93ad056 Author: Yuki Morishita Authored: Mon Aug 22 16:40:05 2016 -0500 Committer: Yuki Morishita Committed: Mon Aug 22 16:40:05 2016 -0500 -- --
[jira] [Commented] (CASSANDRA-12384) Include info about sstable on "Compacting large row” message
[
https://issues.apache.org/jira/browse/CASSANDRA-12384?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15431679#comment-15431679
]
Jason Brown commented on CASSANDRA-12384:
-
I think there's a discrepancy in the log line emitted by the c* patch versus
what the dtest patch is looking for:
cassandra:
{code}logger.warn("Writing large partition {}/{}:{} ({} bytes to sstable {}) ",
metadata.ksName, metadata.cfName, keyString,
FBUtilities.prettyPrintMemory(rowSize), getFilename());{code}
dtest:
{code}node.watch_log_for('{} large partition ks/large:user \({}\ to sstable
'.format(verb, sizematcher), from_mark=mark, timeout=180){code}
The cassandra patch will will "bytes to sstable", while the dtest looks for "to
sstable" ("bytes " is missing)
> Include info about sstable on "Compacting large row” message
>
>
> Key: CASSANDRA-12384
> URL: https://issues.apache.org/jira/browse/CASSANDRA-12384
> Project: Cassandra
> Issue Type: Improvement
>Reporter: sankalp kohli
>Assignee: sankalp kohli
>Priority: Trivial
> Attachments: CASSANDRA-12384_3.0.txt, CASSANDRA-12384_trunk.txt,
> Dtest.txt
>
>
> On a message like this one, it would be helpful to understand which sstable
> this large row is going in
> Compacting large row abc/xyz:38956kjhawf (xyz bytes) incrementally
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (CASSANDRA-12239) Add mshuler's key FE4B2BDA to dist/cassandra/KEYS
[
https://issues.apache.org/jira/browse/CASSANDRA-12239?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15431653#comment-15431653
]
Mark Thomas commented on CASSANDRA-12239:
-
With my Infra and Security team hats on, best practice is individual keys.
Shared keys are too insecure.
For specific cases (JAR signing, signing Windows binaries and signing stuff for
the Apple Store) that need keys that en-users will inherently trust (because
their OS trusts the relevant CAs) Infra provides access to a code signing
service but for normal releases (99+% of all ASF releases) OpenPGP signatures
from a committers key are sufficient.
> Add mshuler's key FE4B2BDA to dist/cassandra/KEYS
> -
>
> Key: CASSANDRA-12239
> URL: https://issues.apache.org/jira/browse/CASSANDRA-12239
> Project: Cassandra
> Issue Type: Task
> Components: Packaging
>Reporter: Michael Shuler
>Assignee: Michael Shuler
>Priority: Blocker
> Fix For: 3.8
>
> Attachments: KEYS+mshuler.diff.txt
>
>
> I've started working on packaging with the 3.8 release and signed the staging
> artifacts with FE4B2BDA. This key will need to be added for the debian
> repository signature to function correctly, if it's released as-is, or
> perhaps [~tjake] will need to re-sign the release. Users will need to also
> fetch this new key and add to {{apt-key}}.
> {{KEYS}} patch attached.
> Assigned to myself, but I am not sure exactly where {{KEYS}} lives - in svn
> somewhere or a direct upload? :)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (CASSANDRA-9875) Rebuild from targeted replica
[ https://issues.apache.org/jira/browse/CASSANDRA-9875?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Geoffrey Yu updated CASSANDRA-9875: --- Status: Patch Available (was: Open) > Rebuild from targeted replica > - > > Key: CASSANDRA-9875 > URL: https://issues.apache.org/jira/browse/CASSANDRA-9875 > Project: Cassandra > Issue Type: Improvement >Reporter: sankalp kohli >Assignee: Geoffrey Yu >Priority: Minor > Labels: lhf > Fix For: 3.x > > Attachments: 9875-dtest-master.txt, 9875-trunk-v2.txt, 9875-trunk.txt > > > Nodetool rebuild command will rebuild all the token ranges handled by the > endpoint. Sometimes we want to rebuild only a certain token range. We should > add this ability to rebuild command. We should also add the ability to stream > from a given replica. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CASSANDRA-9875) Rebuild from targeted replica
[
https://issues.apache.org/jira/browse/CASSANDRA-9875?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Geoffrey Yu updated CASSANDRA-9875:
---
Attachment: 9875-dtest-master.txt
9875-trunk-v2.txt
I've attached a new patch that uses a source filter as well as a patch for two
new dtests. One test verifies the behavior of rebuilding with a specific range
and the other verifies that {{nodetool rebuild}} disallows rebuilding a range
that the current node does not own.
Please let me know how these look!
> Rebuild from targeted replica
> -
>
> Key: CASSANDRA-9875
> URL: https://issues.apache.org/jira/browse/CASSANDRA-9875
> Project: Cassandra
> Issue Type: Improvement
>Reporter: sankalp kohli
>Assignee: Geoffrey Yu
>Priority: Minor
> Labels: lhf
> Fix For: 3.x
>
> Attachments: 9875-dtest-master.txt, 9875-trunk-v2.txt, 9875-trunk.txt
>
>
> Nodetool rebuild command will rebuild all the token ranges handled by the
> endpoint. Sometimes we want to rebuild only a certain token range. We should
> add this ability to rebuild command. We should also add the ability to stream
> from a given replica.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (CASSANDRA-12508) nodetool repair returns status code 0 for some errors
[ https://issues.apache.org/jira/browse/CASSANDRA-12508?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Blake Eggleston updated CASSANDRA-12508: Fix Version/s: 3.x 3.0.9 > nodetool repair returns status code 0 for some errors > - > > Key: CASSANDRA-12508 > URL: https://issues.apache.org/jira/browse/CASSANDRA-12508 > Project: Cassandra > Issue Type: Bug >Reporter: Blake Eggleston >Assignee: Blake Eggleston > Fix For: 3.0.9, 3.x > > > For instance, when specifying hosts that don’t exist, an error message is > logged, but the return code is zero. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CASSANDRA-12239) Add mshuler's key FE4B2BDA to dist/cassandra/KEYS
[
https://issues.apache.org/jira/browse/CASSANDRA-12239?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15431598#comment-15431598
]
Michael Shuler commented on CASSANDRA-12239:
Set as blocker on 3.8 release.
> Add mshuler's key FE4B2BDA to dist/cassandra/KEYS
> -
>
> Key: CASSANDRA-12239
> URL: https://issues.apache.org/jira/browse/CASSANDRA-12239
> Project: Cassandra
> Issue Type: Task
> Components: Packaging
>Reporter: Michael Shuler
>Assignee: Michael Shuler
>Priority: Blocker
> Fix For: 3.8
>
> Attachments: KEYS+mshuler.diff.txt
>
>
> I've started working on packaging with the 3.8 release and signed the staging
> artifacts with FE4B2BDA. This key will need to be added for the debian
> repository signature to function correctly, if it's released as-is, or
> perhaps [~tjake] will need to re-sign the release. Users will need to also
> fetch this new key and add to {{apt-key}}.
> {{KEYS}} patch attached.
> Assigned to myself, but I am not sure exactly where {{KEYS}} lives - in svn
> somewhere or a direct upload? :)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (CASSANDRA-12239) Add mshuler's key FE4B2BDA to dist/cassandra/KEYS
[
https://issues.apache.org/jira/browse/CASSANDRA-12239?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Shuler updated CASSANDRA-12239:
---
Priority: Blocker (was: Major)
Fix Version/s: (was: 3.x)
3.8
> Add mshuler's key FE4B2BDA to dist/cassandra/KEYS
> -
>
> Key: CASSANDRA-12239
> URL: https://issues.apache.org/jira/browse/CASSANDRA-12239
> Project: Cassandra
> Issue Type: Task
> Components: Packaging
>Reporter: Michael Shuler
>Assignee: Michael Shuler
>Priority: Blocker
> Fix For: 3.8
>
> Attachments: KEYS+mshuler.diff.txt
>
>
> I've started working on packaging with the 3.8 release and signed the staging
> artifacts with FE4B2BDA. This key will need to be added for the debian
> repository signature to function correctly, if it's released as-is, or
> perhaps [~tjake] will need to re-sign the release. Users will need to also
> fetch this new key and add to {{apt-key}}.
> {{KEYS}} patch attached.
> Assigned to myself, but I am not sure exactly where {{KEYS}} lives - in svn
> somewhere or a direct upload? :)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (CASSANDRA-12239) Add mshuler's key FE4B2BDA to dist/cassandra/KEYS
[
https://issues.apache.org/jira/browse/CASSANDRA-12239?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Shuler updated CASSANDRA-12239:
---
Status: Awaiting Feedback (was: Open)
> Add mshuler's key FE4B2BDA to dist/cassandra/KEYS
> -
>
> Key: CASSANDRA-12239
> URL: https://issues.apache.org/jira/browse/CASSANDRA-12239
> Project: Cassandra
> Issue Type: Task
> Components: Packaging
>Reporter: Michael Shuler
>Assignee: Michael Shuler
>Priority: Blocker
> Fix For: 3.8
>
> Attachments: KEYS+mshuler.diff.txt
>
>
> I've started working on packaging with the 3.8 release and signed the staging
> artifacts with FE4B2BDA. This key will need to be added for the debian
> repository signature to function correctly, if it's released as-is, or
> perhaps [~tjake] will need to re-sign the release. Users will need to also
> fetch this new key and add to {{apt-key}}.
> {{KEYS}} patch attached.
> Assigned to myself, but I am not sure exactly where {{KEYS}} lives - in svn
> somewhere or a direct upload? :)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (CASSANDRA-12464) Investigate the potential improvement of parallelism on higher level compactions in LCS
[ https://issues.apache.org/jira/browse/CASSANDRA-12464?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wei Deng updated CASSANDRA-12464: - Labels: lcs lhf performance (was: lcs performance) > Investigate the potential improvement of parallelism on higher level > compactions in LCS > --- > > Key: CASSANDRA-12464 > URL: https://issues.apache.org/jira/browse/CASSANDRA-12464 > Project: Cassandra > Issue Type: Improvement > Components: Compaction >Reporter: Wei Deng > Labels: lcs, lhf, performance > > According to LevelDB's design doc > [here|https://github.com/google/leveldb/blob/master/doc/impl.html#L115-L116], > "A compaction merges the contents of the picked files to produce a sequence > of level-(L+1) files", it will "switch to producing a new level-(L+1) file > after the current output file has reached the target file size" (in our case > 160MB), it will also "switch to a new output file when the key range of the > current output file has grown enough to overlap more than ten level-(L+2) > files". This is to ensure "that a later compaction of a level-(L+1) file will > not pick up too much data from level-(L+2)." > Our current code in LeveledCompactionStrategy doesn't implement this last > rule, but we might be able to quickly implement it and see how much a > compaction throughput improvement it can deliver. Potentially we can create a > scenario where a number of large L0 SSTables are present (e.g. 200GB after > switching from STCS) and let it to create thousands of L1 SSTables overflow, > and see how fast LCS can digest this much data from L1 and properly > upper-level them to completion. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CASSANDRA-12436) Under some races commit log may incorrectly think it has unflushed data
[ https://issues.apache.org/jira/browse/CASSANDRA-12436?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15431462#comment-15431462 ] Aleksey Yeschenko commented on CASSANDRA-12436: --- Given that we are planning to push out 3.8 and 3.9 off cassandra-3.9 both, I'm closing the ticket, as it will go into 3.8 just by virtue of being committed to cassandra-3.9 already. > Under some races commit log may incorrectly think it has unflushed data > --- > > Key: CASSANDRA-12436 > URL: https://issues.apache.org/jira/browse/CASSANDRA-12436 > Project: Cassandra > Issue Type: Bug >Reporter: Branimir Lambov >Assignee: Branimir Lambov > Fix For: 3.0.9, 3.9 > > > This can mainfest itself as a "Failed to force-recycle all segments; at least > one segment is still in use with dirty CFs." message after CASSANDRA-11828. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CASSANDRA-12482) dtest failure in upgrade_tests.cql_tests.TestCQLNodes2RF1_Upgrade_current_3_x_To_indev_3_x.select_with_alias_test
[
https://issues.apache.org/jira/browse/CASSANDRA-12482?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Philip Thompson updated CASSANDRA-12482:
Resolution: Fixed
Status: Resolved (was: Patch Available)
> dtest failure in
> upgrade_tests.cql_tests.TestCQLNodes2RF1_Upgrade_current_3_x_To_indev_3_x.select_with_alias_test
> -
>
> Key: CASSANDRA-12482
> URL: https://issues.apache.org/jira/browse/CASSANDRA-12482
> Project: Cassandra
> Issue Type: Test
>Reporter: Sean McCarthy
>Assignee: Philip Thompson
> Labels: dtest
> Attachments: node1.log, node1_debug.log, node1_gc.log, node2.log,
> node2_debug.log, node2_gc.log
>
>
> example failure:
> http://cassci.datastax.com/job/trunk_dtest_upgrade/29/testReport/upgrade_tests.cql_tests/TestCQLNodes2RF1_Upgrade_current_3_x_To_indev_3_x/select_with_alias_test
> {code}
> Stacktrace
> File "/usr/lib/python2.7/unittest/case.py", line 329, in run
> testMethod()
> File "/home/automaton/cassandra-dtest/upgrade_tests/cql_tests.py", line
> 3184, in select_with_alias_test
> assert_invalid(cursor, 'SELECT id AS user_id, name AS user_name FROM
> users WHERE user_id = 0', matching=error_msg)
> File "/home/automaton/cassandra-dtest/assertions.py", line 92, in
> assert_invalid
> assert_exception(session, query, matching=matching, expected=expected)
> File "/home/automaton/cassandra-dtest/assertions.py", line 65, in
> assert_exception
> _assert_exception(session.execute, query, matching=matching,
> expected=expected)
> File "/home/automaton/cassandra-dtest/assertions.py", line 54, in
> _assert_exception
> assert_regexp_matches(str(e), matching)
> File "/usr/lib/python2.7/unittest/case.py", line 1002, in
> assertRegexpMatches
> raise self.failureException(msg)
> 'Regexp didn\'t match: "Aliases aren\'t allowed in the where clause" not
> found in \'Error from server: code=2200 [Invalid query] message="Undefined
> column name user_id"
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (CASSANDRA-12436) Under some races commit log may incorrectly think it has unflushed data
[ https://issues.apache.org/jira/browse/CASSANDRA-12436?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksey Yeschenko updated CASSANDRA-12436: -- Resolution: Fixed Status: Resolved (was: Patch Available) > Under some races commit log may incorrectly think it has unflushed data > --- > > Key: CASSANDRA-12436 > URL: https://issues.apache.org/jira/browse/CASSANDRA-12436 > Project: Cassandra > Issue Type: Bug >Reporter: Branimir Lambov >Assignee: Branimir Lambov > Fix For: 3.0.9, 3.9 > > > This can mainfest itself as a "Failed to force-recycle all segments; at least > one segment is still in use with dirty CFs." message after CASSANDRA-11828. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CASSANDRA-11914) Provide option for cassandra-stress to dump all settings
[ https://issues.apache.org/jira/browse/CASSANDRA-11914?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15431461#comment-15431461 ] Joel Knighton commented on CASSANDRA-11914: --- Thanks - I'll integrate that patch as well in [CASSANDRA-12473]. > Provide option for cassandra-stress to dump all settings > > > Key: CASSANDRA-11914 > URL: https://issues.apache.org/jira/browse/CASSANDRA-11914 > Project: Cassandra > Issue Type: Improvement > Components: Tools >Reporter: Ben Slater >Assignee: Ben Slater >Priority: Minor > Fix For: 3.10 > > Attachments: 11914-NPEFix-trunk.txt > > > cassandra-stress has quite a lot of default settings and settings that are > derived as side effects of explicit options. For people learning the tool and > saving a clear record of what was run, I think it would be useful if there > was an option to have the tool print all its settings at the start of a run. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CASSANDRA-12522) nodetool repair -pr and -local option rejected
[ https://issues.apache.org/jira/browse/CASSANDRA-12522?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jérôme Mainaud updated CASSANDRA-12522: --- Fix Version/s: 3.9 Status: Patch Available (was: Open) The fix test unit call `Database.daemonInitialization()` in order to provide a local dc. However, I'm not sure it is safe for other tests. I would rather mock the object here if I could. Tell me how to improve it if there is a better way. > nodetool repair -pr and -local option rejected > -- > > Key: CASSANDRA-12522 > URL: https://issues.apache.org/jira/browse/CASSANDRA-12522 > Project: Cassandra > Issue Type: Bug > Components: Tools >Reporter: Jérôme Mainaud > Fix For: 3.9 > > Attachments: 12522-trunk.patch > > > Repair command refuse to work with both -pr and -local on an 2.2.6 cluster. > The message is “You need to run primary range repair on all nodes in the > cluster”. > The compatibility was introduiced in CASSANDRA-7450 but RepairOption > validation reject the case. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CASSANDRA-12522) nodetool repair -pr and -local option rejected
[ https://issues.apache.org/jira/browse/CASSANDRA-12522?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jérôme Mainaud updated CASSANDRA-12522: --- Attachment: 12522-trunk.patch > nodetool repair -pr and -local option rejected > -- > > Key: CASSANDRA-12522 > URL: https://issues.apache.org/jira/browse/CASSANDRA-12522 > Project: Cassandra > Issue Type: Bug > Components: Tools >Reporter: Jérôme Mainaud > Attachments: 12522-trunk.patch > > > Repair command refuse to work with both -pr and -local on an 2.2.6 cluster. > The message is “You need to run primary range repair on all nodes in the > cluster”. > The compatibility was introduiced in CASSANDRA-7450 but RepairOption > validation reject the case. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CASSANDRA-12251) dtest failure in upgrade_tests.cql_tests.TestCQLNodes3RF3_Upgrade_current_3_x_To_indev_3_x.whole_list_conditional_test
[
https://issues.apache.org/jira/browse/CASSANDRA-12251?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joel Knighton updated CASSANDRA-12251:
--
Status: Ready to Commit (was: Patch Available)
> dtest failure in
> upgrade_tests.cql_tests.TestCQLNodes3RF3_Upgrade_current_3_x_To_indev_3_x.whole_list_conditional_test
> --
>
> Key: CASSANDRA-12251
> URL: https://issues.apache.org/jira/browse/CASSANDRA-12251
> Project: Cassandra
> Issue Type: Bug
>Reporter: Philip Thompson
>Assignee: Alex Petrov
> Labels: dtest
> Attachments: node1.log, node1_debug.log, node1_gc.log, node2.log,
> node2_debug.log, node2_gc.log, node3.log, node3_debug.log, node3_gc.log
>
>
> example failure:
> http://cassci.datastax.com/job/cassandra-3.8_dtest_upgrade/1/testReport/upgrade_tests.cql_tests/TestCQLNodes3RF3_Upgrade_current_3_x_To_indev_3_x/whole_list_conditional_test
> Failed on CassCI build cassandra-3.8_dtest_upgrade #1
> Relevant error in logs is
> {code}
> Unexpected error in node1 log, error:
> ERROR [InternalResponseStage:2] 2016-07-20 04:58:45,876
> CassandraDaemon.java:217 - Exception in thread
> Thread[InternalResponseStage:2,5,main]
> java.util.concurrent.RejectedExecutionException: ThreadPoolExecutor has shut
> down
> at
> org.apache.cassandra.concurrent.DebuggableThreadPoolExecutor$1.rejectedExecution(DebuggableThreadPoolExecutor.java:61)
> ~[apache-cassandra-3.7.jar:3.7]
> at
> java.util.concurrent.ThreadPoolExecutor.reject(ThreadPoolExecutor.java:823)
> ~[na:1.8.0_51]
> at
> java.util.concurrent.ThreadPoolExecutor.execute(ThreadPoolExecutor.java:1369)
> ~[na:1.8.0_51]
> at
> org.apache.cassandra.concurrent.DebuggableThreadPoolExecutor.execute(DebuggableThreadPoolExecutor.java:165)
> ~[apache-cassandra-3.7.jar:3.7]
> at
> java.util.concurrent.AbstractExecutorService.submit(AbstractExecutorService.java:112)
> ~[na:1.8.0_51]
> at
> org.apache.cassandra.db.ColumnFamilyStore.switchMemtable(ColumnFamilyStore.java:842)
> ~[apache-cassandra-3.7.jar:3.7]
> at
> org.apache.cassandra.db.ColumnFamilyStore.switchMemtableIfCurrent(ColumnFamilyStore.java:822)
> ~[apache-cassandra-3.7.jar:3.7]
> at
> org.apache.cassandra.db.ColumnFamilyStore.forceFlush(ColumnFamilyStore.java:891)
> ~[apache-cassandra-3.7.jar:3.7]
> at
> org.apache.cassandra.schema.SchemaKeyspace.lambda$flush$1(SchemaKeyspace.java:279)
> ~[apache-cassandra-3.7.jar:3.7]
> at
> org.apache.cassandra.schema.SchemaKeyspace$$Lambda$200/1129213153.accept(Unknown
> Source) ~[na:na]
> at java.lang.Iterable.forEach(Iterable.java:75) ~[na:1.8.0_51]
> at
> org.apache.cassandra.schema.SchemaKeyspace.flush(SchemaKeyspace.java:279)
> ~[apache-cassandra-3.7.jar:3.7]
> at
> org.apache.cassandra.schema.SchemaKeyspace.mergeSchema(SchemaKeyspace.java:1271)
> ~[apache-cassandra-3.7.jar:3.7]
> at
> org.apache.cassandra.schema.SchemaKeyspace.mergeSchemaAndAnnounceVersion(SchemaKeyspace.java:1253)
> ~[apache-cassandra-3.7.jar:3.7]
> at
> org.apache.cassandra.service.MigrationTask$1.response(MigrationTask.java:92)
> ~[apache-cassandra-3.7.jar:3.7]
> at
> org.apache.cassandra.net.ResponseVerbHandler.doVerb(ResponseVerbHandler.java:53)
> ~[apache-cassandra-3.7.jar:3.7]
> at
> org.apache.cassandra.net.MessageDeliveryTask.run(MessageDeliveryTask.java:64)
> ~[apache-cassandra-3.7.jar:3.7]
> at
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
> ~[na:1.8.0_51]
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> ~[na:1.8.0_51]
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> ~[na:1.8.0_51]
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> [na:1.8.0_51]
> at java.lang.Thread.run(Thread.java:745) [na:1.8.0_51]
> {code}
> This is on a mixed 3.0.8, 3.8-tentative cluster
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (CASSANDRA-12251) dtest failure in upgrade_tests.cql_tests.TestCQLNodes3RF3_Upgrade_current_3_x_To_indev_3_x.whole_list_conditional_test
[
https://issues.apache.org/jira/browse/CASSANDRA-12251?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15431277#comment-15431277
]
Joel Knighton commented on CASSANDRA-12251:
---
+1 - lgtm. This should merge forward cleanly from 2.2.
> dtest failure in
> upgrade_tests.cql_tests.TestCQLNodes3RF3_Upgrade_current_3_x_To_indev_3_x.whole_list_conditional_test
> --
>
> Key: CASSANDRA-12251
> URL: https://issues.apache.org/jira/browse/CASSANDRA-12251
> Project: Cassandra
> Issue Type: Bug
>Reporter: Philip Thompson
>Assignee: Alex Petrov
> Labels: dtest
> Attachments: node1.log, node1_debug.log, node1_gc.log, node2.log,
> node2_debug.log, node2_gc.log, node3.log, node3_debug.log, node3_gc.log
>
>
> example failure:
> http://cassci.datastax.com/job/cassandra-3.8_dtest_upgrade/1/testReport/upgrade_tests.cql_tests/TestCQLNodes3RF3_Upgrade_current_3_x_To_indev_3_x/whole_list_conditional_test
> Failed on CassCI build cassandra-3.8_dtest_upgrade #1
> Relevant error in logs is
> {code}
> Unexpected error in node1 log, error:
> ERROR [InternalResponseStage:2] 2016-07-20 04:58:45,876
> CassandraDaemon.java:217 - Exception in thread
> Thread[InternalResponseStage:2,5,main]
> java.util.concurrent.RejectedExecutionException: ThreadPoolExecutor has shut
> down
> at
> org.apache.cassandra.concurrent.DebuggableThreadPoolExecutor$1.rejectedExecution(DebuggableThreadPoolExecutor.java:61)
> ~[apache-cassandra-3.7.jar:3.7]
> at
> java.util.concurrent.ThreadPoolExecutor.reject(ThreadPoolExecutor.java:823)
> ~[na:1.8.0_51]
> at
> java.util.concurrent.ThreadPoolExecutor.execute(ThreadPoolExecutor.java:1369)
> ~[na:1.8.0_51]
> at
> org.apache.cassandra.concurrent.DebuggableThreadPoolExecutor.execute(DebuggableThreadPoolExecutor.java:165)
> ~[apache-cassandra-3.7.jar:3.7]
> at
> java.util.concurrent.AbstractExecutorService.submit(AbstractExecutorService.java:112)
> ~[na:1.8.0_51]
> at
> org.apache.cassandra.db.ColumnFamilyStore.switchMemtable(ColumnFamilyStore.java:842)
> ~[apache-cassandra-3.7.jar:3.7]
> at
> org.apache.cassandra.db.ColumnFamilyStore.switchMemtableIfCurrent(ColumnFamilyStore.java:822)
> ~[apache-cassandra-3.7.jar:3.7]
> at
> org.apache.cassandra.db.ColumnFamilyStore.forceFlush(ColumnFamilyStore.java:891)
> ~[apache-cassandra-3.7.jar:3.7]
> at
> org.apache.cassandra.schema.SchemaKeyspace.lambda$flush$1(SchemaKeyspace.java:279)
> ~[apache-cassandra-3.7.jar:3.7]
> at
> org.apache.cassandra.schema.SchemaKeyspace$$Lambda$200/1129213153.accept(Unknown
> Source) ~[na:na]
> at java.lang.Iterable.forEach(Iterable.java:75) ~[na:1.8.0_51]
> at
> org.apache.cassandra.schema.SchemaKeyspace.flush(SchemaKeyspace.java:279)
> ~[apache-cassandra-3.7.jar:3.7]
> at
> org.apache.cassandra.schema.SchemaKeyspace.mergeSchema(SchemaKeyspace.java:1271)
> ~[apache-cassandra-3.7.jar:3.7]
> at
> org.apache.cassandra.schema.SchemaKeyspace.mergeSchemaAndAnnounceVersion(SchemaKeyspace.java:1253)
> ~[apache-cassandra-3.7.jar:3.7]
> at
> org.apache.cassandra.service.MigrationTask$1.response(MigrationTask.java:92)
> ~[apache-cassandra-3.7.jar:3.7]
> at
> org.apache.cassandra.net.ResponseVerbHandler.doVerb(ResponseVerbHandler.java:53)
> ~[apache-cassandra-3.7.jar:3.7]
> at
> org.apache.cassandra.net.MessageDeliveryTask.run(MessageDeliveryTask.java:64)
> ~[apache-cassandra-3.7.jar:3.7]
> at
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
> ~[na:1.8.0_51]
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> ~[na:1.8.0_51]
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> ~[na:1.8.0_51]
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> [na:1.8.0_51]
> at java.lang.Thread.run(Thread.java:745) [na:1.8.0_51]
> {code}
> This is on a mixed 3.0.8, 3.8-tentative cluster
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (CASSANDRA-12486) Structure for compactionhistory output (JSON, YAML)
[ https://issues.apache.org/jira/browse/CASSANDRA-12486?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yuki Morishita updated CASSANDRA-12486: --- Status: Open (was: Patch Available) > Structure for compactionhistory output (JSON, YAML) > --- > > Key: CASSANDRA-12486 > URL: https://issues.apache.org/jira/browse/CASSANDRA-12486 > Project: Cassandra > Issue Type: Improvement > Components: Tools >Reporter: Masataka Yamaguchi >Assignee: Masataka Yamaguchi >Priority: Minor > Fix For: 3.x > > Attachments: CASSANDRA-12486-trunk.patch, > compactionhistory_result.json, compactionhistory_result.txt, > compactionhistory_result.yaml > > > As with nodetool tpstats and tablestats (CASSANDRA-12035), nodetool > compactionhistory should also support useful output formats such as JSON or > YAML, so we implemented it. > Please review the attached patch. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CASSANDRA-12486) Structure for compactionhistory output (JSON, YAML)
[
https://issues.apache.org/jira/browse/CASSANDRA-12486?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15431197#comment-15431197
]
Yuki Morishita commented on CASSANDRA-12486:
Thank you for the patch!
What do you think about printing out {{compacted_at}} the same as table output
({{"2016-08-22T11:20:22.874-05:00"}})?
Also what about sorting by {{compacted_at}}?
> Structure for compactionhistory output (JSON, YAML)
> ---
>
> Key: CASSANDRA-12486
> URL: https://issues.apache.org/jira/browse/CASSANDRA-12486
> Project: Cassandra
> Issue Type: Improvement
> Components: Tools
>Reporter: Masataka Yamaguchi
>Assignee: Masataka Yamaguchi
>Priority: Minor
> Fix For: 3.x
>
> Attachments: CASSANDRA-12486-trunk.patch,
> compactionhistory_result.json, compactionhistory_result.txt,
> compactionhistory_result.yaml
>
>
> As with nodetool tpstats and tablestats (CASSANDRA-12035), nodetool
> compactionhistory should also support useful output formats such as JSON or
> YAML, so we implemented it.
> Please review the attached patch.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (CASSANDRA-12522) nodetool repair -pr and -local option rejected
Jérôme Mainaud created CASSANDRA-12522: -- Summary: nodetool repair -pr and -local option rejected Key: CASSANDRA-12522 URL: https://issues.apache.org/jira/browse/CASSANDRA-12522 Project: Cassandra Issue Type: Bug Components: Tools Reporter: Jérôme Mainaud Repair command refuse to work with both -pr and -local on an 2.2.6 cluster. The message is “You need to run primary range repair on all nodes in the cluster”. The compatibility was introduiced in CASSANDRA-7450 but RepairOption validation reject the case. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CASSANDRA-12508) nodetool repair returns status code 0 for some errors
[ https://issues.apache.org/jira/browse/CASSANDRA-12508?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Blake Eggleston updated CASSANDRA-12508: Status: Patch Available (was: Open) > nodetool repair returns status code 0 for some errors > - > > Key: CASSANDRA-12508 > URL: https://issues.apache.org/jira/browse/CASSANDRA-12508 > Project: Cassandra > Issue Type: Bug >Reporter: Blake Eggleston >Assignee: Blake Eggleston > > For instance, when specifying hosts that don’t exist, an error message is > logged, but the return code is zero. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CASSANDRA-12514) dtest failure in cql_tests.SlowQueryTester.disable_slow_query_log_test
[
https://issues.apache.org/jira/browse/CASSANDRA-12514?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Philip Thompson updated CASSANDRA-12514:
Resolution: Fixed
Status: Resolved (was: Patch Available)
> dtest failure in cql_tests.SlowQueryTester.disable_slow_query_log_test
> --
>
> Key: CASSANDRA-12514
> URL: https://issues.apache.org/jira/browse/CASSANDRA-12514
> Project: Cassandra
> Issue Type: Test
>Reporter: Craig Kodman
>Assignee: Philip Thompson
> Labels: dtest
> Attachments: node1.log, node1_debug.log, node1_gc.log
>
>
> example failure:
> http://cassci.datastax.com/job/cassandra-2.2_dtest/680/testReport/cql_tests/SlowQueryTester/disable_slow_query_log_test
> http://cassci.datastax.com/job/cassandra-2.2_dtest/680/testReport/cql_tests/SlowQueryTester/local_query_test/
> {code}
> Error Message
> Error starting node1.
> >> begin captured logging <<
> dtest: DEBUG: cluster ccm directory: /tmp/dtest-rDW1JQ
> dtest: DEBUG: Done setting configuration options:
> { 'initial_token': None,
> 'num_tokens': '32',
> 'phi_convict_threshold': 5,
> 'range_request_timeout_in_ms': 1,
> 'read_request_timeout_in_ms': 1,
> 'request_timeout_in_ms': 1,
> 'truncate_request_timeout_in_ms': 1,
> 'write_request_timeout_in_ms': 1}
> - >> end captured logging << -
> Stacktrace
> File "/usr/lib/python2.7/unittest/case.py", line 329, in run
> testMethod()
> File "/home/automaton/cassandra-dtest/cql_tests.py", line 945, in
> disable_slow_query_log_test
> "-Dcassandra.test.read_iteration_delay_ms=50"])
> File "/home/automaton/ccm/ccmlib/cluster.py", line 414, in start
> raise NodeError("Error starting {0}.".format(node.name), p)
> "Error starting node1.\n >> begin captured logging <<
> \ndtest: DEBUG: cluster ccm directory:
> /tmp/dtest-rDW1JQ\ndtest: DEBUG: Done setting configuration options:\n{
> 'initial_token': None,\n'num_tokens': '32',\n'phi_convict_threshold':
> 5,\n'range_request_timeout_in_ms': 1,\n
> 'read_request_timeout_in_ms': 1,\n'request_timeout_in_ms': 1,\n
> 'truncate_request_timeout_in_ms': 1,\n'write_request_timeout_in_ms':
> 1}\n- >> end captured logging <<
> -"
> Standard Output
> [node1 ERROR] org.apache.cassandra.exceptions.ConfigurationException: Invalid
> yaml. Please remove properties [slow_query_log_timeout_in_ms] from your
> cassandra.yaml
> at
> org.apache.cassandra.config.YamlConfigurationLoader$MissingPropertiesChecker.check(YamlConfigurationLoader.java:146)
> at
> org.apache.cassandra.config.YamlConfigurationLoader.loadConfig(YamlConfigurationLoader.java:113)
> at
> org.apache.cassandra.config.YamlConfigurationLoader.loadConfig(YamlConfigurationLoader.java:85)
> at
> org.apache.cassandra.config.DatabaseDescriptor.loadConfig(DatabaseDescriptor.java:135)
> at
> org.apache.cassandra.config.DatabaseDescriptor.(DatabaseDescriptor.java:119)
> at
> org.apache.cassandra.service.CassandraDaemon.activate(CassandraDaemon.java:507)
> at
> org.apache.cassandra.service.CassandraDaemon.main(CassandraDaemon.java:641)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (CASSANDRA-12514) dtest failure in cql_tests.SlowQueryTester.disable_slow_query_log_test
[
https://issues.apache.org/jira/browse/CASSANDRA-12514?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Philip Thompson updated CASSANDRA-12514:
Reviewer: Russ Hatch
Status: Patch Available (was: In Progress)
https://github.com/riptano/cassandra-dtest/pull/1267
> dtest failure in cql_tests.SlowQueryTester.disable_slow_query_log_test
> --
>
> Key: CASSANDRA-12514
> URL: https://issues.apache.org/jira/browse/CASSANDRA-12514
> Project: Cassandra
> Issue Type: Test
>Reporter: Craig Kodman
>Assignee: Philip Thompson
> Labels: dtest
> Attachments: node1.log, node1_debug.log, node1_gc.log
>
>
> example failure:
> http://cassci.datastax.com/job/cassandra-2.2_dtest/680/testReport/cql_tests/SlowQueryTester/disable_slow_query_log_test
> http://cassci.datastax.com/job/cassandra-2.2_dtest/680/testReport/cql_tests/SlowQueryTester/local_query_test/
> {code}
> Error Message
> Error starting node1.
> >> begin captured logging <<
> dtest: DEBUG: cluster ccm directory: /tmp/dtest-rDW1JQ
> dtest: DEBUG: Done setting configuration options:
> { 'initial_token': None,
> 'num_tokens': '32',
> 'phi_convict_threshold': 5,
> 'range_request_timeout_in_ms': 1,
> 'read_request_timeout_in_ms': 1,
> 'request_timeout_in_ms': 1,
> 'truncate_request_timeout_in_ms': 1,
> 'write_request_timeout_in_ms': 1}
> - >> end captured logging << -
> Stacktrace
> File "/usr/lib/python2.7/unittest/case.py", line 329, in run
> testMethod()
> File "/home/automaton/cassandra-dtest/cql_tests.py", line 945, in
> disable_slow_query_log_test
> "-Dcassandra.test.read_iteration_delay_ms=50"])
> File "/home/automaton/ccm/ccmlib/cluster.py", line 414, in start
> raise NodeError("Error starting {0}.".format(node.name), p)
> "Error starting node1.\n >> begin captured logging <<
> \ndtest: DEBUG: cluster ccm directory:
> /tmp/dtest-rDW1JQ\ndtest: DEBUG: Done setting configuration options:\n{
> 'initial_token': None,\n'num_tokens': '32',\n'phi_convict_threshold':
> 5,\n'range_request_timeout_in_ms': 1,\n
> 'read_request_timeout_in_ms': 1,\n'request_timeout_in_ms': 1,\n
> 'truncate_request_timeout_in_ms': 1,\n'write_request_timeout_in_ms':
> 1}\n- >> end captured logging <<
> -"
> Standard Output
> [node1 ERROR] org.apache.cassandra.exceptions.ConfigurationException: Invalid
> yaml. Please remove properties [slow_query_log_timeout_in_ms] from your
> cassandra.yaml
> at
> org.apache.cassandra.config.YamlConfigurationLoader$MissingPropertiesChecker.check(YamlConfigurationLoader.java:146)
> at
> org.apache.cassandra.config.YamlConfigurationLoader.loadConfig(YamlConfigurationLoader.java:113)
> at
> org.apache.cassandra.config.YamlConfigurationLoader.loadConfig(YamlConfigurationLoader.java:85)
> at
> org.apache.cassandra.config.DatabaseDescriptor.loadConfig(DatabaseDescriptor.java:135)
> at
> org.apache.cassandra.config.DatabaseDescriptor.(DatabaseDescriptor.java:119)
> at
> org.apache.cassandra.service.CassandraDaemon.activate(CassandraDaemon.java:507)
> at
> org.apache.cassandra.service.CassandraDaemon.main(CassandraDaemon.java:641)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Assigned] (CASSANDRA-12514) dtest failure in cql_tests.SlowQueryTester.disable_slow_query_log_test
[
https://issues.apache.org/jira/browse/CASSANDRA-12514?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Philip Thompson reassigned CASSANDRA-12514:
---
Assignee: Philip Thompson (was: DS Test Eng)
> dtest failure in cql_tests.SlowQueryTester.disable_slow_query_log_test
> --
>
> Key: CASSANDRA-12514
> URL: https://issues.apache.org/jira/browse/CASSANDRA-12514
> Project: Cassandra
> Issue Type: Test
>Reporter: Craig Kodman
>Assignee: Philip Thompson
> Labels: dtest
> Attachments: node1.log, node1_debug.log, node1_gc.log
>
>
> example failure:
> http://cassci.datastax.com/job/cassandra-2.2_dtest/680/testReport/cql_tests/SlowQueryTester/disable_slow_query_log_test
> http://cassci.datastax.com/job/cassandra-2.2_dtest/680/testReport/cql_tests/SlowQueryTester/local_query_test/
> {code}
> Error Message
> Error starting node1.
> >> begin captured logging <<
> dtest: DEBUG: cluster ccm directory: /tmp/dtest-rDW1JQ
> dtest: DEBUG: Done setting configuration options:
> { 'initial_token': None,
> 'num_tokens': '32',
> 'phi_convict_threshold': 5,
> 'range_request_timeout_in_ms': 1,
> 'read_request_timeout_in_ms': 1,
> 'request_timeout_in_ms': 1,
> 'truncate_request_timeout_in_ms': 1,
> 'write_request_timeout_in_ms': 1}
> - >> end captured logging << -
> Stacktrace
> File "/usr/lib/python2.7/unittest/case.py", line 329, in run
> testMethod()
> File "/home/automaton/cassandra-dtest/cql_tests.py", line 945, in
> disable_slow_query_log_test
> "-Dcassandra.test.read_iteration_delay_ms=50"])
> File "/home/automaton/ccm/ccmlib/cluster.py", line 414, in start
> raise NodeError("Error starting {0}.".format(node.name), p)
> "Error starting node1.\n >> begin captured logging <<
> \ndtest: DEBUG: cluster ccm directory:
> /tmp/dtest-rDW1JQ\ndtest: DEBUG: Done setting configuration options:\n{
> 'initial_token': None,\n'num_tokens': '32',\n'phi_convict_threshold':
> 5,\n'range_request_timeout_in_ms': 1,\n
> 'read_request_timeout_in_ms': 1,\n'request_timeout_in_ms': 1,\n
> 'truncate_request_timeout_in_ms': 1,\n'write_request_timeout_in_ms':
> 1}\n- >> end captured logging <<
> -"
> Standard Output
> [node1 ERROR] org.apache.cassandra.exceptions.ConfigurationException: Invalid
> yaml. Please remove properties [slow_query_log_timeout_in_ms] from your
> cassandra.yaml
> at
> org.apache.cassandra.config.YamlConfigurationLoader$MissingPropertiesChecker.check(YamlConfigurationLoader.java:146)
> at
> org.apache.cassandra.config.YamlConfigurationLoader.loadConfig(YamlConfigurationLoader.java:113)
> at
> org.apache.cassandra.config.YamlConfigurationLoader.loadConfig(YamlConfigurationLoader.java:85)
> at
> org.apache.cassandra.config.DatabaseDescriptor.loadConfig(DatabaseDescriptor.java:135)
> at
> org.apache.cassandra.config.DatabaseDescriptor.(DatabaseDescriptor.java:119)
> at
> org.apache.cassandra.service.CassandraDaemon.activate(CassandraDaemon.java:507)
> at
> org.apache.cassandra.service.CassandraDaemon.main(CassandraDaemon.java:641)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Resolved] (CASSANDRA-12515) dtest failure in cql_tests.SlowQueryTester.remote_query_test
[
https://issues.apache.org/jira/browse/CASSANDRA-12515?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Philip Thompson resolved CASSANDRA-12515.
-
Resolution: Duplicate
> dtest failure in cql_tests.SlowQueryTester.remote_query_test
>
>
> Key: CASSANDRA-12515
> URL: https://issues.apache.org/jira/browse/CASSANDRA-12515
> Project: Cassandra
> Issue Type: Test
>Reporter: Craig Kodman
>Assignee: DS Test Eng
> Labels: dtest
> Attachments: node1.log, node1_debug.log, node1_gc.log
>
>
> example failure:
> http://cassci.datastax.com/job/cassandra-2.2_dtest/680/testReport/cql_tests/SlowQueryTester/remote_query_test
> {code}
> Error Message
> 22 Aug 2016 04:05:15 [node1] Missing: ['Starting listening for CQL clients']:
> ERROR [main] 2016-08-22 03:55:13,422 CassandraDaem.
> See system.log for remainder
> >> begin captured logging <<
> dtest: DEBUG: cluster ccm directory: /tmp/dtest-qeHpYA
> dtest: DEBUG: Done setting configuration options:
> { 'initial_token': None,
> 'num_tokens': '32',
> 'phi_convict_threshold': 5,
> 'range_request_timeout_in_ms': 1,
> 'read_request_timeout_in_ms': 1,
> 'request_timeout_in_ms': 1,
> 'truncate_request_timeout_in_ms': 1,
> 'write_request_timeout_in_ms': 1}
> - >> end captured logging << -
> Stacktrace
> File "/usr/lib/python2.7/unittest/case.py", line 329, in run
> testMethod()
> File "/home/automaton/cassandra-dtest/cql_tests.py", line 879, in
> remote_query_test
> node1.start(wait_for_binary_proto=True, join_ring=False) # ensure other
> node executes queries
> File "/home/automaton/ccm/ccmlib/node.py", line 655, in start
> self.wait_for_binary_interface(from_mark=self.mark)
> File "/home/automaton/ccm/ccmlib/node.py", line 493, in
> wait_for_binary_interface
> self.watch_log_for("Starting listening for CQL clients", **kwargs)
> File "/home/automaton/ccm/ccmlib/node.py", line 450, in watch_log_for
> raise TimeoutError(time.strftime("%d %b %Y %H:%M:%S", time.gmtime()) + "
> [" + self.name + "] Missing: " + str([e.pattern for e in tofind]) + ":\n" +
> reads[:50] + ".\nSee {} for remainder".format(filename))
> "22 Aug 2016 04:05:15 [node1] Missing: ['Starting listening for CQL
> clients']:\nERROR [main] 2016-08-22 03:55:13,422 CassandraDaem.\nSee
> system.log for remainder\n >> begin captured logging <<
> \ndtest: DEBUG: cluster ccm directory:
> /tmp/dtest-qeHpYA\ndtest: DEBUG: Done setting configuration options:\n{
> 'initial_token': None,\n'num_tokens': '32',\n'phi_convict_threshold':
> 5,\n'range_request_timeout_in_ms': 1,\n
> 'read_request_timeout_in_ms': 1,\n'request_timeout_in_ms': 1,\n
> 'truncate_request_timeout_in_ms': 1,\n'write_request_timeout_in_ms':
> 1}\n- >> end captured logging <<
> -"
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (CASSANDRA-12518) dtest failure in upgrade_internal_auth_test.TestAuthUpgrade.upgrade_to_30_test
[ https://issues.apache.org/jira/browse/CASSANDRA-12518?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15431033#comment-15431033 ] Philip Thompson commented on CASSANDRA-12518: - I think for now just skipping it on offheap is sufficient. > dtest failure in upgrade_internal_auth_test.TestAuthUpgrade.upgrade_to_30_test > -- > > Key: CASSANDRA-12518 > URL: https://issues.apache.org/jira/browse/CASSANDRA-12518 > Project: Cassandra > Issue Type: Test >Reporter: Sean McCarthy >Assignee: Sean McCarthy > > example failure > http://cassci.datastax.com/job/trunk_offheap_dtest/379/testReport/upgrade_internal_auth_test/TestAuthUpgrade/upgrade_to_30_test/ -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CASSANDRA-12471) Allow for some form of "unset" in CQL's COPY command.
[ https://issues.apache.org/jira/browse/CASSANDRA-12471?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15431015#comment-15431015 ] Nate Sanders commented on CASSANDRA-12471: -- It's my understanding that in Cassandra protocol v4 (2.2 and above), we have a special value called "unset". In the Python driver, it's cassandra.query.UNSET_VALUE, for example. AFAICT, COPY FROM doesn't use these at all -- it just inserts nulls, which create tombstones. It seems that there should be a way to inform COPY FROM that you'd like to map, for example, the empty string to unset instead of null. I haven't thought this through carefully. It does seem to me that COPY FROM should be able to generate unset values in some cases, and currently I'm not sure this is possible. > Allow for some form of "unset" in CQL's COPY command. > - > > Key: CASSANDRA-12471 > URL: https://issues.apache.org/jira/browse/CASSANDRA-12471 > Project: Cassandra > Issue Type: New Feature > Components: CQL >Reporter: Nate Sanders >Priority: Minor > Fix For: 2.2.0 > > > Currently, it looks like there's no way to get "unset" values via the COPY > command, say, for example with empty string fields. Instead, these create > tombstones. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CASSANDRA-12517) dtest failure in upgrade_crc_check_chance_test.TestCrcCheckChanceUpgrade.crc_check_chance_upgrade_test
[ https://issues.apache.org/jira/browse/CASSANDRA-12517?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sean McCarthy updated CASSANDRA-12517: -- Resolution: Fixed Status: Resolved (was: Patch Available) Resolved with the patch from my previous comment. > dtest failure in > upgrade_crc_check_chance_test.TestCrcCheckChanceUpgrade.crc_check_chance_upgrade_test > -- > > Key: CASSANDRA-12517 > URL: https://issues.apache.org/jira/browse/CASSANDRA-12517 > Project: Cassandra > Issue Type: Test >Reporter: Sean McCarthy >Assignee: Sean McCarthy > Labels: dtest > > example failure: > http://cassci.datastax.com/job/trunk_offheap_dtest/377/testReport/upgrade_crc_check_chance_test/TestCrcCheckChanceUpgrade/crc_check_chance_upgrade_test -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CASSANDRA-12517) dtest failure in upgrade_crc_check_chance_test.TestCrcCheckChanceUpgrade.crc_check_chance_upgrade_test
[ https://issues.apache.org/jira/browse/CASSANDRA-12517?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sean McCarthy updated CASSANDRA-12517: -- Tester: Philip Thompson Status: Patch Available (was: In Progress) Excluding this test from off heap runs with this patch: https://github.com/riptano/cassandra-dtest/pull/1266/commits/0a84d1cc12e1e7c1d837fe0a97379271378f09dc > dtest failure in > upgrade_crc_check_chance_test.TestCrcCheckChanceUpgrade.crc_check_chance_upgrade_test > -- > > Key: CASSANDRA-12517 > URL: https://issues.apache.org/jira/browse/CASSANDRA-12517 > Project: Cassandra > Issue Type: Test >Reporter: Sean McCarthy >Assignee: Sean McCarthy > Labels: dtest > > example failure: > http://cassci.datastax.com/job/trunk_offheap_dtest/377/testReport/upgrade_crc_check_chance_test/TestCrcCheckChanceUpgrade/crc_check_chance_upgrade_test -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CASSANDRA-12518) dtest failure in upgrade_internal_auth_test.TestAuthUpgrade.upgrade_to_30_test
[ https://issues.apache.org/jira/browse/CASSANDRA-12518?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sean McCarthy updated CASSANDRA-12518: -- Reviewer: Philip Thompson Status: Patch Available (was: In Progress) Excluding the test from off heap runs with this patch: https://github.com/riptano/cassandra-dtest/pull/1266/commits/0a84d1cc12e1e7c1d837fe0a97379271378f09dc [~philipthompson], what do you think about the second part of Sam's comment? > dtest failure in upgrade_internal_auth_test.TestAuthUpgrade.upgrade_to_30_test > -- > > Key: CASSANDRA-12518 > URL: https://issues.apache.org/jira/browse/CASSANDRA-12518 > Project: Cassandra > Issue Type: Test >Reporter: Sean McCarthy >Assignee: Sean McCarthy > > example failure > http://cassci.datastax.com/job/trunk_offheap_dtest/379/testReport/upgrade_internal_auth_test/TestAuthUpgrade/upgrade_to_30_test/ -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CASSANDRA-12518) dtest failure in upgrade_internal_auth_test.TestAuthUpgrade.upgrade_to_30_test
[
https://issues.apache.org/jira/browse/CASSANDRA-12518?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15430995#comment-15430995
]
Sam Tunnicliffe commented on CASSANDRA-12518:
-
The reason this is failing is that it attempts to start a 3.0 node with
{{memtable_allocation_type: heap_buffers}} which isn't supported in that
version, resulting in this error from node1's log:
{code}
ERROR [main] 2016-08-21 01:40:03,040 CassandraDaemon.java:709 - Exception
encountered during startup
java.lang.ExceptionInInitializerError: null
at org.apache.cassandra.db.lifecycle.Tracker.reset(Tracker.java:199)
~[main/:na]
at org.apache.cassandra.db.lifecycle.Tracker.(Tracker.java:76)
~[main/:na]
at
org.apache.cassandra.db.ColumnFamilyStore.(ColumnFamilyStore.java:392)
~[main/:na]
at
org.apache.cassandra.db.ColumnFamilyStore.(ColumnFamilyStore.java:361)
~[main/:na]
at
org.apache.cassandra.db.ColumnFamilyStore.createColumnFamilyStore(ColumnFamilyStore.java:573)
~[main/:na]
at
org.apache.cassandra.db.ColumnFamilyStore.createColumnFamilyStore(ColumnFamilyStore.java:550)
~[main/:na]
at org.apache.cassandra.db.Keyspace.initCf(Keyspace.java:368)
~[main/:na]
at org.apache.cassandra.db.Keyspace.(Keyspace.java:305)
~[main/:na]
at org.apache.cassandra.db.Keyspace.open(Keyspace.java:129) ~[main/:na]
at org.apache.cassandra.db.Keyspace.open(Keyspace.java:106) ~[main/:na]
at
org.apache.cassandra.db.SystemKeyspace.checkHealth(SystemKeyspace.java:887)
~[main/:na]
at
org.apache.cassandra.service.StartupChecks$8.execute(StartupChecks.java:304)
~[main/:na]
at
org.apache.cassandra.service.StartupChecks.verify(StartupChecks.java:107)
~[main/:na]
at
org.apache.cassandra.service.CassandraDaemon.setup(CassandraDaemon.java:175)
[main/:na]
at
org.apache.cassandra.service.CassandraDaemon.activate(CassandraDaemon.java:568)
[main/:na]
at
org.apache.cassandra.service.CassandraDaemon.main(CassandraDaemon.java:696)
[main/:na]
Caused by: org.apache.cassandra.exceptions.ConfigurationException:
offheap_objects are not available in 3.0. They should be re-introduced in a
future release, see https://issues.apache.org/jira/browse/CASSANDRA-9472 for
details
at
org.apache.cassandra.config.DatabaseDescriptor.getMemtableAllocatorPool(DatabaseDescriptor.java:1887)
~[main/:na]
at org.apache.cassandra.db.Memtable.(Memtable.java:65)
~[main/:na]
... 16 common frames omitted
{code}
I guess that this test is a little idiosyncratic in that it tests upgrading
between 2 specific versions, whilst not being specifically "an upgrade test"
(there are a couple of similar upgrade_* tests for CRC check chance &
supercolumns). The original driver for this test was CASSANDRA-7653, which
modified the schema for internal auth. This was committed in 2.2, but
pre-ticktock we intended to support upgrades from 2.1 to both 2.2 and 3.0 and
so this was the functionality explicitly tested - hence the 2 test cases here
{{upgrade_to_22_test}} and {{upgrade_to_30_test}}. The first action I guess
would be to exclude this test from any of the offheap dtest runs, as it can
only ever fail there and any occurrence of the problems it is intended to catch
would be highlighted by the non-offheap runs.
A followup question is whether the test should be rewritten to more fully
exercise the various possible upgrade paths. A simple approach would be to just
add an {{upgrade_to_trunk_test}} variant, but this would need amending when
trunk moves to a version where we don't support upgrade from 2.1.
> dtest failure in upgrade_internal_auth_test.TestAuthUpgrade.upgrade_to_30_test
> --
>
> Key: CASSANDRA-12518
> URL: https://issues.apache.org/jira/browse/CASSANDRA-12518
> Project: Cassandra
> Issue Type: Test
>Reporter: Sean McCarthy
>Assignee: Sean McCarthy
>
> example failure
> http://cassci.datastax.com/job/trunk_offheap_dtest/379/testReport/upgrade_internal_auth_test/TestAuthUpgrade/upgrade_to_30_test/
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (CASSANDRA-11594) Too many open files on directories
[
https://issues.apache.org/jira/browse/CASSANDRA-11594?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15430979#comment-15430979
]
Philip Thompson commented on CASSANDRA-11594:
-
We're currently working on several other tickets, and could only pick this up
if we bumped one of those. Is that something we should do? We can talk offline.
> Too many open files on directories
> --
>
> Key: CASSANDRA-11594
> URL: https://issues.apache.org/jira/browse/CASSANDRA-11594
> Project: Cassandra
> Issue Type: Bug
> Components: Core
>Reporter: n0rad
>Assignee: Stefania
>Priority: Critical
> Attachments: openfiles.zip, screenshot.png
>
>
> I have a 6 nodes cluster in prod in 3 racks.
> each node :
> - 4Gb commitlogs on 343 files
> - 275Gb data on 504 files
> On saturday, 1 node in each rack crash with with too many open files (seems
> to be the similar node in each rack).
> {code}
> lsof -n -p $PID give me 66899 out of 65826 max
> {code}
> it contains 64527 open directories (2371 uniq)
> a part of the list :
> {code}
> java19076 root 2140r DIR 8,17 143360 4386718705
> /opt/stage2/pod-cassandra-aci-cassandra/rootfs/data/keyspaces/email_logs_query/emails-2d4abd00e9ea11e591199d740e07bd95
> java19076 root 2141r DIR 8,17 143360 4386718705
> /opt/stage2/pod-cassandra-aci-cassandra/rootfs/data/keyspaces/email_logs_query/emails-2d4abd00e9ea11e591199d740e07bd95
> java19076 root 2142r DIR 8,17 143360 4386718705
> /opt/stage2/pod-cassandra-aci-cassandra/rootfs/data/keyspaces/email_logs_query/emails-2d4abd00e9ea11e591199d740e07bd95
> java19076 root 2143r DIR 8,17 143360 4386718705
> /opt/stage2/pod-cassandra-aci-cassandra/rootfs/data/keyspaces/email_logs_query/emails-2d4abd00e9ea11e591199d740e07bd95
> java19076 root 2144r DIR 8,17 143360 4386718705
> /opt/stage2/pod-cassandra-aci-cassandra/rootfs/data/keyspaces/email_logs_query/emails-2d4abd00e9ea11e591199d740e07bd95
> java19076 root 2145r DIR 8,17 143360 4386718705
> /opt/stage2/pod-cassandra-aci-cassandra/rootfs/data/keyspaces/email_logs_query/emails-2d4abd00e9ea11e591199d740e07bd95
> java19076 root 2146r DIR 8,17 143360 4386718705
> /opt/stage2/pod-cassandra-aci-cassandra/rootfs/data/keyspaces/email_logs_query/emails-2d4abd00e9ea11e591199d740e07bd95
> java19076 root 2147r DIR 8,17 143360 4386718705
> /opt/stage2/pod-cassandra-aci-cassandra/rootfs/data/keyspaces/email_logs_query/emails-2d4abd00e9ea11e591199d740e07bd95
> java19076 root 2148r DIR 8,17 143360 4386718705
> /opt/stage2/pod-cassandra-aci-cassandra/rootfs/data/keyspaces/email_logs_query/emails-2d4abd00e9ea11e591199d740e07bd95
> java19076 root 2149r DIR 8,17 143360 4386718705
> /opt/stage2/pod-cassandra-aci-cassandra/rootfs/data/keyspaces/email_logs_query/emails-2d4abd00e9ea11e591199d740e07bd95
> java19076 root 2150r DIR 8,17 143360 4386718705
> /opt/stage2/pod-cassandra-aci-cassandra/rootfs/data/keyspaces/email_logs_query/emails-2d4abd00e9ea11e591199d740e07bd95
> java19076 root 2151r DIR 8,17 143360 4386718705
> /opt/stage2/pod-cassandra-aci-cassandra/rootfs/data/keyspaces/email_logs_query/emails-2d4abd00e9ea11e591199d740e07bd95
> java19076 root 2152r DIR 8,17 143360 4386718705
> /opt/stage2/pod-cassandra-aci-cassandra/rootfs/data/keyspaces/email_logs_query/emails-2d4abd00e9ea11e591199d740e07bd95
> java19076 root 2153r DIR 8,17 143360 4386718705
> /opt/stage2/pod-cassandra-aci-cassandra/rootfs/data/keyspaces/email_logs_query/emails-2d4abd00e9ea11e591199d740e07bd95
> java19076 root 2154r DIR 8,17 143360 4386718705
> /opt/stage2/pod-cassandra-aci-cassandra/rootfs/data/keyspaces/email_logs_query/emails-2d4abd00e9ea11e591199d740e07bd95
> java19076 root 2155r DIR 8,17 143360 4386718705
> /opt/stage2/pod-cassandra-aci-cassandra/rootfs/data/keyspaces/email_logs_query/emails-2d4abd00e9ea11e591199d740e07bd95
> {code}
> The 3 others nodes crashes 4 hours later
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (CASSANDRA-12423) Cells missing from compact storage table after upgrading from 2.1.9 to 3.7
[
https://issues.apache.org/jira/browse/CASSANDRA-12423?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15430959#comment-15430959
]
Adam Holmberg commented on CASSANDRA-12423:
---
We have [PYTHON-213|https://datastax-oss.atlassian.net/browse/PYTHON-213] open.
I believe I addressed what we discussed to the extent possible. There is a gist
linked there for your review if you're willing to take a look.
> Cells missing from compact storage table after upgrading from 2.1.9 to 3.7
> --
>
> Key: CASSANDRA-12423
> URL: https://issues.apache.org/jira/browse/CASSANDRA-12423
> Project: Cassandra
> Issue Type: Bug
>Reporter: Tomasz Grabiec
>Assignee: Stefania
> Attachments: 12423.tar.gz
>
>
> Schema:
> {code}
> create table ks1.test ( id int, c1 text, c2 text, v int, primary key (id, c1,
> c2)) with compact storage and compression = {'sstable_compression': ''};
> {code}
> sstable2json before upgrading:
> {code}
> [
> {"key": "1",
> "cells": [["","0",1470761440040513],
>["a","asd",2470761440040513,"t",1470764842],
>["asd:","0",1470761451368658],
>["asd:asd","0",1470761449416613]]}
> ]
> {code}
> Query result with 2.1.9:
> {code}
> cqlsh> select * from ks1.test;
> id | c1 | c2 | v
> +-+--+---
> 1 | | null | 0
> 1 | asd | | 0
> 1 | asd | asd | 0
> (3 rows)
> {code}
> Query result with 3.7:
> {code}
> cqlsh> select * from ks1.test;
> id | 6331 | 6332 | v
> +--+--+---
> 1 | | null | 0
> (1 rows)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Resolved] (CASSANDRA-12521) dtest failure in upgrade_tests.cql_tests.TestCQLNodes2RF1_Upgrade_current_3_x_To_indev_3_x.select_with_alias_test
[
https://issues.apache.org/jira/browse/CASSANDRA-12521?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Philip Thompson resolved CASSANDRA-12521.
-
Resolution: Duplicate
> dtest failure in
> upgrade_tests.cql_tests.TestCQLNodes2RF1_Upgrade_current_3_x_To_indev_3_x.select_with_alias_test
> -
>
> Key: CASSANDRA-12521
> URL: https://issues.apache.org/jira/browse/CASSANDRA-12521
> Project: Cassandra
> Issue Type: Test
>Reporter: Sean McCarthy
>Assignee: DS Test Eng
> Labels: dtest
> Attachments: node1.log, node1_debug.log, node1_gc.log, node2.log,
> node2_debug.log, node2_gc.log
>
>
> example failure:
> http://cassci.datastax.com/job/trunk_dtest_upgrade/30/testReport/upgrade_tests.cql_tests/TestCQLNodes2RF1_Upgrade_current_3_x_To_indev_3_x/select_with_alias_test
> {code}
> Error Message
> Regexp didn't match: "Aliases aren't allowed in the where clause" not found
> in 'Error from server: code=2200 [Invalid query] message="Undefined column
> name user_id"'
> {code}
> {code}
> Stacktrace
> File "/usr/lib/python2.7/unittest/case.py", line 329, in run
> testMethod()
> File "/home/automaton/cassandra-dtest/upgrade_tests/cql_tests.py", line
> 3189, in select_with_alias_test
> assert_invalid(cursor, 'SELECT id AS user_id, name AS user_name FROM
> users WHERE user_id = 0', matching=error_msg)
> File "/home/automaton/cassandra-dtest/assertions.py", line 92, in
> assert_invalid
> assert_exception(session, query, matching=matching, expected=expected)
> File "/home/automaton/cassandra-dtest/assertions.py", line 65, in
> assert_exception
> _assert_exception(session.execute, query, matching=matching,
> expected=expected)
> File "/home/automaton/cassandra-dtest/assertions.py", line 54, in
> _assert_exception
> assert_regexp_matches(str(e), matching)
> File "/usr/lib/python2.7/unittest/case.py", line 1002, in
> assertRegexpMatches
> raise self.failureException(msg)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (CASSANDRA-12476) SyntaxException when COPY FROM Counter Table with Null value
[
https://issues.apache.org/jira/browse/CASSANDRA-12476?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15430934#comment-15430934
]
Philip Thompson commented on CASSANDRA-12476:
-
We've fixed the issue, they are re-running
> SyntaxException when COPY FROM Counter Table with Null value
>
>
> Key: CASSANDRA-12476
> URL: https://issues.apache.org/jira/browse/CASSANDRA-12476
> Project: Cassandra
> Issue Type: Bug
> Components: Tools
>Reporter: Ashraful Islam
>Assignee: Stefania
>Priority: Minor
> Labels: cqlsh
> Fix For: 2.2.x, 3.0.x, 3.x
>
> Attachments:
> Fix_issue___CASSANDRA_12476__SyntaxException_when_COPY_FROM_Counter_Table_with_Null_value.patch
>
>
> I have a simple counter table
> {noformat}
> CREATE TABLE test (
> a int PRIMARY KEY,
> b counter,
> c counter
> ) ;
> {noformat}
> I have updated b column value with
> {noformat}
> UPDATE test SET b = b + 1 WHERE a = 1;
> {noformat}
> Now I have export the data with
> {noformat}
> COPY test TO 'test.csv';
> {noformat}
> And Import it with
> {noformat}
> COPY test FROM 'test.csv';
> {noformat}
> I get this Error
> {noformat}
> Failed to import 1 rows: SyntaxException - line 1:34 no viable alternative at
> input 'WHERE' (...=b+1,c=c+ [WHERE]...) - will retry later, attempt 1 of 5
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (CASSANDRA-12521) dtest failure in upgrade_tests.cql_tests.TestCQLNodes2RF1_Upgrade_current_3_x_To_indev_3_x.select_with_alias_test
Sean McCarthy created CASSANDRA-12521:
-
Summary: dtest failure in
upgrade_tests.cql_tests.TestCQLNodes2RF1_Upgrade_current_3_x_To_indev_3_x.select_with_alias_test
Key: CASSANDRA-12521
URL: https://issues.apache.org/jira/browse/CASSANDRA-12521
Project: Cassandra
Issue Type: Test
Reporter: Sean McCarthy
Assignee: DS Test Eng
Attachments: node1.log, node1_debug.log, node1_gc.log, node2.log,
node2_debug.log, node2_gc.log
example failure:
http://cassci.datastax.com/job/trunk_dtest_upgrade/30/testReport/upgrade_tests.cql_tests/TestCQLNodes2RF1_Upgrade_current_3_x_To_indev_3_x/select_with_alias_test
{code}
Error Message
Regexp didn't match: "Aliases aren't allowed in the where clause" not found in
'Error from server: code=2200 [Invalid query] message="Undefined column name
user_id"'
{code}
{code}
Stacktrace
File "/usr/lib/python2.7/unittest/case.py", line 329, in run
testMethod()
File "/home/automaton/cassandra-dtest/upgrade_tests/cql_tests.py", line 3189,
in select_with_alias_test
assert_invalid(cursor, 'SELECT id AS user_id, name AS user_name FROM users
WHERE user_id = 0', matching=error_msg)
File "/home/automaton/cassandra-dtest/assertions.py", line 92, in
assert_invalid
assert_exception(session, query, matching=matching, expected=expected)
File "/home/automaton/cassandra-dtest/assertions.py", line 65, in
assert_exception
_assert_exception(session.execute, query, matching=matching,
expected=expected)
File "/home/automaton/cassandra-dtest/assertions.py", line 54, in
_assert_exception
assert_regexp_matches(str(e), matching)
File "/usr/lib/python2.7/unittest/case.py", line 1002, in assertRegexpMatches
raise self.failureException(msg)
{code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Resolved] (CASSANDRA-12520) dtest failure in upgrade_tests.upgrade_through_versions_test.ProtoV4Upgrade_AllVersions_RandomPartitioner_EndsAt_Trunk_HEAD.rolling_upgrade_test
[
https://issues.apache.org/jira/browse/CASSANDRA-12520?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sean McCarthy resolved CASSANDRA-12520.
---
Resolution: Duplicate
duplicate of CASSANDRA-12444
> dtest failure in
> upgrade_tests.upgrade_through_versions_test.ProtoV4Upgrade_AllVersions_RandomPartitioner_EndsAt_Trunk_HEAD.rolling_upgrade_test
>
>
> Key: CASSANDRA-12520
> URL: https://issues.apache.org/jira/browse/CASSANDRA-12520
> Project: Cassandra
> Issue Type: Test
>Reporter: Sean McCarthy
>Assignee: DS Test Eng
> Attachments: node1.log, node1_debug.log, node1_gc.log, node2.log,
> node2_debug.log, node2_gc.log, node3.log, node3_debug.log, node3_gc.log
>
>
> example failure:
> http://cassci.datastax.com/job/trunk_large_dtest/23/testReport/upgrade_tests.upgrade_through_versions_test/ProtoV4Upgrade_AllVersions_RandomPartitioner_EndsAt_Trunk_HEAD/rolling_upgrade_test/
> {code}
> Standard Output
> Error details:
> Errors seen in logs for: node2
> node2: ERROR [SharedPool-Worker-1] 2016-08-19 17:45:01,361 Message.java:611 -
> Unexpected exception during request; channel = [id: 0x8ab46d4d,
> /127.0.0.1:35769 => /127.0.0.2:9042]
> java.lang.AssertionError: null
> at
> org.apache.cassandra.db.ReadCommand$Serializer.serializedSize(ReadCommand.java:632)
> ~[apache-cassandra-3.0.8.jar:3.0.8]
> at
> org.apache.cassandra.db.ReadCommand$Serializer.serializedSize(ReadCommand.java:536)
> ~[apache-cassandra-3.0.8.jar:3.0.8]
> at org.apache.cassandra.net.MessageOut.payloadSize(MessageOut.java:166)
> ~[apache-cassandra-3.0.8.jar:3.0.8]
> at
> org.apache.cassandra.net.OutboundTcpConnectionPool.getConnection(OutboundTcpConnectionPool.java:72)
> ~[apache-cassandra-3.0.8.jar:3.0.8]
> at
> org.apache.cassandra.net.MessagingService.getConnection(MessagingService.java:609)
> ~[apache-cassandra-3.0.8.jar:3.0.8]
> at
> org.apache.cassandra.net.MessagingService.sendOneWay(MessagingService.java:758)
> ~[apache-cassandra-3.0.8.jar:3.0.8]
> at
> org.apache.cassandra.net.MessagingService.sendRR(MessagingService.java:701)
> ~[apache-cassandra-3.0.8.jar:3.0.8]
> at
> org.apache.cassandra.net.MessagingService.sendRRWithFailure(MessagingService.java:684)
> ~[apache-cassandra-3.0.8.jar:3.0.8]
> at
> org.apache.cassandra.service.AbstractReadExecutor.makeRequests(AbstractReadExecutor.java:110)
> ~[apache-cassandra-3.0.8.jar:3.0.8]
> at
> org.apache.cassandra.service.AbstractReadExecutor.makeDataRequests(AbstractReadExecutor.java:85)
> ~[apache-cassandra-3.0.8.jar:3.0.8]
> at
> org.apache.cassandra.service.AbstractReadExecutor$SpeculatingReadExecutor.executeAsync(AbstractReadExecutor.java:264)
> ~[apache-cassandra-3.0.8.jar:3.0.8]
> at
> org.apache.cassandra.service.StorageProxy$SinglePartitionReadLifecycle.doInitialQueries(StorageProxy.java:1703)
> ~[apache-cassandra-3.0.8.jar:3.0.8]
> at
> org.apache.cassandra.service.StorageProxy.fetchRows(StorageProxy.java:1658)
> ~[apache-cassandra-3.0.8.jar:3.0.8]
> at
> org.apache.cassandra.service.StorageProxy.readRegular(StorageProxy.java:1605)
> ~[apache-cassandra-3.0.8.jar:3.0.8]
> at
> org.apache.cassandra.service.StorageProxy.read(StorageProxy.java:1524)
> ~[apache-cassandra-3.0.8.jar:3.0.8]
> at
> org.apache.cassandra.db.SinglePartitionReadCommand.execute(SinglePartitionReadCommand.java:335)
> ~[apache-cassandra-3.0.8.jar:3.0.8]
> at
> org.apache.cassandra.service.pager.AbstractQueryPager.fetchPage(AbstractQueryPager.java:67)
> ~[apache-cassandra-3.0.8.jar:3.0.8]
> at
> org.apache.cassandra.service.pager.SinglePartitionPager.fetchPage(SinglePartitionPager.java:34)
> ~[apache-cassandra-3.0.8.jar:3.0.8]
> at
> org.apache.cassandra.cql3.statements.SelectStatement$Pager$NormalPager.fetchPage(SelectStatement.java:315)
> ~[apache-cassandra-3.0.8.jar:3.0.8]
> at
> org.apache.cassandra.cql3.statements.SelectStatement.execute(SelectStatement.java:351)
> ~[apache-cassandra-3.0.8.jar:3.0.8]
> at
> org.apache.cassandra.cql3.statements.SelectStatement.execute(SelectStatement.java:227)
> ~[apache-cassandra-3.0.8.jar:3.0.8]
> at
> org.apache.cassandra.cql3.statements.SelectStatement.execute(SelectStatement.java:76)
> ~[apache-cassandra-3.0.8.jar:3.0.8]
> at
> org.apache.cassandra.cql3.QueryProcessor.processStatement(QueryProcessor.java:206)
> ~[apache-cassandra-3.0.8.jar:3.0.8]
> at
> org.apache.cassandra.cql3.QueryProcessor.processPrepared(QueryProcessor.java:487)
> ~[apache-cassandra-3.0.8.jar:3.0.8]
> at
> org.apache.cassandra.cql3.QueryProcessor.processPrepared(QueryProcessor.java:464)
> ~[apache-cassandra-3.0
[jira] [Created] (CASSANDRA-12519) dtest failure in offline_tools_test.TestOfflineTools.sstableofflinerelevel_test
Sean McCarthy created CASSANDRA-12519:
-
Summary: dtest failure in
offline_tools_test.TestOfflineTools.sstableofflinerelevel_test
Key: CASSANDRA-12519
URL: https://issues.apache.org/jira/browse/CASSANDRA-12519
Project: Cassandra
Issue Type: Test
Reporter: Sean McCarthy
Assignee: DS Test Eng
Attachments: node1.log, node1_debug.log, node1_gc.log
example failure:
http://cassci.datastax.com/job/trunk_offheap_dtest/379/testReport/offline_tools_test/TestOfflineTools/sstableofflinerelevel_test/
{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 209, in
sstableofflinerelevel_test
self.assertGreater(max(final_levels), 1)
File "/usr/lib/python2.7/unittest/case.py", line 942, in assertGreater
self.fail(self._formatMessage(msg, standardMsg))
File "/usr/lib/python2.7/unittest/case.py", line 410, in fail
raise self.failureException(msg)
"1 not greater than 1
{code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (CASSANDRA-12520) dtest failure in upgrade_tests.upgrade_through_versions_test.ProtoV4Upgrade_AllVersions_RandomPartitioner_EndsAt_Trunk_HEAD.rolling_upgrade_test
Sean McCarthy created CASSANDRA-12520:
-
Summary: dtest failure in
upgrade_tests.upgrade_through_versions_test.ProtoV4Upgrade_AllVersions_RandomPartitioner_EndsAt_Trunk_HEAD.rolling_upgrade_test
Key: CASSANDRA-12520
URL: https://issues.apache.org/jira/browse/CASSANDRA-12520
Project: Cassandra
Issue Type: Test
Reporter: Sean McCarthy
Assignee: DS Test Eng
Attachments: node1.log, node1_debug.log, node1_gc.log, node2.log,
node2_debug.log, node2_gc.log, node3.log, node3_debug.log, node3_gc.log
example failure:
http://cassci.datastax.com/job/trunk_large_dtest/23/testReport/upgrade_tests.upgrade_through_versions_test/ProtoV4Upgrade_AllVersions_RandomPartitioner_EndsAt_Trunk_HEAD/rolling_upgrade_test/
{code}
Standard Output
Error details:
Errors seen in logs for: node2
node2: ERROR [SharedPool-Worker-1] 2016-08-19 17:45:01,361 Message.java:611 -
Unexpected exception during request; channel = [id: 0x8ab46d4d,
/127.0.0.1:35769 => /127.0.0.2:9042]
java.lang.AssertionError: null
at
org.apache.cassandra.db.ReadCommand$Serializer.serializedSize(ReadCommand.java:632)
~[apache-cassandra-3.0.8.jar:3.0.8]
at
org.apache.cassandra.db.ReadCommand$Serializer.serializedSize(ReadCommand.java:536)
~[apache-cassandra-3.0.8.jar:3.0.8]
at org.apache.cassandra.net.MessageOut.payloadSize(MessageOut.java:166)
~[apache-cassandra-3.0.8.jar:3.0.8]
at
org.apache.cassandra.net.OutboundTcpConnectionPool.getConnection(OutboundTcpConnectionPool.java:72)
~[apache-cassandra-3.0.8.jar:3.0.8]
at
org.apache.cassandra.net.MessagingService.getConnection(MessagingService.java:609)
~[apache-cassandra-3.0.8.jar:3.0.8]
at
org.apache.cassandra.net.MessagingService.sendOneWay(MessagingService.java:758)
~[apache-cassandra-3.0.8.jar:3.0.8]
at
org.apache.cassandra.net.MessagingService.sendRR(MessagingService.java:701)
~[apache-cassandra-3.0.8.jar:3.0.8]
at
org.apache.cassandra.net.MessagingService.sendRRWithFailure(MessagingService.java:684)
~[apache-cassandra-3.0.8.jar:3.0.8]
at
org.apache.cassandra.service.AbstractReadExecutor.makeRequests(AbstractReadExecutor.java:110)
~[apache-cassandra-3.0.8.jar:3.0.8]
at
org.apache.cassandra.service.AbstractReadExecutor.makeDataRequests(AbstractReadExecutor.java:85)
~[apache-cassandra-3.0.8.jar:3.0.8]
at
org.apache.cassandra.service.AbstractReadExecutor$SpeculatingReadExecutor.executeAsync(AbstractReadExecutor.java:264)
~[apache-cassandra-3.0.8.jar:3.0.8]
at
org.apache.cassandra.service.StorageProxy$SinglePartitionReadLifecycle.doInitialQueries(StorageProxy.java:1703)
~[apache-cassandra-3.0.8.jar:3.0.8]
at
org.apache.cassandra.service.StorageProxy.fetchRows(StorageProxy.java:1658)
~[apache-cassandra-3.0.8.jar:3.0.8]
at
org.apache.cassandra.service.StorageProxy.readRegular(StorageProxy.java:1605)
~[apache-cassandra-3.0.8.jar:3.0.8]
at
org.apache.cassandra.service.StorageProxy.read(StorageProxy.java:1524)
~[apache-cassandra-3.0.8.jar:3.0.8]
at
org.apache.cassandra.db.SinglePartitionReadCommand.execute(SinglePartitionReadCommand.java:335)
~[apache-cassandra-3.0.8.jar:3.0.8]
at
org.apache.cassandra.service.pager.AbstractQueryPager.fetchPage(AbstractQueryPager.java:67)
~[apache-cassandra-3.0.8.jar:3.0.8]
at
org.apache.cassandra.service.pager.SinglePartitionPager.fetchPage(SinglePartitionPager.java:34)
~[apache-cassandra-3.0.8.jar:3.0.8]
at
org.apache.cassandra.cql3.statements.SelectStatement$Pager$NormalPager.fetchPage(SelectStatement.java:315)
~[apache-cassandra-3.0.8.jar:3.0.8]
at
org.apache.cassandra.cql3.statements.SelectStatement.execute(SelectStatement.java:351)
~[apache-cassandra-3.0.8.jar:3.0.8]
at
org.apache.cassandra.cql3.statements.SelectStatement.execute(SelectStatement.java:227)
~[apache-cassandra-3.0.8.jar:3.0.8]
at
org.apache.cassandra.cql3.statements.SelectStatement.execute(SelectStatement.java:76)
~[apache-cassandra-3.0.8.jar:3.0.8]
at
org.apache.cassandra.cql3.QueryProcessor.processStatement(QueryProcessor.java:206)
~[apache-cassandra-3.0.8.jar:3.0.8]
at
org.apache.cassandra.cql3.QueryProcessor.processPrepared(QueryProcessor.java:487)
~[apache-cassandra-3.0.8.jar:3.0.8]
at
org.apache.cassandra.cql3.QueryProcessor.processPrepared(QueryProcessor.java:464)
~[apache-cassandra-3.0.8.jar:3.0.8]
at
org.apache.cassandra.transport.messages.ExecuteMessage.execute(ExecuteMessage.java:130)
~[apache-cassandra-3.0.8.jar:3.0.8]
at
org.apache.cassandra.transport.Message$Dispatcher.channelRead0(Message.java:507)
[apache-cassandra-3.0.8.jar:3.0.8]
at
org.apache.cassandra.transport.Message$Dispatcher.channelRead0(Message.java:401)
[apache-cassandra-3.0.8.jar:3.0.8]
at
io.netty.channel.SimpleCha
[jira] [Created] (CASSANDRA-12518) dtest failure in upgrade_internal_auth_test.TestAuthUpgrade.upgrade_to_30_test
Sean McCarthy created CASSANDRA-12518: - Summary: dtest failure in upgrade_internal_auth_test.TestAuthUpgrade.upgrade_to_30_test Key: CASSANDRA-12518 URL: https://issues.apache.org/jira/browse/CASSANDRA-12518 Project: Cassandra Issue Type: Test Reporter: Sean McCarthy Assignee: Sean McCarthy example failure http://cassci.datastax.com/job/trunk_offheap_dtest/379/testReport/upgrade_internal_auth_test/TestAuthUpgrade/upgrade_to_30_test/ -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (CASSANDRA-12154) "SELECT * FROM foo LIMIT ;" does not error out
[
https://issues.apache.org/jira/browse/CASSANDRA-12154?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Stupp resolved CASSANDRA-12154.
--
Resolution: Fixed
Fix Version/s: (was: 3.x)
3.10
CI looks good.
Committed as
[4c84d40978c2f6f94f327c1aef1d522e2a107a35|https://github.com/apache/cassandra/commit/4c84d40978c2f6f94f327c1aef1d522e2a107a35]
to [trunk|https://github.com/apache/cassandra/tree/trunk] (not to 3.0).
Thanks for pointing out the issue, [~ethx].
> "SELECT * FROM foo LIMIT ;" does not error out
> --
>
> Key: CASSANDRA-12154
> URL: https://issues.apache.org/jira/browse/CASSANDRA-12154
> Project: Cassandra
> Issue Type: Bug
> Components: CQL
>Reporter: Robert Stupp
>Assignee: Thomas Boucher
>Priority: Minor
> Labels: lhf
> Fix For: 3.10
>
>
> We found out that {{SELECT * FROM foo LIMIT ;}} is unanimously accepted and
> executed but it should not.
> Have not dug deeper why that is possible (it's not a big issue IMO) but it is
> strange. Seems it doesn't parse {{LIMIT}} as {{K_LIMIT}} because otherwise it
> would require an int argument.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
cassandra git commit: "SELECT * FROM foo LIMIT ;" does not error out
Repository: cassandra
Updated Branches:
refs/heads/trunk f2d5cd0f7 -> 4c84d4097
"SELECT * FROM foo LIMIT ;" does not error out
patch by Thomas Boucher; reviewed by Robert Stupp for CASSANDRA-12154
Project: http://git-wip-us.apache.org/repos/asf/cassandra/repo
Commit: http://git-wip-us.apache.org/repos/asf/cassandra/commit/4c84d409
Tree: http://git-wip-us.apache.org/repos/asf/cassandra/tree/4c84d409
Diff: http://git-wip-us.apache.org/repos/asf/cassandra/diff/4c84d409
Branch: refs/heads/trunk
Commit: 4c84d40978c2f6f94f327c1aef1d522e2a107a35
Parents: f2d5cd0
Author: Thomas Boucher
Authored: Mon Aug 22 16:35:29 2016 +0200
Committer: Robert Stupp
Committed: Mon Aug 22 16:35:29 2016 +0200
--
CHANGES.txt| 1 +
src/antlr/Parser.g | 6 ++
2 files changed, 3 insertions(+), 4 deletions(-)
--
http://git-wip-us.apache.org/repos/asf/cassandra/blob/4c84d409/CHANGES.txt
--
diff --git a/CHANGES.txt b/CHANGES.txt
index 1c73c7d..2cedefc 100644
--- a/CHANGES.txt
+++ b/CHANGES.txt
@@ -1,4 +1,5 @@
3.10
+ * "SELECT * FROM foo LIMIT ;" does not error out (CASSANDRA-12154)
* Define executeLocally() at the ReadQuery Level (CASSANDRA-12474)
* Extend read/write failure messages with a map of replica addresses
to error codes in the v5 native protocol (CASSANDRA-12311)
http://git-wip-us.apache.org/repos/asf/cassandra/blob/4c84d409/src/antlr/Parser.g
--
diff --git a/src/antlr/Parser.g b/src/antlr/Parser.g
index d33125f..7273286 100644
--- a/src/antlr/Parser.g
+++ b/src/antlr/Parser.g
@@ -378,8 +378,7 @@ jsonInsertStatement [CFName cf] returns
[UpdateStatement.ParsedInsertJson expr]
;
jsonValue returns [Json.Raw value]
-:
-| s=STRING_LITERAL { $value = new Json.Literal($s.text); }
+: s=STRING_LITERAL { $value = new Json.Literal($s.text); }
| ':' id=noncol_ident { $value = newJsonBindVariables(id); }
| QMARK{ $value = newJsonBindVariables(null); }
;
@@ -1294,8 +1293,7 @@ value returns [Term.Raw value]
;
intValue returns [Term.Raw value]
-:
-| t=INTEGER { $value = Constants.Literal.integer($t.text); }
+: t=INTEGER { $value = Constants.Literal.integer($t.text); }
| ':' id=noncol_ident { $value = newBindVariables(id); }
| QMARK { $value = newBindVariables(null); }
;
[jira] [Created] (CASSANDRA-12517) dtest failure in upgrade_crc_check_chance_test.TestCrcCheckChanceUpgrade.crc_check_chance_upgrade_test
Sean McCarthy created CASSANDRA-12517: - Summary: dtest failure in upgrade_crc_check_chance_test.TestCrcCheckChanceUpgrade.crc_check_chance_upgrade_test Key: CASSANDRA-12517 URL: https://issues.apache.org/jira/browse/CASSANDRA-12517 Project: Cassandra Issue Type: Test Reporter: Sean McCarthy Assignee: Sean McCarthy example failure: http://cassci.datastax.com/job/trunk_offheap_dtest/377/testReport/upgrade_crc_check_chance_test/TestCrcCheckChanceUpgrade/crc_check_chance_upgrade_test -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (CASSANDRA-12516) Interned column identifiers can be overridden incorrectly
Aleksey Yeschenko created CASSANDRA-12516:
-
Summary: Interned column identifiers can be overridden incorrectly
Key: CASSANDRA-12516
URL: https://issues.apache.org/jira/browse/CASSANDRA-12516
Project: Cassandra
Issue Type: Bug
Reporter: Aleksey Yeschenko
Assignee: Stefania
Fix For: 2.1.x, 2.2.x, 3.0.x, 3.x
As discovered by [~Stefania] in CASSANDRA-12423, our use of
{{ColumnIdentifier.internedInstances}} to map byte buffer column names to
column identifiers is incorrect. It's possible for two non-equal
{{ColumnIdentifier}} instances to have the same {{ByteBuffer}} as raw name, and
yet different text representations, due to different column name types, leading
to hard to debug correctness issues.
Should either amend the map to have the type as part of the key, or limit the
use of that map.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (CASSANDRA-12423) Cells missing from compact storage table after upgrading from 2.1.9 to 3.7
[
https://issues.apache.org/jira/browse/CASSANDRA-12423?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15430784#comment-15430784
]
Aleksey Yeschenko commented on CASSANDRA-12423:
---
Looked into it more, together with Stefania. To sum it up, in no particular
order:
1. {{DESCRIBE}} output is broken. Sparse compact tables (with regular columns
defined) that have non-text comparators should be filtered out from
{{DESCRIBE}} output, as they cannot currently be represented via CQL {{CREATE
TABLE}}. [~aholmber] I've raised this issue privately, do you remember if there
is a python-driver JIRA open for it already? (also for filtering out supers).
[~ifesdjeen] same goes for a follow-up JIRA to CASSANDRA-7190
2. The column names for {{Keyspace1.Standard3}} in schema tables in 2.1 and 3.0
are both correct. Should be using {{BytesType}} for regulars in 2.1 (statics in
3.0) given the {{BytesType}} comparator.
3. Yup, you are pretty much right about {{ColumnIdentifier.getInterned()}}
being relied on incorrectly. We should fix this in 2.1 and upwards. I'll open a
separate JIRA (assign to you, if you don't mind it), and link to this one, to
either make the type part of the key in the interned map, or just limit its use.
> Cells missing from compact storage table after upgrading from 2.1.9 to 3.7
> --
>
> Key: CASSANDRA-12423
> URL: https://issues.apache.org/jira/browse/CASSANDRA-12423
> Project: Cassandra
> Issue Type: Bug
>Reporter: Tomasz Grabiec
>Assignee: Stefania
> Attachments: 12423.tar.gz
>
>
> Schema:
> {code}
> create table ks1.test ( id int, c1 text, c2 text, v int, primary key (id, c1,
> c2)) with compact storage and compression = {'sstable_compression': ''};
> {code}
> sstable2json before upgrading:
> {code}
> [
> {"key": "1",
> "cells": [["","0",1470761440040513],
>["a","asd",2470761440040513,"t",1470764842],
>["asd:","0",1470761451368658],
>["asd:asd","0",1470761449416613]]}
> ]
> {code}
> Query result with 2.1.9:
> {code}
> cqlsh> select * from ks1.test;
> id | c1 | c2 | v
> +-+--+---
> 1 | | null | 0
> 1 | asd | | 0
> 1 | asd | asd | 0
> (3 rows)
> {code}
> Query result with 3.7:
> {code}
> cqlsh> select * from ks1.test;
> id | 6331 | 6332 | v
> +--+--+---
> 1 | | null | 0
> (1 rows)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (CASSANDRA-12423) Cells missing from compact storage table after upgrading from 2.1.9 to 3.7
[
https://issues.apache.org/jira/browse/CASSANDRA-12423?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15430720#comment-15430720
]
Aleksey Yeschenko commented on CASSANDRA-12423:
---
As for {{ColumnIdentifier.getInterned()}} use, I still haven't looked at the
exact issue you are facing here, so it may or may not be related. *But* overall
this is definitely a potential problem. It's been broken since forever, and
should be fixed in 2.1 upwards. The bytebuffer name does not unambiguously
represent a column identifier, the type should be part of the key.
> Cells missing from compact storage table after upgrading from 2.1.9 to 3.7
> --
>
> Key: CASSANDRA-12423
> URL: https://issues.apache.org/jira/browse/CASSANDRA-12423
> Project: Cassandra
> Issue Type: Bug
>Reporter: Tomasz Grabiec
>Assignee: Stefania
> Attachments: 12423.tar.gz
>
>
> Schema:
> {code}
> create table ks1.test ( id int, c1 text, c2 text, v int, primary key (id, c1,
> c2)) with compact storage and compression = {'sstable_compression': ''};
> {code}
> sstable2json before upgrading:
> {code}
> [
> {"key": "1",
> "cells": [["","0",1470761440040513],
>["a","asd",2470761440040513,"t",1470764842],
>["asd:","0",1470761451368658],
>["asd:asd","0",1470761449416613]]}
> ]
> {code}
> Query result with 2.1.9:
> {code}
> cqlsh> select * from ks1.test;
> id | c1 | c2 | v
> +-+--+---
> 1 | | null | 0
> 1 | asd | | 0
> 1 | asd | asd | 0
> (3 rows)
> {code}
> Query result with 3.7:
> {code}
> cqlsh> select * from ks1.test;
> id | 6331 | 6332 | v
> +--+--+---
> 1 | | null | 0
> (1 rows)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (CASSANDRA-12423) Cells missing from compact storage table after upgrading from 2.1.9 to 3.7
[
https://issues.apache.org/jira/browse/CASSANDRA-12423?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15430701#comment-15430701
]
Aleksey Yeschenko commented on CASSANDRA-12423:
---
Looking into it. That said, there have been some changes to
{{CompactTables.columnDefinitionComparator()}} method recently in 3.0/trunk.
Only {{regular}} column names should use the comparator to decode/encode the
column name, never clustering columns.
> Cells missing from compact storage table after upgrading from 2.1.9 to 3.7
> --
>
> Key: CASSANDRA-12423
> URL: https://issues.apache.org/jira/browse/CASSANDRA-12423
> Project: Cassandra
> Issue Type: Bug
>Reporter: Tomasz Grabiec
>Assignee: Stefania
> Attachments: 12423.tar.gz
>
>
> Schema:
> {code}
> create table ks1.test ( id int, c1 text, c2 text, v int, primary key (id, c1,
> c2)) with compact storage and compression = {'sstable_compression': ''};
> {code}
> sstable2json before upgrading:
> {code}
> [
> {"key": "1",
> "cells": [["","0",1470761440040513],
>["a","asd",2470761440040513,"t",1470764842],
>["asd:","0",1470761451368658],
>["asd:asd","0",1470761449416613]]}
> ]
> {code}
> Query result with 2.1.9:
> {code}
> cqlsh> select * from ks1.test;
> id | c1 | c2 | v
> +-+--+---
> 1 | | null | 0
> 1 | asd | | 0
> 1 | asd | asd | 0
> (3 rows)
> {code}
> Query result with 3.7:
> {code}
> cqlsh> select * from ks1.test;
> id | 6331 | 6332 | v
> +--+--+---
> 1 | | null | 0
> (1 rows)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (CASSANDRA-12515) dtest failure in cql_tests.SlowQueryTester.remote_query_test
Craig Kodman created CASSANDRA-12515:
Summary: dtest failure in
cql_tests.SlowQueryTester.remote_query_test
Key: CASSANDRA-12515
URL: https://issues.apache.org/jira/browse/CASSANDRA-12515
Project: Cassandra
Issue Type: Test
Reporter: Craig Kodman
Assignee: DS Test Eng
Attachments: node1.log, node1_debug.log, node1_gc.log
example failure:
http://cassci.datastax.com/job/cassandra-2.2_dtest/680/testReport/cql_tests/SlowQueryTester/remote_query_test
{code}
Error Message
22 Aug 2016 04:05:15 [node1] Missing: ['Starting listening for CQL clients']:
ERROR [main] 2016-08-22 03:55:13,422 CassandraDaem.
See system.log for remainder
>> begin captured logging <<
dtest: DEBUG: cluster ccm directory: /tmp/dtest-qeHpYA
dtest: DEBUG: Done setting configuration options:
{ 'initial_token': None,
'num_tokens': '32',
'phi_convict_threshold': 5,
'range_request_timeout_in_ms': 1,
'read_request_timeout_in_ms': 1,
'request_timeout_in_ms': 1,
'truncate_request_timeout_in_ms': 1,
'write_request_timeout_in_ms': 1}
- >> end captured logging << -
Stacktrace
File "/usr/lib/python2.7/unittest/case.py", line 329, in run
testMethod()
File "/home/automaton/cassandra-dtest/cql_tests.py", line 879, in
remote_query_test
node1.start(wait_for_binary_proto=True, join_ring=False) # ensure other
node executes queries
File "/home/automaton/ccm/ccmlib/node.py", line 655, in start
self.wait_for_binary_interface(from_mark=self.mark)
File "/home/automaton/ccm/ccmlib/node.py", line 493, in
wait_for_binary_interface
self.watch_log_for("Starting listening for CQL clients", **kwargs)
File "/home/automaton/ccm/ccmlib/node.py", line 450, in watch_log_for
raise TimeoutError(time.strftime("%d %b %Y %H:%M:%S", time.gmtime()) + " ["
+ self.name + "] Missing: " + str([e.pattern for e in tofind]) + ":\n" +
reads[:50] + ".\nSee {} for remainder".format(filename))
"22 Aug 2016 04:05:15 [node1] Missing: ['Starting listening for CQL
clients']:\nERROR [main] 2016-08-22 03:55:13,422 CassandraDaem.\nSee
system.log for remainder\n >> begin captured logging <<
\ndtest: DEBUG: cluster ccm directory:
/tmp/dtest-qeHpYA\ndtest: DEBUG: Done setting configuration options:\n{
'initial_token': None,\n'num_tokens': '32',\n'phi_convict_threshold':
5,\n'range_request_timeout_in_ms': 1,\n
'read_request_timeout_in_ms': 1,\n'request_timeout_in_ms': 1,\n
'truncate_request_timeout_in_ms': 1,\n'write_request_timeout_in_ms':
1}\n- >> end captured logging << -"
{code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (CASSANDRA-12514) dtest failure in cql_tests.SlowQueryTester.disable_slow_query_log_test
[
https://issues.apache.org/jira/browse/CASSANDRA-12514?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Craig Kodman updated CASSANDRA-12514:
-
Description:
example failure:
http://cassci.datastax.com/job/cassandra-2.2_dtest/680/testReport/cql_tests/SlowQueryTester/disable_slow_query_log_test
http://cassci.datastax.com/job/cassandra-2.2_dtest/680/testReport/cql_tests/SlowQueryTester/local_query_test/
{code}
Error Message
Error starting node1.
>> begin captured logging <<
dtest: DEBUG: cluster ccm directory: /tmp/dtest-rDW1JQ
dtest: DEBUG: Done setting configuration options:
{ 'initial_token': None,
'num_tokens': '32',
'phi_convict_threshold': 5,
'range_request_timeout_in_ms': 1,
'read_request_timeout_in_ms': 1,
'request_timeout_in_ms': 1,
'truncate_request_timeout_in_ms': 1,
'write_request_timeout_in_ms': 1}
- >> end captured logging << -
Stacktrace
File "/usr/lib/python2.7/unittest/case.py", line 329, in run
testMethod()
File "/home/automaton/cassandra-dtest/cql_tests.py", line 945, in
disable_slow_query_log_test
"-Dcassandra.test.read_iteration_delay_ms=50"])
File "/home/automaton/ccm/ccmlib/cluster.py", line 414, in start
raise NodeError("Error starting {0}.".format(node.name), p)
"Error starting node1.\n >> begin captured logging <<
\ndtest: DEBUG: cluster ccm directory:
/tmp/dtest-rDW1JQ\ndtest: DEBUG: Done setting configuration options:\n{
'initial_token': None,\n'num_tokens': '32',\n'phi_convict_threshold':
5,\n'range_request_timeout_in_ms': 1,\n
'read_request_timeout_in_ms': 1,\n'request_timeout_in_ms': 1,\n
'truncate_request_timeout_in_ms': 1,\n'write_request_timeout_in_ms':
1}\n- >> end captured logging << -"
Standard Output
[node1 ERROR] org.apache.cassandra.exceptions.ConfigurationException: Invalid
yaml. Please remove properties [slow_query_log_timeout_in_ms] from your
cassandra.yaml
at
org.apache.cassandra.config.YamlConfigurationLoader$MissingPropertiesChecker.check(YamlConfigurationLoader.java:146)
at
org.apache.cassandra.config.YamlConfigurationLoader.loadConfig(YamlConfigurationLoader.java:113)
at
org.apache.cassandra.config.YamlConfigurationLoader.loadConfig(YamlConfigurationLoader.java:85)
at
org.apache.cassandra.config.DatabaseDescriptor.loadConfig(DatabaseDescriptor.java:135)
at
org.apache.cassandra.config.DatabaseDescriptor.(DatabaseDescriptor.java:119)
at
org.apache.cassandra.service.CassandraDaemon.activate(CassandraDaemon.java:507)
at
org.apache.cassandra.service.CassandraDaemon.main(CassandraDaemon.java:641)
{code}
was:
example failure:
http://cassci.datastax.com/job/cassandra-2.2_dtest/680/testReport/cql_tests/SlowQueryTester/disable_slow_query_log_test
{code}
Error Message
Error starting node1.
>> begin captured logging <<
dtest: DEBUG: cluster ccm directory: /tmp/dtest-rDW1JQ
dtest: DEBUG: Done setting configuration options:
{ 'initial_token': None,
'num_tokens': '32',
'phi_convict_threshold': 5,
'range_request_timeout_in_ms': 1,
'read_request_timeout_in_ms': 1,
'request_timeout_in_ms': 1,
'truncate_request_timeout_in_ms': 1,
'write_request_timeout_in_ms': 1}
- >> end captured logging << -
Stacktrace
File "/usr/lib/python2.7/unittest/case.py", line 329, in run
testMethod()
File "/home/automaton/cassandra-dtest/cql_tests.py", line 945, in
disable_slow_query_log_test
"-Dcassandra.test.read_iteration_delay_ms=50"])
File "/home/automaton/ccm/ccmlib/cluster.py", line 414, in start
raise NodeError("Error starting {0}.".format(node.name), p)
"Error starting node1.\n >> begin captured logging <<
\ndtest: DEBUG: cluster ccm directory:
/tmp/dtest-rDW1JQ\ndtest: DEBUG: Done setting configuration options:\n{
'initial_token': None,\n'num_tokens': '32',\n'phi_convict_threshold':
5,\n'range_request_timeout_in_ms': 1,\n
'read_request_timeout_in_ms': 1,\n'request_timeout_in_ms': 1,\n
'truncate_request_timeout_in_ms': 1,\n'write_request_timeout_in_ms':
1}\n- >> end captured logging << -"
Standard Output
[node1 ERROR] org.apache.cassandra.exceptions.ConfigurationException: Invalid
yaml. Please remove properties [slow_query_log_timeout_in_ms] from your
cassandra.yaml
at
org.apache.cassandra.config.YamlConfigurationLoader$MissingPropertiesChecker.check(YamlConfigurationLoader.java:146)
at
org.apache.cassandra.config.YamlConfigurationLoader.loadConfig(YamlConfigurationLoa
