[
https://issues.apache.org/jira/browse/PHOENIX-1457?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14383105#comment-14383105
]
ASF GitHub Bot commented on PHOENIX-1457:
-----------------------------------------
Github user JamesRTaylor commented on a diff in the pull request:
https://github.com/apache/phoenix/pull/55#discussion_r27269910
--- Diff:
phoenix-core/src/main/java/org/apache/phoenix/query/QueryServices.java ---
@@ -123,9 +123,10 @@
// Index will be partially re-built from index disable time stamp -
following overlap time
public static final String
INDEX_FAILURE_HANDLING_REBUILD_OVERLAP_TIME_ATTRIB =
"phoenix.index.failure.handling.rebuild.overlap.time";
- public static final String MIN_INDEX_PRIOIRTY_ATTRIB =
"phoenix.regionserver.index.priority.min";
- public static final String MAX_INDEX_PRIOIRTY_ATTRIB =
"phoenix.regionserver.index.priority.max";
+ public static final String INDEX_PRIOIRTY_ATTRIB =
"phoenix.regionserver.index.priority";
public static final String INDEX_HANDLER_COUNT_ATTRIB =
"phoenix.regionserver.index.handler.count";
+ public static final String METADATA_PRIOIRTY_ATTRIB =
"phoenix.regionserver.metadata.priority";
--- End diff --
This is a client side and region server param, isn't it? How about
phoenix.index.rpc.priority and phoenix.metadata.rpc.priority?
> 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)
