[
https://issues.apache.org/jira/browse/HDDS-2535?focusedWorklogId=345552&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-345552
]
ASF GitHub Bot logged work on HDDS-2535:
----------------------------------------
Author: ASF GitHub Bot
Created on: 18/Nov/19 20:01
Start Date: 18/Nov/19 20:01
Worklog Time Spent: 10m
Work Description: bharatviswa504 commented on pull request #216:
HDDS-2535. TestOzoneManagerDoubleBufferWithOMResponse is flaky.
URL: https://github.com/apache/hadoop-ozone/pull/216
## What changes were proposed in this pull request?
Fix testDoubleBuffer flakiness.
## What is the link to the Apache JIRA
https://issues.apache.org/jira/browse/HDDS-2535
## How was this patch tested?
Ran the test multiple times, I see now it is passing.
----------------------------------------------------------------
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:
[email protected]
Issue Time Tracking
-------------------
Worklog Id: (was: 345552)
Remaining Estimate: 0h
Time Spent: 10m
> TestOzoneManagerDoubleBufferWithOMResponse is flaky
> ---------------------------------------------------
>
> Key: HDDS-2535
> URL: https://issues.apache.org/jira/browse/HDDS-2535
> Project: Hadoop Distributed Data Store
> Issue Type: Bug
> Components: Ozone Manager
> Reporter: Marton Elek
> Assignee: Bharat Viswanadham
> Priority: Major
> Labels: pull-request-available
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Flakiness can be reproduced locally. Usually it passes, but when I started to
> run it 100 times parallel with high cpu load it failed with the 3rd attempt
> (timed out)
> {code:java}
> -------------------------------------------------------------------------------
> Test set:
> org.apache.hadoop.ozone.om.ratis.TestOzoneManagerDoubleBufferWithOMResponse
> -------------------------------------------------------------------------------
> Tests run: 3, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 503.297 s <<<
> FAILURE! - in
> org.apache.hadoop.ozone.om.ratis.TestOzoneManagerDoubleBufferWithOMResponse
> testDoubleBuffer(org.apache.hadoop.ozone.om.ratis.TestOzoneManagerDoubleBufferWithOMResponse)
> Time elapsed: 500.122 s <<< ERROR!
> java.lang.Exception: test timed out after 500000 milliseconds
> at java.lang.Thread.sleep(Native Method)
> at
> org.apache.hadoop.test.GenericTestUtils.waitFor(GenericTestUtils.java:382)
> at
> org.apache.hadoop.ozone.om.ratis.TestOzoneManagerDoubleBufferWithOMResponse.testDoubleBuffer(TestOzoneManagerDoubleBufferWithOMResponse.java:385)
> at
> org.apache.hadoop.ozone.om.ratis.TestOzoneManagerDoubleBufferWithOMResponse.testDoubleBuffer(TestOzoneManagerDoubleBufferWithOMResponse.java:129)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at
> org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:47)
> at
> org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
> at
> org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:44)
> at
> org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
> at
> org.junit.internal.runners.statements.FailOnTimeout$StatementThread.run(FailOnTimeout.java:74)
> {code}
> Independent from the flakiness I think a test where the timeout is 8 minutes
> and starts 1000 threads to insert 500 buckets (500_000 buckets all together)
> it's more like an integration test and would be better to move the slowest
> part to the integration-test project.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
