[
https://issues.apache.org/jira/browse/CASSANDRA-13855?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17829900#comment-17829900
]
Maxim Muzafarov commented on CASSANDRA-13855:
---------------------------------------------
As I said I have nothing against the HttpSeedProvider, I'll review the current
changes.
Regarding Cloud SeedProviders, I think it should be possible to get a node tag
from the pod metadata in json format as we do now, so we probably don't need to
add any extra dependencies. Once each the seed metadata info is initialized, we
can put that in the ClusterMetadata as we did it for the rack parameter, this
should work, however I haven't tried implementing it on my end.
https://github.com/apache/cassandra/blob/trunk/src/java/org/apache/cassandra/locator/AbstractCloudMetadataServiceSnitch.java#L72
{code}
if (endpoint.equals(FBUtilities.getBroadcastAddressAndPort()))
return getLocalRack();
ClusterMetadata metadata = ClusterMetadata.current();
NodeId nodeId = metadata.directory.peerId(endpoint);
if (nodeId == null)
return DEFAULT_RACK;
return metadata.directory.location(nodeId).rack;
{code}
I'm going to create an issue so we don't mix it up here.
> Implement Http Seed provider
> ----------------------------
>
> Key: CASSANDRA-13855
> URL: https://issues.apache.org/jira/browse/CASSANDRA-13855
> Project: Cassandra
> Issue Type: Improvement
> Components: Legacy/Coordination, Legacy/Core
> Reporter: Jon Haddad
> Assignee: Claude Warren
> Priority: Low
> Labels: lhf
> Fix For: 5.x
>
> Attachments: 0001-Add-URL-Seed-Provider-trunk.txt, signature.asc,
> signature.asc, signature.asc
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> Seems like including a dead simple seed provider that can fetch from a URL, 1
> line per seed, would be useful.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
