You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Yifan Cai (Jira)" <ji...@apache.org> on 2019/12/12 17:55:00 UTC
[jira] [Assigned] (CASSANDRA-15447) in-jvm dtest support for
subnets doesn't change seed provider subnet
[ https://issues.apache.org/jira/browse/CASSANDRA-15447?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Yifan Cai reassigned CASSANDRA-15447:
-------------------------------------
Assignee: Doug Rohrer
> 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
> Time Spent: 50m
> 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: commits-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org