[
https://issues.apache.org/jira/browse/HDFS-10722?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15407837#comment-15407837
]
Rakesh R edited comment on HDFS-10722 at 8/4/16 2:25 PM:
---------------------------------------------------------
IMHO, to skip this test case something similar to
[TestEditLog_testSyncBatching|https://github.com/apache/hadoop/blob/trunk/hadoop-hdfs-project/hadoop-hdfs/src/test/java/org/apache/hadoop/hdfs/server/namenode/TestEditLog.java#L511]
approach rather than skipping only the assertion part, am I missing anything
here?
was (Author: rakeshr):
I think to skip this test case something similar to
[TestEditLog_testSyncBatching|https://github.com/apache/hadoop/blob/trunk/hadoop-hdfs-project/hadoop-hdfs/src/test/java/org/apache/hadoop/hdfs/server/namenode/TestEditLog.java#L511]
approach rather than skipping only the assertion part, am I missing anything
here?
> Fix race condition in TestEditLog#testBatchedSyncWithClosedLogs
> ---------------------------------------------------------------
>
> Key: HDFS-10722
> URL: https://issues.apache.org/jira/browse/HDFS-10722
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: hdfs
> Reporter: Daryn Sharp
> Assignee: Daryn Sharp
> Attachments: HDFS-10722.patch
>
>
> The test may fail the following assertion if async edit logs are enabled:
> {{logging edit without syncing should do not affect txid expected:<1> but
> was:<2>}}. The async thread is doing batched syncs in the background.
> logSync just ensures the edit is durable, so the txid may increase prior to
> sync. It's a race.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
