From issues-return-70738-archive-asf-public=cust-asf.ponee.io@ignite.apache.org Tue Jul 31 06:54:04 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 563BA180662 for ; Tue, 31 Jul 2018 06:54:04 +0200 (CEST) Received: (qmail 9328 invoked by uid 500); 31 Jul 2018 04:54:03 -0000 Mailing-List: contact issues-help@ignite.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@ignite.apache.org Delivered-To: mailing list issues@ignite.apache.org Received: (qmail 9319 invoked by uid 99); 31 Jul 2018 04:54:03 -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; Tue, 31 Jul 2018 04:54:03 +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 F3311180533 for ; Tue, 31 Jul 2018 04:54:02 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd3-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -109.501 X-Spam-Level: X-Spam-Status: No, score=-109.501 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, USER_IN_DEF_SPF_WL=-7.5, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd3-us-west.apache.org [10.40.0.10]) (amavisd-new, port 10024) with ESMTP id uQqteGRg4JgP for ; Tue, 31 Jul 2018 04:54:01 +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 155065F19B for ; Tue, 31 Jul 2018 04:54: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 459CDE00D2 for ; Tue, 31 Jul 2018 04:54: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 065A127756 for ; Tue, 31 Jul 2018 04:54:00 +0000 (UTC) Date: Tue, 31 Jul 2018 04:54:00 +0000 (UTC) From: "Sergey Kosarev (JIRA)" To: issues@ignite.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (IGNITE-9135) TcpDiscovery - High Workload in Stable topology (MessageWorkerQueueSize peaks) 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/IGNITE-9135?page=3Dcom.atlassi= an.jira.plugin.system.issuetabpanels:all-tabpanel ] Sergey Kosarev updated IGNITE-9135: ----------------------------------- Description:=20 On High topology (about 200 servers/ 50 clients) we see often=C2=A0 via jmx= (TcpDiscoverySpiMBean) high MessageWorkerQueueSize peaks (>100)=C2=A0in st= able cluster topology. Also very high number (about 250000) of ProcesedMess= ages, ReceivedMessages for TcpDiscoveryStatusCheckMessage, whereas TcpDisco= veryMetricsUpdateMessage is about 110000. Actually [org.apache.ignite.spi.discovery.tcp.ServerImpl.RingMessageWorker#= metricsCheckFreq|https://github.com/apache/ignite/blob/5faffcee7cfaae90d309= 3e624d27f1b69554ea10/modules/core/src/main/java/org/apache/ignite/spi/disco= very/tcp/ServerImpl.java#L2560] value does not depend on topology size: private long metricsCheckFreq =3D 3 * spi.metricsUpdateFreq + 50; =C2=A0 Why dow we have such peaks on stable topology?=C2=A0 =C2=A0Consider=C2=A0change=C2=A0metricsCheckFreq formula to depend on topol= ogy size. =C2=A0 was: On High topology (about 200 servers/ 50 clients) we see often=C2=A0 via jmx= (TcpDiscoverySpiMBean) high MessageWorkerQueueSize peaks (>100)=C2=A0in st= able cluster topology. Also very high number (about 250000) of ProcesedMess= ages, ReceivedMessages for TcpDiscoveryStatusCheckMessage, whereas TcpDisco= veryMetricsUpdateMessage is about 110000. Actually [org.apache.ignite.spi.discovery.tcp.ServerImpl.RingMessageWorker#= metricsCheckFreq|https://github.com/apache/ignite/blob/d73211d2c1fc3897681a= 3abdc98c5eb383d24475/modules/core/src/main/java/org/apache/ignite/spi/disco= very/tcp/ServerImpl.java#L2628] value does not depend on topology size: private long metricsCheckFreq =3D 3 * spi.metricsUpdateFreq + 50; =C2=A0 Why dow we have such peaks on stable topology?=C2=A0 =C2=A0Consider=C2=A0change=C2=A0metricsCheckFreq formula to depend on topol= ogy size. =C2=A0 > TcpDiscovery - High Workload in Stable topology (MessageWorkerQueueSize p= eaks) > -------------------------------------------------------------------------= ----- > > Key: IGNITE-9135 > URL: https://issues.apache.org/jira/browse/IGNITE-9135 > Project: Ignite > Issue Type: Bug > Reporter: Sergey Kosarev > Priority: Major > Attachments: IMG_20180731_014146_HDR.jpg, IMG_20180731_015439_HDR= .jpg > > > On High topology (about 200 servers/ 50 clients) we see often=C2=A0 via j= mx (TcpDiscoverySpiMBean) high MessageWorkerQueueSize peaks (>100)=C2=A0in = stable cluster topology. Also very high number (about 250000) of ProcesedMe= ssages, ReceivedMessages for TcpDiscoveryStatusCheckMessage, whereas TcpDis= coveryMetricsUpdateMessage is about 110000. > Actually [org.apache.ignite.spi.discovery.tcp.ServerImpl.RingMessageWorke= r#metricsCheckFreq|https://github.com/apache/ignite/blob/5faffcee7cfaae90d3= 093e624d27f1b69554ea10/modules/core/src/main/java/org/apache/ignite/spi/dis= covery/tcp/ServerImpl.java#L2560] value does not depend on topology size: > private long metricsCheckFreq =3D 3 * spi.metricsUpdateFreq + 50; > =C2=A0 > Why dow we have such peaks on stable topology?=C2=A0 > =C2=A0Consider=C2=A0change=C2=A0metricsCheckFreq formula to depend on top= ology size. > =C2=A0 -- This message was sent by Atlassian JIRA (v7.6.3#76005)