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/04/01 23:26:25 UTC

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

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

Enis Soztutar commented on HBASE-15212:
---------------------------------------

bq. Seems this cause TestAsyncIPC.testRpcMaxRequestSize fail?
I've ran that test locally before commit (see https://issues.apache.org/jira/browse/HBASE-15212?focusedCommentId=15207492&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-15207492). It seemed like a flaky test (because I've seen the failure before this if I remember right). But maybe there is an issue. 

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