[
https://issues.apache.org/jira/browse/AMBARI-13678?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14987131#comment-14987131
]
Hudson commented on AMBARI-13678:
---------------------------------
FAILURE: Integrated in Ambari-trunk-Commit #3759 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/3759/])
AMBARI-13678 Make it configurable as to how frequently ActionScheduler (dsen:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=e86d1cd7c3fa6a03f289cd83ed945b5b9acfc668])
*
ambari-server/src/test/java/org/apache/ambari/server/scheduler/ExecutionSchedulerTest.java
*
ambari-server/src/main/java/org/apache/ambari/server/configuration/Configuration.java
*
ambari-server/src/main/java/org/apache/ambari/server/controller/ControllerModule.java
*
ambari-server/src/test/java/org/apache/ambari/server/configuration/ConfigurationTest.java
> 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)
