[ https://issues.apache.org/jira/browse/CASSANDRA-17584 ]
Stefan Miklosovic deleted comment on CASSANDRA-17584:
-----------------------------------------------
was (Author: smiklosovic):
I am looking more into it, there needs to be some way / log to wait for. The
problem is that when StorageService asks if it should hint a mutation to the
node we just turned off the gossip for, it answers "yes" because stuff from
TokenMetadata from was not removed yet. It is removed later down the road after
node turns off the gossip. Indeed, it announces that it did so, but there is
additional logic happening, tokens are moved around and so on and eventually
it is removed from TokenMetadata. I need to find a what to somehow hook into
this process.
> Fix flaky test -
> org.apache.cassandra.db.virtual.GossipInfoTableTest.testSelectAllWithStateTransitions
> ------------------------------------------------------------------------------------------------------
>
> Key: CASSANDRA-17584
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17584
> Project: Cassandra
> Issue Type: Bug
> Components: Feature/Virtual Tables
> Reporter: Brandon Williams
> Assignee: Stefan Miklosovic
> Priority: Normal
> Fix For: 4.1-beta, 4.x
>
>
> h3. Error Message
> ['LOAD' is expected to be null] expected:<null> but was:<Value(122848.0,28)>
> h3. Stacktrace
> junit.framework.AssertionFailedError: ['LOAD' is expected to be null]
> expected:<null> but was:<Value(122848.0,28)> at
> org.apache.cassandra.db.virtual.GossipInfoTableTest.assertValue(GossipInfoTableTest.java:174)
> at
> org.apache.cassandra.db.virtual.GossipInfoTableTest.testSelectAllWithStateTransitions(GossipInfoTableTest.java:96)
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]