From issues-return-82753-archive-asf-public=cust-asf.ponee.io@ignite.apache.org Wed Nov 21 09:37:05 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 7F4E6180668 for ; Wed, 21 Nov 2018 09:37:04 +0100 (CET) Received: (qmail 93217 invoked by uid 500); 21 Nov 2018 08:37: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 93207 invoked by uid 99); 21 Nov 2018 08:37:03 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd1-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 21 Nov 2018 08:37:03 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd1-us-west.apache.org (ASF Mail Server at spamd1-us-west.apache.org) with ESMTP id 11695D1F9C for ; Wed, 21 Nov 2018 08:37:03 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd1-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-us.apache.org ([10.40.0.8]) by localhost (spamd1-us-west.apache.org [10.40.0.7]) (amavisd-new, port 10024) with ESMTP id XZ8puWf1IfB5 for ; Wed, 21 Nov 2018 08:37: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 A7DBB5F60D for ; Wed, 21 Nov 2018 08:37: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 EDAC6E2632 for ; Wed, 21 Nov 2018 08:37: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 4A72421EE6 for ; Wed, 21 Nov 2018 08:37:00 +0000 (UTC) Date: Wed, 21 Nov 2018 08:37:00 +0000 (UTC) From: "Pavel Pereslegin (JIRA)" To: issues@ignite.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Comment Edited] (IGNITE-10058) resetLostPartitions() leaves an additional copy of a partition in the cluster 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-10058?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16694381#comment-16694381 ] Pavel Pereslegin edited comment on IGNITE-10058 at 11/21/18 8:36 AM: --------------------------------------------------------------------- This small patch evicts duplicate {{LOST}} partitions on non-affinity nodes after node re-joins the cluster (after step 4). Affinity is changed in {{CacheAffinitySharedManager#checkRebalanceState}} if it notices that there is a new affinity-node for {{LOST}} partition. was (Author: xtern): This small patch evicts duplicate LOST partitions on non-affinity nodes after node re-joins the cluster (after step 4). Affinity is changed in CacheAffinitySharedManager#checkRebalanceState if it notices that there is a new owner for LOST partition. > resetLostPartitions() leaves an additional copy of a partition in the cluster > ----------------------------------------------------------------------------- > > Key: IGNITE-10058 > URL: https://issues.apache.org/jira/browse/IGNITE-10058 > Project: Ignite > Issue Type: Bug > Reporter: Stanislav Lukyanov > Assignee: Pavel Pereslegin > Priority: Major > > If there are several copies of a LOST partition, resetLostPartitions() will leave all of them in the cluster as OWNING. > Scenario: > 1) Start 4 nodes, a cache with backups=0 and READ_WRITE_SAFE, fill the cache > 2) Stop one node - some partitions are recreated on the remaining nodes as LOST > 3) Start one node - the LOST partitions are being rebalanced to the new node from the existing ones > 4) Wait for rebalance to complete > 5) Call resetLostPartitions() > After that the partitions that were LOST become OWNING on all nodes that had them. Eviction of these partitions doesn't start. > Need to correctly evict additional copies of LOST partitions either after rebalance on step 4 or after resetLostPartitions() call on step 5. > Current resetLostPartitions() implementation does call checkEvictions(), but the ready affinity assignment contains several nodes per partition for some reason. -- This message was sent by Atlassian JIRA (v7.6.3#76005)