You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Marcus Olsson (JIRA)" <ji...@apache.org> on 2019/05/02 11:32:00 UTC
[jira] [Commented] (CASSANDRA-15088) PagingTest failure on trunk
[ https://issues.apache.org/jira/browse/CASSANDRA-15088?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16831556#comment-16831556 ]
Marcus Olsson commented on CASSANDRA-15088:
-------------------------------------------
Thanks for looking at it. Yes, the port was actually added later to cassandra-murmur.yaml during CASSANDRA-14956 as [27b3579|https://github.com/apache/cassandra/commit/27b35799a46dd5b649c4a172f4f8316b48615304] due to a test case failing in a similar way as described in this ticket. It seems like the port was removed again by a later merge from 3.11 -> trunk.
I can fix a patch that aligns the fields but I'm not sure that it's worth to do it for all fields (as long as the test cases are working as intended). Some test cases i.e. _test/unit/org/apache/cassandra/cql3/PstmtPersistenceTest.java_ uses the parameter _prepared_statements_cache_size_mb: 1_ from cassandra.yaml which I don't believe is necessary for test cases using cassandra-murmur.yaml (currently at least). To try to keep these two files aligned will probably be hard to remember as they have already diverged. We could of course add a comment in the yaml files saying that the fields should be aligned but that can still be missed.
But instead of keeping the two yaml files aligned perhaps a better approach would be to have only one yaml file that all test cases depend on and have a programmatic way to change specific fields required for the test cases. This could be done in such a way that the setup phase for all test cases that wants to use murmur3 would define the partitioner in the test case instead of specifying a yaml file to use. But that seems like a larger work and should probably be handled outside of this ticket.
> PagingTest failure on trunk
> ---------------------------
>
> Key: CASSANDRA-15088
> URL: https://issues.apache.org/jira/browse/CASSANDRA-15088
> Project: Cassandra
> Issue Type: Bug
> Components: Test/unit
> Reporter: Marcus Olsson
> Assignee: Marcus Olsson
> Priority: Normal
> Fix For: 4.0
>
> Attachments: 15088-trunk.txt
>
>
> [Example failure|https://circleci.com/gh/emolsson/cassandra/19]
> {noformat}
> java.lang.RuntimeException: Unable to gossip with any peers
> at org.apache.cassandra.gms.Gossiper.doShadowRound(Gossiper.java:1546)
> at org.apache.cassandra.service.StorageService.checkForEndpointCollision(StorageService.java:553)
> at org.apache.cassandra.service.StorageService.prepareToJoin(StorageService.java:841)
> at org.apache.cassandra.service.StorageService.initServer(StorageService.java:699)
> at org.apache.cassandra.service.StorageService.initServer(StorageService.java:650)
> at org.apache.cassandra.service.CassandraDaemon.setup(CassandraDaemon.java:379)
> at org.apache.cassandra.service.CassandraDaemon.init(CassandraDaemon.java:501)
> at org.apache.cassandra.service.EmbeddedCassandraService.start(EmbeddedCassandraService.java:50)
> at org.apache.cassandra.cql3.PagingTest.setup(PagingTest.java:63)
> {noformat}
> Running the test case by itself won't reproduce the issue:
> {noformat}
> ant test -Dtest.name=PagingTest
> {noformat}
> But running it in parallel with other tests will:
> {noformat}
> ant test -Dtest.name=cql3/*
> {noformat}
> From the logs the following can be observed:
> {noformat}
> INFO [main] 2019-04-11 15:32:29,916 Node configuration:[...seed_provider=org.apache.cassandra.locator.SimpleSeedProvider{seeds=127.0.0.1:7017}; storage_port=7027]
> ...
> DEBUG [main] 2019-04-17 10:11:55,418 connection attempt 0 to 127.0.0.1:7044 (GOSSIP)
> DEBUG [main] 2019-04-17 10:11:55,420 creating outbound bootstrap to peer 127.0.0.1:7044, compression: false, encryption: disabled, coalesce: DISABLED, protocolVersion: 12
> DEBUG [ScheduledFastTasks:1] 2019-04-17 10:11:55,538 connection attempt 1 to 127.0.0.1:7044 (GOSSIP)
> DEBUG [ScheduledFastTasks:1] 2019-04-17 10:11:55,538 creating outbound bootstrap to peer 127.0.0.1:7044, compression: false, encryption: disabled, coalesce: DISABLED, protocolVersion: 12
> {noformat}
> It seems like we have an offset issue of 10 between seed/storage_port.
> The port 7044 does not seem to be defined anywhere though.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org