[
https://issues.apache.org/jira/browse/AMBARI-20319?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15899356#comment-15899356
]
Hudson commented on AMBARI-20319:
---------------------------------
FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #6962 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/6962/])
AMBARI-20319 Server startup script keeps waiting even if DB consistency
(lpuskas:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=c21f77dfb6ca4fdd012af4313696eabcc11c1fbc])
* (edit) ambari-server/src/main/python/ambari_server_main.py
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/controller/AmbariServer.java
* (edit) ambari-server/src/main/python/ambari_server/utils.py
> Server startup script keeps waiting even if DB consistency has failed
> ---------------------------------------------------------------------
>
> Key: AMBARI-20319
> URL: https://issues.apache.org/jira/browse/AMBARI-20319
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
> Affects Versions: 3.0.0, 2.5.0
> Reporter: Balázs Bence Sári
> Assignee: Balázs Bence Sári
> Priority: Minor
> Fix For: 3.0.0, 2.5.0
>
> Attachments: AMBARI-20319-Startup_errors-trunk-v1.patch
>
>
> The current logic of the Ambari server startup script:
> 1. Wait for java server process PID
> 2. Java process starts Database check
> 3. Script waits until UI becomes available or timeout occurs
> If DB check fails, the script waits some 50 seconds for the UI, before
> timeout occurs, although it should fail instantly in this case.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
