[
https://issues.apache.org/jira/browse/HDFS-9430?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15037669#comment-15037669
]
Brahma Reddy Battula commented on HDFS-9430:
--------------------------------------------
bq. I agree that the RPC server is fine. We should check the web interface:
I have checked the call heirarchy of all FSNamesystem calls where
{{waitForLoadingFsImage()}} is present. Everything goes through RPC server,
except test calls and {{LeaseManager#checkLeases()}}.
1. TestCalls will be safe, as MiniDfsCluster ensures that it waits till
complete startup of cluster.
2. {{LeaseManager#checkLeases()}} will be called only when NN is out of
safemode, which inturn ensures that image is already loaded.
So IMO, nothing should be affected by removal of {{waitForLoadingFsImage()}}.
> waitforloadingfsimage() can be removed since checknnstartup() already ensures
> image loaded and namenode started.
> ----------------------------------------------------------------------------------------------------------------
>
> Key: HDFS-9430
> URL: https://issues.apache.org/jira/browse/HDFS-9430
> Project: Hadoop HDFS
> Issue Type: Bug
> Reporter: Brahma Reddy Battula
> Assignee: Brahma Reddy Battula
> Attachments: HDFS-9430.patch
>
>
> After initial startup,loading fsimage in between happens only for
> secondarynn..But it wn't server any client requests.
> So IMO it would be ok to remove it.
> Please check commement [here
> |https://issues.apache.org/jira/browse/HDFS-9413?focusedCommentId=15005129&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-15005129]
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
