From issues-return-61096-archive-asf-public=cust-asf.ponee.io@ignite.apache.org Fri Apr 6 18:17: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 30BA3180649 for ; Fri, 6 Apr 2018 18:17:04 +0200 (CEST) Received: (qmail 55501 invoked by uid 500); 6 Apr 2018 16:17: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 55492 invoked by uid 99); 6 Apr 2018 16:17: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; Fri, 06 Apr 2018 16:17: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 C3835180737 for ; Fri, 6 Apr 2018 16:17: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-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 SN0G7LSsWRQv for ; Fri, 6 Apr 2018 16:17: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 4B49C5F19B for ; Fri, 6 Apr 2018 16:17: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 8A6D1E00C8 for ; Fri, 6 Apr 2018 16:17: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 48DBF25615 for ; Fri, 6 Apr 2018 16:17:00 +0000 (UTC) Date: Fri, 6 Apr 2018 16:17:00 +0000 (UTC) From: "Stanislav Lukyanov (JIRA)" To: issues@ignite.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (IGNITE-8133) Baseline topology documentation improvement 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-8133?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16428520#comment-16428520 ] Stanislav Lukyanov commented on IGNITE-8133: -------------------------------------------- Ignite now stores the baseline topology history. If a node attempts to join the cluster, and that node's baseline history is different than the history of the cluster, the node will be rejected to protect the cluster from adding a node that has data modified when the cluster was segmented. Currently this behavior described only in the Javadoc of an internal class org.apache.ignite.internal.processors.cluster.BaselineTopology, so there seem to be no documentation a user (not a developer) can read to find out about it. > Baseline topology documentation improvement > ------------------------------------------- > > Key: IGNITE-8133 > URL: https://issues.apache.org/jira/browse/IGNITE-8133 > Project: Ignite > Issue Type: Improvement > Components: documentation > Affects Versions: 2.4 > Reporter: Stanislav Lukyanov > Assignee: Stanislav Lukyanov > Priority: Critical > Fix For: 2.5 > > > Baseline topology concept was added to Ignite in 2.4 by IEP-4. This changed Ignite cluster behavior when persistence is enabled (first of all, activation and rebalancing timings). > It seems that the current documentation may be confusing. > For example, the sentence > {quote}Note that the baseline topology is not set when the cluster is started for the first time; that's the only time when a manual intervention is needed.{quote} > may lead one to think that baseline topology is not used by default and needs to be enabled only if one wants to use it. > Also, the documentation describes the tools and commands that are used to manage the baseline topology and activation, but doesn't give guidelines on which nodes should be in the topology, when should it be changed, etc. > The documentation should be enhanced to > - give clear understanding that baseline topology always needs to be considered as a part of the cluster architecture when persistence is enabled; > - provide overview of the behavioral changes compared to AI 2.3 (use a note/warning block for that to separate it from the main text?); > - provide basic guidelines and suggestions of how one can start a new cluster and manage it (when to activate/deactivate, when to change baseline topology, what happens and what needs to be done when a node fails or joins, how to use consistentId) -- This message was sent by Atlassian JIRA (v7.6.3#76005)