[
https://issues.apache.org/jira/browse/HDFS-15555?focusedWorklogId=483747&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-483747
]
ASF GitHub Bot logged work on HDFS-15555:
-----------------------------------------
Author: ASF GitHub Bot
Created on: 14/Sep/20 02:35
Start Date: 14/Sep/20 02:35
Worklog Time Spent: 10m
Work Description: aajisaka commented on pull request #2267:
URL: https://github.com/apache/hadoop/pull/2267#issuecomment-691776918
Merged. Thank you @goiri for your review.
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
[email protected]
Issue Time Tracking
-------------------
Worklog Id: (was: 483747)
Time Spent: 2h 20m (was: 2h 10m)
> RBF: Refresh cacheNS when SocketException occurs
> ------------------------------------------------
>
> Key: HDFS-15555
> URL: https://issues.apache.org/jira/browse/HDFS-15555
> Project: Hadoop HDFS
> Issue Type: Sub-task
> Components: rbf
> Environment: HDFS 3.3.0, Java 11
> Reporter: Akira Ajisaka
> Assignee: Akira Ajisaka
> Priority: Major
> Labels: pull-request-available
> Time Spent: 2h 20m
> Remaining Estimate: 0h
>
> Problem:
> When active NameNode is restarted and loading fsimage, DFSRouters
> significantly slow down.
> Investigation:
> When active NameNode is restarted and loading fsimage, RouterRpcClient
> receives SocketException. Since
> RouterRpcClient#isUnavailableException(IOException) returns false when the
> argument is SocketException, the MembershipNameNodeResolver#cacheNS is not
> refreshed. That's why the order of the NameNodes returned by
> MemberShipNameNodeResolver#getNamenodesForNameserviceId(String) is unchanged
> and the active NameNode is still returned first. Therefore RouterRpcClient
> still tries to connect to the NameNode that is loading fsimage.
> After loading the fsimage, the NameNode throws StandbyException. The
> exception is one of the 'Unavailable Exception' and the cacheNS is refreshed.
> Workaround:
> Stop NameNode and wait 1 minute before starting NameNode instead of
> restarting.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
