Hi Kumar,
It seems like the fix for this bug addresses the root cause of the problem,
but doesn't seem to help when the NameNode already suffers this problem.
I would suggest you to download Hadoop 2.7.2, add a try catch block to
catch/swallow the NPE exception. Rebuild it and see if the NameNode
unsubscribe
Hi,
In Hadoop-2.7.2, i am getting same error reported in here
https://issues.apache.org/jira/browse/HDFS-12985
Is there patch available for hadoop-2.7.2 version? How can i restart
namenode without null pointer exception?
Thanks,
Kumar
Hi Takanobu,
sorry for the late reply, I missed your email.
That looks good, I'll take a look at that.
Cheers,
Lars
On Fri, Jul 5, 2019 at 6:47 AM Takanobu Asanuma
wrote:
> Hi Lars,
>
> I investigated it further. BlockPlacementPolicyWithNodeGroup may achieve
> your goal.
>
>
