[jira] [Comment Edited] (PHOENIX-1457) Use high priority queue for metadata endpoint calls

["James Taylor (JIRA)" <ji...@apache.org>]

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

James Taylor edited comment on PHOENIX-1457 at 4/28/15 4:27 AM:
----------------------------------------------------------------

Yes, the Setup section of the secondary_indexing.md needs to be updated to indicate the new config: http://phoenix.apache.org/secondary_indexing.html#Setup

[~tdsilva]


was (Author: jamestaylor):
Yes, we need to update the Setup section of the secondary_indexing.md needs to be updated to indicate the new config: http://phoenix.apache.org/secondary_indexing.html#Setup

[~tdsilva]

> Use high priority queue for metadata endpoint calls
> ---------------------------------------------------
>
>                 Key: PHOENIX-1457
>                 URL: https://issues.apache.org/jira/browse/PHOENIX-1457
>             Project: Phoenix
>          Issue Type: Bug
>            Reporter: James Taylor
>            Assignee: Thomas D'Silva
>              Labels: 4.3.1
>
> If the RS hosting the system table gets swamped, then we'd be bottlenecked waiting for the response back before running a query when we check if the metadata is in sync. We should run endpoint coprocessor calls for MetaDataService at a high priority to avoid that.



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