You are viewing a plain text version of this content. The canonical link for it is here.
Posted to reviews@ambari.apache.org by Alejandro Fernandez <af...@hortonworks.com> on 2017/05/17 05:15:15 UTC

Review Request 59329: Atlas web UI inaccessible after adding Atlas service on upgraded cluster with Hive because /etc/atlas/conf symlink was created ahead of time

-----------------------------------------------------------
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/59329/
-----------------------------------------------------------

Review request for Ambari, Jonathan Hurley, Jayush Luniya, Nate Cole, and Sumit Mohanty.


Bugs: AMBARI-21039
    https://issues.apache.org/jira/browse/AMBARI-21039


Repository: ambari


Description
-------

STR:
*Install Ambari 2.4.3 with HDP 2.5.3.0
*Include ZK, HDFS, MR, YARN, Hive (plus Pig, Tez, Slider), Kafka, Ambari Infra
*Install bits for HDP 2.5.5.0
*Perform EU
*Add Atlas as a service

There will be an alert for "Metadata Server Web UI" being inaccessible because /etc/atlas/conf/solr/ will contain the wrong configs after the upgrade.
This happens because installing Hive will also create artifacts in /usr/hdp/$version/atlas for the hooks, so when the bits are installed, it mistakenly creates /etc/atlas/conf as a broken symlink to /usr/hdp/current/atlas-client/conf (which doesn't exist yet). Because the symlink is broken to begin with, then adding Atlas for the first time does not populate the correct solr configs.

This is a regression of AMBARI-18368, now that /usr/hdp/current/atlas-client exists as a valid symlink even though Atlas is not actually


Diffs
-----

  ambari-common/src/main/python/resource_management/libraries/functions/conf_select.py 8d54053 


Diff: https://reviews.apache.org/r/59329/diff/1/


Testing
-------

Verified on live cluster.


Thanks,

Alejandro Fernandez

Re: Review Request 59329: Atlas web UI inaccessible after adding Atlas service on upgraded cluster with Hive because /etc/atlas/conf symlink was created ahead of time

Posted by Jonathan Hurley <jh...@hortonworks.com>.
-----------------------------------------------------------
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/59329/#review175247
-----------------------------------------------------------


Ship it!




Ship It!

- Jonathan Hurley


On May 17, 2017, 1:15 a.m., Alejandro Fernandez wrote:
> 
> -----------------------------------------------------------
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/59329/
> -----------------------------------------------------------
> 
> (Updated May 17, 2017, 1:15 a.m.)
> 
> 
> Review request for Ambari, Jonathan Hurley, Jayush Luniya, Nate Cole, and Sumit Mohanty.
> 
> 
> Bugs: AMBARI-21039
>     https://issues.apache.org/jira/browse/AMBARI-21039
> 
> 
> Repository: ambari
> 
> 
> Description
> -------
> 
> STR:
> *Install Ambari 2.4.3 with HDP 2.5.3.0
> *Include ZK, HDFS, MR, YARN, Hive (plus Pig, Tez, Slider), Kafka, Ambari Infra
> *Install bits for HDP 2.5.5.0
> *Perform EU
> *Add Atlas as a service
> 
> There will be an alert for "Metadata Server Web UI" being inaccessible because /etc/atlas/conf/solr/ will contain the wrong configs after the upgrade.
> This happens because installing Hive will also create artifacts in /usr/hdp/$version/atlas for the hooks, so when the bits are installed, it mistakenly creates /etc/atlas/conf as a broken symlink to /usr/hdp/current/atlas-client/conf (which doesn't exist yet). Because the symlink is broken to begin with, then adding Atlas for the first time does not populate the correct solr configs.
> 
> This is a regression of AMBARI-18368, now that /usr/hdp/current/atlas-client exists as a valid symlink even though Atlas is not actually
> 
> 
> Diffs
> -----
> 
>   ambari-common/src/main/python/resource_management/libraries/functions/conf_select.py 8d54053 
> 
> 
> Diff: https://reviews.apache.org/r/59329/diff/1/
> 
> 
> Testing
> -------
> 
> Verified on live cluster.
> 
> 
> Thanks,
> 
> Alejandro Fernandez
> 
>

Re: Review Request 59329: Atlas web UI inaccessible after adding Atlas service on upgraded cluster with Hive because /etc/atlas/conf symlink was created ahead of time

Posted by Alejandro Fernandez <af...@hortonworks.com>.
-----------------------------------------------------------
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/59329/
-----------------------------------------------------------

(Updated May 18, 2017, 3:48 p.m.)


Review request for Ambari, Jonathan Hurley, Jayush Luniya, Nate Cole, and Sumit Mohanty.


Bugs: AMBARI-21039
    https://issues.apache.org/jira/browse/AMBARI-21039


Repository: ambari


Description
-------

STR:
*Install Ambari 2.4.3 with HDP 2.5.3.0
*Include ZK, HDFS, MR, YARN, Hive (plus Pig, Tez, Slider), Kafka, Ambari Infra
*Install bits for HDP 2.5.5.0
*Perform EU
*Add Atlas as a service

There will be an alert for "Metadata Server Web UI" being inaccessible because /etc/atlas/conf/solr/ will contain the wrong configs after the upgrade.
This happens because installing Hive will also create artifacts in /usr/hdp/$version/atlas for the hooks, so when the bits are installed, it mistakenly creates /etc/atlas/conf as a broken symlink to /usr/hdp/current/atlas-client/conf (which doesn't exist yet). Because the symlink is broken to begin with, then adding Atlas for the first time does not populate the correct solr configs.

This is a regression of AMBARI-18368, now that /usr/hdp/current/atlas-client exists as a valid symlink even though Atlas is not actually


Diffs
-----

  ambari-common/src/main/python/resource_management/libraries/functions/conf_select.py 8d54053 


Diff: https://reviews.apache.org/r/59329/diff/1/


Testing
-------

Verified on live cluster.


Thanks,

Alejandro Fernandez

Re: Review Request 59329: Atlas web UI inaccessible after adding Atlas service on upgraded cluster with Hive because /etc/atlas/conf symlink was created ahead of time

Posted by Nate Cole <nc...@hortonworks.com>.
-----------------------------------------------------------
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/59329/#review175281
-----------------------------------------------------------


Ship it!




Ship It!

- Nate Cole


On May 17, 2017, 1:15 a.m., Alejandro Fernandez wrote:
> 
> -----------------------------------------------------------
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/59329/
> -----------------------------------------------------------
> 
> (Updated May 17, 2017, 1:15 a.m.)
> 
> 
> Review request for Ambari, Jonathan Hurley, Jayush Luniya, Nate Cole, and Sumit Mohanty.
> 
> 
> Bugs: AMBARI-21039
>     https://issues.apache.org/jira/browse/AMBARI-21039
> 
> 
> Repository: ambari
> 
> 
> Description
> -------
> 
> STR:
> *Install Ambari 2.4.3 with HDP 2.5.3.0
> *Include ZK, HDFS, MR, YARN, Hive (plus Pig, Tez, Slider), Kafka, Ambari Infra
> *Install bits for HDP 2.5.5.0
> *Perform EU
> *Add Atlas as a service
> 
> There will be an alert for "Metadata Server Web UI" being inaccessible because /etc/atlas/conf/solr/ will contain the wrong configs after the upgrade.
> This happens because installing Hive will also create artifacts in /usr/hdp/$version/atlas for the hooks, so when the bits are installed, it mistakenly creates /etc/atlas/conf as a broken symlink to /usr/hdp/current/atlas-client/conf (which doesn't exist yet). Because the symlink is broken to begin with, then adding Atlas for the first time does not populate the correct solr configs.
> 
> This is a regression of AMBARI-18368, now that /usr/hdp/current/atlas-client exists as a valid symlink even though Atlas is not actually
> 
> 
> Diffs
> -----
> 
>   ambari-common/src/main/python/resource_management/libraries/functions/conf_select.py 8d54053 
> 
> 
> Diff: https://reviews.apache.org/r/59329/diff/1/
> 
> 
> Testing
> -------
> 
> Verified on live cluster.
> 
> 
> Thanks,
> 
> Alejandro Fernandez
> 
>

Re: Review Request 59329: Atlas web UI inaccessible after adding Atlas service on upgraded cluster with Hive because /etc/atlas/conf symlink was created ahead of time

Posted by Alejandro Fernandez <af...@hortonworks.com>.
-----------------------------------------------------------
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/59329/#review175205
-----------------------------------------------------------




ambari-common/src/main/python/resource_management/libraries/functions/conf_select.py
Line 360 (original), 363 (patched)
<https://reviews.apache.org/r/59329/#comment248612>

    The underlying bug is that /usr/hdp/current/atlas-client exists (parent_dir) and is valid even when Atlas is not installed as a service in the cluster because Hive service has an RPM for the Atlas plugin that creates /usr/hdp/$version/atlas to put some hooks in it.
    
    If Atlas is not a service, then before it would mistakenly create /etc/atlas/conf -> /usr/hdp/current/atlas-client/conf and therefore be unable to seed it with proper configs when Atlas is added after the EU is done.


- Alejandro Fernandez


On May 17, 2017, 5:15 a.m., Alejandro Fernandez wrote:
> 
> -----------------------------------------------------------
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/59329/
> -----------------------------------------------------------
> 
> (Updated May 17, 2017, 5:15 a.m.)
> 
> 
> Review request for Ambari, Jonathan Hurley, Jayush Luniya, Nate Cole, and Sumit Mohanty.
> 
> 
> Bugs: AMBARI-21039
>     https://issues.apache.org/jira/browse/AMBARI-21039
> 
> 
> Repository: ambari
> 
> 
> Description
> -------
> 
> STR:
> *Install Ambari 2.4.3 with HDP 2.5.3.0
> *Include ZK, HDFS, MR, YARN, Hive (plus Pig, Tez, Slider), Kafka, Ambari Infra
> *Install bits for HDP 2.5.5.0
> *Perform EU
> *Add Atlas as a service
> 
> There will be an alert for "Metadata Server Web UI" being inaccessible because /etc/atlas/conf/solr/ will contain the wrong configs after the upgrade.
> This happens because installing Hive will also create artifacts in /usr/hdp/$version/atlas for the hooks, so when the bits are installed, it mistakenly creates /etc/atlas/conf as a broken symlink to /usr/hdp/current/atlas-client/conf (which doesn't exist yet). Because the symlink is broken to begin with, then adding Atlas for the first time does not populate the correct solr configs.
> 
> This is a regression of AMBARI-18368, now that /usr/hdp/current/atlas-client exists as a valid symlink even though Atlas is not actually
> 
> 
> Diffs
> -----
> 
>   ambari-common/src/main/python/resource_management/libraries/functions/conf_select.py 8d54053 
> 
> 
> Diff: https://reviews.apache.org/r/59329/diff/1/
> 
> 
> Testing
> -------
> 
> Verified on live cluster.
> 
> 
> Thanks,
> 
> Alejandro Fernandez
> 
>