[jira] [Commented] (AMBARI-20319) Server startup script keeps waiting even if DB consistency has failed
[ https://issues.apache.org/jira/browse/AMBARI-20319?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15899509#comment-15899509 ] Hudson commented on AMBARI-20319: - SUCCESS: Integrated in Jenkins build Ambari-branch-2.5 #1199 (See [https://builds.apache.org/job/Ambari-branch-2.5/1199/]) AMBARI-20319 Server startup script keeps waiting even if DB consistency (lpuskas: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=4df38c35f42a632dd822c6c59e4e520f6caad8fd]) * (edit) ambari-server/src/main/python/ambari_server/utils.py * (edit) ambari-server/src/main/java/org/apache/ambari/server/controller/AmbariServer.java * (edit) ambari-server/src/main/python/ambari_server_main.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)
[jira] [Commented] (AMBARI-20319) Server startup script keeps waiting even if DB consistency has failed
[ https://issues.apache.org/jira/browse/AMBARI-20319?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=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=commit=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)
[jira] [Commented] (AMBARI-20319) Server startup script keeps waiting even if DB consistency has failed
[
https://issues.apache.org/jira/browse/AMBARI-20319?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15897698#comment-15897698
]
Hadoop QA commented on AMBARI-20319:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12856291/AMBARI-20319-Startup_errors-trunk-v1.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include
any new or modified tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
ambari-server.
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/10893//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/10893//console
This message is automatically generated.
> 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)
