ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hadoop QA (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AMBARI-13678) Make it configurable as to how frequently ActionScheduler scans DB for tasks
Date Tue, 03 Nov 2015 07:52:27 GMT

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

Hadoop QA commented on AMBARI-13678:
------------------------------------

{color:green}+1 overall{color}.  Here are the results of testing the latest attachment 
  http://issues.apache.org/jira/secure/attachment/12770096/AMBARI-13678.patch
  against trunk revision .

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

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

    {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 core tests{color}.  The patch passed unit tests in ambari-server.

Test results: https://builds.apache.org/job/Ambari-trunk-test-patch/4150//testReport/
Console output: https://builds.apache.org/job/Ambari-trunk-test-patch/4150//console

This message is automatically generated.

> Make it configurable as to how frequently ActionScheduler scans DB for tasks
> ----------------------------------------------------------------------------
>
>                 Key: AMBARI-13678
>                 URL: https://issues.apache.org/jira/browse/AMBARI-13678
>             Project: Ambari
>          Issue Type: Bug
>    Affects Versions: 2.1.3
>            Reporter: Dmytro Sen
>            Assignee: Dmytro Sen
>            Priority: Critical
>             Fix For: 2.1.3
>
>         Attachments: AMBARI-13678.patch
>
>
> ActionScheduler now sleeps only 1 second between scans while it was sleeping for 10 seconds
before. We should make it configurable where user can set the delay. Users with slower DB
would rather have ActionScheduler not work so aggressively.
> Currently, it is hard coded to 1 second.
> {code}
> bindConstant().annotatedWith(Names.named("schedulerSleeptime")).to(1000L);
> {code}
> Lets add a config parameter to {{ambari.properties}} -  {{server.execution.scheduler.wait}}
and default should be 1 second. If the value is more than 60 second then it should automatically
set to 60 second with a log saying so.



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

Mime
View raw message