Details
-
Bug
-
Status: Open
-
Critical
-
Resolution: Unresolved
-
None
-
None
-
None
-
None
Description
Setting up Nodegroup locality destroys data-local writes if NM and DN have separate ip addresses.
When NM requests Namenode for 3 DN locations to write to(for replication=3), the Namenode returns a random order every time.
The reason is, Namenode wrongly assumes that it's list of DN's must include the NM's ip address. This assumption breaks down when you deploy NM and DN on separate machines/ip addresses.