[jira] [Commented] (PHOENIX-4225) Using Google cache may lead to lock up on RS side.

["Hadoop QA (JIRA)" <ji...@apache.org>]

    [ 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)