Federated namenodes are independent of one another (except that they
both get reports from all the/common DNs in the cluster). It is
natural to see one roll its edit logs based on its own rate of
metadata growth, as compared to the other. Their edits, image, etc.
everything is independent - they also do not know about/talk to each
Given the above, I'd say (1) is true and (2) is invalid, and (3) can
be found in PDFs attached to
On Sun, Feb 24, 2013 at 8:39 PM, YouPeng Yang <[EMAIL PROTECTED]> wrote:
> Hi All
> I'm testing the HDFS Federation.I have 2 namenodes in my cluster.
> I find that it is Rolling Edit Log continuously on one namenode,however
> the other one changes nothing.
> My question :
> 1. Is it the right situation.
> 2. I have thought that the two namenodes shoud keep concurrency.
> why they get differences.
> 3. is there any advanced docs about HDFS Federation.