[
https://issues.apache.org/jira/browse/HDFS-9904?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lin Yiqun updated HDFS-9904:
----------------------------
Attachment: HDFS-9904.001.patch
Attach a simple patch as you said, I tested the modified testcase in local and
the result is good.
{code}
-------------------------------------------------------
T E S T S
-------------------------------------------------------
Running org.apache.hadoop.hdfs.server.namenode.ha.TestStandbyCheckpoints
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 21.487 sec - in
org.apache.hadoop.hdfs.server.namenode.ha.TestStandbyCheckpoints
Results :
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0
[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESS
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 45.985 s
[INFO] Finished at: 2016-03-07T10:09:19+08:00
[INFO] Final Memory: 44M/951M
[INFO] ------------------------------------------------------------------------
{code}
> 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)
