[jira] [Updated] (AMBARI-20319) Server startup script keeps waiting even if DB consistency has failed

["Balázs Bence Sári (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/AMBARI-20319?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Balázs Bence Sári updated AMBARI-20319:
---------------------------------------
    Attachment: AMBARI-20319-Startup_errors-trunk-v1.patch

> 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)