[
https://issues.apache.org/jira/browse/HDFS-7991?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14556684#comment-14556684
]
Vinayakumar B commented on HDFS-7991:
-------------------------------------
bq. If doing checkpointing in the active namenode was possible without pausing
the ongoing requests, we would not have moved checkpointing to either secondary
or standby
Yes agree that we cant pause ongoing requests for long time. I actually meant
for these critical situations, not always, saving namespace directly looked
better compare to restart of NN, which also requires someone to monitor the
size of edits and trigger saveNamespace/stop. But in Normal conditions
occurance of this would be very rare. May be If user apps needs to be informed
about the situation, then active NN itself can put itself to safemode before
saving namespace, as done on admin request.
Anyway I am not very strong about safemode or not, that was just a thought as
practically saving just fsImage to disk will take less time, of-course it again
depends on size.
But IMHO, to handle such abnormal cases, NN itself should be able to take
steps, instead of some admin finding out and taking steps.
> Allow users to skip checkpoint when stopping NameNode
> -----------------------------------------------------
>
> Key: HDFS-7991
> URL: https://issues.apache.org/jira/browse/HDFS-7991
> Project: Hadoop HDFS
> Issue Type: Improvement
> Affects Versions: 3.0.0
> Reporter: Jing Zhao
> Assignee: Jing Zhao
> Attachments: HDFS-7991-shellpart.patch, HDFS-7991.000.patch,
> HDFS-7991.001.patch, HDFS-7991.002.patch, HDFS-7991.003.patch,
> HDFS-7991.004.patch
>
>
> This is a follow-up jira of HDFS-6353. HDFS-6353 adds the functionality to
> check if saving namespace is necessary before stopping namenode. As [~kihwal]
> pointed out in this
> [comment|https://issues.apache.org/jira/browse/HDFS-6353?focusedCommentId=14380898&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-14380898],
> in a secured cluster this new functionality requires the user to be kinit'ed.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
