You are viewing a plain text version of this content. The canonical link for it is here.
Posted to hdfs-issues@hadoop.apache.org by "Doroszlai, Attila (JIRA)" <ji...@apache.org> on 2019/08/13 13:34:00 UTC
[jira] [Commented] (HDDS-1952) TestMiniChaosOzoneCluster may run
until OOME
[ https://issues.apache.org/jira/browse/HDDS-1952?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16906203#comment-16906203 ]
Doroszlai, Attila commented on HDDS-1952:
-----------------------------------------
[~nandakumar131], please note that my pull request is just a "workaround". I think it would be nice to investigate the underlying problem. I'm fine with filing a new Jira issue for that.
> TestMiniChaosOzoneCluster may run until OOME
> --------------------------------------------
>
> Key: HDDS-1952
> URL: https://issues.apache.org/jira/browse/HDDS-1952
> Project: Hadoop Distributed Data Store
> Issue Type: Bug
> Components: test
> Reporter: Doroszlai, Attila
> Assignee: Doroszlai, Attila
> Priority: Critical
> Labels: pull-request-available
> Time Spent: 50m
> Remaining Estimate: 0h
>
> {{TestMiniChaosOzoneCluster}} runs load generator on a cluster for supposedly 1 minute, but it may run indefinitely until JVM crashes due to OutOfMemoryError.
> In 0.4.1 nightly build it crashed 29/30 times (and no tests were executed in the remaining one run due to some other error).
> Latest:
> https://github.com/elek/ozone-ci/blob/3f553ed6ad358ba61a302967617de737d7fea01a/byscane/byscane-nightly-wggqd/integration/output.log#L5661-L5662
> When it crashes, it leaves GBs of data lying around.
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-help@hadoop.apache.org