You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Enis Soztutar (JIRA)" <ji...@apache.org> on 2016/03/23 00:13:25 UTC

[jira] [Updated] (HBASE-15212) RRCServer should enforce max request size

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

Enis Soztutar updated HBASE-15212:
----------------------------------
    Fix Version/s: 1.4.0
     Release Note: Adds a configuration parameter "hbase.ipc.max.request.size" which defaults to 256MB to protect the server against very large incoming RPC requests. All requests larger than this size will be immediately rejected before allocating any resources (memory allocation, etc).  

> RRCServer should enforce max request size 
> ------------------------------------------
>
>                 Key: HBASE-15212
>                 URL: https://issues.apache.org/jira/browse/HBASE-15212
>             Project: HBase
>          Issue Type: Improvement
>            Reporter: Enis Soztutar
>            Assignee: Enis Soztutar
>             Fix For: 2.0.0, 1.3.0, 1.4.0
>
>         Attachments: hbase-15212_v1.patch, hbase-15212_v1.patch, hbase-15212_v2.patch
>
>
> A TODO from HBASE-15177 was that we are not protecting the RPCServer in case an RPC request with a very large size is received. This might cause the server to go OOM because we are allocating the RPC serialization into a BB. Instead we should reject the RPC and close the connection.  



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)