On Thu, Apr 21, 2011 at 9:30 PM, Nate McCall wrote:
> It will work as long as thrift and gossip are bound to the same
> interface. The discovery server in Hector also uses the
> CassandraHostConfigurator#getPort for the port in constructing the
> host URL.
Can you please elaborate a little in t
It will work as long as thrift and gossip are bound to the same
interface. The discovery server in Hector also uses the
CassandraHostConfigurator#getPort for the port in constructing the
host URL.
On Thu, Apr 21, 2011 at 10:48 AM, Roshan Dawrani
wrote:
> On Thu, Apr 21, 2011 at 9:10 PM, Nate McCa
On Thu, Apr 21, 2011 at 9:10 PM, Nate McCall wrote:
> Roshan,
> See https://issues.apache.org/jira/browse/CASSANDRA-1777 for more details.
>
Hi...I am not sure I fully understand the current state of auto-discovery of
nodes.
The impression I am getting looking at the issue details is that
auto-
Roshan,
See https://issues.apache.org/jira/browse/CASSANDRA-1777 for more details.
On Thu, Apr 21, 2011 at 10:33 AM, Jonathan Ellis wrote:
> describe_cluster is showing the value of listen_address
>
> On Thu, Apr 21, 2011 at 9:28 AM, Roshan Dawrani
> wrote:
>> Hi,
>> In our Cassandra/Hector env
describe_cluster is showing the value of listen_address
On Thu, Apr 21, 2011 at 9:28 AM, Roshan Dawrani wrote:
> Hi,
> In our Cassandra/Hector environment, we are trying to turn the
> auto-discovery of nodes in the ring on. We have created the DB using the
> following default in cassandra.yaml
>
Hi,
In our Cassandra/Hector environment, we are trying to turn the
auto-discovery of nodes in the ring on. We have created the DB using the
following default in cassandra.yaml
===
# Addresses of hosts that are deemed contact points.
# Cas
