[
https://issues.apache.org/jira/browse/HDFS-12521?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16209151#comment-16209151
]
Lokesh Jain commented on HDFS-12521:
------------------------------------
Thanks for the review [~linyiqun]. The v3 patch addresses the issues pointed
out by you.
Regarding the comment :-
_line204: We can just print the error info instead of checking message then log
error. The error message contained in exception can be showed in logging.
Another point, please use LOG.error here.
_
I did this so that unnecessary exception information is not printed in the
logs. Because on start the container db is empty and listContainer would raise
an exception when used for initializing ContainerStateManager.
> Ozone: SCM should read all Container info into memory when booting up
> ---------------------------------------------------------------------
>
> Key: HDFS-12521
> URL: https://issues.apache.org/jira/browse/HDFS-12521
> Project: Hadoop HDFS
> Issue Type: Sub-task
> Components: ozone
> Reporter: Anu Engineer
> Assignee: Lokesh Jain
> Labels: ozoneMerge
> Attachments: HDFS-12521-HDFS-7240.001.patch,
> HDFS-12521-HDFS-7240.002.patch, HDFS-12521-HDFS-7240.003.patch
>
>
> When SCM boots up it should read all containers into memory. This is a
> performance optimization that allows delays on SCM side. This JIRA tracks
> that issue.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
