[
https://issues.apache.org/jira/browse/CASSANDRA-7544?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16812873#comment-16812873
]
Keshav Varma commented on CASSANDRA-7544:
-----------------------------------------
[~aweisberg], I see you added support for this in cqlsh atÂ
[https://github.com/apache/cassandra/blame/2d622e05d1576d20c3bf6504cbdaf438a895b4cf/bin/cqlsh.py#L490],
but I can't find any corresponding commit in the published python-driver that
makes this work. In the meantime, this ends up breaking cqlsh for me on trunk
since that keyword argument doesn't exist
([https://github.com/datastax/python-driver/blob/4.x/cassandra/cluster.py#L707]).
Is there a different fork or branch that includes the driver side changes thatÂ
makes this work for you?
> 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: Normal
> 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
