From issues-return-189012-archive-asf-public=cust-asf.ponee.io@spark.apache.org Tue Apr 10 20:33:40 2018 Return-Path: X-Original-To: archive-asf-public@cust-asf.ponee.io Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by mx-eu-01.ponee.io (Postfix) with SMTP id 5F9D118064C for ; Tue, 10 Apr 2018 20:33:40 +0200 (CEST) Received: (qmail 4626 invoked by uid 500); 10 Apr 2018 18:33:39 -0000 Mailing-List: contact issues-help@spark.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Delivered-To: mailing list issues@spark.apache.org Received: (qmail 4617 invoked by uid 99); 10 Apr 2018 18:33:39 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd4-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 10 Apr 2018 18:33:39 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd4-us-west.apache.org (ASF Mail Server at spamd4-us-west.apache.org) with ESMTP id 0EA71C03DE for ; Tue, 10 Apr 2018 18:33:39 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd4-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -110.311 X-Spam-Level: X-Spam-Status: No, score=-110.311 tagged_above=-999 required=6.31 tests=[ENV_AND_HDR_SPF_MATCH=-0.5, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_SPF_WL=-7.5, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd4-us-west.apache.org [10.40.0.11]) (amavisd-new, port 10024) with ESMTP id mFh0T3wy4q21 for ; Tue, 10 Apr 2018 18:33:37 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTP id B1AA36134D for ; Tue, 10 Apr 2018 18:24: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 08539E0BD4 for ; Tue, 10 Apr 2018 18:24:01 +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 B1E66241D4 for ; Tue, 10 Apr 2018 18:24:00 +0000 (UTC) Date: Tue, 10 Apr 2018 18:24:00 +0000 (UTC) From: "shane knapp (JIRA)" To: issues@spark.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Resolved] (SPARK-8571) spark streaming hanging processes upon build exit MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/SPARK-8571?page=3Dcom.atlassia= n.jira.plugin.system.issuetabpanels:all-tabpanel ] shane knapp resolved SPARK-8571. -------------------------------- Resolution: Not A Problem > spark streaming hanging processes upon build exit > ------------------------------------------------- > > Key: SPARK-8571 > URL: https://issues.apache.org/jira/browse/SPARK-8571 > Project: Spark > Issue Type: Bug > Components: Build, DStreams > Environment: centos 6.6 amplab build system > Reporter: shane knapp > Assignee: shane knapp > Priority: Minor > Labels: build, test > > over the past 3 months i've been noticing that there are occasionally han= ging processes on our build system workers after various spark builds have = finished. these are all spark streaming processes. > today i noticed a 3+ hour spark build that was timed out after 200 minute= s (https://amplab.cs.berkeley.edu/jenkins/job/Spark-Master-Maven-pre-YARN/2= 994/), and the matrix build hadoop.version=3D2.0.0-mr1-cdh4.1.2 ran on amp-= jenkins-worker-02. after the timeout, it left the following process (and a= ll of it's children) hanging. > the process' CLI command was: > {quote} > [root@amp-jenkins-worker-02 ~]# ps auxwww|grep 1714 > jenkins 1714 733 2.7 21342148 3642740 ? Sl 07:52 1713:41 java -= Dderby.system.durability=3Dtest -Djava.awt.headless=3Dtrue -Djava.io.tmpdir= =3D/home/jenkins/workspace/Spark-Master-Maven-pre-YARN/hadoop.version/2.0.0= -mr1-cdh4.1.2/label/centos/streaming/target/tmp -Dspark.driver.allowMultipl= eContexts=3Dtrue -Dspark.test.home=3D/home/jenkins/workspace/Spark-Master-M= aven-pre-YARN/hadoop.version/2.0.0-mr1-cdh4.1.2/label/centos -Dspark.testin= g=3D1 -Dspark.ui.enabled=3Dfalse -Dspark.ui.showConsoleProgress=3Dfalse -Db= asedir=3D/home/jenkins/workspace/Spark-Master-Maven-pre-YARN/hadoop.version= /2.0.0-mr1-cdh4.1.2/label/centos/streaming -ea -Xmx3g -XX:MaxPermSize=3D512= m -XX:ReservedCodeCacheSize=3D512m org.scalatest.tools.Runner -R /home/jenk= ins/workspace/Spark-Master-Maven-pre-YARN/hadoop.version/2.0.0-mr1-cdh4.1.2= /label/centos/streaming/target/scala-2.10/classes /home/jenkins/workspace/S= park-Master-Maven-pre-YARN/hadoop.version/2.0.0-mr1-cdh4.1.2/label/centos/s= treaming/target/scala-2.10/test-classes -o -f /home/jenkins/workspace/Spark= -Master-Maven-pre-YARN/hadoop.version/2.0.0-mr1-cdh4.1.2/label/centos/strea= ming/target/surefire-reports/SparkTestSuite.txt -u /home/jenkins/workspace/= Spark-Master-Maven-pre-YARN/hadoop.version/2.0.0-mr1-cdh4.1.2/label/centos/= streaming/target/surefire-reports/. > {quote} > stracing that process doesn't give us much: > {quote} > [root@amp-jenkins-worker-02 ~]# strace -p 1714 > Process 1714 attached - interrupt to quit > futex(0x7ff3cdd269d0, FUTEX_WAIT, 1715, NULL > {quote} > stracing it's children gives is a *little* bit more... some loop like th= is: > {quote} > > futex(0x7ff3c8012d28, FUTEX_WAKE_PRIVATE, 1) =3D 0 > futex(0x7ff3c8012f54, FUTEX_WAIT_PRIVATE, 28969, NULL) =3D 0 > futex(0x7ff3c8012f28, FUTEX_WAKE_PRIVATE, 1) =3D 0 > futex(0x7ff3c8f17954, FUTEX_WAKE_OP_PRIVATE, 1, 1, 0x7ff3c8f17950, {FUTEX= _OP_SET, 0, FUTEX_OP_CMP_GT, 1}) =3D 1 > futex(0x7ff3c8f17928, FUTEX_WAKE_PRIVATE, 1) =3D 1 > futex(0x7ff3c8012d54, FUTEX_WAIT_BITSET_PRIVATE, 1, {2263862, 865233273},= ffffffff) =3D -1 ETIMEDOUT (Connection timed out) > {quote} > and others loop on prtrace_attach (no such process) or restart_syscall (r= esuming interrupted call) > even though this behavior has been solidly pinned to jobs timing out (whi= ch ends w/an aborted, not failed, build), i've seen it happen for failed bu= ilds as well. if i see any hanging processes from failed (not aborted) bui= lds, i will investigate them and update this bug as well. -- This message was sent by Atlassian JIRA (v7.6.3#76005) --------------------------------------------------------------------- To unsubscribe, e-mail: issues-unsubscribe@spark.apache.org For additional commands, e-mail: issues-help@spark.apache.org