Nick Allen created METRON-1203:
----------------------------------
Summary: Profiler MPack 'topology.work.childopts' Value Does Not
Match Ambari Setting
Key: METRON-1203
URL: https://issues.apache.org/jira/browse/METRON-1203
Project: Metron
Issue Type: Bug
Affects Versions: 0.4.1
Reporter: Nick Allen
After kerberization, the `config/profiler.properties` file's
''topology.work.childopts' setting look-like this.
{code}
topology.worker.childopts=-Djava.security.auth.login.config=/usr/hcp/1.3.0.0-51/metron/client_jaas.conf
{code}
When I look in the Ambari settings for the Profiler, the
topology.worker.childopts field is blank.
I then add a few values like the following through Ambari and restart the
Profiler topology.
{code}
-Dsun.security.krb5.debug=true
-Djava.security.auth.login.config=/usr/hcp/1.3.0.0-51/metron/client_jaas.conf
{code}
What Ambari actually populates in the 'config/profiler.properties' is actually
this.
{code}
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
{code}
It seems to prepend the value given by the user with the following in all cases.
{code}
Djava.security.auth.login.config=/usr/hcp/1.3.0.0-51/metron/client_jaas.conf
{code}
A user would expect that the values defined in Ambari, is what the topology
would actually run with.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
