[
https://issues.apache.org/jira/browse/CASSANDRA-16248?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sam Tunnicliffe updated CASSANDRA-16248:
----------------------------------------
Description:
A couple of recent updates appear to have broken {{o.a.c.d.t.GossipTest}}
* There seems to have been a merge/commit race between CASSANDRA-16146
([{{fee7a108}}|https://github.com/apache/cassandra/commit/fee7a10823da1e29bd0e6504fea9679389180c9e])
and CASSANDRA-15935
([{{41952a2f}}|https://github.com/apache/cassandra/commit/41952a2f73ba5198250f64beba8f7ff1203204ab]).
The former adds a ByteBuddy interception on {{StorageService::bootstrap}}, but
the latter changed the method signature, so this never actually gets injected.
This causes a latch in the test not to be counted down and it hangs until
timeout.
* After fixing the test code, it still hangs due to changes to
{{server_encryption_options}} initialization in CASSANDRA-16144
([{{f293376a}}|https://github.com/apache/cassandra/commit/f293376aa8dd315a208ef2f03bdcb7a84dcc675c]).
It appears to be causing an incorrect keystore location to be specified, which
causes instance startup to fail, again leading to the test hanging until it
times out. I don't have the cycles to dig into this further right now, but
reverting that commit (and making the test fix above) restores the green bar.
was:
A couple of recent updates appear to have broken {{o.a.c.d.t.GossipTest}}
* There seems to have been a merge/commit race between CASSANDRA-16146
({{fee7a108}}|https://github.com/apache/cassandra/commit/fee7a10823da1e29bd0e6504fea9679389180c9e)
and CASSANDRA-15935
({{41952a2f}}|https://github.com/apache/cassandra/commit/41952a2f73ba5198250f64beba8f7ff1203204ab)).
The former adds a ByteBuddy interception on {{StorageService::bootstrap}}, but
the latter changed the method signature, so this never actually gets injected.
This causes a latch in the test not to be counted down and it hangs until
timeout.
* After fixing the test code, it still hangs due to changes to
{{server_encryption_options}} initialization in CASSANDRA-166144
({{f293376a|https://github.com/apache/cassandra/commit/f293376aa8dd315a208ef2f03bdcb7a84dcc675c).
It appears to be causing an incorrect keystore location to be specified, which
causes instance startup to fail, again leading to the test hanging until it
times out. I don't have the cycles to dig into this further right now, but
reverting that commit (and making the test fix above) restores the green bar.
> GossipTest hangs until timeout, then fails.
> -------------------------------------------
>
> Key: CASSANDRA-16248
> URL: https://issues.apache.org/jira/browse/CASSANDRA-16248
> Project: Cassandra
> Issue Type: Bug
> Components: Local/Startup and Shutdown, Messaging/Internode,
> Test/dtest/java
> Reporter: Sam Tunnicliffe
> Priority: Normal
>
> A couple of recent updates appear to have broken {{o.a.c.d.t.GossipTest}}
> * There seems to have been a merge/commit race between CASSANDRA-16146
> ([{{fee7a108}}|https://github.com/apache/cassandra/commit/fee7a10823da1e29bd0e6504fea9679389180c9e])
> and CASSANDRA-15935
> ([{{41952a2f}}|https://github.com/apache/cassandra/commit/41952a2f73ba5198250f64beba8f7ff1203204ab]).
> The former adds a ByteBuddy interception on {{StorageService::bootstrap}},
> but the latter changed the method signature, so this never actually gets
> injected. This causes a latch in the test not to be counted down and it hangs
> until timeout.
> * After fixing the test code, it still hangs due to changes to
> {{server_encryption_options}} initialization in CASSANDRA-16144
> ([{{f293376a}}|https://github.com/apache/cassandra/commit/f293376aa8dd315a208ef2f03bdcb7a84dcc675c]).
> It appears to be causing an incorrect keystore location to be specified,
> which causes instance startup to fail, again leading to the test hanging
> until it times out. I don't have the cycles to dig into this further right
> now, but reverting that commit (and making the test fix above) restores the
> green bar.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
