[
https://issues.apache.org/jira/browse/PHOENIX-5482?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17028445#comment-17028445
]
Hadoop QA commented on PHOENIX-5482:
------------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12992439/PHOENIX-5482.patch
against master branch at commit b27168de1922d429229935b16eef49c00a88aab1.
ATTACHMENT ID: 12992439
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include
any new or modified tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 lineLengths{color}. The patch does not introduce lines
longer than 100
{color:red}-1 core tests{color}. The patch failed these unit tests:
./phoenix-core/target/failsafe-reports/TEST-org.apache.phoenix.end2end.join.HashJoinNoIndexIT
Test results:
https://builds.apache.org/job/PreCommit-PHOENIX-Build/3377//testReport/
Console output:
https://builds.apache.org/job/PreCommit-PHOENIX-Build/3377//console
This message is automatically generated.
> PhoenixRpcScheduler should use HBase priority max queue length
> --------------------------------------------------------------
>
> Key: PHOENIX-5482
> URL: https://issues.apache.org/jira/browse/PHOENIX-5482
> Project: Phoenix
> Issue Type: Improvement
> Reporter: Geoffrey Jacoby
> Assignee: Mihir Monani
> Priority: Major
> Attachments: PHOENIX-5482.patch
>
>
> HBase 1.3 and 2.0 introduced the
> hbase.ipc.server.priority.max.callqueue.length setting in HBASE-15470, to
> allow operators to vary the max queue length size for hbase:meta requests
> independently of normal regions.
> The PhoenixRpcScheduler doesn't check this setting, and uses the existing
> ipc.server.max.callqueue.length for all of its queues (normal, index, and
> metadata). While we should still default to this setting if the newer
> priority callqueue setting isn't present, Phoenix should use the new setting
> for index and metadata queues if it's present.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
