hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Work logged] (HDDS-1780) TestFailureHandlingByClient tests are flaky
Date Tue, 16 Jul 2019 16:53:00 GMT

     [ https://issues.apache.org/jira/browse/HDDS-1780?focusedWorklogId=277584&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-277584

ASF GitHub Bot logged work on HDDS-1780:

                Author: ASF GitHub Bot
            Created on: 16/Jul/19 16:52
            Start Date: 16/Jul/19 16:52
    Worklog Time Spent: 10m 
      Work Description: adoroszlai commented on pull request #1073: HDDS-1780. TestFailureHandlingByClient
tests are flaky.
URL: https://github.com/apache/hadoop/pull/1073#discussion_r304001568

 File path: hadoop-hdds/client/src/main/java/org/apache/hadoop/hdds/scm/storage/BlockOutputStream.java
 @@ -160,7 +159,7 @@ public BlockOutputStream(BlockID blockID,
     bufferList = null;
     totalDataFlushedLength = 0;
     writtenDataLength = 0;
-    failedServers = Collections.emptyList();
+    failedServers = new ArrayList<>(0);
 Review comment:
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:

Issue Time Tracking

    Worklog Id:     (was: 277584)
    Time Spent: 0.5h  (was: 20m)

> TestFailureHandlingByClient tests are flaky
> -------------------------------------------
>                 Key: HDDS-1780
>                 URL: https://issues.apache.org/jira/browse/HDDS-1780
>             Project: Hadoop Distributed Data Store
>          Issue Type: Bug
>          Components: Ozone Client
>    Affects Versions: 0.5.0
>            Reporter: Shashikant Banerjee
>            Assignee: Shashikant Banerjee
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 0.5.0
>          Time Spent: 0.5h
>  Remaining Estimate: 0h
> The tests seem to fail bcoz , when the datanode goes down with stale node interval being
set to a low value, containers may get closed early and client writes might fail with closed
container exception rather than pipeline failure/Timeout exceptions as excepted in the tests.
The fix made here is to tune the stale node interval.

This message was sent by Atlassian JIRA

To unsubscribe, e-mail: hdfs-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-help@hadoop.apache.org

View raw message