[
https://issues.apache.org/jira/browse/AMBARI-4527?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Siddharth Wagle updated AMBARI-4527:
------------------------------------
Description:
*Problem description*:
Batch request to do rolling restart does not work.
The API says "201 created", but no requests are created.
*Reason*:
Server clock synced up with NTP daemon and was reset after Scheduler initialize
and before Scheduler start.
This caused the Thread.sleep() in the Scheduler.startDelayed() to be paused for
a long time since the native implementation relies on server clock.
was:
*Problem description*:
Batch request to do rolling restart does not work.
The API says "201 created", but no requests are created.
*Reason*:
Server clock synced up with NTP daemon and was reset after Scheduler initialize
and before Scheduler start. This caused the Thread.sleep() in the
Scheduler.startDelayed() to be paused for a long time since the native
implementation relies on server clock.
> Rolling Restart not working
> ----------------------------
>
> Key: AMBARI-4527
> URL: https://issues.apache.org/jira/browse/AMBARI-4527
> Project: Ambari
> Issue Type: Bug
> Components: controller
> Affects Versions: 1.5.0
> Reporter: Siddharth Wagle
> Assignee: Siddharth Wagle
> Fix For: 1.5.0
>
>
> *Problem description*:
> Batch request to do rolling restart does not work.
> The API says "201 created", but no requests are created.
> *Reason*:
> Server clock synced up with NTP daemon and was reset after Scheduler
> initialize and before Scheduler start.
> This caused the Thread.sleep() in the Scheduler.startDelayed() to be paused
> for a long time since the native implementation relies on server clock.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
