Yes That worked. Thanks for the pointer. Once the broadcast_address is
pointed to public IP, end points are coming with public IP. so Hectors
NodeAutoDiscoveryService matches with the existing host and not treating it
as new node.
On Wed, Dec 12, 2012 at 11:10 PM, Andrey Ilinykh wrote:
> It make
It makes sense. rpc_address is interface to listen. Try to set up public IP
to broadcast_address.
Andrey
On Wed, Dec 12, 2012 at 9:33 AM, santi kumar wrote:
> When I configured rpc_address with public IP, cassandra is not starting
> up. It's trowing 'unable to create thrift socket on . When I
When I configured rpc_address with public IP, cassandra is not starting up.
It's trowing 'unable to create thrift socket on . When I changed
it to private IP, it was good.
java.lang.RuntimeException: Unable to create thrift socket to /
107.21.80.94:9160
at
org.apache.cassandra.thrift.Cassa
> Though I configured the listen_address with public dns, still I had the same
> issue.
Internally the public DNS resolves to the private IP.
> looks like describe_ring() is the one which provides the details.
describe_ring() returns includes the registered RPC addresses for the nodes.
Trying
We have a 4 node cluster in us-east region in two different AZ's. Clients
connect to this cluster from our datacenter which is not on AWS.
Hector clients are initialized with public DNS names, then listern_address
is with private ip and rpc_address is with 0.0.0.0.
Having issues with Node Auto Di
