Stable infrastructures require deterministic behavior to be understood. I
believe that mdns limits the determinism of a system by requiring that I
accept that a machine will be picking a random address. When I setup my DCs
I want machines to have a single constant ip address so that I don't have to
Frankly, I agree with Allen's comments.
I think that discovering the zookeeper should be done with a well known DNS
address (e.g. zookeeper.$cluster.prod.example.com). It would be pretty rare
for something like the address of the zookeeper to change in a stable
infrastructure. When it does, DNS ca
Internet Assigned Number Authority has allocated 169.254.1.0 to
169.254.254.255 for the propose of communicate between nodes. This is
65024 IP address designed for local area network only. They are not
allow to be routed. Zeroconf is randomly selecting one address out of
the 65024 available addr
On Jul 6, 2011, at 5:05 PM, Eric Yang wrote:
> Did you know that almost all linux desktop system comes with avahi
> pre-installed and turn on by default?
... which is why most admins turn those services off by default. :)
> What is more interesting is
> that there are thousands of thos
Did you know that almost all linux desktop system comes with avahi
pre-installed and turn on by default? What is more interesting is
that there are thousands of those machines broadcast in large
cooperation without anyone noticing them? I have recently built a
multicast dns browser and look into
On Jul 5, 2011, at 2:40 AM, Steve Loughran wrote:
> 1. you could use DNS proper, by way of Bonjour/avahi. You don't need to be
> running any mDNS server to support .local, and I would strongly advise
> against it in a large cluster (because .local resolution puts a lot of CPU
> load on every se
I am currently working on RPM packages for Zookeeper, Pig, Hive and
HCat. It may take a while for me to circle back to this. Never the
less, it is interesting work that I would like to contrib. Thanks
regards,
Eric
On Wed, Jul 6, 2011 at 9:18 AM, Patrick Hunt wrote:
> Eric, I'd be happy to wo
Eric, I'd be happy to work with you to get it committed if you'd like
to take a whack. Would be a great addition to contrib.
Patrick
On Wed, Jul 6, 2011 at 9:15 AM, Eric Yang wrote:
> It would be nicer, if it was written in Java. I think something wrap
> on top of jmdns would be a better fit fo
It would be nicer, if it was written in Java. I think something wrap
on top of jmdns would be a better fit for Zookeeper.
regards,
Eric
On Wed, Jul 6, 2011 at 9:10 AM, Patrick Hunt wrote:
> There's a long standing "ZooKeeper DNS server" jira which can be found
> here, someone has already create
There's a long standing "ZooKeeper DNS server" jira which can be found
here, someone has already created a basic implementation:
https://issues.apache.org/jira/browse/ZOOKEEPER-703
Patrick
On Wed, Jul 6, 2011 at 2:52 AM, Steve Loughran wrote:
> On 05/07/11 23:00, Eric Yang wrote:
>>
>> In anothe
On 05/07/11 23:00, Eric Yang wrote:
In another project, I have implemented a bonjour beacon (jmdns) which
sit on the Zookeeper nodes to advertise the location of zookeeper
servers. When clients start up, it will discover location of
zookeeper through multicast dns. Once, the server locations ar
In another project, I have implemented a bonjour beacon (jmdns) which
sit on the Zookeeper nodes to advertise the location of zookeeper
servers. When clients start up, it will discover location of
zookeeper through multicast dns. Once, the server locations are
resolved (ip:port and TXT records),
On 04/07/11 18:22, Ted Dunning wrote:
One reasonable suggestion that I have heard recently was to do like Google
does and put a DNS front end onto Zookeeper. Machines would need to have
DNS set up properly and a requests for a special ZK based domain would have
to be delegated to the fancy DNS s
One reasonable suggestion that I have heard recently was to do like Google
does and put a DNS front end onto Zookeeper. Machines would need to have
DNS set up properly and a requests for a special ZK based domain would have
to be delegated to the fancy DNS setup, but this would allow all kinds of
On 03/07/11 03:11, Raja Nagendra Kumar wrote:
Hi,
Instead of depending on local syncup to configuration files, would it be a
nice way to adopt JINI Discovery model, where in masters and slaves can
discover each other dynamically through a UDP broadcast/heart beat methods
That assumes that UDP
automatically discover the master and start supporting the master with in <
x seconds.
Regards,
Raja Nagendra Kumar,
C.T.O
www.tejasoft.com
-Hadoop Adoption Consulting
--
View this message in context:
http://old.nabble.com/Hadoop-Master-and-Slave-Discovery-tp31981952p31981952.html
Sent from
16 matches
Mail list logo
