Marton Elek created HDDS-3330:
---------------------------------
Summary: TestDeleteWithSlowFollower is still flaky
Key: HDDS-3330
URL: https://issues.apache.org/jira/browse/HDDS-3330
Project: Hadoop Distributed Data Store
Issue Type: Improvement
Components: test
Reporter: Marton Elek
Assignee: Shashikant Banerjee
{code}
Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 666.209 s <<<
FAILURE! - in org.apache.hadoop.ozone.client.rpc.TestDeleteWithSlowFollower
testDeleteKeyWithSlowFollower(org.apache.hadoop.ozone.client.rpc.TestDeleteWithSlowFollower)
Time elapsed: 640.745 s <<< ERROR!
java.io.IOException: INTERNAL_ERROR
org.apache.hadoop.ozone.om.exceptions.OMException: Allocated 0 blocks.
Requested 1 blocks
at
org.apache.hadoop.ozone.client.io.KeyOutputStream.handleWrite(KeyOutputStream.java:229)
at
org.apache.hadoop.ozone.client.io.KeyOutputStream.handleRetry(KeyOutputStream.java:402)
at
org.apache.hadoop.ozone.client.io.KeyOutputStream.handleException(KeyOutputStream.java:347)
at
org.apache.hadoop.ozone.client.io.KeyOutputStream.handleFlushOrClose(KeyOutputStream.java:458)
at
org.apache.hadoop.ozone.client.io.KeyOutputStream.close(KeyOutputStream.java:509)
at
org.apache.hadoop.ozone.client.io.OzoneOutputStream.close(OzoneOutputStream.java:60)
at
org.apache.hadoop.ozone.client.rpc.TestDeleteWithSlowFollower.testDeleteKeyWithSlowFollower(TestDeleteWithSlowFollower.java:225)
{code}
I learned this from [~shashikant]
bq. we kill a datanode after some IO, SCM is out of safe mode by then . SCM
takes time to destroy a pipeline and form a new one
bq. With only minimal set of dn in cluster, if we want to write again, we need
to wait for a new pipeline to open up before writing again
Will turn off this test until the fix.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: ozone-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: ozone-issues-h...@hadoop.apache.org
