phoenix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "James Taylor (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (PHOENIX-1670) Investigate lease timeout on aggregate queries
Date Sun, 24 Jan 2016 02:59:39 GMT

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

James Taylor resolved PHOENIX-1670.
-----------------------------------
    Resolution: Duplicate

Duplicate of PHOENIX-1428.

> Investigate lease timeout on aggregate queries
> ----------------------------------------------
>
>                 Key: PHOENIX-1670
>                 URL: https://issues.apache.org/jira/browse/PHOENIX-1670
>             Project: Phoenix
>          Issue Type: Bug
>            Reporter: James Taylor
>
> In theory, we shouldn't hit a lease timeout for aggregate queries, because we chunk up
the scan on the client side to manageable chunks. However, I believe [~mujtabachohan] has
seen this occurring. Another curious issue is that unless we open the scanner when the iterator
is created, aggregate scans take a perf hit which I don't completely understand. Another thing
that [~lhofhansl] noticed was that running the scan on the region server during the post scanner
open hook could be problematic. We might need to run the scan instead on the first next()
call we get from the client instead.



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

Mime
View raw message