[
https://issues.apache.org/jira/browse/HBASE-5560?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13227319#comment-13227319
]
stack commented on HBASE-5560:
------------------------------
Pardon me lads. Did not mean to confuse. Lars I was telling a story. It used
to be a queue of 100 times the number of handlers. After we figured that, it
was changed to be configurable and ten by default. On 15 minutes, that seems
way too long. I'm good w/ 5 minutes but would prefer 90 seconds (which is 1.5
times the rpcTimeout -- the client won't be there after 60 seconds pass...
should we hold on for some factor times rpcTimeout?).
> 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
