----------------------------------------------------------- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/36508/#review91758 -----------------------------------------------------------
Ship it! Ship It! - Jonathan Hurley On July 15, 2015, 1:14 p.m., Dmytro Sen wrote: > > ----------------------------------------------------------- > This is an automatically generated e-mail. To reply, visit: > https://reviews.apache.org/r/36508/ > ----------------------------------------------------------- > > (Updated July 15, 2015, 1:14 p.m.) > > > Review request for Ambari, Jonathan Hurley and Nate Cole. > > > Bugs: AMBARI-12419 > https://issues.apache.org/jira/browse/AMBARI-12419 > > > Repository: ambari > > > Description > ------- > > The issue is noticed in an RU cluster where rolling upgrade has to be > performed with ambari2.1.0. After installing dal bits we are setting final > flag for a property 'tez.am.resource.memory.mb' to final which you can see in > V3 config of the cluster. Then enabling security and HA is performed. After > these operations we see that the final flag was turned off. Upon checking the > versions, V4 doesn't have this final flag and changes between V3 and V4 is > that, security is enabled at V4. (HiveServer2 Authentication is set to > kerberos in V4 not in V3). > > > Diffs > ----- > > > ambari-server/src/main/java/org/apache/ambari/server/state/ConfigHelper.java > 8b4b1e2 > > ambari-server/src/test/java/org/apache/ambari/server/state/ConfigHelperTest.java > 1376d29 > > Diff: https://reviews.apache.org/r/36508/diff/ > > > Testing > ------- > > [INFO] Reactor Summary: > [INFO] > [INFO] Ambari Main ....................................... SUCCESS [6.261s] > [INFO] Apache Ambari Project POM ......................... SUCCESS [0.073s] > [INFO] Ambari Web ........................................ SUCCESS [44.994s] > [INFO] Ambari Views ...................................... SUCCESS [3.141s] > [INFO] Ambari Admin View ................................. SUCCESS [12.016s] > [INFO] ambari-metrics .................................... SUCCESS [0.891s] > [INFO] Ambari Metrics Common ............................. SUCCESS [2.405s] > [INFO] Ambari Metrics Hadoop Sink ........................ SUCCESS [4.246s] > [INFO] Ambari Metrics Flume Sink ......................... SUCCESS [2.049s] > [INFO] Ambari Metrics Kafka Sink ......................... SUCCESS [3.349s] > [INFO] Ambari Metrics Storm Sink ......................... SUCCESS [2.325s] > [INFO] Ambari Metrics Collector .......................... SUCCESS [3:23.397s] > [INFO] Ambari Metrics Monitor ............................ SUCCESS [3.840s] > [INFO] Ambari Metrics Assembly ........................... SUCCESS [1:43.661s] > [INFO] Ambari Server ..................................... SUCCESS > [1:08:07.981s] > [INFO] Ambari Agent ...................................... SUCCESS [20.250s] > [INFO] Ambari Client ..................................... SUCCESS [0.073s] > [INFO] Ambari Python Client .............................. SUCCESS [0.784s] > [INFO] Ambari Groovy Client .............................. SUCCESS [12.384s] > [INFO] Ambari Shell ...................................... SUCCESS [0.060s] > [INFO] Ambari Python Shell ............................... SUCCESS [0.103s] > [INFO] Ambari Groovy Shell ............................... SUCCESS [7.909s] > > > Thanks, > > Dmytro Sen > >
