[
https://issues.apache.org/jira/browse/CASSANDRA-15447?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16994788#comment-16994788
]
Doug Rohrer commented on CASSANDRA-15447:
-----------------------------------------
PRs for all four active branches are now available. The patch is essentially
identical for all four, and require very few changes.
Separately, it appears there's something causing FailingRepairTest to fail when
run with other dtests - this is true on trunk w/o my changes but I'll take a
look and see if I can figure out what's bleeding over from some previous test
that's causing it.
> 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
> Priority: Normal
> Labels: pull-request-available
> Time Spent: 40m
> 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]
