You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@phoenix.apache.org by "Jeongdae Kim (JIRA)" <ji...@apache.org> on 2017/02/14 02:23:41 UTC

[jira] [Commented] (PHOENIX-3486) RoundRobinResultIterator doesn't work correctly because of setting Scan's cache size inappropriately in PhoenixInputForamt

    [ https://issues.apache.org/jira/browse/PHOENIX-3486?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15864897#comment-15864897 ] 

Jeongdae Kim commented on PHOENIX-3486:
---------------------------------------

failed tests are not related to this patch. could anyone give me reviews for this patch?

> RoundRobinResultIterator doesn't work correctly because of setting Scan's cache size inappropriately in PhoenixInputForamt
> --------------------------------------------------------------------------------------------------------------------------
>
>                 Key: PHOENIX-3486
>                 URL: https://issues.apache.org/jira/browse/PHOENIX-3486
>             Project: Phoenix
>          Issue Type: Bug
>            Reporter: Jeongdae Kim
>            Assignee: Jeongdae Kim
>              Labels: HivePhoenix
>         Attachments: PHOENIX-3486.patch
>
>
> RoundRobinResultIterator uses "hbase.client.scanner.caching" to fill caches  in parallel for all scans, but by setting Scan.setCaching() in PhoenixInputForrmat(phoenix-hive), RoundRobinResultIterator doesn't work correctly, because if Scan have cache size by setCaching(), HBase uses cache size from Scan.getCaching() to fill cache, not "hbase.client.scanner.caching", and RoundRobinResultIterator scans the table in parallel to fill caches every "hbase.client.scanner.caching", resulting in unintended parallel scan operation,  this causes scan performance degradation.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)