You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues-all@impala.apache.org by "Tim Armstrong (Jira)" <ji...@apache.org> on 2020/11/17 20:16:00 UTC
[jira] [Commented] (IMPALA-9832) Runaway disk usage for ASAN test
run
[ https://issues.apache.org/jira/browse/IMPALA-9832?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17233930#comment-17233930 ]
Tim Armstrong commented on IMPALA-9832:
---------------------------------------
[~joemcdonnell] any idea what happened here or if it's recurred?
> Runaway disk usage for ASAN test run
> ------------------------------------
>
> Key: IMPALA-9832
> URL: https://issues.apache.org/jira/browse/IMPALA-9832
> Project: IMPALA
> Issue Type: Bug
> Components: Backend
> Affects Versions: Impala 4.0
> Reporter: Joe McDonnell
> Priority: Critical
> Labels: broken-build, flaky
>
> A recent ASAN run saw hundreds of test failures due to the HDFS NameNode going into safe mode due to lack of disk space:
> {noformat}
> 2020-06-05 01:03:36,366 WARN org.apache.hadoop.hdfs.server.namenode.NameNodeResourceChecker: Space available on volume '/dev/nvme0n1p1' is 4419584, which is below the configured reserved amount 104857600
> 2020-06-05 01:03:36,366 WARN org.apache.hadoop.hdfs.server.namenode.FSNamesystem: NameNode low on available disk space. Entering safe mode.{noformat}
> Metrics about diskspace usage at the time show the device (which had a capacity of 300GB) getting to 99-100% disk usage. Previous runs on the same configuration usually stayed in the 35-40% range. The core job with the same commits also stayed in the 35-40% range.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-all-unsubscribe@impala.apache.org
For additional commands, e-mail: issues-all-help@impala.apache.org