[ https://issues.apache.org/jira/browse/HBASE-16285?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Duo Zhang updated HBASE-16285: ------------------------------ Resolution: Fixed Hadoop Flags: Reviewed Status: Resolved (was: Patch Available) Pushed to branch-1.3+. Thanks all for reviewing. > Drop RPC requests if it must be considered as timeout at client > --------------------------------------------------------------- > > Key: HBASE-16285 > URL: https://issues.apache.org/jira/browse/HBASE-16285 > Project: HBase > Issue Type: Improvement > Affects Versions: 2.0.0, 1.3.0, 1.4.0 > Reporter: Phil Yang > Assignee: Phil Yang > Fix For: 2.0.0, 1.3.0, 1.4.0 > > Attachments: HBASE-16285-branch-1-v1.patch, > HBASE-16285-branch-1-v2.patch, HBASE-16285-branch-1-v3.patch, > HBASE-16285-branch-1-v4.patch, HBASE-16285-branch-1-v5.patch, > HBASE-16285-branch-1-v5.patch, HBASE-16285-branch-1-v6.patch, > HBASE-16285-v1.patch, HBASE-16285-v2.patch, HBASE-16285-v3.patch, > HBASE-16285-v4.patch, HBASE-16285-v5.patch, HBASE-16285-v6.patch, > HBASE-16285-v7.patch, HBASE-16285-v7.patch, HBASE-16285-v8.patch, > HBASE-16285-v9.patch > > > After HBASE-15593, we have a timeout param in header of RPC requests. We can > use it in more scenes. > A straightforward scene is to drop requests if it has waited so long in RPC > queue and has been dropped by client. Even if we handle this request and send > the response back, it will not be used any more. And client may have sent a > retry. In an extreme case, if the server is slow, all requests may be timeout > or queue-full-exception because we should handle previous requests which have > been dropped by client and many resources at server are wasted. -- This message was sent by Atlassian JIRA (v6.3.4#6332)