Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id E4AAB200D1A for ; Mon, 9 Oct 2017 12:54:03 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id E358C1609E0; Mon, 9 Oct 2017 10:54:03 +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 353C81609BB for ; Mon, 9 Oct 2017 12:54:03 +0200 (CEST) Received: (qmail 31356 invoked by uid 500); 9 Oct 2017 10:54:02 -0000 Mailing-List: contact dev-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 dev@ignite.apache.org Received: (qmail 31345 invoked by uid 99); 9 Oct 2017 10:54:02 -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; Mon, 09 Oct 2017 10:54:02 +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 9A0E8D58EC for ; Mon, 9 Oct 2017 10:54:01 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd1-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -100.002 X-Spam-Level: X-Spam-Status: No, score=-100.002 tagged_above=-999 required=6.31 tests=[RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, 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 FfQLurWKbZ4p for ; Mon, 9 Oct 2017 10:54: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 BDE495FBE6 for ; Mon, 9 Oct 2017 10:54: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 4DD56E0059 for ; Mon, 9 Oct 2017 10: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 0F50F2435A for ; Mon, 9 Oct 2017 10:54:00 +0000 (UTC) Date: Mon, 9 Oct 2017 10:54:00 +0000 (UTC) From: "Vladislav Pyatkov (JIRA)" To: dev@ignite.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Created] (IGNITE-6579) WAL history does not used when node returns to cluster again MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Mon, 09 Oct 2017 10:54:04 -0000 Vladislav Pyatkov created IGNITE-6579: ----------------------------------------- Summary: WAL history does not used when node returns to cluster again Key: IGNITE-6579 URL: https://issues.apache.org/jira/browse/IGNITE-6579 Project: Ignite Issue Type: Bug Components: persistence Reporter: Vladislav Pyatkov When I have set big enough value to "WAL history size" and stop node on 20 minutes, I got the message from coordinator (order=1): {noformat} 2017-10-06 15:46:33.429 [WARN ][sys-#10740%DPL_GRID%DplGridNodeName%][o.a.i.i.p.c.d.d.GridDhtPartitionTopologyImpl] Partition has been scheduled for rebalancing due to outdated update counter [nodeId=e51a1db2-f49b-44a9-b122-adde4016d9e7, cacheOrGroupName=CACHEGROUP_PARTICLE_DServiceZone, partId=2424, haveHistory=false] 2017-10-06 15:46:33.429 [WARN ][sys-#10740%DPL_GRID%DplGridNodeName%][o.a.i.i.p.c.d.d.GridDhtPartitionTopologyImpl] Partition has been scheduled for rebalancing due to outdated update counter [nodeId=e51a1db2-f49b-44a9-b122-adde4016d9e7, cacheOrGroupName=CACHEGROUP_PARTICLE_DServiceZone, partId=2427, haveHistory=false] 2017-10-06 15:46:33.429 [WARN ][sys-#10740%DPL_GRID%DplGridNodeName%][o.a.i.i.p.c.d.d.GridDhtPartitionTopologyImpl] Partition has been scheduled for rebalancing due to outdated update counter [nodeId=e51a1db2-f49b-44a9-b122-adde4016d9e7, cacheOrGroupName=CACHEGROUP_PARTICLE_DServiceZone, partId=2426, haveHistory=false] {noformat} after start node again. I think, history size should be enough, but I see it is not by logs (haveHistory=false). -- This message was sent by Atlassian JIRA (v6.4.14#64029)