You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "T Jake Luciani (JIRA)" <ji...@apache.org> on 2010/11/23 21:10:15 UTC
[jira] Resolved: (CASSANDRA-1769) Change internal endpoints to
contain address AND port
[ https://issues.apache.org/jira/browse/CASSANDRA-1769?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
T Jake Luciani resolved CASSANDRA-1769.
---------------------------------------
Resolution: Won't Fix
This isn't really a issue, nevermind.
> Change internal endpoints to contain address AND port
> -----------------------------------------------------
>
> Key: CASSANDRA-1769
> URL: https://issues.apache.org/jira/browse/CASSANDRA-1769
> Project: Cassandra
> Issue Type: Improvement
> Components: Core
> Reporter: T Jake Luciani
> Priority: Minor
>
> The fact that each cassandra instance needs to run on it's own ip is tricky and confusing for folks who want to run a local cluster, BMT, or thick client.
> I propose we make a Endpoint class that contains host AND port so many nodes can run on the same ip
> This would affect gossip and messaging but in the end you could have a local cluster running on localhost.
> The only change to users would be to specify a host:port for the seed
> Ports could even be auto-picked within a range [7000-8000]
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.