phoenix-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hadoop QA (JIRA)" <>
Subject [jira] [Commented] (PHOENIX-5252) Add job priority option to UpdateStatisticsTool
Date Mon, 22 Apr 2019 22:24:00 GMT


Hadoop QA commented on PHOENIX-5252:

{color:red}-1 overall{color}.  Here are the results of testing the latest attachment
  against 4.x-HBase-1.4 branch at commit 4ef749dd92d4af7529a07d343cb0186302979a14.
  ATTACHMENT ID: 12966645

    {color:green}+1 @author{color}.  The patch does not contain any @author tags.

    {color:green}+1 tests included{color}.  The patch appears to include 3 new or modified

    {color:green}+1 javac{color}.  The applied patch does not increase the total number of
javac compiler warnings.

    {color:red}-1 release audit{color}.  The applied patch generated 6 release audit warnings
(more than the master's current 0 warnings).

    {color:green}+1 lineLengths{color}.  The patch does not introduce lines longer than 100

    {color:green}+1 core tests{color}.  The patch passed unit tests in .

Test results:
Release audit warnings:
Console output:

This message is automatically generated.

> Add job priority option to UpdateStatisticsTool
> -----------------------------------------------
>                 Key: PHOENIX-5252
>                 URL:
>             Project: Phoenix
>          Issue Type: New Feature
>            Reporter: Xinyi Yan
>            Assignee: Xinyi Yan
>            Priority: Major
>              Labels: stats, statsCollection
>             Fix For: 4.15.0, 5.1.0
>         Attachments: PHOENIX-5252-4.x-HBase-1.4.patch, PHOENIX-5252.patch
>          Time Spent: 20m
>  Remaining Estimate: 0h
> This Jira adds a new command line option that allows users to specify the job priority
to the tool. 
> The current implementation doesn't support the MR job priority, and it might limit the
usecase. For instance, we have 10 running jobs in a queue, and we get a new urgent MR job.
Instead of deleting all currently running jobs, inserting a high priority job could solve
this problem.

This message was sent by Atlassian JIRA

View raw message