hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andrew Purtell (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HBASE-13090) Progress heartbeats for long running scanners
Date Tue, 24 Feb 2015 17:44:04 GMT

     [ https://issues.apache.org/jira/browse/HBASE-13090?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Andrew Purtell updated HBASE-13090:
-----------------------------------
    Description: 
It can be necessary to set very long timeouts for clients that issue scans over large regions
when all data in the region might be filtered out depending on scan criteria. This is a usability
concern because it can be hard to identify what worst case timeout to use until scans are
occasionally/intermittently failing in production, depending on variable scan criteria. It
would be better if the client-server scan protocol can send back periodic progress heartbeats
to clients as long as server scanners are alive and making progress.

This is related but orthogonal to streaming scan (HBASE-13071). 

  was:
It can be necessary to set very long timeouts for clients that issue scans over large regions
when all data in the region is filtered out. This is a usability concern because it can be
hard to identify what worst case timeout to use until scans are occasionally/intermittently
failing in production, depending on variable scan criteria. It would be better if the client-server
scan protocol can send back periodic progress heartbeats to clients as long as server scanners
are alive and making progress.

This is related but orthogonal to streaming scan (HBASE-13071). 


> Progress heartbeats for long running scanners
> ---------------------------------------------
>
>                 Key: HBASE-13090
>                 URL: https://issues.apache.org/jira/browse/HBASE-13090
>             Project: HBase
>          Issue Type: New Feature
>            Reporter: Andrew Purtell
>
> It can be necessary to set very long timeouts for clients that issue scans over large
regions when all data in the region might be filtered out depending on scan criteria. This
is a usability concern because it can be hard to identify what worst case timeout to use until
scans are occasionally/intermittently failing in production, depending on variable scan criteria.
It would be better if the client-server scan protocol can send back periodic progress heartbeats
to clients as long as server scanners are alive and making progress.
> This is related but orthogonal to streaming scan (HBASE-13071). 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message