[jira] [Commented] (CASSANDRA-11317) dtest failure in repair_tests.incremental_repair_test.TestIncRepair.sstable_repairedset_test
[
https://issues.apache.org/jira/browse/CASSANDRA-11317?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15210679#comment-15210679
]
Yuki Morishita commented on CASSANDRA-11317:
Yes, fix was accidental, but if tools are working, then I think we can close
this issue.
I believe adding {{Config.setClientMode}} will break some of standalone tools
[as I
stated|https://issues.apache.org/jira/browse/CASSANDRA-8616?focusedCommentId=15143867=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-15143867]
in CASSANDRA-8616.
I filed CASSANDRA-11191 for eliminating {{Config.setClientMode}} in the future.
> dtest failure in
> repair_tests.incremental_repair_test.TestIncRepair.sstable_repairedset_test
>
>
> Key: CASSANDRA-11317
> URL: https://issues.apache.org/jira/browse/CASSANDRA-11317
> Project: Cassandra
> Issue Type: Bug
>Reporter: Jim Witschey
>Assignee: Joel Knighton
> Labels: dtest
> Fix For: 2.2.x
>
>
> example failure:
> http://cassci.datastax.com/job/cassandra-2.2_dtest/536/testReport/repair_tests.incremental_repair_test/TestIncRepair/sstable_repairedset_test
> Here's the failure and stack trace:
> {code}
> [' 0']
> >> begin captured logging <<
> dtest: DEBUG: cluster ccm directory: /mnt/tmp/dtest-4WjpOf
> 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,
> 'start_rpc': 'true'}
> dtest: DEBUG: Repair timestamps are: [' 0', ' 0']
> - >> end captured logging << -
> 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 198, in sstable_repairedset_test
> self.assertGreaterEqual(len(uniquematches), 2, uniquematches)
> File "/usr/lib/python2.7/unittest/case.py", line 948, in assertGreaterEqual
> self.fail(self._formatMessage(msg, standardMsg))
> File "/usr/lib/python2.7/unittest/case.py", line 410, in fail
> raise self.failureException(msg)
> "[' 0']\n >> begin captured logging <<
> \ndtest: DEBUG: cluster ccm directory:
> /mnt/tmp/dtest-4WjpOf\ndtest: DEBUG: Custom init_config not found. Setting
> defaults.\ndtest: DEBUG: Done setting configuration options:\n{
> 'initial_token': None,\n'num_tokens': '32',\n'phi_convict_threshold':
> 5,\n'start_rpc': 'true'}\ndtest: DEBUG: Repair timestamps are: [' 0', '
> 0']\n- >> end captured logging << -"
> {code}
> This has failed in this way on CassCI build cassandra-2.2_dtest 536-9.
> [~philipthompson] Could you have a first look at this? You had a recent look
> at this test in CASSANDRA-11220.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (CASSANDRA-11317) dtest failure in repair_tests.incremental_repair_test.TestIncRepair.sstable_repairedset_test
[
https://issues.apache.org/jira/browse/CASSANDRA-11317?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15210570#comment-15210570
]
Joel Knighton commented on CASSANDRA-11317:
---
[~yukim] It looks like this was "solved" by the backport of [CASSANDRA-10679]
in [CASSANDRA-9598], since that put cassandra.yaml on the classpath so it can
be loaded by client tools now. Is that a good enough fix, or should we still
set Config.clientMode(true) for all the tools that explicitly init
DatabaseDescriptor after [CASSANDRA-10412]. (This includes
SSTableExpiredBlockers, SSTableExport, SSTableImport, SSTableLevelResetter,
SSTableMetadataViewer, SSTableOfflineRelevel, SSTableRepairedAtSetter,
StandaloneScrubber, StandaloneSplitter, StandaloneUpgrader, StandaloneVerifier).
It looks like at least some of these were failing in the same way before
[CASSANDRA-9598]. From my perspective (with limited experience here), it looks
like the fact that this was fixed was accidental, and we don't want the client
tools loading cassandra.yaml.
> dtest failure in
> repair_tests.incremental_repair_test.TestIncRepair.sstable_repairedset_test
>
>
> Key: CASSANDRA-11317
> URL: https://issues.apache.org/jira/browse/CASSANDRA-11317
> Project: Cassandra
> Issue Type: Bug
>Reporter: Jim Witschey
>Assignee: Joel Knighton
> Labels: dtest
> Fix For: 2.2.x
>
>
> example failure:
> http://cassci.datastax.com/job/cassandra-2.2_dtest/536/testReport/repair_tests.incremental_repair_test/TestIncRepair/sstable_repairedset_test
> Here's the failure and stack trace:
> {code}
> [' 0']
> >> begin captured logging <<
> dtest: DEBUG: cluster ccm directory: /mnt/tmp/dtest-4WjpOf
> 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,
> 'start_rpc': 'true'}
> dtest: DEBUG: Repair timestamps are: [' 0', ' 0']
> - >> end captured logging << -
> 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 198, in sstable_repairedset_test
> self.assertGreaterEqual(len(uniquematches), 2, uniquematches)
> File "/usr/lib/python2.7/unittest/case.py", line 948, in assertGreaterEqual
> self.fail(self._formatMessage(msg, standardMsg))
> File "/usr/lib/python2.7/unittest/case.py", line 410, in fail
> raise self.failureException(msg)
> "[' 0']\n >> begin captured logging <<
> \ndtest: DEBUG: cluster ccm directory:
> /mnt/tmp/dtest-4WjpOf\ndtest: DEBUG: Custom init_config not found. Setting
> defaults.\ndtest: DEBUG: Done setting configuration options:\n{
> 'initial_token': None,\n'num_tokens': '32',\n'phi_convict_threshold':
> 5,\n'start_rpc': 'true'}\ndtest: DEBUG: Repair timestamps are: [' 0', '
> 0']\n- >> end captured logging << -"
> {code}
> This has failed in this way on CassCI build cassandra-2.2_dtest 536-9.
> [~philipthompson] Could you have a first look at this? You had a recent look
> at this test in CASSANDRA-11220.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (CASSANDRA-11317) dtest failure in repair_tests.incremental_repair_test.TestIncRepair.sstable_repairedset_test
[
https://issues.apache.org/jira/browse/CASSANDRA-11317?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15204443#comment-15204443
]
Philip Thompson commented on CASSANDRA-11317:
-
Should this be set to Patch Available with [~jkni]'s patch?
> dtest failure in
> repair_tests.incremental_repair_test.TestIncRepair.sstable_repairedset_test
>
>
> Key: CASSANDRA-11317
> URL: https://issues.apache.org/jira/browse/CASSANDRA-11317
> Project: Cassandra
> Issue Type: Bug
>Reporter: Jim Witschey
> Labels: dtest
> Fix For: 2.2.x
>
>
> example failure:
> http://cassci.datastax.com/job/cassandra-2.2_dtest/536/testReport/repair_tests.incremental_repair_test/TestIncRepair/sstable_repairedset_test
> Here's the failure and stack trace:
> {code}
> [' 0']
> >> begin captured logging <<
> dtest: DEBUG: cluster ccm directory: /mnt/tmp/dtest-4WjpOf
> 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,
> 'start_rpc': 'true'}
> dtest: DEBUG: Repair timestamps are: [' 0', ' 0']
> - >> end captured logging << -
> 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 198, in sstable_repairedset_test
> self.assertGreaterEqual(len(uniquematches), 2, uniquematches)
> File "/usr/lib/python2.7/unittest/case.py", line 948, in assertGreaterEqual
> self.fail(self._formatMessage(msg, standardMsg))
> File "/usr/lib/python2.7/unittest/case.py", line 410, in fail
> raise self.failureException(msg)
> "[' 0']\n >> begin captured logging <<
> \ndtest: DEBUG: cluster ccm directory:
> /mnt/tmp/dtest-4WjpOf\ndtest: DEBUG: Custom init_config not found. Setting
> defaults.\ndtest: DEBUG: Done setting configuration options:\n{
> 'initial_token': None,\n'num_tokens': '32',\n'phi_convict_threshold':
> 5,\n'start_rpc': 'true'}\ndtest: DEBUG: Repair timestamps are: [' 0', '
> 0']\n- >> end captured logging << -"
> {code}
> This has failed in this way on CassCI build cassandra-2.2_dtest 536-9.
> [~philipthompson] Could you have a first look at this? You had a recent look
> at this test in CASSANDRA-11220.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (CASSANDRA-11317) dtest failure in repair_tests.incremental_repair_test.TestIncRepair.sstable_repairedset_test
[
https://issues.apache.org/jira/browse/CASSANDRA-11317?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15204449#comment-15204449
]
Joel Knighton commented on CASSANDRA-11317:
---
Not quite yet - [CASSANDRA-10412] made similar changes in a bunch of other
offline tools so I'd like to do a spot check that similar problems aren't
present elsewhere.
I'll assign to myself and submit a patch officially once I've checked the other
tools.
> dtest failure in
> repair_tests.incremental_repair_test.TestIncRepair.sstable_repairedset_test
>
>
> Key: CASSANDRA-11317
> URL: https://issues.apache.org/jira/browse/CASSANDRA-11317
> Project: Cassandra
> Issue Type: Bug
>Reporter: Jim Witschey
> Labels: dtest
> Fix For: 2.2.x
>
>
> example failure:
> http://cassci.datastax.com/job/cassandra-2.2_dtest/536/testReport/repair_tests.incremental_repair_test/TestIncRepair/sstable_repairedset_test
> Here's the failure and stack trace:
> {code}
> [' 0']
> >> begin captured logging <<
> dtest: DEBUG: cluster ccm directory: /mnt/tmp/dtest-4WjpOf
> 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,
> 'start_rpc': 'true'}
> dtest: DEBUG: Repair timestamps are: [' 0', ' 0']
> - >> end captured logging << -
> 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 198, in sstable_repairedset_test
> self.assertGreaterEqual(len(uniquematches), 2, uniquematches)
> File "/usr/lib/python2.7/unittest/case.py", line 948, in assertGreaterEqual
> self.fail(self._formatMessage(msg, standardMsg))
> File "/usr/lib/python2.7/unittest/case.py", line 410, in fail
> raise self.failureException(msg)
> "[' 0']\n >> begin captured logging <<
> \ndtest: DEBUG: cluster ccm directory:
> /mnt/tmp/dtest-4WjpOf\ndtest: DEBUG: Custom init_config not found. Setting
> defaults.\ndtest: DEBUG: Done setting configuration options:\n{
> 'initial_token': None,\n'num_tokens': '32',\n'phi_convict_threshold':
> 5,\n'start_rpc': 'true'}\ndtest: DEBUG: Repair timestamps are: [' 0', '
> 0']\n- >> end captured logging << -"
> {code}
> This has failed in this way on CassCI build cassandra-2.2_dtest 536-9.
> [~philipthompson] Could you have a first look at this? You had a recent look
> at this test in CASSANDRA-11220.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (CASSANDRA-11317) dtest failure in repair_tests.incremental_repair_test.TestIncRepair.sstable_repairedset_test
[
https://issues.apache.org/jira/browse/CASSANDRA-11317?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15187923#comment-15187923
]
Joel Knighton commented on CASSANDRA-11317:
---
Sure - I've pushed the change at
[11317-2.2|https://github.com/jkni/cassandra/tree/11317-2.2]. It is a one-liner
that sets clientMode to true.
Looking at the stack trace, it looks like this was probably broken by
[CASSANDRA-10412], which inits DatabaseDescriptor directly in many offline
tools.
> dtest failure in
> repair_tests.incremental_repair_test.TestIncRepair.sstable_repairedset_test
>
>
> Key: CASSANDRA-11317
> URL: https://issues.apache.org/jira/browse/CASSANDRA-11317
> Project: Cassandra
> Issue Type: Bug
>Reporter: Jim Witschey
> Labels: dtest
> Fix For: 2.2.x
>
>
> example failure:
> http://cassci.datastax.com/job/cassandra-2.2_dtest/536/testReport/repair_tests.incremental_repair_test/TestIncRepair/sstable_repairedset_test
> Here's the failure and stack trace:
> {code}
> [' 0']
> >> begin captured logging <<
> dtest: DEBUG: cluster ccm directory: /mnt/tmp/dtest-4WjpOf
> 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,
> 'start_rpc': 'true'}
> dtest: DEBUG: Repair timestamps are: [' 0', ' 0']
> - >> end captured logging << -
> 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 198, in sstable_repairedset_test
> self.assertGreaterEqual(len(uniquematches), 2, uniquematches)
> File "/usr/lib/python2.7/unittest/case.py", line 948, in assertGreaterEqual
> self.fail(self._formatMessage(msg, standardMsg))
> File "/usr/lib/python2.7/unittest/case.py", line 410, in fail
> raise self.failureException(msg)
> "[' 0']\n >> begin captured logging <<
> \ndtest: DEBUG: cluster ccm directory:
> /mnt/tmp/dtest-4WjpOf\ndtest: DEBUG: Custom init_config not found. Setting
> defaults.\ndtest: DEBUG: Done setting configuration options:\n{
> 'initial_token': None,\n'num_tokens': '32',\n'phi_convict_threshold':
> 5,\n'start_rpc': 'true'}\ndtest: DEBUG: Repair timestamps are: [' 0', '
> 0']\n- >> end captured logging << -"
> {code}
> This has failed in this way on CassCI build cassandra-2.2_dtest 536-9.
> [~philipthompson] Could you have a first look at this? You had a recent look
> at this test in CASSANDRA-11220.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (CASSANDRA-11317) dtest failure in repair_tests.incremental_repair_test.TestIncRepair.sstable_repairedset_test
[
https://issues.apache.org/jira/browse/CASSANDRA-11317?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15187873#comment-15187873
]
Yuki Morishita commented on CASSANDRA-11317:
CASSANDRA-10132 is caused by BufferPool introduced in CASSANDRA-8897, thus 3.0+.
[~jkni] would you mind sharing your fix here?
> dtest failure in
> repair_tests.incremental_repair_test.TestIncRepair.sstable_repairedset_test
>
>
> Key: CASSANDRA-11317
> URL: https://issues.apache.org/jira/browse/CASSANDRA-11317
> Project: Cassandra
> Issue Type: Bug
>Reporter: Jim Witschey
> Labels: dtest
> Fix For: 2.2.x
>
>
> example failure:
> http://cassci.datastax.com/job/cassandra-2.2_dtest/536/testReport/repair_tests.incremental_repair_test/TestIncRepair/sstable_repairedset_test
> Here's the failure and stack trace:
> {code}
> [' 0']
> >> begin captured logging <<
> dtest: DEBUG: cluster ccm directory: /mnt/tmp/dtest-4WjpOf
> 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,
> 'start_rpc': 'true'}
> dtest: DEBUG: Repair timestamps are: [' 0', ' 0']
> - >> end captured logging << -
> 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 198, in sstable_repairedset_test
> self.assertGreaterEqual(len(uniquematches), 2, uniquematches)
> File "/usr/lib/python2.7/unittest/case.py", line 948, in assertGreaterEqual
> self.fail(self._formatMessage(msg, standardMsg))
> File "/usr/lib/python2.7/unittest/case.py", line 410, in fail
> raise self.failureException(msg)
> "[' 0']\n >> begin captured logging <<
> \ndtest: DEBUG: cluster ccm directory:
> /mnt/tmp/dtest-4WjpOf\ndtest: DEBUG: Custom init_config not found. Setting
> defaults.\ndtest: DEBUG: Done setting configuration options:\n{
> 'initial_token': None,\n'num_tokens': '32',\n'phi_convict_threshold':
> 5,\n'start_rpc': 'true'}\ndtest: DEBUG: Repair timestamps are: [' 0', '
> 0']\n- >> end captured logging << -"
> {code}
> This has failed in this way on CassCI build cassandra-2.2_dtest 536-9.
> [~philipthompson] Could you have a first look at this? You had a recent look
> at this test in CASSANDRA-11220.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (CASSANDRA-11317) dtest failure in repair_tests.incremental_repair_test.TestIncRepair.sstable_repairedset_test
[
https://issues.apache.org/jira/browse/CASSANDRA-11317?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15187756#comment-15187756
]
Joel Knighton commented on CASSANDRA-11317:
---
It looks like this is because [CASSANDRA-10132] was only merged in 3.0+. Is
there a reason it wasn't included in 2.2 [~yukim]?
Backporting this fix looks like it fixes the test (in a few local test runs).
> dtest failure in
> repair_tests.incremental_repair_test.TestIncRepair.sstable_repairedset_test
>
>
> Key: CASSANDRA-11317
> URL: https://issues.apache.org/jira/browse/CASSANDRA-11317
> Project: Cassandra
> Issue Type: Bug
>Reporter: Jim Witschey
> Labels: dtest
> Fix For: 2.2.x
>
>
> example failure:
> http://cassci.datastax.com/job/cassandra-2.2_dtest/536/testReport/repair_tests.incremental_repair_test/TestIncRepair/sstable_repairedset_test
> Here's the failure and stack trace:
> {code}
> [' 0']
> >> begin captured logging <<
> dtest: DEBUG: cluster ccm directory: /mnt/tmp/dtest-4WjpOf
> 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,
> 'start_rpc': 'true'}
> dtest: DEBUG: Repair timestamps are: [' 0', ' 0']
> - >> end captured logging << -
> 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 198, in sstable_repairedset_test
> self.assertGreaterEqual(len(uniquematches), 2, uniquematches)
> File "/usr/lib/python2.7/unittest/case.py", line 948, in assertGreaterEqual
> self.fail(self._formatMessage(msg, standardMsg))
> File "/usr/lib/python2.7/unittest/case.py", line 410, in fail
> raise self.failureException(msg)
> "[' 0']\n >> begin captured logging <<
> \ndtest: DEBUG: cluster ccm directory:
> /mnt/tmp/dtest-4WjpOf\ndtest: DEBUG: Custom init_config not found. Setting
> defaults.\ndtest: DEBUG: Done setting configuration options:\n{
> 'initial_token': None,\n'num_tokens': '32',\n'phi_convict_threshold':
> 5,\n'start_rpc': 'true'}\ndtest: DEBUG: Repair timestamps are: [' 0', '
> 0']\n- >> end captured logging << -"
> {code}
> This has failed in this way on CassCI build cassandra-2.2_dtest 536-9.
> [~philipthompson] Could you have a first look at this? You had a recent look
> at this test in CASSANDRA-11220.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (CASSANDRA-11317) dtest failure in repair_tests.incremental_repair_test.TestIncRepair.sstable_repairedset_test
[
https://issues.apache.org/jira/browse/CASSANDRA-11317?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15185333#comment-15185333
]
Philip Thompson commented on CASSANDRA-11317:
-
I can't find any commits in the last six months that have caused this. The
change in behavior across versions makes me think this is a bug, since all CCM
is doing is shelling out to the tool.
> dtest failure in
> repair_tests.incremental_repair_test.TestIncRepair.sstable_repairedset_test
>
>
> Key: CASSANDRA-11317
> URL: https://issues.apache.org/jira/browse/CASSANDRA-11317
> Project: Cassandra
> Issue Type: Test
>Reporter: Jim Witschey
>Assignee: Philip Thompson
> Labels: dtest
>
> example failure:
> http://cassci.datastax.com/job/cassandra-2.2_dtest/536/testReport/repair_tests.incremental_repair_test/TestIncRepair/sstable_repairedset_test
> Here's the failure and stack trace:
> {code}
> [' 0']
> >> begin captured logging <<
> dtest: DEBUG: cluster ccm directory: /mnt/tmp/dtest-4WjpOf
> 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,
> 'start_rpc': 'true'}
> dtest: DEBUG: Repair timestamps are: [' 0', ' 0']
> - >> end captured logging << -
> 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 198, in sstable_repairedset_test
> self.assertGreaterEqual(len(uniquematches), 2, uniquematches)
> File "/usr/lib/python2.7/unittest/case.py", line 948, in assertGreaterEqual
> self.fail(self._formatMessage(msg, standardMsg))
> File "/usr/lib/python2.7/unittest/case.py", line 410, in fail
> raise self.failureException(msg)
> "[' 0']\n >> begin captured logging <<
> \ndtest: DEBUG: cluster ccm directory:
> /mnt/tmp/dtest-4WjpOf\ndtest: DEBUG: Custom init_config not found. Setting
> defaults.\ndtest: DEBUG: Done setting configuration options:\n{
> 'initial_token': None,\n'num_tokens': '32',\n'phi_convict_threshold':
> 5,\n'start_rpc': 'true'}\ndtest: DEBUG: Repair timestamps are: [' 0', '
> 0']\n- >> end captured logging << -"
> {code}
> This has failed in this way on CassCI build cassandra-2.2_dtest 536-9.
> [~philipthompson] Could you have a first look at this? You had a recent look
> at this test in CASSANDRA-11220.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (CASSANDRA-11317) dtest failure in repair_tests.incremental_repair_test.TestIncRepair.sstable_repairedset_test
[
https://issues.apache.org/jira/browse/CASSANDRA-11317?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15185320#comment-15185320
]
Philip Thompson commented on CASSANDRA-11317:
-
I see this exception on 2.2 when I run it locally:
{code}
Exception (org.apache.cassandra.exceptions.ConfigurationException) encountered
during startup: Expecting URI in variable: [cassandra.config]. Please prefix
the file with file:/// for local files or file:/// for remote files.
Aborting. If you are executing this from an external tool, it needs to set
Config.setClientMode(true) to avoid loading configuration.
org.apache.cassandra.exceptions.ConfigurationException: Expecting URI in
variable: [cassandra.config]. Please prefix the file with file:/// for local
files or file:/// for remote files. Aborting. If you are executing this
from an external tool, it needs to set Config.setClientMode(true) to avoid
loading configuration.
at
org.apache.cassandra.config.YamlConfigurationLoader.getStorageConfigURL(YamlConfigurationLoader.java:73)
at
org.apache.cassandra.config.YamlConfigurationLoader.loadConfig(YamlConfigurationLoader.java:85)
at
org.apache.cassandra.config.DatabaseDescriptor.loadConfig(DatabaseDescriptor.java:135)
at
org.apache.cassandra.config.DatabaseDescriptor.(DatabaseDescriptor.java:119)
at org.apache.cassandra.tools.Util.initDatabaseDescriptor(Util.java:38)
at
org.apache.cassandra.tools.SSTableRepairedAtSetter.main(SSTableRepairedAtSetter.java:66)
{code}
All other versions work fine, and the syntax for sstablerepairedset doesn't
appear to have changed in while, so this seems like a 2.2 bug. I'll try
bisecting.
> dtest failure in
> repair_tests.incremental_repair_test.TestIncRepair.sstable_repairedset_test
>
>
> Key: CASSANDRA-11317
> URL: https://issues.apache.org/jira/browse/CASSANDRA-11317
> Project: Cassandra
> Issue Type: Test
>Reporter: Jim Witschey
>Assignee: Philip Thompson
> Labels: dtest
>
> example failure:
> http://cassci.datastax.com/job/cassandra-2.2_dtest/536/testReport/repair_tests.incremental_repair_test/TestIncRepair/sstable_repairedset_test
> Here's the failure and stack trace:
> {code}
> [' 0']
> >> begin captured logging <<
> dtest: DEBUG: cluster ccm directory: /mnt/tmp/dtest-4WjpOf
> 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,
> 'start_rpc': 'true'}
> dtest: DEBUG: Repair timestamps are: [' 0', ' 0']
> - >> end captured logging << -
> 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 198, in sstable_repairedset_test
> self.assertGreaterEqual(len(uniquematches), 2, uniquematches)
> File "/usr/lib/python2.7/unittest/case.py", line 948, in assertGreaterEqual
> self.fail(self._formatMessage(msg, standardMsg))
> File "/usr/lib/python2.7/unittest/case.py", line 410, in fail
> raise self.failureException(msg)
> "[' 0']\n >> begin captured logging <<
> \ndtest: DEBUG: cluster ccm directory:
> /mnt/tmp/dtest-4WjpOf\ndtest: DEBUG: Custom init_config not found. Setting
> defaults.\ndtest: DEBUG: Done setting configuration options:\n{
> 'initial_token': None,\n'num_tokens': '32',\n'phi_convict_threshold':
> 5,\n'start_rpc': 'true'}\ndtest: DEBUG: Repair timestamps are: [' 0', '
> 0']\n- >> end captured logging << -"
> {code}
> This has failed in this way on CassCI build cassandra-2.2_dtest 536-9.
> [~philipthompson] Could you have a first look at this? You had a recent look
> at this test in CASSANDRA-11220.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
