<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>question Re: how to limit the logs rotation under /var/log/ambari-metrics-collector in Archives of Support Questions (Read Only)</title>
    <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/how-to-limit-the-logs-rotation-under-var-log-ambari-metrics/m-p/208671#M79167</link>
    <description>&lt;P&gt;&lt;A rel="user" href="https://community.cloudera.com/users/26229/uribarih.html" nodeid="26229"&gt;@Michael Bronson&lt;/A&gt;&lt;/P&gt;&lt;P&gt;The Logs (like collector-gc.log Or gc.log)  produced by the JVM following &lt;STRONG&gt;are not controlled by the Log4j&lt;/STRONG&gt; So there is no way to control them or their rotations using Log4j &lt;/P&gt;&lt;PRE&gt;-Xloggc:/var/log/ambari-metrics-collector/collector-gc.log-201806070708
-Xloggc:/var/log/ambari-metrics-collector/gc.log-201806070708&lt;/PRE&gt;&lt;P&gt;In order to control those GC log files you will need to rely on the OS utilities like&lt;STRONG&gt; "logrotate" &lt;/STRONG&gt;or "cronjobs" to clear those logs.&lt;/P&gt;&lt;P&gt;.&lt;/P&gt;&lt;P&gt;JVM provides some options like "-XX:+UseGCLogFileRotation" however they are responsible for rotating the GC logs when the &lt;STRONG&gt;JVM process is keep running&lt;/STRONG&gt;.  &lt;/P&gt;&lt;P&gt;However You can however control the AMS component logs like HMaster logs or AMS collector logs using the log4j settings &lt;/P&gt;&lt;P&gt;like:&lt;/P&gt;&lt;PRE&gt;log4j.appender.file.MaxFileSize={{ams_log_max_backup_size}}MB
log4j.appender.file.MaxBackupIndex={{ams_log_number_of_backup_files}}&lt;/PRE&gt;&lt;P&gt;.&lt;/P&gt;</description>
    <pubDate>Thu, 07 Jun 2018 14:42:13 GMT</pubDate>
    <dc:creator>jsensharma</dc:creator>
    <dc:date>2018-06-07T14:42:13Z</dc:date>
    <item>
      <title>how to limit the logs rotation under /var/log/ambari-metrics-collector</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/how-to-limit-the-logs-rotation-under-var-log-ambari-metrics/m-p/208669#M79165</link>
      <description>&lt;P&gt;how to limit the logs rotation under &lt;STRONG&gt;/var/log/ambari-metrics-collector&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;so logs will be only on the last month&lt;/P&gt;&lt;P&gt;under /var/log/ambari-metrics-collector we see logs from Jul , but we want only logs until month ( logs rotation no longer then month )&lt;/P&gt;&lt;PRE&gt;otal 7277584
-rw-r--r--. 1 ams  hadoop     13794 Jul 13  2017 collector-gc.log-201707131628
-rw-r--r--. 1 ams  hadoop      1430 Jul 13  2017 gc.log-201707131628
-rw-r--r--  1 ams  hadoop 126748287 Aug 14  2017 collector-gc.log-201707160637
-rw-r--r--  1 ams  hadoop 178518767 Aug 28  2017 gc.log-201707160637
-rw-r--r--. 1 ams  hadoop  83886155 Sep 14  2017 ambari-metrics-collector.log.30
-rw-r--r--  1 ams  hadoop  94522724 Sep 17  2017 collector-gc.log-201708280731
-rw-r--r--  1 ams  hadoop 128748829 Sep 17  2017 gc.log-201708280731
-rw-r--r--  1 ams  hadoop      2850 Sep 18  2017 collector-gc.log-201709181421
-rw-r--r--  1 ams  hadoop     60849 Sep 18  2017 gc.log-201709181421
-rw-r--r--  1 ams  hadoop      3517 Sep 18  2017 collector-gc.log-201709181424
-rw-r--r--  1 ams  hadoop     82562 Sep 18  2017 gc.log-201709181424
-rw-r--r--  1 ams  hadoop 117495363 Oct 19  2017 collector-gc.log-201709181508
-rw-r--r--  1 ams  hadoop 164381669 Oct 19  2017 gc.log-201709181508
-rw-r--r--  1 ams  hadoop     16634 Oct 19  2017 collector-gc.log-201710191738
-rw-r--r--  1 ams  hadoop     46149 Oct 19  2017 gc.log-201710191738
-rw-r--r--  1 ams  hadoop   7052909 Oct 23  2017 collector-gc.log-201710200633
-rw-r--r--  1 ams  hadoop  13763796 Oct 23  2017 gc.log-201710200633
-rw-r--r--  1 ams  hadoop    632288 Oct 23  2017 collector-gc.log-201710231021
-rw-r--r--  1 ams  hadoop   1048289 Oct 23  2017 gc.log-201710231021
-rw-r--r--  1 ams  hadoop   1927171 Oct 24  2017 collector-gc.log-201710231649
-rw-r--r--  1 ams  hadoop   3473874 Oct 24  2017 gc.log-201710231649
-rw-r--r--. 1 ams  hadoop 268435531 Oct 28  2017 hbase-ams-master-master02.sys654.com.log.5
-rw-r--r--  1 ams  hadoop  83886115 Nov  1  2017 ambari-metrics-collector.log.29
-rw-r--r--  1 ams  hadoop  79689213 Nov 15  2017 collector-gc.log-201710241352
-rw-r--r--  1 ams  hadoop 137289030 Nov 15  2017 gc.log-201710241352
-rw-r--r--  1 ams  hadoop   4736994 Nov 16  2017 collector-gc.log-201711151355
-rw-r--r--  1 ams  hadoop   8037548 Nov 16  2017 gc.log-201711151355
-rw-r--r--  1 ams  hadoop  15168598 Nov 19  2017 collector-gc.log-201711161246
-rw-r--r--  1 ams  hadoop  23919164 Nov 19  2017 gc.log-201711161246
-rw-r--r--  1 ams  hadoop  83720006 Dec  6 16:32 collector-gc.log-201711191241
-rw-r--r--  1 ams  hadoop 139759594 Dec  6 16:35 gc.log-201711191241
-rw-r--r--  1 ams  hadoop  83886082 Dec 17 10:03 ambari-metrics-collector.log.28
-rw-r--r--  1 ams  hadoop 110573406 Dec 25 16:10 collector-gc.log-201712061635
-rw-r--r--  1 ams  hadoop 184118442 Dec 25 16:13 gc.log-201712061635
-rw-r--r--  1 ams  hadoop      1440 Jan  1 04:38 gc.log-201712251613
-rw-r--r--  1 ams  hadoop  39360581 Jan  1 04:40 collector-gc.log-201712251613
-rw-r--r--  1 ams  hadoop      1437 Jan 10 00:03 gc.log-201801021532
-rw-r--r--  1 ams  hadoop  42005865 Jan 10 00:04 collector-gc.log-201801021532
-rw-r--r--  1 ams  hadoop      1439 Jan 10 01:04 gc.log-201801100004
-rw-r--r--  1 ams  hadoop    286342 Jan 10 01:05 collector-gc.log-201801100004
-rw-r--r--  1 ams  hadoop      3637 Jan 10 01:11 gc.log-201801100105
-rw-r--r--  1 ams  hadoop      3085 Jan 10 01:13 collector-gc.log-201801100105
-rw-r--r--  1 ams  hadoop      1437 Jan 10 01:16 gc.log-201801100113
-rw-r--r--  1 ams  hadoop      7230 Jan 10 01:18 collector-gc.log-201801100113
-rw-r--r--  1 ams  hadoop      3636 Jan 10 01:24 gc.log-201801100118
-rw-r--r--  1 ams  hadoop      3085 Jan 10 01:25 collector-gc.log-201801100118
-rw-r--r--  1 ams  hadoop      1438 Jan 10 01:35 gc.log-201801100126
-rw-r--r--  1 ams  hadoop     17357 Jan 10 01:36 collector-gc.log-201801100126&lt;/PRE&gt;</description>
      <pubDate>Tue, 05 Jun 2018 03:13:13 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/how-to-limit-the-logs-rotation-under-var-log-ambari-metrics/m-p/208669#M79165</guid>
      <dc:creator>mike_bronson7</dc:creator>
      <dc:date>2018-06-05T03:13:13Z</dc:date>
    </item>
    <item>
      <title>Re: how to limit the logs rotation under /var/log/ambari-metrics-collector</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/how-to-limit-the-logs-rotation-under-var-log-ambari-metrics/m-p/208670#M79166</link>
      <description>&lt;P&gt;Within Ambari, you can go to the config: Ambari UI --&amp;gt; Ambari Metrics --&amp;gt; Configs --&amp;gt; Advanced ams-log4j&lt;/P&gt;&lt;P&gt;There you should find this property, when being set to something like 31 in combination with a daily rotation you will only keep 1 month of logs:&lt;/P&gt;&lt;P&gt;log4j.appender.file.MaxBackupIndex=31&lt;/P&gt;&lt;P&gt;Or when you configure a monthly rotation, you set the number to 1.&lt;/P&gt;&lt;P&gt;It doesn't delete the existing older log files, you'll have to clean it manually.&lt;/P&gt;</description>
      <pubDate>Thu, 07 Jun 2018 14:18:58 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/how-to-limit-the-logs-rotation-under-var-log-ambari-metrics/m-p/208670#M79166</guid>
      <dc:creator>arald</dc:creator>
      <dc:date>2018-06-07T14:18:58Z</dc:date>
    </item>
    <item>
      <title>Re: how to limit the logs rotation under /var/log/ambari-metrics-collector</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/how-to-limit-the-logs-rotation-under-var-log-ambari-metrics/m-p/208671#M79167</link>
      <description>&lt;P&gt;&lt;A rel="user" href="https://community.cloudera.com/users/26229/uribarih.html" nodeid="26229"&gt;@Michael Bronson&lt;/A&gt;&lt;/P&gt;&lt;P&gt;The Logs (like collector-gc.log Or gc.log)  produced by the JVM following &lt;STRONG&gt;are not controlled by the Log4j&lt;/STRONG&gt; So there is no way to control them or their rotations using Log4j &lt;/P&gt;&lt;PRE&gt;-Xloggc:/var/log/ambari-metrics-collector/collector-gc.log-201806070708
-Xloggc:/var/log/ambari-metrics-collector/gc.log-201806070708&lt;/PRE&gt;&lt;P&gt;In order to control those GC log files you will need to rely on the OS utilities like&lt;STRONG&gt; "logrotate" &lt;/STRONG&gt;or "cronjobs" to clear those logs.&lt;/P&gt;&lt;P&gt;.&lt;/P&gt;&lt;P&gt;JVM provides some options like "-XX:+UseGCLogFileRotation" however they are responsible for rotating the GC logs when the &lt;STRONG&gt;JVM process is keep running&lt;/STRONG&gt;.  &lt;/P&gt;&lt;P&gt;However You can however control the AMS component logs like HMaster logs or AMS collector logs using the log4j settings &lt;/P&gt;&lt;P&gt;like:&lt;/P&gt;&lt;PRE&gt;log4j.appender.file.MaxFileSize={{ams_log_max_backup_size}}MB
log4j.appender.file.MaxBackupIndex={{ams_log_number_of_backup_files}}&lt;/PRE&gt;&lt;P&gt;.&lt;/P&gt;</description>
      <pubDate>Thu, 07 Jun 2018 14:42:13 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/how-to-limit-the-logs-rotation-under-var-log-ambari-metrics/m-p/208671#M79167</guid>
      <dc:creator>jsensharma</dc:creator>
      <dc:date>2018-06-07T14:42:13Z</dc:date>
    </item>
  </channel>
</rss>

