That's a good observation. I think it should have logic to always swap. If hive.server2.transport.mode is set to "binary", then swap hive.server2.thrift.port between 10,000 and 10,010 If hive.server2.transport.mode is set to "http", then swap hive.server2.http.port between 10,001 and 10,011
Thanks, Alejandro On 2/4/16, 1:10 PM, "Di Li" <[email protected]> wrote: >Hello folks, > >When rolling upgrade HDP 2.2 to 2.3, HiveServer2 port is changed from >10000 to 10010. The same port change logic is in upgrade-2.4.xml as well. > >But wouldn't this make no difference if I rolling upgrade a 2.3 cluster >that was originally rolling upgrade from an HDP 2.2 cluster , where the >port had already been changed to 10010? It'd be like changing the port >from 10010 (on HDP 2.3) to 10010 (on HDP 2.4), right ? > >How does Ambari handle Hive Server 2 port value change in this >continuously upgrade case? > > >Thank you. > >Di Li
