ble given
that cassandra binds to only one interface.
On 09/01/2010 03:23 PM, Benjamin Black wrote:
On Wed, Sep 1, 2010 at 3:18 PM, Andres March wrote:
I thought you might say that. Is there some reason to gossip IP addresses
vs hostnames? I thought that layer of indirection could be useful in
ct, but a great start.
b
On Wed, Sep 1, 2010 at 2:57 PM, Andres March wrote:
Is it not possible to put the external host name in cassandra.yaml and add a
host entry in /etc/hosts for that name to resolve to the local interface?
On 09/01/2010 01:24 PM, Benjamin Black wrote:
The issue is this:
by which a node is told to bind one IP
(the internal one), while it gossips another (the external one).
I like what this patch does conceptually, but would prefer
configuration options to cause it to happen (obviously a much larger
patch). Very cool, Peter!
b
On Wed, Sep 1, 2010 at 1:10 PM, An
Could you explain this point further? Was there an exception?
On 09/01/2010 09:26 AM, Peter Fales wrote:
that doesn't quite work with the stock Cassandra, as it will
try to bind and listen on those addresses and give up because they
don't appear to be valid network addresses.
estimates as to when a fix for this will be checked
into
> trunk?
>
> Coincidentally, has anyone tracked down the issue?
>
> I'm experiencing same issue with nightly build from a week ago.
>
> Thank You
>
--
Jonathan Ellis
Project Chair, Apache Cassandra
co-founder
repair operations,
etc., afterward.
https://issues.apache.org/jira/browse/CASSANDRA-1285
Gary.
On Thu, Aug 19, 2010 at 18:00, Andres March wrote:
How should we go about changing the replication factor and other keyspace
settings now that it and other KSMetaData are no longer managed in
be a big
gap in the management API for the KSMetaData we might want to change.
--
*Andres March*
ama...@qualcomm.com <mailto:ama...@qualcomm.com>
Qualcomm Internet Services
using a 0.7 SNAPSHOT built last friday with a framed transport.
--
*Andres March*
ama...@qualcomm.com <mailto:ama...@qualcomm.com>
Qualcomm Internet Services
