You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ambari.apache.org by Dmitro Lisnichenko <dl...@hortonworks.com> on 2015/04/23 14:05:31 UTC
Review Request 33478: Usability: bootstrapping hosts shows "Preparing"
without any information and seems stuck. Additional changes
-----------------------------------------------------------
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/33478/
-----------------------------------------------------------
Review request for Ambari and Andrew Onischuk.
Bugs: AMBARI-10294
https://issues.apache.org/jira/browse/AMBARI-10294
Repository: ambari
Description
-------
This is a regression introduced in 2.0.0.
When doing SSH bootstrap of hosts via Install Wizard, the hosts are shown as "Preparing". When you click on the host, no information shows up. It gets stuck in this state until "Registering".
In 1.7.0, "Preparing" state was very brief and immediately switched to "Installing".
This is a BE issue.
API returns "RUNNING" without any information when installing Ambari Agent on the hosts.
This issue caused by absent of propagation fail of runing bootstrap.py (server side) to HostStatus which are pooled by UI.
So If bootstrap.py has syntax errors or fails while imports python modules it cant create *.log and *.done files, so java code can wait infinitely until *.done file will be created.
So solution of this issue is to propagate fatal errors of bootstrap.py to hostStatus info. In this case, setup of agents will fail and root cause of issue will be sent to UI
Diffs
-----
ambari-server/src/main/java/org/apache/ambari/server/bootstrap/BSHostStatusCollector.java cf3ee64
ambari-server/src/main/java/org/apache/ambari/server/bootstrap/BSRunner.java fe873d7
Diff: https://reviews.apache.org/r/33478/diff/
Testing
-------
in progress
Thanks,
Dmitro Lisnichenko
Re: Review Request 33478: Usability: bootstrapping hosts shows
"Preparing"
without any information and seems stuck. Additional changes
Posted by Andrew Onischuk <ao...@hortonworks.com>.
-----------------------------------------------------------
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/33478/#review81312
-----------------------------------------------------------
Ship it!
Ship It!
- Andrew Onischuk
On April 23, 2015, 1 p.m., Dmitro Lisnichenko wrote:
>
> -----------------------------------------------------------
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/33478/
> -----------------------------------------------------------
>
> (Updated April 23, 2015, 1 p.m.)
>
>
> Review request for Ambari and Andrew Onischuk.
>
>
> Bugs: AMBARI-10294
> https://issues.apache.org/jira/browse/AMBARI-10294
>
>
> Repository: ambari
>
>
> Description
> -------
>
> This is a regression introduced in 2.0.0.
> When doing SSH bootstrap of hosts via Install Wizard, the hosts are shown as "Preparing". When you click on the host, no information shows up. It gets stuck in this state until "Registering".
> In 1.7.0, "Preparing" state was very brief and immediately switched to "Installing".
> This is a BE issue.
> API returns "RUNNING" without any information when installing Ambari Agent on the hosts.
> This issue caused by absent of propagation fail of runing bootstrap.py (server side) to HostStatus which are pooled by UI.
> So If bootstrap.py has syntax errors or fails while imports python modules it cant create *.log and *.done files, so java code can wait infinitely until *.done file will be created.
> So solution of this issue is to propagate fatal errors of bootstrap.py to hostStatus info. In this case, setup of agents will fail and root cause of issue will be sent to UI
>
>
> Diffs
> -----
>
> ambari-server/src/main/java/org/apache/ambari/server/bootstrap/BSHostStatusCollector.java cf3ee64
> ambari-server/src/main/java/org/apache/ambari/server/bootstrap/BSRunner.java fe873d7
>
> Diff: https://reviews.apache.org/r/33478/diff/
>
>
> Testing
> -------
>
> [INFO] ------------------------------------------------------------------------
> [INFO] Reactor Summary:
> [INFO]
> [INFO] Ambari Views ...................................... SUCCESS [4.337s]
> [INFO] Ambari Metrics Common ............................. SUCCESS [2.008s]
> [INFO] Ambari Server ..................................... SUCCESS [53:37.014s]
> [INFO] ------------------------------------------------------------------------
> [INFO] BUILD SUCCESS
> [INFO] ------------------------------------------------------------------------
> [INFO] Total time: 53:46.209s
> [INFO] Finished at: Thu Apr 23 15:58:16 EEST 2015
> [INFO] Final Memory: 34M/313M
> [INFO] ------------------------------------------------------------------------
>
>
> Thanks,
>
> Dmitro Lisnichenko
>
>
Re: Review Request 33478: Usability: bootstrapping hosts shows
"Preparing"
without any information and seems stuck. Additional changes
Posted by Dmitro Lisnichenko <dl...@hortonworks.com>.
-----------------------------------------------------------
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/33478/
-----------------------------------------------------------
(Updated April 23, 2015, 1 p.m.)
Review request for Ambari and Andrew Onischuk.
Bugs: AMBARI-10294
https://issues.apache.org/jira/browse/AMBARI-10294
Repository: ambari
Description
-------
This is a regression introduced in 2.0.0.
When doing SSH bootstrap of hosts via Install Wizard, the hosts are shown as "Preparing". When you click on the host, no information shows up. It gets stuck in this state until "Registering".
In 1.7.0, "Preparing" state was very brief and immediately switched to "Installing".
This is a BE issue.
API returns "RUNNING" without any information when installing Ambari Agent on the hosts.
This issue caused by absent of propagation fail of runing bootstrap.py (server side) to HostStatus which are pooled by UI.
So If bootstrap.py has syntax errors or fails while imports python modules it cant create *.log and *.done files, so java code can wait infinitely until *.done file will be created.
So solution of this issue is to propagate fatal errors of bootstrap.py to hostStatus info. In this case, setup of agents will fail and root cause of issue will be sent to UI
Diffs
-----
ambari-server/src/main/java/org/apache/ambari/server/bootstrap/BSHostStatusCollector.java cf3ee64
ambari-server/src/main/java/org/apache/ambari/server/bootstrap/BSRunner.java fe873d7
Diff: https://reviews.apache.org/r/33478/diff/
Testing (updated)
-------
[INFO] ------------------------------------------------------------------------
[INFO] Reactor Summary:
[INFO]
[INFO] Ambari Views ...................................... SUCCESS [4.337s]
[INFO] Ambari Metrics Common ............................. SUCCESS [2.008s]
[INFO] Ambari Server ..................................... SUCCESS [53:37.014s]
[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESS
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 53:46.209s
[INFO] Finished at: Thu Apr 23 15:58:16 EEST 2015
[INFO] Final Memory: 34M/313M
[INFO] ------------------------------------------------------------------------
Thanks,
Dmitro Lisnichenko