[jira] [Updated] (HBASE-10605) Manage the call timeout in the server
[ https://issues.apache.org/jira/browse/HBASE-10605?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nicolas Liochon updated HBASE-10605: Assignee: (was: Nicolas Liochon) > Manage the call timeout in the server > - > > Key: HBASE-10605 > URL: https://issues.apache.org/jira/browse/HBASE-10605 > Project: HBase > Issue Type: Improvement > Components: IPC/RPC, regionserver >Affects Versions: 0.99.0 >Reporter: Nicolas Liochon > > Since HBASE-10566, we have an explicit call timeout available in the client. > We could forward it to the server, and use this information for: > - if the call is still in the queue, just cancel it > - if the call is under execution, makes this information available in > RpcCallContext (actually change the RpcCallContext#disconnectSince to > something more generic), so it can be used by the query under execution to > stop its execution > - in the future, interrupt it to manage the case 'stuck on a dead datanode' > or something similar > - if the operation has finished, don't send the reply to the client, as by > definition the client is not interested anymore. > From this, it will be easy to manage the cancellation: > disconnect/timeout/cancellation are similar from a service execution PoV -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-10605) Manage the call timeout in the server
[ https://issues.apache.org/jira/browse/HBASE-10605?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Dimiduk updated HBASE-10605: - Fix Version/s: (was: 1.1.0) Manage the call timeout in the server - Key: HBASE-10605 URL: https://issues.apache.org/jira/browse/HBASE-10605 Project: HBase Issue Type: Improvement Components: regionserver, rpc Affects Versions: 0.99.0 Reporter: Nicolas Liochon Assignee: Nicolas Liochon Since HBASE-10566, we have an explicit call timeout available in the client. We could forward it to the server, and use this information for: - if the call is still in the queue, just cancel it - if the call is under execution, makes this information available in RpcCallContext (actually change the RpcCallContext#disconnectSince to something more generic), so it can be used by the query under execution to stop its execution - in the future, interrupt it to manage the case 'stuck on a dead datanode' or something similar - if the operation has finished, don't send the reply to the client, as by definition the client is not interested anymore. From this, it will be easy to manage the cancellation: disconnect/timeout/cancellation are similar from a service execution PoV -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-10605) Manage the call timeout in the server
[ https://issues.apache.org/jira/browse/HBASE-10605?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Enis Soztutar updated HBASE-10605: -- Fix Version/s: (was: 1.0.0) 1.1.0 Manage the call timeout in the server - Key: HBASE-10605 URL: https://issues.apache.org/jira/browse/HBASE-10605 Project: HBase Issue Type: Improvement Components: regionserver, rpc Affects Versions: 0.99.0 Reporter: Nicolas Liochon Assignee: Nicolas Liochon Fix For: 1.1.0 Since HBASE-10566, we have an explicit call timeout available in the client. We could forward it to the server, and use this information for: - if the call is still in the queue, just cancel it - if the call is under execution, makes this information available in RpcCallContext (actually change the RpcCallContext#disconnectSince to something more generic), so it can be used by the query under execution to stop its execution - in the future, interrupt it to manage the case 'stuck on a dead datanode' or something similar - if the operation has finished, don't send the reply to the client, as by definition the client is not interested anymore. From this, it will be easy to manage the cancellation: disconnect/timeout/cancellation are similar from a service execution PoV -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-10605) Manage the call timeout in the server
[ https://issues.apache.org/jira/browse/HBASE-10605?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stack updated HBASE-10605: -- Component/s: rpc Manage the call timeout in the server - Key: HBASE-10605 URL: https://issues.apache.org/jira/browse/HBASE-10605 Project: HBase Issue Type: Improvement Components: regionserver, rpc Affects Versions: 0.99.0 Reporter: Nicolas Liochon Assignee: Nicolas Liochon Fix For: 1.0.0 Since HBASE-10566, we have an explicit call timeout available in the client. We could forward it to the server, and use this information for: - if the call is still in the queue, just cancel it - if the call is under execution, makes this information available in RpcCallContext (actually change the RpcCallContext#disconnectSince to something more generic), so it can be used by the query under execution to stop its execution - in the future, interrupt it to manage the case 'stuck on a dead datanode' or something similar - if the operation has finished, don't send the reply to the client, as by definition the client is not interested anymore. From this, it will be easy to manage the cancellation: disconnect/timeout/cancellation are similar from a service execution PoV -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-10605) Manage the call timeout in the server
[ https://issues.apache.org/jira/browse/HBASE-10605?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Enis Soztutar updated HBASE-10605: -- Fix Version/s: (was: 0.99.2) 1.0.0 Manage the call timeout in the server - Key: HBASE-10605 URL: https://issues.apache.org/jira/browse/HBASE-10605 Project: HBase Issue Type: Improvement Components: regionserver Affects Versions: 0.99.0 Reporter: Nicolas Liochon Assignee: Nicolas Liochon Fix For: 1.0.0 Since HBASE-10566, we have an explicit call timeout available in the client. We could forward it to the server, and use this information for: - if the call is still in the queue, just cancel it - if the call is under execution, makes this information available in RpcCallContext (actually change the RpcCallContext#disconnectSince to something more generic), so it can be used by the query under execution to stop its execution - in the future, interrupt it to manage the case 'stuck on a dead datanode' or something similar - if the operation has finished, don't send the reply to the client, as by definition the client is not interested anymore. From this, it will be easy to manage the cancellation: disconnect/timeout/cancellation are similar from a service execution PoV -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-10605) Manage the call timeout in the server
[ https://issues.apache.org/jira/browse/HBASE-10605?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Enis Soztutar updated HBASE-10605: -- Fix Version/s: (was: 0.99.1) 0.99.2 Manage the call timeout in the server - Key: HBASE-10605 URL: https://issues.apache.org/jira/browse/HBASE-10605 Project: HBase Issue Type: Improvement Components: regionserver Affects Versions: 0.99.0 Reporter: Nicolas Liochon Assignee: Nicolas Liochon Fix For: 0.99.2 Since HBASE-10566, we have an explicit call timeout available in the client. We could forward it to the server, and use this information for: - if the call is still in the queue, just cancel it - if the call is under execution, makes this information available in RpcCallContext (actually change the RpcCallContext#disconnectSince to something more generic), so it can be used by the query under execution to stop its execution - in the future, interrupt it to manage the case 'stuck on a dead datanode' or something similar - if the operation has finished, don't send the reply to the client, as by definition the client is not interested anymore. From this, it will be easy to manage the cancellation: disconnect/timeout/cancellation are similar from a service execution PoV -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-10605) Manage the call timeout in the server
[ https://issues.apache.org/jira/browse/HBASE-10605?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Enis Soztutar updated HBASE-10605: -- Fix Version/s: (was: 0.99.0) 0.99.1 Manage the call timeout in the server - Key: HBASE-10605 URL: https://issues.apache.org/jira/browse/HBASE-10605 Project: HBase Issue Type: Improvement Components: regionserver Affects Versions: 0.99.0 Reporter: Nicolas Liochon Assignee: Nicolas Liochon Fix For: 0.99.1 Since HBASE-10566, we have an explicit call timeout available in the client. We could forward it to the server, and use this information for: - if the call is still in the queue, just cancel it - if the call is under execution, makes this information available in RpcCallContext (actually change the RpcCallContext#disconnectSince to something more generic), so it can be used by the query under execution to stop its execution - in the future, interrupt it to manage the case 'stuck on a dead datanode' or something similar - if the operation has finished, don't send the reply to the client, as by definition the client is not interested anymore. From this, it will be easy to manage the cancellation: disconnect/timeout/cancellation are similar from a service execution PoV -- This message was sent by Atlassian JIRA (v6.3.4#6332)
