From issues-return-150211-archive-asf-public=cust-asf.ponee.io@flink.apache.org Wed Jan 31 03:52:04 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 3F5D418061A for ; Wed, 31 Jan 2018 03:52:04 +0100 (CET) Received: by cust-asf.ponee.io (Postfix) id 2EE4C160C54; Wed, 31 Jan 2018 02:52:04 +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 764A7160C53 for ; Wed, 31 Jan 2018 03:52:03 +0100 (CET) Received: (qmail 20750 invoked by uid 500); 31 Jan 2018 02:52:02 -0000 Mailing-List: contact issues-help@flink.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@flink.apache.org Delivered-To: mailing list issues@flink.apache.org Received: (qmail 20741 invoked by uid 99); 31 Jan 2018 02:52:02 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd3-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 31 Jan 2018 02:52:02 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd3-us-west.apache.org (ASF Mail Server at spamd3-us-west.apache.org) with ESMTP id 1BF6918C43C for ; Wed, 31 Jan 2018 02:52:02 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd3-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -109.511 X-Spam-Level: X-Spam-Status: No, score=-109.511 tagged_above=-999 required=6.31 tests=[ENV_AND_HDR_SPF_MATCH=-0.5, KAM_ASCII_DIVIDERS=0.8, 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 (spamd3-us-west.apache.org [10.40.0.10]) (amavisd-new, port 10024) with ESMTP id i6NGVtPKjPbL for ; Wed, 31 Jan 2018 02:52:01 +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 C1B695F1B9 for ; Wed, 31 Jan 2018 02:52:00 +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 497F4E00B0 for ; Wed, 31 Jan 2018 02:52: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 0ACC521301 for ; Wed, 31 Jan 2018 02:52:00 +0000 (UTC) Date: Wed, 31 Jan 2018 02:52:00 +0000 (UTC) From: "zhu.qing (JIRA)" To: issues@flink.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (FLINK-8526) When use parallelism equals to half of the number of cpu, join and shuffle operators will easly cause deadlock. 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/FLINK-8526?page=3Dcom.atlassia= n.jira.plugin.system.issuetabpanels:all-tabpanel ] zhu.qing updated FLINK-8526: ---------------------------- Description:=20 The next program attached will stuck at some special parallelism in some si= tuation. When parallelism is 80 in previous setting, The program will alway= s stuck. And when parallelism is 100, everything goes well.=C2=A0 According= to my research I found when the parallelism equals to number of taskslots.= The program is not fastest and probably caused network buffer not enough. = How networker buffer related to parallelism and=C2=A0 how parallelism relat= e to running task (In other words we have 160 taskslots but running task ca= n be far more than taskslots).=C2=A0 Parallelism cannot be equals to half of the cpu. Or will casuse "java.io.FileNotFoundException" was:The next program attached will stuck at some special parallelism in s= ome situation. When parallelism is 80 in previous setting, The program will= always stuck. And when parallelism is 100, everything goes well.=C2=A0 Acc= ording to my research I found when the parallelism equals to number of task= slots. The program is not fastest and probably caused network buffer not en= ough. How networker buffer related to parallelism and=C2=A0 how parallelism= relate to running task (In other words we have 160 taskslots but running t= ask can be far more than taskslots).=C2=A0 > When use parallelism equals to half of the number of cpu, join and shuffl= e operators will easly cause deadlock. > -------------------------------------------------------------------------= -------------------------------------- > > Key: FLINK-8526 > URL: https://issues.apache.org/jira/browse/FLINK-8526 > Project: Flink > Issue Type: Bug > Components: Cluster Management, Java API, Local Runtime > Affects Versions: 1.4.0 > Environment: 8 machines(96GB and 24 cores)=C2=A0 and 20 taskslot = per taskmanager. twitter-2010 dataset. And parallelism setting to 80. I run= my code in standalone mode.=C2=A0 > Reporter: zhu.qing > Priority: Major > Attachments: T2AdjActiveV.java, T2AdjMessage.java > > Original Estimate: 72h > Remaining Estimate: 72h > > The next program attached will stuck at some special parallelism in some = situation. When parallelism is 80 in previous setting, The program will alw= ays stuck. And when parallelism is 100, everything goes well.=C2=A0 Accordi= ng to my research I found when the parallelism equals to number of taskslot= s. The program is not fastest and probably caused network buffer not enough= . How networker buffer related to parallelism and=C2=A0 how parallelism rel= ate to running task (In other words we have 160 taskslots but running task = can be far more than taskslots).=C2=A0 > Parallelism cannot be equals to half of the cpu. > Or will casuse "java.io.FileNotFoundException" -- This message was sent by Atlassian JIRA (v7.6.3#76005)