ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dmytro Sen (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 15:19:27 GMT

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

Dmytro Sen commented on AMBARI-13678:
-------------------------------------

failing "test/python/stacks/2.0.6/HBASE/test_hbase_master.py" are not related to this commit

> 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