You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@phoenix.apache.org by "Lars Hofhansl (JIRA)" <ji...@apache.org> on 2018/10/13 21:51:00 UTC

[jira] [Commented] (PHOENIX-4893) Phoenix scans SYSCAT region from RegionServerCoprocessor

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

Lars Hofhansl commented on PHOENIX-4893:
----------------------------------------

Now that SYSCAT is split, there is zero advantage in doing the lookup from the server (since more likely than not the other rows will be hosted on another server)... In fact it's a disadvantage as we'll be holding up a handler thread.

> Phoenix scans SYSCAT region from RegionServerCoprocessor
> --------------------------------------------------------
>
>                 Key: PHOENIX-4893
>                 URL: https://issues.apache.org/jira/browse/PHOENIX-4893
>             Project: Phoenix
>          Issue Type: Sub-task
>            Reporter: Lars Hofhansl
>            Priority: Major
>
> In a stack trace I see that phoenix.coprocessor.ViewFinder.findRelatedViews() scans SYSCAT. With splittable SYSCAT which now involves regions from other servers.
> We should really push this to the client now.
> Related to HBASE-21166
> [~tdsilva]



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)