[
https://issues.apache.org/jira/browse/CASSANDRA-15447?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alex Petrov updated CASSANDRA-15447:
------------------------------------
Fix Version/s: 3.11.x
3.0.x
2.2.x
4.0
Since Version: 2.2.15
Source Control Link:
https://github.com/apache/cassandra/commit/fdc055da124efc92a73bd208b4463ee5528c85e0
Resolution: Fixed
Status: Resolved (was: Ready to Commit)
Committed to 2.2 as
[563592801aad00e002f0a162d5e2625a4b0e8723|https://github.com/apache/cassandra/commit/563592801aad00e002f0a162d5e2625a4b0e8723]
and merged to
[3.0|https://github.com/apache/cassandra/commit/49918efa803d6a420a281f24f9b12ca9208ba68f],
[3.11|https://github.com/apache/cassandra/commit/78143bc66fbb0050fcbdd1b31ba08c5aed466ad8]
and
[trunk|https://github.com/apache/cassandra/commit/fdc055da124efc92a73bd208b4463ee5528c85e0].
> in-jvm dtest support for subnets doesn't change seed provider subnet
> --------------------------------------------------------------------
>
> Key: CASSANDRA-15447
> URL: https://issues.apache.org/jira/browse/CASSANDRA-15447
> Project: Cassandra
> Issue Type: Bug
> Components: Test/dtest
> Reporter: Doug Rohrer
> Assignee: Doug Rohrer
> Priority: Normal
> Labels: pull-request-available
> Fix For: 4.0, 2.2.x, 3.0.x, 3.11.x
>
> Time Spent: 1h 20m
> Remaining Estimate: 0h
>
> When using the `withSubnet` function on AbstractCluster.Builder, the
> newly-selected subnet is never used when setting up the SeedProvider in the
> constructor of InstanceConfig, which is hard-coded to 127.0.0.1. Because of
> this, clusters with any subnet other than 0, and gossip enabled, cannot start
> up as they have no seed provider in their subnet and what should be the seed
> (instance 1) doesn't think it is the seed.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
