[jira] [Commented] (CASSANDRA-12284) Cqlsh not supporting Copy command
[ https://issues.apache.org/jira/browse/CASSANDRA-12284?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15392060#comment-15392060 ] Michael Shuler commented on CASSANDRA-12284: The https://pypi.python.org/pypi/cqlsh latest version, 5.0.3, detail page shows: Author: Andrew Mussey Maintainer: Spiro Sideris Home Page: https://github.com/spiside/cqlsh Version 4.1.1 shows: Author: Andrew Mussey Home Page: https://github.com/amussey/cqlsh I would suggest opening a github issue for problems with pypi releases. Those releases are not done by the Apache Cassandra project. > Cqlsh not supporting Copy command > - > > Key: CASSANDRA-12284 > URL: https://issues.apache.org/jira/browse/CASSANDRA-12284 > Project: Cassandra > Issue Type: Bug > Components: CQL > Environment: Debian and OSX(yosemite) >Reporter: Abhinav Johri > Fix For: 3.3 > > > I installed cqlsh for my cassandra server using pip command. > I wanted to copy a table as CSV to my local system so I used COPY TO command > but it threw me the following error. > Traceback (most recent call last): > File "/usr/local/bin/cqlsh", line 1133, in onecmd > self.handle_statement(st, statementtext) > File "/usr/local/bin/cqlsh", line 1170, in handle_statement > return custom_handler(parsed) > File "/usr/local/bin/cqlsh", line 1837, in do_copy > rows = self.perform_csv_export(ks, cf, columns, fname, opts) > File "/usr/local/bin/cqlsh", line 1956, in perform_csv_export > csv_options, dialect_options, unrecognized_options = > copyutil.parse_options(self, opts) > AttributeError: 'module' object has no attribute 'parse_options' -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (CASSANDRA-12284) Cqlsh not supporting Copy command
[ https://issues.apache.org/jira/browse/CASSANDRA-12284?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Shuler resolved CASSANDRA-12284. Resolution: Invalid > Cqlsh not supporting Copy command > - > > Key: CASSANDRA-12284 > URL: https://issues.apache.org/jira/browse/CASSANDRA-12284 > Project: Cassandra > Issue Type: Bug > Components: CQL > Environment: Debian and OSX(yosemite) >Reporter: Abhinav Johri > Fix For: 3.3 > > > I installed cqlsh for my cassandra server using pip command. > I wanted to copy a table as CSV to my local system so I used COPY TO command > but it threw me the following error. > Traceback (most recent call last): > File "/usr/local/bin/cqlsh", line 1133, in onecmd > self.handle_statement(st, statementtext) > File "/usr/local/bin/cqlsh", line 1170, in handle_statement > return custom_handler(parsed) > File "/usr/local/bin/cqlsh", line 1837, in do_copy > rows = self.perform_csv_export(ks, cf, columns, fname, opts) > File "/usr/local/bin/cqlsh", line 1956, in perform_csv_export > csv_options, dialect_options, unrecognized_options = > copyutil.parse_options(self, opts) > AttributeError: 'module' object has no attribute 'parse_options' -- 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=15389636#comment-15389636 ] Michael Shuler commented on CASSANDRA-11895: Thanks for finding where this is, I was going a little mad. :) I would think this qualifies as non-critical and we know this test works as expected in 2.2+, so I'd be supportive of just skipping this test in 2.1. > 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] [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=15388365#comment-15388365
]
Michael Shuler commented on CASSANDRA-11895:
I added this to {{dtest.py}} and it still failed on 2.1:
{noformat}
(11895-cqlsh-utf8)mshuler@hana:~/git/cassandra-dtest$ git diff master
diff --git a/dtest.py b/dtest.py
index b8a339e..47f968b 100644
--- a/dtest.py
+++ b/dtest.py
@@ -90,6 +90,10 @@ if os.environ.get('DISABLE_VNODES', '').lower() in ('yes',
'true'):
CURRENT_TEST = ""
+# set default encoding for all tests - CASSANDRA-11895
+reload(sys)
+sys.setdefaultencoding('utf-8')
+
logging.basicConfig(filename=os.path.join(LOG_SAVED_DIR, "dtest.log"),
filemode='w',
format='%(asctime)s,%(msecs)d %(name)s %(current_test)s
%(levelname)s %(message)s',
{noformat}
This test passes on 2.2+ for me without the above, so I'm not sure what's
different about 2.1 that throws this error, regardless of what we've tried so
far:
{noformat}
test_unicode_invalid_request_error (cqlsh_tests.cqlsh_tests.TestCqlsh) ... FAIL
==
FAIL: test_unicode_invalid_request_error (cqlsh_tests.cqlsh_tests.TestCqlsh)
--
Traceback (most recent call last):
File "/home/automaton/cassandra-dtest/cqlsh_tests/cqlsh_tests.py", line 483,
in test_unicode_invalid_request_error
self.assertIn(u'"รค" is not a valid keyspace name', err)
AssertionError: u'"\xe4" is not a valid keyspace name' not found in
u":2:'ascii' codec can't encode character u'\\xe4' in position 36:
ordinal not in range(128)\n"
>> begin captured logging <<
dtest: DEBUG: cluster ccm directory: /tmp/dtest-xcod69
dtest: DEBUG: Done setting configuration options:
{ 'initial_token': None,
'num_tokens': '32',
'phi_convict_threshold': 5,
'range_request_timeout_in_ms': 1,
'read_request_timeout_in_ms': 1,
'request_timeout_in_ms': 1,
'truncate_request_timeout_in_ms': 1,
'write_request_timeout_in_ms': 1}
- >> end captured logging << -
--
Ran 1 test in 7.761s
{noformat}
> 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] [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=15387916#comment-15387916 ] Michael Shuler commented on CASSANDRA-11895: I can try it out! > 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: DS Test Eng > 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] [Assigned] (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:all-tabpanel ] Michael Shuler reassigned CASSANDRA-11895: -- Assignee: Michael Shuler (was: DS Test Eng) > 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] [Commented] (CASSANDRA-12249) dtest failure in upgrade_tests.paging_test.TestPagingDataNodes3RF3_Upgrade_current_3_0_x_To_indev_3_x.basic_paging_test
[
https://issues.apache.org/jira/browse/CASSANDRA-12249?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15386193#comment-15386193
]
Michael Shuler commented on CASSANDRA-12249:
I believe this is a dupe of CASSANDRA-12236, or at least depends on it being
fixed, from the full node2_debug.log error:
{noformat}
INFO [SharedPool-Worker-1] 2016-07-20 04:50:56,533 Gossiper.java:994 -
InetAddress /127.0.0.1 is now UP
DEBUG [SharedPool-Worker-1] 2016-07-20 04:50:56,534 MigrationManager.java:101 -
Submitting migration task for /127.0.0.1
ERROR [MessagingService-Incoming-/127.0.0.1] 2016-07-20 04:50:56,568
CassandraDaemon.java:201 - Exception in thread
Thread[MessagingService-Incoming-/127.0.0.1,5,main]
java.lang.RuntimeException: Unknown column cdc during deserialization
at
org.apache.cassandra.db.Columns$Serializer.deserialize(Columns.java:432)
~[apache-cassandra-3.0.8.jar:3.0.8]
at
org.apache.cassandra.db.SerializationHeader$Serializer.deserializeForMessaging(SerializationHeader.java:427)
~[apache-cassandra-3.0.8.jar:3.0.8]
at
org.apache.cassandra.db.rows.UnfilteredRowIteratorSerializer.deserializeHeader(UnfilteredRowIteratorSerializer.java:190)
~[apache-cassandra-3.0.8.jar:3.0.8]
at
org.apache.cassandra.db.partitions.PartitionUpdate$PartitionUpdateSerializer.deserialize30(PartitionUpdate.java:657)
~[apache-cassandra-3.0.8.jar:3.0.8]
at
org.apache.cassandra.db.partitions.PartitionUpdate$PartitionUpdateSerializer.deserialize(PartitionUpdate.java:645)
~[apache-cassandra-3.0.8.jar:3.0.8]
at
org.apache.cassandra.db.Mutation$MutationSerializer.deserialize(Mutation.java:344)
~[apache-cassandra-3.0.8.jar:3.0.8]
at
org.apache.cassandra.db.Mutation$MutationSerializer.deserialize(Mutation.java:353)
~[apache-cassandra-3.0.8.jar:3.0.8]
at
org.apache.cassandra.service.MigrationManager$MigrationsSerializer.deserialize(MigrationManager.java:609)
~[apache-cassandra-3.0.8.jar:3.0.8]
at
org.apache.cassandra.service.MigrationManager$MigrationsSerializer.deserialize(MigrationManager.java:592)
~[apache-cassandra-3.0.8.jar:3.0.8]
at org.apache.cassandra.net.MessageIn.read(MessageIn.java:98)
~[apache-cassandra-3.0.8.jar:3.0.8]
at
org.apache.cassandra.net.IncomingTcpConnection.receiveMessage(IncomingTcpConnection.java:201)
~[apache-cassandra-3.0.8.jar:3.0.8]
at
org.apache.cassandra.net.IncomingTcpConnection.receiveMessages(IncomingTcpConnection.java:178)
~[apache-cassandra-3.0.8.jar:3.0.8]
at
org.apache.cassandra.net.IncomingTcpConnection.run(IncomingTcpConnection.java:92)
~[apache-cassandra-3.0.8.jar:3.0.8]
ERROR [MessagingService-Incoming-/127.0.0.1] 2016-07-20 04:50:56,623
CassandraDaemon.java:201 - Exception in thread
Thread[MessagingService-Incoming-/127.0.0.1,5,main]
java.lang.RuntimeException: Unknown column cdc during deserialization
at
org.apache.cassandra.db.Columns$Serializer.deserialize(Columns.java:432)
~[apache-cassandra-3.0.8.jar:3.0.8]
at
org.apache.cassandra.db.SerializationHeader$Serializer.deserializeForMessaging(SerializationHeader.java:427)
~[apache-cassandra-3.0.8.jar:3.0.8]
at
org.apache.cassandra.db.rows.UnfilteredRowIteratorSerializer.deserializeHeader(UnfilteredRowIteratorSerializer.java:190)
~[apache-cassandra-3.0.8.jar:3.0.8]
at
org.apache.cassandra.db.partitions.PartitionUpdate$PartitionUpdateSerializer.deserialize30(PartitionUpdate.java:657)
~[apache-cassandra-3.0.8.jar:3.0.8]
at
org.apache.cassandra.db.partitions.PartitionUpdate$PartitionUpdateSerializer.deserialize(PartitionUpdate.java:645)
~[apache-cassandra-3.0.8.jar:3.0.8]
at
org.apache.cassandra.db.Mutation$MutationSerializer.deserialize(Mutation.java:344)
~[apache-cassandra-3.0.8.jar:3.0.8]
at
org.apache.cassandra.db.Mutation$MutationSerializer.deserialize(Mutation.java:353)
~[apache-cassandra-3.0.8.jar:3.0.8]
at
org.apache.cassandra.service.MigrationManager$MigrationsSerializer.deserialize(MigrationManager.java:609)
~[apache-cassandra-3.0.8.jar:3.0.8]
at
org.apache.cassandra.service.MigrationManager$MigrationsSerializer.deserialize(MigrationManager.java:592)
~[apache-cassandra-3.0.8.jar:3.0.8]
at org.apache.cassandra.net.MessageIn.read(MessageIn.java:98)
~[apache-cassandra-3.0.8.jar:3.0.8]
at
org.apache.cassandra.net.IncomingTcpConnection.receiveMessage(IncomingTcpConnection.java:201)
~[apache-cassandra-3.0.8.jar:3.0.8]
at
org.apache.cassandra.net.IncomingTcpConnection.receiveMessages(IncomingTcpConnection.java:178)
~[apache-cassandra-3.0.8.jar:3.0.8]
at
org.apache.cassandra.net.IncomingTcpConnection.run(IncomingTcpConnection.java:92)
~[apache-cassandra-3.0.8.jar:3.0.8]
DEBUG [GossipStage:1] 2016-07-20 04:50:57,474 MigrationManager.java:101 -
Submitting migration task for /127.0.0.1
ERROR
[jira] [Created] (CASSANDRA-12239) Add mshuler's key FE4B2BDA to dist/cassandra/KEYS
Michael Shuler created CASSANDRA-12239:
--
Summary: Add mshuler's key FE4B2BDA to dist/cassandra/KEYS
Key: CASSANDRA-12239
URL: https://issues.apache.org/jira/browse/CASSANDRA-12239
Project: Cassandra
Issue Type: Task
Components: Packaging
Reporter: Michael Shuler
Assignee: Michael Shuler
Fix For: 3.x
Attachments: KEYS+mshuler.diff.txt
I've started working on packaging with the 3.8 release and signed the staging
artifacts with FE4B2BDA. This key will need to be added for the debian
repository signature to function correctly, if it's released as-is, or perhaps
[~tjake] will need to re-sign the release. Users will need to also fetch this
new key and add to {{apt-key}}.
{{KEYS}} patch attached.
Assigned to myself, but I am not sure exactly where {{KEYS}} lives - in svn
somewhere or a direct upload? :)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (CASSANDRA-9754) Make index info heap friendly for large CQL partitions
[ https://issues.apache.org/jira/browse/CASSANDRA-9754?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Shuler updated CASSANDRA-9754: -- Tester: (was: Michael Shuler) > Make index info heap friendly for large CQL partitions > -- > > Key: CASSANDRA-9754 > URL: https://issues.apache.org/jira/browse/CASSANDRA-9754 > Project: Cassandra > Issue Type: Improvement >Reporter: sankalp kohli >Assignee: Michael Kjellman >Priority: Minor > Fix For: 4.x > > Attachments: 9754_part1-v1.diff, 9754_part2-v1.diff > > > Looking at a heap dump of 2.0 cluster, I found that majority of the objects > are IndexInfo and its ByteBuffers. This is specially bad in endpoints with > large CQL partitions. If a CQL partition is say 6,4GB, it will have 100K > IndexInfo objects and 200K ByteBuffers. This will create a lot of churn for > GC. Can this be improved by not creating so many objects? -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CASSANDRA-9754) Make index info heap friendly for large CQL partitions
[ https://issues.apache.org/jira/browse/CASSANDRA-9754?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Shuler updated CASSANDRA-9754: -- Tester: Michael Shuler > Make index info heap friendly for large CQL partitions > -- > > Key: CASSANDRA-9754 > URL: https://issues.apache.org/jira/browse/CASSANDRA-9754 > Project: Cassandra > Issue Type: Improvement >Reporter: sankalp kohli >Assignee: Michael Kjellman >Priority: Minor > Fix For: 4.x > > Attachments: 9754_part1-v1.diff, 9754_part2-v1.diff > > > Looking at a heap dump of 2.0 cluster, I found that majority of the objects > are IndexInfo and its ByteBuffers. This is specially bad in endpoints with > large CQL partitions. If a CQL partition is say 6,4GB, it will have 100K > IndexInfo objects and 200K ByteBuffers. This will create a lot of churn for > GC. Can this be improved by not creating so many objects? -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CASSANDRA-12170) Create ci job to run ant test-cdc weekly
[ https://issues.apache.org/jira/browse/CASSANDRA-12170?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15371356#comment-15371356 ] Michael Shuler commented on CASSANDRA-12170: This is running on ASF's Jenkins. https://builds.apache.org/view/A-D/view/Cassandra/job/Cassandra-test-cdc/ > Create ci job to run ant test-cdc weekly > > > Key: CASSANDRA-12170 > URL: https://issues.apache.org/jira/browse/CASSANDRA-12170 > Project: Cassandra > Issue Type: Test >Reporter: Joshua McKenzie >Assignee: Michael Shuler >Priority: Minor > > With CASSANDRA-8844, we added a new ant target 'test-cdc'. This exercises all > unit tests w/a CDC-enabled CommitLogSegmentManager. We need a CI job to run > this weekly and catch any potential regressions in functionality. > Should be able to copy from 'testall' on trunk and just change the target. > Only needed on trunk. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (CASSANDRA-12170) Create ci job to run ant test-cdc weekly
[ https://issues.apache.org/jira/browse/CASSANDRA-12170?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Shuler resolved CASSANDRA-12170. Resolution: Done > Create ci job to run ant test-cdc weekly > > > Key: CASSANDRA-12170 > URL: https://issues.apache.org/jira/browse/CASSANDRA-12170 > Project: Cassandra > Issue Type: Test >Reporter: Joshua McKenzie >Assignee: Michael Shuler >Priority: Minor > > With CASSANDRA-8844, we added a new ant target 'test-cdc'. This exercises all > unit tests w/a CDC-enabled CommitLogSegmentManager. We need a CI job to run > this weekly and catch any potential regressions in functionality. > Should be able to copy from 'testall' on trunk and just change the target. > Only needed on trunk. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CASSANDRA-8876) Allow easier init script reuse
[ https://issues.apache.org/jira/browse/CASSANDRA-8876?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Shuler updated CASSANDRA-8876: -- Status: Testing (was: Patch Available) > Allow easier init script reuse > -- > > Key: CASSANDRA-8876 > URL: https://issues.apache.org/jira/browse/CASSANDRA-8876 > Project: Cassandra > Issue Type: Improvement > Components: Packaging >Reporter: Marko Asplund >Assignee: Michael Shuler > Fix For: 3.x > > Attachments: trunk-CASSANDRA-8876.txt > > > Make it possible to reuse the Cassandra debian init script with different > configuration and Cassandra home paths by making paths configurable via > environment variables set in /etc/default/cassandra. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (CASSANDRA-7961) Run dtests on ARM
[ https://issues.apache.org/jira/browse/CASSANDRA-7961?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Shuler resolved CASSANDRA-7961. --- Resolution: Later Closing this out as Later to clean up queue. It's interesting, but I don't think I've seen any ARM users. > Run dtests on ARM > - > > Key: CASSANDRA-7961 > URL: https://issues.apache.org/jira/browse/CASSANDRA-7961 > Project: Cassandra > Issue Type: Test >Reporter: Ryan McGuire >Assignee: Michael Shuler >Priority: Minor > > It looks pretty easy to setup an [emulated ARM > environment|https://wiki.ubuntu.com/ARM/RootfsFromScratch/QemuDebootstrap], > we might want to look into setting this up on Cassci. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CASSANDRA-9320) test-burn target should be run occasionally
[ https://issues.apache.org/jira/browse/CASSANDRA-9320?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15371028#comment-15371028 ] Michael Shuler commented on CASSANDRA-9320: --- Been attempting this on ASF's Jenkins https://builds.apache.org/view/A-D/view/Cassandra/job/Cassandra-test-burn/ > test-burn target should be run occasionally > --- > > Key: CASSANDRA-9320 > URL: https://issues.apache.org/jira/browse/CASSANDRA-9320 > Project: Cassandra > Issue Type: Test >Reporter: Ariel Weisberg >Assignee: Michael Shuler >Priority: Minor > Fix For: 3.x > > > The tests are all concurrency tests right now so they need to run on the > largest # of cores we have available. The tests are not configured to run > very long right now, but the intent is that they run for longer periods (days > even). > They aren't described as high value right now because the code under test > hasn't change since first introduced so we can defer setting this job up > until higher priority things are done. > I think we should still run them at some low frequency so they don't rot or > some change doesn't sneak in that effects them. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CASSANDRA-12129) deb Packages cannot be installed under Ubuntu 16.04 (xenial) due to missing dependency
[
https://issues.apache.org/jira/browse/CASSANDRA-12129?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15368023#comment-15368023
]
Michael Shuler commented on CASSANDRA-12129:
Just a little further help - the dependencies for python-support are minimal.
{{apt-get install}} those deps, if needed. Here's where you can grab the
latest Ubuntu release of python-support, if you need to install an older
version of Cassandra on Ubuntu 16.04:
http://packages.ubuntu.com/wily/python-support
> deb Packages cannot be installed under Ubuntu 16.04 (xenial) due to missing
> dependency
> --
>
> Key: CASSANDRA-12129
> URL: https://issues.apache.org/jira/browse/CASSANDRA-12129
> Project: Cassandra
> Issue Type: Bug
> Components: Packaging
> Environment: Ubuntu 16.04 (Xenial)
>Reporter: Stuart Bishop
>Assignee: Michael Shuler
> Fix For: 2.1.15, 2.2.7, 3.0.6, 3.6
>
>
> The deb packages depend on python-support, which no longer exists in Ubuntu
> 16.04 (xenial).
> $ sudo apt install cassandra
> Reading package lists... Done
> Building dependency tree
> Reading state information... Done
> Some packages could not be installed. This may mean that you have
> requested an impossible situation or if you are using the unstable
> distribution that some required packages have not yet been created
> or been moved out of Incoming.
> The following information may help to resolve the situation:
> The following packages have unmet dependencies:
> cassandra : Depends: python-support (>= 0.90.0) but it is not installable
> Recommends: ntp but it is not going to be installed or
> time-daemon
> E: Unable to correct problems, you have held broken packages.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Resolved] (CASSANDRA-12129) deb Packages cannot be installed under Ubuntu 16.04 (xenial) due to missing dependency
[ https://issues.apache.org/jira/browse/CASSANDRA-12129?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Shuler resolved CASSANDRA-12129. Resolution: Not A Problem Fix Version/s: 2.1.15 2.2.7 3.0.6 3.6 > deb Packages cannot be installed under Ubuntu 16.04 (xenial) due to missing > dependency > -- > > Key: CASSANDRA-12129 > URL: https://issues.apache.org/jira/browse/CASSANDRA-12129 > Project: Cassandra > Issue Type: Bug > Components: Packaging > Environment: Ubuntu 16.04 (Xenial) >Reporter: Stuart Bishop >Assignee: Michael Shuler > Fix For: 3.6, 3.0.6, 2.2.7, 2.1.15 > > > The deb packages depend on python-support, which no longer exists in Ubuntu > 16.04 (xenial). > $ sudo apt install cassandra > Reading package lists... Done > Building dependency tree > Reading state information... Done > Some packages could not be installed. This may mean that you have > requested an impossible situation or if you are using the unstable > distribution that some required packages have not yet been created > or been moved out of Incoming. > The following information may help to resolve the situation: > The following packages have unmet dependencies: > cassandra : Depends: python-support (>= 0.90.0) but it is not installable > Recommends: ntp but it is not going to be installed or > time-daemon > E: Unable to correct problems, you have held broken packages. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CASSANDRA-12129) deb Packages cannot be installed under Ubuntu 16.04 (xenial) due to missing dependency
[ https://issues.apache.org/jira/browse/CASSANDRA-12129?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15367992#comment-15367992 ] Michael Shuler commented on CASSANDRA-12129: CASSANDRA-10853 migration from python-support to dh_python2 was fixed for: Fix Version/s: 2.1.15, 2.2.7, 3.0.6, 3.6 You didn't mention what version you were attempting to install, but the ones above should work fine on Ubuntu 16.04. Older Cassandra debs than above will indeed have this problem, but it's possible to also probably grab python-support (and deps) from a previous Ubuntu release, if you must. Please, reopen this ticket and let us know if the above versions or greater don't install cleanly! > deb Packages cannot be installed under Ubuntu 16.04 (xenial) due to missing > dependency > -- > > Key: CASSANDRA-12129 > URL: https://issues.apache.org/jira/browse/CASSANDRA-12129 > Project: Cassandra > Issue Type: Bug > Components: Packaging > Environment: Ubuntu 16.04 (Xenial) >Reporter: Stuart Bishop >Assignee: Michael Shuler > > The deb packages depend on python-support, which no longer exists in Ubuntu > 16.04 (xenial). > $ sudo apt install cassandra > Reading package lists... Done > Building dependency tree > Reading state information... Done > Some packages could not be installed. This may mean that you have > requested an impossible situation or if you are using the unstable > distribution that some required packages have not yet been created > or been moved out of Incoming. > The following information may help to resolve the situation: > The following packages have unmet dependencies: > cassandra : Depends: python-support (>= 0.90.0) but it is not installable > Recommends: ntp but it is not going to be installed or > time-daemon > E: Unable to correct problems, you have held broken packages. -- 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=15367753#comment-15367753
]
Michael Shuler commented on CASSANDRA-11895:
http://stackoverflow.com/a/31137935/3033735
Suggests:
{noformat}
import sys
reload(sys)
sys.setdefaultencoding('utf-8')
{noformat}
I do not find any setdefaultencoding() in dtest - should we do this?
> 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: DS Test Eng
> 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] [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=15367745#comment-15367745
]
Michael Shuler commented on CASSANDRA-11895:
This test still failed when swapping around how/when the
{{PYTHONIOENCODING=utf-8}} env var is set. Not sure what else we might try to
correct this..
https://cassci.datastax.com/job/cassandra-2.1_dtest/493/testReport/cqlsh_tests.cqlsh_tests/TestCqlsh/test_unicode_invalid_request_error/
> 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: DS Test Eng
> 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-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=15366747#comment-15366747
]
Michael Shuler edited comment on CASSANDRA-11895 at 7/7/16 9:07 PM:
We've already been setting {{PYTHONIOENCODING=utf-8}} in dtest run environments
since CASSANDRA-11799. I switched the cassandra-2.1_dtest to use a straight
{{export}} when nosetests is run, instead of from a system-wide profile
configuration, so we'll see if this test passes with that(?). This should make
no difference at all, but we'll see.
https://cassci.datastax.com/job/cassandra-2.1_dtest/493/
was (Author: mshuler):
We've already been setting {{PYTHONIOENCODING=utf=8}} in dtest run environments
since CASSANDRA-11799. I switched the cassandra-2.1_dtest to use a straight
{{export}} when nosetests is run, instead of from a system-wide profile
configuration, so we'll see if this test passes with that(?). This should make
no difference at all, but we'll see.
https://cassci.datastax.com/job/cassandra-2.1_dtest/493/
> 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: DS Test Eng
> 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-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=15366747#comment-15366747
]
Michael Shuler edited comment on CASSANDRA-11895 at 7/7/16 9:07 PM:
We've already been setting {{PYTHONIOENCODING=utf=8}} in dtest run environments
since CASSANDRA-11799. I switched the cassandra-2.1_dtest to use a straight
{{export}} when nosetests is run, instead of from a system-wide profile
configuration, so we'll see if this test passes with that(?). This should make
no difference at all, but we'll see.
https://cassci.datastax.com/job/cassandra-2.1_dtest/493/
was (Author: mshuler):
We're already been setting {{PYTHONIOENCODING=utf=8}} in dtest run environments
since CASSANDRA-11799. I switched the cassandra-2.1_dtest to use a straight
{{export}} when nosetests is run, instead of from a system-wide profile
configuration, so we'll see if this test passes with that(?). This should make
no difference at all, but we'll see.
https://cassci.datastax.com/job/cassandra-2.1_dtest/493/
> 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: DS Test Eng
> 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] [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=15366747#comment-15366747
]
Michael Shuler commented on CASSANDRA-11895:
We're already been setting {{PYTHONIOENCODING=utf=8}} in dtest run environments
since CASSANDRA-11799. I switched the cassandra-2.1_dtest to use a straight
{{export}} when nosetests is run, instead of from a system-wide profile
configuration, so we'll see if this test passes with that(?). This should make
no difference at all, but we'll see.
https://cassci.datastax.com/job/cassandra-2.1_dtest/493/
> 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: DS Test Eng
> 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] [Commented] (CASSANDRA-12135) dtest failure in repair_tests.incremental_repair_test.TestIncRepair.sstable_marking_test
[
https://issues.apache.org/jira/browse/CASSANDRA-12135?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15364640#comment-15364640
]
Michael Shuler commented on CASSANDRA-12135:
Not sure, but I can't rule it out.
> dtest failure in
> repair_tests.incremental_repair_test.TestIncRepair.sstable_marking_test
>
>
> Key: CASSANDRA-12135
> URL: https://issues.apache.org/jira/browse/CASSANDRA-12135
> 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_jdk8/240/testReport/repair_tests.incremental_repair_test/TestIncRepair/sstable_marking_test
> Failed on CassCI build cassandra-2.1_dtest_jdk8 #240
> {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 42, in sstable_marking_test
> node3.stop(gently=True)
> File "/home/automaton/ccm/ccmlib/node.py", line 701, in stop
> raise NodeError("Problem stopping node %s" % self.name)
> "Problem stopping node node3
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (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:comment-tabpanel=15364398#comment-15364398
]
Michael Shuler commented on CASSANDRA-12136:
{{openstack-cassci-external-df85c4d-jenkins-cassandra-3}} has to be the missing
hostname configuration somewhere - I'm not certain where this name comes from,
but must be auto-generated by openstack and must not be resolvable.
> 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
> 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] [Commented] (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:comment-tabpanel=15364390#comment-15364390
]
Michael Shuler commented on CASSANDRA-12136:
I worry any time a server does not know its own name :) I believe this is a
configuration error with the test server, something along the lines of
{{/etc/hosts}} missing a critical entry like {{127.0.0.1 localhost}} or there
is an incorrect entry.
> 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
> 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] [Commented] (CASSANDRA-8876) Allow easier init script reuse
[ https://issues.apache.org/jira/browse/CASSANDRA-8876?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15351718#comment-15351718 ] Michael Shuler commented on CASSANDRA-8876: --- Thanks for the patch. I'll test out how this works for default installs and see how it goes. > Allow easier init script reuse > -- > > Key: CASSANDRA-8876 > URL: https://issues.apache.org/jira/browse/CASSANDRA-8876 > Project: Cassandra > Issue Type: Improvement > Components: Packaging >Reporter: Marko Asplund >Assignee: Michael Shuler > Fix For: 3.x > > Attachments: trunk-CASSANDRA-8876.txt > > > Make it possible to reuse the Cassandra debian init script with different > configuration and Cassandra home paths by making paths configurable via > environment variables set in /etc/default/cassandra. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (CASSANDRA-8876) Allow easier init script reuse
[ https://issues.apache.org/jira/browse/CASSANDRA-8876?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Shuler reassigned CASSANDRA-8876: - Assignee: Michael Shuler > Allow easier init script reuse > -- > > Key: CASSANDRA-8876 > URL: https://issues.apache.org/jira/browse/CASSANDRA-8876 > Project: Cassandra > Issue Type: Improvement > Components: Packaging >Reporter: Marko Asplund >Assignee: Michael Shuler > Fix For: 3.x > > Attachments: trunk-CASSANDRA-8876.txt > > > Make it possible to reuse the Cassandra debian init script with different > configuration and Cassandra home paths by making paths configurable via > environment variables set in /etc/default/cassandra. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CASSANDRA-11661) Cassandra 2.0 and later require Java 7u25 or later - jdk 101
[ https://issues.apache.org/jira/browse/CASSANDRA-11661?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15300269#comment-15300269 ] Michael Shuler commented on CASSANDRA-11661: I pinged the devs on your 2.1.15 release question, [~hessu]. Thanks! > Cassandra 2.0 and later require Java 7u25 or later - jdk 101 > > > Key: CASSANDRA-11661 > URL: https://issues.apache.org/jira/browse/CASSANDRA-11661 > Project: Cassandra > Issue Type: Bug > Components: Testing > Environment: Cassandra Server 2.1.5 and Java jdk1.7.0_101-b14 >Reporter: William Boutin >Assignee: Eduard Tudenhoefner >Priority: Critical > Fix For: 2.1.15, 2.2.7, 3.7, 3.0.7 > > Attachments: 11661-2.1.patch, 11661-2.2.patch, 11661-3.0.patch > > > We have been running the cassandr server version 2.1.5. Friday, we applied > the latest java patch, Java(TM) SE Runtime Environment (build 1.7.0_101-b14). > Cassandra cannot start with this patch. The cassandra log states: Cassandra > 2.0 and later require Java 7u25 or later. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (CASSANDRA-11799) dtest failure in cqlsh_tests.cqlsh_tests.TestCqlsh.test_unicode_syntax_error
[
https://issues.apache.org/jira/browse/CASSANDRA-11799?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Shuler resolved CASSANDRA-11799.
Resolution: Fixed
Fix Version/s: (was: 3.0.x)
(was: 2.2.x)
(was: 3.x)
3.0.7
2.2.7
3.6
> dtest failure in cqlsh_tests.cqlsh_tests.TestCqlsh.test_unicode_syntax_error
>
>
> Key: CASSANDRA-11799
> URL: https://issues.apache.org/jira/browse/CASSANDRA-11799
> Project: Cassandra
> Issue Type: Test
>Reporter: Philip Thompson
>Assignee: Tyler Hobbs
> Labels: cqlsh, dtest
> Fix For: 3.6, 2.2.7, 3.0.7
>
>
> example failure:
> http://cassci.datastax.com/job/cassandra-3.0_dtest/703/testReport/cqlsh_tests.cqlsh_tests/TestCqlsh/test_unicode_syntax_error
> Failed on CassCI build cassandra-3.0_dtest #703
> Also failing is
> cqlsh_tests.cqlsh_tests.TestCqlsh.test_unicode_invalid_request_error
> The relevant failure is
> {code}
> 'ascii' codec can't encode character u'\xe4' in position 12: ordinal not in
> range(128)
> {code}
> These are failing on 2.2, 3.0 and trunk.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (CASSANDRA-11799) dtest failure in cqlsh_tests.cqlsh_tests.TestCqlsh.test_unicode_syntax_error
[
https://issues.apache.org/jira/browse/CASSANDRA-11799?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15298421#comment-15298421
]
Michael Shuler commented on CASSANDRA-11799:
Templates all updated to include {{PYTHONIOENCODING='utf-8'}} and I'll commit
the removal of the known_failure in dtest shortly.
> dtest failure in cqlsh_tests.cqlsh_tests.TestCqlsh.test_unicode_syntax_error
>
>
> Key: CASSANDRA-11799
> URL: https://issues.apache.org/jira/browse/CASSANDRA-11799
> Project: Cassandra
> Issue Type: Test
>Reporter: Philip Thompson
>Assignee: Tyler Hobbs
> Labels: cqlsh, dtest
> Fix For: 2.2.x, 3.0.x, 3.x
>
>
> example failure:
> http://cassci.datastax.com/job/cassandra-3.0_dtest/703/testReport/cqlsh_tests.cqlsh_tests/TestCqlsh/test_unicode_syntax_error
> Failed on CassCI build cassandra-3.0_dtest #703
> Also failing is
> cqlsh_tests.cqlsh_tests.TestCqlsh.test_unicode_invalid_request_error
> The relevant failure is
> {code}
> 'ascii' codec can't encode character u'\xe4' in position 12: ordinal not in
> range(128)
> {code}
> These are failing on 2.2, 3.0 and trunk.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (CASSANDRA-11799) dtest failure in cqlsh_tests.cqlsh_tests.TestCqlsh.test_unicode_syntax_error
[
https://issues.apache.org/jira/browse/CASSANDRA-11799?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15294133#comment-15294133
]
Michael Shuler commented on CASSANDRA-11799:
We finally figured out how to reproduce this. When using {{--with-xunit}} and
we {{| tee -a logfile}}, this is when we expose the problem.
All looks fine locally:
{noformat}
$ nosetests --with-xunit -vs
cqlsh_tests/cqlsh_tests.py:TestCqlsh.test_unicode_invalid_request_error
cqlsh_tests/cqlsh_tests.py:TestCqlsh.test_unicode_syntax_error
test_unicode_invalid_request_error (cqlsh_tests.cqlsh_tests.TestCqlsh) ... (EE)
:2:InvalidRequest: code=2200 [Invalid query] message=""รค" is not a
valid keyspace name"(EE) ok
test_unicode_syntax_error (cqlsh_tests.cqlsh_tests.TestCqlsh) ... (EE)
:2:Invalid syntax at char 1(EE) :2: รค;(EE) :2: ^(EE)
ok
--
XML: /home/mshuler/git/cassandra-dtest/nosetests.xml
--
Ran 2 tests in 24.650s
OK
{noformat}
Pipe to tee and we repro the problem in CI:
{noformat}
$ nosetests --with-xunit -vs
cqlsh_tests/cqlsh_tests.py:TestCqlsh.test_unicode_invalid_request_error
cqlsh_tests/cqlsh_tests.py:TestCqlsh.test_unicode_syntax_error | tee -a logfile
test_unicode_invalid_request_error (cqlsh_tests.cqlsh_tests.TestCqlsh) ... (EE)
ERROR
test_unicode_syntax_error (cqlsh_tests.cqlsh_tests.TestCqlsh) ... (EE)
:2:Invalid syntax at char 1(EE) ERROR
==
ERROR: test_unicode_invalid_request_error (cqlsh_tests.cqlsh_tests.TestCqlsh)
--
Traceback (most recent call last):
File "/home/mshuler/git/cassandra-dtest/cqlsh_tests/cqlsh_tests.py", line
476, in test_unicode_invalid_request_error
output, err = node1.run_cqlsh(cmds=cmd, return_output=True)
File "/home/mshuler/git/ccm/ccmlib/node.py", line 816, in run_cqlsh
print_("(EE) ", err, end='')
File "/usr/lib/python2.7/dist-packages/nose/plugins/xunit.py", line 126, in
write
s.write(data)
File "/usr/lib/python2.7/dist-packages/nose/plugins/xunit.py", line 126, in
write
s.write(data)
File "/usr/lib/python2.7/dist-packages/nose/plugins/xunit.py", line 126, in
write
s.write(data)
File "/usr/lib/python2.7/dist-packages/nose/plugins/xunit.py", line 126, in
write
s.write(data)
UnicodeEncodeError: 'ascii' codec can't encode character u'\xe4' in position
62: ordinal not in range(128)
>> begin captured logging <<
dtest: DEBUG: cluster ccm directory: /tmp/dtest-Wvh3PT
dtest: DEBUG: Custom init_config not found. Setting defaults.
dtest: DEBUG: Done setting configuration options:
{ 'initial_token': None,
'num_tokens': '256',
'phi_convict_threshold': 5,
'range_request_timeout_in_ms': 1,
'read_request_timeout_in_ms': 1,
'request_timeout_in_ms': 1,
'truncate_request_timeout_in_ms': 1,
'write_request_timeout_in_ms': 1}
- >> end captured logging << -
==
ERROR: test_unicode_syntax_error (cqlsh_tests.cqlsh_tests.TestCqlsh)
--
Traceback (most recent call last):
File "/home/mshuler/git/cassandra-dtest/cqlsh_tests/cqlsh_tests.py", line
456, in test_unicode_syntax_error
output, err = node1.run_cqlsh(cmds=u"รค;".encode('utf8'), return_output=True)
File "/home/mshuler/git/ccm/ccmlib/node.py", line 816, in run_cqlsh
print_("(EE) ", err, end='')
File "/usr/lib/python2.7/dist-packages/nose/plugins/xunit.py", line 126, in
write
s.write(data)
File "/usr/lib/python2.7/dist-packages/nose/plugins/xunit.py", line 126, in
write
s.write(data)
File "/usr/lib/python2.7/dist-packages/nose/plugins/xunit.py", line 126, in
write
s.write(data)
File "/usr/lib/python2.7/dist-packages/nose/plugins/xunit.py", line 126, in
write
s.write(data)
UnicodeEncodeError: 'ascii' codec can't encode character u'\xe4' in position
12: ordinal not in range(128)
>> begin captured logging <<
dtest: DEBUG: cluster ccm directory: /tmp/dtest-lh6EEU
dtest: DEBUG: Custom init_config not found. Setting defaults.
dtest: DEBUG: Done setting configuration options:
{ 'initial_token': None,
'num_tokens': '256',
'phi_convict_threshold': 5,
'range_request_timeout_in_ms': 1,
'read_request_timeout_in_ms': 1,
'request_timeout_in_ms': 1,
'truncate_request_timeout_in_ms': 1,
'write_request_timeout_in_ms': 1}
- >> end captured logging << -
--
XML:
[jira] [Commented] (CASSANDRA-11799) dtest failure in cqlsh_tests.cqlsh_tests.TestCqlsh.test_unicode_syntax_error
[
https://issues.apache.org/jira/browse/CASSANDRA-11799?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15291271#comment-15291271
]
Michael Shuler commented on CASSANDRA-11799:
I'll check these out in the same environments we test on - they are UTF8 locale
boxes and I think there are other UTF8 tests, but I'll see what I can come up
with.
> dtest failure in cqlsh_tests.cqlsh_tests.TestCqlsh.test_unicode_syntax_error
>
>
> Key: CASSANDRA-11799
> URL: https://issues.apache.org/jira/browse/CASSANDRA-11799
> Project: Cassandra
> Issue Type: Test
>Reporter: Philip Thompson
>Assignee: Tyler Hobbs
> Labels: cqlsh, dtest
> Fix For: 2.2.x, 3.0.x, 3.x
>
>
> example failure:
> http://cassci.datastax.com/job/cassandra-3.0_dtest/703/testReport/cqlsh_tests.cqlsh_tests/TestCqlsh/test_unicode_syntax_error
> Failed on CassCI build cassandra-3.0_dtest #703
> Also failing is
> cqlsh_tests.cqlsh_tests.TestCqlsh.test_unicode_invalid_request_error
> The relevant failure is
> {code}
> 'ascii' codec can't encode character u'\xe4' in position 12: ordinal not in
> range(128)
> {code}
> These are failing on 2.2, 3.0 and trunk.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (CASSANDRA-11818) C* does neither recover nor trigger stability inspector on direct memory OOM
[
https://issues.apache.org/jira/browse/CASSANDRA-11818?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15287276#comment-15287276
]
Michael Shuler commented on CASSANDRA-11818:
It's on the list, now :)
> C* does neither recover nor trigger stability inspector on direct memory OOM
>
>
> Key: CASSANDRA-11818
> URL: https://issues.apache.org/jira/browse/CASSANDRA-11818
> Project: Cassandra
> Issue Type: Bug
>Reporter: Robert Stupp
> Attachments: oom-histo-live.txt, oom-stack.txt
>
>
> The following stack trace is not caught by {{JVMStabilityInspector}}.
> Situation was caused by a load test with a lot of parallel writes and reads
> against a single node.
> {code}
> ERROR [SharedPool-Worker-1] 2016-05-17 18:38:44,187 Message.java:611 -
> Unexpected exception during request; channel = [id: 0x1e02351b,
> L:/127.0.0.1:9042 - R:/127.0.0.1:51087]
> java.lang.OutOfMemoryError: Direct buffer memory
> at java.nio.Bits.reserveMemory(Bits.java:693) ~[na:1.8.0_92]
> at java.nio.DirectByteBuffer.(DirectByteBuffer.java:123)
> ~[na:1.8.0_92]
> at java.nio.ByteBuffer.allocateDirect(ByteBuffer.java:311)
> ~[na:1.8.0_92]
> at io.netty.buffer.PoolArena$DirectArena.newChunk(PoolArena.java:672)
> ~[netty-all-4.0.36.Final.jar:4.0.36.Final]
> at io.netty.buffer.PoolArena.allocateNormal(PoolArena.java:234)
> ~[netty-all-4.0.36.Final.jar:4.0.36.Final]
> at io.netty.buffer.PoolArena.allocate(PoolArena.java:218)
> ~[netty-all-4.0.36.Final.jar:4.0.36.Final]
> at io.netty.buffer.PoolArena.allocate(PoolArena.java:138)
> ~[netty-all-4.0.36.Final.jar:4.0.36.Final]
> at
> io.netty.buffer.PooledByteBufAllocator.newDirectBuffer(PooledByteBufAllocator.java:270)
> ~[netty-all-4.0.36.Final.jar:4.0.36.Final]
> at
> io.netty.buffer.AbstractByteBufAllocator.directBuffer(AbstractByteBufAllocator.java:177)
> ~[netty-all-4.0.36.Final.jar:4.0.36.Final]
> at
> io.netty.buffer.AbstractByteBufAllocator.directBuffer(AbstractByteBufAllocator.java:168)
> ~[netty-all-4.0.36.Final.jar:4.0.36.Final]
> at
> io.netty.buffer.AbstractByteBufAllocator.buffer(AbstractByteBufAllocator.java:105)
> ~[netty-all-4.0.36.Final.jar:4.0.36.Final]
> at
> org.apache.cassandra.transport.Message$ProtocolEncoder.encode(Message.java:349)
> ~[main/:na]
> at
> org.apache.cassandra.transport.Message$ProtocolEncoder.encode(Message.java:314)
> ~[main/:na]
> at
> io.netty.handler.codec.MessageToMessageEncoder.write(MessageToMessageEncoder.java:89)
> ~[netty-all-4.0.36.Final.jar:4.0.36.Final]
> at
> io.netty.channel.AbstractChannelHandlerContext.invokeWrite(AbstractChannelHandlerContext.java:619)
> ~[netty-all-4.0.36.Final.jar:4.0.36.Final]
> at
> io.netty.channel.AbstractChannelHandlerContext.write(AbstractChannelHandlerContext.java:676)
> ~[netty-all-4.0.36.Final.jar:4.0.36.Final]
> at
> io.netty.channel.AbstractChannelHandlerContext.write(AbstractChannelHandlerContext.java:612)
> ~[netty-all-4.0.36.Final.jar:4.0.36.Final]
> at
> org.apache.cassandra.transport.Message$Dispatcher$Flusher.run(Message.java:445)
> ~[main/:na]
> at
> io.netty.util.concurrent.PromiseTask$RunnableAdapter.call(PromiseTask.java:38)
> ~[netty-all-4.0.36.Final.jar:4.0.36.Final]
> at
> io.netty.util.concurrent.ScheduledFutureTask.run(ScheduledFutureTask.java:120)
> ~[netty-all-4.0.36.Final.jar:4.0.36.Final]
> at
> io.netty.util.concurrent.SingleThreadEventExecutor.runAllTasks(SingleThreadEventExecutor.java:358)
> ~[netty-all-4.0.36.Final.jar:4.0.36.Final]
> at io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:374)
> ~[netty-all-4.0.36.Final.jar:4.0.36.Final]
> at
> io.netty.util.concurrent.SingleThreadEventExecutor$2.run(SingleThreadEventExecutor.java:112)
> ~[netty-all-4.0.36.Final.jar:4.0.36.Final]
> at
> io.netty.util.concurrent.DefaultThreadFactory$DefaultRunnableDecorator.run(DefaultThreadFactory.java:137)
> ~[netty-all-4.0.36.Final.jar:4.0.36.Final]
> at java.lang.Thread.run(Thread.java:745) [na:1.8.0_92]
> {code}
> The situation does not get better when the load driver is stopped.
> I can reproduce this scenario at will. Managed to get histogram, stack traces
> and heap dump. Already increased {{-XX:MaxDirectMemorySize}} to {{2g}}.
> A {{nodetool flush}} causes the daemon to exit (as that direct-memory OOM is
> caught by {{JVMStabilityInspector}}).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (CASSANDRA-8092) Check for swallowed Throwable in CI environment
[ https://issues.apache.org/jira/browse/CASSANDRA-8092?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15287216#comment-15287216 ] Michael Shuler commented on CASSANDRA-8092: --- I'm all for someone committing this utility and we can set up CI to run it. > Check for swallowed Throwable in CI environment > --- > > Key: CASSANDRA-8092 > URL: https://issues.apache.org/jira/browse/CASSANDRA-8092 > Project: Cassandra > Issue Type: Test >Reporter: Joshua McKenzie >Assignee: Michael Shuler >Priority: Minor > Fix For: 2.1.x > > Attachments: 7507_check_swallowed.txt > > > Reference CASSANDRA-7507. We don't want to swallow Throwable or Exception's > in the code-base but rather delegate them to the JVMStabilityInspector added > in that ticket. Attached patch adds a python script to tools\bin (maybe > incorrect placement) that'll check for Throwable and return count of > swallowed. It will also do the same for Exception if you pass it the flag > for that. > Ideally we'd integrate checking our code-base on build in the CI environment > and fail if we have count > 0 on Throwable for now, and update it to include > Exception as well after CASSANDRA-7579. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (CASSANDRA-11795) cassandra-stress legacy mode fails - time to remove it?
Michael Shuler created CASSANDRA-11795:
--
Summary: cassandra-stress legacy mode fails - time to remove it?
Key: CASSANDRA-11795
URL: https://issues.apache.org/jira/browse/CASSANDRA-11795
Project: Cassandra
Issue Type: Bug
Components: Tools
Reporter: Michael Shuler
Priority: Minor
Fix For: 3.x
{noformat}
(trunk)mshuler@hana:~/git/cassandra$ cassandra-stress legacy -o INSERT
Running in legacy support mode. Translating command to:
stress write n=100 -col n=fixed(5) size=fixed(34) data=repeat(1) -rate
threads=50 -log interval=10 -mode thrift
Invalid parameter data=repeat(1)
Usage: cassandra-stress [options]
Help usage: cassandra-stress help
---Commands---
read : Multiple concurrent reads - the cluster must first be
populated by a write test
write: Multiple concurrent writes against the cluster
<...>
{noformat}
I tried legacy mode as a one-off, since someone provided a 2.0 stress option
command line to duplicate. Is it time to remove legacy, perhaps?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Issue Comment Deleted] (CASSANDRA-11352) Include units of metrics in the cassandra-stress tool
[
https://issues.apache.org/jira/browse/CASSANDRA-11352?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Shuler updated CASSANDRA-11352:
---
Comment: was deleted
(was: [~thobbs] anything attempting to do math on metrics output, which now
contains commas, fails or needs to strip the strings. Any way to flag this as
{{--human-readable}} or similar? The metrics are no longer really numeric
metrics, but pretty human-readable representations of numbers.)
> Include units of metrics in the cassandra-stress tool
> --
>
> Key: CASSANDRA-11352
> URL: https://issues.apache.org/jira/browse/CASSANDRA-11352
> Project: Cassandra
> Issue Type: Improvement
> Components: Tools
>Reporter: Rajath Subramanyam
>Assignee: Giampaolo
>Priority: Minor
> Labels: lhf
> Fix For: 3.6
>
> Attachments:
> cassandra-11352-trunk-giampaolo-trapasso@radicalbit-io.patch
>
>
> cassandra-stress in the Results section can have units for the metrics as an
> improvement to make the tool more usable.
> {noformat}
> Results:
> op rate : 14668 [READ:7334, WRITE:7334]
> partition rate: 14668 [READ:7334, WRITE:7334]
> row rate : 14668 [READ:7334, WRITE:7334]
> latency mean : 0.7 [READ:0.7, WRITE:0.7]
> latency median: 0.6 [READ:0.6, WRITE:0.6]
> latency 95th percentile : 0.8 [READ:0.8, WRITE:0.8]
> latency 99th percentile : 1.2 [READ:1.2, WRITE:1.2]
> latency 99.9th percentile : 8.8 [READ:8.9, WRITE:9.0]
> latency max : 448.7 [READ:162.3, WRITE:448.7]
> Total partitions : 105612753 [READ:52805915, WRITE:52806838]
> Total errors : 0 [READ:0, WRITE:0]
> total gc count: 0
> total gc mb : 0
> total gc time (s) : 0
> avg gc time(ms) : NaN
> stdev gc time(ms) : 0
> Total operation time : 02:00:00
> END
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (CASSANDRA-11352) Include units of metrics in the cassandra-stress tool
[
https://issues.apache.org/jira/browse/CASSANDRA-11352?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15280479#comment-15280479
]
Michael Shuler commented on CASSANDRA-11352:
[~thobbs] anything attempting to do math on metrics output, which now contains
commas, fails or needs to strip the strings. Any way to flag this as
{{--human-readable}} or similar? The metrics are no longer really numeric
metrics, but pretty human-readable representations of numbers.
> Include units of metrics in the cassandra-stress tool
> --
>
> Key: CASSANDRA-11352
> URL: https://issues.apache.org/jira/browse/CASSANDRA-11352
> Project: Cassandra
> Issue Type: Improvement
> Components: Tools
>Reporter: Rajath Subramanyam
>Assignee: Giampaolo
>Priority: Minor
> Labels: lhf
> Fix For: 3.6
>
> Attachments:
> cassandra-11352-trunk-giampaolo-trapasso@radicalbit-io.patch
>
>
> cassandra-stress in the Results section can have units for the metrics as an
> improvement to make the tool more usable.
> {noformat}
> Results:
> op rate : 14668 [READ:7334, WRITE:7334]
> partition rate: 14668 [READ:7334, WRITE:7334]
> row rate : 14668 [READ:7334, WRITE:7334]
> latency mean : 0.7 [READ:0.7, WRITE:0.7]
> latency median: 0.6 [READ:0.6, WRITE:0.6]
> latency 95th percentile : 0.8 [READ:0.8, WRITE:0.8]
> latency 99th percentile : 1.2 [READ:1.2, WRITE:1.2]
> latency 99.9th percentile : 8.8 [READ:8.9, WRITE:9.0]
> latency max : 448.7 [READ:162.3, WRITE:448.7]
> Total partitions : 105612753 [READ:52805915, WRITE:52806838]
> Total errors : 0 [READ:0, WRITE:0]
> total gc count: 0
> total gc mb : 0
> total gc time (s) : 0
> avg gc time(ms) : NaN
> stdev gc time(ms) : 0
> Total operation time : 02:00:00
> END
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (CASSANDRA-11725) Check for unnecessary JMX port setting in env vars at startup
[
https://issues.apache.org/jira/browse/CASSANDRA-11725?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15280329#comment-15280329
]
Michael Shuler commented on CASSANDRA-11725:
Confirming this commit works for allowing public IP setting in
{{java.rmi.server.hostname}} on a cloud server that does not know its public
IP. That bind was failing previously, but works out fine now. Thanks!
> Check for unnecessary JMX port setting in env vars at startup
> -
>
> Key: CASSANDRA-11725
> URL: https://issues.apache.org/jira/browse/CASSANDRA-11725
> Project: Cassandra
> Issue Type: Bug
> Components: Lifecycle
>Reporter: Sam Tunnicliffe
>Assignee: Sam Tunnicliffe
>Priority: Minor
> Labels: lhf
> Fix For: 3.6
>
>
> Since CASSANDRA-10091, C* expects to always be in control of initializing its
> JMX connector server. However, if {{com.sun.management.jmxremote.port}} is
> set when the JVM is started, the bootstrap agent takes over and sets up the
> server before any C* code runs. Because C* is then unable to bind the server
> it creates to the specified port, startup is halted and the root cause is
> somewhat unclear.
> We should add a check at startup so a more informative message can be
> provided. This would test for the presence of the system property which would
> differentiate from the case where some other process is already bound to the
> port.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Resolved] (CASSANDRA-11540) The JVM should exit if jmx fails to bind
[
https://issues.apache.org/jira/browse/CASSANDRA-11540?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Shuler resolved CASSANDRA-11540.
Resolution: Fixed
I just found the config change that helps out with my env situation:
{{-Dcassandra.jmx.local.port=7199}} instead of
{{-Dcom.sun.management.jmxremote.port=7199}}
> The JVM should exit if jmx fails to bind
>
>
> Key: CASSANDRA-11540
> URL: https://issues.apache.org/jira/browse/CASSANDRA-11540
> Project: Cassandra
> Issue Type: Bug
> Components: Core
>Reporter: Brandon Williams
>Assignee: Alex Petrov
> Labels: lhf
> Fix For: 2.2.7, 3.7, 3.0.7
>
>
> If you are already running a cassandra instance, but for some reason try to
> start another one, this happens:
> {noformat}
> INFO 20:57:09 JNA mlockall successful
> WARN 20:57:09 JMX is not enabled to receive remote connections. Please see
> cassandra-env.sh for more info.
> ERROR 20:57:10 Error starting local jmx server:
> java.rmi.server.ExportException: Port already in use: 7199; nested exception
> is:
> java.net.BindException: Address already in use
> at sun.rmi.transport.tcp.TCPTransport.listen(TCPTransport.java:340)
> ~[na:1.7.0_76]
> at
> sun.rmi.transport.tcp.TCPTransport.exportObject(TCPTransport.java:248)
> ~[na:1.7.0_76]
> at
> sun.rmi.transport.tcp.TCPEndpoint.exportObject(TCPEndpoint.java:411)
> ~[na:1.7.0_76]
> at sun.rmi.transport.LiveRef.exportObject(LiveRef.java:147)
> ~[na:1.7.0_76]
> at
> sun.rmi.server.UnicastServerRef.exportObject(UnicastServerRef.java:207)
> ~[na:1.7.0_76]
> at sun.rmi.registry.RegistryImpl.setup(RegistryImpl.java:122)
> ~[na:1.7.0_76]
> at sun.rmi.registry.RegistryImpl.(RegistryImpl.java:98)
> ~[na:1.7.0_76]
> at
> java.rmi.registry.LocateRegistry.createRegistry(LocateRegistry.java:239)
> ~[na:1.7.0_76]
> at
> org.apache.cassandra.service.CassandraDaemon.maybeInitJmx(CassandraDaemon.java:100)
> [main/:na]
> at
> org.apache.cassandra.service.CassandraDaemon.setup(CassandraDaemon.java:222)
> [main/:na]
> at
> org.apache.cassandra.service.CassandraDaemon.activate(CassandraDaemon.java:564)
> [main/:na]
> at
> org.apache.cassandra.service.CassandraDaemon.main(CassandraDaemon.java:653)
> [main/:na]
> Caused by: java.net.BindException: Address already in use
> at java.net.PlainSocketImpl.socketBind(Native Method) ~[na:1.7.0_76]
> at
> java.net.AbstractPlainSocketImpl.bind(AbstractPlainSocketImpl.java:376)
> ~[na:1.7.0_76]
> at java.net.ServerSocket.bind(ServerSocket.java:376) ~[na:1.7.0_76]
> at java.net.ServerSocket.(ServerSocket.java:237) ~[na:1.7.0_76]
> at
> javax.net.DefaultServerSocketFactory.createServerSocket(ServerSocketFactory.java:231)
> ~[na:1.7.0_76]
> at
> org.apache.cassandra.utils.RMIServerSocketFactoryImpl.createServerSocket(RMIServerSocketFactoryImpl.java:13)
> ~[main/:na]
> at
> sun.rmi.transport.tcp.TCPEndpoint.newServerSocket(TCPEndpoint.java:666)
> ~[na:1.7.0_76]
> at sun.rmi.transport.tcp.TCPTransport.listen(TCPTransport.java:329)
> ~[na:1.7.0_76]
> ... 11 common frames omitted
> {noformat}
> However the startup continues, and ends up replaying commitlogs, which is
> probably not a good thing.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Reopened] (CASSANDRA-11540) The JVM should exit if jmx fails to bind
[
https://issues.apache.org/jira/browse/CASSANDRA-11540?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Shuler reopened CASSANDRA-11540:
> The JVM should exit if jmx fails to bind
>
>
> Key: CASSANDRA-11540
> URL: https://issues.apache.org/jira/browse/CASSANDRA-11540
> Project: Cassandra
> Issue Type: Bug
> Components: Core
>Reporter: Brandon Williams
>Assignee: Alex Petrov
> Labels: lhf
> Fix For: 2.2.7, 3.7, 3.0.7
>
>
> If you are already running a cassandra instance, but for some reason try to
> start another one, this happens:
> {noformat}
> INFO 20:57:09 JNA mlockall successful
> WARN 20:57:09 JMX is not enabled to receive remote connections. Please see
> cassandra-env.sh for more info.
> ERROR 20:57:10 Error starting local jmx server:
> java.rmi.server.ExportException: Port already in use: 7199; nested exception
> is:
> java.net.BindException: Address already in use
> at sun.rmi.transport.tcp.TCPTransport.listen(TCPTransport.java:340)
> ~[na:1.7.0_76]
> at
> sun.rmi.transport.tcp.TCPTransport.exportObject(TCPTransport.java:248)
> ~[na:1.7.0_76]
> at
> sun.rmi.transport.tcp.TCPEndpoint.exportObject(TCPEndpoint.java:411)
> ~[na:1.7.0_76]
> at sun.rmi.transport.LiveRef.exportObject(LiveRef.java:147)
> ~[na:1.7.0_76]
> at
> sun.rmi.server.UnicastServerRef.exportObject(UnicastServerRef.java:207)
> ~[na:1.7.0_76]
> at sun.rmi.registry.RegistryImpl.setup(RegistryImpl.java:122)
> ~[na:1.7.0_76]
> at sun.rmi.registry.RegistryImpl.(RegistryImpl.java:98)
> ~[na:1.7.0_76]
> at
> java.rmi.registry.LocateRegistry.createRegistry(LocateRegistry.java:239)
> ~[na:1.7.0_76]
> at
> org.apache.cassandra.service.CassandraDaemon.maybeInitJmx(CassandraDaemon.java:100)
> [main/:na]
> at
> org.apache.cassandra.service.CassandraDaemon.setup(CassandraDaemon.java:222)
> [main/:na]
> at
> org.apache.cassandra.service.CassandraDaemon.activate(CassandraDaemon.java:564)
> [main/:na]
> at
> org.apache.cassandra.service.CassandraDaemon.main(CassandraDaemon.java:653)
> [main/:na]
> Caused by: java.net.BindException: Address already in use
> at java.net.PlainSocketImpl.socketBind(Native Method) ~[na:1.7.0_76]
> at
> java.net.AbstractPlainSocketImpl.bind(AbstractPlainSocketImpl.java:376)
> ~[na:1.7.0_76]
> at java.net.ServerSocket.bind(ServerSocket.java:376) ~[na:1.7.0_76]
> at java.net.ServerSocket.(ServerSocket.java:237) ~[na:1.7.0_76]
> at
> javax.net.DefaultServerSocketFactory.createServerSocket(ServerSocketFactory.java:231)
> ~[na:1.7.0_76]
> at
> org.apache.cassandra.utils.RMIServerSocketFactoryImpl.createServerSocket(RMIServerSocketFactoryImpl.java:13)
> ~[main/:na]
> at
> sun.rmi.transport.tcp.TCPEndpoint.newServerSocket(TCPEndpoint.java:666)
> ~[na:1.7.0_76]
> at sun.rmi.transport.tcp.TCPTransport.listen(TCPTransport.java:329)
> ~[na:1.7.0_76]
> ... 11 common frames omitted
> {noformat}
> However the startup continues, and ends up replaying commitlogs, which is
> probably not a good thing.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Comment Edited] (CASSANDRA-11540) The JVM should exit if jmx fails to bind
[
https://issues.apache.org/jira/browse/CASSANDRA-11540?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15273271#comment-15273271
]
Michael Shuler edited comment on CASSANDRA-11540 at 5/5/16 10:56 PM:
-
Just a quick note on behavior after this commit, as we have found in cstar_perf
(trunk will not start at all, currently).
If a user happens to set an environment variable {{JVM_OPTS="$JVM_OPTS
-Dcom.sun.management.jmxremote.port=7199 ..."}} startup fails. There's no other
Cassandra running and nothing was listening to 7199 prior to startup.
I believe that commit 7b0c716 introduced for CASSANDRA-10091 does something a
little wonky with regards to JVM_OPTS. The previous commit, ad7e36b, does not
throw an error when JVM_OPTS are passed in the user env.
If this hard failure is working as intended, please let me know!
Repro on trunk HEAD:
{noformat}
(trunk)mshuler@mana:~/git/cassandra$ sudo netstat -atunp | grep 7199
(trunk)mshuler@mana:~/git/cassandra$
(trunk)mshuler@mana:~/git/cassandra$ export
JVM_OPTS="-Dcom.sun.management.jmxremote.port=7199
-Dcom.sun.management.jmxremote.ssl=false
-Dcom.sun.management.jmxremote.authenticate=false
-Djava.rmi.server.hostname=127.0.0.1"
(trunk)mshuler@mana:~/git/cassandra$
(trunk)mshuler@mana:~/git/cassandra$ cassandra -f
<...>
INFO 22:00:18 Not submitting build tasks for views in keyspace system as
storage service is not initialized
ERROR 22:00:18 Port already in use: 7199; nested exception is:
java.net.BindException: Address already in use
java.net.BindException: Address already in use
at java.net.PlainSocketImpl.socketBind(Native Method) ~[na:1.8.0_92]
at
java.net.AbstractPlainSocketImpl.bind(AbstractPlainSocketImpl.java:387)
~[na:1.8.0_92]
at java.net.ServerSocket.bind(ServerSocket.java:375) ~[na:1.8.0_92]
at java.net.ServerSocket.(ServerSocket.java:237) ~[na:1.8.0_92]
at
javax.net.DefaultServerSocketFactory.createServerSocket(ServerSocketFactory.java:231)
~[na:1.8.0_92]
at
org.apache.cassandra.utils.RMIServerSocketFactoryImpl.createServerSocket(RMIServerSocketFactoryImpl.java:21)
~[main/:na]
at
sun.rmi.transport.tcp.TCPEndpoint.newServerSocket(TCPEndpoint.java:666)
~[na:1.8.0_92]
at sun.rmi.transport.tcp.TCPTransport.listen(TCPTransport.java:330)
~[na:1.8.0_92]
at
sun.rmi.transport.tcp.TCPTransport.exportObject(TCPTransport.java:249)
~[na:1.8.0_92]
at sun.rmi.transport.tcp.TCPEndpoint.exportObject(TCPEndpoint.java:411)
~[na:1.8.0_92]
at sun.rmi.transport.LiveRef.exportObject(LiveRef.java:147)
~[na:1.8.0_92]
at
sun.rmi.server.UnicastServerRef.exportObject(UnicastServerRef.java:212)
~[na:1.8.0_92]
at sun.rmi.registry.RegistryImpl.setup(RegistryImpl.java:152)
~[na:1.8.0_92]
at sun.rmi.registry.RegistryImpl.(RegistryImpl.java:112)
~[na:1.8.0_92]
at
java.rmi.registry.LocateRegistry.createRegistry(LocateRegistry.java:239)
~[na:1.8.0_92]
at
org.apache.cassandra.utils.JMXServerUtils.createJMXServer(JMXServerUtils.java:94)
~[main/:na]
at
org.apache.cassandra.service.CassandraDaemon.maybeInitJmx(CassandraDaemon.java:124)
[main/:na]
at
org.apache.cassandra.service.CassandraDaemon.setup(CassandraDaemon.java:193)
[main/:na]
at
org.apache.cassandra.service.CassandraDaemon.activate(CassandraDaemon.java:568)
[main/:na]
at
org.apache.cassandra.service.CassandraDaemon.main(CassandraDaemon.java:697)
[main/:na]
(trunk)mshuler@mana:~/git/cassandra$
{noformat}
was (Author: mshuler):
Just a quick note on behavior after this commit, as we have found in cstar_perf
(trunk will not start at all, currently).
If a user happens to set and environment variable {{JVM_OPTS="$JVM_OPTS
-Dcom.sun.management.jmxremote.port=7199 ..."}} startup fails. There's no other
Cassandra running and nothing was listening to 7199 prior to startup.
I believe that commit 7b0c716 introduced for CASSANDRA-10091 does something a
little wonky with regards to JVM_OPTS. The previous commit, ad7e36b, does not
throw an error when JVM_OPTS are passed in the user env.
If this hard failure is working as intended, please let me know!
Repro on trunk HEAD:
{noformat}
(trunk)mshuler@mana:~/git/cassandra$ sudo netstat -atunp | grep 7199
(trunk)mshuler@mana:~/git/cassandra$
(trunk)mshuler@mana:~/git/cassandra$ export
JVM_OPTS="-Dcom.sun.management.jmxremote.port=7199
-Dcom.sun.management.jmxremote.ssl=false
-Dcom.sun.management.jmxremote.authenticate=false
-Djava.rmi.server.hostname=127.0.0.1"
(trunk)mshuler@mana:~/git/cassandra$
(trunk)mshuler@mana:~/git/cassandra$ cassandra -f
<...>
INFO 22:00:18 Not submitting build tasks for views in keyspace system as
storage service is not initialized
ERROR 22:00:18 Port already in use: 7199; nested exception is:
java.net.BindException: Address already in use
[jira] [Commented] (CASSANDRA-11540) The JVM should exit if jmx fails to bind
[
https://issues.apache.org/jira/browse/CASSANDRA-11540?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15273271#comment-15273271
]
Michael Shuler commented on CASSANDRA-11540:
Just a quick note on behavior after this commit, as we have found in cstar_perf
(trunk will not start at all, currently).
If a user happens to set and environment variable {{JVM_OPTS="$JVM_OPTS
-Dcom.sun.management.jmxremote.port=7199 ..."}} startup fails. There's no other
Cassandra running and nothing was listening to 7199 prior to startup.
I believe that commit 7b0c716 introduced for CASSANDRA-10091 does something a
little wonky with regards to JVM_OPTS. The previous commit, ad7e36b, does not
throw an error when JVM_OPTS are passed in the user env.
If this hard failure is working as intended, please let me know!
Repro on trunk HEAD:
{noformat}
(trunk)mshuler@mana:~/git/cassandra$ sudo netstat -atunp | grep 7199
(trunk)mshuler@mana:~/git/cassandra$
(trunk)mshuler@mana:~/git/cassandra$ export
JVM_OPTS="-Dcom.sun.management.jmxremote.port=7199
-Dcom.sun.management.jmxremote.ssl=false
-Dcom.sun.management.jmxremote.authenticate=false
-Djava.rmi.server.hostname=127.0.0.1"
(trunk)mshuler@mana:~/git/cassandra$
(trunk)mshuler@mana:~/git/cassandra$ cassandra -f
<...>
INFO 22:00:18 Not submitting build tasks for views in keyspace system as
storage service is not initialized
ERROR 22:00:18 Port already in use: 7199; nested exception is:
java.net.BindException: Address already in use
java.net.BindException: Address already in use
at java.net.PlainSocketImpl.socketBind(Native Method) ~[na:1.8.0_92]
at
java.net.AbstractPlainSocketImpl.bind(AbstractPlainSocketImpl.java:387)
~[na:1.8.0_92]
at java.net.ServerSocket.bind(ServerSocket.java:375) ~[na:1.8.0_92]
at java.net.ServerSocket.(ServerSocket.java:237) ~[na:1.8.0_92]
at
javax.net.DefaultServerSocketFactory.createServerSocket(ServerSocketFactory.java:231)
~[na:1.8.0_92]
at
org.apache.cassandra.utils.RMIServerSocketFactoryImpl.createServerSocket(RMIServerSocketFactoryImpl.java:21)
~[main/:na]
at
sun.rmi.transport.tcp.TCPEndpoint.newServerSocket(TCPEndpoint.java:666)
~[na:1.8.0_92]
at sun.rmi.transport.tcp.TCPTransport.listen(TCPTransport.java:330)
~[na:1.8.0_92]
at
sun.rmi.transport.tcp.TCPTransport.exportObject(TCPTransport.java:249)
~[na:1.8.0_92]
at sun.rmi.transport.tcp.TCPEndpoint.exportObject(TCPEndpoint.java:411)
~[na:1.8.0_92]
at sun.rmi.transport.LiveRef.exportObject(LiveRef.java:147)
~[na:1.8.0_92]
at
sun.rmi.server.UnicastServerRef.exportObject(UnicastServerRef.java:212)
~[na:1.8.0_92]
at sun.rmi.registry.RegistryImpl.setup(RegistryImpl.java:152)
~[na:1.8.0_92]
at sun.rmi.registry.RegistryImpl.(RegistryImpl.java:112)
~[na:1.8.0_92]
at
java.rmi.registry.LocateRegistry.createRegistry(LocateRegistry.java:239)
~[na:1.8.0_92]
at
org.apache.cassandra.utils.JMXServerUtils.createJMXServer(JMXServerUtils.java:94)
~[main/:na]
at
org.apache.cassandra.service.CassandraDaemon.maybeInitJmx(CassandraDaemon.java:124)
[main/:na]
at
org.apache.cassandra.service.CassandraDaemon.setup(CassandraDaemon.java:193)
[main/:na]
at
org.apache.cassandra.service.CassandraDaemon.activate(CassandraDaemon.java:568)
[main/:na]
at
org.apache.cassandra.service.CassandraDaemon.main(CassandraDaemon.java:697)
[main/:na]
(trunk)mshuler@mana:~/git/cassandra$
{noformat}
> The JVM should exit if jmx fails to bind
>
>
> Key: CASSANDRA-11540
> URL: https://issues.apache.org/jira/browse/CASSANDRA-11540
> Project: Cassandra
> Issue Type: Bug
> Components: Core
>Reporter: Brandon Williams
>Assignee: Alex Petrov
> Labels: lhf
> Fix For: 2.2.7, 3.7, 3.0.7
>
>
> If you are already running a cassandra instance, but for some reason try to
> start another one, this happens:
> {noformat}
> INFO 20:57:09 JNA mlockall successful
> WARN 20:57:09 JMX is not enabled to receive remote connections. Please see
> cassandra-env.sh for more info.
> ERROR 20:57:10 Error starting local jmx server:
> java.rmi.server.ExportException: Port already in use: 7199; nested exception
> is:
> java.net.BindException: Address already in use
> at sun.rmi.transport.tcp.TCPTransport.listen(TCPTransport.java:340)
> ~[na:1.7.0_76]
> at
> sun.rmi.transport.tcp.TCPTransport.exportObject(TCPTransport.java:248)
> ~[na:1.7.0_76]
> at
> sun.rmi.transport.tcp.TCPEndpoint.exportObject(TCPEndpoint.java:411)
> ~[na:1.7.0_76]
> at sun.rmi.transport.LiveRef.exportObject(LiveRef.java:147)
> ~[na:1.7.0_76]
> at
> sun.rmi.server.UnicastServerRef.exportObject(UnicastServerRef.java:207)
>
[jira] [Updated] (CASSANDRA-11661) Cassandra 2.0 and later require Java 7u25 or later - jdk 101
[ https://issues.apache.org/jira/browse/CASSANDRA-11661?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Shuler updated CASSANDRA-11661: --- Fix Version/s: (was: 2.2.x) (was: 2.1.x) 3.0.7 2.2.7 2.1.15 > Cassandra 2.0 and later require Java 7u25 or later - jdk 101 > > > Key: CASSANDRA-11661 > URL: https://issues.apache.org/jira/browse/CASSANDRA-11661 > Project: Cassandra > Issue Type: Bug > Components: Testing > Environment: Cassandra Server 2.1.5 and Java jdk1.7.0_101-b14 >Reporter: William Boutin >Assignee: Eduard Tudenhoefner >Priority: Critical > Fix For: 2.1.15, 2.2.7, 3.7, 3.0.7 > > Attachments: 11661-2.1.patch, 11661-2.2.patch, 11661-3.0.patch > > > We have been running the cassandr server version 2.1.5. Friday, we applied > the latest java patch, Java(TM) SE Runtime Environment (build 1.7.0_101-b14). > Cassandra cannot start with this patch. The cassandra log states: Cassandra > 2.0 and later require Java 7u25 or later. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CASSANDRA-11661) Cassandra 2.0 and later require Java 7u25 or later - jdk 101
[ https://issues.apache.org/jira/browse/CASSANDRA-11661?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Shuler updated CASSANDRA-11661: --- Fix Version/s: (was: 3.0.x) 3.7 > Cassandra 2.0 and later require Java 7u25 or later - jdk 101 > > > Key: CASSANDRA-11661 > URL: https://issues.apache.org/jira/browse/CASSANDRA-11661 > Project: Cassandra > Issue Type: Bug > Components: Testing > Environment: Cassandra Server 2.1.5 and Java jdk1.7.0_101-b14 >Reporter: William Boutin >Assignee: Eduard Tudenhoefner >Priority: Critical > Fix For: 2.1.15, 2.2.7, 3.7, 3.0.7 > > Attachments: 11661-2.1.patch, 11661-2.2.patch, 11661-3.0.patch > > > We have been running the cassandr server version 2.1.5. Friday, we applied > the latest java patch, Java(TM) SE Runtime Environment (build 1.7.0_101-b14). > Cassandra cannot start with this patch. The cassandra log states: Cassandra > 2.0 and later require Java 7u25 or later. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CASSANDRA-11661) Cassandra 2.0 and later require Java 7u25 or later - jdk 101
[ https://issues.apache.org/jira/browse/CASSANDRA-11661?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Shuler updated CASSANDRA-11661: --- Status: Ready to Commit (was: Patch Available) > Cassandra 2.0 and later require Java 7u25 or later - jdk 101 > > > Key: CASSANDRA-11661 > URL: https://issues.apache.org/jira/browse/CASSANDRA-11661 > Project: Cassandra > Issue Type: Bug > Components: Testing > Environment: Cassandra Server 2.1.5 and Java jdk1.7.0_101-b14 >Reporter: William Boutin >Assignee: Eduard Tudenhoefner >Priority: Critical > Fix For: 2.1.x, 2.2.x, 3.0.x > > Attachments: 11661-2.1.patch, 11661-2.2.patch, 11661-3.0.patch > > > We have been running the cassandr server version 2.1.5. Friday, we applied > the latest java patch, Java(TM) SE Runtime Environment (build 1.7.0_101-b14). > Cassandra cannot start with this patch. The cassandra log states: Cassandra > 2.0 and later require Java 7u25 or later. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CASSANDRA-11661) Cassandra 2.0 and later require Java 7u25 or later - jdk 101
[ https://issues.apache.org/jira/browse/CASSANDRA-11661?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15268914#comment-15268914 ] Michael Shuler commented on CASSANDRA-11661: +1 to patches - need a committer :) > Cassandra 2.0 and later require Java 7u25 or later - jdk 101 > > > Key: CASSANDRA-11661 > URL: https://issues.apache.org/jira/browse/CASSANDRA-11661 > Project: Cassandra > Issue Type: Bug > Components: Testing > Environment: Cassandra Server 2.1.5 and Java jdk1.7.0_101-b14 >Reporter: William Boutin >Assignee: Michael Shuler >Priority: Critical > Fix For: 2.1.x, 2.2.x, 3.0.x > > Attachments: 11661-2.1.patch, 11661-2.2.patch, 11661-3.0.patch > > > We have been running the cassandr server version 2.1.5. Friday, we applied > the latest java patch, Java(TM) SE Runtime Environment (build 1.7.0_101-b14). > Cassandra cannot start with this patch. The cassandra log states: Cassandra > 2.0 and later require Java 7u25 or later. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CASSANDRA-11661) Cassandra 2.0 and later require Java 7u25 or later - jdk 101
[ https://issues.apache.org/jira/browse/CASSANDRA-11661?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Shuler updated CASSANDRA-11661: --- Assignee: Eduard Tudenhoefner (was: Michael Shuler) > Cassandra 2.0 and later require Java 7u25 or later - jdk 101 > > > Key: CASSANDRA-11661 > URL: https://issues.apache.org/jira/browse/CASSANDRA-11661 > Project: Cassandra > Issue Type: Bug > Components: Testing > Environment: Cassandra Server 2.1.5 and Java jdk1.7.0_101-b14 >Reporter: William Boutin >Assignee: Eduard Tudenhoefner >Priority: Critical > Fix For: 2.1.x, 2.2.x, 3.0.x > > Attachments: 11661-2.1.patch, 11661-2.2.patch, 11661-3.0.patch > > > We have been running the cassandr server version 2.1.5. Friday, we applied > the latest java patch, Java(TM) SE Runtime Environment (build 1.7.0_101-b14). > Cassandra cannot start with this patch. The cassandra log states: Cassandra > 2.0 and later require Java 7u25 or later. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CASSANDRA-11661) Cassandra 2.0 and later require Java 7u25 or later - jdk 101
[ https://issues.apache.org/jira/browse/CASSANDRA-11661?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Shuler updated CASSANDRA-11661: --- Reviewer: Michael Shuler > Cassandra 2.0 and later require Java 7u25 or later - jdk 101 > > > Key: CASSANDRA-11661 > URL: https://issues.apache.org/jira/browse/CASSANDRA-11661 > Project: Cassandra > Issue Type: Bug > Components: Testing > Environment: Cassandra Server 2.1.5 and Java jdk1.7.0_101-b14 >Reporter: William Boutin >Assignee: Michael Shuler >Priority: Critical > Fix For: 2.1.x, 2.2.x, 3.0.x > > Attachments: 11661-2.1.patch, 11661-2.2.patch, 11661-3.0.patch > > > We have been running the cassandr server version 2.1.5. Friday, we applied > the latest java patch, Java(TM) SE Runtime Environment (build 1.7.0_101-b14). > Cassandra cannot start with this patch. The cassandra log states: Cassandra > 2.0 and later require Java 7u25 or later. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (CASSANDRA-11573) cqlsh fails with undefined symbol: PyUnicodeUCS2_DecodeUTF8
[
https://issues.apache.org/jira/browse/CASSANDRA-11573?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Shuler resolved CASSANDRA-11573.
Resolution: Fixed
Fix Version/s: 3.6
Closing ticket, since root cause ticket has been committed for the upcoming 3.6
release. Thanks for letting us know!
> cqlsh fails with undefined symbol: PyUnicodeUCS2_DecodeUTF8
> ---
>
> Key: CASSANDRA-11573
> URL: https://issues.apache.org/jira/browse/CASSANDRA-11573
> Project: Cassandra
> Issue Type: Bug
> Environment: centos 7, datastax ddc 3.5
> installed according to
> http://docs.datastax.com/en/cassandra/3.x/cassandra/install/installRHEL.html
> JVM vendor/version: OpenJDK 64-Bit Server VM/1.8.0_77
> Cassandra version: 3.5.0
>Reporter: Oli Schacher
>Assignee: Michael Shuler
> Fix For: 3.6
>
>
> trying to run cqlsh produces:
> {quote}
> cqlsh
> Traceback (most recent call last):
> File "/usr/bin/cqlsh.py", line 170, in
> from cqlshlib.copyutil import ExportTask, ImportTask
> ImportError: /usr/lib/python2.7/site-packages/cqlshlib/copyutil.so: undefined
> symbol: PyUnicodeUCS2_DecodeUTF8
> {quote}
> with 3.4 the error does not happen.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (CASSANDRA-11514) trunk compaction performance regression
[
https://issues.apache.org/jira/browse/CASSANDRA-11514?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15260406#comment-15260406
]
Michael Shuler commented on CASSANDRA-11514:
I was unable to find a concrete method to bisect this - I attempted a good
number of variations to find a way to call a commit "good" or "bad", but was
unsuccessful. Those are on a private jira
[CSTAR-478|https://datastax.jira.com/browse/CSTAR-478], which I'm going to
close, since I'm currently unsure of how to proceed.
> trunk compaction performance regression
> ---
>
> Key: CASSANDRA-11514
> URL: https://issues.apache.org/jira/browse/CASSANDRA-11514
> Project: Cassandra
> Issue Type: Bug
> Components: Compaction
> Environment: cstar_perf
>Reporter: Michael Shuler
> Labels: performance
> Fix For: 3.x
>
> Attachments: trunk-compaction_dtcs-op_rate.png,
> trunk-compaction_lcs-op_rate.png
>
>
> It appears that a commit between Mar 29-30 has resulted in a drop in
> compaction performance. I attempted to get a log list of commits to post
> here, but
> {noformat}
> git log trunk@{2016-03-29}..trunk@{2016-03-31}
> {noformat}
> appears to be incomplete, since reading through {{git log}} I see netty and
> och were upgraded during this time period.
> !trunk-compaction_dtcs-op_rate.png!
> !trunk-compaction_lcs-op_rate.png!
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (CASSANDRA-10853) deb package migration to dh_python2
[
https://issues.apache.org/jira/browse/CASSANDRA-10853?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15259124#comment-15259124
]
Michael Shuler commented on CASSANDRA-10853:
sed and a rebuild verified this looks better :)
{noformat}
22:42:07 + /var/lib/jenkins/automaton/bin/ctool run --stream
jenkins-mshuler_trunk_deb-18 0 echo "DESCRIBE TABLES;" | cqlsh
22:42:11
22:42:11 Keyspace system_traces
22:42:11 --
22:42:11 events sessions
22:42:11
22:42:11 Keyspace system_schema
22:42:11 --
22:42:11 tables triggersviewskeyspaces dropped_columns
22:42:11 functions aggregates indexes types columns
22:42:11
22:42:11 Keyspace system_auth
22:42:11
22:42:11 resource_role_permissons_index role_permissions role_members roles
22:42:11
22:42:11 Keyspace system
22:42:11 ---
22:42:11 available_ranges peers paxos
range_xfers
22:42:11 batches compaction_history batchloglocal
22:42:11 "IndexInfo" sstable_activitysize_estimates hints
22:42:11 views_builds_in_progress peer_events built_views
22:42:11
22:42:11 Keyspace system_distributed
22:42:11 ---
22:42:11 repair_history view_build_status parent_repair_history
22:42:11
22:42:11
{noformat}
> deb package migration to dh_python2
> ---
>
> Key: CASSANDRA-10853
> URL: https://issues.apache.org/jira/browse/CASSANDRA-10853
> Project: Cassandra
> Issue Type: Task
> Components: Packaging
>Reporter: Michael Shuler
>Assignee: Michael Shuler
> Fix For: 2.1.15, 3.6, 3.0.6, 2.2.7
>
> Attachments: 10853_2.1.txt, 10853_3.0.txt, 10853_rules.txt
>
>
> I'm working on a deb job in jenkins, and I had forgotten to open a bug for
> this. There is no urgent need, since {{python-support}} is in Jessie, but
> this package is currently in transition to be removed.
> http://deb.li/dhs2p
> During deb build:
> {noformat}
> dh_pysupport: This program is deprecated, you should use dh_python2 instead.
> Migration guide: http://deb.li/dhs2p
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (CASSANDRA-10853) deb package migration to dh_python2
[
https://issues.apache.org/jira/browse/CASSANDRA-10853?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Shuler updated CASSANDRA-10853:
---
Status: Patch Available (was: Reopened)
> deb package migration to dh_python2
> ---
>
> Key: CASSANDRA-10853
> URL: https://issues.apache.org/jira/browse/CASSANDRA-10853
> Project: Cassandra
> Issue Type: Task
> Components: Packaging
>Reporter: Michael Shuler
>Assignee: Michael Shuler
> Fix For: 2.1.15, 3.6, 3.0.6, 2.2.7
>
> Attachments: 10853_2.1.txt, 10853_3.0.txt, 10853_rules.txt
>
>
> I'm working on a deb job in jenkins, and I had forgotten to open a bug for
> this. There is no urgent need, since {{python-support}} is in Jessie, but
> this package is currently in transition to be removed.
> http://deb.li/dhs2p
> During deb build:
> {noformat}
> dh_pysupport: This program is deprecated, you should use dh_python2 instead.
> Migration guide: http://deb.li/dhs2p
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (CASSANDRA-10853) deb package migration to dh_python2
[
https://issues.apache.org/jira/browse/CASSANDRA-10853?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Shuler updated CASSANDRA-10853:
---
Attachment: 10853_rules.txt
[~tjake] I missed the {{debian/rules}} edit when I recreated patches.
10853_rules.txt is attached. It's one line and should merge from 2.1 all the
way up. Sorry about that!
> deb package migration to dh_python2
> ---
>
> Key: CASSANDRA-10853
> URL: https://issues.apache.org/jira/browse/CASSANDRA-10853
> Project: Cassandra
> Issue Type: Task
> Components: Packaging
>Reporter: Michael Shuler
>Assignee: Michael Shuler
> Fix For: 2.1.15, 3.6, 3.0.6, 2.2.7
>
> Attachments: 10853_2.1.txt, 10853_3.0.txt, 10853_rules.txt
>
>
> I'm working on a deb job in jenkins, and I had forgotten to open a bug for
> this. There is no urgent need, since {{python-support}} is in Jessie, but
> this package is currently in transition to be removed.
> http://deb.li/dhs2p
> During deb build:
> {noformat}
> dh_pysupport: This program is deprecated, you should use dh_python2 instead.
> Migration guide: http://deb.li/dhs2p
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Reopened] (CASSANDRA-10853) deb package migration to dh_python2
[
https://issues.apache.org/jira/browse/CASSANDRA-10853?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Shuler reopened CASSANDRA-10853:
I believe my initial test environment was tainted with cqlshlib in PYTHONPATH
or similar.. A package build of trunk after this commit and installation on a
fresh m3.medium gave me an error on import:
{noformat}
21:20:22 + /var/lib/jenkins/automaton/bin/ctool run --stream
jenkins-mshuler_trunk_deb-17 0 echo "DESCRIBE TABLES;" | cqlsh
21:20:24 Traceback (most recent call last):
21:20:24 File "/usr/bin/cqlsh.py", line 167, in
21:20:24 from cqlshlib import cql3handling, cqlhandling, pylexotron,
sslhandling
21:20:24 ImportError: No module named cqlshlib
21:20:24
21:20:24 Results for Node 0:
21:20:24 Host: ec2-54-172-207-27.compute-1.amazonaws.com
21:20:24 Private: 172.31.25.94
21:20:24 Start: 1461705623.42
21:20:24 Finished: 1461705624.03
21:20:24 Elapsed: 0.610841035843
21:20:24 Return Code: 1
21:20:24 Out:
21:20:24 Traceback (most recent call last):
21:20:24 File "/usr/bin/cqlsh.py", line 167, in
21:20:24 from cqlshlib import cql3handling, cqlhandling, pylexotron, sslhandling
21:20:24 ImportError: No module named cqlshlib
21:20:24 Err:
21:20:24
21:20:24
{noformat}
I'll see if I can find the problem.
> deb package migration to dh_python2
> ---
>
> Key: CASSANDRA-10853
> URL: https://issues.apache.org/jira/browse/CASSANDRA-10853
> Project: Cassandra
> Issue Type: Task
> Components: Packaging
>Reporter: Michael Shuler
>Assignee: Michael Shuler
> Fix For: 2.1.15, 3.6, 3.0.6, 2.2.7
>
> Attachments: 10853_2.1.txt, 10853_3.0.txt
>
>
> I'm working on a deb job in jenkins, and I had forgotten to open a bug for
> this. There is no urgent need, since {{python-support}} is in Jessie, but
> this package is currently in transition to be removed.
> http://deb.li/dhs2p
> During deb build:
> {noformat}
> dh_pysupport: This program is deprecated, you should use dh_python2 instead.
> Migration guide: http://deb.li/dhs2p
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Assigned] (CASSANDRA-11573) cqlsh fails with undefined symbol: PyUnicodeUCS2_DecodeUTF8
[
https://issues.apache.org/jira/browse/CASSANDRA-11573?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Shuler reassigned CASSANDRA-11573:
--
Assignee: Michael Shuler
> cqlsh fails with undefined symbol: PyUnicodeUCS2_DecodeUTF8
> ---
>
> Key: CASSANDRA-11573
> URL: https://issues.apache.org/jira/browse/CASSANDRA-11573
> Project: Cassandra
> Issue Type: Bug
> Environment: centos 7, datastax ddc 3.5
> installed according to
> http://docs.datastax.com/en/cassandra/3.x/cassandra/install/installRHEL.html
> JVM vendor/version: OpenJDK 64-Bit Server VM/1.8.0_77
> Cassandra version: 3.5.0
>Reporter: Oli Schacher
>Assignee: Michael Shuler
>
> trying to run cqlsh produces:
> {quote}
> cqlsh
> Traceback (most recent call last):
> File "/usr/bin/cqlsh.py", line 170, in
> from cqlshlib.copyutil import ExportTask, ImportTask
> ImportError: /usr/lib/python2.7/site-packages/cqlshlib/copyutil.so: undefined
> symbol: PyUnicodeUCS2_DecodeUTF8
> {quote}
> with 3.4 the error does not happen.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (CASSANDRA-10853) deb package migration to dh_python2
[
https://issues.apache.org/jira/browse/CASSANDRA-10853?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Shuler updated CASSANDRA-10853:
---
Status: Patch Available (was: In Progress)
> deb package migration to dh_python2
> ---
>
> Key: CASSANDRA-10853
> URL: https://issues.apache.org/jira/browse/CASSANDRA-10853
> Project: Cassandra
> Issue Type: Task
> Components: Packaging
>Reporter: Michael Shuler
>Assignee: Michael Shuler
> Fix For: 3.0.x, 3.x
>
> Attachments: 10853_2.1.txt, 10853_3.0.txt
>
>
> I'm working on a deb job in jenkins, and I had forgotten to open a bug for
> this. There is no urgent need, since {{python-support}} is in Jessie, but
> this package is currently in transition to be removed.
> http://deb.li/dhs2p
> During deb build:
> {noformat}
> dh_pysupport: This program is deprecated, you should use dh_python2 instead.
> Migration guide: http://deb.li/dhs2p
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (CASSANDRA-10853) deb package migration to dh_python2
[
https://issues.apache.org/jira/browse/CASSANDRA-10853?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Shuler updated CASSANDRA-10853:
---
Reviewer: T Jake Luciani
> deb package migration to dh_python2
> ---
>
> Key: CASSANDRA-10853
> URL: https://issues.apache.org/jira/browse/CASSANDRA-10853
> Project: Cassandra
> Issue Type: Task
> Components: Packaging
>Reporter: Michael Shuler
>Assignee: Michael Shuler
> Fix For: 2.1.15, 3.6, 3.0.6, 2.2.7
>
> Attachments: 10853_2.1.txt, 10853_3.0.txt
>
>
> I'm working on a deb job in jenkins, and I had forgotten to open a bug for
> this. There is no urgent need, since {{python-support}} is in Jessie, but
> this package is currently in transition to be removed.
> http://deb.li/dhs2p
> During deb build:
> {noformat}
> dh_pysupport: This program is deprecated, you should use dh_python2 instead.
> Migration guide: http://deb.li/dhs2p
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (CASSANDRA-10853) deb package migration to dh_python2
[
https://issues.apache.org/jira/browse/CASSANDRA-10853?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Shuler updated CASSANDRA-10853:
---
Fix Version/s: (was: 3.0.x)
(was: 3.x)
2.2.7
3.0.6
3.6
2.1.15
> deb package migration to dh_python2
> ---
>
> Key: CASSANDRA-10853
> URL: https://issues.apache.org/jira/browse/CASSANDRA-10853
> Project: Cassandra
> Issue Type: Task
> Components: Packaging
>Reporter: Michael Shuler
>Assignee: Michael Shuler
> Fix For: 2.1.15, 3.6, 3.0.6, 2.2.7
>
> Attachments: 10853_2.1.txt, 10853_3.0.txt
>
>
> I'm working on a deb job in jenkins, and I had forgotten to open a bug for
> this. There is no urgent need, since {{python-support}} is in Jessie, but
> this package is currently in transition to be removed.
> http://deb.li/dhs2p
> During deb build:
> {noformat}
> dh_pysupport: This program is deprecated, you should use dh_python2 instead.
> Migration guide: http://deb.li/dhs2p
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (CASSANDRA-10853) deb package migration to dh_python2
[
https://issues.apache.org/jira/browse/CASSANDRA-10853?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Shuler updated CASSANDRA-10853:
---
Attachment: 10853_3.0.txt
10853_2.1.txt attached for cassandra-2.1 and cassandra-2.2 branches
10853_3.0.txt attached for cassandra-3.0 and trunk branches
> deb package migration to dh_python2
> ---
>
> Key: CASSANDRA-10853
> URL: https://issues.apache.org/jira/browse/CASSANDRA-10853
> Project: Cassandra
> Issue Type: Task
> Components: Packaging
>Reporter: Michael Shuler
>Assignee: Michael Shuler
> Fix For: 3.0.x, 3.x
>
> Attachments: 10853_2.1.txt, 10853_3.0.txt
>
>
> I'm working on a deb job in jenkins, and I had forgotten to open a bug for
> this. There is no urgent need, since {{python-support}} is in Jessie, but
> this package is currently in transition to be removed.
> http://deb.li/dhs2p
> During deb build:
> {noformat}
> dh_pysupport: This program is deprecated, you should use dh_python2 instead.
> Migration guide: http://deb.li/dhs2p
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (CASSANDRA-10853) deb package migration to dh_python2
[
https://issues.apache.org/jira/browse/CASSANDRA-10853?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Shuler updated CASSANDRA-10853:
---
Attachment: 10853_2.1.txt
> deb package migration to dh_python2
> ---
>
> Key: CASSANDRA-10853
> URL: https://issues.apache.org/jira/browse/CASSANDRA-10853
> Project: Cassandra
> Issue Type: Task
> Components: Packaging
>Reporter: Michael Shuler
>Assignee: Michael Shuler
> Fix For: 3.0.x, 3.x
>
> Attachments: 10853_2.1.txt
>
>
> I'm working on a deb job in jenkins, and I had forgotten to open a bug for
> this. There is no urgent need, since {{python-support}} is in Jessie, but
> this package is currently in transition to be removed.
> http://deb.li/dhs2p
> During deb build:
> {noformat}
> dh_pysupport: This program is deprecated, you should use dh_python2 instead.
> Migration guide: http://deb.li/dhs2p
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (CASSANDRA-10853) deb package migration to dh_python2
[
https://issues.apache.org/jira/browse/CASSANDRA-10853?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Shuler updated CASSANDRA-10853:
---
Attachment: (was: 10853_minimal_wip.txt)
> deb package migration to dh_python2
> ---
>
> Key: CASSANDRA-10853
> URL: https://issues.apache.org/jira/browse/CASSANDRA-10853
> Project: Cassandra
> Issue Type: Task
> Components: Packaging
>Reporter: Michael Shuler
>Assignee: Michael Shuler
> Fix For: 3.0.x, 3.x
>
>
> I'm working on a deb job in jenkins, and I had forgotten to open a bug for
> this. There is no urgent need, since {{python-support}} is in Jessie, but
> this package is currently in transition to be removed.
> http://deb.li/dhs2p
> During deb build:
> {noformat}
> dh_pysupport: This program is deprecated, you should use dh_python2 instead.
> Migration guide: http://deb.li/dhs2p
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (CASSANDRA-11642) sstabledump and sstableverify need to be added to deb packages
[
https://issues.apache.org/jira/browse/CASSANDRA-11642?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Shuler updated CASSANDRA-11642:
---
Fix Version/s: 2.2.7
> sstabledump and sstableverify need to be added to deb packages
> --
>
> Key: CASSANDRA-11642
> URL: https://issues.apache.org/jira/browse/CASSANDRA-11642
> Project: Cassandra
> Issue Type: Bug
> Components: Tools
> Environment: OS: Debian
> Cassandra 3.5
>Reporter: Attila Szucs
>Assignee: T Jake Luciani
> Fix For: 3.6, 3.0.6, 2.2.7
>
> Attachments: CASSANDRA-11642.txt, CASSANDRA-11642_2.2.txt
>
>
> Command-line tool sstabledump is not installed on Debian.
> I used the following source:
> {code}
> deb http://www.apache.org/dist/cassandra/debian 35x main
> {code}
> with the following installation commands:
> {code}
> sudo apt-get install cassandra
> sudo apt-get install cassandra-tools
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (CASSANDRA-11642) sstabledump is not installed with cassandra-tools
[
https://issues.apache.org/jira/browse/CASSANDRA-11642?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Shuler updated CASSANDRA-11642:
---
Attachment: CASSANDRA-11642_2.2.txt
CASSANDRA-11642_2.2.txt attached for cassandra-2.2 branch
CASSANDRA-11642.txt is for cassandra-3.0 and up
> sstabledump is not installed with cassandra-tools
> -
>
> Key: CASSANDRA-11642
> URL: https://issues.apache.org/jira/browse/CASSANDRA-11642
> Project: Cassandra
> Issue Type: Bug
> Components: Tools
> Environment: OS: Debian
> Cassandra 3.5
>Reporter: Attila Szucs
>Assignee: T Jake Luciani
> Fix For: 3.6, 3.0.6
>
> Attachments: CASSANDRA-11642.txt, CASSANDRA-11642_2.2.txt
>
>
> Command-line tool sstabledump is not installed on Debian.
> I used the following source:
> {code}
> deb http://www.apache.org/dist/cassandra/debian 35x main
> {code}
> with the following installation commands:
> {code}
> sudo apt-get install cassandra
> sudo apt-get install cassandra-tools
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (CASSANDRA-11642) sstabledump and sstableverify need to be added to deb packages
[
https://issues.apache.org/jira/browse/CASSANDRA-11642?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Shuler updated CASSANDRA-11642:
---
Summary: sstabledump and sstableverify need to be added to deb packages
(was: sstabledump is not installed with cassandra-tools)
> sstabledump and sstableverify need to be added to deb packages
> --
>
> Key: CASSANDRA-11642
> URL: https://issues.apache.org/jira/browse/CASSANDRA-11642
> Project: Cassandra
> Issue Type: Bug
> Components: Tools
> Environment: OS: Debian
> Cassandra 3.5
>Reporter: Attila Szucs
>Assignee: T Jake Luciani
> Fix For: 3.6, 3.0.6
>
> Attachments: CASSANDRA-11642.txt, CASSANDRA-11642_2.2.txt
>
>
> Command-line tool sstabledump is not installed on Debian.
> I used the following source:
> {code}
> deb http://www.apache.org/dist/cassandra/debian 35x main
> {code}
> with the following installation commands:
> {code}
> sudo apt-get install cassandra
> sudo apt-get install cassandra-tools
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (CASSANDRA-11642) sstabledump is not installed with cassandra-tools
[
https://issues.apache.org/jira/browse/CASSANDRA-11642?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15256656#comment-15256656
]
Michael Shuler commented on CASSANDRA-11642:
Clarification:
- sstabledump is cassandra-3.0 branch and up
- sstableverify is cassandra-2.2 branch and up
> sstabledump is not installed with cassandra-tools
> -
>
> Key: CASSANDRA-11642
> URL: https://issues.apache.org/jira/browse/CASSANDRA-11642
> Project: Cassandra
> Issue Type: Bug
> Components: Tools
> Environment: OS: Debian
> Cassandra 3.5
>Reporter: Attila Szucs
>Assignee: T Jake Luciani
> Fix For: 3.6, 3.0.6
>
> Attachments: CASSANDRA-11642.txt
>
>
> Command-line tool sstabledump is not installed on Debian.
> I used the following source:
> {code}
> deb http://www.apache.org/dist/cassandra/debian 35x main
> {code}
> with the following installation commands:
> {code}
> sudo apt-get install cassandra
> sudo apt-get install cassandra-tools
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (CASSANDRA-11642) sstabledump is not installed with cassandra-tools
[
https://issues.apache.org/jira/browse/CASSANDRA-11642?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Shuler updated CASSANDRA-11642:
---
Attachment: CASSANDRA-11642.txt
stress is already in the cassandra package, but we're missing sstableverify,
too. Patch attached.
> sstabledump is not installed with cassandra-tools
> -
>
> Key: CASSANDRA-11642
> URL: https://issues.apache.org/jira/browse/CASSANDRA-11642
> Project: Cassandra
> Issue Type: Bug
> Components: Tools
> Environment: OS: Debian
> Cassandra 3.5
>Reporter: Attila Szucs
>Assignee: T Jake Luciani
> Fix For: 3.6, 3.0.6
>
> Attachments: CASSANDRA-11642.txt
>
>
> Command-line tool sstabledump is not installed on Debian.
> I used the following source:
> {code}
> deb http://www.apache.org/dist/cassandra/debian 35x main
> {code}
> with the following installation commands:
> {code}
> sudo apt-get install cassandra
> sudo apt-get install cassandra-tools
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (CASSANDRA-11630) Make cython optional in pylib/setup.py
[
https://issues.apache.org/jira/browse/CASSANDRA-11630?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Shuler updated CASSANDRA-11630:
---
Attachment: (was: cassandra_3.4_amd64.build)
> Make cython optional in pylib/setup.py
> --
>
> Key: CASSANDRA-11630
> URL: https://issues.apache.org/jira/browse/CASSANDRA-11630
> Project: Cassandra
> Issue Type: Bug
> Components: Tools
>Reporter: Stefania
>Assignee: Stefania
> Fix For: 2.1.x, 2.2.x, 3.0.x, 3.x
>
> Attachments: cassandra_3.4_amd64.build.txt
>
>
> When building deb packages, we currently run [this
> line|https://github.com/apache/cassandra/blob/trunk/debian/rules#L33-L34]:
> {code}
> cd pylib && python setup.py install --no-compile --install-layout deb \
> --root $(CURDIR)/debian/cassandra
> {code}
> Since CASSANDRA-11053 was introduced, this will build the cython extensions
> for _copyutil.py_.
> We should change _setup.py_ so that when we specify {{--no-compile}} then the
> cython extensions are not built, in a similar way to what is done for the
> Python driver.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (CASSANDRA-11630) Make cython optional in pylib/setup.py
[
https://issues.apache.org/jira/browse/CASSANDRA-11630?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Shuler updated CASSANDRA-11630:
---
Attachment: cassandra_3.4_amd64.build.txt
> Make cython optional in pylib/setup.py
> --
>
> Key: CASSANDRA-11630
> URL: https://issues.apache.org/jira/browse/CASSANDRA-11630
> Project: Cassandra
> Issue Type: Bug
> Components: Tools
>Reporter: Stefania
>Assignee: Stefania
> Fix For: 2.1.x, 2.2.x, 3.0.x, 3.x
>
> Attachments: cassandra_3.4_amd64.build.txt
>
>
> When building deb packages, we currently run [this
> line|https://github.com/apache/cassandra/blob/trunk/debian/rules#L33-L34]:
> {code}
> cd pylib && python setup.py install --no-compile --install-layout deb \
> --root $(CURDIR)/debian/cassandra
> {code}
> Since CASSANDRA-11053 was introduced, this will build the cython extensions
> for _copyutil.py_.
> We should change _setup.py_ so that when we specify {{--no-compile}} then the
> cython extensions are not built, in a similar way to what is done for the
> Python driver.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (CASSANDRA-11630) Make cython optional in pylib/setup.py
[
https://issues.apache.org/jira/browse/CASSANDRA-11630?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Shuler updated CASSANDRA-11630:
---
Attachment: cassandra_3.4_amd64.build
pbuilder log of trunk commit 7afc157 + patch attached for fun (says 3.4, since
that's what's currently in debian/changelog)
> Make cython optional in pylib/setup.py
> --
>
> Key: CASSANDRA-11630
> URL: https://issues.apache.org/jira/browse/CASSANDRA-11630
> Project: Cassandra
> Issue Type: Bug
> Components: Tools
>Reporter: Stefania
>Assignee: Stefania
> Fix For: 2.1.x, 2.2.x, 3.0.x, 3.x
>
> Attachments: cassandra_3.4_amd64.build
>
>
> When building deb packages, we currently run [this
> line|https://github.com/apache/cassandra/blob/trunk/debian/rules#L33-L34]:
> {code}
> cd pylib && python setup.py install --no-compile --install-layout deb \
> --root $(CURDIR)/debian/cassandra
> {code}
> Since CASSANDRA-11053 was introduced, this will build the cython extensions
> for _copyutil.py_.
> We should change _setup.py_ so that when we specify {{--no-compile}} then the
> cython extensions are not built, in a similar way to what is done for the
> Python driver.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (CASSANDRA-11630) Make cython optional in pylib/setup.py
[
https://issues.apache.org/jira/browse/CASSANDRA-11630?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15254751#comment-15254751
]
Michael Shuler commented on CASSANDRA-11630:
Your patch works perfectly to suppress the cython build of copyutil and the
need for the build dependency in our deb build. Thanks!
> Make cython optional in pylib/setup.py
> --
>
> Key: CASSANDRA-11630
> URL: https://issues.apache.org/jira/browse/CASSANDRA-11630
> Project: Cassandra
> Issue Type: Bug
> Components: Tools
>Reporter: Stefania
>Assignee: Stefania
> Fix For: 2.1.x, 2.2.x, 3.0.x, 3.x
>
>
> When building deb packages, we currently run [this
> line|https://github.com/apache/cassandra/blob/trunk/debian/rules#L33-L34]:
> {code}
> cd pylib && python setup.py install --no-compile --install-layout deb \
> --root $(CURDIR)/debian/cassandra
> {code}
> Since CASSANDRA-11053 was introduced, this will build the cython extensions
> for _copyutil.py_.
> We should change _setup.py_ so that when we specify {{--no-compile}} then the
> cython extensions are not built, in a similar way to what is done for the
> Python driver.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (CASSANDRA-11630) Make cython optional in pylib/setup.py
[
https://issues.apache.org/jira/browse/CASSANDRA-11630?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Shuler updated CASSANDRA-11630:
---
Tester: Michael Shuler
> Make cython optional in pylib/setup.py
> --
>
> Key: CASSANDRA-11630
> URL: https://issues.apache.org/jira/browse/CASSANDRA-11630
> Project: Cassandra
> Issue Type: Bug
> Components: Tools
>Reporter: Stefania
>Assignee: Stefania
> Fix For: 2.1.x, 2.2.x, 3.0.x, 3.x
>
>
> When building deb packages, we currently run [this
> line|https://github.com/apache/cassandra/blob/trunk/debian/rules#L33-L34]:
> {code}
> cd pylib && python setup.py install --no-compile --install-layout deb \
> --root $(CURDIR)/debian/cassandra
> {code}
> Since CASSANDRA-11053 was introduced, this will build the cython extensions
> for _copyutil.py_.
> We should change _setup.py_ so that when we specify {{--no-compile}} then the
> cython extensions are not built, in a similar way to what is done for the
> Python driver.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (CASSANDRA-11636) dtest failure in auth_test.TestAuth.restart_node_doesnt_lose_auth_data_test
Michael Shuler created CASSANDRA-11636:
--
Summary: dtest failure in
auth_test.TestAuth.restart_node_doesnt_lose_auth_data_test
Key: CASSANDRA-11636
URL: https://issues.apache.org/jira/browse/CASSANDRA-11636
Project: Cassandra
Issue Type: Test
Reporter: Michael Shuler
Assignee: DS Test Eng
example failure:
http://cassci.datastax.com/job/cassandra-2.1_dtest/448/testReport/auth_test/TestAuth/restart_node_doesnt_lose_auth_data_test
Failed on CassCI build cassandra-2.1_dtest #448 - 2.1.14-tentative
{noformat}
Error Message
Problem stopping node node1
>> begin captured logging <<
dtest: DEBUG: cluster ccm directory: /mnt/tmp/dtest-sLlSHx
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: Default role created by node1
- >> end captured logging << -
Stacktrace
File "/usr/lib/python2.7/unittest/case.py", line 329, in run
testMethod()
File "/home/automaton/cassandra-dtest/auth_test.py", line 910, in
restart_node_doesnt_lose_auth_data_test
self.cluster.stop()
File "/home/automaton/ccm/ccmlib/cluster.py", line 376, in stop
if not node.stop(wait, gently=gently):
File "/home/automaton/ccm/ccmlib/node.py", line 677, in stop
raise NodeError("Problem stopping node %s" % self.name)
"Problem stopping node node1\n >> begin captured logging <<
\ndtest: DEBUG: cluster ccm directory:
/mnt/tmp/dtest-sLlSHx\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'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\n- >>
end captured logging << -"
{noformat}
This test was successful in the next build on a commit that does not appear to
be auth-related, and the test does not appear to be flappy. Looping over the
test, I have not gotten a failure.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (CASSANDRA-11635) test-clientutil-jar unit test fails
[
https://issues.apache.org/jira/browse/CASSANDRA-11635?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Shuler updated CASSANDRA-11635:
---
Fix Version/s: 3.0.x
2.2.x
> test-clientutil-jar unit test fails
> ---
>
> Key: CASSANDRA-11635
> URL: https://issues.apache.org/jira/browse/CASSANDRA-11635
> Project: Cassandra
> Issue Type: Test
> Components: Testing
>Reporter: Michael Shuler
> Labels: unittest
> Fix For: 2.2.x, 3.0.x, 3.x
>
>
> {noformat}
> test-clientutil-jar:
> [junit] Testsuite: org.apache.cassandra.serializers.ClientUtilsTest
> [junit] Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed:
> 0.314 sec
> [junit]
> [junit] Testcase: test(org.apache.cassandra.serializers.ClientUtilsTest):
> Caused an ERROR
> [junit] org/apache/cassandra/utils/SigarLibrary
> [junit] java.lang.NoClassDefFoundError:
> org/apache/cassandra/utils/SigarLibrary
> [junit] at org.apache.cassandra.utils.UUIDGen.hash(UUIDGen.java:328)
> [junit] at
> org.apache.cassandra.utils.UUIDGen.makeNode(UUIDGen.java:307)
> [junit] at
> org.apache.cassandra.utils.UUIDGen.makeClockSeqAndNode(UUIDGen.java:256)
> [junit] at
> org.apache.cassandra.utils.UUIDGen.(UUIDGen.java:39)
> [junit] at
> org.apache.cassandra.serializers.ClientUtilsTest.test(ClientUtilsTest.java:56)
> [junit] Caused by: java.lang.ClassNotFoundException:
> org.apache.cassandra.utils.SigarLibrary
> [junit] at java.net.URLClassLoader.findClass(URLClassLoader.java:381)
> [junit] at java.lang.ClassLoader.loadClass(ClassLoader.java:424)
> [junit] at
> sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:331)
> [junit] at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
> [junit]
> [junit]
> [junit] Test org.apache.cassandra.serializers.ClientUtilsTest FAILED
> BUILD FAILED
> {noformat}
> I'll see if I can find a spot where this passes, but it appears to have been
> failing for a long time.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (CASSANDRA-11635) test-clientutil-jar unit test fails
[
https://issues.apache.org/jira/browse/CASSANDRA-11635?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15254185#comment-15254185
]
Michael Shuler commented on CASSANDRA-11635:
Setting fixver from git without testing them all.
{noformat}
$ git branch -r --contains 47e8ef9
origin/HEAD -> origin/trunk
origin/cassandra-2.2
origin/cassandra-3.0
origin/cassandra-3.5
origin/trunk
{noformat}
> test-clientutil-jar unit test fails
> ---
>
> Key: CASSANDRA-11635
> URL: https://issues.apache.org/jira/browse/CASSANDRA-11635
> Project: Cassandra
> Issue Type: Test
> Components: Testing
>Reporter: Michael Shuler
> Labels: unittest
> Fix For: 3.x
>
>
> {noformat}
> test-clientutil-jar:
> [junit] Testsuite: org.apache.cassandra.serializers.ClientUtilsTest
> [junit] Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed:
> 0.314 sec
> [junit]
> [junit] Testcase: test(org.apache.cassandra.serializers.ClientUtilsTest):
> Caused an ERROR
> [junit] org/apache/cassandra/utils/SigarLibrary
> [junit] java.lang.NoClassDefFoundError:
> org/apache/cassandra/utils/SigarLibrary
> [junit] at org.apache.cassandra.utils.UUIDGen.hash(UUIDGen.java:328)
> [junit] at
> org.apache.cassandra.utils.UUIDGen.makeNode(UUIDGen.java:307)
> [junit] at
> org.apache.cassandra.utils.UUIDGen.makeClockSeqAndNode(UUIDGen.java:256)
> [junit] at
> org.apache.cassandra.utils.UUIDGen.(UUIDGen.java:39)
> [junit] at
> org.apache.cassandra.serializers.ClientUtilsTest.test(ClientUtilsTest.java:56)
> [junit] Caused by: java.lang.ClassNotFoundException:
> org.apache.cassandra.utils.SigarLibrary
> [junit] at java.net.URLClassLoader.findClass(URLClassLoader.java:381)
> [junit] at java.lang.ClassLoader.loadClass(ClassLoader.java:424)
> [junit] at
> sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:331)
> [junit] at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
> [junit]
> [junit]
> [junit] Test org.apache.cassandra.serializers.ClientUtilsTest FAILED
> BUILD FAILED
> {noformat}
> I'll see if I can find a spot where this passes, but it appears to have been
> failing for a long time.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (CASSANDRA-11635) test-clientutil-jar unit test fails
[
https://issues.apache.org/jira/browse/CASSANDRA-11635?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15254179#comment-15254179
]
Michael Shuler commented on CASSANDRA-11635:
Looking at the commit that bisect shows, this makes sense to me.
> test-clientutil-jar unit test fails
> ---
>
> Key: CASSANDRA-11635
> URL: https://issues.apache.org/jira/browse/CASSANDRA-11635
> Project: Cassandra
> Issue Type: Test
> Components: Testing
>Reporter: Michael Shuler
> Labels: unittest
> Fix For: 3.x
>
>
> {noformat}
> test-clientutil-jar:
> [junit] Testsuite: org.apache.cassandra.serializers.ClientUtilsTest
> [junit] Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed:
> 0.314 sec
> [junit]
> [junit] Testcase: test(org.apache.cassandra.serializers.ClientUtilsTest):
> Caused an ERROR
> [junit] org/apache/cassandra/utils/SigarLibrary
> [junit] java.lang.NoClassDefFoundError:
> org/apache/cassandra/utils/SigarLibrary
> [junit] at org.apache.cassandra.utils.UUIDGen.hash(UUIDGen.java:328)
> [junit] at
> org.apache.cassandra.utils.UUIDGen.makeNode(UUIDGen.java:307)
> [junit] at
> org.apache.cassandra.utils.UUIDGen.makeClockSeqAndNode(UUIDGen.java:256)
> [junit] at
> org.apache.cassandra.utils.UUIDGen.(UUIDGen.java:39)
> [junit] at
> org.apache.cassandra.serializers.ClientUtilsTest.test(ClientUtilsTest.java:56)
> [junit] Caused by: java.lang.ClassNotFoundException:
> org.apache.cassandra.utils.SigarLibrary
> [junit] at java.net.URLClassLoader.findClass(URLClassLoader.java:381)
> [junit] at java.lang.ClassLoader.loadClass(ClassLoader.java:424)
> [junit] at
> sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:331)
> [junit] at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
> [junit]
> [junit]
> [junit] Test org.apache.cassandra.serializers.ClientUtilsTest FAILED
> BUILD FAILED
> {noformat}
> I'll see if I can find a spot where this passes, but it appears to have been
> failing for a long time.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (CASSANDRA-11635) test-clientutil-jar unit test fails
[
https://issues.apache.org/jira/browse/CASSANDRA-11635?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15254176#comment-15254176
]
Michael Shuler commented on CASSANDRA-11635:
{noformat}
47e8ef9e9ce70c54115681f854f483a53992c988 is the first bad commit
commit 47e8ef9e9ce70c54115681f854f483a53992c988
Author: Sylvain Lebresne
Date: Fri Jan 15 15:25:03 2016 +0100
Make UUID LSB unique per-process
patch by slebresne; reviewed by benedict for CASSANDRA-7925
:100644 100644 2bfba80011c5b6c5db1508772ef54de7a75fbcc2
f571c295cccb0be22bf46526cc93d890811550ac M CHANGES.txt
:04 04 4b557fdd87eccbc61931d6ec52ba7c511adb47a0
e807214b140475a51f628deac65b8f8c60b77541 M src
bisect run success
{noformat}
> test-clientutil-jar unit test fails
> ---
>
> Key: CASSANDRA-11635
> URL: https://issues.apache.org/jira/browse/CASSANDRA-11635
> Project: Cassandra
> Issue Type: Test
> Components: Testing
>Reporter: Michael Shuler
> Labels: unittest
> Fix For: 3.x
>
>
> {noformat}
> test-clientutil-jar:
> [junit] Testsuite: org.apache.cassandra.serializers.ClientUtilsTest
> [junit] Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed:
> 0.314 sec
> [junit]
> [junit] Testcase: test(org.apache.cassandra.serializers.ClientUtilsTest):
> Caused an ERROR
> [junit] org/apache/cassandra/utils/SigarLibrary
> [junit] java.lang.NoClassDefFoundError:
> org/apache/cassandra/utils/SigarLibrary
> [junit] at org.apache.cassandra.utils.UUIDGen.hash(UUIDGen.java:328)
> [junit] at
> org.apache.cassandra.utils.UUIDGen.makeNode(UUIDGen.java:307)
> [junit] at
> org.apache.cassandra.utils.UUIDGen.makeClockSeqAndNode(UUIDGen.java:256)
> [junit] at
> org.apache.cassandra.utils.UUIDGen.(UUIDGen.java:39)
> [junit] at
> org.apache.cassandra.serializers.ClientUtilsTest.test(ClientUtilsTest.java:56)
> [junit] Caused by: java.lang.ClassNotFoundException:
> org.apache.cassandra.utils.SigarLibrary
> [junit] at java.net.URLClassLoader.findClass(URLClassLoader.java:381)
> [junit] at java.lang.ClassLoader.loadClass(ClassLoader.java:424)
> [junit] at
> sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:331)
> [junit] at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
> [junit]
> [junit]
> [junit] Test org.apache.cassandra.serializers.ClientUtilsTest FAILED
> BUILD FAILED
> {noformat}
> I'll see if I can find a spot where this passes, but it appears to have been
> failing for a long time.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (CASSANDRA-10756) Timeout failures in NativeTransportService.testConcurrentDestroys unit test
[
https://issues.apache.org/jira/browse/CASSANDRA-10756?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Shuler updated CASSANDRA-10756:
---
Tester: Michael Shuler
> Timeout failures in NativeTransportService.testConcurrentDestroys unit test
> ---
>
> Key: CASSANDRA-10756
> URL: https://issues.apache.org/jira/browse/CASSANDRA-10756
> Project: Cassandra
> Issue Type: Bug
>Reporter: Joel Knighton
>Assignee: Alex Petrov
> Fix For: 3.x
>
>
> History of test on trunk
> [here|http://cassci.datastax.com/job/trunk_testall/lastCompletedBuild/testReport/org.apache.cassandra.service/NativeTransportServiceTest/testConcurrentDestroys/history/].
> I've seen these failures across 3.0/trunk for a while. I ran the test looping
> locally for a while and the timeout is fairly easy to reproduce. The timeout
> appears to be an indefinite hang and not a timing issue.
> When the timeout occurs, the following stack trace is at the end of the logs
> for the unit test.
> {code}
> ERROR [ForkJoinPool.commonPool-worker-1] 2015-11-22 21:30:53,635 Failed to
> submit a listener notification task. Event loop shut down?
> java.util.concurrent.RejectedExecutionException: event executor terminated
> at
> io.netty.util.concurrent.SingleThreadEventExecutor.reject(SingleThreadEventExecutor.java:745)
> ~[netty-all-4.0.23.Final.jar:4.0.23.Final]
> at
> io.netty.util.concurrent.SingleThreadEventExecutor.addTask(SingleThreadEventExecutor.java:322)
> ~[netty-all-4.0.23.Final.jar:4.0.23.Final]
> at
> io.netty.util.concurrent.SingleThreadEventExecutor.execute(SingleThreadEventExecutor.java:728)
> ~[netty-all-4.0.23.Final.jar:4.0.23.Final]
> at
> io.netty.util.concurrent.DefaultPromise.execute(DefaultPromise.java:671)
> [netty-all-4.0.23.Final.jar:4.0.23.Final]
> at
> io.netty.util.concurrent.DefaultPromise.notifyLateListener(DefaultPromise.java:641)
> [netty-all-4.0.23.Final.jar:4.0.23.Final]
> at
> io.netty.util.concurrent.DefaultPromise.addListener(DefaultPromise.java:138)
> [netty-all-4.0.23.Final.jar:4.0.23.Final]
> at
> io.netty.channel.DefaultChannelPromise.addListener(DefaultChannelPromise.java:93)
> [netty-all-4.0.23.Final.jar:4.0.23.Final]
> at
> io.netty.channel.DefaultChannelPromise.addListener(DefaultChannelPromise.java:28)
> [netty-all-4.0.23.Final.jar:4.0.23.Final]
> at
> io.netty.channel.group.DefaultChannelGroupFuture.(DefaultChannelGroupFuture.java:116)
> [netty-all-4.0.23.Final.jar:4.0.23.Final]
> at
> io.netty.channel.group.DefaultChannelGroup.close(DefaultChannelGroup.java:275)
> [netty-all-4.0.23.Final.jar:4.0.23.Final]
> at
> io.netty.channel.group.DefaultChannelGroup.close(DefaultChannelGroup.java:167)
> [netty-all-4.0.23.Final.jar:4.0.23.Final]
> at
> org.apache.cassandra.transport.Server$ConnectionTracker.closeAll(Server.java:277)
> [main/:na]
> at org.apache.cassandra.transport.Server.close(Server.java:180)
> [main/:na]
> at org.apache.cassandra.transport.Server.stop(Server.java:116)
> [main/:na]
> at java.util.Collections$SingletonSet.forEach(Collections.java:4767)
> ~[na:1.8.0_60]
> at
> org.apache.cassandra.service.NativeTransportService.stop(NativeTransportService.java:136)
> ~[main/:na]
> at
> org.apache.cassandra.service.NativeTransportService.destroy(NativeTransportService.java:144)
> ~[main/:na]
> at
> org.apache.cassandra.service.NativeTransportServiceTest.lambda$withService$102(NativeTransportServiceTest.java:201)
> ~[classes/:na]
> at java.util.stream.IntPipeline$3$1.accept(IntPipeline.java:233)
> ~[na:1.8.0_60]
> at
> java.util.stream.Streams$RangeIntSpliterator.forEachRemaining(Streams.java:110)
> ~[na:1.8.0_60]
> at java.util.Spliterator$OfInt.forEachRemaining(Spliterator.java:693)
> ~[na:1.8.0_60]
> at
> java.util.stream.AbstractPipeline.copyInto(AbstractPipeline.java:481)
> ~[na:1.8.0_60]
> at
> java.util.stream.AbstractPipeline.wrapAndCopyInto(AbstractPipeline.java:471)
> ~[na:1.8.0_60]
> at java.util.stream.ReduceOps$ReduceTask.doLeaf(ReduceOps.java:747)
> ~[na:1.8.0_60]
> at java.util.stream.ReduceOps$ReduceTask.doLeaf(ReduceOps.java:721)
> ~[na:1.8.0_60]
> at java.util.stream.AbstractTask.compute(AbstractTask.java:316)
> ~[na:1.8.0_60]
> at
> java.util.concurrent.CountedCompleter.exec(CountedCompleter.java:731)
> ~[na:1.8.0_60]
> at java.util.concurrent.ForkJoinTask.doExec(ForkJoinTask.java:289)
> ~[na:1.8.0_60]
> at
> java.util.concurrent.ForkJoinPool$WorkQueue.runTask(ForkJoinPool.java:1056)
> ~[na:1.8.0_60]
> at java.util.concurrent.ForkJoinPool.runWorker(ForkJoinPool.java:1692)
> ~[na:1.8.0_60]
> at
>
[jira] [Commented] (CASSANDRA-10756) Timeout failures in NativeTransportService.testConcurrentDestroys unit test
[
https://issues.apache.org/jira/browse/CASSANDRA-10756?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15254114#comment-15254114
]
Michael Shuler commented on CASSANDRA-10756:
I patched trunk at commit 7afc157 and looped over {{ant test
-Dtest.name=NativeTransportServiceTest}} 80+ times and {{ant test-compression
-Dtest.name=NativeTransportServiceTest}} 110+ times with no failures. LGTM from
a test perspective.
> Timeout failures in NativeTransportService.testConcurrentDestroys unit test
> ---
>
> Key: CASSANDRA-10756
> URL: https://issues.apache.org/jira/browse/CASSANDRA-10756
> Project: Cassandra
> Issue Type: Bug
>Reporter: Joel Knighton
>Assignee: Alex Petrov
> Fix For: 3.x
>
>
> History of test on trunk
> [here|http://cassci.datastax.com/job/trunk_testall/lastCompletedBuild/testReport/org.apache.cassandra.service/NativeTransportServiceTest/testConcurrentDestroys/history/].
> I've seen these failures across 3.0/trunk for a while. I ran the test looping
> locally for a while and the timeout is fairly easy to reproduce. The timeout
> appears to be an indefinite hang and not a timing issue.
> When the timeout occurs, the following stack trace is at the end of the logs
> for the unit test.
> {code}
> ERROR [ForkJoinPool.commonPool-worker-1] 2015-11-22 21:30:53,635 Failed to
> submit a listener notification task. Event loop shut down?
> java.util.concurrent.RejectedExecutionException: event executor terminated
> at
> io.netty.util.concurrent.SingleThreadEventExecutor.reject(SingleThreadEventExecutor.java:745)
> ~[netty-all-4.0.23.Final.jar:4.0.23.Final]
> at
> io.netty.util.concurrent.SingleThreadEventExecutor.addTask(SingleThreadEventExecutor.java:322)
> ~[netty-all-4.0.23.Final.jar:4.0.23.Final]
> at
> io.netty.util.concurrent.SingleThreadEventExecutor.execute(SingleThreadEventExecutor.java:728)
> ~[netty-all-4.0.23.Final.jar:4.0.23.Final]
> at
> io.netty.util.concurrent.DefaultPromise.execute(DefaultPromise.java:671)
> [netty-all-4.0.23.Final.jar:4.0.23.Final]
> at
> io.netty.util.concurrent.DefaultPromise.notifyLateListener(DefaultPromise.java:641)
> [netty-all-4.0.23.Final.jar:4.0.23.Final]
> at
> io.netty.util.concurrent.DefaultPromise.addListener(DefaultPromise.java:138)
> [netty-all-4.0.23.Final.jar:4.0.23.Final]
> at
> io.netty.channel.DefaultChannelPromise.addListener(DefaultChannelPromise.java:93)
> [netty-all-4.0.23.Final.jar:4.0.23.Final]
> at
> io.netty.channel.DefaultChannelPromise.addListener(DefaultChannelPromise.java:28)
> [netty-all-4.0.23.Final.jar:4.0.23.Final]
> at
> io.netty.channel.group.DefaultChannelGroupFuture.(DefaultChannelGroupFuture.java:116)
> [netty-all-4.0.23.Final.jar:4.0.23.Final]
> at
> io.netty.channel.group.DefaultChannelGroup.close(DefaultChannelGroup.java:275)
> [netty-all-4.0.23.Final.jar:4.0.23.Final]
> at
> io.netty.channel.group.DefaultChannelGroup.close(DefaultChannelGroup.java:167)
> [netty-all-4.0.23.Final.jar:4.0.23.Final]
> at
> org.apache.cassandra.transport.Server$ConnectionTracker.closeAll(Server.java:277)
> [main/:na]
> at org.apache.cassandra.transport.Server.close(Server.java:180)
> [main/:na]
> at org.apache.cassandra.transport.Server.stop(Server.java:116)
> [main/:na]
> at java.util.Collections$SingletonSet.forEach(Collections.java:4767)
> ~[na:1.8.0_60]
> at
> org.apache.cassandra.service.NativeTransportService.stop(NativeTransportService.java:136)
> ~[main/:na]
> at
> org.apache.cassandra.service.NativeTransportService.destroy(NativeTransportService.java:144)
> ~[main/:na]
> at
> org.apache.cassandra.service.NativeTransportServiceTest.lambda$withService$102(NativeTransportServiceTest.java:201)
> ~[classes/:na]
> at java.util.stream.IntPipeline$3$1.accept(IntPipeline.java:233)
> ~[na:1.8.0_60]
> at
> java.util.stream.Streams$RangeIntSpliterator.forEachRemaining(Streams.java:110)
> ~[na:1.8.0_60]
> at java.util.Spliterator$OfInt.forEachRemaining(Spliterator.java:693)
> ~[na:1.8.0_60]
> at
> java.util.stream.AbstractPipeline.copyInto(AbstractPipeline.java:481)
> ~[na:1.8.0_60]
> at
> java.util.stream.AbstractPipeline.wrapAndCopyInto(AbstractPipeline.java:471)
> ~[na:1.8.0_60]
> at java.util.stream.ReduceOps$ReduceTask.doLeaf(ReduceOps.java:747)
> ~[na:1.8.0_60]
> at java.util.stream.ReduceOps$ReduceTask.doLeaf(ReduceOps.java:721)
> ~[na:1.8.0_60]
> at java.util.stream.AbstractTask.compute(AbstractTask.java:316)
> ~[na:1.8.0_60]
> at
> java.util.concurrent.CountedCompleter.exec(CountedCompleter.java:731)
> ~[na:1.8.0_60]
> at java.util.concurrent.ForkJoinTask.doExec(ForkJoinTask.java:289)
>
[jira] [Created] (CASSANDRA-11635) test-clientutil-jar unit test fails
Michael Shuler created CASSANDRA-11635:
--
Summary: test-clientutil-jar unit test fails
Key: CASSANDRA-11635
URL: https://issues.apache.org/jira/browse/CASSANDRA-11635
Project: Cassandra
Issue Type: Test
Components: Testing
Reporter: Michael Shuler
Fix For: 3.x
{noformat}
test-clientutil-jar:
[junit] Testsuite: org.apache.cassandra.serializers.ClientUtilsTest
[junit] Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed:
0.314 sec
[junit]
[junit] Testcase: test(org.apache.cassandra.serializers.ClientUtilsTest):
Caused an ERROR
[junit] org/apache/cassandra/utils/SigarLibrary
[junit] java.lang.NoClassDefFoundError:
org/apache/cassandra/utils/SigarLibrary
[junit] at org.apache.cassandra.utils.UUIDGen.hash(UUIDGen.java:328)
[junit] at org.apache.cassandra.utils.UUIDGen.makeNode(UUIDGen.java:307)
[junit] at
org.apache.cassandra.utils.UUIDGen.makeClockSeqAndNode(UUIDGen.java:256)
[junit] at org.apache.cassandra.utils.UUIDGen.(UUIDGen.java:39)
[junit] at
org.apache.cassandra.serializers.ClientUtilsTest.test(ClientUtilsTest.java:56)
[junit] Caused by: java.lang.ClassNotFoundException:
org.apache.cassandra.utils.SigarLibrary
[junit] at java.net.URLClassLoader.findClass(URLClassLoader.java:381)
[junit] at java.lang.ClassLoader.loadClass(ClassLoader.java:424)
[junit] at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:331)
[junit] at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
[junit]
[junit]
[junit] Test org.apache.cassandra.serializers.ClientUtilsTest FAILED
BUILD FAILED
{noformat}
I'll see if I can find a spot where this passes, but it appears to have been
failing for a long time.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (CASSANDRA-11574) COPY FROM command in cqlsh throws error
[ https://issues.apache.org/jira/browse/CASSANDRA-11574?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15252316#comment-15252316 ] Michael Shuler commented on CASSANDRA-11574: The deb rules builds the .so with a patch I am working on for CASSANDRA-10853, since cython is a new dependency. I assume Jake has cython installed by chance, otherwise the deb build exits. https://github.com/apache/cassandra/blob/trunk/debian/rules#L33-L34 > COPY FROM command in cqlsh throws error > --- > > Key: CASSANDRA-11574 > URL: https://issues.apache.org/jira/browse/CASSANDRA-11574 > Project: Cassandra > Issue Type: Bug > Components: Tools > Environment: Operating System: Ubuntu Server 14.04 > JDK: Oracle JDK 8 update 77 > Python: 2.7.6 >Reporter: Mahafuzur Rahman >Assignee: Stefania > Labels: cqlsh > Fix For: 2.1.x, 2.2.x, 3.0.x, 3.x > > > Any COPY FROM command in cqlsh is throwing the following error: > "get_num_processes() takes no keyword arguments" > Example command: > COPY inboxdata > (to_user_id,to_user_network,created_time,attachments,from_user_id,from_user_name,from_user_network,id,message,to_user_name,updated_time) > FROM 'inbox.csv'; > Similar commands worked parfectly in the previous versions such as 3.0.4 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CASSANDRA-10853) deb package migration to dh_python2
[
https://issues.apache.org/jira/browse/CASSANDRA-10853?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Shuler updated CASSANDRA-10853:
---
Attachment: 10853_minimal_wip.txt
10853_minimal_wip.txt patch attached, but I have another branch with additional
changes to come.
> deb package migration to dh_python2
> ---
>
> Key: CASSANDRA-10853
> URL: https://issues.apache.org/jira/browse/CASSANDRA-10853
> Project: Cassandra
> Issue Type: Task
> Components: Packaging
>Reporter: Michael Shuler
>Assignee: Michael Shuler
> Fix For: 3.0.x, 3.x
>
> Attachments: 10853_minimal_wip.txt
>
>
> I'm working on a deb job in jenkins, and I had forgotten to open a bug for
> this. There is no urgent need, since {{python-support}} is in Jessie, but
> this package is currently in transition to be removed.
> http://deb.li/dhs2p
> During deb build:
> {noformat}
> dh_pysupport: This program is deprecated, you should use dh_python2 instead.
> Migration guide: http://deb.li/dhs2p
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (CASSANDRA-10853) deb package migration to dh_python2
[
https://issues.apache.org/jira/browse/CASSANDRA-10853?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15246944#comment-15246944
]
Michael Shuler commented on CASSANDRA-10853:
Ubuntu 16.04 x86_64 looks happy with some minimal deb build updates to migrate
to dh_python2, but it also looks like we're missing at least sstabledump in
trunk:
{noformat}
$ ssh 192.168.56.102
Warning: Permanently added '192.168.56.102' (ECDSA) to the list of known hosts.
Welcome to Ubuntu 16.04 LTS (GNU/Linux 4.4.0-18-generic x86_64)
<...>
$ sudo dpkg -i cassandra*.deb
Selecting previously unselected package cassandra.
(Reading database ... 59234 files and directories currently installed.)
Preparing to unpack cassandra_3.4_all.deb ...
Unpacking cassandra (3.4) ...
Selecting previously unselected package cassandra-tools.
Preparing to unpack cassandra-tools_3.4_all.deb ...
Unpacking cassandra-tools (3.4) ...
Setting up cassandra (3.4) ...
vm.max_map_count = 1048575
net.ipv4.tcp_keepalive_time = 300
update-rc.d: warning: start and stop actions are no longer supported; falling
back to defaults
Setting up cassandra-tools (3.4) ...
Processing triggers for ureadahead (0.100.0-19) ...
Processing triggers for systemd (229-4ubuntu4) ...
$ cqlsh
Connected to Test Cluster at 127.0.0.1:9042.
[cqlsh 5.0.1 | Cassandra 3.4 | CQL spec 3.4.2 | Native protocol v4]
Use HELP for help.
cqlsh> DESC TABLES
Keyspace system_traces
--
events sessions
Keyspace system_schema
--
tables triggersviewskeyspaces dropped_columns
functions aggregates indexes types columns
Keyspace system_auth
resource_role_permissons_index role_permissions role_members roles
Keyspace system
---
available_ranges peers paxos range_xfers
batches compaction_history batchloglocal
"IndexInfo" sstable_activitysize_estimates hints
views_builds_in_progress peer_events built_views
Keyspace system_distributed
---
repair_history view_build_status parent_repair_history
cqlsh>
{noformat}
> deb package migration to dh_python2
> ---
>
> Key: CASSANDRA-10853
> URL: https://issues.apache.org/jira/browse/CASSANDRA-10853
> Project: Cassandra
> Issue Type: Task
> Components: Packaging
>Reporter: Michael Shuler
>Assignee: Michael Shuler
> Fix For: 3.0.x, 3.x
>
>
> I'm working on a deb job in jenkins, and I had forgotten to open a bug for
> this. There is no urgent need, since {{python-support}} is in Jessie, but
> this package is currently in transition to be removed.
> http://deb.li/dhs2p
> During deb build:
> {noformat}
> dh_pysupport: This program is deprecated, you should use dh_python2 instead.
> Migration guide: http://deb.li/dhs2p
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (CASSANDRA-10853) deb package migration to dh_python2
[
https://issues.apache.org/jira/browse/CASSANDRA-10853?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15246724#comment-15246724
]
Michael Shuler commented on CASSANDRA-10853:
Verifying that we still run on i386, without an i386 shared lib, which appears
to be difficult to try to build with cython:
{noformat}
mshuler@debian:~$ dpkg --print-architecture
i386
mshuler@debian:~$ ls -l /usr/lib/python2.7/dist-packages/cqlshlib/copyutil.*
-rw-r--r-- 1 root root 101082 Apr 18 13:48
/usr/lib/python2.7/dist-packages/cqlshlib/copyutil.py
-rw-r--r-- 1 root root 102345 Apr 18 17:37
/usr/lib/python2.7/dist-packages/cqlshlib/copyutil.pyc
-rw-r--r-- 1 root root 6194568 Apr 18 14:08
/usr/lib/python2.7/dist-packages/cqlshlib/copyutil.x86_64-linux-gnu.so
mshuler@debian:~$ cqlsh
Connected to Test Cluster at 127.0.0.1:9042.
[cqlsh 5.0.1 | Cassandra 3.4 | CQL spec 3.4.2 | Native protocol v4]
Use HELP for help.
cqlsh>
{noformat}
In another shell, nothing is returned by {{lsof |grep cqlshlib}}. We could
probably jump through a bunch of hoops to build both x86_64 and i386 .so files,
but it's not a simple task. IMO, building the 64-bit .so and accepting the fact
that 32-bit users won't benefit from the C extension is probably fine.
> deb package migration to dh_python2
> ---
>
> Key: CASSANDRA-10853
> URL: https://issues.apache.org/jira/browse/CASSANDRA-10853
> Project: Cassandra
> Issue Type: Task
> Components: Packaging
>Reporter: Michael Shuler
>Assignee: Michael Shuler
> Fix For: 3.0.x, 3.x
>
>
> I'm working on a deb job in jenkins, and I had forgotten to open a bug for
> this. There is no urgent need, since {{python-support}} is in Jessie, but
> this package is currently in transition to be removed.
> http://deb.li/dhs2p
> During deb build:
> {noformat}
> dh_pysupport: This program is deprecated, you should use dh_python2 instead.
> Migration guide: http://deb.li/dhs2p
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (CASSANDRA-10853) deb package migration to dh_python2
[
https://issues.apache.org/jira/browse/CASSANDRA-10853?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15246610#comment-15246610
]
Michael Shuler commented on CASSANDRA-10853:
Stripping the shared lib reduces the .so file size by almost 80% - could
probably include that step at build time
{noformat}
$ sudo lsof |grep cqlshlib
python 7879 mshuler mem REG8,11338464
3545695 /usr/lib/python2.7/dist-packages/cqlshlib/copyutil.x86_64-linux-gnu.so
python 7879 7887 mshuler mem REG8,11338464
3545695 /usr/lib/python2.7/dist-packages/cqlshlib/copyutil.x86_64-linux-gnu.so
python 7879 7888 mshuler mem REG8,11338464
3545695 /usr/lib/python2.7/dist-packages/cqlshlib/copyutil.x86_64-linux-gnu.so
python 7879 7892 mshuler mem REG8,11338464
3545695 /usr/lib/python2.7/dist-packages/cqlshlib/copyutil.x86_64-linux-gnu.so
python 7879 7893 mshuler mem REG8,11338464
3545695 /usr/lib/python2.7/dist-packages/cqlshlib/copyutil.x86_64-linux-gnu.so
{noformat}
> deb package migration to dh_python2
> ---
>
> Key: CASSANDRA-10853
> URL: https://issues.apache.org/jira/browse/CASSANDRA-10853
> Project: Cassandra
> Issue Type: Task
> Components: Packaging
>Reporter: Michael Shuler
>Assignee: Michael Shuler
> Fix For: 3.0.x, 3.x
>
>
> I'm working on a deb job in jenkins, and I had forgotten to open a bug for
> this. There is no urgent need, since {{python-support}} is in Jessie, but
> this package is currently in transition to be removed.
> http://deb.li/dhs2p
> During deb build:
> {noformat}
> dh_pysupport: This program is deprecated, you should use dh_python2 instead.
> Migration guide: http://deb.li/dhs2p
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (CASSANDRA-10853) deb package migration to dh_python2
[
https://issues.apache.org/jira/browse/CASSANDRA-10853?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15246604#comment-15246604
]
Michael Shuler commented on CASSANDRA-10853:
Verifying that the architecture triplet renamed shared lib is correctly used by
installed cythonized cqlsh:
{noformat}
$ /usr/bin/cqlsh
Connected to Test Cluster at 127.0.0.1:9042.
[cqlsh 5.0.1 | Cassandra 3.4 | CQL spec 3.4.2 | Native protocol v4]
Use HELP for help.
cassandra@cqlsh>
# in another shell
$ sudo lsof |grep cqlshlib
python 7633 mshuler mem REG8,16194568
3545669 /usr/lib/python2.7/dist-packages/cqlshlib/copyutil.x86_64-linux-gnu.so
python 7633 7641 mshuler mem REG8,16194568
3545669 /usr/lib/python2.7/dist-packages/cqlshlib/copyutil.x86_64-linux-gnu.so
python 7633 7642 mshuler mem REG8,16194568
3545669 /usr/lib/python2.7/dist-packages/cqlshlib/copyutil.x86_64-linux-gnu.so
python 7633 7646 mshuler mem REG8,16194568
3545669 /usr/lib/python2.7/dist-packages/cqlshlib/copyutil.x86_64-linux-gnu.so
python 7633 7647 mshuler mem REG8,16194568
3545669 /usr/lib/python2.7/dist-packages/cqlshlib/copyutil.x86_64-linux-gnu.so
$
{noformat}
> deb package migration to dh_python2
> ---
>
> Key: CASSANDRA-10853
> URL: https://issues.apache.org/jira/browse/CASSANDRA-10853
> Project: Cassandra
> Issue Type: Task
> Components: Packaging
>Reporter: Michael Shuler
>Assignee: Michael Shuler
> Fix For: 3.0.x, 3.x
>
>
> I'm working on a deb job in jenkins, and I had forgotten to open a bug for
> this. There is no urgent need, since {{python-support}} is in Jessie, but
> this package is currently in transition to be removed.
> http://deb.li/dhs2p
> During deb build:
> {noformat}
> dh_pysupport: This program is deprecated, you should use dh_python2 instead.
> Migration guide: http://deb.li/dhs2p
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (CASSANDRA-10853) deb package migration to dh_python2
[
https://issues.apache.org/jira/browse/CASSANDRA-10853?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15246370#comment-15246370
]
Michael Shuler commented on CASSANDRA-10853:
Since we are now building architecture-specific libraries, the package is no
longer technically an arch-all build:
{noformat}
dh_python2
readelf: Error: Not an ELF file - it has the wrong magic bytes at the start
readelf: Error: Not an ELF file - it has the wrong magic bytes at the start
I: dh_python2 fs:298: renaming copyutil.so to copyutil.x86_64-linux-gnu.so
{noformat}
{noformat}
$ dpkg --contents ../cassandra_3.4_all.deb | grep python
drwxr-xr-x root/root 0 2016-04-18 14:08 ./usr/lib/python2.7/
drwxr-xr-x root/root 0 2016-04-18 14:08
./usr/lib/python2.7/dist-packages/
-rw-r--r-- root/root 208 2016-04-18 14:08
./usr/lib/python2.7/dist-packages/cassandra_pylib-0.0.0.egg-info
drwxr-xr-x root/root 0 2016-04-18 14:08
./usr/lib/python2.7/dist-packages/cqlshlib/
-rw-r--r-- root/root 54083 2016-04-18 13:48
./usr/lib/python2.7/dist-packages/cqlshlib/cql3handling.py
-rw-r--r-- root/root 6194568 2016-04-18 14:08
./usr/lib/python2.7/dist-packages/cqlshlib/copyutil.x86_64-linux-gnu.so
-rw-r--r-- root/root 4532 2016-04-18 13:47
./usr/lib/python2.7/dist-packages/cqlshlib/helptopics.py
-rw-r--r-- root/root 12973 2016-04-18 13:47
./usr/lib/python2.7/dist-packages/cqlshlib/cqlhandling.py
-rw-r--r-- root/root 784 2016-04-18 13:47
./usr/lib/python2.7/dist-packages/cqlshlib/__init__.py
-rw-r--r-- root/root 2711 2016-04-18 13:47
./usr/lib/python2.7/dist-packages/cqlshlib/saferscanner.py
-rw-r--r-- root/root 4525 2016-04-18 13:47
./usr/lib/python2.7/dist-packages/cqlshlib/util.py
-rw-r--r-- root/root 15872 2016-04-18 13:47
./usr/lib/python2.7/dist-packages/cqlshlib/wcwidth.py
-rw-r--r-- root/root 19445 2016-04-18 13:48
./usr/lib/python2.7/dist-packages/cqlshlib/formatting.py
-rw-r--r-- root/root 18854 2016-04-18 13:47
./usr/lib/python2.7/dist-packages/cqlshlib/pylexotron.py
-rw-r--r-- root/root 3268 2016-04-18 13:48
./usr/lib/python2.7/dist-packages/cqlshlib/tracing.py
-rw-r--r-- root/root101082 2016-04-18 13:48
./usr/lib/python2.7/dist-packages/cqlshlib/copyutil.py
-rw-r--r-- root/root 3725 2016-04-18 13:47
./usr/lib/python2.7/dist-packages/cqlshlib/sslhandling.py
-rw-r--r-- root/root 3956 2016-04-18 13:47
./usr/lib/python2.7/dist-packages/cqlshlib/displaying.py
{noformat}
> deb package migration to dh_python2
> ---
>
> Key: CASSANDRA-10853
> URL: https://issues.apache.org/jira/browse/CASSANDRA-10853
> Project: Cassandra
> Issue Type: Task
> Components: Packaging
>Reporter: Michael Shuler
>Assignee: Michael Shuler
> Fix For: 3.0.x, 3.x
>
>
> I'm working on a deb job in jenkins, and I had forgotten to open a bug for
> this. There is no urgent need, since {{python-support}} is in Jessie, but
> this package is currently in transition to be removed.
> http://deb.li/dhs2p
> During deb build:
> {noformat}
> dh_pysupport: This program is deprecated, you should use dh_python2 instead.
> Migration guide: http://deb.li/dhs2p
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (CASSANDRA-10853) deb package migration to dh_python2
[
https://issues.apache.org/jira/browse/CASSANDRA-10853?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15246035#comment-15246035
]
Michael Shuler commented on CASSANDRA-10853:
C* branches 2.1+ now require cython at build time for copyutil, so let's
include this, too
{noformat}
diff --git a/debian/control b/debian/control
index 8a30de1..93b6aa5 100644
--- a/debian/control
+++ b/debian/control
@@ -3,7 +3,7 @@ Section: misc
Priority: extra
Maintainer: Eric Evans
Uploaders: Sylvain Lebresne
-Build-Depends: debhelper (>= 5), openjdk-7-jdk | java7-jdk, ant (>= 1.7),
ant-optional (>= 1.7), python-support, dpatch, bash-completion
+Build-Depends: debhelper (>= 5), openjdk-7-jdk | java7-jdk, ant (>= 1.7),
ant-optional (>= 1.7), python-support, dpatch, bash-completion, cython
Homepage: http://cassandra.apache.org
Vcs-Git: http://git-wip-us.apache.org/repos/asf/cassandra.git
Vcs-Browser: https://git-wip-us.apache.org/repos/asf?p=cassandra.git
{noformat}
> deb package migration to dh_python2
> ---
>
> Key: CASSANDRA-10853
> URL: https://issues.apache.org/jira/browse/CASSANDRA-10853
> Project: Cassandra
> Issue Type: Task
> Components: Packaging
>Reporter: Michael Shuler
>Assignee: Michael Shuler
> Fix For: 3.0.x, 3.x
>
>
> I'm working on a deb job in jenkins, and I had forgotten to open a bug for
> this. There is no urgent need, since {{python-support}} is in Jessie, but
> this package is currently in transition to be removed.
> http://deb.li/dhs2p
> During deb build:
> {noformat}
> dh_pysupport: This program is deprecated, you should use dh_python2 instead.
> Migration guide: http://deb.li/dhs2p
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (CASSANDRA-11560) dtest failure in user_types_test.TestUserTypes.udt_subfield_test
[
https://issues.apache.org/jira/browse/CASSANDRA-11560?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15242196#comment-15242196
]
Michael Shuler commented on CASSANDRA-11560:
Merged. Thanks, Tyler!
> dtest failure in user_types_test.TestUserTypes.udt_subfield_test
>
>
> Key: CASSANDRA-11560
> URL: https://issues.apache.org/jira/browse/CASSANDRA-11560
> Project: Cassandra
> Issue Type: Test
>Reporter: Michael Shuler
>Assignee: Tyler Hobbs
> Labels: dtest
>
> example failure:
> http://cassci.datastax.com/job/trunk_dtest/1125/testReport/user_types_test/TestUserTypes/udt_subfield_test
> Failed on CassCI build trunk_dtest #1125
> Appears to be a test problem:
> {noformat}
> Error Message
> 'NoneType' object is not iterable
> >> begin captured logging <<
> dtest: DEBUG: cluster ccm directory: /mnt/tmp/dtest-Kzg9Sk
> 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}
> - >> end captured logging << -
> Stacktrace
> File "/usr/lib/python2.7/unittest/case.py", line 329, in run
> testMethod()
> File "/home/automaton/cassandra-dtest/tools.py", line 253, in wrapped
> f(obj)
> File "/home/automaton/cassandra-dtest/user_types_test.py", line 767, in
> udt_subfield_test
> self.assertEqual(listify(rows[0]), [[None]])
> File "/home/automaton/cassandra-dtest/user_types_test.py", line 25, in
> listify
> for i in item:
> "'NoneType' object is not iterable\n >> begin captured
> logging << \ndtest: DEBUG: cluster ccm directory:
> /mnt/tmp/dtest-Kzg9Sk\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'range_request_timeout_in_ms': 1,\n
> 'read_request_timeout_in_ms': 1,\n'request_timeout_in_ms': 1,\n
> 'truncate_request_timeout_in_ms': 1,\n'write_request_timeout_in_ms':
> 1}\n- >> end captured logging <<
> -"
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (CASSANDRA-11565) dtest failure in cqlsh_tests.cqlsh_copy_tests.CqlshCopyTest.test_bulk_round_trip_non_prepared_statements
Michael Shuler created CASSANDRA-11565:
--
Summary: dtest failure in
cqlsh_tests.cqlsh_copy_tests.CqlshCopyTest.test_bulk_round_trip_non_prepared_statements
Key: CASSANDRA-11565
URL: https://issues.apache.org/jira/browse/CASSANDRA-11565
Project: Cassandra
Issue Type: Test
Reporter: Michael Shuler
Assignee: DS Test Eng
example failure:
http://cassci.datastax.com/job/cassandra-2.1_offheap_dtest/329/testReport/cqlsh_tests.cqlsh_copy_tests/CqlshCopyTest/test_bulk_round_trip_non_prepared_statements
Failed on CassCI build cassandra-2.1_offheap_dtest #329
{noformat}
Error Message
'int' object has no attribute 'on_read_timeout'
>> begin captured logging <<
dtest: DEBUG: cluster ccm directory: /mnt/tmp/dtest-LNfFyy
dtest: DEBUG: Custom init_config not found. Setting defaults.
dtest: DEBUG: Done setting configuration options:
{ 'initial_token': None,
'memtable_allocation_type': 'offheap_objects',
'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: Running stress without any user profile
- >> end captured logging << -
Stacktrace
File "/usr/lib/python2.7/unittest/case.py", line 329, in run
testMethod()
File "/home/automaton/cassandra-dtest/cqlsh_tests/cqlsh_copy_tests.py", line
2325, in test_bulk_round_trip_non_prepared_statements
copy_from_options={'PREPAREDSTATEMENTS': False})
File "/home/automaton/cassandra-dtest/cqlsh_tests/cqlsh_copy_tests.py", line
2283, in _test_bulk_round_trip
num_records = create_records()
File "/home/automaton/cassandra-dtest/cqlsh_tests/cqlsh_copy_tests.py", line
2258, in create_records
ret = rows_to_list(self.session.execute(count_statement))[0][0]
File "cassandra/cluster.py", line 1581, in cassandra.cluster.Session.execute
(cassandra/cluster.c:27046)
return self.execute_async(query, parameters, trace, custom_payload,
timeout).result()
File "cassandra/cluster.py", line 3145, in
cassandra.cluster.ResponseFuture.result (cassandra/cluster.c:59905)
raise self._final_exception
"'int' object has no attribute 'on_read_timeout'\n >> begin
captured logging << \ndtest: DEBUG: cluster ccm directory:
/mnt/tmp/dtest-LNfFyy\ndtest: DEBUG: Custom init_config not found. Setting
defaults.\ndtest: DEBUG: Done setting configuration options:\n{
'initial_token': None,\n'memtable_allocation_type': 'offheap_objects',\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: Running stress without any user
profile\n- >> end captured logging << -"
{noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (CASSANDRA-11564) dtest failure in secondary_indexes_test.TestSecondaryIndexes.test_query_indexes_with_vnodes
Michael Shuler created CASSANDRA-11564:
--
Summary: dtest failure in
secondary_indexes_test.TestSecondaryIndexes.test_query_indexes_with_vnodes
Key: CASSANDRA-11564
URL: https://issues.apache.org/jira/browse/CASSANDRA-11564
Project: Cassandra
Issue Type: Test
Reporter: Michael Shuler
Assignee: DS Test Eng
example failure:
http://cassci.datastax.com/job/trunk_novnode_dtest/344/testReport/secondary_indexes_test/TestSecondaryIndexes/test_query_indexes_with_vnodes
Failed on CassCI build trunk_novnode_dtest #344
Test does not appear to configure single-token cluster correctly:
{noformat}
Error Message
Error starting node1.
>> begin captured logging <<
dtest: DEBUG: cluster ccm directory: /mnt/tmp/dtest-4pEIhy
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}
- >> end captured logging << -
Stacktrace
File "/usr/lib/python2.7/unittest/case.py", line 329, in run
testMethod()
File "/home/automaton/cassandra-dtest/secondary_indexes_test.py", line 436,
in test_query_indexes_with_vnodes
cluster.populate(2, use_vnodes=True).start()
File "/home/automaton/ccm/ccmlib/cluster.py", line 360, in start
raise NodeError("Error starting {0}.".format(node.name), p)
"Error starting node1.\n >> begin captured logging <<
\ndtest: DEBUG: cluster ccm directory:
/mnt/tmp/dtest-4pEIhy\ndtest: DEBUG: Custom init_config not found. Setting
defaults.\ndtest: DEBUG: Done setting configuration options:\n{ 'num_tokens':
None,\n'phi_convict_threshold': 5,\n'range_request_timeout_in_ms':
1,\n'read_request_timeout_in_ms': 1,\n'request_timeout_in_ms':
1,\n'truncate_request_timeout_in_ms': 1,\n
'write_request_timeout_in_ms': 1}\n- >> end captured
logging << -"
Standard Output
[node1 ERROR] Invalid yaml. Those properties [num_tokens] are not valid
[node2 ERROR] Invalid yaml. Those properties [num_tokens] are not valid
{noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (CASSANDRA-11563) dtest failure in repair_tests.incremental_repair_test.TestIncRepair.sstable_marking_test_not_intersecting_all_ranges
Michael Shuler created CASSANDRA-11563:
--
Summary: dtest failure in
repair_tests.incremental_repair_test.TestIncRepair.sstable_marking_test_not_intersecting_all_ranges
Key: CASSANDRA-11563
URL: https://issues.apache.org/jira/browse/CASSANDRA-11563
Project: Cassandra
Issue Type: Test
Reporter: Michael Shuler
Assignee: DS Test Eng
example failure:
http://cassci.datastax.com/job/trunk_novnode_dtest/344/testReport/repair_tests.incremental_repair_test/TestIncRepair/sstable_marking_test_not_intersecting_all_ranges
Failed on CassCI build trunk_novnode_dtest #344
Test does not appear to deal with single-token cluster testing correctly:
{noformat}
Error Message
Error starting node1.
>> begin captured logging <<
dtest: DEBUG: cluster ccm directory: /mnt/tmp/dtest-I164Fa
dtest: DEBUG: Custom init_config not found. Setting defaults.
dtest: DEBUG: Done setting configuration options:
{ 'num_tokens': None, 'phi_convict_threshold': 5, 'start_rpc': 'true'}
- >> 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
369, in sstable_marking_test_not_intersecting_all_ranges
cluster.populate(4, use_vnodes=True).start()
File "/home/automaton/ccm/ccmlib/cluster.py", line 360, in start
raise NodeError("Error starting {0}.".format(node.name), p)
"Error starting node1.\n >> begin captured logging <<
\ndtest: DEBUG: cluster ccm directory:
/mnt/tmp/dtest-I164Fa\ndtest: DEBUG: Custom init_config not found. Setting
defaults.\ndtest: DEBUG: Done setting configuration options:\n{ 'num_tokens':
None, 'phi_convict_threshold': 5, 'start_rpc': 'true'}\n-
>> end captured logging << -"
Standard Output
[node1 ERROR] Invalid yaml. Those properties [num_tokens] are not valid
[node3 ERROR] Invalid yaml. Those properties [num_tokens] are not valid
[node2 ERROR] Invalid yaml. Those properties [num_tokens] are not valid
[node4 ERROR] Invalid yaml. Those properties [num_tokens] are not valid
{noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (CASSANDRA-11560) dtest failure in user_types_test.TestUserTypes.udt_subfield_test
Michael Shuler created CASSANDRA-11560:
--
Summary: dtest failure in
user_types_test.TestUserTypes.udt_subfield_test
Key: CASSANDRA-11560
URL: https://issues.apache.org/jira/browse/CASSANDRA-11560
Project: Cassandra
Issue Type: Test
Reporter: Michael Shuler
Assignee: DS Test Eng
example failure:
http://cassci.datastax.com/job/trunk_dtest/1125/testReport/user_types_test/TestUserTypes/udt_subfield_test
Failed on CassCI build trunk_dtest #1125
Appears to be a test problem:
{noformat}
Error Message
'NoneType' object is not iterable
>> begin captured logging <<
dtest: DEBUG: cluster ccm directory: /mnt/tmp/dtest-Kzg9Sk
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}
- >> end captured logging << -
Stacktrace
File "/usr/lib/python2.7/unittest/case.py", line 329, in run
testMethod()
File "/home/automaton/cassandra-dtest/tools.py", line 253, in wrapped
f(obj)
File "/home/automaton/cassandra-dtest/user_types_test.py", line 767, in
udt_subfield_test
self.assertEqual(listify(rows[0]), [[None]])
File "/home/automaton/cassandra-dtest/user_types_test.py", line 25, in listify
for i in item:
"'NoneType' object is not iterable\n >> begin captured
logging << \ndtest: DEBUG: cluster ccm directory:
/mnt/tmp/dtest-Kzg9Sk\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'range_request_timeout_in_ms': 1,\n
'read_request_timeout_in_ms': 1,\n'request_timeout_in_ms': 1,\n
'truncate_request_timeout_in_ms': 1,\n'write_request_timeout_in_ms':
1}\n- >> end captured logging << -"
{noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (CASSANDRA-10853) deb package migration to dh_python2
[
https://issues.apache.org/jira/browse/CASSANDRA-10853?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Shuler updated CASSANDRA-10853:
---
Fix Version/s: 3.0.x
> deb package migration to dh_python2
> ---
>
> Key: CASSANDRA-10853
> URL: https://issues.apache.org/jira/browse/CASSANDRA-10853
> Project: Cassandra
> Issue Type: Task
> Components: Packaging
>Reporter: Michael Shuler
>Assignee: Michael Shuler
> Fix For: 3.0.x, 3.x
>
>
> I'm working on a deb job in jenkins, and I had forgotten to open a bug for
> this. There is no urgent need, since {{python-support}} is in Jessie, but
> this package is currently in transition to be removed.
> http://deb.li/dhs2p
> During deb build:
> {noformat}
> dh_pysupport: This program is deprecated, you should use dh_python2 instead.
> Migration guide: http://deb.li/dhs2p
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (CASSANDRA-11505) dtest failure in cqlsh_tests.cqlsh_copy_tests.CqlshCopyTest.test_reading_max_parse_errors
[
https://issues.apache.org/jira/browse/CASSANDRA-11505?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15236494#comment-15236494
]
Michael Shuler commented on CASSANDRA-11505:
2.1 HEAD hung on test_reading_max_parse_errors on my first try. Since it has
been intermittent, we probably hadn't hit it in CI due to the smaller number of
2.1 commits. With your 2.1 patch, 50 loops over the test have completed
successfully. +1 for 2.1, too :)
> dtest failure in
> cqlsh_tests.cqlsh_copy_tests.CqlshCopyTest.test_reading_max_parse_errors
> -
>
> Key: CASSANDRA-11505
> URL: https://issues.apache.org/jira/browse/CASSANDRA-11505
> Project: Cassandra
> Issue Type: Test
> Components: Tools
>Reporter: Michael Shuler
>Assignee: Stefania
> Labels: dtest
> Fix For: 2.1.x, 2.2.x
>
>
> example failure:
> http://cassci.datastax.com/job/cassandra-3.0_novnode_dtest/197/testReport/cqlsh_tests.cqlsh_copy_tests/CqlshCopyTest/test_reading_max_parse_errors
> Failed on CassCI build cassandra-3.0_novnode_dtest #197
> {noformat}
> Error Message
> False is not true
> >> begin captured logging <<
> dtest: DEBUG: cluster ccm directory: /mnt/tmp/dtest-c2AJlu
> 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: Importing csv file /mnt/tmp/tmp2O43PH with 10 max parse errors
> - >> end captured logging << -
> Stacktrace
> File "/usr/lib/python2.7/unittest/case.py", line 329, in run
> testMethod()
> File "/home/automaton/cassandra-dtest/cqlsh_tests/cqlsh_copy_tests.py",
> line 943, in test_reading_max_parse_errors
> self.assertTrue(num_rows_imported < (num_rows / 2)) # less than the
> maximum number of valid rows in the csv
> File "/usr/lib/python2.7/unittest/case.py", line 422, in assertTrue
> raise self.failureException(msg)
> "False is not true\n >> begin captured logging <<
> \ndtest: DEBUG: cluster ccm directory:
> /mnt/tmp/dtest-c2AJlu\ndtest: DEBUG: Custom init_config not found. Setting
> defaults.\ndtest: DEBUG: Done setting configuration options:\n{
> 'num_tokens': None,\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: Importing csv file /mnt/tmp/tmp2O43PH with 10 max parse
> errors\n- >> end captured logging <<
> -"
> Standard Output
> (EE) Using CQL driver: '/home/automaton/cassandra/bin/../lib/cassandra-driver-internal-only-3.0.0-6af642d.zip/cassandra-driver-3.0.0-6af642d/cassandra/__init__.py'>(EE)
> Using connect timeout: 5 seconds(EE) Using 'utf-8' encoding(EE)
> :2:Failed to import 2500 rows: ParseError - could not convert string
> to float: abc, given up without retries(EE) :2:Exceeded maximum
> number of parse errors 10(EE) :2:Failed to process 2500 rows; failed
> rows written to import_ks_testmaxparseerrors.err(EE) :2:Exceeded
> maximum number of parse errors 10(EE)
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (CASSANDRA-11505) dtest failure in cqlsh_tests.cqlsh_copy_tests.CqlshCopyTest.test_reading_max_parse_errors
[
https://issues.apache.org/jira/browse/CASSANDRA-11505?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15235641#comment-15235641
]
Michael Shuler commented on CASSANDRA-11505:
+1 for backporting to 2.2.
I was unable to get 2.2 to hang on test_reading_max_parse_errors looping over
the test for a long time.
3.0 passes running in a loop. I think we're good here with your patch!
> dtest failure in
> cqlsh_tests.cqlsh_copy_tests.CqlshCopyTest.test_reading_max_parse_errors
> -
>
> Key: CASSANDRA-11505
> URL: https://issues.apache.org/jira/browse/CASSANDRA-11505
> Project: Cassandra
> Issue Type: Test
>Reporter: Michael Shuler
>Assignee: Stefania
> Labels: dtest
>
> example failure:
> http://cassci.datastax.com/job/cassandra-3.0_novnode_dtest/197/testReport/cqlsh_tests.cqlsh_copy_tests/CqlshCopyTest/test_reading_max_parse_errors
> Failed on CassCI build cassandra-3.0_novnode_dtest #197
> {noformat}
> Error Message
> False is not true
> >> begin captured logging <<
> dtest: DEBUG: cluster ccm directory: /mnt/tmp/dtest-c2AJlu
> 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: Importing csv file /mnt/tmp/tmp2O43PH with 10 max parse errors
> - >> end captured logging << -
> Stacktrace
> File "/usr/lib/python2.7/unittest/case.py", line 329, in run
> testMethod()
> File "/home/automaton/cassandra-dtest/cqlsh_tests/cqlsh_copy_tests.py",
> line 943, in test_reading_max_parse_errors
> self.assertTrue(num_rows_imported < (num_rows / 2)) # less than the
> maximum number of valid rows in the csv
> File "/usr/lib/python2.7/unittest/case.py", line 422, in assertTrue
> raise self.failureException(msg)
> "False is not true\n >> begin captured logging <<
> \ndtest: DEBUG: cluster ccm directory:
> /mnt/tmp/dtest-c2AJlu\ndtest: DEBUG: Custom init_config not found. Setting
> defaults.\ndtest: DEBUG: Done setting configuration options:\n{
> 'num_tokens': None,\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: Importing csv file /mnt/tmp/tmp2O43PH with 10 max parse
> errors\n- >> end captured logging <<
> -"
> Standard Output
> (EE) Using CQL driver: '/home/automaton/cassandra/bin/../lib/cassandra-driver-internal-only-3.0.0-6af642d.zip/cassandra-driver-3.0.0-6af642d/cassandra/__init__.py'>(EE)
> Using connect timeout: 5 seconds(EE) Using 'utf-8' encoding(EE)
> :2:Failed to import 2500 rows: ParseError - could not convert string
> to float: abc, given up without retries(EE) :2:Exceeded maximum
> number of parse errors 10(EE) :2:Failed to process 2500 rows; failed
> rows written to import_ks_testmaxparseerrors.err(EE) :2:Exceeded
> maximum number of parse errors 10(EE)
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Comment Edited] (CASSANDRA-11505) dtest failure in cqlsh_tests.cqlsh_copy_tests.CqlshCopyTest.test_reading_max_parse_errors
[
https://issues.apache.org/jira/browse/CASSANDRA-11505?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15235339#comment-15235339
]
Michael Shuler edited comment on CASSANDRA-11505 at 4/11/16 4:03 PM:
-
Thanks for tracking this down - we were discussing a different way to capture
stdout/err in the test and looking at the patch, this makes sense. I'm looping
over this test with your patch on 2.2 HEAD to see if I can get it to hang up on
me.
was (Author: mshuler):
Thanks for tracking this down - we were discussing a different way to capture
stdout/err in the test and looking at the patch, this makes sense. I'm looping
over this test with your patch on 2.2 HEAD to see if I can get it to hang up on
me. I think this hung on 3.0 also, so I'll check there too.
> dtest failure in
> cqlsh_tests.cqlsh_copy_tests.CqlshCopyTest.test_reading_max_parse_errors
> -
>
> Key: CASSANDRA-11505
> URL: https://issues.apache.org/jira/browse/CASSANDRA-11505
> Project: Cassandra
> Issue Type: Test
>Reporter: Michael Shuler
>Assignee: Stefania
> Labels: dtest
>
> example failure:
> http://cassci.datastax.com/job/cassandra-3.0_novnode_dtest/197/testReport/cqlsh_tests.cqlsh_copy_tests/CqlshCopyTest/test_reading_max_parse_errors
> Failed on CassCI build cassandra-3.0_novnode_dtest #197
> {noformat}
> Error Message
> False is not true
> >> begin captured logging <<
> dtest: DEBUG: cluster ccm directory: /mnt/tmp/dtest-c2AJlu
> 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: Importing csv file /mnt/tmp/tmp2O43PH with 10 max parse errors
> - >> end captured logging << -
> Stacktrace
> File "/usr/lib/python2.7/unittest/case.py", line 329, in run
> testMethod()
> File "/home/automaton/cassandra-dtest/cqlsh_tests/cqlsh_copy_tests.py",
> line 943, in test_reading_max_parse_errors
> self.assertTrue(num_rows_imported < (num_rows / 2)) # less than the
> maximum number of valid rows in the csv
> File "/usr/lib/python2.7/unittest/case.py", line 422, in assertTrue
> raise self.failureException(msg)
> "False is not true\n >> begin captured logging <<
> \ndtest: DEBUG: cluster ccm directory:
> /mnt/tmp/dtest-c2AJlu\ndtest: DEBUG: Custom init_config not found. Setting
> defaults.\ndtest: DEBUG: Done setting configuration options:\n{
> 'num_tokens': None,\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: Importing csv file /mnt/tmp/tmp2O43PH with 10 max parse
> errors\n- >> end captured logging <<
> -"
> Standard Output
> (EE) Using CQL driver: '/home/automaton/cassandra/bin/../lib/cassandra-driver-internal-only-3.0.0-6af642d.zip/cassandra-driver-3.0.0-6af642d/cassandra/__init__.py'>(EE)
> Using connect timeout: 5 seconds(EE) Using 'utf-8' encoding(EE)
> :2:Failed to import 2500 rows: ParseError - could not convert string
> to float: abc, given up without retries(EE) :2:Exceeded maximum
> number of parse errors 10(EE) :2:Failed to process 2500 rows; failed
> rows written to import_ks_testmaxparseerrors.err(EE) :2:Exceeded
> maximum number of parse errors 10(EE)
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (CASSANDRA-11505) dtest failure in cqlsh_tests.cqlsh_copy_tests.CqlshCopyTest.test_reading_max_parse_errors
[
https://issues.apache.org/jira/browse/CASSANDRA-11505?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15235339#comment-15235339
]
Michael Shuler commented on CASSANDRA-11505:
Thanks for tracking this down - we were discussing a different way to capture
stdout/err in the test and looking at the patch, this makes sense. I'm looping
over this test with your patch on 2.2 HEAD to see if I can get it to hang up on
me. I think this hung on 3.0 also, so I'll check there too.
> dtest failure in
> cqlsh_tests.cqlsh_copy_tests.CqlshCopyTest.test_reading_max_parse_errors
> -
>
> Key: CASSANDRA-11505
> URL: https://issues.apache.org/jira/browse/CASSANDRA-11505
> Project: Cassandra
> Issue Type: Test
>Reporter: Michael Shuler
>Assignee: Stefania
> Labels: dtest
>
> example failure:
> http://cassci.datastax.com/job/cassandra-3.0_novnode_dtest/197/testReport/cqlsh_tests.cqlsh_copy_tests/CqlshCopyTest/test_reading_max_parse_errors
> Failed on CassCI build cassandra-3.0_novnode_dtest #197
> {noformat}
> Error Message
> False is not true
> >> begin captured logging <<
> dtest: DEBUG: cluster ccm directory: /mnt/tmp/dtest-c2AJlu
> 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: Importing csv file /mnt/tmp/tmp2O43PH with 10 max parse errors
> - >> end captured logging << -
> Stacktrace
> File "/usr/lib/python2.7/unittest/case.py", line 329, in run
> testMethod()
> File "/home/automaton/cassandra-dtest/cqlsh_tests/cqlsh_copy_tests.py",
> line 943, in test_reading_max_parse_errors
> self.assertTrue(num_rows_imported < (num_rows / 2)) # less than the
> maximum number of valid rows in the csv
> File "/usr/lib/python2.7/unittest/case.py", line 422, in assertTrue
> raise self.failureException(msg)
> "False is not true\n >> begin captured logging <<
> \ndtest: DEBUG: cluster ccm directory:
> /mnt/tmp/dtest-c2AJlu\ndtest: DEBUG: Custom init_config not found. Setting
> defaults.\ndtest: DEBUG: Done setting configuration options:\n{
> 'num_tokens': None,\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: Importing csv file /mnt/tmp/tmp2O43PH with 10 max parse
> errors\n- >> end captured logging <<
> -"
> Standard Output
> (EE) Using CQL driver: '/home/automaton/cassandra/bin/../lib/cassandra-driver-internal-only-3.0.0-6af642d.zip/cassandra-driver-3.0.0-6af642d/cassandra/__init__.py'>(EE)
> Using connect timeout: 5 seconds(EE) Using 'utf-8' encoding(EE)
> :2:Failed to import 2500 rows: ParseError - could not convert string
> to float: abc, given up without retries(EE) :2:Exceeded maximum
> number of parse errors 10(EE) :2:Failed to process 2500 rows; failed
> rows written to import_ks_testmaxparseerrors.err(EE) :2:Exceeded
> maximum number of parse errors 10(EE)
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (CASSANDRA-11539) dtest failure in topology_test.TestTopology.movement_test
Michael Shuler created CASSANDRA-11539:
--
Summary: dtest failure in topology_test.TestTopology.movement_test
Key: CASSANDRA-11539
URL: https://issues.apache.org/jira/browse/CASSANDRA-11539
Project: Cassandra
Issue Type: Test
Components: Testing
Reporter: Michael Shuler
Assignee: DS Test Eng
Fix For: 3.x
example failure:
{noformat}
Error Message
values not within 16.00% of the max: (335.88, 404.31) ()
>> begin captured logging <<
dtest: DEBUG: cluster ccm directory: /mnt/tmp/dtest-XGOyDd
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}
- >> end captured logging << -
Stacktrace
File "/usr/lib/python2.7/unittest/case.py", line 329, in run
testMethod()
File "/home/automaton/cassandra-dtest/topology_test.py", line 93, in
movement_test
assert_almost_equal(sizes[1], sizes[2])
File "/home/automaton/cassandra-dtest/assertions.py", line 75, in
assert_almost_equal
assert vmin > vmax * (1.0 - error) or vmin == vmax, "values not within
%.2f%% of the max: %s (%s)" % (error * 100, args, error_message)
"values not within 16.00% of the max: (335.88, 404.31) ()\n
>> begin captured logging << \ndtest: DEBUG: cluster ccm
directory: /mnt/tmp/dtest-XGOyDd\ndtest: DEBUG: Custom init_config not found.
Setting defaults.\ndtest: DEBUG: Done setting configuration options:\n{
'num_tokens': None,\n'phi_convict_threshold': 5,\n
'range_request_timeout_in_ms': 1,\n'read_request_timeout_in_ms':
1,\n'request_timeout_in_ms': 1,\n
'truncate_request_timeout_in_ms': 1,\n'write_request_timeout_in_ms':
1}\n- >> end captured logging << -"
{noformat}
http://cassci.datastax.com/job/cassandra-3.5_novnode_dtest/22/testReport/topology_test/TestTopology/movement_test
I dug through this test's history on the trunk, 3.5, 3.0, and 2.2 branches. It
appears this test is stable and passing on 3.0 & 2.2 (which could be just
luck). On trunk & 3.5, however, this test has flapped a small number of times.
The test's threshold is 16% and I found test failures in the 3.5 branch of
16.2%, 16.9%, and 18.3%. In trunk I found 17.4% and 23.5% diff failures.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (CASSANDRA-11514) trunk compaction performance regression
[
https://issues.apache.org/jira/browse/CASSANDRA-11514?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15230918#comment-15230918
]
Michael Shuler commented on CASSANDRA-11514:
Larger run on DTCS
[trunk_3.5_3.0-compaction_DTCS|http://cstar.datastax.com/tests/artifacts/c9dd18fc-fcd7-11e5-8f8b-0256e416528f/graph]
seems to support that trunk and 3.5 both have this commit. The differences
seem pretty small, so it could be difficult to determine a difference between 2
commits.
> trunk compaction performance regression
> ---
>
> Key: CASSANDRA-11514
> URL: https://issues.apache.org/jira/browse/CASSANDRA-11514
> Project: Cassandra
> Issue Type: Bug
> Components: Compaction
> Environment: cstar_perf
>Reporter: Michael Shuler
> Labels: performance
> Fix For: 3.x
>
> Attachments: trunk-compaction_dtcs-op_rate.png,
> trunk-compaction_lcs-op_rate.png
>
>
> It appears that a commit between Mar 29-30 has resulted in a drop in
> compaction performance. I attempted to get a log list of commits to post
> here, but
> {noformat}
> git log trunk@{2016-03-29}..trunk@{2016-03-31}
> {noformat}
> appears to be incomplete, since reading through {{git log}} I see netty and
> och were upgraded during this time period.
> !trunk-compaction_dtcs-op_rate.png!
> !trunk-compaction_lcs-op_rate.png!
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
