[
https://issues.apache.org/jira/browse/HDFS-9904?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15183248#comment-15183248
]
Kihwal Lee commented on HDFS-9904:
----------------------------------
Thanks for working on the fix. The config is used to determine whether to
create a new checkpoint. A standby will, after loading/replaying edits, check
how many transactions went by since the last checkpoint. If the number is
greater than the configured limit, it will do checkpoint. As you can see from
the test output, there are around 106 transactions at the end. In order to
prevent the standby from checkpointing, the config value should be bigger than
that. E.g. 1000. Also, it should be set before the namenode is started and
should be reset for other test cases.
> testCheckpointCancellationDuringUpload occasionally fails
> ----------------------------------------------------------
>
> Key: HDFS-9904
> URL: https://issues.apache.org/jira/browse/HDFS-9904
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: test
> Affects Versions: 2.7.3
> Reporter: Kihwal Lee
> Attachments: HDFS-9904.001.patch
>
>
> The failure was at the end of the test case where the txid of the standby
> (former active) is checked. Since the checkpoint/uploading was canceled , it
> is not supposed to have the new checkpoint. Looking at the test log, that was
> still the case, but the standby then did checkpoint on its own and bumped up
> the txid, right before the check was performed.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
