phoenix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (PHOENIX-4225) Using Google cache may lead to lock up on RS side.
Date Wed, 27 Sep 2017 20:43:00 GMT

    [ https://issues.apache.org/jira/browse/PHOENIX-4225?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16183231#comment-16183231
] 

Hudson commented on PHOENIX-4225:
---------------------------------

FAILURE: Integrated in Jenkins build Phoenix-master #1815 (See [https://builds.apache.org/job/Phoenix-master/1815/])
PHOENIX-4225 Using Google cache may lead to lock up on RS side. (ssa: rev 764eb8f13237a89961e259aca366e45b38b76ef1)
* (edit) phoenix-core/src/test/java/org/apache/phoenix/cache/TenantCacheTest.java
* (edit) phoenix-core/src/main/java/org/apache/phoenix/cache/TenantCacheImpl.java


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

Mime
View raw message