@yadir Aguilar Few things: The screenshot "memory.png" is showing the GC log of HMaster process and not for the Ambari Metrics Collector process. The GC log file for AMS will be this one "/var/log/ambari-metrics-collector/collector-gc.logxxxxxxxx" . The "pause.png" screenshot shows some INFO messages and the JVMUtil pause messages are mostly concerned when they are WARN level. INFO messages about the pause can keep appearing in the logs. So you should do this to actually see the Pauses which needs to be reviewed. # cat /var/log/ambari-metrics-collector/hbase-ams-master-xxxxxxxxx.log | grep -i pause | grep -i WARN General Recommendation (trial basis) Also if you are running AMS in Embedded Mode default settigns then i will suggest you to try increasing the AMS collector heap size from default 512 MB to a bit high value lik2 1G to 2G and then restart the AMS Collector again. Similarly try increasing the HMaster memory to something around 2G to 4G and see if it helps. The parameters can be found here: in ambari UI "ams-env" --> "metrics_collector_heapsize" "ams-hbase-env" --> "hbase_master_heapsize" For More accurate Tuning Recommendations (data needed) For more accurate tuning of AMS service you may need to collect some additional details like the output fo the following API calls and the current memory usage: 1. The JSON response from the following API calls to see the uni queue metrics and hosts, to understand the load on AMS. http://<ams-host>:6188/ws/v1/timeline/metrics/metadata http://<ams-host>:6188/ws/v1/timeline/metrics/hosts 2. Current memory usages (either complete GC logs HMaster /var/log/ambari-metrics-collector/gc.log-xxxxxx and for AMS collector GC log : /var/log/ambari-metrics-collector/collector-gc.logxxxxxxxx ) 3. The output of the AMS HMaster jmx call: AMS HBase jmx Snapshot - http://<METRICS_COLLECTOR_HOST>:61310/jmx 4. The AMS HMaster UI output to understand the "Region Count" and "StoreFile Count" http://<METRICS_COLLECTOR_HOST>:61310 5. AMS collector and HMaster GC complete logs. 6. AMS Configurations: # tar czhfv /tmp/ams_collector_etc_$(hostname)_$(date +"%Y%m%d%H%M%S").tar.gz /etc/ambari-metrics-collector/ # tar czhfv /tmp/ams_hmaster_etc_$(hostname)_$(date +"%Y%m%d%H%M%S").tar.gz /etc/ams-hbase/ . ... View more

@Wayne Pakkala Your query looks Duplicate to other HCC Thread: https://community.hortonworks.com/questions/215099/where-are-the-tutorial-users-or-how-do-i-create-th.html?childToView=215100#answer-215100 Can you please close one of the HCC Thread and continue on one? Answer from other thread: If you are talking about the users like "maria_dev","raj_ops" etc then those users can be found on HDP Sandbox they are already created and available. You can get more detail about those users and their credentials here: https://hortonworks.com/tutorial/learning-the-ropes-of-the-hortonworks-sandbox/ Please install HDP Sandbox and you can find these users. Also check the Ambari UI Ambari UI --> Admin(drop down top right corner) --> Manage Ambari --> Users . Using terminal : (SSH port 2222 must be used) Or use http://localhost:4200 # ssh root@127.0.0.1 -p 2222 Enter Password: hadoop [raj_ops@sandbox ~]$ id uid=1024(raj_ops) gid=1024(raj_ops) groups=1024(raj_ops) [raj_ops@sandbox ~]$ exit logout [root@sandbox ~]# su - maria_dev [maria_dev@sandbox ~]$ id uid=1023(maria_dev) gid=1023(maria_dev) groups=1023(maria_dev) . ... View more

@yadir Aguilar What you posted does not look like an error. Can you please provide more details like the UI screenshot where you see this message? Or if you are using Hive View then can you please share the complete hive view log/ambari-server.log /var/log/ambari-server/hive-next-view/hive-view.log /var/log/ambari-server/hive20-view/hive20-view.log /var/log/ambari-server/ambari-server.log . ... View more

@Michael Bronson By default the NMAUDIT and RMAUDIT files will be using the "DailyRollingFileAppender" hence in a day the file size might vary and as soon as the date changes then Log will be rotated "rm-audit.log" and "nm-audit.log" so you might see file size varying. If you want a fix size for log rotation then you will need RollingFileAppender (instead of DailyRollingFileAppender) as i see that you have already implemented the same on other thread. https://community.hortonworks.com/questions/214983/how-to-in-force-the-audit-logs-in-order-to-test-th.html?childToView=214988#comment-214988 # Audit logging for ResourceManager rm.audit.logger=${hadoop.root.logger} log4j.logger.org.apache.hadoop.yarn.server.resourcemanager.RMAuditLogger=${rm.audit.logger} log4j.additivity.org.apache.hadoop.yarn.server.resourcemanager.RMAuditLogger=false #log4j.appender.RMAUDIT=org.apache.log4j.DailyRollingFileAppender log4j.appender.RMAUDIT.File=${yarn.log.dir}/rm-audit.log log4j.appender.RMAUDIT.layout=org.apache.log4j.PatternLayout log4j.appender.RMAUDIT.layout.ConversionPattern=%d{ISO8601} %p %c{2}: %m%n #log4j.appender.RMAUDIT.DatePattern=.yyyy-MM-dd log4j.appender.RMAUDIT=org.apache.log4j.RollingFileAppender log4j.appender.RMAUDIT.MaxBackupIndex=5 log4j.appender.RMAUDIT.MaxFileSize=1MB . RollingFileAppender provides options like MaxFileSize to control the log rotation by file size. ... View more

@Michael Bronson Please try running some "Yarn Service Checks" from ambari UI 10-20 times and keep checking the "Active Resource Manager" logs "rm-audit.log" You can also try running the following ambari API call to trigger the Yarn Service check in a for look 20-50 times and monitor the audit log growth. # curl -sH "X-Requested-By: ambari" -u admin:admin -X POST -d '{"RequestInfo":{"context":"YARN Service Check","command":"YARN_SERVICE_CHECK"},"Requests/resource_filters":[{"service_name":"YARN"}]}' http://hdfcluster1.example.com:8080/api/v1/clusters/TestCluster/requests . ... View more