[jira] [Closed] (PHOENIX-4903) HashCache recreated on client for every RegionServer it is sent to

["Chinmay Kulkarni (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/PHOENIX-4903?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Chinmay Kulkarni closed PHOENIX-4903.
-------------------------------------

Bulk closing Jiras for the 4.15.0 release.

> 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
(v8.3.4#803005)