[
https://issues.apache.org/jira/browse/CASSANDRA-7544?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16349197#comment-16349197
]
Ariel Weisberg commented on CASSANDRA-7544:
-------------------------------------------
bq. I don't think this is accurate. Protocol does not dictate which tables are
present, server version does.
Driver support isn't merged yet so if we want to use server version to do that
we can.
bq. On another note, is there a reason this was implemented as a new system
table (system.peers_v2), rather than new columns in the existing system.peers? I
The primary key changed. We don't support schema changes of the primary key so
there has to be a new table.
> Allow storage port to be configurable per node
> ----------------------------------------------
>
> Key: CASSANDRA-7544
> URL: https://issues.apache.org/jira/browse/CASSANDRA-7544
> Project: Cassandra
> Issue Type: Improvement
> Reporter: Sam Overton
> Assignee: Ariel Weisberg
> Priority: Major
> Fix For: 4.0
>
>
> Currently storage_port must be configured identically on all nodes in a
> cluster and it is assumed that this is the case when connecting to a remote
> node.
> This prevents running in any environment that requires multiple nodes to be
> able to bind to the same network interface, such as with many automatic
> provisioning/deployment frameworks.
> The current solutions seems to be
> * use a separate network interface for each node deployed to the same box.
> This puts a big requirement on IP allocation at large scale.
> * allow multiple clusters to be provisioned from the same resource pool, but
> restrict allocation to a maximum of one node per host from each cluster,
> assuming each cluster is running on a different storage port.
> It would make operations much simpler in these kind of environments if the
> environment provisioning the resources could assign the ports to be used when
> bringing up a new node on shared hardware.
> The changes required would be at least the following:
> 1. configure seeds as IP:port instead of just IP
> 2. gossip the storage port as part of a node's ApplicationState
> 3. refer internally to nodes by hostID instead of IP, since there will be
> multiple nodes with the same IP
> (1) & (2) are mostly trivial and I already have a patch for these. The bulk
> of the work to enable this is (3), and I would structure this as a separate
> pre-requisite patch.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
