@Manoj690  Going through your logs I can see that the Namenode is in SAFE MODE, and in this case it won't allow you to change the status of any file in the cluster including the logs. 2019-08-22 12:31:01,376 [server.Accumulo] INFO : Attempting to talk to zookeeper 2019-08-22 12:31:01,681 [server.Accumulo] INFO : ZooKeeper connected and initialized, attempting to talk to HDFS 2019-08-22 12:31:01,946 [server.Accumulo] WARN : Waiting for the NameNode to leave safemode 2019-08-22 12:31:01,946 [server.Accumulo] INFO : Backing off due to failure; current sleep period is 1.0 seconds 2019-08-22 12:31:02,950 [server.Accumulo] WARN : Waiting for the NameNode to leave safemode 2019-08-22 12:31:02,950 [server.Accumulo] INFO : Backing off due to failure; current sleep period is 2.0 seconds 2019-08-22 12:31:04,954 [server.Accumulo] WARN : Waiting for the NameNode to leave safemode   To resolve the issue can you do the following as hdfs user $ hdfs dfsadmin -safemode get Safe mode is OFF The above is the desired output but if you get ON then proceed like below First backup your FS Image & Edits $ hdfs dfsadmin -saveNamespace   Then exit the safemode $ hdfs dfsadmin -safemode leave Once successful then revalidate $ hdfs dfsadmin -safemode get   This time it should be off and you can now successfully restart the failed services from Ambari everything should succeed HTH ... View more

@Ray Teruya OutOfMemoryError is a subclass of java.lang.VirtualMachineError; it’s thrown by the JVM when it encounters a problem related to utilizing resources. More specifically, the error occurs when the JVM spent too much time performing Garbage Collection and was only able to reclaim very little heap space. According to Java docs, by default, the JVM is configured to throw this error if the Java process spends more than 98% of its time doing GC and when only less than 2% of the heap is recovered in each run. In other words, this means that our application has exhausted nearly all the available memory and the Garbage Collector has spent too much time trying to clean it and failed repeatedly. In this situation, users experience extreme slowness of the application. Certain operations, which usually complete in milliseconds, take more time to complete. This is because the CPU is using its entire capacity for Garbage Collection and hence cannot perform any other tasks. Solution: On HDP 3.x & 2.6.x depending on the memory available to the cluster check and increase the below You could throttle it to 2048 MB HTH ... View more

@Matas Mockus This is a duplicate posting I responded to the initial thread. http://community.hortonworks.com/answers/249938/view.html Did you check the response please either merge or delete this post as it will be difficult to follow the 2 threads! ... View more

@Matas Mockus The below error comes up in your ambari-agent logs , can you check your hiveServer2 hostname, you might need to adjust in Ambari UI Execute['! beeline -u 'jdbc:hive2://:10000/;transportMode=binary;auth=noSasl' It should look like this Execute['! beeline -u 'jdbc:hive2://{some_host_FQDN}:10000/;transportMode=binary;auth=noSasl' Please try that and revert ... View more