Details
-
Bug
-
Status: To Do
-
Major
-
Resolution: Unresolved
-
0.4.1
-
None
-
None
Description
After kerberization, the 'topology.work.childopts' setting in `config/profiler.properties` is defined as follows.
topology.worker.childopts=-Djava.security.auth.login.config=/usr/hcp/1.3.0.0-51/metron/client_jaas.conf
When I look in the Ambari settings for the Profiler, the topology.worker.childopts field is blank. I would expect Ambari to display this value, not blank so that it matches what the topology will run with.
Then I then add a few values like the following through Ambari and restart the Profiler topology.
-Dsun.security.krb5.debug=true -Djava.security.auth.login.config=/usr/hcp/1.3.0.0-51/metron/client_jaas.conf
What Ambari actually populates in the 'config/profiler.properties' is actually this.
topology.worker.childopts=-Djava.security.auth.login.config=/usr/hcp/1.3.0.0-51/metron/client_jaas.conf -Dsun.security.krb5.debug=true -Djava.security.auth.login.config=/usr/hcp/1.3.0.0-51/metron/client_jaas.conf
It seems to prepend the value given by the user with the following in all cases.
Djava.security.auth.login.config=/usr/hcp/1.3.0.0-51/metron/client_jaas.conf
A user would expect that the values defined in Ambari, is what the topology would actually run with.