I can see the logic of having an internal DNS entry 'seednodes.internaldomain.com',
this might only have 3 defined seed nodes out of 100, but the benefit is single point configuration, no need to edit configs across 100 machines, easily redefinable on the fly as needed...
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.
On Sat, Apr 3, 2010 at 12:55 PM, gabriele renzi <email@example.com> wrote:
> On Sat, Apr 3, 2010 at 6:40 PM, Avinash Lakshman
> <firstname.lastname@example.org> 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
> would it make sense to just use a round robin dns on the available
> nodes and use that as seed?
> I do not have a clear understanding of the bootstrap mechanics but I
> have the impression that seed nodes do not have any special role, am I