[
https://issues.apache.org/jira/browse/HDFS-12940?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16309398#comment-16309398
]
Nanda kumar commented on HDFS-12940:
------------------------------------
[~vagarychen], it fails occasionally. Once or twice in every twenty runs. Even
in the previous build of this jira testWriteSize and testListKeys has failed
with {{Commit key failed, error:KEY_NOT_FOUND}}
[TestKeySpaceManager#testWriteSize failure |
https://builds.apache.org/job/PreCommit-HDFS-Build/22483/testReport/org.apache.hadoop.ozone.ksm/TestKeySpaceManager/testWriteSize/]
[TestKeySpaceManager#testListKeys failure |
https://builds.apache.org/job/PreCommit-HDFS-Build/22483/testReport/org.apache.hadoop.ozone.ksm/TestKeySpaceManager/testListKeys/]
I will move {{testExpiredOpenKey}} to a separate test class as you suggested.
> 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
> Attachments: HDFS-12940-HDFS-7240.000.patch,
> HDFS-12940-HDFS-7240.001.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
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
