Mailing-List: contact hdfs-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Date: Thu, 4 Aug 2016 14:58:20 +0000 (UTC)
From: "Daryn Sharp (JIRA)" <jira@apache.org>
To: hdfs-issues@hadoop.apache.org
Message-ID: <JIRA.12994895.1470317697000.225038.1470322700707@Atlassian.JIRA>
In-Reply-To: <JIRA.12994895.1470317697000@Atlassian.JIRA>
References: <JIRA.12994895.1470317697000@Atlassian.JIRA> <JIRA.12994895.1470317697932@arcas>
Subject: [jira] [Commented] (HDFS-10722) Fix race condition in
 TestEditLog#testBatchedSyncWithClosedLogs
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Thu, 04 Aug 2016 14:58:23 -0000


    [ https://issues.apache.org/jira/browse/HDFS-10722?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15407891#comment-15407891 ] 

Daryn Sharp commented on HDFS-10722:
------------------------------------

The remainder of the test case still has value so I wouldn't short out the entire test.

> 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: hdfs-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-help@hadoop.apache.org