[ 
https://issues.apache.org/jira/browse/AMBARI-11009?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14533563#comment-14533563
 ] 

Alejandro Fernandez commented on AMBARI-11009:
----------------------------------------------

1. In HDP 2.3, when installing multiple nimbus servers, the service check 
fails. To resolve this, modify the cmd as follows,
{code}storm jar /tmp/wordCount.jar storm.starter.WordCountTopology 
WordCount{unique}{code} if nimbus.seeds is supported and in the storm configs.

2. In RU from HDP 2.2  -> 2.3.0.0, Storm will not be rolling, so the upgrade 
pack still needs instructions to deactivate and kill running topologies before 
upgrading Storm, and to rebuild the topologies after.

In 2.3.0.0, Storm's defaults.yaml will have the property 
storm.meta.serialization.delegate set to 
backtype.storm.serialization.GzipThriftSerializationDelegate, so as long as 
Ambari doesn't override the property, the RU from 2.3.0.0 to 2.3+ will be 
rolling. So the upgrade pack from Dal to Dal will not need these manual 
confirmations.

To test this out, deploy HDP 2.3.0.0, then perform and RU to HDP 2.3+, and 
verify the topologies are still running

3. Currently, the nimbus.seeds property is marked as final and cannot be edited 
in the UI, so this needs to change to enable Nimbus HA

> Storm service check fails with multiple nimbus hosts, remove messages from 
> Storm RU now that it is rolling, allow nimbus.seeds to be edited 
> --------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: AMBARI-11009
>                 URL: https://issues.apache.org/jira/browse/AMBARI-11009
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-server
>    Affects Versions: 2.1.0
>            Reporter: Alejandro Fernandez
>            Assignee: Alejandro Fernandez
>             Fix For: 2.1.0
>
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to