On Sat, 3 Apr 2010 13:52:22 -0700 Benjamin Black b...@b3k.us wrote:
BB What happens if the IP I get back is for a seed that happens to be
BB down right then? And then that IP is cached locally by my resolver?
You have to set the TTL to be the right number of seconds for your
environment. With
2010/4/5 Ted Zlatanov t...@lifelogs.com
On Sat, 3 Apr 2010 14:10:37 -0500 Jonathan Ellis jbel...@gmail.com
wrote:
JE IMO the right way to do it is to configure your machines so that
JE autodetecting listenaddress Just Works, so you can deploy exactly the
JE same config to all nodes.
It
On Mon, 5 Apr 2010 13:10:38 -0500 Brandon Williams dri...@gmail.com wrote:
BW 2010/4/5 Ted Zlatanov t...@lifelogs.com
It would be nice if Cassandra looked at all the available interfaces and
selected the one whose reverse DNS lookup returned .*cassandra.* (or
some keyword the user provided).
Just added this to the wiki as it seemed a very frequent request on
irc: http://wiki.apache.org/cassandra/MultinodeCluster
Would very much appreciate feedback and edits to improve it.
b
Hi,
Nice work.
I guess just a small mistake :
the second ListenAddress192.168.1.1/ListenAddress should be
ListenAddress192.168.2.34/ListenAddress
And I would suggest to add a small part on making the thrift interface
listening on more than localhost.
Kind regards,
Benoit.
2010/4/3 Benjamin
Thank you! Updated.
On Sat, Apr 3, 2010 at 2:57 AM, Benoit Perroud ben...@noisette.ch wrote:
Hi,
Nice work.
I guess just a small mistake :
the second ListenAddress192.168.1.1/ListenAddress should be
ListenAddress192.168.2.34/ListenAddress
And I would suggest to add a small part on
Seeds are used for ring discovery, so there really isn't a load
concern for them, afaict. Have enough to meet your availability
needs, including placement, and rock out.
On Sat, Apr 3, 2010 at 9:01 AM, Joseph Ruscio jrus...@gmail.com wrote:
Ben,
Great, was looking for something like this just
IMO the right way to do it is to configure your machines so that
autodetecting listenaddress Just Works, so you can deploy exactly the
same config to all nodes.
On Sat, Apr 3, 2010 at 3:14 AM, Benjamin Black b...@b3k.us wrote:
Just added this to the wiki as it seemed a very frequent request on
I do not claim it is the best/right way, just the one least likely to go wrong.
On Sat, Apr 3, 2010 at 12:10 PM, Jonathan Ellis jbel...@gmail.com wrote:
IMO the right way to do it is to configure your machines so that
autodetecting listenaddress Just Works, so you can deploy exactly the
same
On Sat, Apr 3, 2010 at 6:40 PM, Avinash Lakshman
avinash.laksh...@gmail.com wrote:
We use anywhere from 3-5 seeds for clusters that have over 150 nodes. That
should suffice for larger sizes too since they are only for initial
discovery.
would it make sense to just use a round robin dns on the
Seems like a lot of complexity for a very small win (how often do you
bootstrap new nodes? if you only need a handful of seeds, what's all
that hard about listing them all on all nodes?). I prefer simple and
predictable, and trying to do this with round robin DNS seems to be
neither, to me.
b
11 matches
Mail list logo
