From issues-return-89019-archive-asf-public=cust-asf.ponee.io@ignite.apache.org Thu Jan 24 02:21:05 2019 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 7319C18066C for ; Thu, 24 Jan 2019 02:21:05 +0100 (CET) Received: (qmail 1476 invoked by uid 500); 24 Jan 2019 01:21:04 -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 1467 invoked by uid 99); 24 Jan 2019 01:21:04 -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; Thu, 24 Jan 2019 01:21:04 +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 087F01805E8 for ; Thu, 24 Jan 2019 01:21:04 +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 2VyND86htowY for ; Thu, 24 Jan 2019 01:21: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 2ADBE5F583 for ; Thu, 24 Jan 2019 01:21: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 5E0C9E00A7 for ; Thu, 24 Jan 2019 01:21: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 0843A242A2 for ; Thu, 24 Jan 2019 01:21:00 +0000 (UTC) Date: Thu, 24 Jan 2019 01:21:00 +0000 (UTC) From: "Evgenii Zhuravlev (JIRA)" To: issues@ignite.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (IGNITE-11052) Add documentation for "failed to wait for partition map exchange" message 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/IGNITE-11052?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Evgenii Zhuravlev updated IGNITE-11052: --------------------------------------- Description: We should describe why this message could be seen in logs and how to debug the real problem that caused this message. This message can be printed in the case when cluster trying to change topology version when some of the operations still running on the previous topology version. It could be either long running operations which could finish successfully after a while or deadlock(or some other operations, that won't be able to finish by some reason) Here are some examples on the user list: http://apache-ignite-users.70518.x6.nabble.com/Failed-to-wait-for-initial-partition-map-exchange-td6252i20.html http://apache-ignite-users.70518.x6.nabble.com/Large-durable-caches-td20097i20.html http://apache-ignite-users.70518.x6.nabble.com/Cache-operations-hanging-for-a-minute-when-one-of-server-nodes-goes-down-td21964.html was:We should describe why this message could be seen in logs and how to debug the real problem that caused this message. > Add documentation for "failed to wait for partition map exchange" message > ------------------------------------------------------------------------- > > Key: IGNITE-11052 > URL: https://issues.apache.org/jira/browse/IGNITE-11052 > Project: Ignite > Issue Type: Improvement > Components: documentation > Reporter: Evgenii Zhuravlev > Assignee: Denis Magda > Priority: Major > > We should describe why this message could be seen in logs and how to debug the real problem that caused this message. > This message can be printed in the case when cluster trying to change topology version when some of the operations still running on the previous topology version. It could be either long running operations which could finish successfully after a while or deadlock(or some other operations, that won't be able to finish by some reason) > Here are some examples on the user list: > http://apache-ignite-users.70518.x6.nabble.com/Failed-to-wait-for-initial-partition-map-exchange-td6252i20.html > http://apache-ignite-users.70518.x6.nabble.com/Large-durable-caches-td20097i20.html > http://apache-ignite-users.70518.x6.nabble.com/Cache-operations-hanging-for-a-minute-when-one-of-server-nodes-goes-down-td21964.html -- This message was sent by Atlassian JIRA (v7.6.3#76005)