[
https://issues.apache.org/jira/browse/HBASE-13090?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
stack updated HBASE-13090:
--------------------------
Resolution: Fixed
Fix Version/s: (was: 1.2.0)
1.1.0
Hadoop Flags: Reviewed
Status: Resolved (was: Patch Available)
Pushed to branch-1, branch-1.1, and master. [~ndimiduk] I pushed it since you
seem to want it. Patch looks good to me and we'll be running tests over next
week or so so if issue it'll turn up... Thanks.
Thanks for the patch [~jonathan.lawlor]
> 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
> Assignee: Jonathan Lawlor
> Fix For: 2.0.0, 1.1.0
>
> Attachments: HBASE-13090-v1.patch, HBASE-13090-v2.patch,
> HBASE-13090-v3.patch, HBASE-13090-v3.patch, HBASE-13090-v4.patch,
> HBASE-13090-v6.patch, HBASE-13090-v7.patch
>
>
> 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)
