[
https://issues.apache.org/jira/browse/HDFS-12940?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16299767#comment-16299767
]
Nanda kumar commented on HDFS-12940:
------------------------------------
Chen, thanks for testing it.
For now, I'm going with the first approach that you have explained, if the
test-case is still not stable with this change we can move it to a separate
test class. I ran multiple times after making the change and it didn't fail in
my local.
bq. We may also want to decrease the check interval and cleanup threshold to
make this test run faster.
I tried to change it from 2 sec to 1 sec, but other test-cases started failing
randomly with {{java.io.IOException: Commit key failed, error:KEY_NOT_FOUND}}.
So not going ahead with reducing the time interval.
> 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]
