HDFS - YARN - InfraSolr: ZK Client when using custom zookeeper principal

[#1]

Current on version HDP-2.6.x - Ambari-2.5.x if the zookeeper principal name is changed or customized manual changes are required for HDFS, Yarn and Ambari-Infra.

In Ambari - config - for yarn and HDFS: yarn-env.sh

YARN_OPTS="-Dzookeeper.sasl.client=true -Dzookeeper.sasl.client.username=sand-box-zookeeper -Djava.security.auth.login.config=/etc/hadoop/2.6.0.3-8/0/yarn_jaas.conf -Dzookeeper.sasl.clientconfig=Client $YARN_OPTS" 

hadoop/conf/hadoop-env.sh

export HADOOP_ZKFC_OPTS="-Dzookeeper.sasl.client=true -Dzookeeper.sasl.client.username=sandbox-zookeeper -Djava.security.auth.login.config=/usr/hdp/current/hadoop-client/conf/secure/hdfs_jaas.conf -Dzookeeper.sasl.clientconfig=Client $HADOOP_ZKFC_OPTS" 

For Ambari-Infra/Solr edit /usr/lib/ambari-infra-solr-client/solrCloudCli.sh

PATH=$JAVA_HOME/bin:$PATH $JVM -classpath "$sdir:$sdir/libs/*" -Dzookeeper.sasl.client.username=sandbox-zookeeper org.apache.ambari.logsearch.solr.AmbariSolrCloudCLI ${1+"$@"} 

edit /usr/lib/ambari-infra-solr/bin/solr

#add lines below to bottom of script 
ADDITIONAL_CMD_OPTS="$ADDITIONAL_CMD_OPTS -Dzookeeper.sasl.client.username=hcedhp02-zookeeper" 
launch_solr "$FG" "$ADDITIONAL_CMD_OPTS"

These services will now restart correctly and use your custom zookeeper principal name for the client connection.