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 88BAE200D29 for ; Thu, 26 Oct 2017 18:42:04 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 875D1160BF3; Thu, 26 Oct 2017 16:42:04 +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 CCAB21609E5 for ; Thu, 26 Oct 2017 18:42:03 +0200 (CEST) Received: (qmail 11250 invoked by uid 500); 26 Oct 2017 16:42: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 11241 invoked by uid 99); 26 Oct 2017 16:42: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; Thu, 26 Oct 2017 16:42: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 4DDB8C0653 for ; Thu, 26 Oct 2017 16:42:02 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd1-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -100.001 X-Spam-Level: X-Spam-Status: No, score=-100.001 tagged_above=-999 required=6.31 tests=[RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd1-us-west.apache.org [10.40.0.7]) (amavisd-new, port 10024) with ESMTP id dTPUEpBr_QlP for ; Thu, 26 Oct 2017 16:42: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 145EB5F5B8 for ; Thu, 26 Oct 2017 16:42: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 5AC9EE00B3 for ; Thu, 26 Oct 2017 16:42: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 1F8C0212F9 for ; Thu, 26 Oct 2017 16:42:00 +0000 (UTC) Date: Thu, 26 Oct 2017 16:42:00 +0000 (UTC) From: "Vyacheslav Koptilin (JIRA)" To: issues@ignite.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Created] (IGNITE-6767) NearCache#localPeek(key, NEAR) always returns 'null' if the node, which owns the primary partition for the given key, left the cluster. MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Thu, 26 Oct 2017 16:42:04 -0000 Vyacheslav Koptilin created IGNITE-6767: ------------------------------------------- Summary: NearCache#localPeek(key, NEAR) always returns 'null' if the node, which owns the primary partition for the given key, left the cluster. Key: IGNITE-6767 URL: https://issues.apache.org/jira/browse/IGNITE-6767 Project: Ignite Issue Type: Bug Security Level: Public (Viewable by anyone) Components: cache Affects Versions: 2.1 Reporter: Vyacheslav Koptilin {{IgniteCache.localPeek(key, PeekMode.NEAR)}} always returns 'null' if the node, which owns the primary partition for the given key, left the cluster, even if {{IgniteCache.get(key)}} was called. How to reproduce: # start two server nodes. # create partitioned or atomic cache and populate data. # start client node with near cache configured. # perform {{IgniteCache.get(key)}} and check that {{IgniteCache.localPeek(key, PeekMode.NEAR)}} returns not null value. # stop server node which owns primary partition for the given {{key}}. # perform {{IgniteCache.get(key)}}. # after that {{IgniteCache.localPeek(key, PeekMode.NEAR)}} always returns null value. This issue was reported in the user-list: http://apache-ignite-users.70518.x6.nabble.com/Near-Cache-Topoolgy-change-causes-NearCache-to-always-miss-tt17539.html -- This message was sent by Atlassian JIRA (v6.4.14#64029)