From issues-return-85119-archive-asf-public=cust-asf.ponee.io@ignite.apache.org Mon Dec 10 17:56: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 C4AAE180627 for ; Mon, 10 Dec 2018 17:56:04 +0100 (CET) Received: (qmail 4318 invoked by uid 500); 10 Dec 2018 16:56: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 4309 invoked by uid 99); 10 Dec 2018 16:56: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; Mon, 10 Dec 2018 16:56: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 9380ACF52B for ; Mon, 10 Dec 2018 16:56:03 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd1-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -110.301 X-Spam-Level: X-Spam-Status: No, score=-110.301 tagged_above=-999 required=6.31 tests=[ENV_AND_HDR_SPF_MATCH=-0.5, 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 (spamd1-us-west.apache.org [10.40.0.7]) (amavisd-new, port 10024) with ESMTP id A0rr7LVVVHOf for ; Mon, 10 Dec 2018 16:56: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 7A3F35F65D for ; Mon, 10 Dec 2018 16:56: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 91ABBE0E87 for ; Mon, 10 Dec 2018 16:56: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 1F7E8252EA for ; Mon, 10 Dec 2018 16:56:00 +0000 (UTC) Date: Mon, 10 Dec 2018 16:56:00 +0000 (UTC) From: "Pavel Kovalenko (JIRA)" To: issues@ignite.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Created] (IGNITE-10624) Cache deployment id may be different that cluster-wide after recovery MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 Pavel Kovalenko created IGNITE-10624: ---------------------------------------- Summary: Cache deployment id may be different that cluster-wide after recovery Key: IGNITE-10624 URL: https://issues.apache.org/jira/browse/IGNITE-10624 Project: Ignite Issue Type: Bug Components: cache, sql Affects Versions: 2.8 Reporter: Pavel Kovalenko Assignee: Pavel Kovalenko Fix For: 2.8 When schema for a cache is changing (GridQueryProcessor#processSchemaOperationLocal), it may produce false-negative "CACHE_NOT_FOUND" message if a cache was started during recovery while cluster-wide descriptor was changed. {noformat} if (cacheInfo == null || !F.eq(depId, cacheInfo.dynamicDeploymentId())) throw new SchemaOperationException(SchemaOperationException.CODE_CACHE_NOT_FOUND, cacheName); {noformat} -- This message was sent by Atlassian JIRA (v7.6.3#76005)