cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ariel Weisberg (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-7544) Allow storage port to be configurable per node
Date Thu, 02 Feb 2017 03:30:51 GMT

    [ https://issues.apache.org/jira/browse/CASSANDRA-7544?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15849342#comment-15849342
] 

Ariel Weisberg commented on CASSANDRA-7544:
-------------------------------------------

This introduces a client library impacting change for CASSANDRA-11596 that is currently disabled
by a flag so that client libraries that claim to support the next version of the protocol
continue to work.

[~rkuris] how are things going with the Java client?

Currently no one has done the Python driver or any of the other drivers. Not sure how we go
about integrating changes that require drivers to support a newer version of the protocol.

> 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
>             Fix For: 3.x
>
>
> 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
(v6.3.15#6346)

Mime
View raw message