You are viewing a plain text version of this content. The canonical link for it is here.
Posted to reviews@ambari.apache.org by Vishal Suvagia via Review Board <no...@reviews.apache.org> on 2017/03/21 15:23:41 UTC

Review Request 57809: AMBARI-20505 : Changes needed to handle AMBARI-19623 in EU/RU scenario.

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

Review request for Ambari, Alejandro Fernandez, Gautam Borad, Madhan Neethiraj, Mugdha Varadkar, Oliver Szabo, and Sumit Mohanty.


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


Repository: ambari


Description
-------

Currently zookeeper connect/session timeout values for atlas are set to 200/400 ms respectively which are very low and not practical/recommended values. Due to this atlas startup fails more frequently.Below are recommended configurations.

For Atlas:
atlas.kafka.zookeeper.connection.timeout.ms=30000
atlas.kafka.zookeeper.session.timeout.ms=60000
atlas.audit.zookeeper.session.timeout.ms=60000

For Zookeeper:
tickTime=3000

As fresh installation scenario have already been fixed in AMBARI-19623, This patch is to handle the EU and RU scenarios.


Diffs
-----

  ambari-server/src/main/resources/common-services/ATLAS/0.1.0.2.3/configuration/application-properties.xml e4fc3de 
  ambari-server/src/main/resources/common-services/ATLAS/0.7.0.2.5/configuration/application-properties.xml 70af02c 
  ambari-server/src/main/resources/common-services/ZOOKEEPER/3.4.5/configuration/zoo.cfg.xml 5877877 


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


Testing
-------

Verified install and upgrade on CentOS-6.


Thanks,

Vishal Suvagia


Re: Review Request 57809: AMBARI-20505 : Changes needed to handle AMBARI-19623 in EU/RU scenario.

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


Ship it!




Ambari 2.5 RC0 is in progress and any commits would invalidate the release candidate. If this is a blocker, please let me know. Otherwise, I can commit to trunk now, and after 2.5 is released commit it to that branch and then close the Jira.

- Alejandro Fernandez


On March 22, 2017, 6:22 a.m., Vishal Suvagia wrote:
> 
> -----------------------------------------------------------
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/57809/
> -----------------------------------------------------------
> 
> (Updated March 22, 2017, 6:22 a.m.)
> 
> 
> Review request for Ambari, Alejandro Fernandez, Gautam Borad, Madhan Neethiraj, Mugdha Varadkar, Oliver Szabo, and Sumit Mohanty.
> 
> 
> Bugs: AMBARI-20505
>     https://issues.apache.org/jira/browse/AMBARI-20505
> 
> 
> Repository: ambari
> 
> 
> Description
> -------
> 
> Currently zookeeper connect/session timeout values for atlas are set to 200/400 ms respectively which are very low and not practical/recommended values. Due to this atlas startup fails more frequently.Below are recommended configurations.
> 
> For Atlas:
> atlas.kafka.zookeeper.connection.timeout.ms=30000
> atlas.kafka.zookeeper.session.timeout.ms=60000
> atlas.audit.zookeeper.session.timeout.ms=60000
> 
> 
> As fresh installation scenario have already been fixed in AMBARI-19623, This patch is to handle the EU and RU scenarios.
> 
> 
> Diffs
> -----
> 
>   ambari-server/src/main/resources/stacks/HDP/2.5/upgrades/config-upgrade.xml c13724b 
>   ambari-server/src/main/resources/stacks/HDP/2.5/upgrades/nonrolling-upgrade-2.5.xml 39cb0dc 
>   ambari-server/src/main/resources/stacks/HDP/2.5/upgrades/nonrolling-upgrade-2.6.xml 57a5203 
>   ambari-server/src/main/resources/stacks/HDP/2.5/upgrades/upgrade-2.5.xml b5b45cb 
>   ambari-server/src/main/resources/stacks/HDP/2.5/upgrades/upgrade-2.6.xml 44d0a2a 
> 
> 
> Diff: https://reviews.apache.org/r/57809/diff/2/
> 
> 
> Testing
> -------
> 
> Verified install and upgrade on CentOS-6.
> 
> 
> Thanks,
> 
> Vishal Suvagia
> 
>


Re: Review Request 57809: AMBARI-20505 : Changes needed to handle AMBARI-19623 in EU/RU scenario.

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



Pushed to trunk, commit ca2c83582e135bb5410b62775292a780e68757eb
STILL NEED TO COMMIT TO branch-2.5 after the RC candidate is done and the 2.5 release is done. Leave the Jira open until then.

- Alejandro Fernandez


On March 22, 2017, 6:22 a.m., Vishal Suvagia wrote:
> 
> -----------------------------------------------------------
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/57809/
> -----------------------------------------------------------
> 
> (Updated March 22, 2017, 6:22 a.m.)
> 
> 
> Review request for Ambari, Alejandro Fernandez, Gautam Borad, Madhan Neethiraj, Mugdha Varadkar, Oliver Szabo, and Sumit Mohanty.
> 
> 
> Bugs: AMBARI-20505
>     https://issues.apache.org/jira/browse/AMBARI-20505
> 
> 
> Repository: ambari
> 
> 
> Description
> -------
> 
> Currently zookeeper connect/session timeout values for atlas are set to 200/400 ms respectively which are very low and not practical/recommended values. Due to this atlas startup fails more frequently.Below are recommended configurations.
> 
> For Atlas:
> atlas.kafka.zookeeper.connection.timeout.ms=30000
> atlas.kafka.zookeeper.session.timeout.ms=60000
> atlas.audit.zookeeper.session.timeout.ms=60000
> 
> 
> As fresh installation scenario have already been fixed in AMBARI-19623, This patch is to handle the EU and RU scenarios.
> 
> 
> Diffs
> -----
> 
>   ambari-server/src/main/resources/stacks/HDP/2.5/upgrades/config-upgrade.xml c13724b 
>   ambari-server/src/main/resources/stacks/HDP/2.5/upgrades/nonrolling-upgrade-2.5.xml 39cb0dc 
>   ambari-server/src/main/resources/stacks/HDP/2.5/upgrades/nonrolling-upgrade-2.6.xml 57a5203 
>   ambari-server/src/main/resources/stacks/HDP/2.5/upgrades/upgrade-2.5.xml b5b45cb 
>   ambari-server/src/main/resources/stacks/HDP/2.5/upgrades/upgrade-2.6.xml 44d0a2a 
> 
> 
> Diff: https://reviews.apache.org/r/57809/diff/2/
> 
> 
> Testing
> -------
> 
> Verified install and upgrade on CentOS-6.
> 
> 
> Thanks,
> 
> Vishal Suvagia
> 
>


Re: Review Request 57809: AMBARI-20505 : Changes needed to handle AMBARI-19623 in EU/RU scenario.

Posted by Vishal Suvagia via Review Board <no...@reviews.apache.org>.
-----------------------------------------------------------
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/57809/
-----------------------------------------------------------

(Updated March 22, 2017, 6:22 a.m.)


Review request for Ambari, Alejandro Fernandez, Gautam Borad, Madhan Neethiraj, Mugdha Varadkar, Oliver Szabo, and Sumit Mohanty.


Changes
-------

Updating patch to change configurations on HDP upgrades.
Seperate patch for branch-2.5 is attached to Apache JIRA.


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


Repository: ambari


Description (updated)
-------

Currently zookeeper connect/session timeout values for atlas are set to 200/400 ms respectively which are very low and not practical/recommended values. Due to this atlas startup fails more frequently.Below are recommended configurations.

For Atlas:
atlas.kafka.zookeeper.connection.timeout.ms=30000
atlas.kafka.zookeeper.session.timeout.ms=60000
atlas.audit.zookeeper.session.timeout.ms=60000


As fresh installation scenario have already been fixed in AMBARI-19623, This patch is to handle the EU and RU scenarios.


Diffs (updated)
-----

  ambari-server/src/main/resources/stacks/HDP/2.5/upgrades/config-upgrade.xml c13724b 
  ambari-server/src/main/resources/stacks/HDP/2.5/upgrades/nonrolling-upgrade-2.5.xml 39cb0dc 
  ambari-server/src/main/resources/stacks/HDP/2.5/upgrades/nonrolling-upgrade-2.6.xml 57a5203 
  ambari-server/src/main/resources/stacks/HDP/2.5/upgrades/upgrade-2.5.xml b5b45cb 
  ambari-server/src/main/resources/stacks/HDP/2.5/upgrades/upgrade-2.6.xml 44d0a2a 


Diff: https://reviews.apache.org/r/57809/diff/2/

Changes: https://reviews.apache.org/r/57809/diff/1-2/


Testing
-------

Verified install and upgrade on CentOS-6.


Thanks,

Vishal Suvagia


Re: Review Request 57809: AMBARI-20505 : Changes needed to handle AMBARI-19623 in EU/RU scenario.

Posted by Vishal Suvagia via Review Board <no...@reviews.apache.org>.

> On March 21, 2017, 8:06 p.m., Alejandro Fernandez wrote:
> > ambari-server/src/main/resources/common-services/ATLAS/0.1.0.2.3/configuration/application-properties.xml
> > Line 164 (original), 164 (patched)
> > <https://reviews.apache.org/r/57809/diff/1/?file=1670906#file1670906line164>
> >
> >     Is this meant to affect existing installs that just upgrade Ambari, or clusters that upgrade their stack to a specific version?

the patch is updated to change configurations when doing HDP upgrade.


- Vishal


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


On March 21, 2017, 3:23 p.m., Vishal Suvagia wrote:
> 
> -----------------------------------------------------------
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/57809/
> -----------------------------------------------------------
> 
> (Updated March 21, 2017, 3:23 p.m.)
> 
> 
> Review request for Ambari, Alejandro Fernandez, Gautam Borad, Madhan Neethiraj, Mugdha Varadkar, Oliver Szabo, and Sumit Mohanty.
> 
> 
> Bugs: AMBARI-20505
>     https://issues.apache.org/jira/browse/AMBARI-20505
> 
> 
> Repository: ambari
> 
> 
> Description
> -------
> 
> Currently zookeeper connect/session timeout values for atlas are set to 200/400 ms respectively which are very low and not practical/recommended values. Due to this atlas startup fails more frequently.Below are recommended configurations.
> 
> For Atlas:
> atlas.kafka.zookeeper.connection.timeout.ms=30000
> atlas.kafka.zookeeper.session.timeout.ms=60000
> atlas.audit.zookeeper.session.timeout.ms=60000
> 
> For Zookeeper:
> tickTime=3000
> 
> As fresh installation scenario have already been fixed in AMBARI-19623, This patch is to handle the EU and RU scenarios.
> 
> 
> Diffs
> -----
> 
>   ambari-server/src/main/resources/common-services/ATLAS/0.1.0.2.3/configuration/application-properties.xml e4fc3de 
>   ambari-server/src/main/resources/common-services/ATLAS/0.7.0.2.5/configuration/application-properties.xml 70af02c 
>   ambari-server/src/main/resources/common-services/ZOOKEEPER/3.4.5/configuration/zoo.cfg.xml 5877877 
> 
> 
> Diff: https://reviews.apache.org/r/57809/diff/1/
> 
> 
> Testing
> -------
> 
> Verified install and upgrade on CentOS-6.
> 
> 
> Thanks,
> 
> Vishal Suvagia
> 
>


Re: Review Request 57809: AMBARI-20505 : Changes needed to handle AMBARI-19623 in EU/RU scenario.

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




ambari-server/src/main/resources/common-services/ATLAS/0.1.0.2.3/configuration/application-properties.xml
Line 164 (original), 164 (patched)
<https://reviews.apache.org/r/57809/#comment242047>

    Is this meant to affect existing installs that just upgrade Ambari, or clusters that upgrade their stack to a specific version?


- Alejandro Fernandez


On March 21, 2017, 3:23 p.m., Vishal Suvagia wrote:
> 
> -----------------------------------------------------------
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/57809/
> -----------------------------------------------------------
> 
> (Updated March 21, 2017, 3:23 p.m.)
> 
> 
> Review request for Ambari, Alejandro Fernandez, Gautam Borad, Madhan Neethiraj, Mugdha Varadkar, Oliver Szabo, and Sumit Mohanty.
> 
> 
> Bugs: AMBARI-20505
>     https://issues.apache.org/jira/browse/AMBARI-20505
> 
> 
> Repository: ambari
> 
> 
> Description
> -------
> 
> Currently zookeeper connect/session timeout values for atlas are set to 200/400 ms respectively which are very low and not practical/recommended values. Due to this atlas startup fails more frequently.Below are recommended configurations.
> 
> For Atlas:
> atlas.kafka.zookeeper.connection.timeout.ms=30000
> atlas.kafka.zookeeper.session.timeout.ms=60000
> atlas.audit.zookeeper.session.timeout.ms=60000
> 
> For Zookeeper:
> tickTime=3000
> 
> As fresh installation scenario have already been fixed in AMBARI-19623, This patch is to handle the EU and RU scenarios.
> 
> 
> Diffs
> -----
> 
>   ambari-server/src/main/resources/common-services/ATLAS/0.1.0.2.3/configuration/application-properties.xml e4fc3de 
>   ambari-server/src/main/resources/common-services/ATLAS/0.7.0.2.5/configuration/application-properties.xml 70af02c 
>   ambari-server/src/main/resources/common-services/ZOOKEEPER/3.4.5/configuration/zoo.cfg.xml 5877877 
> 
> 
> Diff: https://reviews.apache.org/r/57809/diff/1/
> 
> 
> Testing
> -------
> 
> Verified install and upgrade on CentOS-6.
> 
> 
> Thanks,
> 
> Vishal Suvagia
> 
>