cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Vijay (JIRA)" <>
Subject [jira] [Updated] (CASSANDRA-2491) A new config parameter, broadcast_address
Date Thu, 09 Jun 2011 16:31:58 GMT


Vijay updated CASSANDRA-2491:

    Attachment: 2491_broadcast_address_v2.patch

1) Rebased
2) Attached patch has modification to IncomingTcpConnection (re factor) in order to support
Gossiper.instance.setVersion as versions should be on broadcast IP and socket.getInetAddress
will break.
3) Allow brodcastAddress to be set by snitch so we can automate via snitch (property or EC2MultiregionSnitch).

> A new config parameter, broadcast_address
> -----------------------------------------
>                 Key: CASSANDRA-2491
>                 URL:
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Core
>         Environment: x86_64 GNU/Linux
>            Reporter: Khee Chin
>            Assignee: Khee Chin
>            Priority: Trivial
>              Labels: patch
>             Fix For: 1.0
>         Attachments: 2491_broadcast_address.patch, 2491_broadcast_address_v2.patch
>   Original Estimate: 336h
>  Remaining Estimate: 336h
> A new config parameter, broadcast_address
> In a cluster setup where one or more nodes is behind a firewall and has a private ip
address, listen_address does not allow the hosts behind the firewalls to be discovered by
other nodes.
> Attached is a patch that introduces a new config parameter broadcast_address which allows
Cassandra nodes to explicitly specify their external ip address. 
> In addition, this allows listen_address to be set to on the already firewalled
> broadcast_address fallsback to listen_address when it is not stated.

This message is automatically generated by JIRA.
For more information on JIRA, see:

View raw message