Details
-
Bug
-
Status: Resolved
-
Major
-
Resolution: Fixed
-
None
-
None
-
Reviewed
Description
The datanode should know which NN is active when it is connecting/registering to the NN. Currently, it only figures this out during its first (and subsequent) heartbeat(s) and so there is a period of time where the datanode is alive and registered, but can't actually do anything because it doesn't know which NN is active. A byproduct of this is that the MiniDFSCluster will become active before it knows what NN is active, which can lead to NPEs when calling getActiveNN().