[
https://issues.apache.org/jira/browse/PHOENIX-1457?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14383097#comment-14383097
]
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_r27269819
--- Diff:
phoenix-core/src/main/java/org/apache/phoenix/query/ConnectionQueryServicesImpl.java
---
@@ -290,7 +290,7 @@ private void openConnection() throws SQLException {
@Override
public HTableInterface getTable(byte[] tableName) throws SQLException {
try {
- return
HBaseFactoryProvider.getHTableFactory().getTable(tableName, connection, null);
+ return
HBaseFactoryProvider.getHTableFactory().getTable(tableName, connection,
getExecutor());
--- End diff --
Revert this change please - it was part of our experiment to get the
RpcScheduler set on the client-side.
> 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)
