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

Phabricator commented on HBASE-5560:
------------------------------------

stack has commented on the revision "[jira][HBASE-5560] Avoid RegionServer GC 
caused by timed-out calls".

  Excellent lads.  Good one.  +1 . And +1 on 90seconds rather than 15 minutes 
(though this patch seems to have 15minutes still in spite of your comment 
Dhruba).

  Reminds me of another ugly one; the queue of incoming rpc requests which was 
hard-coded at 100 outstanding requests * the number of handlers (So, if batch 
puts, could be 2MB*100*100 of unaccounted for memory when server was working 
hard).

REVISION DETAIL
  https://reviews.facebook.net/D2241

                
> Avoid RegionServer GC caused by timed-out calls
> -----------------------------------------------
>
>                 Key: HBASE-5560
>                 URL: https://issues.apache.org/jira/browse/HBASE-5560
>             Project: HBase
>          Issue Type: Improvement
>            Reporter: dhruba borthakur
>            Assignee: dhruba borthakur
>             Fix For: 0.94.0, 0.96.0
>
>         Attachments: D2241.1.patch, D2241.2.patch
>
>
> The HBaseRpcServer queues up rpc responses if the socket connection to the 
> client is not yet ready to receive data. Calls are queued here until a 15 
> minute timeout occurs. I am able to generate a full GC when I artificially 
> make a client read rpc-responses very slowly. This jira is to make this 15 
> minute time configurable.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to