hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "stack (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-13090) Progress heartbeats for long running scanners
Date Fri, 06 Mar 2015 19:27:41 GMT

    [ https://issues.apache.org/jira/browse/HBASE-13090?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14350766#comment-14350766

stack commented on HBASE-13090:

Thanks [~jonathan.lawlor]

Why does RsRpcServices have to be involved? Could remaining scan time not be up in RegionScanner?

bq. This means that it would still be possible to timeout due to a single long running StoreScanner#next()
call in the event that partial Results are not supported.

Dang. Can we flag these timeouts as "Its your own fault" or, "don't use filter" or "don't
short scan" ?

If you can do the heartbeat usiing ScanResponse rather than pollute Result, that'd be better.

Looks good to me [~jonathan.lawlor]

[~lhofhansl] Any input here honey?

> 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

View raw message