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 B1FE2200D16 for ; Tue, 26 Sep 2017 00:40:07 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id B091B1609E9; Mon, 25 Sep 2017 22:40:07 +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 0383C1609BB for ; Tue, 26 Sep 2017 00:40:06 +0200 (CEST) Received: (qmail 85385 invoked by uid 500); 25 Sep 2017 22:40:06 -0000 Mailing-List: contact dev-help@phoenix.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@phoenix.apache.org Delivered-To: mailing list dev@phoenix.apache.org Received: (qmail 85374 invoked by uid 99); 25 Sep 2017 22:40:06 -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, 25 Sep 2017 22:40:06 +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 A800DDCF5E for ; Mon, 25 Sep 2017 22:40:05 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd1-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -99.202 X-Spam-Level: X-Spam-Status: No, score=-99.202 tagged_above=-999 required=6.31 tests=[KAM_ASCII_DIVIDERS=0.8, 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 MfGyvkfPYY0N for ; Mon, 25 Sep 2017 22:40:04 +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 022E260D9C for ; Mon, 25 Sep 2017 22:40:04 +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 AE575E06C4 for ; Mon, 25 Sep 2017 22:40:03 +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 138E024282 for ; Mon, 25 Sep 2017 22:40:02 +0000 (UTC) Date: Mon, 25 Sep 2017 22:40:02 +0000 (UTC) From: "James Taylor (JIRA)" To: dev@phoenix.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (PHOENIX-4224) Automatic resending cache for HashJoin doesn't work when cache has expired on server side MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Mon, 25 Sep 2017 22:40:07 -0000 [ https://issues.apache.org/jira/browse/PHOENIX-4224?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Taylor updated PHOENIX-4224: ---------------------------------- Priority: Blocker (was: Major) > Automatic resending cache for HashJoin doesn't work when cache has expired on server side > ------------------------------------------------------------------------------------------ > > Key: PHOENIX-4224 > URL: https://issues.apache.org/jira/browse/PHOENIX-4224 > Project: Phoenix > Issue Type: Bug > Affects Versions: 4.12.0 > Reporter: Sergey Soldatov > Assignee: Sergey Soldatov > Priority: Blocker > Fix For: 4.12.0 > > > The problem occurs when the cache has expired on server side and client want to resend it. This problem has been introduced in PHOENIX-4010. Actual result in this case is that client doesn't send the cache because of the following check: > {noformat} > if (cache.addServer(tableRegionLocation) ... )) { > success = addServerCache(table, startkeyOfRegion, pTable, cacheId, cache.getCachePtr(), cacheFactory, txState); > } > {noformat} > Since the region location hasn't been changed, we actually don't send cache again, but produce new scanner which will fail with the same error and client will fall to recursion. -- This message was sent by Atlassian JIRA (v6.4.14#64029)