Member since
04-06-2018
16
Posts
1
Kudos Received
0
Solutions
09-08-2018
10:21 AM
I've figured out what the problem is there. In order to make it work - you need to add more fields to your user config in env.xml. Compare the above cassandra example: <property>
<name>cassandra_user</name>
<value>cassandra</value>
<property-type>USER</property-type>
<description></description>
</property> And working YARN example from the Ambari 2.7 server: <property>
<name>yarn_ats_user</name>
<display-name>Yarn ATS User</display-name>
<value>yarn-ats</value>
<property-type>USER</property-type>
<description>YARN Client User for ATSv2 backend</description>
<value-attributes>
<type>user</type>
<overridable>false</overridable>
<user-groups>
<property>
<type>cluster-env</type>
<name>user_group</name>
</property>
</user-groups>
</value-attributes>
<on-ambari-upgrade add="false"/>
</property> You need to add the display-name and value-attributes fields to your env.xml file (https://github.com/Dominion-Digital/ambari-cassandra-service/blob/master/configuration/cassandra-env.xml, for example). Then - restart ambari server and this problem should be solved. In case of service install - you may want to remove and then add again your service.
... View more