From dev-return-45237-apmail-phoenix-dev-archive=phoenix.apache.org@phoenix.apache.org Tue Sep 26 22:00:05 2017 Return-Path: X-Original-To: apmail-phoenix-dev-archive@minotaur.apache.org Delivered-To: apmail-phoenix-dev-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 7EC1A10FE9 for ; Tue, 26 Sep 2017 22:00:05 +0000 (UTC) Received: (qmail 29528 invoked by uid 500); 26 Sep 2017 22:00:05 -0000 Delivered-To: apmail-phoenix-dev-archive@phoenix.apache.org Received: (qmail 29475 invoked by uid 500); 26 Sep 2017 22:00:05 -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 29464 invoked by uid 99); 26 Sep 2017 22:00:05 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd2-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 26 Sep 2017 22:00:05 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd2-us-west.apache.org (ASF Mail Server at spamd2-us-west.apache.org) with ESMTP id AB4EC1A291D for ; Tue, 26 Sep 2017 22:00:04 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd2-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 (spamd2-us-west.apache.org [10.40.0.9]) (amavisd-new, port 10024) with ESMTP id 2d8x6zkJwPbp for ; Tue, 26 Sep 2017 22:00:03 +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 4E0235FB0B for ; Tue, 26 Sep 2017 22:00:03 +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 CD937E0059 for ; Tue, 26 Sep 2017 22:00:02 +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 CB40E2425E for ; Tue, 26 Sep 2017 22:00:00 +0000 (UTC) Date: Tue, 26 Sep 2017 22:00:00 +0000 (UTC) From: "Hadoop QA (JIRA)" To: dev@phoenix.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (PHOENIX-4225) Using Google cache may lead to lock up on RS side. 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/PHOENIX-4225?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16181651#comment-16181651 ] Hadoop QA commented on PHOENIX-4225: ------------------------------------ {color:red}-1 overall{color}. Here are the results of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12889160/PHOENIX-4225-1.patch against master branch at commit 5d9572736a991f19121477a0822d4b8bf26b4c69. ATTACHMENT ID: 12889160 {color:green}+1 @author{color}. The patch does not contain any @author tags. {color:green}+1 tests included{color}. The patch appears to include 3 new or modified tests. {color:green}+1 javac{color}. The applied patch does not increase the total number of javac compiler warnings. {color:green}+1 release audit{color}. The applied patch does not increase the total number of release audit warnings. {color:red}-1 lineLengths{color}. The patch introduces the following lines longer than 100: + TenantCacheImpl cache = new TenantCacheImpl(memoryManager, maxServerCacheTimeToLive, ticker); + TenantCacheImpl cache = new TenantCacheImpl(memoryManager, maxServerCacheTimeToLive, ticker); {color:red}-1 core tests{color}. The patch failed these unit tests: Test results: https://builds.apache.org/job/PreCommit-PHOENIX-Build/1485//testReport/ Console output: https://builds.apache.org/job/PreCommit-PHOENIX-Build/1485//console This message is automatically generated. > Using Google cache may lead to lock up on RS side. > --------------------------------------------------- > > Key: PHOENIX-4225 > URL: https://issues.apache.org/jira/browse/PHOENIX-4225 > Project: Phoenix > Issue Type: Bug > Reporter: Sergey Soldatov > Assignee: Sergey Soldatov > Fix For: 4.12.0 > > Attachments: PHOENIX-4225-1.patch > > > On the server side we are using google cache with life time bounds. This is integrated with GlobalMemoryManager which is used for almost all tasks that requires memory allocation. The problem is that when the cache member get removed, it doesn't send remove notification until next write/get operation happen. But in some cases once the large cache was removed (but memory manager doesn't know that since it relies on the notification), we try to resend it and memory manager get stuck waiting for free space, blocking all other operations with the memory manager. -- This message was sent by Atlassian JIRA (v6.4.14#64029)