[jira] [Commented] (CASSANDRA-10864) Dropped mutations high until cluster restart
[ https://issues.apache.org/jira/browse/CASSANDRA-10864?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16311471#comment-16311471 ] Jim Witschey commented on CASSANDRA-10864: -- No new insight from me. I'll defer to you, other Jeff, and Yuki here. > Dropped mutations high until cluster restart > > > Key: CASSANDRA-10864 > URL: https://issues.apache.org/jira/browse/CASSANDRA-10864 > Project: Cassandra > Issue Type: Bug >Reporter: Jeff Ferland > Labels: proposed-wontfix > > Originally raised and investigated in > https://www.mail-archive.com/user@cassandra.apache.org/msg44586.html > Cause is still unclear, but a rolling restart has on two occasions since been > performed to cope with dropped mutations and timed-out reads. > Pattern is indicative of some kind of code quality issue possibly involving > locking operations. Stack flame graphs do not show a clear difference between > restarts. -- This message was sent by Atlassian JIRA (v6.4.14#64029) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-12725) dtest failure in repair_tests.incremental_repair_test.TestIncRepair.sstable_marking_test_not_intersecting_all_ranges
[
https://issues.apache.org/jira/browse/CASSANDRA-12725?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15582829#comment-15582829
]
Jim Witschey commented on CASSANDRA-12725:
--
bq. What should happen if we run this tool on a node with no sstables
I feel like the way the tool failed here is reasonable. The failure message
could be better.
We should check that the tool fails on a node with no SSTables.
> dtest failure in
> repair_tests.incremental_repair_test.TestIncRepair.sstable_marking_test_not_intersecting_all_ranges
>
>
> Key: CASSANDRA-12725
> URL: https://issues.apache.org/jira/browse/CASSANDRA-12725
> Project: Cassandra
> Issue Type: Test
>Reporter: Sean McCarthy
>Assignee: DS Test Eng
> Labels: dtest
>
> example failure:
> http://cassci.datastax.com/job/trunk_offheap_dtest/406/testReport/repair_tests.incremental_repair_test/TestIncRepair/sstable_marking_test_not_intersecting_all_ranges
> {code}
> Error Message
> Subprocess sstablemetadata on keyspace: keyspace1, column_family: None exited
> with non-zero status; exit status: 1;
> stdout:
> usage: Usage: sstablemetadata [--gc_grace_seconds n]
> Dump contents of given SSTable to standard output in JSON format.
> --gc_grace_secondsThe gc_grace_seconds to use when
>calculating droppable tombstones
> {code}
> {code}
> Stacktrace
> File "/usr/lib/python2.7/unittest/case.py", line 329, in run
> testMethod()
> File
> "/home/automaton/cassandra-dtest/repair_tests/incremental_repair_test.py",
> line 366, in sstable_marking_test_not_intersecting_all_ranges
> for out in (node.run_sstablemetadata(keyspace='keyspace1').stdout for
> node in cluster.nodelist()):
> File
> "/home/automaton/cassandra-dtest/repair_tests/incremental_repair_test.py",
> line 366, in
> for out in (node.run_sstablemetadata(keyspace='keyspace1').stdout for
> node in cluster.nodelist()):
> File "/usr/local/lib/python2.7/dist-packages/ccmlib/node.py", line 1021, in
> run_sstablemetadata
> return handle_external_tool_process(p, "sstablemetadata on keyspace: {},
> column_family: {}".format(keyspace, column_families))
> File "/usr/local/lib/python2.7/dist-packages/ccmlib/node.py", line 1983, in
> handle_external_tool_process
> raise ToolError(cmd_args, rc, out, err)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (CASSANDRA-12137) dtest failure in sstable_generation_loading_test.TestSSTableGenerationAndLoading.sstableloader_compression_deflate_to_snappy_test
[
https://issues.apache.org/jira/browse/CASSANDRA-12137?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15546565#comment-15546565
]
Jim Witschey commented on CASSANDRA-12137:
--
Attempting a rerun here:
http://cassci.datastax.com/view/Parameterized/job/parameterized_dtest_multiplexer/346/
> dtest failure in
> sstable_generation_loading_test.TestSSTableGenerationAndLoading.sstableloader_compression_deflate_to_snappy_test
> -
>
> Key: CASSANDRA-12137
> URL: https://issues.apache.org/jira/browse/CASSANDRA-12137
> Project: Cassandra
> Issue Type: Test
>Reporter: Sean McCarthy
>Assignee: Jim Witschey
> Labels: dtest
>
> example failure:
> http://cassci.datastax.com/job/cassandra-3.0_dtest/764/testReport/sstable_generation_loading_test/TestSSTableGenerationAndLoading/sstableloader_compression_deflate_to_snappy_test
> {code}
> Stacktrace
> File "/usr/lib/python2.7/unittest/case.py", line 329, in run
> testMethod()
> File "/home/automaton/cassandra-dtest/sstable_generation_loading_test.py",
> line 75, in sstableloader_compression_deflate_to_snappy_test
> self.load_sstable_with_configuration('Deflate', 'Snappy')
> File "/home/automaton/cassandra-dtest/sstable_generation_loading_test.py",
> line 178, in load_sstable_with_configuration
> "sstableloader exited with a non-zero status: {}".format(exit_status))
> File "/usr/lib/python2.7/unittest/case.py", line 513, in assertEqual
> assertion_func(first, second, msg=msg)
> File "/usr/lib/python2.7/unittest/case.py", line 506, in _baseAssertEqual
> raise self.failureException(msg)
> "sstableloader exited with a non-zero status: 1
> {code}
> Related failures:
> http://cassci.datastax.com/job/cassandra-3.0_dtest/764/testReport/sstable_generation_loading_test/TestSSTableGenerationAndLoading/sstableloader_compression_none_to_snappy_test/
> http://cassci.datastax.com/job/cassandra-3.0_dtest/764/testReport/sstable_generation_loading_test/TestSSTableGenerationAndLoading/sstableloader_with_mv_test/
> Failed on CassCI build cassandra-3.0_dtest #764
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (CASSANDRA-11811) dtest failure in snapshot_test.TestArchiveCommitlog.test_archive_commitlog
[
https://issues.apache.org/jira/browse/CASSANDRA-11811?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15514525#comment-15514525
]
Jim Witschey commented on CASSANDRA-11811:
--
PR in flight and under discussion here:
https://github.com/riptano/cassandra-dtest/pull/1340
> dtest failure in snapshot_test.TestArchiveCommitlog.test_archive_commitlog
> --
>
> Key: CASSANDRA-11811
> URL: https://issues.apache.org/jira/browse/CASSANDRA-11811
> Project: Cassandra
> Issue Type: Bug
>Reporter: Philip Thompson
>Assignee: Jim Witschey
> Labels: dtest
> Fix For: 3.x
>
>
> example failure:
> http://cassci.datastax.com/job/trunk_dtest_win32/416/testReport/snapshot_test/TestArchiveCommitlog/test_archive_commitlog
> Failed on CassCI build trunk_dtest_win32 #416
> Relevant error is pasted. This is clearly a test problem. No idea why it only
> happens on windows, as of yet. Affecting most tests in the
> TestArchiveCommitlog suite
> {code}
> WARN: Failed to flush node: node1 on shutdown.
> Unexpected error in node1 log, error:
> ERROR [main] 2016-05-13 21:15:02,701 CassandraDaemon.java:729 - Fatal
> configuration error
> org.apache.cassandra.exceptions.ConfigurationException: Cannot change the
> number of tokens from 64 to 32
> at
> org.apache.cassandra.service.StorageService.joinTokenRing(StorageService.java:1043)
> ~[main/:na]
> at
> org.apache.cassandra.service.StorageService.initServer(StorageService.java:740)
> ~[main/:na]
> at
> org.apache.cassandra.service.StorageService.initServer(StorageService.java:625)
> ~[main/:na]
> at
> org.apache.cassandra.service.CassandraDaemon.setup(CassandraDaemon.java:368)
> [main/:na]
> at
> org.apache.cassandra.service.CassandraDaemon.activate(CassandraDaemon.java:583)
> [main/:na]
> at
> org.apache.cassandra.service.CassandraDaemon.main(CassandraDaemon.java:712)
> [main/:na]
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (CASSANDRA-11811) dtest failure in snapshot_test.TestArchiveCommitlog.test_archive_commitlog
[
https://issues.apache.org/jira/browse/CASSANDRA-11811?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15514070#comment-15514070
]
Jim Witschey commented on CASSANDRA-11811:
--
I can fix this quickly and easily in the CDC tests, but no promises for the
snapshot tests.
> dtest failure in snapshot_test.TestArchiveCommitlog.test_archive_commitlog
> --
>
> Key: CASSANDRA-11811
> URL: https://issues.apache.org/jira/browse/CASSANDRA-11811
> Project: Cassandra
> Issue Type: Bug
>Reporter: Philip Thompson
>Assignee: Jim Witschey
> Labels: dtest
> Fix For: 3.x
>
>
> example failure:
> http://cassci.datastax.com/job/trunk_dtest_win32/416/testReport/snapshot_test/TestArchiveCommitlog/test_archive_commitlog
> Failed on CassCI build trunk_dtest_win32 #416
> Relevant error is pasted. This is clearly a test problem. No idea why it only
> happens on windows, as of yet. Affecting most tests in the
> TestArchiveCommitlog suite
> {code}
> WARN: Failed to flush node: node1 on shutdown.
> Unexpected error in node1 log, error:
> ERROR [main] 2016-05-13 21:15:02,701 CassandraDaemon.java:729 - Fatal
> configuration error
> org.apache.cassandra.exceptions.ConfigurationException: Cannot change the
> number of tokens from 64 to 32
> at
> org.apache.cassandra.service.StorageService.joinTokenRing(StorageService.java:1043)
> ~[main/:na]
> at
> org.apache.cassandra.service.StorageService.initServer(StorageService.java:740)
> ~[main/:na]
> at
> org.apache.cassandra.service.StorageService.initServer(StorageService.java:625)
> ~[main/:na]
> at
> org.apache.cassandra.service.CassandraDaemon.setup(CassandraDaemon.java:368)
> [main/:na]
> at
> org.apache.cassandra.service.CassandraDaemon.activate(CassandraDaemon.java:583)
> [main/:na]
> at
> org.apache.cassandra.service.CassandraDaemon.main(CassandraDaemon.java:712)
> [main/:na]
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Assigned] (CASSANDRA-11811) dtest failure in snapshot_test.TestArchiveCommitlog.test_archive_commitlog
[
https://issues.apache.org/jira/browse/CASSANDRA-11811?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jim Witschey reassigned CASSANDRA-11811:
Assignee: Jim Witschey (was: DS Test Eng)
> dtest failure in snapshot_test.TestArchiveCommitlog.test_archive_commitlog
> --
>
> Key: CASSANDRA-11811
> URL: https://issues.apache.org/jira/browse/CASSANDRA-11811
> Project: Cassandra
> Issue Type: Bug
>Reporter: Philip Thompson
>Assignee: Jim Witschey
> Labels: dtest
> Fix For: 3.x
>
>
> example failure:
> http://cassci.datastax.com/job/trunk_dtest_win32/416/testReport/snapshot_test/TestArchiveCommitlog/test_archive_commitlog
> Failed on CassCI build trunk_dtest_win32 #416
> Relevant error is pasted. This is clearly a test problem. No idea why it only
> happens on windows, as of yet. Affecting most tests in the
> TestArchiveCommitlog suite
> {code}
> WARN: Failed to flush node: node1 on shutdown.
> Unexpected error in node1 log, error:
> ERROR [main] 2016-05-13 21:15:02,701 CassandraDaemon.java:729 - Fatal
> configuration error
> org.apache.cassandra.exceptions.ConfigurationException: Cannot change the
> number of tokens from 64 to 32
> at
> org.apache.cassandra.service.StorageService.joinTokenRing(StorageService.java:1043)
> ~[main/:na]
> at
> org.apache.cassandra.service.StorageService.initServer(StorageService.java:740)
> ~[main/:na]
> at
> org.apache.cassandra.service.StorageService.initServer(StorageService.java:625)
> ~[main/:na]
> at
> org.apache.cassandra.service.CassandraDaemon.setup(CassandraDaemon.java:368)
> [main/:na]
> at
> org.apache.cassandra.service.CassandraDaemon.activate(CassandraDaemon.java:583)
> [main/:na]
> at
> org.apache.cassandra.service.CassandraDaemon.main(CassandraDaemon.java:712)
> [main/:na]
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (CASSANDRA-12148) Improve determinism of CDC data availability
[
https://issues.apache.org/jira/browse/CASSANDRA-12148?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15513657#comment-15513657
]
Jim Witschey commented on CASSANDRA-12148:
--
Seeing a couple failures in the new test. Test report:
http://cassci.datastax.com/view/Parameterized/job/parameterized_dtest_multiplexer/326/testReport/
We see [some CDC index files created in the destination
node|http://cassci.datastax.com/view/Parameterized/job/parameterized_dtest_multiplexer/326/testReport/node_0_iter_001.cdc_test/TestCDC/test_cdc_data_available_in_cdc_raw/],
and [a case where the CDC segments are, unexpectedly, different after writing
non-CDC
data|http://cassci.datastax.com/view/Parameterized/job/parameterized_dtest_multiplexer/326/testReport/node_0_iter_001.cdc_test/TestCDC/test_insertion_and_commitlog_behavior_after_reaching_cdc_total_space/].
The second could be a bad expectation now that availability behavior has
changed, I'm not sure.
> Improve determinism of CDC data availability
>
>
> Key: CASSANDRA-12148
> URL: https://issues.apache.org/jira/browse/CASSANDRA-12148
> Project: Cassandra
> Issue Type: Improvement
>Reporter: Joshua McKenzie
>Assignee: Joshua McKenzie
>
> The latency with which CDC data becomes available has a known limitation due
> to our reliance on CommitLogSegments being discarded to have the data
> available in cdc_raw: if a slowly written table co-habitates a
> CommitLogSegment with CDC data, the CommitLogSegment won't be flushed until
> we hit either memory pressure on memtables or CommitLog limit pressure.
> Ultimately, this leaves a non-deterministic element to when data becomes
> available for CDC consumption unless a consumer parses live CommitLogSegments.
> To work around this limitation and make semi-realtime CDC consumption more
> friendly to end-users, I propose we extend CDC as follows:
> h6. High level:
> * Consumers parse hard links of active CommitLogSegments in cdc_raw instead
> of waiting for flush/discard and file move
> * C* stores an offset of the highest seen CDC mutation in a separate idx file
> per commit log segment in cdc_raw. Clients tail this index file, delta their
> local last parsed offset on change, and parse the corresponding commit log
> segment using their last parsed offset as min
> * C* flags that index file with an offset and DONE when the file is flushed
> so clients know when they can clean up
> h6. Details:
> * On creation of a CommitLogSegment, also hard-link the file in cdc_raw
> * On first write of a CDC-enabled mutation to a segment, we:
> ** Flag it as {{CDCState.CONTAINS}}
> ** Set a long tracking the {{CommitLogPosition}} of the 1st CDC-enabled
> mutation in the log
> ** Set a long in the CommitLogSegment tracking the offset of the end of the
> last written CDC mutation in the segment if higher than the previously known
> highest CDC offset
> * On subsequent writes to the segment, we update the offset of the highest
> known CDC data
> * On CommitLogSegment fsync, we write a file in cdc_raw as
> _cdc.idx containing the min offset and end offset fsynced to
> disk per file
> * On segment discard, if CDCState == {{CDCState.PERMITTED}}, delete both the
> segment in commitlog and in cdc_raw
> * On segment discard, if CDCState == {{CDCState.CONTAINS}}, delete the
> segment in commitlog and update the _cdc.idx file w/end offset
> and a DONE marker
> * On segment replay, store the highest end offset of seen CDC-enabled
> mutations from a segment and write that to _cdc.idx on
> completion of segment replay. This should bridge the potential correctness
> gap of a node writing to a segment and then dying before it can write the
> _cdc.idx file.
> This should allow clients to skip the beginning of a file to the 1st CDC
> mutation, track an offset of how far they've parsed, delta against the
> _cdc.idx file end offset, and use that as a determinant on when to parse new
> CDC data. Any existing clients written to the initial implementation of CDC
> need only add the _cdc.idx logic and checking for DONE marker
> to their code, so the burden on users to update to support this should be
> quite small for the benefit of having data available as soon as it's fsynced
> instead of at a non-deterministic time when potentially unrelated tables are
> flushed.
> Finally, we should look into extending the interface on CommitLogReader to be
> more friendly for realtime parsing, perhaps supporting taking a
> CommitLogDescriptor and RandomAccessReader and resuming readSection calls,
> assuming the reader is at the start of a SyncSegment. Would probably also
> need to rewind to the start of the segment before returning so subsequent
> calls would respect this contract. This would skip needing to deserialize the
> descriptor and all
[jira] [Commented] (CASSANDRA-12137) dtest failure in sstable_generation_loading_test.TestSSTableGenerationAndLoading.sstableloader_compression_deflate_to_snappy_test
[
https://issues.apache.org/jira/browse/CASSANDRA-12137?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15510051#comment-15510051
]
Jim Witschey commented on CASSANDRA-12137:
--
Good lord:
http://cassci.datastax.com/view/Parameterized/job/parameterized_dtest_multiplexer/319/testReport/
Does this look familiar at all?
> dtest failure in
> sstable_generation_loading_test.TestSSTableGenerationAndLoading.sstableloader_compression_deflate_to_snappy_test
> -
>
> Key: CASSANDRA-12137
> URL: https://issues.apache.org/jira/browse/CASSANDRA-12137
> Project: Cassandra
> Issue Type: Test
>Reporter: Sean McCarthy
>Assignee: Jim Witschey
> Labels: dtest
>
> example failure:
> http://cassci.datastax.com/job/cassandra-3.0_dtest/764/testReport/sstable_generation_loading_test/TestSSTableGenerationAndLoading/sstableloader_compression_deflate_to_snappy_test
> {code}
> Stacktrace
> File "/usr/lib/python2.7/unittest/case.py", line 329, in run
> testMethod()
> File "/home/automaton/cassandra-dtest/sstable_generation_loading_test.py",
> line 75, in sstableloader_compression_deflate_to_snappy_test
> self.load_sstable_with_configuration('Deflate', 'Snappy')
> File "/home/automaton/cassandra-dtest/sstable_generation_loading_test.py",
> line 178, in load_sstable_with_configuration
> "sstableloader exited with a non-zero status: {}".format(exit_status))
> File "/usr/lib/python2.7/unittest/case.py", line 513, in assertEqual
> assertion_func(first, second, msg=msg)
> File "/usr/lib/python2.7/unittest/case.py", line 506, in _baseAssertEqual
> raise self.failureException(msg)
> "sstableloader exited with a non-zero status: 1
> {code}
> Related failures:
> http://cassci.datastax.com/job/cassandra-3.0_dtest/764/testReport/sstable_generation_loading_test/TestSSTableGenerationAndLoading/sstableloader_compression_none_to_snappy_test/
> http://cassci.datastax.com/job/cassandra-3.0_dtest/764/testReport/sstable_generation_loading_test/TestSSTableGenerationAndLoading/sstableloader_with_mv_test/
> Failed on CassCI build cassandra-3.0_dtest #764
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (CASSANDRA-12148) Improve determinism of CDC data availability
[
https://issues.apache.org/jira/browse/CASSANDRA-12148?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15507392#comment-15507392
]
Jim Witschey commented on CASSANDRA-12148:
--
After review I've opened a [new
PR|https://github.com/riptano/cassandra-dtest/pull/1332]. The new CI run
mentioned above is
[here|http://cassci.datastax.com/view/Parameterized/job/parameterized_dtest_multiplexer/324/].
> Improve determinism of CDC data availability
>
>
> Key: CASSANDRA-12148
> URL: https://issues.apache.org/jira/browse/CASSANDRA-12148
> Project: Cassandra
> Issue Type: Improvement
>Reporter: Joshua McKenzie
>Assignee: Joshua McKenzie
>
> The latency with which CDC data becomes available has a known limitation due
> to our reliance on CommitLogSegments being discarded to have the data
> available in cdc_raw: if a slowly written table co-habitates a
> CommitLogSegment with CDC data, the CommitLogSegment won't be flushed until
> we hit either memory pressure on memtables or CommitLog limit pressure.
> Ultimately, this leaves a non-deterministic element to when data becomes
> available for CDC consumption unless a consumer parses live CommitLogSegments.
> To work around this limitation and make semi-realtime CDC consumption more
> friendly to end-users, I propose we extend CDC as follows:
> h6. High level:
> * Consumers parse hard links of active CommitLogSegments in cdc_raw instead
> of waiting for flush/discard and file move
> * C* stores an offset of the highest seen CDC mutation in a separate idx file
> per commit log segment in cdc_raw. Clients tail this index file, delta their
> local last parsed offset on change, and parse the corresponding commit log
> segment using their last parsed offset as min
> * C* flags that index file with an offset and DONE when the file is flushed
> so clients know when they can clean up
> h6. Details:
> * On creation of a CommitLogSegment, also hard-link the file in cdc_raw
> * On first write of a CDC-enabled mutation to a segment, we:
> ** Flag it as {{CDCState.CONTAINS}}
> ** Set a long tracking the {{CommitLogPosition}} of the 1st CDC-enabled
> mutation in the log
> ** Set a long in the CommitLogSegment tracking the offset of the end of the
> last written CDC mutation in the segment if higher than the previously known
> highest CDC offset
> * On subsequent writes to the segment, we update the offset of the highest
> known CDC data
> * On CommitLogSegment fsync, we write a file in cdc_raw as
> _cdc.idx containing the min offset and end offset fsynced to
> disk per file
> * On segment discard, if CDCState == {{CDCState.PERMITTED}}, delete both the
> segment in commitlog and in cdc_raw
> * On segment discard, if CDCState == {{CDCState.CONTAINS}}, delete the
> segment in commitlog and update the _cdc.idx file w/end offset
> and a DONE marker
> * On segment replay, store the highest end offset of seen CDC-enabled
> mutations from a segment and write that to _cdc.idx on
> completion of segment replay. This should bridge the potential correctness
> gap of a node writing to a segment and then dying before it can write the
> _cdc.idx file.
> This should allow clients to skip the beginning of a file to the 1st CDC
> mutation, track an offset of how far they've parsed, delta against the
> _cdc.idx file end offset, and use that as a determinant on when to parse new
> CDC data. Any existing clients written to the initial implementation of CDC
> need only add the _cdc.idx logic and checking for DONE marker
> to their code, so the burden on users to update to support this should be
> quite small for the benefit of having data available as soon as it's fsynced
> instead of at a non-deterministic time when potentially unrelated tables are
> flushed.
> Finally, we should look into extending the interface on CommitLogReader to be
> more friendly for realtime parsing, perhaps supporting taking a
> CommitLogDescriptor and RandomAccessReader and resuming readSection calls,
> assuming the reader is at the start of a SyncSegment. Would probably also
> need to rewind to the start of the segment before returning so subsequent
> calls would respect this contract. This would skip needing to deserialize the
> descriptor and all completed SyncSegments to get to the root of the desired
> segment for parsing.
> One alternative we discussed offline - instead of just storing the highest
> seen CDC offset, we could instead store an offset per CDC mutation
> (potentially delta encoded) in the idx file to allow clients to seek and only
> parse the mutations with CDC enabled. My hunch is that the performance delta
> from doing so wouldn't justify the complexity given the SyncSegment
> deserialization and seeking restrictions in the compressed and encrypted
> cases as mentioned
[jira] [Commented] (CASSANDRA-12137) dtest failure in sstable_generation_loading_test.TestSSTableGenerationAndLoading.sstableloader_compression_deflate_to_snappy_test
[
https://issues.apache.org/jira/browse/CASSANDRA-12137?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15503899#comment-15503899
]
Jim Witschey commented on CASSANDRA-12137:
--
Thanks for the bump. The build failed trying to {{tar}} up artifacts. I'll try
again x80, here:
http://cassci.datastax.com/view/Parameterized/job/parameterized_dtest_multiplexer/319/
If that fails too I'll be properly suspicious.
> dtest failure in
> sstable_generation_loading_test.TestSSTableGenerationAndLoading.sstableloader_compression_deflate_to_snappy_test
> -
>
> Key: CASSANDRA-12137
> URL: https://issues.apache.org/jira/browse/CASSANDRA-12137
> Project: Cassandra
> Issue Type: Test
>Reporter: Sean McCarthy
>Assignee: Jim Witschey
> Labels: dtest
>
> example failure:
> http://cassci.datastax.com/job/cassandra-3.0_dtest/764/testReport/sstable_generation_loading_test/TestSSTableGenerationAndLoading/sstableloader_compression_deflate_to_snappy_test
> {code}
> Stacktrace
> File "/usr/lib/python2.7/unittest/case.py", line 329, in run
> testMethod()
> File "/home/automaton/cassandra-dtest/sstable_generation_loading_test.py",
> line 75, in sstableloader_compression_deflate_to_snappy_test
> self.load_sstable_with_configuration('Deflate', 'Snappy')
> File "/home/automaton/cassandra-dtest/sstable_generation_loading_test.py",
> line 178, in load_sstable_with_configuration
> "sstableloader exited with a non-zero status: {}".format(exit_status))
> File "/usr/lib/python2.7/unittest/case.py", line 513, in assertEqual
> assertion_func(first, second, msg=msg)
> File "/usr/lib/python2.7/unittest/case.py", line 506, in _baseAssertEqual
> raise self.failureException(msg)
> "sstableloader exited with a non-zero status: 1
> {code}
> Related failures:
> http://cassci.datastax.com/job/cassandra-3.0_dtest/764/testReport/sstable_generation_loading_test/TestSSTableGenerationAndLoading/sstableloader_compression_none_to_snappy_test/
> http://cassci.datastax.com/job/cassandra-3.0_dtest/764/testReport/sstable_generation_loading_test/TestSSTableGenerationAndLoading/sstableloader_with_mv_test/
> Failed on CassCI build cassandra-3.0_dtest #764
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (CASSANDRA-12656) dtest failure in replace_address_test.TestReplaceAddress.restart_failed_replace_test
[
https://issues.apache.org/jira/browse/CASSANDRA-12656?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15497292#comment-15497292
]
Jim Witschey commented on CASSANDRA-12656:
--
I have not followed up with CI results, but the code change is correct.
> dtest failure in
> replace_address_test.TestReplaceAddress.restart_failed_replace_test
>
>
> Key: CASSANDRA-12656
> URL: https://issues.apache.org/jira/browse/CASSANDRA-12656
> Project: Cassandra
> Issue Type: Test
>Reporter: Sean McCarthy
>Assignee: Jim Witschey
> Labels: dtest
>
> example failure:
> http://cassci.datastax.com/job/cassandra-3.0_large_dtest/27/testReport/replace_address_test/TestReplaceAddress/restart_failed_replace_test
> {code}
> Stacktrace
> File "/usr/lib/python2.7/unittest/case.py", line 329, in run
> testMethod()
> File "/home/automaton/cassandra-dtest/tools/decorators.py", line 46, in
> wrapped
> f(obj)
> File "/home/automaton/cassandra-dtest/replace_address_test.py", line 460,
> in restart_failed_replace_test
> self._test_restart_failed_replace(mode='wipe')
> File "/home/automaton/cassandra-dtest/replace_address_test.py", line 463,
> in _test_restart_failed_replace
> self.ignore_log_patterns.append(r'Error while waiting on bootstrap to
> complete')
> "'tuple' object has no attribute 'append'
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (CASSANDRA-11248) (windows) dtest failure in commitlog_test.TestCommitLog.stop_failure_policy_test and stop_commit_failure_policy_test
[
https://issues.apache.org/jira/browse/CASSANDRA-11248?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15485094#comment-15485094
]
Jim Witschey commented on CASSANDRA-11248:
--
[~Purple] Great, thank you for the clarification.
> (windows) dtest failure in
> commitlog_test.TestCommitLog.stop_failure_policy_test and
> stop_commit_failure_policy_test
>
>
> Key: CASSANDRA-11248
> URL: https://issues.apache.org/jira/browse/CASSANDRA-11248
> Project: Cassandra
> Issue Type: Test
>Reporter: Russ Hatch
>Assignee: DS Test Eng
> Labels: dtest, windows
>
> example failure:
> http://cassci.datastax.com/job/cassandra-2.2_dtest_win32/167/testReport/commitlog_test/TestCommitLog/stop_failure_policy_test
> Failed on CassCI build cassandra-2.2_dtest_win32 #167
> failing intermittently, looks possibly related to CASSANDRA-11242 with:
> {noformat}
> Cannot find the commitlog failure message in logs
> {noformat}
> But there's another suspect message here not present on 11242, which is
> {noformat}
> [node1 ERROR] Java HotSpot(TM) 64-Bit Server VM warning: Cannot open file
> D:\jenkins\workspace\cassandra-2.2_dtest_win32\cassandra\/logs/gc.log due to
> No such file or directory
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (CASSANDRA-11248) (windows) dtest failure in commitlog_test.TestCommitLog.stop_failure_policy_test and stop_commit_failure_policy_test
[
https://issues.apache.org/jira/browse/CASSANDRA-11248?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15484981#comment-15484981
]
Jim Witschey commented on CASSANDRA-11248:
--
[~Purple] Thanks for your input. Could you describe your issue in more detail?
Are you missing log messages with certain failure policies, or missing `gc.log`?
> (windows) dtest failure in
> commitlog_test.TestCommitLog.stop_failure_policy_test and
> stop_commit_failure_policy_test
>
>
> Key: CASSANDRA-11248
> URL: https://issues.apache.org/jira/browse/CASSANDRA-11248
> Project: Cassandra
> Issue Type: Test
>Reporter: Russ Hatch
>Assignee: DS Test Eng
> Labels: dtest, windows
>
> example failure:
> http://cassci.datastax.com/job/cassandra-2.2_dtest_win32/167/testReport/commitlog_test/TestCommitLog/stop_failure_policy_test
> Failed on CassCI build cassandra-2.2_dtest_win32 #167
> failing intermittently, looks possibly related to CASSANDRA-11242 with:
> {noformat}
> Cannot find the commitlog failure message in logs
> {noformat}
> But there's another suspect message here not present on 11242, which is
> {noformat}
> [node1 ERROR] Java HotSpot(TM) 64-Bit Server VM warning: Cannot open file
> D:\jenkins\workspace\cassandra-2.2_dtest_win32\cassandra\/logs/gc.log due to
> No such file or directory
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (CASSANDRA-12364) dtest failure in upgrade_tests.paging_test.TestPagingDatasetChangesNodes3RF3_Upgrade_current_3_x_To_indev_3_x.test_cell_TTL_expiry_during_paging
[
https://issues.apache.org/jira/browse/CASSANDRA-12364?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15484853#comment-15484853
]
Jim Witschey commented on CASSANDRA-12364:
--
[~slebresne] Is it safe in the general case to ignore
{{RejectedExecutionException}}s in the logs, or do we need to make sure it only
happens at certain points during test execution, or that it happens only with
certain messages?
> dtest failure in
> upgrade_tests.paging_test.TestPagingDatasetChangesNodes3RF3_Upgrade_current_3_x_To_indev_3_x.test_cell_TTL_expiry_during_paging
>
>
> Key: CASSANDRA-12364
> URL: https://issues.apache.org/jira/browse/CASSANDRA-12364
> Project: Cassandra
> Issue Type: Test
>Reporter: Sean McCarthy
>Assignee: Russ Hatch
> 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/trunk_dtest_upgrade/10/testReport/upgrade_tests.paging_test/TestPagingDatasetChangesNodes3RF3_Upgrade_current_3_x_To_indev_3_x/test_cell_TTL_expiry_during_paging
> {code}
> Error Message
> Unexpected error in log, see stdout
> {code}
> {code}
> Standard Output
> http://git-wip-us.apache.org/repos/asf/cassandra.git
> git:5051c0f6eb3f984600600c9577d6b5ece9038c74
> Unexpected error in node1 log, error:
> ERROR [InternalResponseStage:4] 2016-07-28 03:23:02,097
> CassandraDaemon.java:217 - Exception in thread
> Thread[InternalResponseStage:4,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
> org.apache.cassandra.db.ColumnFamilyStore.waitForFlushes(ColumnFamilyStore.java:930)
> ~[apache-cassandra-3.7.jar:3.7]
> at
> org.apache.cassandra.db.ColumnFamilyStore.forceFlush(ColumnFamilyStore.java:892)
> ~[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/2113926365.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}
> Related failures:
> http://cassci.datastax.com/job/trunk_dtest_upgrade/11/testReport/upgrade_tests.paging_test/TestPagingWithDeletionsNodes3RF3_Upgrade_current_3_x_To_indev_3_x/test_ttl_deletions/
> http://cassci.datastax.com/job/trunk_dtest_upgrade/12/testReport/upgrade_tests.cql_tests/TestCQLNodes3RF3_Upgrade_current_3_x_To_indev_3_x/static_columns_with_distinct_test/
> http://cassci.datastax.com/job/trunk_dtest_upgrade/12/testReport/upgrade_tests.cql_tests/TestCQLNodes3RF3_Upgrade_current_3_x_To_indev_3_x/refuse_in_with_indexes_test/
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Resolved] (CASSANDRA-12340) dtest failure in upgrade_supercolumns_test.TestSCUpgrade.upgrade_with_counters_test
[
https://issues.apache.org/jira/browse/CASSANDRA-12340?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jim Witschey resolved CASSANDRA-12340.
--
Resolution: Fixed
Thanks, closing
> dtest failure in
> upgrade_supercolumns_test.TestSCUpgrade.upgrade_with_counters_test
> ---
>
> Key: CASSANDRA-12340
> URL: https://issues.apache.org/jira/browse/CASSANDRA-12340
> Project: Cassandra
> Issue Type: Test
>Reporter: Sean McCarthy
>Assignee: Jim Witschey
> Labels: dtest
> Attachments: node1.log, node2.log, node3.log
>
>
> example failure:
> http://cassci.datastax.com/job/cassandra-2.1_dtest_jdk8/249/testReport/upgrade_supercolumns_test/TestSCUpgrade/upgrade_with_counters_test
> {code}
> Standard Output
> Unexpected error in node3 log, error:
> ERROR [CompactionExecutor:1] 2016-07-28 15:34:19,533 CassandraDaemon.java
> (line 191) Exception in thread Thread[CompactionExecutor:1,1,main]
> java.util.concurrent.RejectedExecutionException: Task
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask@5fb8b2bf
> rejected from
> org.apache.cassandra.concurrent.DebuggableScheduledThreadPoolExecutor@1ae851ad[Terminated,
> pool size = 0, active threads = 0, queued tasks = 0, completed tasks = 8]
> at
> java.util.concurrent.ThreadPoolExecutor$AbortPolicy.rejectedExecution(ThreadPoolExecutor.java:2047)
> at
> java.util.concurrent.ThreadPoolExecutor.reject(ThreadPoolExecutor.java:823)
> at
> java.util.concurrent.ScheduledThreadPoolExecutor.delayedExecute(ScheduledThreadPoolExecutor.java:326)
> at
> java.util.concurrent.ScheduledThreadPoolExecutor.schedule(ScheduledThreadPoolExecutor.java:533)
> at
> java.util.concurrent.ScheduledThreadPoolExecutor.submit(ScheduledThreadPoolExecutor.java:632)
> at
> org.apache.cassandra.io.sstable.SSTableDeletingTask.schedule(SSTableDeletingTask.java:65)
> at
> org.apache.cassandra.io.sstable.SSTableReader.releaseReference(SSTableReader.java:976)
> at
> org.apache.cassandra.db.DataTracker.removeOldSSTablesSize(DataTracker.java:383)
> at org.apache.cassandra.db.DataTracker.postReplace(DataTracker.java:348)
> at org.apache.cassandra.db.DataTracker.replace(DataTracker.java:342)
> at
> org.apache.cassandra.db.DataTracker.replaceCompactedSSTables(DataTracker.java:245)
> at
> org.apache.cassandra.db.ColumnFamilyStore.replaceCompactedSSTables(ColumnFamilyStore.java:995)
> at
> org.apache.cassandra.db.compaction.CompactionTask.replaceCompactedSSTables(CompactionTask.java:270)
> at
> org.apache.cassandra.db.compaction.CompactionTask.runWith(CompactionTask.java:230)
> at
> org.apache.cassandra.io.util.DiskAwareRunnable.runMayThrow(DiskAwareRunnable.java:48)
> at
> org.apache.cassandra.utils.WrappedRunnable.run(WrappedRunnable.java:28)
> at
> org.apache.cassandra.db.compaction.CompactionTask.executeInternal(CompactionTask.java:58)
> at
> org.apache.cassandra.db.compaction.AbstractCompactionTask.execute(AbstractCompactionTask.java:60)
> at
> org.apache.cassandra.db.compaction.CompactionManager$BackgroundCompactionTask.run(CompactionManager.java:208)
> at
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:745)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (CASSANDRA-12340) dtest failure in upgrade_supercolumns_test.TestSCUpgrade.upgrade_with_counters_test
[
https://issues.apache.org/jira/browse/CASSANDRA-12340?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15452523#comment-15452523
]
Jim Witschey commented on CASSANDRA-12340:
--
dtest PR merged. Running x100 here:
http://cassci.datastax.com/view/Parameterized/job/parameterized_dtest_multiplexer/295/
If that runs clean, are we good to close this [~jkni]?
> dtest failure in
> upgrade_supercolumns_test.TestSCUpgrade.upgrade_with_counters_test
> ---
>
> Key: CASSANDRA-12340
> URL: https://issues.apache.org/jira/browse/CASSANDRA-12340
> Project: Cassandra
> Issue Type: Test
>Reporter: Sean McCarthy
>Assignee: Jim Witschey
> Labels: dtest
> Attachments: node1.log, node2.log, node3.log
>
>
> example failure:
> http://cassci.datastax.com/job/cassandra-2.1_dtest_jdk8/249/testReport/upgrade_supercolumns_test/TestSCUpgrade/upgrade_with_counters_test
> {code}
> Standard Output
> Unexpected error in node3 log, error:
> ERROR [CompactionExecutor:1] 2016-07-28 15:34:19,533 CassandraDaemon.java
> (line 191) Exception in thread Thread[CompactionExecutor:1,1,main]
> java.util.concurrent.RejectedExecutionException: Task
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask@5fb8b2bf
> rejected from
> org.apache.cassandra.concurrent.DebuggableScheduledThreadPoolExecutor@1ae851ad[Terminated,
> pool size = 0, active threads = 0, queued tasks = 0, completed tasks = 8]
> at
> java.util.concurrent.ThreadPoolExecutor$AbortPolicy.rejectedExecution(ThreadPoolExecutor.java:2047)
> at
> java.util.concurrent.ThreadPoolExecutor.reject(ThreadPoolExecutor.java:823)
> at
> java.util.concurrent.ScheduledThreadPoolExecutor.delayedExecute(ScheduledThreadPoolExecutor.java:326)
> at
> java.util.concurrent.ScheduledThreadPoolExecutor.schedule(ScheduledThreadPoolExecutor.java:533)
> at
> java.util.concurrent.ScheduledThreadPoolExecutor.submit(ScheduledThreadPoolExecutor.java:632)
> at
> org.apache.cassandra.io.sstable.SSTableDeletingTask.schedule(SSTableDeletingTask.java:65)
> at
> org.apache.cassandra.io.sstable.SSTableReader.releaseReference(SSTableReader.java:976)
> at
> org.apache.cassandra.db.DataTracker.removeOldSSTablesSize(DataTracker.java:383)
> at org.apache.cassandra.db.DataTracker.postReplace(DataTracker.java:348)
> at org.apache.cassandra.db.DataTracker.replace(DataTracker.java:342)
> at
> org.apache.cassandra.db.DataTracker.replaceCompactedSSTables(DataTracker.java:245)
> at
> org.apache.cassandra.db.ColumnFamilyStore.replaceCompactedSSTables(ColumnFamilyStore.java:995)
> at
> org.apache.cassandra.db.compaction.CompactionTask.replaceCompactedSSTables(CompactionTask.java:270)
> at
> org.apache.cassandra.db.compaction.CompactionTask.runWith(CompactionTask.java:230)
> at
> org.apache.cassandra.io.util.DiskAwareRunnable.runMayThrow(DiskAwareRunnable.java:48)
> at
> org.apache.cassandra.utils.WrappedRunnable.run(WrappedRunnable.java:28)
> at
> org.apache.cassandra.db.compaction.CompactionTask.executeInternal(CompactionTask.java:58)
> at
> org.apache.cassandra.db.compaction.AbstractCompactionTask.execute(AbstractCompactionTask.java:60)
> at
> org.apache.cassandra.db.compaction.CompactionManager$BackgroundCompactionTask.run(CompactionManager.java:208)
> at
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:745)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (CASSANDRA-12456) dtest failure in auth_test.TestAuth.system_auth_ks_is_alterable_test
[
https://issues.apache.org/jira/browse/CASSANDRA-12456?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15452406#comment-15452406
]
Jim Witschey commented on CASSANDRA-12456:
--
dtest PR:
https://github.com/riptano/cassandra-dtest/pull/1254
> dtest failure in auth_test.TestAuth.system_auth_ks_is_alterable_test
>
>
> Key: CASSANDRA-12456
> URL: https://issues.apache.org/jira/browse/CASSANDRA-12456
> Project: Cassandra
> Issue Type: Test
>Reporter: Craig Kodman
>Assignee: Jim Witschey
> Labels: dtest
> Attachments: node1.log, node1_debug.log, node1_gc.log, node2.log,
> node2_debug.log, node2_gc.log, node3.log, node3_debug.log, node3_gc.log
>
>
> example failure:
> http://cassci.datastax.com/job/cassandra-2.2_dtest/675/testReport/auth_test/TestAuth/system_auth_ks_is_alterable_test
> {code}
> Stacktrace
> File "/usr/lib/python2.7/unittest/case.py", line 329, in run
> testMethod()
> File "/home/automaton/cassandra-dtest/auth_test.py", line 49, in
> system_auth_ks_is_alterable_test
> session.cluster.refresh_schema_metadata()
> File "cassandra/cluster.py", line 1606, in
> cassandra.cluster.Cluster.refresh_schema_metadata (cassandra/cluster.c:29510)
> raise DriverException("Schema metadata was not refreshed. See log for
> details.")
> "Schema metadata was not refreshed. See log for
> details.\n >> begin captured logging <<
> \ndtest: DEBUG: cluster ccm directory:
> /tmp/dtest-vDljld\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}\ndtest: DEBUG: Default role created by node1\ndtest: DEBUG: nodes
> started\n- >> end captured logging <<
> -"
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (CASSANDRA-12137) dtest failure in sstable_generation_loading_test.TestSSTableGenerationAndLoading.sstableloader_compression_deflate_to_snappy_test
[
https://issues.apache.org/jira/browse/CASSANDRA-12137?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15452373#comment-15452373
]
Jim Witschey commented on CASSANDRA-12137:
--
Running x200 here:
http://cassci.datastax.com/view/Parameterized/job/parameterized_dtest_multiplexer/293/
> dtest failure in
> sstable_generation_loading_test.TestSSTableGenerationAndLoading.sstableloader_compression_deflate_to_snappy_test
> -
>
> Key: CASSANDRA-12137
> URL: https://issues.apache.org/jira/browse/CASSANDRA-12137
> Project: Cassandra
> Issue Type: Test
>Reporter: Sean McCarthy
>Assignee: Jim Witschey
> Labels: dtest
>
> example failure:
> http://cassci.datastax.com/job/cassandra-3.0_dtest/764/testReport/sstable_generation_loading_test/TestSSTableGenerationAndLoading/sstableloader_compression_deflate_to_snappy_test
> {code}
> Stacktrace
> File "/usr/lib/python2.7/unittest/case.py", line 329, in run
> testMethod()
> File "/home/automaton/cassandra-dtest/sstable_generation_loading_test.py",
> line 75, in sstableloader_compression_deflate_to_snappy_test
> self.load_sstable_with_configuration('Deflate', 'Snappy')
> File "/home/automaton/cassandra-dtest/sstable_generation_loading_test.py",
> line 178, in load_sstable_with_configuration
> "sstableloader exited with a non-zero status: {}".format(exit_status))
> File "/usr/lib/python2.7/unittest/case.py", line 513, in assertEqual
> assertion_func(first, second, msg=msg)
> File "/usr/lib/python2.7/unittest/case.py", line 506, in _baseAssertEqual
> raise self.failureException(msg)
> "sstableloader exited with a non-zero status: 1
> {code}
> Related failures:
> http://cassci.datastax.com/job/cassandra-3.0_dtest/764/testReport/sstable_generation_loading_test/TestSSTableGenerationAndLoading/sstableloader_compression_none_to_snappy_test/
> http://cassci.datastax.com/job/cassandra-3.0_dtest/764/testReport/sstable_generation_loading_test/TestSSTableGenerationAndLoading/sstableloader_with_mv_test/
> Failed on CassCI build cassandra-3.0_dtest #764
--
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=15452349#comment-15452349
]
Jim Witschey commented on CASSANDRA-12092:
--
Merged the PR, thanks [~Stefania] -- are we good to close this ticket?
> 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-12488) dtest failure in upgrade_tests.cql_tests.TestCQLNodes3RF3_Upgrade_current_3_0_x_To_indev_3_x.cql3_non_compound_range_tombstones_test
[ https://issues.apache.org/jira/browse/CASSANDRA-12488?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jim Witschey updated CASSANDRA-12488: - Description: example failure: http://cassci.datastax.com/job/cassandra-3.9_dtest_upgrade/25/testReport/upgrade_tests.cql_tests/TestCQLNodes3RF3_Upgrade_current_3_0_x_To_indev_3_x/cql3_non_compound_range_tombstones_test/ It looks like this is failing with a TimedOutException. was: example failure: http://cassci.datastax.com/job/cassandra-3.9_dtest_upgrade/lastCompletedBuild/testReport/upgrade_tests.cql_tests/TestCQLNodes3RF3_Upgrade_current_3_0_x_To_indev_3_x/cql3_non_compound_range_tombstones_test It looks like this is failing with a TimedOutException. > dtest failure in > upgrade_tests.cql_tests.TestCQLNodes3RF3_Upgrade_current_3_0_x_To_indev_3_x.cql3_non_compound_range_tombstones_test > > > Key: CASSANDRA-12488 > URL: https://issues.apache.org/jira/browse/CASSANDRA-12488 > Project: Cassandra > Issue Type: Test > Components: Testing >Reporter: Joel Knighton >Assignee: DS Test Eng > Labels: dtest > > example failure: > http://cassci.datastax.com/job/cassandra-3.9_dtest_upgrade/25/testReport/upgrade_tests.cql_tests/TestCQLNodes3RF3_Upgrade_current_3_0_x_To_indev_3_x/cql3_non_compound_range_tombstones_test/ > It looks like this is failing with a TimedOutException. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CASSANDRA-12137) dtest failure in sstable_generation_loading_test.TestSSTableGenerationAndLoading.sstableloader_compression_deflate_to_snappy_test
[
https://issues.apache.org/jira/browse/CASSANDRA-12137?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jim Witschey updated CASSANDRA-12137:
-
Status: In Progress (was: Patch Available)
> dtest failure in
> sstable_generation_loading_test.TestSSTableGenerationAndLoading.sstableloader_compression_deflate_to_snappy_test
> -
>
> Key: CASSANDRA-12137
> URL: https://issues.apache.org/jira/browse/CASSANDRA-12137
> Project: Cassandra
> Issue Type: Test
>Reporter: Sean McCarthy
>Assignee: Jim Witschey
> Labels: dtest
>
> example failure:
> http://cassci.datastax.com/job/cassandra-3.0_dtest/764/testReport/sstable_generation_loading_test/TestSSTableGenerationAndLoading/sstableloader_compression_deflate_to_snappy_test
> {code}
> Stacktrace
> File "/usr/lib/python2.7/unittest/case.py", line 329, in run
> testMethod()
> File "/home/automaton/cassandra-dtest/sstable_generation_loading_test.py",
> line 75, in sstableloader_compression_deflate_to_snappy_test
> self.load_sstable_with_configuration('Deflate', 'Snappy')
> File "/home/automaton/cassandra-dtest/sstable_generation_loading_test.py",
> line 178, in load_sstable_with_configuration
> "sstableloader exited with a non-zero status: {}".format(exit_status))
> File "/usr/lib/python2.7/unittest/case.py", line 513, in assertEqual
> assertion_func(first, second, msg=msg)
> File "/usr/lib/python2.7/unittest/case.py", line 506, in _baseAssertEqual
> raise self.failureException(msg)
> "sstableloader exited with a non-zero status: 1
> {code}
> Related failures:
> http://cassci.datastax.com/job/cassandra-3.0_dtest/764/testReport/sstable_generation_loading_test/TestSSTableGenerationAndLoading/sstableloader_compression_none_to_snappy_test/
> http://cassci.datastax.com/job/cassandra-3.0_dtest/764/testReport/sstable_generation_loading_test/TestSSTableGenerationAndLoading/sstableloader_with_mv_test/
> Failed on CassCI build cassandra-3.0_dtest #764
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (CASSANDRA-12137) dtest failure in sstable_generation_loading_test.TestSSTableGenerationAndLoading.sstableloader_compression_deflate_to_snappy_test
[
https://issues.apache.org/jira/browse/CASSANDRA-12137?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15422867#comment-15422867
]
Jim Witschey commented on CASSANDRA-12137:
--
PR merged after a successful run on CassCI. Running here now with the new dtest
changes:
http://cassci.datastax.com/view/Parameterized/job/parameterized_dtest_multiplexer/252/
> dtest failure in
> sstable_generation_loading_test.TestSSTableGenerationAndLoading.sstableloader_compression_deflate_to_snappy_test
> -
>
> Key: CASSANDRA-12137
> URL: https://issues.apache.org/jira/browse/CASSANDRA-12137
> Project: Cassandra
> Issue Type: Test
>Reporter: Sean McCarthy
>Assignee: Jim Witschey
> Labels: dtest
>
> example failure:
> http://cassci.datastax.com/job/cassandra-3.0_dtest/764/testReport/sstable_generation_loading_test/TestSSTableGenerationAndLoading/sstableloader_compression_deflate_to_snappy_test
> {code}
> Stacktrace
> File "/usr/lib/python2.7/unittest/case.py", line 329, in run
> testMethod()
> File "/home/automaton/cassandra-dtest/sstable_generation_loading_test.py",
> line 75, in sstableloader_compression_deflate_to_snappy_test
> self.load_sstable_with_configuration('Deflate', 'Snappy')
> File "/home/automaton/cassandra-dtest/sstable_generation_loading_test.py",
> line 178, in load_sstable_with_configuration
> "sstableloader exited with a non-zero status: {}".format(exit_status))
> File "/usr/lib/python2.7/unittest/case.py", line 513, in assertEqual
> assertion_func(first, second, msg=msg)
> File "/usr/lib/python2.7/unittest/case.py", line 506, in _baseAssertEqual
> raise self.failureException(msg)
> "sstableloader exited with a non-zero status: 1
> {code}
> Related failures:
> http://cassci.datastax.com/job/cassandra-3.0_dtest/764/testReport/sstable_generation_loading_test/TestSSTableGenerationAndLoading/sstableloader_compression_none_to_snappy_test/
> http://cassci.datastax.com/job/cassandra-3.0_dtest/764/testReport/sstable_generation_loading_test/TestSSTableGenerationAndLoading/sstableloader_with_mv_test/
> Failed on CassCI build cassandra-3.0_dtest #764
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (CASSANDRA-12456) dtest failure in auth_test.TestAuth.system_auth_ks_is_alterable_test
[
https://issues.apache.org/jira/browse/CASSANDRA-12456?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15421629#comment-15421629
]
Jim Witschey commented on CASSANDRA-12456:
--
I'm going to bump up the timeout on the schema refresh as a first attempt at
addressing this. There's an opportunity to test and refactor some of our
utility classes in dtest, so I'm taking that opportunity now.
> dtest failure in auth_test.TestAuth.system_auth_ks_is_alterable_test
>
>
> Key: CASSANDRA-12456
> URL: https://issues.apache.org/jira/browse/CASSANDRA-12456
> Project: Cassandra
> Issue Type: Test
>Reporter: Craig Kodman
>Assignee: Jim Witschey
> Labels: dtest
> Attachments: node1.log, node1_debug.log, node1_gc.log, node2.log,
> node2_debug.log, node2_gc.log, node3.log, node3_debug.log, node3_gc.log
>
>
> example failure:
> http://cassci.datastax.com/job/cassandra-2.2_dtest/675/testReport/auth_test/TestAuth/system_auth_ks_is_alterable_test
> {code}
> Stacktrace
> File "/usr/lib/python2.7/unittest/case.py", line 329, in run
> testMethod()
> File "/home/automaton/cassandra-dtest/auth_test.py", line 49, in
> system_auth_ks_is_alterable_test
> session.cluster.refresh_schema_metadata()
> File "cassandra/cluster.py", line 1606, in
> cassandra.cluster.Cluster.refresh_schema_metadata (cassandra/cluster.c:29510)
> raise DriverException("Schema metadata was not refreshed. See log for
> details.")
> "Schema metadata was not refreshed. See log for
> details.\n >> begin captured logging <<
> \ndtest: DEBUG: cluster ccm directory:
> /tmp/dtest-vDljld\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}\ndtest: DEBUG: Default role created by node1\ndtest: DEBUG: nodes
> started\n- >> end captured logging <<
> -"
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (CASSANDRA-12137) dtest failure in sstable_generation_loading_test.TestSSTableGenerationAndLoading.sstableloader_compression_deflate_to_snappy_test
[
https://issues.apache.org/jira/browse/CASSANDRA-12137?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jim Witschey updated CASSANDRA-12137:
-
Status: Patch Available (was: In Progress)
> dtest failure in
> sstable_generation_loading_test.TestSSTableGenerationAndLoading.sstableloader_compression_deflate_to_snappy_test
> -
>
> Key: CASSANDRA-12137
> URL: https://issues.apache.org/jira/browse/CASSANDRA-12137
> Project: Cassandra
> Issue Type: Test
>Reporter: Sean McCarthy
>Assignee: Jim Witschey
> Labels: dtest
>
> example failure:
> http://cassci.datastax.com/job/cassandra-3.0_dtest/764/testReport/sstable_generation_loading_test/TestSSTableGenerationAndLoading/sstableloader_compression_deflate_to_snappy_test
> {code}
> Stacktrace
> File "/usr/lib/python2.7/unittest/case.py", line 329, in run
> testMethod()
> File "/home/automaton/cassandra-dtest/sstable_generation_loading_test.py",
> line 75, in sstableloader_compression_deflate_to_snappy_test
> self.load_sstable_with_configuration('Deflate', 'Snappy')
> File "/home/automaton/cassandra-dtest/sstable_generation_loading_test.py",
> line 178, in load_sstable_with_configuration
> "sstableloader exited with a non-zero status: {}".format(exit_status))
> File "/usr/lib/python2.7/unittest/case.py", line 513, in assertEqual
> assertion_func(first, second, msg=msg)
> File "/usr/lib/python2.7/unittest/case.py", line 506, in _baseAssertEqual
> raise self.failureException(msg)
> "sstableloader exited with a non-zero status: 1
> {code}
> Related failures:
> http://cassci.datastax.com/job/cassandra-3.0_dtest/764/testReport/sstable_generation_loading_test/TestSSTableGenerationAndLoading/sstableloader_compression_none_to_snappy_test/
> http://cassci.datastax.com/job/cassandra-3.0_dtest/764/testReport/sstable_generation_loading_test/TestSSTableGenerationAndLoading/sstableloader_with_mv_test/
> Failed on CassCI build cassandra-3.0_dtest #764
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (CASSANDRA-12415) dtest failure in replace_address_test.TestReplaceAddress.replace_stopped_node_test
[ https://issues.apache.org/jira/browse/CASSANDRA-12415?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jim Witschey updated CASSANDRA-12415: - Resolution: Fixed Status: Resolved (was: Patch Available) > dtest failure in > replace_address_test.TestReplaceAddress.replace_stopped_node_test > -- > > Key: CASSANDRA-12415 > URL: https://issues.apache.org/jira/browse/CASSANDRA-12415 > Project: Cassandra > Issue Type: Test >Reporter: Philip Thompson >Assignee: Jim Witschey > Labels: blocked, dtest > > example failure: > http://cassci.datastax.com/job/cassandra-3.9_dtest/31/testReport/replace_address_test/TestReplaceAddress/replace_stopped_node_test > Node4 just doesn't start up in time. Maybe bump up the timeout, or move to > large test? -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CASSANDRA-12415) dtest failure in replace_address_test.TestReplaceAddress.replace_stopped_node_test
[ https://issues.apache.org/jira/browse/CASSANDRA-12415?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15421517#comment-15421517 ] Jim Witschey commented on CASSANDRA-12415: -- Merged, closing. > dtest failure in > replace_address_test.TestReplaceAddress.replace_stopped_node_test > -- > > Key: CASSANDRA-12415 > URL: https://issues.apache.org/jira/browse/CASSANDRA-12415 > Project: Cassandra > Issue Type: Test >Reporter: Philip Thompson >Assignee: Jim Witschey > Labels: blocked, dtest > > example failure: > http://cassci.datastax.com/job/cassandra-3.9_dtest/31/testReport/replace_address_test/TestReplaceAddress/replace_stopped_node_test > Node4 just doesn't start up in time. Maybe bump up the timeout, or move to > large test? -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CASSANDRA-12415) dtest failure in replace_address_test.TestReplaceAddress.replace_stopped_node_test
[ https://issues.apache.org/jira/browse/CASSANDRA-12415?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15421488#comment-15421488 ] Jim Witschey commented on CASSANDRA-12415: -- Filed [this dtest PR|https://github.com/riptano/cassandra-dtest/pull/1238], which addresses the issue without dependencies: bq. This should have all the tests that I tagged as resource-intensive in #1212 run only on large instances. My mistake for thinking that actually skipping those should be blocked on other work. > dtest failure in > replace_address_test.TestReplaceAddress.replace_stopped_node_test > -- > > Key: CASSANDRA-12415 > URL: https://issues.apache.org/jira/browse/CASSANDRA-12415 > Project: Cassandra > Issue Type: Test >Reporter: Philip Thompson >Assignee: Jim Witschey > Labels: blocked, dtest > > example failure: > http://cassci.datastax.com/job/cassandra-3.9_dtest/31/testReport/replace_address_test/TestReplaceAddress/replace_stopped_node_test > Node4 just doesn't start up in time. Maybe bump up the timeout, or move to > large test? -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CASSANDRA-12415) dtest failure in replace_address_test.TestReplaceAddress.replace_stopped_node_test
[ https://issues.apache.org/jira/browse/CASSANDRA-12415?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jim Witschey updated CASSANDRA-12415: - Labels: blocked dtest (was: dtest) > dtest failure in > replace_address_test.TestReplaceAddress.replace_stopped_node_test > -- > > Key: CASSANDRA-12415 > URL: https://issues.apache.org/jira/browse/CASSANDRA-12415 > Project: Cassandra > Issue Type: Test >Reporter: Philip Thompson >Assignee: Jim Witschey > Labels: blocked, dtest > > example failure: > http://cassci.datastax.com/job/cassandra-3.9_dtest/31/testReport/replace_address_test/TestReplaceAddress/replace_stopped_node_test > Node4 just doesn't start up in time. Maybe bump up the timeout, or move to > large test? -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (CASSANDRA-12456) dtest failure in auth_test.TestAuth.system_auth_ks_is_alterable_test
[
https://issues.apache.org/jira/browse/CASSANDRA-12456?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jim Witschey reassigned CASSANDRA-12456:
Assignee: Jim Witschey (was: DS Test Eng)
> dtest failure in auth_test.TestAuth.system_auth_ks_is_alterable_test
>
>
> Key: CASSANDRA-12456
> URL: https://issues.apache.org/jira/browse/CASSANDRA-12456
> Project: Cassandra
> Issue Type: Test
>Reporter: Craig Kodman
>Assignee: Jim Witschey
> Labels: dtest
> Attachments: node1.log, node1_debug.log, node1_gc.log, node2.log,
> node2_debug.log, node2_gc.log, node3.log, node3_debug.log, node3_gc.log
>
>
> example failure:
> http://cassci.datastax.com/job/cassandra-2.2_dtest/675/testReport/auth_test/TestAuth/system_auth_ks_is_alterable_test
> {code}
> Stacktrace
> File "/usr/lib/python2.7/unittest/case.py", line 329, in run
> testMethod()
> File "/home/automaton/cassandra-dtest/auth_test.py", line 49, in
> system_auth_ks_is_alterable_test
> session.cluster.refresh_schema_metadata()
> File "cassandra/cluster.py", line 1606, in
> cassandra.cluster.Cluster.refresh_schema_metadata (cassandra/cluster.c:29510)
> raise DriverException("Schema metadata was not refreshed. See log for
> details.")
> "Schema metadata was not refreshed. See log for
> details.\n >> begin captured logging <<
> \ndtest: DEBUG: cluster ccm directory:
> /tmp/dtest-vDljld\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}\ndtest: DEBUG: Default role created by node1\ndtest: DEBUG: nodes
> started\n- >> end captured logging <<
> -"
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (CASSANDRA-12415) dtest failure in replace_address_test.TestReplaceAddress.replace_stopped_node_test
[
https://issues.apache.org/jira/browse/CASSANDRA-12415?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15418973#comment-15418973
]
Jim Witschey commented on CASSANDRA-12415:
--
Merged "move to larger instances" ticket here:
https://github.com/riptano/cassandra-dtest/pull/1212
Actually running this test on larger instances will start when we use
{{attrib}} for test exclusion, which I believe [~sean.mccarthy] is working on.
> dtest failure in
> replace_address_test.TestReplaceAddress.replace_stopped_node_test
> --
>
> Key: CASSANDRA-12415
> URL: https://issues.apache.org/jira/browse/CASSANDRA-12415
> Project: Cassandra
> Issue Type: Test
>Reporter: Philip Thompson
>Assignee: Jim Witschey
> Labels: dtest
>
> example failure:
> http://cassci.datastax.com/job/cassandra-3.9_dtest/31/testReport/replace_address_test/TestReplaceAddress/replace_stopped_node_test
> Node4 just doesn't start up in time. Maybe bump up the timeout, or move to
> large test?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (CASSANDRA-12137) dtest failure in sstable_generation_loading_test.TestSSTableGenerationAndLoading.sstableloader_compression_deflate_to_snappy_test
[
https://issues.apache.org/jira/browse/CASSANDRA-12137?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15417398#comment-15417398
]
Jim Witschey commented on CASSANDRA-12137:
--
I've lost a lot of the context for this, but I've filed this PR to hopefully
get some debug output:
https://github.com/riptano/cassandra-dtest/pull/1221
The previous PR failed because of what I believe is a CCM bug, which we have in
our queue to investigate.
> dtest failure in
> sstable_generation_loading_test.TestSSTableGenerationAndLoading.sstableloader_compression_deflate_to_snappy_test
> -
>
> Key: CASSANDRA-12137
> URL: https://issues.apache.org/jira/browse/CASSANDRA-12137
> Project: Cassandra
> Issue Type: Test
>Reporter: Sean McCarthy
>Assignee: Jim Witschey
> Labels: dtest
>
> example failure:
> http://cassci.datastax.com/job/cassandra-3.0_dtest/764/testReport/sstable_generation_loading_test/TestSSTableGenerationAndLoading/sstableloader_compression_deflate_to_snappy_test
> {code}
> Stacktrace
> File "/usr/lib/python2.7/unittest/case.py", line 329, in run
> testMethod()
> File "/home/automaton/cassandra-dtest/sstable_generation_loading_test.py",
> line 75, in sstableloader_compression_deflate_to_snappy_test
> self.load_sstable_with_configuration('Deflate', 'Snappy')
> File "/home/automaton/cassandra-dtest/sstable_generation_loading_test.py",
> line 178, in load_sstable_with_configuration
> "sstableloader exited with a non-zero status: {}".format(exit_status))
> File "/usr/lib/python2.7/unittest/case.py", line 513, in assertEqual
> assertion_func(first, second, msg=msg)
> File "/usr/lib/python2.7/unittest/case.py", line 506, in _baseAssertEqual
> raise self.failureException(msg)
> "sstableloader exited with a non-zero status: 1
> {code}
> Related failures:
> http://cassci.datastax.com/job/cassandra-3.0_dtest/764/testReport/sstable_generation_loading_test/TestSSTableGenerationAndLoading/sstableloader_compression_none_to_snappy_test/
> http://cassci.datastax.com/job/cassandra-3.0_dtest/764/testReport/sstable_generation_loading_test/TestSSTableGenerationAndLoading/sstableloader_with_mv_test/
> Failed on CassCI build cassandra-3.0_dtest #764
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Comment Edited] (CASSANDRA-12415) dtest failure in replace_address_test.TestReplaceAddress.replace_stopped_node_test
[ https://issues.apache.org/jira/browse/CASSANDRA-12415?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15415434#comment-15415434 ] Jim Witschey edited comment on CASSANDRA-12415 at 8/10/16 3:17 PM: --- +1 to moving to larger instances. Filed https://github.com/riptano/cassandra-dtest/pull/1204 was (Author: mambocab): +1 to moving to larger instances. > dtest failure in > replace_address_test.TestReplaceAddress.replace_stopped_node_test > -- > > Key: CASSANDRA-12415 > URL: https://issues.apache.org/jira/browse/CASSANDRA-12415 > Project: Cassandra > Issue Type: Test >Reporter: Philip Thompson >Assignee: DS Test Eng > Labels: dtest > > example failure: > http://cassci.datastax.com/job/cassandra-3.9_dtest/31/testReport/replace_address_test/TestReplaceAddress/replace_stopped_node_test > Node4 just doesn't start up in time. Maybe bump up the timeout, or move to > large test? -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CASSANDRA-12415) dtest failure in replace_address_test.TestReplaceAddress.replace_stopped_node_test
[ https://issues.apache.org/jira/browse/CASSANDRA-12415?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15415434#comment-15415434 ] Jim Witschey commented on CASSANDRA-12415: -- +1 to moving to larger instances. > dtest failure in > replace_address_test.TestReplaceAddress.replace_stopped_node_test > -- > > Key: CASSANDRA-12415 > URL: https://issues.apache.org/jira/browse/CASSANDRA-12415 > Project: Cassandra > Issue Type: Test >Reporter: Philip Thompson >Assignee: DS Test Eng > Labels: dtest > > example failure: > http://cassci.datastax.com/job/cassandra-3.9_dtest/31/testReport/replace_address_test/TestReplaceAddress/replace_stopped_node_test > Node4 just doesn't start up in time. Maybe bump up the timeout, or move to > large test? -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CASSANDRA-12167) Review JMX metrics test coverage
[ https://issues.apache.org/jira/browse/CASSANDRA-12167?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15411981#comment-15411981 ] Jim Witschey commented on CASSANDRA-12167: -- Sounds right -- but, I think that the documentation on these was fleshed out much better, which could make it more doable for TE. Thoughts? > Review JMX metrics test coverage > > > Key: CASSANDRA-12167 > URL: https://issues.apache.org/jira/browse/CASSANDRA-12167 > Project: Cassandra > Issue Type: Test >Reporter: Jim Witschey >Assignee: DS Test Eng > Labels: dtest > > I just deleted the dtest that was meant to smoke test JMX metrics: > https://github.com/riptano/cassandra-dtest/pull/1085 > The idea was that you'd read JMX metrics, run stress, then make sure the > metrics went up, down, or stayed the same, as appropriate. This kind of > coverage would be good to have. > I don't think we have it anywhere in the dtests, and it probably isn't > appropriate in unit tests. We should check there's no coverage in the unit > tests, and add some coverage. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CASSANDRA-12176) dtest failure in materialized_views_test.TestMaterializedViews.complex_repair_test
[
https://issues.apache.org/jira/browse/CASSANDRA-12176?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15408264#comment-15408264
]
Jim Witschey commented on CASSANDRA-12176:
--
Filed [dtest PR 1171|https://github.com/riptano/cassandra-dtest/pull/1171] to
address the unrelated failures seen on the multiplexer job, Philip or Russ to
review.
Filed and merged [dtest PR
1174|https://github.com/riptano/cassandra-dtest/pull/1174] to have this run on
larger instances on CassCI. [~philipthompson], do you reckon that's sufficient
to close this ticket, or does that risk ignoring a real bug in C* or the test?
> dtest failure in
> materialized_views_test.TestMaterializedViews.complex_repair_test
> --
>
> Key: CASSANDRA-12176
> URL: https://issues.apache.org/jira/browse/CASSANDRA-12176
> Project: Cassandra
> Issue Type: Bug
>Reporter: Sean McCarthy
>Assignee: Carl Yeksigian
> Labels: dtest
> Attachments: node1.log, node1_debug.log, node1_gc.log, node2.log,
> node2_debug.log, node2_gc.log, node3.log, node3_debug.log, node3_gc.log,
> node4.log, node4_debug.log, node4_gc.log, node5.log, node5_debug.log,
> node5_gc.log
>
>
> example failure:
> http://cassci.datastax.com/job/cassandra-3.9_novnode_dtest/8/testReport/materialized_views_test/TestMaterializedViews/complex_repair_test
> Failed on CassCI build cassandra-3.9_novnode_dtest #8
> {code}
> Stacktrace
> File "/usr/lib/python2.7/unittest/case.py", line 329, in run
> testMethod()
> File "/home/automaton/cassandra-dtest/materialized_views_test.py", line
> 956, in complex_repair_test
> session.execute("CREATE TABLE ks.t (id int PRIMARY KEY, v int, v2 text,
> v3 decimal)"
> File "cassandra/cluster.py", line 1941, in
> cassandra.cluster.Session.execute (cassandra/cluster.c:33642)
> return self.execute_async(query, parameters, trace, custom_payload,
> timeout, execution_profile).result()
> File "cassandra/cluster.py", line 3629, in
> cassandra.cluster.ResponseFuture.result (cassandra/cluster.c:69369)
> raise self._final_exception
> ' message="Keyspace ks doesn\'t exist">
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (CASSANDRA-12340) dtest failure in upgrade_supercolumns_test.TestSCUpgrade.upgrade_with_counters_test
[
https://issues.apache.org/jira/browse/CASSANDRA-12340?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15404664#comment-15404664
]
Jim Witschey commented on CASSANDRA-12340:
--
This is my dtest PR:
https://github.com/riptano/cassandra-dtest/pull/1157/files
Could I get a review from a dev? It's occurred to me that this might not be the
only test affected by this problem, in which case this needs a fix applying to
more tests.
> dtest failure in
> upgrade_supercolumns_test.TestSCUpgrade.upgrade_with_counters_test
> ---
>
> Key: CASSANDRA-12340
> URL: https://issues.apache.org/jira/browse/CASSANDRA-12340
> Project: Cassandra
> Issue Type: Test
>Reporter: Sean McCarthy
>Assignee: Jim Witschey
> Labels: dtest
> Attachments: node1.log, node2.log, node3.log
>
>
> example failure:
> http://cassci.datastax.com/job/cassandra-2.1_dtest_jdk8/249/testReport/upgrade_supercolumns_test/TestSCUpgrade/upgrade_with_counters_test
> {code}
> Standard Output
> Unexpected error in node3 log, error:
> ERROR [CompactionExecutor:1] 2016-07-28 15:34:19,533 CassandraDaemon.java
> (line 191) Exception in thread Thread[CompactionExecutor:1,1,main]
> java.util.concurrent.RejectedExecutionException: Task
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask@5fb8b2bf
> rejected from
> org.apache.cassandra.concurrent.DebuggableScheduledThreadPoolExecutor@1ae851ad[Terminated,
> pool size = 0, active threads = 0, queued tasks = 0, completed tasks = 8]
> at
> java.util.concurrent.ThreadPoolExecutor$AbortPolicy.rejectedExecution(ThreadPoolExecutor.java:2047)
> at
> java.util.concurrent.ThreadPoolExecutor.reject(ThreadPoolExecutor.java:823)
> at
> java.util.concurrent.ScheduledThreadPoolExecutor.delayedExecute(ScheduledThreadPoolExecutor.java:326)
> at
> java.util.concurrent.ScheduledThreadPoolExecutor.schedule(ScheduledThreadPoolExecutor.java:533)
> at
> java.util.concurrent.ScheduledThreadPoolExecutor.submit(ScheduledThreadPoolExecutor.java:632)
> at
> org.apache.cassandra.io.sstable.SSTableDeletingTask.schedule(SSTableDeletingTask.java:65)
> at
> org.apache.cassandra.io.sstable.SSTableReader.releaseReference(SSTableReader.java:976)
> at
> org.apache.cassandra.db.DataTracker.removeOldSSTablesSize(DataTracker.java:383)
> at org.apache.cassandra.db.DataTracker.postReplace(DataTracker.java:348)
> at org.apache.cassandra.db.DataTracker.replace(DataTracker.java:342)
> at
> org.apache.cassandra.db.DataTracker.replaceCompactedSSTables(DataTracker.java:245)
> at
> org.apache.cassandra.db.ColumnFamilyStore.replaceCompactedSSTables(ColumnFamilyStore.java:995)
> at
> org.apache.cassandra.db.compaction.CompactionTask.replaceCompactedSSTables(CompactionTask.java:270)
> at
> org.apache.cassandra.db.compaction.CompactionTask.runWith(CompactionTask.java:230)
> at
> org.apache.cassandra.io.util.DiskAwareRunnable.runMayThrow(DiskAwareRunnable.java:48)
> at
> org.apache.cassandra.utils.WrappedRunnable.run(WrappedRunnable.java:28)
> at
> org.apache.cassandra.db.compaction.CompactionTask.executeInternal(CompactionTask.java:58)
> at
> org.apache.cassandra.db.compaction.AbstractCompactionTask.execute(AbstractCompactionTask.java:60)
> at
> org.apache.cassandra.db.compaction.CompactionManager$BackgroundCompactionTask.run(CompactionManager.java:208)
> at
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:745)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (CASSANDRA-11126) select_distinct_with_deletions_test failing on non-vnode environments
[
https://issues.apache.org/jira/browse/CASSANDRA-11126?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15404041#comment-15404041
]
Jim Witschey commented on CASSANDRA-11126:
--
Note that the commands I provided end with the names of the tests to run:
{code}
...
upgrade_tests/cql_tests.py:TestCQLNodes2RF1_Upgrade_current_2_1_x_To_indev_3_0_x.select_distinct_with_deletions_test
upgrade_tests/cql_tests.py:TestCQLNodes2RF1_Upgrade_current_2_1_x_To_indev_3_x.select_distinct_with_deletions_test
upgrade_tests/cql_tests.py:TestCQLNodes2RF1_Upgrade_current_2_2_x_To_indev_3_0_x.select_distinct_with_deletions_test
upgrade_tests/cql_tests.py:TestCQLNodes2RF1_Upgrade_current_2_2_x_To_indev_3_x.select_distinct_with_deletions_test
{code}
Those classes (e.g. {{TestCQLNodes2RF1_Upgrade_current_2_1_x_To_indev_3_0_x}})
are generated at runtime. {{TestCQL}} is a base class that is not configured to
run. I'll file a PR to improve error reporting in this case.
> select_distinct_with_deletions_test failing on non-vnode environments
> -
>
> Key: CASSANDRA-11126
> URL: https://issues.apache.org/jira/browse/CASSANDRA-11126
> Project: Cassandra
> Issue Type: Bug
>Reporter: Ryan McGuire
>Assignee: Sylvain Lebresne
> Labels: dtest
> Fix For: 3.0.x
>
>
> Looks like this was fixed in CASSANDRA-10762, but not for non-vnode
> environments:
> {code}
> $ DISABLE_VNODES=yes KEEP_TEST_DIR=yes CASSANDRA_VERSION=git:cassandra-3.0
> PRINT_DEBUG=true nosetests -s -v
> upgrade_tests/cql_tests.py:TestCQLNodes2RF1.select_distinct_with_deletions_test
> select_distinct_with_deletions_test
> (upgrade_tests.cql_tests.TestCQLNodes2RF1) ... cluster ccm directory:
> /tmp/dtest-UXb0un
> http://git-wip-us.apache.org/repos/asf/cassandra.git git:cassandra-3.0
> Custom init_config not found. Setting defaults.
> Done setting configuration options:
> { 'num_tokens': None,
> '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}
> getting default job version for 3.0.3
> UpgradePath(starting_version='binary:2.2.3', upgrade_version=None)
> starting from 2.2.3
> upgrading to {'install_dir':
> '/home/ryan/.ccm/repository/gitCOLONcassandra-3.0'}
> Querying upgraded node
> FAIL
> ==
> FAIL: select_distinct_with_deletions_test
> (upgrade_tests.cql_tests.TestCQLNodes2RF1)
> --
> Traceback (most recent call last):
> File "/home/ryan/git/datastax/cassandra-dtest/upgrade_tests/cql_tests.py",
> line 3360, in select_distinct_with_deletions_test
> self.assertEqual(9, len(rows))
> AssertionError: 9 != 8
> >> begin captured logging <<
> dtest: DEBUG: cluster ccm directory: /tmp/dtest-UXb0un
> dtest: DEBUG: Custom init_config not found. Setting defaults.
> dtest: DEBUG: Done setting configuration options:
> { 'num_tokens': None,
> '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}
> dtest: DEBUG: getting default job version for 3.0.3
> dtest: DEBUG: UpgradePath(starting_version='binary:2.2.3',
> upgrade_version=None)
> dtest: DEBUG: starting from 2.2.3
> dtest: DEBUG: upgrading to {'install_dir':
> '/home/ryan/.ccm/repository/gitCOLONcassandra-3.0'}
> dtest: DEBUG: Querying upgraded node
> - >> end captured logging << -
> --
> Ran 1 test in 56.022s
> FAILED (failures=1)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (CASSANDRA-12340) dtest failure in upgrade_supercolumns_test.TestSCUpgrade.upgrade_with_counters_test
[
https://issues.apache.org/jira/browse/CASSANDRA-12340?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15402433#comment-15402433
]
Jim Witschey commented on CASSANDRA-12340:
--
I can make a PR for dtest. Who makes decisions about whether this is
sufficiently critical for a C* 2.1 fix?
> dtest failure in
> upgrade_supercolumns_test.TestSCUpgrade.upgrade_with_counters_test
> ---
>
> Key: CASSANDRA-12340
> URL: https://issues.apache.org/jira/browse/CASSANDRA-12340
> Project: Cassandra
> Issue Type: Test
>Reporter: Sean McCarthy
>Assignee: Jim Witschey
> Labels: dtest
> Attachments: node1.log, node2.log, node3.log
>
>
> example failure:
> http://cassci.datastax.com/job/cassandra-2.1_dtest_jdk8/249/testReport/upgrade_supercolumns_test/TestSCUpgrade/upgrade_with_counters_test
> {code}
> Standard Output
> Unexpected error in node3 log, error:
> ERROR [CompactionExecutor:1] 2016-07-28 15:34:19,533 CassandraDaemon.java
> (line 191) Exception in thread Thread[CompactionExecutor:1,1,main]
> java.util.concurrent.RejectedExecutionException: Task
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask@5fb8b2bf
> rejected from
> org.apache.cassandra.concurrent.DebuggableScheduledThreadPoolExecutor@1ae851ad[Terminated,
> pool size = 0, active threads = 0, queued tasks = 0, completed tasks = 8]
> at
> java.util.concurrent.ThreadPoolExecutor$AbortPolicy.rejectedExecution(ThreadPoolExecutor.java:2047)
> at
> java.util.concurrent.ThreadPoolExecutor.reject(ThreadPoolExecutor.java:823)
> at
> java.util.concurrent.ScheduledThreadPoolExecutor.delayedExecute(ScheduledThreadPoolExecutor.java:326)
> at
> java.util.concurrent.ScheduledThreadPoolExecutor.schedule(ScheduledThreadPoolExecutor.java:533)
> at
> java.util.concurrent.ScheduledThreadPoolExecutor.submit(ScheduledThreadPoolExecutor.java:632)
> at
> org.apache.cassandra.io.sstable.SSTableDeletingTask.schedule(SSTableDeletingTask.java:65)
> at
> org.apache.cassandra.io.sstable.SSTableReader.releaseReference(SSTableReader.java:976)
> at
> org.apache.cassandra.db.DataTracker.removeOldSSTablesSize(DataTracker.java:383)
> at org.apache.cassandra.db.DataTracker.postReplace(DataTracker.java:348)
> at org.apache.cassandra.db.DataTracker.replace(DataTracker.java:342)
> at
> org.apache.cassandra.db.DataTracker.replaceCompactedSSTables(DataTracker.java:245)
> at
> org.apache.cassandra.db.ColumnFamilyStore.replaceCompactedSSTables(ColumnFamilyStore.java:995)
> at
> org.apache.cassandra.db.compaction.CompactionTask.replaceCompactedSSTables(CompactionTask.java:270)
> at
> org.apache.cassandra.db.compaction.CompactionTask.runWith(CompactionTask.java:230)
> at
> org.apache.cassandra.io.util.DiskAwareRunnable.runMayThrow(DiskAwareRunnable.java:48)
> at
> org.apache.cassandra.utils.WrappedRunnable.run(WrappedRunnable.java:28)
> at
> org.apache.cassandra.db.compaction.CompactionTask.executeInternal(CompactionTask.java:58)
> at
> org.apache.cassandra.db.compaction.AbstractCompactionTask.execute(AbstractCompactionTask.java:60)
> at
> org.apache.cassandra.db.compaction.CompactionManager$BackgroundCompactionTask.run(CompactionManager.java:208)
> at
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:745)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Assigned] (CASSANDRA-12340) dtest failure in upgrade_supercolumns_test.TestSCUpgrade.upgrade_with_counters_test
[
https://issues.apache.org/jira/browse/CASSANDRA-12340?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jim Witschey reassigned CASSANDRA-12340:
Assignee: Jim Witschey (was: DS Test Eng)
> dtest failure in
> upgrade_supercolumns_test.TestSCUpgrade.upgrade_with_counters_test
> ---
>
> Key: CASSANDRA-12340
> URL: https://issues.apache.org/jira/browse/CASSANDRA-12340
> Project: Cassandra
> Issue Type: Test
>Reporter: Sean McCarthy
>Assignee: Jim Witschey
> Labels: dtest
> Attachments: node1.log, node2.log, node3.log
>
>
> example failure:
> http://cassci.datastax.com/job/cassandra-2.1_dtest_jdk8/249/testReport/upgrade_supercolumns_test/TestSCUpgrade/upgrade_with_counters_test
> {code}
> Standard Output
> Unexpected error in node3 log, error:
> ERROR [CompactionExecutor:1] 2016-07-28 15:34:19,533 CassandraDaemon.java
> (line 191) Exception in thread Thread[CompactionExecutor:1,1,main]
> java.util.concurrent.RejectedExecutionException: Task
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask@5fb8b2bf
> rejected from
> org.apache.cassandra.concurrent.DebuggableScheduledThreadPoolExecutor@1ae851ad[Terminated,
> pool size = 0, active threads = 0, queued tasks = 0, completed tasks = 8]
> at
> java.util.concurrent.ThreadPoolExecutor$AbortPolicy.rejectedExecution(ThreadPoolExecutor.java:2047)
> at
> java.util.concurrent.ThreadPoolExecutor.reject(ThreadPoolExecutor.java:823)
> at
> java.util.concurrent.ScheduledThreadPoolExecutor.delayedExecute(ScheduledThreadPoolExecutor.java:326)
> at
> java.util.concurrent.ScheduledThreadPoolExecutor.schedule(ScheduledThreadPoolExecutor.java:533)
> at
> java.util.concurrent.ScheduledThreadPoolExecutor.submit(ScheduledThreadPoolExecutor.java:632)
> at
> org.apache.cassandra.io.sstable.SSTableDeletingTask.schedule(SSTableDeletingTask.java:65)
> at
> org.apache.cassandra.io.sstable.SSTableReader.releaseReference(SSTableReader.java:976)
> at
> org.apache.cassandra.db.DataTracker.removeOldSSTablesSize(DataTracker.java:383)
> at org.apache.cassandra.db.DataTracker.postReplace(DataTracker.java:348)
> at org.apache.cassandra.db.DataTracker.replace(DataTracker.java:342)
> at
> org.apache.cassandra.db.DataTracker.replaceCompactedSSTables(DataTracker.java:245)
> at
> org.apache.cassandra.db.ColumnFamilyStore.replaceCompactedSSTables(ColumnFamilyStore.java:995)
> at
> org.apache.cassandra.db.compaction.CompactionTask.replaceCompactedSSTables(CompactionTask.java:270)
> at
> org.apache.cassandra.db.compaction.CompactionTask.runWith(CompactionTask.java:230)
> at
> org.apache.cassandra.io.util.DiskAwareRunnable.runMayThrow(DiskAwareRunnable.java:48)
> at
> org.apache.cassandra.utils.WrappedRunnable.run(WrappedRunnable.java:28)
> at
> org.apache.cassandra.db.compaction.CompactionTask.executeInternal(CompactionTask.java:58)
> at
> org.apache.cassandra.db.compaction.AbstractCompactionTask.execute(AbstractCompactionTask.java:60)
> at
> org.apache.cassandra.db.compaction.CompactionManager$BackgroundCompactionTask.run(CompactionManager.java:208)
> at
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:745)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Resolved] (CASSANDRA-12339) dtest failure in cql_tracing_test.TestCqlTracing.tracing_unknown_impl_test
[ https://issues.apache.org/jira/browse/CASSANDRA-12339?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jim Witschey resolved CASSANDRA-12339. -- Resolution: Invalid > dtest failure in cql_tracing_test.TestCqlTracing.tracing_unknown_impl_test > -- > > Key: CASSANDRA-12339 > URL: https://issues.apache.org/jira/browse/CASSANDRA-12339 > Project: Cassandra > Issue Type: Test >Reporter: Craig Kodman >Assignee: DS Test Eng > Labels: dtest > Attachments: node1.log, node1_debug.log, node1_gc.log, node2.log, > node2_debug.log, node2_gc.log, node3.log, node3_debug.log, node3_gc.log > > > example failure: > http://cassci.datastax.com/job/cassandra-3.9_dtest/21/testReport/cql_tracing_test/TestCqlTracing/tracing_unknown_impl_test -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CASSANDRA-12339) dtest failure in cql_tracing_test.TestCqlTracing.tracing_unknown_impl_test
[ https://issues.apache.org/jira/browse/CASSANDRA-12339?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15399457#comment-15399457 ] Jim Witschey commented on CASSANDRA-12339: -- This failure seems to have happened on an earlier commit than the one that closed [CASSANDRA-11465|https://issues.apache.org/jira/browse/CASSANDRA-11465?focusedCommentId=1539=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-1539]. Closing. > dtest failure in cql_tracing_test.TestCqlTracing.tracing_unknown_impl_test > -- > > Key: CASSANDRA-12339 > URL: https://issues.apache.org/jira/browse/CASSANDRA-12339 > Project: Cassandra > Issue Type: Test >Reporter: Craig Kodman >Assignee: DS Test Eng > Labels: dtest > Attachments: node1.log, node1_debug.log, node1_gc.log, node2.log, > node2_debug.log, node2_gc.log, node3.log, node3_debug.log, node3_gc.log > > > example failure: > http://cassci.datastax.com/job/cassandra-3.9_dtest/21/testReport/cql_tracing_test/TestCqlTracing/tracing_unknown_impl_test -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CASSANDRA-12261) dtest failure in write_failures_test.TestWriteFailures.test_thrift
[
https://issues.apache.org/jira/browse/CASSANDRA-12261?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15397687#comment-15397687
]
Jim Witschey commented on CASSANDRA-12261:
--
bq. are you aware of any other tests with the same problem or a reasonably
reliable way to reproduce this?
No and no, unfortunately.
> dtest failure in write_failures_test.TestWriteFailures.test_thrift
> --
>
> Key: CASSANDRA-12261
> URL: https://issues.apache.org/jira/browse/CASSANDRA-12261
> Project: Cassandra
> Issue Type: Bug
>Reporter: Philip Thompson
>Assignee: Stefania
> Labels: dtest
> Fix For: 3.x
>
> 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.9_novnode_dtest/14/testReport/write_failures_test/TestWriteFailures/test_thrift
> Failure is
> {code}
> Unexpected error in node3 log, error:
> ERROR [NonPeriodicTasks:1] 2016-07-20 07:09:52,127 LogTransaction.java:205 -
> Unable to delete
> /tmp/dtest-CSPEFG/test/node3/data2/system_schema/tables-afddfb9dbc1e30688056eed6c302ba09/mb-2-big-Data.db
> as it does not exist
> Unexpected error in node3 log, error:
> ERROR [NonPeriodicTasks:1] 2016-07-20 07:09:52,334 LogTransaction.java:205 -
> Unable to delete
> /tmp/dtest-CSPEFG/test/node3/data2/system_schema/tables-afddfb9dbc1e30688056eed6c302ba09/mb-15-big-Data.db
> as it does not exist
> Unexpected error in node3 log, error:
> ERROR [NonPeriodicTasks:1] 2016-07-20 07:09:52,337 LogTransaction.java:205 -
> Unable to delete
> /tmp/dtest-CSPEFG/test/node3/data2/system_schema/tables-afddfb9dbc1e30688056eed6c302ba09/mb-31-big-Data.db
> as it does not exist
> Unexpected error in node3 log, error:
> ERROR [NonPeriodicTasks:1] 2016-07-20 07:09:52,339 LogTransaction.java:205 -
> Unable to delete
> /tmp/dtest-CSPEFG/test/node3/data2/system_schema/tables-afddfb9dbc1e30688056eed6c302ba09/mb-18-big-Data.db
> as it does not exist
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (CASSANDRA-11126) select_distinct_with_deletions_test failing on non-vnode environments
[
https://issues.apache.org/jira/browse/CASSANDRA-11126?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15396324#comment-15396324
]
Jim Witschey commented on CASSANDRA-11126:
--
Yeah, there's been some UI churn as we've been 1) trying to remove our
dependence on environment variables and 2) trying to make the upgrade tests
more maintainable. Sorry about that. The following command demonstrates that
this is still a bug:
{code}
RUN_STATIC_UPGRADE_MATRIX=true CASSANDRA_VERSION=git:trunk
JAVA8_HOME=/usr/lib/jvm/java-8-oracle JAVA7_HOME=/usr/lib/jvm/java-7-oracle
./run_dtests.py --vnodes false --nose-options='-v'
upgrade_tests/cql_tests.py:TestCQLNodes2RF1_Upgrade_current_2_1_x_To_indev_3_0_x.select_distinct_with_deletions_test
upgrade_tests/cql_tests.py:TestCQLNodes2RF1_Upgrade_current_2_1_x_To_indev_3_x.select_distinct_with_deletions_test
upgrade_tests/cql_tests.py:TestCQLNodes2RF1_Upgrade_current_2_2_x_To_indev_3_0_x.select_distinct_with_deletions_test
upgrade_tests/cql_tests.py:TestCQLNodes2RF1_Upgrade_current_2_2_x_To_indev_3_x.select_distinct_with_deletions_test
{code}
To run these upgrade tests upgrading to a version in a local directory, you can
do the following:
{code}
LOCAL_GIT_REPO=/home/mambocab/cstar_src/cassandra
CASSANDRA_VERSION=local:ccm_local_demo_branch
JAVA8_HOME=/usr/lib/jvm/java-8-oracle JAVA7_HOME=/usr/lib/jvm/java-7-oracle
./run_dtests.py --vnodes false --nose-options='-vv'
upgrade_tests/cql_tests.py:TestCQLNodes2RF1_Upgrade_current_2_1_x_To_indev_3_0_x.select_distinct_with_deletions_test
upgrade_tests/cql_tests.py:TestCQLNodes2RF1_Upgrade_current_2_1_x_To_indev_3_x.select_distinct_with_deletions_test
upgrade_tests/cql_tests.py:TestCQLNodes2RF1_Upgrade_current_2_2_x_To_indev_3_0_x.select_distinct_with_deletions_test
upgrade_tests/cql_tests.py:TestCQLNodes2RF1_Upgrade_current_2_2_x_To_indev_3_x.select_distinct_with_deletions_test
{code}
Depending on the C* version at the branch specified in {{CASSANDRA_VERSION}},
each test will either run or be skipped. If the branch is on the 3.0 line,
it'll be upgraded to in the {{*_3.0.x}} classes, and if it's on the 3.X line,
it'll be upgraded to in the {{*_3.x}} test classes. Otherwise, the test will be
skipped.
Sorry again for the interface churn; this could definitely use some
documentation
> select_distinct_with_deletions_test failing on non-vnode environments
> -
>
> Key: CASSANDRA-11126
> URL: https://issues.apache.org/jira/browse/CASSANDRA-11126
> Project: Cassandra
> Issue Type: Bug
>Reporter: Ryan McGuire
>Assignee: Sylvain Lebresne
> Labels: dtest
> Fix For: 3.0.x
>
>
> Looks like this was fixed in CASSANDRA-10762, but not for non-vnode
> environments:
> {code}
> $ DISABLE_VNODES=yes KEEP_TEST_DIR=yes CASSANDRA_VERSION=git:cassandra-3.0
> PRINT_DEBUG=true nosetests -s -v
> upgrade_tests/cql_tests.py:TestCQLNodes2RF1.select_distinct_with_deletions_test
> select_distinct_with_deletions_test
> (upgrade_tests.cql_tests.TestCQLNodes2RF1) ... cluster ccm directory:
> /tmp/dtest-UXb0un
> http://git-wip-us.apache.org/repos/asf/cassandra.git git:cassandra-3.0
> Custom init_config not found. Setting defaults.
> Done setting configuration options:
> { 'num_tokens': None,
> '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}
> getting default job version for 3.0.3
> UpgradePath(starting_version='binary:2.2.3', upgrade_version=None)
> starting from 2.2.3
> upgrading to {'install_dir':
> '/home/ryan/.ccm/repository/gitCOLONcassandra-3.0'}
> Querying upgraded node
> FAIL
> ==
> FAIL: select_distinct_with_deletions_test
> (upgrade_tests.cql_tests.TestCQLNodes2RF1)
> --
> Traceback (most recent call last):
> File "/home/ryan/git/datastax/cassandra-dtest/upgrade_tests/cql_tests.py",
> line 3360, in select_distinct_with_deletions_test
> self.assertEqual(9, len(rows))
> AssertionError: 9 != 8
> >> begin captured logging <<
> dtest: DEBUG: cluster ccm directory: /tmp/dtest-UXb0un
> dtest: DEBUG: Custom init_config not found. Setting defaults.
> dtest: DEBUG: Done setting configuration options:
> { 'num_tokens': None,
> '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}
> dtest: DEBUG: getting default job
[jira] [Comment Edited] (CASSANDRA-11126) select_distinct_with_deletions_test failing on non-vnode environments
[
https://issues.apache.org/jira/browse/CASSANDRA-11126?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15396324#comment-15396324
]
Jim Witschey edited comment on CASSANDRA-11126 at 7/27/16 8:35 PM:
---
Yeah, there's been some UI churn as we've been 1) trying to remove our
dependence on environment variables and 2) trying to make the upgrade tests
more maintainable. Sorry about that. The following command demonstrates that
this is still a bug:
{code}
RUN_STATIC_UPGRADE_MATRIX=true CASSANDRA_VERSION=git:trunk
JAVA8_HOME=/usr/lib/jvm/java-8-oracle JAVA7_HOME=/usr/lib/jvm/java-7-oracle
./run_dtests.py --vnodes false --nose-options='-v'
upgrade_tests/cql_tests.py:TestCQLNodes2RF1_Upgrade_current_2_1_x_To_indev_3_0_x.select_distinct_with_deletions_test
upgrade_tests/cql_tests.py:TestCQLNodes2RF1_Upgrade_current_2_1_x_To_indev_3_x.select_distinct_with_deletions_test
upgrade_tests/cql_tests.py:TestCQLNodes2RF1_Upgrade_current_2_2_x_To_indev_3_0_x.select_distinct_with_deletions_test
upgrade_tests/cql_tests.py:TestCQLNodes2RF1_Upgrade_current_2_2_x_To_indev_3_x.select_distinct_with_deletions_test
{code}
To run these upgrade tests upgrading to a version in a local directory, you can
do the following:
{code}
LOCAL_GIT_REPO=/home/mambocab/cstar_src/cassandra
CASSANDRA_VERSION=local:ccm_local_demo_branch
JAVA8_HOME=/usr/lib/jvm/java-8-oracle JAVA7_HOME=/usr/lib/jvm/java-7-oracle
./run_dtests.py --vnodes false --nose-options='-vv'
upgrade_tests/cql_tests.py:TestCQLNodes2RF1_Upgrade_current_2_1_x_To_indev_3_0_x.select_distinct_with_deletions_test
upgrade_tests/cql_tests.py:TestCQLNodes2RF1_Upgrade_current_2_1_x_To_indev_3_x.select_distinct_with_deletions_test
upgrade_tests/cql_tests.py:TestCQLNodes2RF1_Upgrade_current_2_2_x_To_indev_3_0_x.select_distinct_with_deletions_test
upgrade_tests/cql_tests.py:TestCQLNodes2RF1_Upgrade_current_2_2_x_To_indev_3_x.select_distinct_with_deletions_test
{code}
Depending on the C* version at the branch specified in {{CASSANDRA_VERSION}},
each test will either run or be skipped. If the branch is on the 3.0 line,
it'll be upgraded to in the {{*_3.0.x}} classes, and if it's on the 3.X line,
it'll be upgraded to in the {{*_3.x}} test classes. Otherwise, the test will be
skipped.
Sorry again for the interface churn; this could definitely use some
documentation
was (Author: mambocab):
Yeah, there's been some UI churn as we've been 1) trying to remove our
dependence on environment variables and 2) trying to make the upgrade tests
more maintainable. Sorry about that. The following command demonstrates that
this is still a bug:
{code}
RUN_STATIC_UPGRADE_MATRIX=true CASSANDRA_VERSION=git:trunk
JAVA8_HOME=/usr/lib/jvm/java-8-oracle JAVA7_HOME=/usr/lib/jvm/java-7-oracle
./run_dtests.py --vnodes false --nose-options='-v'
upgrade_tests/cql_tests.py:TestCQLNodes2RF1_Upgrade_current_2_1_x_To_indev_3_0_x.select_distinct_with_deletions_test
upgrade_tests/cql_tests.py:TestCQLNodes2RF1_Upgrade_current_2_1_x_To_indev_3_x.select_distinct_with_deletions_test
upgrade_tests/cql_tests.py:TestCQLNodes2RF1_Upgrade_current_2_2_x_To_indev_3_0_x.select_distinct_with_deletions_test
upgrade_tests/cql_tests.py:TestCQLNodes2RF1_Upgrade_current_2_2_x_To_indev_3_x.select_distinct_with_deletions_test
{code}
To run these upgrade tests upgrading to a version in a local directory, you can
do the following:
{code}
LOCAL_GIT_REPO=/home/mambocab/cstar_src/cassandra
CASSANDRA_VERSION=local:ccm_local_demo_branch
JAVA8_HOME=/usr/lib/jvm/java-8-oracle JAVA7_HOME=/usr/lib/jvm/java-7-oracle
./run_dtests.py --vnodes false --nose-options='-vv'
upgrade_tests/cql_tests.py:TestCQLNodes2RF1_Upgrade_current_2_1_x_To_indev_3_0_x.select_distinct_with_deletions_test
upgrade_tests/cql_tests.py:TestCQLNodes2RF1_Upgrade_current_2_1_x_To_indev_3_x.select_distinct_with_deletions_test
upgrade_tests/cql_tests.py:TestCQLNodes2RF1_Upgrade_current_2_2_x_To_indev_3_0_x.select_distinct_with_deletions_test
upgrade_tests/cql_tests.py:TestCQLNodes2RF1_Upgrade_current_2_2_x_To_indev_3_x.select_distinct_with_deletions_test
{code}
Depending on the C* version at the branch specified in {{CASSANDRA_VERSION}},
each test will either run or be skipped. If the branch is on the 3.0 line,
it'll be upgraded to in the {{*_3.0.x}} classes, and if it's on the 3.X line,
it'll be upgraded to in the {{*_3.x}} test classes. Otherwise, the test will be
skipped.
Sorry again for the interface churn; this could definitely use some
documentation
> select_distinct_with_deletions_test failing on non-vnode environments
> -
>
> Key: CASSANDRA-11126
> URL: https://issues.apache.org/jira/browse/CASSANDRA-11126
> Project: Cassandra
> Issue Type: Bug
>Reporter: Ryan McGuire
>
[jira] [Updated] (CASSANDRA-12275) dtest failure in offline_tools_test.TestOfflineTools.sstableofflinerelevel_test
[ https://issues.apache.org/jira/browse/CASSANDRA-12275?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jim Witschey updated CASSANDRA-12275: - Assignee: DS Test Eng (was: Jim Witschey) > dtest failure in > offline_tools_test.TestOfflineTools.sstableofflinerelevel_test > --- > > Key: CASSANDRA-12275 > URL: https://issues.apache.org/jira/browse/CASSANDRA-12275 > Project: Cassandra > Issue Type: Test >Reporter: Craig Kodman >Assignee: DS Test Eng > Labels: dtest, windows > Attachments: node1.log, node1_debug.log, node1_gc.log > > > example failure: > http://cassci.datastax.com/job/cassandra-2.2_dtest_win32/271/testReport/offline_tools_test/TestOfflineTools/sstableofflinerelevel_test -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CASSANDRA-12275) dtest failure in offline_tools_test.TestOfflineTools.sstableofflinerelevel_test
[ https://issues.apache.org/jira/browse/CASSANDRA-12275?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15394368#comment-15394368 ] Jim Witschey commented on CASSANDRA-12275: -- I don't know what could cause the tool to give no SSTable levels, so I've added some debugging improvements to the test: https://github.com/riptano/cassandra-dtest/pull/1137 Reassigning this to DS Test Eng while we wait for failures with more debug output. > dtest failure in > offline_tools_test.TestOfflineTools.sstableofflinerelevel_test > --- > > Key: CASSANDRA-12275 > URL: https://issues.apache.org/jira/browse/CASSANDRA-12275 > Project: Cassandra > Issue Type: Test >Reporter: Craig Kodman >Assignee: DS Test Eng > Labels: dtest, windows > Attachments: node1.log, node1_debug.log, node1_gc.log > > > example failure: > http://cassci.datastax.com/job/cassandra-2.2_dtest_win32/271/testReport/offline_tools_test/TestOfflineTools/sstableofflinerelevel_test -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CASSANDRA-12275) dtest failure in offline_tools_test.TestOfflineTools.sstableofflinerelevel_test
[
https://issues.apache.org/jira/browse/CASSANDRA-12275?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15394179#comment-15394179
]
Jim Witschey commented on CASSANDRA-12275:
--
Here's the error from Jenkins:
{code}
Error Message
max() arg is an empty sequence
>> begin captured logging <<
dtest: DEBUG: cluster ccm directory: d:\temp\dtest-19w_cr
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}
dtest: DEBUG: Altering compaction strategy to LCS
dtest: DEBUG: Waiting for compactions to finish
dtest: DEBUG: Stopping node
dtest: DEBUG: Done stopping node
dtest: DEBUG: Getting initial levels
dtest: DEBUG: Running sstablelevelreset
dtest: DEBUG: Getting final levels
- >> end captured logging << -
Stacktrace
File "C:\tools\python2\lib\unittest\case.py", line 329, in run
testMethod()
File
"D:\jenkins\workspace\cassandra-2.2_dtest_win32\cassandra-dtest\offline_tools_test.py",
line 178, in sstableofflinerelevel_test
self.assertGreater(max(initial_levels), 1)
"max() arg is an empty sequence\n >> begin captured logging
<< \ndtest: DEBUG: cluster ccm directory:
d:\\temp\\dtest-19w_cr\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}\ndtest: DEBUG: Altering compaction strategy to LCS\ndtest: DEBUG:
Waiting for compactions to finish\ndtest: DEBUG: Stopping node\ndtest: DEBUG:
Done stopping node\ndtest: DEBUG: Getting initial levels\ndtest: DEBUG: Running
sstablelevelreset\ndtest: DEBUG: Getting final levels\n- >>
end captured logging << -"
Standard Error
Started: node1 with pid: 5740
Started: node1 with pid: 6512
Started: node1 with pid: 7468
{code}
> dtest failure in
> offline_tools_test.TestOfflineTools.sstableofflinerelevel_test
> ---
>
> Key: CASSANDRA-12275
> URL: https://issues.apache.org/jira/browse/CASSANDRA-12275
> Project: Cassandra
> Issue Type: Test
>Reporter: Craig Kodman
>Assignee: DS Test Eng
> Labels: dtest, windows
> Attachments: node1.log, node1_debug.log, node1_gc.log
>
>
> example failure:
> http://cassci.datastax.com/job/cassandra-2.2_dtest_win32/271/testReport/offline_tools_test/TestOfflineTools/sstableofflinerelevel_test
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Assigned] (CASSANDRA-12275) dtest failure in offline_tools_test.TestOfflineTools.sstableofflinerelevel_test
[ https://issues.apache.org/jira/browse/CASSANDRA-12275?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jim Witschey reassigned CASSANDRA-12275: Assignee: Jim Witschey (was: DS Test Eng) > dtest failure in > offline_tools_test.TestOfflineTools.sstableofflinerelevel_test > --- > > Key: CASSANDRA-12275 > URL: https://issues.apache.org/jira/browse/CASSANDRA-12275 > Project: Cassandra > Issue Type: Test >Reporter: Craig Kodman >Assignee: Jim Witschey > Labels: dtest, windows > Attachments: node1.log, node1_debug.log, node1_gc.log > > > example failure: > http://cassci.datastax.com/job/cassandra-2.2_dtest_win32/271/testReport/offline_tools_test/TestOfflineTools/sstableofflinerelevel_test -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Comment Edited] (CASSANDRA-12296) system_auth can't be rebuilt by default
[
https://issues.apache.org/jira/browse/CASSANDRA-12296?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15394169#comment-15394169
]
Jim Witschey edited comment on CASSANDRA-12296 at 7/26/16 5:42 PM:
---
bq. perhaps we can indeed update the message to make this more clear.
Yeah, that's why I say it might just be a UX bug.
Telling users to use NTS for all _their_ keyspaces doesn't necessarily imply
doing so for _system_ keyspaces. I'd expect those to just work, and as a user I
might not think of them as "mine".
Why does {{system_auth}} use {{SimpleStrategy}} in the first place?
was (Author: mambocab):
Yeah, that's why I say it's probably a UX bug.
Why does {{system_auth}} use {{SimpleStrategy}} in the first place?
> system_auth can't be rebuilt by default
> ---
>
> Key: CASSANDRA-12296
> URL: https://issues.apache.org/jira/browse/CASSANDRA-12296
> Project: Cassandra
> Issue Type: Bug
>Reporter: Jim Witschey
>Priority: Minor
> Labels: lhf
>
> This came up in discussion of CASSANDRA-11687. {{nodetool rebuild}} was
> failing in a dtest. [~pauloricardomg] explained:
> bq. before [CASSANDRA-11848] the local node could be considered a source,
> while now sources are restricted only to dc2, so since {{system_auth}} uses
> {{SimpleStrategy}} depending on the token arrangement there could or not be
> sources from dc2. Fix is to either use
> {{-Dcassandra.consistent.rangemovement=false}} or update {{system_auth}} to
> use {{NetworkTopologyStrategy}} with 2 dcs..
> This is, at the very least, a UX bug. When {{rebuild}} fails, it fails with
> {code}
> nodetool: Unable to find sufficient sources for streaming range
> (-3287869951390391138,-1624006824486474209] in keyspace system_auth with
> RF=1.If you want to ignore this, consider using system property
> -Dcassandra.consistent.rangemovement=false.
> {code}
> which suggests that a user should give up consistency guarantees when it's
> not necessary.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (CASSANDRA-12296) system_auth can't be rebuilt by default
[
https://issues.apache.org/jira/browse/CASSANDRA-12296?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15394169#comment-15394169
]
Jim Witschey commented on CASSANDRA-12296:
--
Yeah, that's why I say it's probably a UX bug.
Why does {{system_auth}} use {{SimpleStrategy}} in the first place?
> system_auth can't be rebuilt by default
> ---
>
> Key: CASSANDRA-12296
> URL: https://issues.apache.org/jira/browse/CASSANDRA-12296
> Project: Cassandra
> Issue Type: Bug
>Reporter: Jim Witschey
>Priority: Minor
> Labels: lhf
>
> This came up in discussion of CASSANDRA-11687. {{nodetool rebuild}} was
> failing in a dtest. [~pauloricardomg] explained:
> bq. before [CASSANDRA-11848] the local node could be considered a source,
> while now sources are restricted only to dc2, so since {{system_auth}} uses
> {{SimpleStrategy}} depending on the token arrangement there could or not be
> sources from dc2. Fix is to either use
> {{-Dcassandra.consistent.rangemovement=false}} or update {{system_auth}} to
> use {{NetworkTopologyStrategy}} with 2 dcs..
> This is, at the very least, a UX bug. When {{rebuild}} fails, it fails with
> {code}
> nodetool: Unable to find sufficient sources for streaming range
> (-3287869951390391138,-1624006824486474209] in keyspace system_auth with
> RF=1.If you want to ignore this, consider using system property
> -Dcassandra.consistent.rangemovement=false.
> {code}
> which suggests that a user should give up consistency guarantees when it's
> not necessary.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Resolved] (CASSANDRA-12286) dtest failure in cdc_test.TestCDC.test_cdc_data_available_in_cdc_raw
[
https://issues.apache.org/jira/browse/CASSANDRA-12286?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jim Witschey resolved CASSANDRA-12286.
--
Resolution: Duplicate
> dtest failure in cdc_test.TestCDC.test_cdc_data_available_in_cdc_raw
>
>
> Key: CASSANDRA-12286
> URL: https://issues.apache.org/jira/browse/CASSANDRA-12286
> Project: Cassandra
> Issue Type: Test
>Reporter: Craig Kodman
>Assignee: Jim Witschey
> 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/cassandra-3.9_dtest/18/testReport/cdc_test/TestCDC/test_cdc_data_available_in_cdc_raw
> EDIT: for posterity, here's Jenkins's output:
> {code}
> Error Message
> Unexpected error in log, see stdout
> >> begin captured logging <<
> dtest: DEBUG: cluster ccm directory: /tmp/dtest-Fmzmjh
> 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}
> dtest: DEBUG: 1 rows inserted into ks.cdc_tab
> dtest: DEBUG: draining
> dtest: DEBUG: stopping
> dtest: DEBUG: adding node
> dtest: DEBUG: starting new node
> dtest: DEBUG: recreating ks and table
> dtest: DEBUG: creating new table
> dtest: DEBUG: stopping new node
> dtest: DEBUG: moving cdc_raw and restarting node
> dtest: DEBUG: moving
> /tmp/dtest-Fmzmjh/test/node1/cdc_raw/CommitLog-6-1469415177396.log to
> /tmp/dtest-Fmzmjh/test/node2/commitlogs/CommitLog-6-1469415177396.log
> dtest: DEBUG: moving
> /tmp/dtest-Fmzmjh/test/node1/cdc_raw/CommitLog-6-1469415177395.log to
> /tmp/dtest-Fmzmjh/test/node2/commitlogs/CommitLog-6-1469415177395.log
> dtest: DEBUG: removing ccm cluster test at: /tmp/dtest-Fmzmjh
> dtest: DEBUG: clearing ssl stores from [/tmp/dtest-Fmzmjh] directory
> - >> end captured logging << -
> Stacktrace
> File "/usr/lib/python2.7/unittest/case.py", line 358, in run
> self.tearDown()
> File "/home/automaton/cassandra-dtest/dtest.py", line 663, in tearDown
> raise AssertionError('Unexpected error in log, see stdout')
> "Unexpected error in log, see stdout\n >> begin captured
> logging << \ndtest: DEBUG: cluster ccm directory:
> /tmp/dtest-Fmzmjh\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}\ndtest: DEBUG: 1 rows inserted into ks.cdc_tab\ndtest: DEBUG:
> draining\ndtest: DEBUG: stopping\ndtest: DEBUG: adding node\ndtest: DEBUG:
> starting new node\ndtest: DEBUG: recreating ks and table\ndtest: DEBUG:
> creating new table\ndtest: DEBUG: stopping new node\ndtest: DEBUG: moving
> cdc_raw and restarting node\ndtest: DEBUG: moving
> /tmp/dtest-Fmzmjh/test/node1/cdc_raw/CommitLog-6-1469415177396.log to
> /tmp/dtest-Fmzmjh/test/node2/commitlogs/CommitLog-6-1469415177396.log\ndtest:
> DEBUG: moving
> /tmp/dtest-Fmzmjh/test/node1/cdc_raw/CommitLog-6-1469415177395.log to
> /tmp/dtest-Fmzmjh/test/node2/commitlogs/CommitLog-6-1469415177395.log\ndtest:
> DEBUG: removing ccm cluster test at: /tmp/dtest-Fmzmjh\ndtest: DEBUG:
> clearing ssl stores from [/tmp/dtest-Fmzmjh] directory\n-
> >> end captured logging << -"
> Standard Output
> Unexpected error in node2 log, error:
> ERROR [main] 2016-07-25 02:54:48,789 CassandraDaemon.java:733 - Fatal
> configuration error
> org.apache.cassandra.exceptions.ConfigurationException: Cannot change the
> number of tokens from 64 to 32
> at
> org.apache.cassandra.service.StorageService.joinTokenRing(StorageService.java:966)
> ~[main/:na]
> at
> org.apache.cassandra.service.StorageService.initServer(StorageService.java:663)
> ~[main/:na]
> at
> org.apache.cassandra.service.StorageService.initServer(StorageService.java:548)
> ~[main/:na]
> at
> org.apache.cassandra.service.CassandraDaemon.setup(CassandraDaemon.java:371)
> [main/:na]
> at
> org.apache.cassandra.service.CassandraDaemon.activate(CassandraDaemon.java:587)
> [main/:na]
> at
> org.apache.cassandra.service.CassandraDaemon.main(CassandraDaemon.java:716)
> [main/:na]
> {code}
--
This message was sent by Atlassian
[jira] [Commented] (CASSANDRA-11811) dtest failure in snapshot_test.TestArchiveCommitlog.test_archive_commitlog
[
https://issues.apache.org/jira/browse/CASSANDRA-11811?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15394029#comment-15394029
]
Jim Witschey commented on CASSANDRA-11811:
--
A similar error was reported as CASSANDRA-12286, where
{{cdc_test.py:TestCDC.test_cdc_data_available_in_cdc_raw}} failed. I'm closing
that as a dupe, but we should note that we saw this failure on 3.9 (commit
9501c64f) on Linux.
> dtest failure in snapshot_test.TestArchiveCommitlog.test_archive_commitlog
> --
>
> Key: CASSANDRA-11811
> URL: https://issues.apache.org/jira/browse/CASSANDRA-11811
> Project: Cassandra
> Issue Type: Bug
>Reporter: Philip Thompson
>Assignee: Branimir Lambov
> Labels: dtest, windows
> Fix For: 3.x
>
>
> example failure:
> http://cassci.datastax.com/job/trunk_dtest_win32/416/testReport/snapshot_test/TestArchiveCommitlog/test_archive_commitlog
> Failed on CassCI build trunk_dtest_win32 #416
> Relevant error is pasted. This is clearly a test problem. No idea why it only
> happens on windows, as of yet. Affecting most tests in the
> TestArchiveCommitlog suite
> {code}
> WARN: Failed to flush node: node1 on shutdown.
> Unexpected error in node1 log, error:
> ERROR [main] 2016-05-13 21:15:02,701 CassandraDaemon.java:729 - Fatal
> configuration error
> org.apache.cassandra.exceptions.ConfigurationException: Cannot change the
> number of tokens from 64 to 32
> at
> org.apache.cassandra.service.StorageService.joinTokenRing(StorageService.java:1043)
> ~[main/:na]
> at
> org.apache.cassandra.service.StorageService.initServer(StorageService.java:740)
> ~[main/:na]
> at
> org.apache.cassandra.service.StorageService.initServer(StorageService.java:625)
> ~[main/:na]
> at
> org.apache.cassandra.service.CassandraDaemon.setup(CassandraDaemon.java:368)
> [main/:na]
> at
> org.apache.cassandra.service.CassandraDaemon.activate(CassandraDaemon.java:583)
> [main/:na]
> at
> org.apache.cassandra.service.CassandraDaemon.main(CassandraDaemon.java:712)
> [main/:na]
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (CASSANDRA-12286) dtest failure in cdc_test.TestCDC.test_cdc_data_available_in_cdc_raw
[
https://issues.apache.org/jira/browse/CASSANDRA-12286?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jim Witschey updated CASSANDRA-12286:
-
Description:
example failure:
http://cassci.datastax.com/job/cassandra-3.9_dtest/18/testReport/cdc_test/TestCDC/test_cdc_data_available_in_cdc_raw
EDIT: for posterity, here's Jenkins's output:
{code}
Error Message
Unexpected error in log, see stdout
>> begin captured logging <<
dtest: DEBUG: cluster ccm directory: /tmp/dtest-Fmzmjh
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}
dtest: DEBUG: 1 rows inserted into ks.cdc_tab
dtest: DEBUG: draining
dtest: DEBUG: stopping
dtest: DEBUG: adding node
dtest: DEBUG: starting new node
dtest: DEBUG: recreating ks and table
dtest: DEBUG: creating new table
dtest: DEBUG: stopping new node
dtest: DEBUG: moving cdc_raw and restarting node
dtest: DEBUG: moving
/tmp/dtest-Fmzmjh/test/node1/cdc_raw/CommitLog-6-1469415177396.log to
/tmp/dtest-Fmzmjh/test/node2/commitlogs/CommitLog-6-1469415177396.log
dtest: DEBUG: moving
/tmp/dtest-Fmzmjh/test/node1/cdc_raw/CommitLog-6-1469415177395.log to
/tmp/dtest-Fmzmjh/test/node2/commitlogs/CommitLog-6-1469415177395.log
dtest: DEBUG: removing ccm cluster test at: /tmp/dtest-Fmzmjh
dtest: DEBUG: clearing ssl stores from [/tmp/dtest-Fmzmjh] directory
- >> end captured logging << -
Stacktrace
File "/usr/lib/python2.7/unittest/case.py", line 358, in run
self.tearDown()
File "/home/automaton/cassandra-dtest/dtest.py", line 663, in tearDown
raise AssertionError('Unexpected error in log, see stdout')
"Unexpected error in log, see stdout\n >> begin captured
logging << \ndtest: DEBUG: cluster ccm directory:
/tmp/dtest-Fmzmjh\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}\ndtest: DEBUG: 1 rows inserted into ks.cdc_tab\ndtest: DEBUG:
draining\ndtest: DEBUG: stopping\ndtest: DEBUG: adding node\ndtest: DEBUG:
starting new node\ndtest: DEBUG: recreating ks and table\ndtest: DEBUG:
creating new table\ndtest: DEBUG: stopping new node\ndtest: DEBUG: moving
cdc_raw and restarting node\ndtest: DEBUG: moving
/tmp/dtest-Fmzmjh/test/node1/cdc_raw/CommitLog-6-1469415177396.log to
/tmp/dtest-Fmzmjh/test/node2/commitlogs/CommitLog-6-1469415177396.log\ndtest:
DEBUG: moving
/tmp/dtest-Fmzmjh/test/node1/cdc_raw/CommitLog-6-1469415177395.log to
/tmp/dtest-Fmzmjh/test/node2/commitlogs/CommitLog-6-1469415177395.log\ndtest:
DEBUG: removing ccm cluster test at: /tmp/dtest-Fmzmjh\ndtest: DEBUG: clearing
ssl stores from [/tmp/dtest-Fmzmjh] directory\n- >> end
captured logging << -"
Standard Output
Unexpected error in node2 log, error:
ERROR [main] 2016-07-25 02:54:48,789 CassandraDaemon.java:733 - Fatal
configuration error
org.apache.cassandra.exceptions.ConfigurationException: Cannot change the
number of tokens from 64 to 32
at
org.apache.cassandra.service.StorageService.joinTokenRing(StorageService.java:966)
~[main/:na]
at
org.apache.cassandra.service.StorageService.initServer(StorageService.java:663)
~[main/:na]
at
org.apache.cassandra.service.StorageService.initServer(StorageService.java:548)
~[main/:na]
at
org.apache.cassandra.service.CassandraDaemon.setup(CassandraDaemon.java:371)
[main/:na]
at
org.apache.cassandra.service.CassandraDaemon.activate(CassandraDaemon.java:587)
[main/:na]
at
org.apache.cassandra.service.CassandraDaemon.main(CassandraDaemon.java:716)
[main/:na]
{code}
was:
example failure:
http://cassci.datastax.com/job/cassandra-3.9_dtest/18/testReport/cdc_test/TestCDC/test_cdc_data_available_in_cdc_raw
> dtest failure in cdc_test.TestCDC.test_cdc_data_available_in_cdc_raw
>
>
> Key: CASSANDRA-12286
> URL: https://issues.apache.org/jira/browse/CASSANDRA-12286
> Project: Cassandra
> Issue Type: Test
>Reporter: Craig Kodman
>Assignee: Jim Witschey
> Labels: dtest
> Attachments: node1.log, node1_debug.log, node1_gc.log, node2.log,
> node2_debug.log, node2_gc.log
>
>
> example failure:
>
[jira] [Commented] (CASSANDRA-11687) dtest failure in rebuild_test.TestRebuild.simple_rebuild_test
[
https://issues.apache.org/jira/browse/CASSANDRA-11687?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15393911#comment-15393911
]
Jim Witschey commented on CASSANDRA-11687:
--
I've filed [dtest PR 1133|https://github.com/riptano/cassandra-dtest/pull/1133]
to address the problem where {{rebuild}} would fail to find sources for
{{system_auth}}. This test still fails locally when nodetool allows concurrent
rebuilding. Reassigning to [~yukim] to address that issue.
> dtest failure in rebuild_test.TestRebuild.simple_rebuild_test
> -
>
> Key: CASSANDRA-11687
> URL: https://issues.apache.org/jira/browse/CASSANDRA-11687
> Project: Cassandra
> Issue Type: Bug
>Reporter: Russ Hatch
>Assignee: Jim Witschey
> Labels: dtest
>
> single failure on most recent run (3.0 no-vnode)
> {noformat}
> concurrent rebuild should not be allowed, but one rebuild command should have
> succeeded.
> {noformat}
> http://cassci.datastax.com/job/cassandra-3.0_novnode_dtest/217/testReport/rebuild_test/TestRebuild/simple_rebuild_test
> Failed on CassCI build cassandra-3.0_novnode_dtest #217
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (CASSANDRA-11687) dtest failure in rebuild_test.TestRebuild.simple_rebuild_test
[
https://issues.apache.org/jira/browse/CASSANDRA-11687?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jim Witschey updated CASSANDRA-11687:
-
Assignee: Yuki Morishita (was: Jim Witschey)
> dtest failure in rebuild_test.TestRebuild.simple_rebuild_test
> -
>
> Key: CASSANDRA-11687
> URL: https://issues.apache.org/jira/browse/CASSANDRA-11687
> Project: Cassandra
> Issue Type: Bug
>Reporter: Russ Hatch
>Assignee: Yuki Morishita
> Labels: dtest
>
> single failure on most recent run (3.0 no-vnode)
> {noformat}
> concurrent rebuild should not be allowed, but one rebuild command should have
> succeeded.
> {noformat}
> http://cassci.datastax.com/job/cassandra-3.0_novnode_dtest/217/testReport/rebuild_test/TestRebuild/simple_rebuild_test
> Failed on CassCI build cassandra-3.0_novnode_dtest #217
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (CASSANDRA-12296) system_auth can't be rebuilt by default
Jim Witschey created CASSANDRA-12296:
Summary: system_auth can't be rebuilt by default
Key: CASSANDRA-12296
URL: https://issues.apache.org/jira/browse/CASSANDRA-12296
Project: Cassandra
Issue Type: Bug
Reporter: Jim Witschey
This came up in discussion of CASSANDRA-11687. {{nodetool rebuild}} was failing
in a dtest. [~pauloricardomg] explained:
bq. before [CASSANDRA-11848] the local node could be considered a source, while
now sources are restricted only to dc2, so since {{system_auth}} uses
{{SimpleStrategy}} depending on the token arrangement there could or not be
sources from dc2. Fix is to either use
{{-Dcassandra.consistent.rangemovement=false}} or update {{system_auth}} to use
{{NetworkTopologyStrategy}} with 2 dcs..
This is, at the very least, a UX bug. When {{rebuild}} fails, it fails with
{code}
nodetool: Unable to find sufficient sources for streaming range
(-3287869951390391138,-1624006824486474209] in keyspace system_auth with
RF=1.If you want to ignore this, consider using system property
-Dcassandra.consistent.rangemovement=false.
{code}
which suggests that a user should give up consistency guarantees when it's not
necessary.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (CASSANDRA-11687) dtest failure in rebuild_test.TestRebuild.simple_rebuild_test
[
https://issues.apache.org/jira/browse/CASSANDRA-11687?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15389964#comment-15389964
]
Jim Witschey commented on CASSANDRA-11687:
--
[~yukim] If you agree with Paulo that this is a test issue, feel free to assign
this ticket to me and I'll deal with it.
> dtest failure in rebuild_test.TestRebuild.simple_rebuild_test
> -
>
> Key: CASSANDRA-11687
> URL: https://issues.apache.org/jira/browse/CASSANDRA-11687
> Project: Cassandra
> Issue Type: Bug
>Reporter: Russ Hatch
>Assignee: Yuki Morishita
> Labels: dtest
>
> single failure on most recent run (3.0 no-vnode)
> {noformat}
> concurrent rebuild should not be allowed, but one rebuild command should have
> succeeded.
> {noformat}
> http://cassci.datastax.com/job/cassandra-3.0_novnode_dtest/217/testReport/rebuild_test/TestRebuild/simple_rebuild_test
> Failed on CassCI build cassandra-3.0_novnode_dtest #217
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (CASSANDRA-11687) dtest failure in rebuild_test.TestRebuild.simple_rebuild_test
[
https://issues.apache.org/jira/browse/CASSANDRA-11687?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15389958#comment-15389958
]
Jim Witschey commented on CASSANDRA-11687:
--
bq. True, but I maintain that there are enough sources for system_auth for all
ranges up, at the time of rebuild.
Oh, I agree -- just saying that passing tests in the CassCI history may be the
result of incorrect test code.
> dtest failure in rebuild_test.TestRebuild.simple_rebuild_test
> -
>
> Key: CASSANDRA-11687
> URL: https://issues.apache.org/jira/browse/CASSANDRA-11687
> Project: Cassandra
> Issue Type: Bug
>Reporter: Russ Hatch
>Assignee: Yuki Morishita
> Labels: dtest
>
> single failure on most recent run (3.0 no-vnode)
> {noformat}
> concurrent rebuild should not be allowed, but one rebuild command should have
> succeeded.
> {noformat}
> http://cassci.datastax.com/job/cassandra-3.0_novnode_dtest/217/testReport/rebuild_test/TestRebuild/simple_rebuild_test
> Failed on CassCI build cassandra-3.0_novnode_dtest #217
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (CASSANDRA-11895) dtest failure in cqlsh_tests.cqlsh_tests.TestCqlsh.test_unicode_invalid_request_error
[ https://issues.apache.org/jira/browse/CASSANDRA-11895?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15388396#comment-15388396 ] Jim Witschey commented on CASSANDRA-11895: -- Could this be related to the Python-version-related stuff that [~Stefania] has been looking at? > dtest failure in > cqlsh_tests.cqlsh_tests.TestCqlsh.test_unicode_invalid_request_error > - > > Key: CASSANDRA-11895 > URL: https://issues.apache.org/jira/browse/CASSANDRA-11895 > Project: Cassandra > Issue Type: Test >Reporter: Sean McCarthy >Assignee: Michael Shuler > Labels: dtest > Attachments: node1.log > > > example failure: > http://cassci.datastax.com/job/cassandra-2.1_dtest/470/testReport/cqlsh_tests.cqlsh_tests/TestCqlsh/test_unicode_invalid_request_error > Failed on CassCI build cassandra-2.1_dtest #470 > This is after the fix for CASSANDRA-11799. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Comment Edited] (CASSANDRA-12250) dtest failure in upgrade_tests.cql_tests.TestCQLNodes2RF1_Upgrade_current_3_x_To_indev_3_x.bug_5732_test
[
https://issues.apache.org/jira/browse/CASSANDRA-12250?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15388276#comment-15388276
]
Jim Witschey edited comment on CASSANDRA-12250 at 7/21/16 7:35 PM:
---
Closing with that dtest PR, as its CassCI run ran clean:
http://cassci.datastax.com/view/Parameterized/job/parameterized_dtest_multiplexer/180/console
was (Author: mambocab):
Closing with that dtest PR.
> dtest failure in
> upgrade_tests.cql_tests.TestCQLNodes2RF1_Upgrade_current_3_x_To_indev_3_x.bug_5732_test
>
>
> Key: CASSANDRA-12250
> URL: https://issues.apache.org/jira/browse/CASSANDRA-12250
> Project: Cassandra
> Issue Type: Test
>Reporter: Philip Thompson
>Assignee: Jim Witschey
> Labels: dtest
>
> example failure:
> http://cassci.datastax.com/job/cassandra-3.8_dtest_upgrade/1/testReport/upgrade_tests.cql_tests/TestCQLNodes2RF1_Upgrade_current_3_x_To_indev_3_x/bug_5732_test
> Failed on CassCI build cassandra-3.8_dtest_upgrade #1
> The error failing the test is:
> {code}
> ERROR [SharedPool-Worker-1] 2016-07-20 05:06:04,982
> MessageDeliveryTask.java:74 - The secondary index 'testindex' is not yet
> available
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Resolved] (CASSANDRA-12250) dtest failure in upgrade_tests.cql_tests.TestCQLNodes2RF1_Upgrade_current_3_x_To_indev_3_x.bug_5732_test
[
https://issues.apache.org/jira/browse/CASSANDRA-12250?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jim Witschey resolved CASSANDRA-12250.
--
Resolution: Fixed
> dtest failure in
> upgrade_tests.cql_tests.TestCQLNodes2RF1_Upgrade_current_3_x_To_indev_3_x.bug_5732_test
>
>
> Key: CASSANDRA-12250
> URL: https://issues.apache.org/jira/browse/CASSANDRA-12250
> Project: Cassandra
> Issue Type: Test
>Reporter: Philip Thompson
>Assignee: Jim Witschey
> Labels: dtest
>
> example failure:
> http://cassci.datastax.com/job/cassandra-3.8_dtest_upgrade/1/testReport/upgrade_tests.cql_tests/TestCQLNodes2RF1_Upgrade_current_3_x_To_indev_3_x/bug_5732_test
> Failed on CassCI build cassandra-3.8_dtest_upgrade #1
> The error failing the test is:
> {code}
> ERROR [SharedPool-Worker-1] 2016-07-20 05:06:04,982
> MessageDeliveryTask.java:74 - The secondary index 'testindex' is not yet
> available
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (CASSANDRA-12250) dtest failure in upgrade_tests.cql_tests.TestCQLNodes2RF1_Upgrade_current_3_x_To_indev_3_x.bug_5732_test
[
https://issues.apache.org/jira/browse/CASSANDRA-12250?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15388276#comment-15388276
]
Jim Witschey commented on CASSANDRA-12250:
--
Closing with that dtest PR.
> dtest failure in
> upgrade_tests.cql_tests.TestCQLNodes2RF1_Upgrade_current_3_x_To_indev_3_x.bug_5732_test
>
>
> Key: CASSANDRA-12250
> URL: https://issues.apache.org/jira/browse/CASSANDRA-12250
> Project: Cassandra
> Issue Type: Test
>Reporter: Philip Thompson
>Assignee: Jim Witschey
> Labels: dtest
>
> example failure:
> http://cassci.datastax.com/job/cassandra-3.8_dtest_upgrade/1/testReport/upgrade_tests.cql_tests/TestCQLNodes2RF1_Upgrade_current_3_x_To_indev_3_x/bug_5732_test
> Failed on CassCI build cassandra-3.8_dtest_upgrade #1
> The error failing the test is:
> {code}
> ERROR [SharedPool-Worker-1] 2016-07-20 05:06:04,982
> MessageDeliveryTask.java:74 - The secondary index 'testindex' is not yet
> available
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (CASSANDRA-12250) dtest failure in upgrade_tests.cql_tests.TestCQLNodes2RF1_Upgrade_current_3_x_To_indev_3_x.bug_5732_test
[
https://issues.apache.org/jira/browse/CASSANDRA-12250?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15388197#comment-15388197
]
Jim Witschey commented on CASSANDRA-12250:
--
Filed [dtest PR 1117|https://github.com/riptano/cassandra-dtest/pull/1117].
> dtest failure in
> upgrade_tests.cql_tests.TestCQLNodes2RF1_Upgrade_current_3_x_To_indev_3_x.bug_5732_test
>
>
> Key: CASSANDRA-12250
> URL: https://issues.apache.org/jira/browse/CASSANDRA-12250
> Project: Cassandra
> Issue Type: Test
>Reporter: Philip Thompson
>Assignee: Jim Witschey
> Labels: dtest
>
> example failure:
> http://cassci.datastax.com/job/cassandra-3.8_dtest_upgrade/1/testReport/upgrade_tests.cql_tests/TestCQLNodes2RF1_Upgrade_current_3_x_To_indev_3_x/bug_5732_test
> Failed on CassCI build cassandra-3.8_dtest_upgrade #1
> The error failing the test is:
> {code}
> ERROR [SharedPool-Worker-1] 2016-07-20 05:06:04,982
> MessageDeliveryTask.java:74 - The secondary index 'testindex' is not yet
> available
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Assigned] (CASSANDRA-12250) dtest failure in upgrade_tests.cql_tests.TestCQLNodes2RF1_Upgrade_current_3_x_To_indev_3_x.bug_5732_test
[
https://issues.apache.org/jira/browse/CASSANDRA-12250?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jim Witschey reassigned CASSANDRA-12250:
Assignee: Jim Witschey (was: DS Test Eng)
> dtest failure in
> upgrade_tests.cql_tests.TestCQLNodes2RF1_Upgrade_current_3_x_To_indev_3_x.bug_5732_test
>
>
> Key: CASSANDRA-12250
> URL: https://issues.apache.org/jira/browse/CASSANDRA-12250
> Project: Cassandra
> Issue Type: Test
>Reporter: Philip Thompson
>Assignee: Jim Witschey
> Labels: dtest
>
> example failure:
> http://cassci.datastax.com/job/cassandra-3.8_dtest_upgrade/1/testReport/upgrade_tests.cql_tests/TestCQLNodes2RF1_Upgrade_current_3_x_To_indev_3_x/bug_5732_test
> Failed on CassCI build cassandra-3.8_dtest_upgrade #1
> The error failing the test is:
> {code}
> ERROR [SharedPool-Worker-1] 2016-07-20 05:06:04,982
> MessageDeliveryTask.java:74 - The secondary index 'testindex' is not yet
> available
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (CASSANDRA-11446) dtest failure in scrub_test.TestScrub.test_nodetool_scrub
[
https://issues.apache.org/jira/browse/CASSANDRA-11446?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jim Witschey updated CASSANDRA-11446:
-
Issue Type: Test (was: Bug)
> dtest failure in scrub_test.TestScrub.test_nodetool_scrub
> -
>
> Key: CASSANDRA-11446
> URL: https://issues.apache.org/jira/browse/CASSANDRA-11446
> Project: Cassandra
> Issue Type: Test
>Reporter: Philip Thompson
>Assignee: Jim Witschey
> Labels: dtest
>
> test_nodetool_scrub is failing on trunk with offheap memtables. The failure
> is in this assertion:
> {{self.assertEqual(initial_sstables, scrubbed_sstables)}}
> Example failure:
> http://cassci.datastax.com/job/trunk_offheap_dtest/95/testReport/scrub_test/TestScrub/test_nodetool_scrub/
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Resolved] (CASSANDRA-11446) dtest failure in scrub_test.TestScrub.test_nodetool_scrub
[
https://issues.apache.org/jira/browse/CASSANDRA-11446?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jim Witschey resolved CASSANDRA-11446.
--
Resolution: Fixed
Closing with https://github.com/riptano/cassandra-dtest/pull/1086
> dtest failure in scrub_test.TestScrub.test_nodetool_scrub
> -
>
> Key: CASSANDRA-11446
> URL: https://issues.apache.org/jira/browse/CASSANDRA-11446
> Project: Cassandra
> Issue Type: Bug
>Reporter: Philip Thompson
>Assignee: Jim Witschey
> Labels: dtest
>
> test_nodetool_scrub is failing on trunk with offheap memtables. The failure
> is in this assertion:
> {{self.assertEqual(initial_sstables, scrubbed_sstables)}}
> Example failure:
> http://cassci.datastax.com/job/trunk_offheap_dtest/95/testReport/scrub_test/TestScrub/test_nodetool_scrub/
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Resolved] (CASSANDRA-12262) dtest failure in user_functions_test.TestUserFunctions.udf_with_udt_test
[ https://issues.apache.org/jira/browse/CASSANDRA-12262?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jim Witschey resolved CASSANDRA-12262. -- Resolution: Cannot Reproduce Assignee: Jim Witschey (was: DS Test Eng) Nothing useful in stdout either. I think this is one to just close, unfortunately. > dtest failure in user_functions_test.TestUserFunctions.udf_with_udt_test > > > Key: CASSANDRA-12262 > URL: https://issues.apache.org/jira/browse/CASSANDRA-12262 > Project: Cassandra > Issue Type: Test >Reporter: Philip Thompson >Assignee: Jim Witschey > Labels: dtest > > example failure: > http://cassci.datastax.com/job/cassandra-3.9_dtest/14/testReport/user_functions_test/TestUserFunctions/udf_with_udt_test > It seems to just be failing to start up? No logs were captured at all. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CASSANDRA-11687) dtest failure in rebuild_test.TestRebuild.simple_rebuild_test
[
https://issues.apache.org/jira/browse/CASSANDRA-11687?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15387875#comment-15387875
]
Jim Witschey commented on CASSANDRA-11687:
--
This problem could have been around for a while but not caught because of bad
error handling in the test.
> dtest failure in rebuild_test.TestRebuild.simple_rebuild_test
> -
>
> Key: CASSANDRA-11687
> URL: https://issues.apache.org/jira/browse/CASSANDRA-11687
> Project: Cassandra
> Issue Type: Bug
>Reporter: Russ Hatch
> Labels: dtest
>
> single failure on most recent run (3.0 no-vnode)
> {noformat}
> concurrent rebuild should not be allowed, but one rebuild command should have
> succeeded.
> {noformat}
> http://cassci.datastax.com/job/cassandra-3.0_novnode_dtest/217/testReport/rebuild_test/TestRebuild/simple_rebuild_test
> Failed on CassCI build cassandra-3.0_novnode_dtest #217
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (CASSANDRA-11999) dtest failure in cqlsh_tests.cqlsh_tests.TestCqlsh.test_refresh_schema_on_timeout_error
[ https://issues.apache.org/jira/browse/CASSANDRA-11999?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15386066#comment-15386066 ] Jim Witschey commented on CASSANDRA-11999: -- [~Stefania] If I understand CASSANDRA-11850 correctly, this will be closed when it's merged. I'm going to assign this to you because of that; if I'm wrong, feel free to assign it back to DS Test Eng. > dtest failure in > cqlsh_tests.cqlsh_tests.TestCqlsh.test_refresh_schema_on_timeout_error > --- > > Key: CASSANDRA-11999 > URL: https://issues.apache.org/jira/browse/CASSANDRA-11999 > Project: Cassandra > Issue Type: Test >Reporter: Craig Kodman >Assignee: DS Test Eng > Labels: dtest > Attachments: node1.log, node1_debug.log, node2.log, node2_debug.log, > node3.log, node3_debug.log > > > example failure: > http://cassci.datastax.com/job/cassandra-3.0_dtest/745/testReport/cqlsh_tests.cqlsh_tests/TestCqlsh/test_refresh_schema_on_timeout_error > Failed on CassCI build cassandra-3.0_dtest #745 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CASSANDRA-11999) dtest failure in cqlsh_tests.cqlsh_tests.TestCqlsh.test_refresh_schema_on_timeout_error
[ https://issues.apache.org/jira/browse/CASSANDRA-11999?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jim Witschey updated CASSANDRA-11999: - Assignee: Stefania (was: DS Test Eng) > dtest failure in > cqlsh_tests.cqlsh_tests.TestCqlsh.test_refresh_schema_on_timeout_error > --- > > Key: CASSANDRA-11999 > URL: https://issues.apache.org/jira/browse/CASSANDRA-11999 > Project: Cassandra > Issue Type: Test >Reporter: Craig Kodman >Assignee: Stefania > Labels: dtest > Attachments: node1.log, node1_debug.log, node2.log, node2_debug.log, > node3.log, node3_debug.log > > > example failure: > http://cassci.datastax.com/job/cassandra-3.0_dtest/745/testReport/cqlsh_tests.cqlsh_tests/TestCqlsh/test_refresh_schema_on_timeout_error > Failed on CassCI build cassandra-3.0_dtest #745 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Comment Edited] (CASSANDRA-12137) dtest failure in sstable_generation_loading_test.TestSSTableGenerationAndLoading.sstableloader_compression_deflate_to_snappy_test
[
https://issues.apache.org/jira/browse/CASSANDRA-12137?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15366593#comment-15366593
]
Jim Witschey edited comment on CASSANDRA-12137 at 7/20/16 2:53 PM:
---
Filed a PR to address the problem with accessing {{sstableloader}}:
https://github.com/riptano/cassandra-dtest/pull/1080
This depends on a CCM PR. Reassigning this to TE while we wait.
was (Author: mambocab):
Filed a PR to address the problem with accessing {{sstableloader}}:
https://github.com/riptano/cassandra-dtest/pull/1080
Reassigning this to TE while we wait.
> dtest failure in
> sstable_generation_loading_test.TestSSTableGenerationAndLoading.sstableloader_compression_deflate_to_snappy_test
> -
>
> Key: CASSANDRA-12137
> URL: https://issues.apache.org/jira/browse/CASSANDRA-12137
> Project: Cassandra
> Issue Type: Test
>Reporter: Sean McCarthy
>Assignee: DS Test Eng
> Labels: dtest
>
> example failure:
> http://cassci.datastax.com/job/cassandra-3.0_dtest/764/testReport/sstable_generation_loading_test/TestSSTableGenerationAndLoading/sstableloader_compression_deflate_to_snappy_test
> {code}
> Stacktrace
> File "/usr/lib/python2.7/unittest/case.py", line 329, in run
> testMethod()
> File "/home/automaton/cassandra-dtest/sstable_generation_loading_test.py",
> line 75, in sstableloader_compression_deflate_to_snappy_test
> self.load_sstable_with_configuration('Deflate', 'Snappy')
> File "/home/automaton/cassandra-dtest/sstable_generation_loading_test.py",
> line 178, in load_sstable_with_configuration
> "sstableloader exited with a non-zero status: {}".format(exit_status))
> File "/usr/lib/python2.7/unittest/case.py", line 513, in assertEqual
> assertion_func(first, second, msg=msg)
> File "/usr/lib/python2.7/unittest/case.py", line 506, in _baseAssertEqual
> raise self.failureException(msg)
> "sstableloader exited with a non-zero status: 1
> {code}
> Related failures:
> http://cassci.datastax.com/job/cassandra-3.0_dtest/764/testReport/sstable_generation_loading_test/TestSSTableGenerationAndLoading/sstableloader_compression_none_to_snappy_test/
> http://cassci.datastax.com/job/cassandra-3.0_dtest/764/testReport/sstable_generation_loading_test/TestSSTableGenerationAndLoading/sstableloader_with_mv_test/
> Failed on CassCI build cassandra-3.0_dtest #764
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (CASSANDRA-12162) dtest failure in repair_tests.repair_test.TestRepair.simple_sequential_repair_test
[
https://issues.apache.org/jira/browse/CASSANDRA-12162?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15385936#comment-15385936
]
Jim Witschey commented on CASSANDRA-12162:
--
This is a relatively low-value failure, since it fails on Windows only. I'll
leave it open, and if it hasn't flapped after a few more runs, I'll close.
> dtest failure in
> repair_tests.repair_test.TestRepair.simple_sequential_repair_test
> --
>
> Key: CASSANDRA-12162
> URL: https://issues.apache.org/jira/browse/CASSANDRA-12162
> Project: Cassandra
> Issue Type: Test
>Reporter: Sean McCarthy
>Assignee: DS Test Eng
> Labels: dtest
> Attachments: node1.log, node1_debug.log, node1_gc.log, node2.log,
> node2_debug.log, node2_gc.log, node3.log, node3_debug.log, node3_gc.log
>
>
> example failure:
> http://cassci.datastax.com/job/cassandra-2.2_dtest_win32/267/testReport/repair_tests.repair_test/TestRepair/simple_sequential_repair_test
> Failed on CassCI build cassandra-2.2_dtest_win32 #267
> {code}
> Stacktrace
> File "C:\tools\python2\lib\unittest\case.py", line 329, in run
> testMethod()
> File
> "D:\jenkins\workspace\cassandra-2.2_dtest_win32\cassandra-dtest\repair_tests\repair_test.py",
> line 241, in simple_sequential_repair_test
> self._simple_repair(sequential=True)
> File
> "D:\jenkins\workspace\cassandra-2.2_dtest_win32\cassandra-dtest\repair_tests\repair_test.py",
> line 295, in _simple_repair
> self._populate_cluster()
> File
> "D:\jenkins\workspace\cassandra-2.2_dtest_win32\cassandra-dtest\repair_tests\repair_test.py",
> line 98, in _populate_cluster
> insert_c1c2(session, n=1000, consistency=ConsistencyLevel.ALL)
> File
> "D:\jenkins\workspace\cassandra-2.2_dtest_win32\cassandra-dtest\tools.py",
> line 78, in insert_c1c2
> execute_concurrent_with_args(session, statement, [['k{}'.format(k)] for k
> in keys])
> File "cassandra\concurrent.py", line 224, in
> cassandra.concurrent.execute_concurrent_with_args
> (cassandra/concurrent.c:5996)
> return execute_concurrent(session, zip(cycle((statement,)), parameters),
> *args, **kwargs)
> File "cassandra\concurrent.py", line 92, in
> cassandra.concurrent.execute_concurrent (cassandra/concurrent.c:1455)
> return executor.execute(concurrency, raise_on_first_error)
> File "cassandra\concurrent.py", line 187, in
> cassandra.concurrent.ConcurrentExecutorListResults.execute
> (cassandra/concurrent.c:4824)
> return super(ConcurrentExecutorListResults, self).execute(concurrency,
> fail_fast)
> File "cassandra\concurrent.py", line 115, in
> cassandra.concurrent._ConcurrentExecutor.execute (cassandra/concurrent.c:2120)
> return self._results()
> File "cassandra\concurrent.py", line 201, in
> cassandra.concurrent.ConcurrentExecutorListResults._results
> (cassandra/concurrent.c:5617)
> with self._condition:
> File "cassandra\concurrent.py", line 205, in
> cassandra.concurrent.ConcurrentExecutorListResults._results
> (cassandra/concurrent.c:5549)
> self._raise(self._exception)
> File "cassandra\concurrent.py", line 153, in
> cassandra.concurrent._ConcurrentExecutor._raise (cassandra/concurrent.c:3498)
> raise exc
> 'Error from server: code=1500 [Replica(s) failed to execute write]
> message="Operation failed - received 2 responses and 1 failures"
> info={\'failures\': 1, \'received_responses\': 2, \'required_responses\': 3,
> \'consistency\': \'ALL\'}
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Comment Edited] (CASSANDRA-11465) dtest failure in cql_tracing_test.TestCqlTracing.tracing_unknown_impl_test
[
https://issues.apache.org/jira/browse/CASSANDRA-11465?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15384761#comment-15384761
]
Jim Witschey edited comment on CASSANDRA-11465 at 7/19/16 8:02 PM:
---
I ran the following script:
{code}
for i in `seq 30` ; do
echo iteration $i
PRINT_DEBUG=true DEBUG=true
CASSANDRA_VERSION=github:stef1927/11465-cqlsh-3.9
TRACE=org.apache.cassandra.tracing.TraceStateImpl nosetests cql_tracing_test.py
killall -9 java
done
for i in `seq 30` ; do
echo iteration $i
PRINT_DEBUG=true DEBUG=true
CASSANDRA_VERSION=github:stef1927/11465-cqlsh
TRACE=org.apache.cassandra.tracing.TraceStateImpl nosetests cql_tracing_test.py
killall -9 java
done
{code}
and saw no failures:
https://gist.github.com/072692334800285afc8d362165cb37a6
EDIT: I did so on an {{m3.xlarge}} instance on openstack.
was (Author: mambocab):
I ran the following script:
{code}
for i in `seq 30` ; do
echo iteration $i
PRINT_DEBUG=true DEBUG=true
CASSANDRA_VERSION=github:stef1927/11465-cqlsh-3.9
TRACE=org.apache.cassandra.tracing.TraceStateImpl nosetests cql_tracing_test.py
killall -9 java
done
for i in `seq 30` ; do
echo iteration $i
PRINT_DEBUG=true DEBUG=true
CASSANDRA_VERSION=github:stef1927/11465-cqlsh
TRACE=org.apache.cassandra.tracing.TraceStateImpl nosetests cql_tracing_test.py
killall -9 java
done
{code}
and saw no failures:
https://gist.github.com/072692334800285afc8d362165cb37a6
> dtest failure in cql_tracing_test.TestCqlTracing.tracing_unknown_impl_test
> --
>
> Key: CASSANDRA-11465
> URL: https://issues.apache.org/jira/browse/CASSANDRA-11465
> Project: Cassandra
> Issue Type: Bug
>Reporter: Philip Thompson
>Assignee: Stefania
> Labels: dtest
>
> Failing on the following assert, on trunk only:
> {{self.assertEqual(len(errs[0]), 1)}}
> Is not failing consistently.
> example failure:
> http://cassci.datastax.com/job/trunk_dtest/1087/testReport/cql_tracing_test/TestCqlTracing/tracing_unknown_impl_test
> Failed on CassCI build trunk_dtest #1087
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (CASSANDRA-11465) dtest failure in cql_tracing_test.TestCqlTracing.tracing_unknown_impl_test
[
https://issues.apache.org/jira/browse/CASSANDRA-11465?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15384761#comment-15384761
]
Jim Witschey commented on CASSANDRA-11465:
--
I ran the following script:
{code}
for i in `seq 30` ; do
echo iteration $i
PRINT_DEBUG=true DEBUG=true
CASSANDRA_VERSION=github:stef1927/11465-cqlsh-3.9
TRACE=org.apache.cassandra.tracing.TraceStateImpl nosetests cql_tracing_test.py
killall -9 java
done
for i in `seq 30` ; do
echo iteration $i
PRINT_DEBUG=true DEBUG=true
CASSANDRA_VERSION=github:stef1927/11465-cqlsh
TRACE=org.apache.cassandra.tracing.TraceStateImpl nosetests cql_tracing_test.py
killall -9 java
done
{code}
and saw no failures:
https://gist.github.com/072692334800285afc8d362165cb37a6
> dtest failure in cql_tracing_test.TestCqlTracing.tracing_unknown_impl_test
> --
>
> Key: CASSANDRA-11465
> URL: https://issues.apache.org/jira/browse/CASSANDRA-11465
> Project: Cassandra
> Issue Type: Bug
>Reporter: Philip Thompson
>Assignee: Stefania
> Labels: dtest
>
> Failing on the following assert, on trunk only:
> {{self.assertEqual(len(errs[0]), 1)}}
> Is not failing consistently.
> example failure:
> http://cassci.datastax.com/job/trunk_dtest/1087/testReport/cql_tracing_test/TestCqlTracing/tracing_unknown_impl_test
> Failed on CassCI build trunk_dtest #1087
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (CASSANDRA-12162) dtest failure in repair_tests.repair_test.TestRepair.simple_sequential_repair_test
[
https://issues.apache.org/jira/browse/CASSANDRA-12162?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15384678#comment-15384678
]
Jim Witschey commented on CASSANDRA-12162:
--
Filed [PR 1110|https://github.com/riptano/cassandra-dtest/pull/1110] to attempt
to address this by increasing the number of retries during insertion.
> dtest failure in
> repair_tests.repair_test.TestRepair.simple_sequential_repair_test
> --
>
> Key: CASSANDRA-12162
> URL: https://issues.apache.org/jira/browse/CASSANDRA-12162
> Project: Cassandra
> Issue Type: Test
>Reporter: Sean McCarthy
>Assignee: DS Test Eng
> Labels: dtest
> Attachments: node1.log, node1_debug.log, node1_gc.log, node2.log,
> node2_debug.log, node2_gc.log, node3.log, node3_debug.log, node3_gc.log
>
>
> example failure:
> http://cassci.datastax.com/job/cassandra-2.2_dtest_win32/267/testReport/repair_tests.repair_test/TestRepair/simple_sequential_repair_test
> Failed on CassCI build cassandra-2.2_dtest_win32 #267
> {code}
> Stacktrace
> File "C:\tools\python2\lib\unittest\case.py", line 329, in run
> testMethod()
> File
> "D:\jenkins\workspace\cassandra-2.2_dtest_win32\cassandra-dtest\repair_tests\repair_test.py",
> line 241, in simple_sequential_repair_test
> self._simple_repair(sequential=True)
> File
> "D:\jenkins\workspace\cassandra-2.2_dtest_win32\cassandra-dtest\repair_tests\repair_test.py",
> line 295, in _simple_repair
> self._populate_cluster()
> File
> "D:\jenkins\workspace\cassandra-2.2_dtest_win32\cassandra-dtest\repair_tests\repair_test.py",
> line 98, in _populate_cluster
> insert_c1c2(session, n=1000, consistency=ConsistencyLevel.ALL)
> File
> "D:\jenkins\workspace\cassandra-2.2_dtest_win32\cassandra-dtest\tools.py",
> line 78, in insert_c1c2
> execute_concurrent_with_args(session, statement, [['k{}'.format(k)] for k
> in keys])
> File "cassandra\concurrent.py", line 224, in
> cassandra.concurrent.execute_concurrent_with_args
> (cassandra/concurrent.c:5996)
> return execute_concurrent(session, zip(cycle((statement,)), parameters),
> *args, **kwargs)
> File "cassandra\concurrent.py", line 92, in
> cassandra.concurrent.execute_concurrent (cassandra/concurrent.c:1455)
> return executor.execute(concurrency, raise_on_first_error)
> File "cassandra\concurrent.py", line 187, in
> cassandra.concurrent.ConcurrentExecutorListResults.execute
> (cassandra/concurrent.c:4824)
> return super(ConcurrentExecutorListResults, self).execute(concurrency,
> fail_fast)
> File "cassandra\concurrent.py", line 115, in
> cassandra.concurrent._ConcurrentExecutor.execute (cassandra/concurrent.c:2120)
> return self._results()
> File "cassandra\concurrent.py", line 201, in
> cassandra.concurrent.ConcurrentExecutorListResults._results
> (cassandra/concurrent.c:5617)
> with self._condition:
> File "cassandra\concurrent.py", line 205, in
> cassandra.concurrent.ConcurrentExecutorListResults._results
> (cassandra/concurrent.c:5549)
> self._raise(self._exception)
> File "cassandra\concurrent.py", line 153, in
> cassandra.concurrent._ConcurrentExecutor._raise (cassandra/concurrent.c:3498)
> raise exc
> 'Error from server: code=1500 [Replica(s) failed to execute write]
> message="Operation failed - received 2 responses and 1 failures"
> info={\'failures\': 1, \'received_responses\': 2, \'required_responses\': 3,
> \'consistency\': \'ALL\'}
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Comment Edited] (CASSANDRA-11687) dtest failure in rebuild_test.TestRebuild.simple_rebuild_test
[
https://issues.apache.org/jira/browse/CASSANDRA-11687?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15384487#comment-15384487
]
Jim Witschey edited comment on CASSANDRA-11687 at 7/19/16 4:55 PM:
---
That PR also improved error handling, and here's the error I get running
locally:
{code}
==
ERROR: rebuild_test.py:TestRebuild.simple_rebuild_test
--
Traceback (most recent call last):
File "/home/mambocab/cstar_src/cassandra-dtest/rebuild_test.py", line 96, in
simple_rebuild_test
rebuild()
File "/home/mambocab/cstar_src/cassandra-dtest/rebuild_test.py", line 88, in
rebuild
raise e
NodetoolError: Nodetool command
'/home/mambocab/.ccm/repository/gitCOLONtrunk/bin/nodetool -h localhost -p 7200
rebuild dc1' failed; exit status: 1; stdout: nodetool: Unable to find
sufficient sources for streaming range
(-3287869951390391138,-1624006824486474209] in keyspace system_auth with
RF=1.If you want to ignore this, consider using system property
-Dcassandra.consistent.rangemovement=false.
See 'nodetool help' or 'nodetool help '.
>> begin captured logging <<
ccm: INFO: Fetching Cassandra updates...
dtest: DEBUG: cluster ccm directory: /tmp/dtest-QDgw0_
ccm: INFO: Fetching Cassandra updates...
dtest: DEBUG: Done setting configuration options:
{ 'num_tokens': None, 'phi_convict_threshold': 5, 'start_rpc': 'true'}
cassandra.cluster: INFO: New Cassandra host discovered
cassandra.cluster: WARNING: Host 127.0.0.1 has been marked down
cassandra.pool: INFO: Successful reconnection to 127.0.0.1, marking node up if
it isn't already
cassandra.cluster: INFO: Host 127.0.0.1 may be up; will prepare queries and
open connection pool
cassandra.cluster: INFO: New Cassandra host discovered
- >> end captured logging << -
--
{code}
-So, looks like we're calling {{rebuild}} incorrectly.- This shouldn't fail
this way. The thing to do here, as the error says, may be to set
{{cassandra.consistent.rangemovement}} to {{false}}.
EDIT: for the record, this was the PR:
https://github.com/riptano/cassandra-dtest/pull/1106
was (Author: mambocab):
That PR also improved error handling, and here's the error I get running
locally:
{code}
==
ERROR: rebuild_test.py:TestRebuild.simple_rebuild_test
--
Traceback (most recent call last):
File "/home/mambocab/cstar_src/cassandra-dtest/rebuild_test.py", line 96, in
simple_rebuild_test
rebuild()
File "/home/mambocab/cstar_src/cassandra-dtest/rebuild_test.py", line 88, in
rebuild
raise e
NodetoolError: Nodetool command
'/home/mambocab/.ccm/repository/gitCOLONtrunk/bin/nodetool -h localhost -p 7200
rebuild dc1' failed; exit status: 1; stdout: nodetool: Unable to find
sufficient sources for streaming range
(-3287869951390391138,-1624006824486474209] in keyspace system_auth with
RF=1.If you want to ignore this, consider using system property
-Dcassandra.consistent.rangemovement=false.
See 'nodetool help' or 'nodetool help '.
>> begin captured logging <<
ccm: INFO: Fetching Cassandra updates...
dtest: DEBUG: cluster ccm directory: /tmp/dtest-QDgw0_
ccm: INFO: Fetching Cassandra updates...
dtest: DEBUG: Done setting configuration options:
{ 'num_tokens': None, 'phi_convict_threshold': 5, 'start_rpc': 'true'}
cassandra.cluster: INFO: New Cassandra host discovered
cassandra.cluster: WARNING: Host 127.0.0.1 has been marked down
cassandra.pool: INFO: Successful reconnection to 127.0.0.1, marking node up if
it isn't already
cassandra.cluster: INFO: Host 127.0.0.1 may be up; will prepare queries and
open connection pool
cassandra.cluster: INFO: New Cassandra host discovered
- >> end captured logging << -
--
{code}
So, looks like we're calling {{rebuild}} incorrectly.
EDIT: for the record, this was the PR:
https://github.com/riptano/cassandra-dtest/pull/1106
> dtest failure in rebuild_test.TestRebuild.simple_rebuild_test
> -
>
> Key: CASSANDRA-11687
> URL: https://issues.apache.org/jira/browse/CASSANDRA-11687
> Project: Cassandra
> Issue Type: Test
>Reporter: Russ Hatch
>Assignee: DS Test Eng
> Labels: dtest
>
> single failure on most recent run (3.0 no-vnode)
> {noformat}
> concurrent rebuild should not be allowed, but one rebuild command should have
>
[jira] [Comment Edited] (CASSANDRA-11687) dtest failure in rebuild_test.TestRebuild.simple_rebuild_test
[
https://issues.apache.org/jira/browse/CASSANDRA-11687?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15384487#comment-15384487
]
Jim Witschey edited comment on CASSANDRA-11687 at 7/19/16 4:50 PM:
---
That PR also improved error handling, and here's the error I get running
locally:
{code}
==
ERROR: rebuild_test.py:TestRebuild.simple_rebuild_test
--
Traceback (most recent call last):
File "/home/mambocab/cstar_src/cassandra-dtest/rebuild_test.py", line 96, in
simple_rebuild_test
rebuild()
File "/home/mambocab/cstar_src/cassandra-dtest/rebuild_test.py", line 88, in
rebuild
raise e
NodetoolError: Nodetool command
'/home/mambocab/.ccm/repository/gitCOLONtrunk/bin/nodetool -h localhost -p 7200
rebuild dc1' failed; exit status: 1; stdout: nodetool: Unable to find
sufficient sources for streaming range
(-3287869951390391138,-1624006824486474209] in keyspace system_auth with
RF=1.If you want to ignore this, consider using system property
-Dcassandra.consistent.rangemovement=false.
See 'nodetool help' or 'nodetool help '.
>> begin captured logging <<
ccm: INFO: Fetching Cassandra updates...
dtest: DEBUG: cluster ccm directory: /tmp/dtest-QDgw0_
ccm: INFO: Fetching Cassandra updates...
dtest: DEBUG: Done setting configuration options:
{ 'num_tokens': None, 'phi_convict_threshold': 5, 'start_rpc': 'true'}
cassandra.cluster: INFO: New Cassandra host discovered
cassandra.cluster: WARNING: Host 127.0.0.1 has been marked down
cassandra.pool: INFO: Successful reconnection to 127.0.0.1, marking node up if
it isn't already
cassandra.cluster: INFO: Host 127.0.0.1 may be up; will prepare queries and
open connection pool
cassandra.cluster: INFO: New Cassandra host discovered
- >> end captured logging << -
--
{code}
So, looks like we're calling {{rebuild}} incorrectly.
EDIT: for the record, this was the PR:
https://github.com/riptano/cassandra-dtest/pull/1106
was (Author: mambocab):
That PR also improved error handling, and here's the error I get running
locally:
{code}
==
ERROR: rebuild_test.py:TestRebuild.simple_rebuild_test
--
Traceback (most recent call last):
File "/home/mambocab/cstar_src/cassandra-dtest/rebuild_test.py", line 96, in
simple_rebuild_test
rebuild()
File "/home/mambocab/cstar_src/cassandra-dtest/rebuild_test.py", line 88, in
rebuild
raise e
NodetoolError: Nodetool command
'/home/mambocab/.ccm/repository/gitCOLONtrunk/bin/nodetool -h localhost -p 7200
rebuild dc1' failed; exit status: 1; stdout: nodetool: Unable to find
sufficient sources for streaming range
(-3287869951390391138,-1624006824486474209] in keyspace system_auth with
RF=1.If you want to ignore this, consider using system property
-Dcassandra.consistent.rangemovement=false.
See 'nodetool help' or 'nodetool help '.
>> begin captured logging <<
ccm: INFO: Fetching Cassandra updates...
dtest: DEBUG: cluster ccm directory: /tmp/dtest-QDgw0_
ccm: INFO: Fetching Cassandra updates...
dtest: DEBUG: Done setting configuration options:
{ 'num_tokens': None, 'phi_convict_threshold': 5, 'start_rpc': 'true'}
cassandra.cluster: INFO: New Cassandra host discovered
cassandra.cluster: WARNING: Host 127.0.0.1 has been marked down
cassandra.pool: INFO: Successful reconnection to 127.0.0.1, marking node up if
it isn't already
cassandra.cluster: INFO: Host 127.0.0.1 may be up; will prepare queries and
open connection pool
cassandra.cluster: INFO: New Cassandra host discovered
- >> end captured logging << -
--
{code}
So, looks like we're calling {{rebuild}} incorrectly.
> dtest failure in rebuild_test.TestRebuild.simple_rebuild_test
> -
>
> Key: CASSANDRA-11687
> URL: https://issues.apache.org/jira/browse/CASSANDRA-11687
> Project: Cassandra
> Issue Type: Test
>Reporter: Russ Hatch
>Assignee: DS Test Eng
> Labels: dtest
>
> single failure on most recent run (3.0 no-vnode)
> {noformat}
> concurrent rebuild should not be allowed, but one rebuild command should have
> succeeded.
> {noformat}
> http://cassci.datastax.com/job/cassandra-3.0_novnode_dtest/217/testReport/rebuild_test/TestRebuild/simple_rebuild_test
> Failed on CassCI build cassandra-3.0_novnode_dtest #217
--
This message was sent by
[jira] [Commented] (CASSANDRA-11687) dtest failure in rebuild_test.TestRebuild.simple_rebuild_test
[
https://issues.apache.org/jira/browse/CASSANDRA-11687?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15384487#comment-15384487
]
Jim Witschey commented on CASSANDRA-11687:
--
That PR also improved error handling, and here's the error I get running
locally:
{code}
==
ERROR: rebuild_test.py:TestRebuild.simple_rebuild_test
--
Traceback (most recent call last):
File "/home/mambocab/cstar_src/cassandra-dtest/rebuild_test.py", line 96, in
simple_rebuild_test
rebuild()
File "/home/mambocab/cstar_src/cassandra-dtest/rebuild_test.py", line 88, in
rebuild
raise e
NodetoolError: Nodetool command
'/home/mambocab/.ccm/repository/gitCOLONtrunk/bin/nodetool -h localhost -p 7200
rebuild dc1' failed; exit status: 1; stdout: nodetool: Unable to find
sufficient sources for streaming range
(-3287869951390391138,-1624006824486474209] in keyspace system_auth with
RF=1.If you want to ignore this, consider using system property
-Dcassandra.consistent.rangemovement=false.
See 'nodetool help' or 'nodetool help '.
>> begin captured logging <<
ccm: INFO: Fetching Cassandra updates...
dtest: DEBUG: cluster ccm directory: /tmp/dtest-QDgw0_
ccm: INFO: Fetching Cassandra updates...
dtest: DEBUG: Done setting configuration options:
{ 'num_tokens': None, 'phi_convict_threshold': 5, 'start_rpc': 'true'}
cassandra.cluster: INFO: New Cassandra host discovered
cassandra.cluster: WARNING: Host 127.0.0.1 has been marked down
cassandra.pool: INFO: Successful reconnection to 127.0.0.1, marking node up if
it isn't already
cassandra.cluster: INFO: Host 127.0.0.1 may be up; will prepare queries and
open connection pool
cassandra.cluster: INFO: New Cassandra host discovered
- >> end captured logging << -
--
{code}
So, looks like we're calling {{rebuild}} incorrectly.
> dtest failure in rebuild_test.TestRebuild.simple_rebuild_test
> -
>
> Key: CASSANDRA-11687
> URL: https://issues.apache.org/jira/browse/CASSANDRA-11687
> Project: Cassandra
> Issue Type: Test
>Reporter: Russ Hatch
>Assignee: DS Test Eng
> Labels: dtest
>
> single failure on most recent run (3.0 no-vnode)
> {noformat}
> concurrent rebuild should not be allowed, but one rebuild command should have
> succeeded.
> {noformat}
> http://cassci.datastax.com/job/cassandra-3.0_novnode_dtest/217/testReport/rebuild_test/TestRebuild/simple_rebuild_test
> Failed on CassCI build cassandra-3.0_novnode_dtest #217
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (CASSANDRA-11687) dtest failure in rebuild_test.TestRebuild.simple_rebuild_test
[
https://issues.apache.org/jira/browse/CASSANDRA-11687?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15382883#comment-15382883
]
Jim Witschey commented on CASSANDRA-11687:
--
I'm not sure it matters:
https://github.com/riptano/cassandra-dtest/blob/d2c93023ebe26a3aff98a85bd62deb96c9403c49/rebuild_test.py#L81-L97
It's going to be a failing {{nodetool}} call one way or the other. (Side note:
I'm making a PR to make the two error-handling cases use the same logic.)
> dtest failure in rebuild_test.TestRebuild.simple_rebuild_test
> -
>
> Key: CASSANDRA-11687
> URL: https://issues.apache.org/jira/browse/CASSANDRA-11687
> Project: Cassandra
> Issue Type: Test
>Reporter: Russ Hatch
>Assignee: DS Test Eng
> Labels: dtest
>
> single failure on most recent run (3.0 no-vnode)
> {noformat}
> concurrent rebuild should not be allowed, but one rebuild command should have
> succeeded.
> {noformat}
> http://cassci.datastax.com/job/cassandra-3.0_novnode_dtest/217/testReport/rebuild_test/TestRebuild/simple_rebuild_test
> Failed on CassCI build cassandra-3.0_novnode_dtest #217
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (CASSANDRA-12225) dtest failure in materialized_views_test.TestMaterializedViews.clustering_column_test
[
https://issues.apache.org/jira/browse/CASSANDRA-12225?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jim Witschey updated CASSANDRA-12225:
-
Fix Version/s: (was: 3.9)
> dtest failure in
> materialized_views_test.TestMaterializedViews.clustering_column_test
> -
>
> Key: CASSANDRA-12225
> URL: https://issues.apache.org/jira/browse/CASSANDRA-12225
> Project: Cassandra
> Issue Type: Test
>Reporter: Sean McCarthy
>Assignee: DS Test Eng
> Labels: dtest
> Attachments: node1.log, node1_debug.log, node1_gc.log, node2.log,
> node2_debug.log, node2_gc.log, node3.log, node3_debug.log, node3_gc.log
>
>
> example failure:
> http://cassci.datastax.com/job/trunk_offheap_dtest/336/testReport/materialized_views_test/TestMaterializedViews/clustering_column_test
> Failed on CassCI build trunk_offheap_dtest #336
> {code}
> Stacktrace
> File "/usr/lib/python2.7/unittest/case.py", line 329, in run
> testMethod()
> File "/home/automaton/cassandra-dtest/materialized_views_test.py", line
> 321, in clustering_column_test
> self.assertEqual(len(result), 2, "Expecting {} users, got {}".format(2,
> len(result)))
> File "/usr/lib/python2.7/unittest/case.py", line 513, in assertEqual
> assertion_func(first, second, msg=msg)
> File "/usr/lib/python2.7/unittest/case.py", line 506, in _baseAssertEqual
> raise self.failureException(msg)
> "Expecting 2 users, got 1
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (CASSANDRA-12124) dtest failure in upgrade_tests.cql_tests.TestCQLNodes2RF1_Upgrade_next_2_1_x_To_head_trunk.select_with_alias_test
[ https://issues.apache.org/jira/browse/CASSANDRA-12124?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jim Witschey updated CASSANDRA-12124: - Fix Version/s: (was: 3.9) > dtest failure in > upgrade_tests.cql_tests.TestCQLNodes2RF1_Upgrade_next_2_1_x_To_head_trunk.select_with_alias_test > - > > Key: CASSANDRA-12124 > URL: https://issues.apache.org/jira/browse/CASSANDRA-12124 > Project: Cassandra > Issue Type: Test >Reporter: Philip Thompson >Assignee: DS Test Eng > Labels: dtest > > example failure: > http://cassci.datastax.com/job/upgrade_tests-all-custom_branch_runs/37/testReport/upgrade_tests.cql_tests/TestCQLNodes2RF1_Upgrade_next_2_1_x_To_head_trunk/select_with_alias_test > Failed on CassCI build upgrade_tests-all-custom_branch_runs #37 > This is just a problem with different error messages across C* versions. > Someone needs to do the legwork of figuring out what is required where, and > filtering. The query is failing correctly. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CASSANDRA-12164) dtest failure in materialized_views_test.TestMaterializedViews.add_dc_after_mv_network_replication_test
[
https://issues.apache.org/jira/browse/CASSANDRA-12164?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jim Witschey updated CASSANDRA-12164:
-
Fix Version/s: (was: 3.9)
> dtest failure in
> materialized_views_test.TestMaterializedViews.add_dc_after_mv_network_replication_test
> ---
>
> Key: CASSANDRA-12164
> URL: https://issues.apache.org/jira/browse/CASSANDRA-12164
> Project: Cassandra
> Issue Type: Test
>Reporter: Sean McCarthy
>Assignee: DS Test Eng
> Labels: dtest
> Attachments: node1.log, node1_debug.log, node1_gc.log, node2.log,
> node2_debug.log, node2_gc.log, node3.log, node3_debug.log, node3_gc.log,
> node4.log, node4_debug.log, node4_gc.log, node5.log, node5_debug.log,
> node5_gc.log
>
>
> example failure:
> http://cassci.datastax.com/job/trunk_offheap_dtest/309/testReport/materialized_views_test/TestMaterializedViews/add_dc_after_mv_network_replication_test
> Failed on CassCI build trunk_offheap_dtest #309
> {code}
> Standard Output
> Unexpected error in node4 log, error:
> ERROR [main] 2016-07-06 19:21:26,631 MigrationManager.java:164 - Migration
> task failed to complete
> {code}
> Related failure:
> http://cassci.datastax.com/job/trunk_novnode_dtest/423/testReport/materialized_views_test/TestMaterializedViews/add_node_after_mv_test/
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (CASSANDRA-12225) dtest failure in materialized_views_test.TestMaterializedViews.clustering_column_test
[
https://issues.apache.org/jira/browse/CASSANDRA-12225?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jim Witschey updated CASSANDRA-12225:
-
Fix Version/s: 3.9
> dtest failure in
> materialized_views_test.TestMaterializedViews.clustering_column_test
> -
>
> Key: CASSANDRA-12225
> URL: https://issues.apache.org/jira/browse/CASSANDRA-12225
> Project: Cassandra
> Issue Type: Test
>Reporter: Sean McCarthy
>Assignee: DS Test Eng
> Labels: dtest
> Fix For: 3.9
>
> 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_offheap_dtest/336/testReport/materialized_views_test/TestMaterializedViews/clustering_column_test
> Failed on CassCI build trunk_offheap_dtest #336
> {code}
> Stacktrace
> File "/usr/lib/python2.7/unittest/case.py", line 329, in run
> testMethod()
> File "/home/automaton/cassandra-dtest/materialized_views_test.py", line
> 321, in clustering_column_test
> self.assertEqual(len(result), 2, "Expecting {} users, got {}".format(2,
> len(result)))
> File "/usr/lib/python2.7/unittest/case.py", line 513, in assertEqual
> assertion_func(first, second, msg=msg)
> File "/usr/lib/python2.7/unittest/case.py", line 506, in _baseAssertEqual
> raise self.failureException(msg)
> "Expecting 2 users, got 1
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (CASSANDRA-12164) dtest failure in materialized_views_test.TestMaterializedViews.add_dc_after_mv_network_replication_test
[
https://issues.apache.org/jira/browse/CASSANDRA-12164?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jim Witschey updated CASSANDRA-12164:
-
Fix Version/s: 3.9
> dtest failure in
> materialized_views_test.TestMaterializedViews.add_dc_after_mv_network_replication_test
> ---
>
> Key: CASSANDRA-12164
> URL: https://issues.apache.org/jira/browse/CASSANDRA-12164
> Project: Cassandra
> Issue Type: Test
>Reporter: Sean McCarthy
>Assignee: DS Test Eng
> Labels: dtest
> Fix For: 3.9
>
> 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
>
>
> example failure:
> http://cassci.datastax.com/job/trunk_offheap_dtest/309/testReport/materialized_views_test/TestMaterializedViews/add_dc_after_mv_network_replication_test
> Failed on CassCI build trunk_offheap_dtest #309
> {code}
> Standard Output
> Unexpected error in node4 log, error:
> ERROR [main] 2016-07-06 19:21:26,631 MigrationManager.java:164 - Migration
> task failed to complete
> {code}
> Related failure:
> http://cassci.datastax.com/job/trunk_novnode_dtest/423/testReport/materialized_views_test/TestMaterializedViews/add_node_after_mv_test/
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (CASSANDRA-11902) dtest failure in hintedhandoff_test.TestHintedHandoffConfig.hintedhandoff_dc_reenabled_test
[ https://issues.apache.org/jira/browse/CASSANDRA-11902?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15382672#comment-15382672 ] Jim Witschey commented on CASSANDRA-11902: -- I think I'd rather have a dev have a look. > dtest failure in > hintedhandoff_test.TestHintedHandoffConfig.hintedhandoff_dc_reenabled_test > --- > > Key: CASSANDRA-11902 > URL: https://issues.apache.org/jira/browse/CASSANDRA-11902 > Project: Cassandra > Issue Type: Test >Reporter: Philip Thompson >Assignee: DS Test Eng > Labels: dtest > Fix For: 3.9 > > Attachments: node1.log, node1_debug.log, node2.log, node2_debug.log > > > Failure occurred on trunk here: > http://cassci.datastax.com/job/trunk_dtest/1239/testReport/hintedhandoff_test/TestHintedHandoffConfig/hintedhandoff_dc_reenabled_test/ > Logs are attached > We re-enable HH on a DC, but we aren't seeing hints move in the logs, so this > does worry me a bit. I'm not sure quite how flaky it is. It's only failed > once. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CASSANDRA-11902) dtest failure in hintedhandoff_test.TestHintedHandoffConfig.hintedhandoff_dc_reenabled_test
[ https://issues.apache.org/jira/browse/CASSANDRA-11902?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jim Witschey updated CASSANDRA-11902: - Fix Version/s: 3.9 > dtest failure in > hintedhandoff_test.TestHintedHandoffConfig.hintedhandoff_dc_reenabled_test > --- > > Key: CASSANDRA-11902 > URL: https://issues.apache.org/jira/browse/CASSANDRA-11902 > Project: Cassandra > Issue Type: Test >Reporter: Philip Thompson >Assignee: DS Test Eng > Labels: dtest > Fix For: 3.9 > > Attachments: node1.log, node1_debug.log, node2.log, node2_debug.log > > > Failure occurred on trunk here: > http://cassci.datastax.com/job/trunk_dtest/1239/testReport/hintedhandoff_test/TestHintedHandoffConfig/hintedhandoff_dc_reenabled_test/ > Logs are attached > We re-enable HH on a DC, but we aren't seeing hints move in the logs, so this > does worry me a bit. I'm not sure quite how flaky it is. It's only failed > once. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CASSANDRA-11951) dtest failure in user_functions_test.TestUserFunctions.test_migration
[
https://issues.apache.org/jira/browse/CASSANDRA-11951?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jim Witschey updated CASSANDRA-11951:
-
Fix Version/s: 3.9
> dtest failure in user_functions_test.TestUserFunctions.test_migration
> -
>
> Key: CASSANDRA-11951
> URL: https://issues.apache.org/jira/browse/CASSANDRA-11951
> Project: Cassandra
> Issue Type: Test
>Reporter: Sean McCarthy
>Assignee: Philip Thompson
> Labels: dtest
> Fix For: 3.9
>
> Attachments: node1.log, node1_debug.log, node2.log, node2_debug.log,
> node3.log, node3_debug.log
>
>
> example failure:
> http://cassci.datastax.com/job/trunk_offheap_dtest/234/testReport/user_functions_test/TestUserFunctions/test_migration
> Failed on CassCI build trunk_offheap_dtest #234
> Logs are attached.
> {code}
> Stacktrace
> File "/usr/lib/python2.7/unittest/case.py", line 329, in run
> testMethod()
> File "/home/automaton/cassandra-dtest/user_functions_test.py", line 50, in
> test_migration
> session2.execute("use ks")
> File "cassandra/cluster.py", line 1706, in
> cassandra.cluster.Session.execute (cassandra/cluster.c:28532)
> return self.execute_async(query, parameters, trace, custom_payload,
> timeout).result()
> File "cassandra/cluster.py", line 3339, in
> cassandra.cluster.ResponseFuture.result (cassandra/cluster.c:62978)
> raise self._final_exception
> 'Error from server: code=2200 [Invalid query] message="Keyspace \'ks\' does
> not exist"\n >> begin captured logging <<
> \ndtest: DEBUG: cluster ccm directory:
> /mnt/tmp/dtest-1nvamN\ndtest: DEBUG: Custom init_config not found. Setting
> defaults.\ndtest: DEBUG: Done setting configuration options:\n{
> \'enable_scripted_user_defined_functions\': \'true\',\n
> \'enable_user_defined_functions\': \'true\',\n\'initial_token\': None,\n
> \'memtable_allocation_type\': \'offheap_objects\',\n\'num_tokens\':
> \'32\',\n\'phi_convict_threshold\': 5}\n- >> end
> captured logging << -'
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (CASSANDRA-12136) dtest failure in cqlsh_tests.cqlsh_copy_tests.CqlshCopyTest.test_round_trip_random
[
https://issues.apache.org/jira/browse/CASSANDRA-12136?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jim Witschey updated CASSANDRA-12136:
-
Fix Version/s: 3.9
> dtest failure in
> cqlsh_tests.cqlsh_copy_tests.CqlshCopyTest.test_round_trip_random
> --
>
> Key: CASSANDRA-12136
> URL: https://issues.apache.org/jira/browse/CASSANDRA-12136
> Project: Cassandra
> Issue Type: Test
>Reporter: Sean McCarthy
>Assignee: DS Test Eng
> Labels: dtest
> Fix For: 3.9
>
> 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.0_dtest/764/testReport/cqlsh_tests.cqlsh_copy_tests/CqlshCopyTest/test_round_trip_random
> {code}
> Stacktrace
> File "/usr/lib/python2.7/unittest/case.py", line 329, in run
> testMethod()
> File "/home/automaton/cassandra-dtest/dtest.py", line 928, in wrapped
> f(obj)
> File "/home/automaton/cassandra-dtest/cqlsh_tests/cqlsh_copy_tests.py",
> line 2334, in test_round_trip_random
> self._test_round_trip(nodes=3, partitioner="random")
> File "/home/automaton/cassandra-dtest/cqlsh_tests/cqlsh_copy_tests.py",
> line 2296, in _test_round_trip
> self.prepare(nodes=nodes, partitioner=partitioner)
> File "/home/automaton/cassandra-dtest/cqlsh_tests/cqlsh_copy_tests.py",
> line 109, in prepare
> self.cluster.populate(nodes,
> tokens=tokens).start(wait_for_binary_proto=True)
> File "/home/automaton/ccm/ccmlib/cluster.py", line 412, in start
> raise NodeError("Error starting {0}.".format(node.name), p)
> "Error starting node1.
> {code}
> Failed on CassCI build cassandra-3.0_dtest #764
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (CASSANDRA-11909) dtest failure in cql_tests.AbortedQueriesTester.remote_query_test
[
https://issues.apache.org/jira/browse/CASSANDRA-11909?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jim Witschey updated CASSANDRA-11909:
-
Fix Version/s: 3.9
> dtest failure in cql_tests.AbortedQueriesTester.remote_query_test
> -
>
> Key: CASSANDRA-11909
> URL: https://issues.apache.org/jira/browse/CASSANDRA-11909
> Project: Cassandra
> Issue Type: Test
>Reporter: Craig Kodman
>Assignee: DS Test Eng
> Labels: dtest
> Fix For: 3.9
>
>
> example failure:
> http://cassci.datastax.com/job/trunk_dtest/1243/testReport/cql_tests/AbortedQueriesTester/remote_query_test
> Failed on CassCI build trunk_dtest #1243
> {code}
> ERROR [SharedPool-Worker-1] 2016-05-27 10:08:49,471 Keyspace.java:504 -
> Attempting to mutate non-existant table 01855840-23f3-11e6-912e-c5dc3b68cc6d
> (ks.test2)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (CASSANDRA-12064) dtest failure in auth_test.TestAuth.login_test
[
https://issues.apache.org/jira/browse/CASSANDRA-12064?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jim Witschey updated CASSANDRA-12064:
-
Fix Version/s: 3.9
> dtest failure in auth_test.TestAuth.login_test
> --
>
> Key: CASSANDRA-12064
> URL: https://issues.apache.org/jira/browse/CASSANDRA-12064
> Project: Cassandra
> Issue Type: Test
>Reporter: Sean McCarthy
>Assignee: DS Test Eng
> Labels: dtest
> Fix For: 3.9
>
> Attachments: node1.log, node1_debug.log, node1_gc.log
>
>
> example failure:
> http://cassci.datastax.com/job/trunk_dtest/1284/testReport/auth_test/TestAuth/login_test
> Failed on CassCI build trunk_dtest #1284
> {code}
> Stacktrace
> File "/usr/lib/python2.7/unittest/case.py", line 329, in run
> testMethod()
> File "/home/automaton/cassandra-dtest/auth_test.py", line 82, in login_test
> assert isinstance(e.errors.values()[0], AuthenticationFailed)
> {code}
> Logs are attached.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (CASSANDRA-12124) dtest failure in upgrade_tests.cql_tests.TestCQLNodes2RF1_Upgrade_next_2_1_x_To_head_trunk.select_with_alias_test
[ https://issues.apache.org/jira/browse/CASSANDRA-12124?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jim Witschey updated CASSANDRA-12124: - Fix Version/s: 3.9 > dtest failure in > upgrade_tests.cql_tests.TestCQLNodes2RF1_Upgrade_next_2_1_x_To_head_trunk.select_with_alias_test > - > > Key: CASSANDRA-12124 > URL: https://issues.apache.org/jira/browse/CASSANDRA-12124 > Project: Cassandra > Issue Type: Test >Reporter: Philip Thompson >Assignee: DS Test Eng > Labels: dtest > Fix For: 3.9 > > > example failure: > http://cassci.datastax.com/job/upgrade_tests-all-custom_branch_runs/37/testReport/upgrade_tests.cql_tests/TestCQLNodes2RF1_Upgrade_next_2_1_x_To_head_trunk/select_with_alias_test > Failed on CassCI build upgrade_tests-all-custom_branch_runs #37 > This is just a problem with different error messages across C* versions. > Someone needs to do the legwork of figuring out what is required where, and > filtering. The query is failing correctly. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Comment Edited] (CASSANDRA-12099) dtest failure in snitch_test.TestGossipingPropertyFileSnitch.test_prefer_local_reconnect_on_listen_address
[
https://issues.apache.org/jira/browse/CASSANDRA-12099?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15380110#comment-15380110
]
Jim Witschey edited comment on CASSANDRA-12099 at 7/15/16 9:04 PM:
---
CASSANDRA-12072 has been closed. Should this be closed too, [~philipthompson]?
was (Author: mambocab):
CASSANDRA-12072 has been closed. Should this be [~philipthompson]?
> dtest failure in
> snitch_test.TestGossipingPropertyFileSnitch.test_prefer_local_reconnect_on_listen_address
> --
>
> Key: CASSANDRA-12099
> URL: https://issues.apache.org/jira/browse/CASSANDRA-12099
> Project: Cassandra
> Issue Type: Test
>Reporter: Sean McCarthy
>Assignee: DS Test Eng
> Labels: dtest
> Attachments: node1.log, node1_debug.log, node1_gc.log
>
>
> example failure:
> http://cassci.datastax.com/job/trunk_offheap_dtest/274/testReport/snitch_test/TestGossipingPropertyFileSnitch/test_prefer_local_reconnect_on_listen_address
> Failed on CassCI build trunk_offheap_dtest #274
> {code}
> Stacktrace
> File "/usr/lib/python2.7/unittest/case.py", line 358, in run
> self.tearDown()
> File "/home/automaton/cassandra-dtest/dtest.py", line 761, in tearDown
> ['\n'.join(msg) for msg in node.grep_log_for_errors()]))
> File "/home/automaton/ccm/ccmlib/node.py", line 357, in grep_log_for_errors
> return self.grep_log_for_errors_from(seek_start=getattr(self,
> 'error_mark', 0))
> File "/home/automaton/ccm/ccmlib/node.py", line 360, in
> grep_log_for_errors_from
> with open(os.path.join(self.get_path(), 'logs', filename)) as f:
> "[Errno 2] No such file or directory:
> '/mnt/tmp/dtest-Pa4WH7/test/node2/logs/system.log'
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (CASSANDRA-12099) dtest failure in snitch_test.TestGossipingPropertyFileSnitch.test_prefer_local_reconnect_on_listen_address
[
https://issues.apache.org/jira/browse/CASSANDRA-12099?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15380110#comment-15380110
]
Jim Witschey commented on CASSANDRA-12099:
--
CASSANDRA-12072 has been closed. Should this be [~philipthompson]?
> dtest failure in
> snitch_test.TestGossipingPropertyFileSnitch.test_prefer_local_reconnect_on_listen_address
> --
>
> Key: CASSANDRA-12099
> URL: https://issues.apache.org/jira/browse/CASSANDRA-12099
> Project: Cassandra
> Issue Type: Test
>Reporter: Sean McCarthy
>Assignee: DS Test Eng
> Labels: dtest
> Attachments: node1.log, node1_debug.log, node1_gc.log
>
>
> example failure:
> http://cassci.datastax.com/job/trunk_offheap_dtest/274/testReport/snitch_test/TestGossipingPropertyFileSnitch/test_prefer_local_reconnect_on_listen_address
> Failed on CassCI build trunk_offheap_dtest #274
> {code}
> Stacktrace
> File "/usr/lib/python2.7/unittest/case.py", line 358, in run
> self.tearDown()
> File "/home/automaton/cassandra-dtest/dtest.py", line 761, in tearDown
> ['\n'.join(msg) for msg in node.grep_log_for_errors()]))
> File "/home/automaton/ccm/ccmlib/node.py", line 357, in grep_log_for_errors
> return self.grep_log_for_errors_from(seek_start=getattr(self,
> 'error_mark', 0))
> File "/home/automaton/ccm/ccmlib/node.py", line 360, in
> grep_log_for_errors_from
> with open(os.path.join(self.get_path(), 'logs', filename)) as f:
> "[Errno 2] No such file or directory:
> '/mnt/tmp/dtest-Pa4WH7/test/node2/logs/system.log'
> {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=15380068#comment-15380068
]
Jim Witschey commented on CASSANDRA-12092:
--
It's important to note that this failed with the {{WRITE/READ/SERIAL}}
consistency set to {{THREE/ONE/-}}
{code}
Error Message
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]
>> begin captured logging <<
dtest: DEBUG: cluster ccm directory: /tmp/dtest-shYOzK
dtest: DEBUG: Custom init_config not found. Setting defaults.
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}
dtest: DEBUG: Testing single dc, counters
dtest: DEBUG: Changing snitch for single dc case
dtest: DEBUG: Testing accuracy with WRITE/READ/SERIAL consistency set to
ALL/ALL/- (keys : 0 to 49)
dtest: DEBUG: Testing accuracy with WRITE/READ/SERIAL consistency set to
QUORUM/QUORUM/- (keys : 50 to 99)
dtest: DEBUG: Testing accuracy with WRITE/READ/SERIAL consistency set to
ALL/ONE/- (keys : 100 to 149)
dtest: DEBUG: Testing accuracy with WRITE/READ/SERIAL consistency set to
ONE/ALL/- (keys : 150 to 199)
dtest: DEBUG: Testing accuracy with WRITE/READ/SERIAL consistency set to
QUORUM/ONE/- (keys : 200 to 249)
dtest: DEBUG: Testing accuracy with WRITE/READ/SERIAL consistency set to
ONE/QUORUM/- (keys : 250 to 299)
dtest: DEBUG: Waiting for workers to complete
dtest: DEBUG: Testing accuracy with WRITE/READ/SERIAL consistency set to
TWO/TWO/- (keys : 300 to 349)
dtest: DEBUG: Testing accuracy with WRITE/READ/SERIAL consistency set to
ONE/THREE/- (keys : 350 to 399)
dtest: DEBUG: Testing accuracy with WRITE/READ/SERIAL consistency set to
THREE/ONE/- (keys : 400 to 449)
dtest: DEBUG: Failed with exception : 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]
- >> end captured logging << -
{code}
> 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: DS Test Eng
> Labels: dtest
> Attachments: 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-11927) dtest failure in replication_test.ReplicationTest.simple_test
[
https://issues.apache.org/jira/browse/CASSANDRA-11927?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15379510#comment-15379510
]
Jim Witschey commented on CASSANDRA-11927:
--
The test asserts 20 times that a query hits the right nodes. In the test's
output, that assertion does actually run 20 times:
{code}
Unexpected error in log, see stdout
>> begin captured logging <<
dtest: DEBUG: cluster ccm directory: /mnt/tmp/dtest-c4_IWW
dtest: DEBUG: Custom init_config not found. Setting defaults.
dtest: DEBUG: Done setting configuration options:
{ 'num_tokens': None,
'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}
dtest: DEBUG:
replicas should be: set(['127.0.0.3', '127.0.0.2', '127.0.0.1'])
dtest: DEBUG: replicas were: set(['127.0.0.3', '127.0.0.2', '127.0.0.1'])
dtest: DEBUG:
replicas should be: set(['127.0.0.3', '127.0.0.2', '127.0.0.1'])
dtest: DEBUG: replicas were: set(['127.0.0.3', '127.0.0.2', '127.0.0.1'])
dtest: DEBUG:
replicas should be: set(['127.0.0.3', '127.0.0.2', '127.0.0.1'])
dtest: DEBUG: replicas were: set(['127.0.0.3', '127.0.0.2', '127.0.0.1'])
dtest: DEBUG:
replicas should be: set(['127.0.0.3', '127.0.0.2', '127.0.0.1'])
dtest: DEBUG: replicas were: set(['127.0.0.3', '127.0.0.2', '127.0.0.1'])
dtest: DEBUG:
replicas should be: set(['127.0.0.3', '127.0.0.2', '127.0.0.1'])
dtest: DEBUG: replicas were: set(['127.0.0.3', '127.0.0.2', '127.0.0.1'])
dtest: DEBUG:
replicas should be: set(['127.0.0.3', '127.0.0.2', '127.0.0.1'])
dtest: DEBUG: replicas were: set(['127.0.0.3', '127.0.0.2', '127.0.0.1'])
dtest: DEBUG:
replicas should be: set(['127.0.0.3', '127.0.0.2', '127.0.0.1'])
dtest: DEBUG: replicas were: set(['127.0.0.3', '127.0.0.2', '127.0.0.1'])
dtest: DEBUG:
replicas should be: set(['127.0.0.3', '127.0.0.2', '127.0.0.1'])
dtest: DEBUG: replicas were: set(['127.0.0.3', '127.0.0.2', '127.0.0.1'])
dtest: DEBUG:
replicas should be: set(['127.0.0.3', '127.0.0.2', '127.0.0.1'])
dtest: DEBUG: replicas were: set(['127.0.0.3', '127.0.0.2', '127.0.0.1'])
dtest: DEBUG:
replicas should be: set(['127.0.0.3', '127.0.0.2', '127.0.0.1'])
dtest: DEBUG: replicas were: set(['127.0.0.3', '127.0.0.2', '127.0.0.1'])
dtest: DEBUG:
replicas should be: set(['127.0.0.3', '127.0.0.2', '127.0.0.1'])
dtest: DEBUG: replicas were: set(['127.0.0.3', '127.0.0.2', '127.0.0.1'])
dtest: DEBUG:
replicas should be: set(['127.0.0.3', '127.0.0.2', '127.0.0.1'])
dtest: DEBUG: replicas were: set(['127.0.0.3', '127.0.0.2', '127.0.0.1'])
dtest: DEBUG:
replicas should be: set(['127.0.0.3', '127.0.0.2', '127.0.0.1'])
dtest: DEBUG: replicas were: set(['127.0.0.3', '127.0.0.2', '127.0.0.1'])
dtest: DEBUG:
replicas should be: set(['127.0.0.3', '127.0.0.2', '127.0.0.1'])
dtest: DEBUG: replicas were: set(['127.0.0.3', '127.0.0.2', '127.0.0.1'])
dtest: DEBUG:
replicas should be: set(['127.0.0.3', '127.0.0.2', '127.0.0.1'])
dtest: DEBUG: replicas were: set(['127.0.0.3', '127.0.0.2', '127.0.0.1'])
dtest: DEBUG:
replicas should be: set(['127.0.0.3', '127.0.0.2', '127.0.0.1'])
dtest: DEBUG: replicas were: set(['127.0.0.3', '127.0.0.2', '127.0.0.1'])
dtest: DEBUG:
replicas should be: set(['127.0.0.3', '127.0.0.2', '127.0.0.1'])
dtest: DEBUG: replicas were: set(['127.0.0.3', '127.0.0.2', '127.0.0.1'])
dtest: DEBUG:
replicas should be: set(['127.0.0.3', '127.0.0.2', '127.0.0.1'])
dtest: DEBUG: replicas were: set(['127.0.0.3', '127.0.0.2', '127.0.0.1'])
dtest: DEBUG:
replicas should be: set(['127.0.0.3', '127.0.0.2', '127.0.0.1'])
dtest: DEBUG: replicas were: set(['127.0.0.3', '127.0.0.2', '127.0.0.1'])
dtest: DEBUG:
replicas should be: set(['127.0.0.3', '127.0.0.2', '127.0.0.1'])
dtest: DEBUG: replicas were: set(['127.0.0.3', '127.0.0.2', '127.0.0.1'])
dtest: DEBUG: removing ccm cluster test at: /mnt/tmp/dtest-c4_IWW
dtest: DEBUG: clearing ssl stores from [/mnt/tmp/dtest-c4_IWW] directory
- >> end captured logging << -
{code}
So, the error found in the logs, presumably logged at table creation, didn't
break the behavior tested for here.
Marking as a bug and unassigning to add to dev queue.
> dtest failure in replication_test.ReplicationTest.simple_test
> -
>
> Key: CASSANDRA-11927
> URL: https://issues.apache.org/jira/browse/CASSANDRA-11927
> Project: Cassandra
> Issue Type: Test
>Reporter: Sean McCarthy
>Assignee: Jim Witschey
> Labels: dtest
> Attachments: node1.log, node1_debug.log, node2.log, node2_debug.log,
> node3.log, node3_debug.log
>
>
> example failure:
>
[jira] [Updated] (CASSANDRA-11927) dtest failure in replication_test.ReplicationTest.simple_test
[
https://issues.apache.org/jira/browse/CASSANDRA-11927?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jim Witschey updated CASSANDRA-11927:
-
Issue Type: Bug (was: Test)
> dtest failure in replication_test.ReplicationTest.simple_test
> -
>
> Key: CASSANDRA-11927
> URL: https://issues.apache.org/jira/browse/CASSANDRA-11927
> Project: Cassandra
> Issue Type: Bug
>Reporter: Sean McCarthy
>Assignee: Jim Witschey
> Labels: dtest
> Attachments: node1.log, node1_debug.log, node2.log, node2_debug.log,
> node3.log, node3_debug.log
>
>
> example failure:
> http://cassci.datastax.com/job/trunk_novnode_dtest/387/testReport/replication_test/ReplicationTest/simple_test
> Failed on CassCI build trunk_novnode_dtest #387
> Logs are attached.
> Unexpected error in question:
> {code}
> ERROR [SharedPool-Worker-1] 2016-05-30 16:00:17,211 Keyspace.java:504 -
> Attempting to mutate non-existant table 99f5be60-267f-11e6-ad5f-f13d771494ea
> (test.test)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (CASSANDRA-11927) dtest failure in replication_test.ReplicationTest.simple_test
[
https://issues.apache.org/jira/browse/CASSANDRA-11927?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jim Witschey updated CASSANDRA-11927:
-
Assignee: (was: Jim Witschey)
> dtest failure in replication_test.ReplicationTest.simple_test
> -
>
> Key: CASSANDRA-11927
> URL: https://issues.apache.org/jira/browse/CASSANDRA-11927
> Project: Cassandra
> Issue Type: Bug
>Reporter: Sean McCarthy
> Labels: dtest
> Attachments: node1.log, node1_debug.log, node2.log, node2_debug.log,
> node3.log, node3_debug.log
>
>
> example failure:
> http://cassci.datastax.com/job/trunk_novnode_dtest/387/testReport/replication_test/ReplicationTest/simple_test
> Failed on CassCI build trunk_novnode_dtest #387
> Logs are attached.
> Unexpected error in question:
> {code}
> ERROR [SharedPool-Worker-1] 2016-05-30 16:00:17,211 Keyspace.java:504 -
> Attempting to mutate non-existant table 99f5be60-267f-11e6-ad5f-f13d771494ea
> (test.test)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Comment Edited] (CASSANDRA-11927) dtest failure in replication_test.ReplicationTest.simple_test
[
https://issues.apache.org/jira/browse/CASSANDRA-11927?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15379390#comment-15379390
]
Jim Witschey edited comment on CASSANDRA-11927 at 7/15/16 1:50 PM:
---
This looks like a race between {{ColumnFamilyStore}} and {{Keyspace}}. From
{{node3_debug.log}}:
{code}
DEBUG [MigrationStage:1] 2016-05-30 16:00:17,191 Schema.java:465 - Adding
org.apache.cassandra.config.CFMetaData@81d417e[cfId=99f5be60-267f-11e6-ad5f-f13d771494ea,ksName=test,cfName=test,flags=[COMPOUND],params=TableParams{comment=,
read_repair_chance=0.0, dclocal_read_repair_chance=0.1,
bloom_filter_fp_chance=0.01, crc_check_chance=1.0, gc_grace_seconds=864000,
default_time_to_live=0, memtable_flush_period_in_ms=0, min_index_interval=128,
max_index_interval=2048, speculative_retry=99PERCENTILE, caching={'keys' :
'ALL', 'rows_per_partition' : 'NONE'},
compaction=CompactionParams{class=org.apache.cassandra.db.compaction.SizeTieredCompactionStrategy,
options={max_threshold=32, min_threshold=4}},
compression=org.apache.cassandra.schema.CompressionParams@4388edc3,
extensions={}},comparator=comparator(),partitionColumns=[[] |
[value]],partitionKeyColumns=[ColumnDefinition{name=id,
type=org.apache.cassandra.db.marshal.Int32Type, kind=PARTITION_KEY,
position=0}],clusteringColumns=[],keyValidator=org.apache.cassandra.db.marshal.Int32Type,columnMetadata=[ColumnDefinition{name=id,
type=org.apache.cassandra.db.marshal.Int32Type, kind=PARTITION_KEY,
position=0}, ColumnDefinition{name=value,
type=org.apache.cassandra.db.marshal.UTF8Type, kind=REGULAR,
position=-1}],droppedColumns={},triggers=[],indexes=[]] to cfIdMap
DEBUG [GossipStage:1] 2016-05-30 16:00:17,204 MigrationManager.java:94 - Not
pulling schema because versions match or shouldPullSchemaFrom returned false
INFO [MigrationStage:1] 2016-05-30 16:00:17,210 ColumnFamilyStore.java:405 -
Initializing test.test
ERROR [SharedPool-Worker-1] 2016-05-30 16:00:17,211 Keyspace.java:504 -
Attempting to mutate non-existant table 99f5be60-267f-11e6-ad5f-f13d771494ea
(test.test)
DEBUG [MigrationStage:1] 2016-05-30 16:00:17,297 MigrationManager.java:557 -
Gossiping my schema version a8612214-71b9-3e94-863e-04dd77cbbb88
{code}
was (Author: mambocab):
This looks like a race condition. From {{node3_debug.log}}:
{code}
DEBUG [MigrationStage:1] 2016-05-30 16:00:17,191 Schema.java:465 - Adding
org.apache.cassandra.config.CFMetaData@81d417e[cfId=99f5be60-267f-11e6-ad5f-f13d771494ea,ksName=test,cfName=test,flags=[COMPOUND],params=TableParams{comment=,
read_repair_chance=0.0, dclocal_read_repair_chance=0.1,
bloom_filter_fp_chance=0.01, crc_check_chance=1.0, gc_grace_seconds=864000,
default_time_to_live=0, memtable_flush_period_in_ms=0, min_index_interval=128,
max_index_interval=2048, speculative_retry=99PERCENTILE, caching={'keys' :
'ALL', 'rows_per_partition' : 'NONE'},
compaction=CompactionParams{class=org.apache.cassandra.db.compaction.SizeTieredCompactionStrategy,
options={max_threshold=32, min_threshold=4}},
compression=org.apache.cassandra.schema.CompressionParams@4388edc3,
extensions={}},comparator=comparator(),partitionColumns=[[] |
[value]],partitionKeyColumns=[ColumnDefinition{name=id,
type=org.apache.cassandra.db.marshal.Int32Type, kind=PARTITION_KEY,
position=0}],clusteringColumns=[],keyValidator=org.apache.cassandra.db.marshal.Int32Type,columnMetadata=[ColumnDefinition{name=id,
type=org.apache.cassandra.db.marshal.Int32Type, kind=PARTITION_KEY,
position=0}, ColumnDefinition{name=value,
type=org.apache.cassandra.db.marshal.UTF8Type, kind=REGULAR,
position=-1}],droppedColumns={},triggers=[],indexes=[]] to cfIdMap
DEBUG [GossipStage:1] 2016-05-30 16:00:17,204 MigrationManager.java:94 - Not
pulling schema because versions match or shouldPullSchemaFrom returned false
INFO [MigrationStage:1] 2016-05-30 16:00:17,210 ColumnFamilyStore.java:405 -
Initializing test.test
ERROR [SharedPool-Worker-1] 2016-05-30 16:00:17,211 Keyspace.java:504 -
Attempting to mutate non-existant table 99f5be60-267f-11e6-ad5f-f13d771494ea
(test.test)
DEBUG [MigrationStage:1] 2016-05-30 16:00:17,297 MigrationManager.java:557 -
Gossiping my schema version a8612214-71b9-3e94-863e-04dd77cbbb88
{code}
> dtest failure in replication_test.ReplicationTest.simple_test
> -
>
> Key: CASSANDRA-11927
> URL: https://issues.apache.org/jira/browse/CASSANDRA-11927
> Project: Cassandra
> Issue Type: Test
>Reporter: Sean McCarthy
>Assignee: Jim Witschey
> Labels: dtest
> Attachments: node1.log, node1_debug.log, node2.log, node2_debug.log,
> node3.log, node3_debug.log
>
>
> example failure:
> http://cassci.datastax.com/job/trunk_novnode_dtest/387/testReport/replication_test/ReplicationTest/simple_test
> Failed on CassCI
[jira] [Commented] (CASSANDRA-11927) dtest failure in replication_test.ReplicationTest.simple_test
[
https://issues.apache.org/jira/browse/CASSANDRA-11927?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15379390#comment-15379390
]
Jim Witschey commented on CASSANDRA-11927:
--
This looks like a race condition. From {{node3_debug.log}}:
{code}
DEBUG [MigrationStage:1] 2016-05-30 16:00:17,191 Schema.java:465 - Adding
org.apache.cassandra.config.CFMetaData@81d417e[cfId=99f5be60-267f-11e6-ad5f-f13d771494ea,ksName=test,cfName=test,flags=[COMPOUND],params=TableParams{comment=,
read_repair_chance=0.0, dclocal_read_repair_chance=0.1,
bloom_filter_fp_chance=0.01, crc_check_chance=1.0, gc_grace_seconds=864000,
default_time_to_live=0, memtable_flush_period_in_ms=0, min_index_interval=128,
max_index_interval=2048, speculative_retry=99PERCENTILE, caching={'keys' :
'ALL', 'rows_per_partition' : 'NONE'},
compaction=CompactionParams{class=org.apache.cassandra.db.compaction.SizeTieredCompactionStrategy,
options={max_threshold=32, min_threshold=4}},
compression=org.apache.cassandra.schema.CompressionParams@4388edc3,
extensions={}},comparator=comparator(),partitionColumns=[[] |
[value]],partitionKeyColumns=[ColumnDefinition{name=id,
type=org.apache.cassandra.db.marshal.Int32Type, kind=PARTITION_KEY,
position=0}],clusteringColumns=[],keyValidator=org.apache.cassandra.db.marshal.Int32Type,columnMetadata=[ColumnDefinition{name=id,
type=org.apache.cassandra.db.marshal.Int32Type, kind=PARTITION_KEY,
position=0}, ColumnDefinition{name=value,
type=org.apache.cassandra.db.marshal.UTF8Type, kind=REGULAR,
position=-1}],droppedColumns={},triggers=[],indexes=[]] to cfIdMap
DEBUG [GossipStage:1] 2016-05-30 16:00:17,204 MigrationManager.java:94 - Not
pulling schema because versions match or shouldPullSchemaFrom returned false
INFO [MigrationStage:1] 2016-05-30 16:00:17,210 ColumnFamilyStore.java:405 -
Initializing test.test
ERROR [SharedPool-Worker-1] 2016-05-30 16:00:17,211 Keyspace.java:504 -
Attempting to mutate non-existant table 99f5be60-267f-11e6-ad5f-f13d771494ea
(test.test)
DEBUG [MigrationStage:1] 2016-05-30 16:00:17,297 MigrationManager.java:557 -
Gossiping my schema version a8612214-71b9-3e94-863e-04dd77cbbb88
{code}
> dtest failure in replication_test.ReplicationTest.simple_test
> -
>
> Key: CASSANDRA-11927
> URL: https://issues.apache.org/jira/browse/CASSANDRA-11927
> Project: Cassandra
> Issue Type: Test
>Reporter: Sean McCarthy
>Assignee: Jim Witschey
> Labels: dtest
> Attachments: node1.log, node1_debug.log, node2.log, node2_debug.log,
> node3.log, node3_debug.log
>
>
> example failure:
> http://cassci.datastax.com/job/trunk_novnode_dtest/387/testReport/replication_test/ReplicationTest/simple_test
> Failed on CassCI build trunk_novnode_dtest #387
> Logs are attached.
> Unexpected error in question:
> {code}
> ERROR [SharedPool-Worker-1] 2016-05-30 16:00:17,211 Keyspace.java:504 -
> Attempting to mutate non-existant table 99f5be60-267f-11e6-ad5f-f13d771494ea
> (test.test)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Assigned] (CASSANDRA-11927) dtest failure in replication_test.ReplicationTest.simple_test
[
https://issues.apache.org/jira/browse/CASSANDRA-11927?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jim Witschey reassigned CASSANDRA-11927:
Assignee: Jim Witschey (was: DS Test Eng)
> dtest failure in replication_test.ReplicationTest.simple_test
> -
>
> Key: CASSANDRA-11927
> URL: https://issues.apache.org/jira/browse/CASSANDRA-11927
> Project: Cassandra
> Issue Type: Test
>Reporter: Sean McCarthy
>Assignee: Jim Witschey
> Labels: dtest
> Attachments: node1.log, node1_debug.log, node2.log, node2_debug.log,
> node3.log, node3_debug.log
>
>
> example failure:
> http://cassci.datastax.com/job/trunk_novnode_dtest/387/testReport/replication_test/ReplicationTest/simple_test
> Failed on CassCI build trunk_novnode_dtest #387
> Logs are attached.
> Unexpected error in question:
> {code}
> ERROR [SharedPool-Worker-1] 2016-05-30 16:00:17,211 Keyspace.java:504 -
> Attempting to mutate non-existant table 99f5be60-267f-11e6-ad5f-f13d771494ea
> (test.test)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
