Hi @Michael Bronson , Yeah exactly thats what i did. ... View more

@Michael Bronson Can you please mark correct answer if you are satisfied with my answer? ... View more

@Michael Bronson Yes, as of now Ambari 2.7 is the latest version and it is certified to use with HDP 3.0 If it answer my question then please mark this as correct answer. ... View more

@Michael Bronson For Kafka its not even enabled GC logging I guess - hence you can ignore that part. but you can set that like below. In kafka-env section, From export KAFKA_KERBEROS_PARAMS="-Djavax.security.auth.useSubjectCredsOnly=false to: export KAFKA_KERBEROS_PARAMS="-Djavax.security.auth.useSubjectCredsOnly=false -XX:+PrintGCTimeStamps -XX:+UseGCLogFileRotation -XX:NumberOfGCLogFiles=5 -XX:GCLogFileSize=2M If you satisfied with answers then please mark my comment as correct answer. this will help others as well. ... View more

@Jay , thank you so much we do the testing and they are fine , now we need to do the steps VIA API ... View more

Hi @Michael Bronson, sorry i missed the comment as you didnt tag me by name. you can follow the same method with --action=set . you can refer to this Good document by apache : https://cwiki.apache.org/confluence/display/AMBARI/Modify+configurations#Modifyconfigurations-Editconfigurationusingconfigs.py Please Mark answer as resolved if this helped you 🙂 ... View more

@Michael Bronson ZooKeeper needs an odd number of hosts so it can build a quorum. A 3 node cluster can survive the loss of 1 node. It will fail if there is a simultaneous loss of 2 nodes (for example a node fails during an upgrade). If zookeeper goes down the brokers will not operate. Designing a ZooKeeper deployment explains: "For the ZooKeeper service to be active, there must be a majority of non-failing machines that can communicate with each other. To create a deployment that can tolerate the failure of F machines, you should count on deploying 2xF+1 machines. Thus, a deployment that consists of three machines can handle one failure, and a deployment of five machines can handle two failures. Note that a deployment of six machines can only handle two failures since three machines is not a majority. For this reason, ZooKeeper deployments are usually made up of an odd number of machines." ... View more

@Geoffrey , any suggestion how to ciontinue from this point ? ... View more

@Michael Bronson the practice of using 2x memory for swap space is very old and out of date. It was usefull on a time when systems had as an example 256MB of ram and does not apply as of today. Using a swap space in hadoop nodes, worker or masters is not recommended because it will not prevent you from having issues even when the swap space memory is being used due to RAM hitting the threshold defined with the swapiness parameters. In the refered post: "If you have the need to use more memory, or expect to need more, than the amount of RAM which has been purchased. And can accept severe degradation in failure. In this case you would need a lot of swap configured. Your better off buying the right amount of memory." "The fear with disabling swap on masters is that an OOM (out of memory) event could affect cluster availability. But that will still happen even with swap configured, it just will take slightly longer. Good administrator/operator practices would be to monitor RAM availability, then fix any issues before running out of memory" If you really have a requirement to have it configured on your master nodes, then just set the swap as you like, example a 1/4 of total system memory and set the swappiness value to 0. ... View more