Hi Anita… This is the expected behavior. When disabling Kerberos, the configuration properties changed while enabling Kerberos are reverted back to the relevant stack’s default values. There are many reasons for this, one of which has to do with upgrading Ambari or the stack after Kerberos was enabled. With this scenario, simply revering back to an earlier version of the configurations is not a good idea since property sets and/or property meanings could have changed.
Rob On 7/11/16, 1:49 PM, "Anita Jebaraj" <[email protected]> wrote: Hello everyone, I have a question regarding the values for the kerberos related properties being reset to the default value after disabling kerberos. I tried this scenario in properties like templeton.hive.properties and dfs.datanode.address. For ex: I changed the port number for the property dfs.datanode.address from 0.0.0.0:50010 to 0.0.0.0:50050. When enabling kerberos the value is changed to 0.0.0.0:0019, which is expected, but after disabling kerberos, the value is reset back to 0.0.0.0:50010(default value) instead of the user customized value 0.0.0.0.50050. Can someone please confirm if this is a defect or an expected behavior for kerberos related properties. Thanks, Anita Jebaraj
