hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Nanda kumar (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-12940) Ozone: KSM: TestKeySpaceManager#testExpiredOpenKey fails occasionally
Date Sat, 20 Jan 2018 19:13:01 GMT

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

Nanda kumar commented on HDFS-12940:

Thanks [~xyao] for the review. Committed this to the feature branch.

> Ozone: KSM: TestKeySpaceManager#testExpiredOpenKey fails occasionally
> ---------------------------------------------------------------------
>                 Key: HDFS-12940
>                 URL: https://issues.apache.org/jira/browse/HDFS-12940
>             Project: Hadoop HDFS
>          Issue Type: Sub-task
>            Reporter: Nanda kumar
>            Assignee: Nanda kumar
>            Priority: Major
>         Attachments: HDFS-12940-HDFS-7240.000.patch, HDFS-12940-HDFS-7240.001.patch,
HDFS-12940-HDFS-7240.002.patch, HDFS-12940-HDFS-7240.003.patch, HDFS-12940-HDFS-7240.004.patch
> {{TestKeySpaceManager#testExpiredOpenKey}} is flaky.
> In {{testExpiredOpenKey}} we are opening four keys for writing and wait for them to expire
(without committing). Verification/Assertion is done by querying {{MiniOzoneCluster}} and
matching the count. Since the {{cluster}} instance of {{MiniOzoneCluster}} is shared between
test-cases in {{TestKeySpaceManager}}, we should not rely on the count. The verification should
only happen by matching the keyNames and not with the count.

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