From common-issues-return-146404-archive-asf-public=cust-asf.ponee.io@hadoop.apache.org Wed Jan 3 22:42:05 2018 Return-Path: X-Original-To: archive-asf-public@eu.ponee.io Delivered-To: archive-asf-public@eu.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by mx-eu-01.ponee.io (Postfix) with ESMTP id 8435F18077A for ; Wed, 3 Jan 2018 22:42:05 +0100 (CET) Received: by cust-asf.ponee.io (Postfix) id 73F3B160C1B; Wed, 3 Jan 2018 21:42:05 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id B9898160C05 for ; Wed, 3 Jan 2018 22:42:04 +0100 (CET) Received: (qmail 68902 invoked by uid 500); 3 Jan 2018 21:42:03 -0000 Mailing-List: contact common-issues-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Delivered-To: mailing list common-issues@hadoop.apache.org Received: (qmail 68891 invoked by uid 99); 3 Jan 2018 21:42:03 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd1-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 03 Jan 2018 21:42:03 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd1-us-west.apache.org (ASF Mail Server at spamd1-us-west.apache.org) with ESMTP id 3B357C1AC5 for ; Wed, 3 Jan 2018 21:42:03 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd1-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -99.211 X-Spam-Level: X-Spam-Status: No, score=-99.211 tagged_above=-999 required=6.31 tests=[KAM_ASCII_DIVIDERS=0.8, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd1-us-west.apache.org [10.40.0.7]) (amavisd-new, port 10024) with ESMTP id GIWW6KGBCo2W for ; Wed, 3 Jan 2018 21:42:02 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTP id B69305FAEF for ; Wed, 3 Jan 2018 21:42:01 +0000 (UTC) Received: from jira-lw-us.apache.org (unknown [207.244.88.139]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id DE117E0F55 for ; Wed, 3 Jan 2018 21:42:00 +0000 (UTC) Received: from jira-lw-us.apache.org (localhost [127.0.0.1]) by jira-lw-us.apache.org (ASF Mail Server at jira-lw-us.apache.org) with ESMTP id 47B29240F6 for ; Wed, 3 Jan 2018 21:42:00 +0000 (UTC) Date: Wed, 3 Jan 2018 21:42:00 +0000 (UTC) From: "Allen Wittenauer (JIRA)" To: common-issues@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Comment Edited] (HADOOP-15153) [branch-2.8] Increase heap memory to avoid the OOM in pre-commit MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/HADOOP-15153?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16310329#comment-16310329 ] Allen Wittenauer edited comment on HADOOP-15153 at 1/3/18 9:41 PM: ------------------------------------------------------------------- bq. Hoping INFRA-15685 will be pushed soon so that jenkins will be happy Not likely. Someone should probably upgrade surefire since that helped trunk tremendously. But branch-2 shows the problem significantly worse than trunk, so there are likely other things going on there too. With the vendors having mostly decided to run their own testing pipelines, it's pretty much a community problem at this point. bq. AFAIK,this problem with only HDFS project. Mostly. Rarely common and sometimes MR. See HDFS-12711 and any reports that talk about unreaped processes. This has been a problem for months. Yetus is just smart enough now to stop it from crashing the boxes. was (Author: aw): bq. Hoping INFRA-15685 will be pushed soon so that jenkins will be happy Not likely. Someone should probably upgrade surefire since that helped trunk tremendously. But branch-2 shows the problem significantly worse than trunk, so there are likely other things going on there too. With the vendors having mostly decided to run their own testing pipelines, it's pretty much a community problem at this point. bq. AFAIK,this problem with only HDFS project. Mostly. Rarely common and sometimes MR. See HDFS-12711 and any reports that talk about unreaped processes. This has been a problem for months. Yetus is just smart enough know to stop it from crashing the boxes. > [branch-2.8] Increase heap memory to avoid the OOM in pre-commit > ---------------------------------------------------------------- > > Key: HADOOP-15153 > URL: https://issues.apache.org/jira/browse/HADOOP-15153 > Project: Hadoop Common > Issue Type: Bug > Components: build > Reporter: Brahma Reddy Battula > Assignee: Brahma Reddy Battula > Attachments: HADOOP-15153-branch-2.8.patch > > > Refernce: > https://builds.apache.org/job/PreCommit-HDFS-Build/22528/consoleFull > https://builds.apache.org/job/PreCommit-HDFS-Build/22528/artifact/out/branch-mvninstall-root.txt > {noformat} > [ERROR] unable to create new native thread -> [Help 1] > [ERROR] > [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch. > [ERROR] Re-run Maven using the -X switch to enable full debug logging. > [ERROR] > [ERROR] For more information about the errors and possible solutions, please read the following articles: > [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/OutOfMemoryError > {noformat} -- This message was sent by Atlassian JIRA (v6.4.14#64029) --------------------------------------------------------------------- To unsubscribe, e-mail: common-issues-unsubscribe@hadoop.apache.org For additional commands, e-mail: common-issues-help@hadoop.apache.org