[
https://issues.apache.org/jira/browse/HDFS-1984?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Todd Lipcon updated HDFS-1984:
------------------------------
Component/s: name-node
Description:
One of the motivations of HDFS-1073 is that it decouples the checkpoint process
so that multiple checkpoints could be taken at the same time and not interfere
with each other.
Currently on the 1073 branch this doesn't quite work right, since we have some
state and validation in FSImage that's tied to a single fsimage_N -- thus if
two 2NNs perform a checkpoint at different transaction IDs, only one will
succeed.
As a stress test, we can run two 2NNs each configured with the
fs.checkpoint.interval set to "0" which causes them to continuously checkpoint
as fast as they can.
Affects Version/s: Edit log branch (HDFS-1073)
Fix Version/s: Edit log branch (HDFS-1073)
> HDFS-1073: Enable multiple checkpointers to run simultaneously
> --------------------------------------------------------------
>
> Key: HDFS-1984
> URL: https://issues.apache.org/jira/browse/HDFS-1984
> Project: Hadoop HDFS
> Issue Type: Sub-task
> Components: name-node
> Affects Versions: Edit log branch (HDFS-1073)
> Reporter: Todd Lipcon
> Assignee: Todd Lipcon
> Fix For: Edit log branch (HDFS-1073)
>
>
> One of the motivations of HDFS-1073 is that it decouples the checkpoint
> process so that multiple checkpoints could be taken at the same time and not
> interfere with each other.
> Currently on the 1073 branch this doesn't quite work right, since we have
> some state and validation in FSImage that's tied to a single fsimage_N --
> thus if two 2NNs perform a checkpoint at different transaction IDs, only one
> will succeed.
> As a stress test, we can run two 2NNs each configured with the
> fs.checkpoint.interval set to "0" which causes them to continuously
> checkpoint as fast as they can.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
