[
https://issues.apache.org/jira/browse/HBASE-16505?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15563571#comment-15563571
]
Ted Yu commented on HBASE-16505:
--------------------------------
{code}
126 } catch (TimeoutIOException e){
127 RpcServer.LOG.info("Can not complete this request in time, drop
it: " + call);
{code}
Should the log be at WARN level ?
> Pass deadline to HRegion operations
> -----------------------------------
>
> Key: HBASE-16505
> URL: https://issues.apache.org/jira/browse/HBASE-16505
> Project: HBase
> Issue Type: Sub-task
> Reporter: Phil Yang
> Assignee: Phil Yang
> Fix For: 2.0.0
>
> Attachments: HBASE-16505-branch-1-v1.patch,
> HBASE-16505-branch-1-v2.patch, HBASE-16505-v1.patch, HBASE-16505-v10.patch,
> HBASE-16505-v10.patch, HBASE-16505-v11.patch, HBASE-16505-v11.patch,
> HBASE-16505-v12.patch, HBASE-16505-v2.patch, HBASE-16505-v3.patch,
> HBASE-16505-v4.patch, HBASE-16505-v5.patch, HBASE-16505-v6.patch,
> HBASE-16505-v7.patch, HBASE-16505-v8.patch, HBASE-16505-v9.patch
>
>
> If we want to know the correct setting of timeout in read/write path, we need
> add a new parameter in operation-methods of Region.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)