[
https://issues.apache.org/jira/browse/PHOENIX-4903?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16621353#comment-16621353
]
Hudson commented on PHOENIX-4903:
---------------------------------
FAILURE: Integrated in Jenkins build PreCommit-PHOENIX-Build #2043 (See
[https://builds.apache.org/job/PreCommit-PHOENIX-Build/2043/])
PHOENIX-4903 Use same hash cache RPC message across all calls (elserj: rev
2084a6ccefe27e4a5c0e8073fc0302d94ca8548c)
* (edit)
phoenix-core/src/main/java/org/apache/phoenix/cache/ServerCacheClient.java
> HashCache recreated on client for every RegionServer it is sent to
> ------------------------------------------------------------------
>
> Key: PHOENIX-4903
> URL: https://issues.apache.org/jira/browse/PHOENIX-4903
> Project: Phoenix
> Issue Type: Improvement
> Reporter: Marcell Ortutay
> Assignee: Marcell Ortutay
> Priority: Major
> Fix For: 4.15.0, 5.1.0
>
>
> To distribute the hash cache to region servers, the master node makes an
> `AddServerCacheRequest` RPC to each region servers. If there are N region
> servers, it makes N of these RPC's. For each of the region servers, it
> generates a serialized RPC message and sends it out. This happens
> concurrently, and the result is that it uses O(N) memory on the master.
> As an example, if the `AddServerCacheRequest` RPC message is 100MB, and you
> have a cluster of 100 nodes, it would use 10GB memory on the master,
> potentially resulting in an "OutOfMemory" exception.
> It would be better if the master could use O(1) memory for the RPC.
> I observed this behavior in Phoenix 4.14.1
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
