<?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: Yarn Timeline db consuming 466GB space in Support Questions</title>
    <link>https://community.cloudera.com/t5/Support-Questions/Yarn-Timeline-db-consuming-466GB-space/m-p/140177#M102800</link>
    <description>&lt;P&gt;Thanks It worked. I just want to know if there are any consequences after deleting the&lt;STRONG&gt; leveldb-timeline-store.ldb &lt;/STRONG&gt;directory&lt;STRONG&gt;. &lt;/STRONG&gt;After deleteing content of this directory and restarting timeline server, the contents of this directory regenerated and freed up the space.&lt;STRONG&gt;
&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;We set  “yarn.timeline-service.ttl-ms”
from 267840000000(~443weeks) to 604800000(7 Days) to limit the size of the
leveldb storage, according to hortonworks document.&lt;/P&gt;</description>
    <pubDate>Wed, 27 Jul 2016 19:43:25 GMT</pubDate>
    <dc:creator>anshul_sisodia</dc:creator>
    <dc:date>2016-07-27T19:43:25Z</dc:date>
    <item>
      <title>Yarn Timeline db consuming 466GB space</title>
      <link>https://community.cloudera.com/t5/Support-Questions/Yarn-Timeline-db-consuming-466GB-space/m-p/140175#M102798</link>
      <description>&lt;P&gt;I have a scenario where yarn timeline store db is increasing day by day. In April it was 346GB and now it increased to 466GB and occupying lot of space in /var/opt/hadoop/yarn/timeline.&lt;/P&gt;&lt;P&gt;#   df -h
Filesystem      Size  Used Avail Use% Mounted on
/dev/sda2        30G   11G   18G  37% /
udev            126G  260K  126G   1% /dev
tmpfs           126G     0  126G   0% /dev/shm
/dev/sda5       5.0G  2.5G  2.2G  54% /var
&lt;EM&gt;&lt;STRONG&gt;/dev/sda7       756G  698G   21G  98% /var/opt/&lt;/STRONG&gt;&lt;/EM&gt;
/dev/sdb        2.5T  6.6G  2.3T   1% /data&lt;/P&gt;&lt;P&gt;when i checked disk usage on /var/opt/hadoop/yarn/timeline&lt;/P&gt;&lt;P&gt;du -sh *
466G    leveldb-timeline-store.ldb
40K     timeline-state-store.ldb&lt;/P&gt;&lt;P&gt;I don't know why it is occupying this much of space. What steps do i need to take to make it consume less space.&lt;/P&gt;</description>
      <pubDate>Thu, 21 Jul 2016 17:16:46 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Support-Questions/Yarn-Timeline-db-consuming-466GB-space/m-p/140175#M102798</guid>
      <dc:creator>anshul_sisodia</dc:creator>
      <dc:date>2016-07-21T17:16:46Z</dc:date>
    </item>
    <item>
      <title>Re: Yarn Timeline db consuming 466GB space</title>
      <link>https://community.cloudera.com/t5/Support-Questions/Yarn-Timeline-db-consuming-466GB-space/m-p/140176#M102799</link>
      <description>&lt;P&gt;Yarn timeline store should cleanup old values. Parameters are:&lt;/P&gt;&lt;P&gt;Cleanup cycle ( when he deletes ) &lt;/P&gt;&lt;P&gt;yarn.timeline-service.leveldb-timeline-store.ttl-interval-ms&lt;/P&gt;&lt;P&gt;Time to live ( what to delete )&lt;/P&gt;&lt;P&gt;yarn.timeline-service.ttl-ms&lt;/P&gt;&lt;P&gt;Oh and finally enable the age off&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;yarn.timeline-service.ttl-enable&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="https://docs.hortonworks.com/HDPDocuments/HDP2/HDP-2.3.2/bk_yarn_resource_mgt/content/ref-e54bc3f2-f1bc-4bc6-b6cb-e6337589feb6.1.html" target="_blank"&gt;https://docs.hortonworks.com/HDPDocuments/HDP2/HDP-2.3.2/bk_yarn_resource_mgt/content/ref-e54bc3f2-f1bc-4bc6-b6cb-e6337589feb6.1.html&lt;/A&gt;&lt;/P&gt;&lt;P&gt;I would check those. If you want to clean things you can set that to a low settings and restart. Alternatively you should be able to simply delete the database if you want to its just log information after all. Finally if the parameters are correct and do not work you might want to open a support ticket.&lt;/P&gt;</description>
      <pubDate>Thu, 21 Jul 2016 18:01:41 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Support-Questions/Yarn-Timeline-db-consuming-466GB-space/m-p/140176#M102799</guid>
      <dc:creator>bleonhardi</dc:creator>
      <dc:date>2016-07-21T18:01:41Z</dc:date>
    </item>
    <item>
      <title>Re: Yarn Timeline db consuming 466GB space</title>
      <link>https://community.cloudera.com/t5/Support-Questions/Yarn-Timeline-db-consuming-466GB-space/m-p/140177#M102800</link>
      <description>&lt;P&gt;Thanks It worked. I just want to know if there are any consequences after deleting the&lt;STRONG&gt; leveldb-timeline-store.ldb &lt;/STRONG&gt;directory&lt;STRONG&gt;. &lt;/STRONG&gt;After deleteing content of this directory and restarting timeline server, the contents of this directory regenerated and freed up the space.&lt;STRONG&gt;
&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;We set  “yarn.timeline-service.ttl-ms”
from 267840000000(~443weeks) to 604800000(7 Days) to limit the size of the
leveldb storage, according to hortonworks document.&lt;/P&gt;</description>
      <pubDate>Wed, 27 Jul 2016 19:43:25 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Support-Questions/Yarn-Timeline-db-consuming-466GB-space/m-p/140177#M102800</guid>
      <dc:creator>anshul_sisodia</dc:creator>
      <dc:date>2016-07-27T19:43:25Z</dc:date>
    </item>
    <item>
      <title>Re: Yarn Timeline db consuming 466GB space</title>
      <link>https://community.cloudera.com/t5/Support-Questions/Yarn-Timeline-db-consuming-466GB-space/m-p/140178#M102801</link>
      <description>&lt;P&gt;The main consequences are for running jobs some of which may depend on ats ( too late for that ) and any investigation of performance of old jobs ( which are now gone ) apart from that nothing I would know about. Would be interested to know who set the retention period to 8 years &lt;span class="lia-unicode-emoji" title=":slightly_smiling_face:"&gt;🙂&lt;/span&gt; That doesnt make any sense at all. You could have simply changed that as well he should have cleaned up the data soon as well. Hope that works.&lt;/P&gt;</description>
      <pubDate>Wed, 27 Jul 2016 19:58:48 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Support-Questions/Yarn-Timeline-db-consuming-466GB-space/m-p/140178#M102801</guid>
      <dc:creator>bleonhardi</dc:creator>
      <dc:date>2016-07-27T19:58:48Z</dc:date>
    </item>
    <item>
      <title>Re: Yarn Timeline db consuming 466GB space</title>
      <link>https://community.cloudera.com/t5/Support-Questions/Yarn-Timeline-db-consuming-466GB-space/m-p/140179#M102802</link>
      <description>&lt;P&gt;I made sure that no jobs were running at that time when the deletion happened :). Also I am not sure who set retention period to 8 years, have to check that. &lt;/P&gt;&lt;P&gt;One thing i want to know here, if before deletion, I have would have set the property to 7days and restarted only timeline server, would it remove all the older logs from leveldb and keep logs which are generated in last 7 days? I guess after restarting Yarn, Job history server also resets.. and gets clears at regular intervals.. not sure though!!&lt;/P&gt;</description>
      <pubDate>Wed, 27 Jul 2016 21:37:23 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Support-Questions/Yarn-Timeline-db-consuming-466GB-space/m-p/140179#M102802</guid>
      <dc:creator>anshul_sisodia</dc:creator>
      <dc:date>2016-07-27T21:37:23Z</dc:date>
    </item>
    <item>
      <title>Re: Yarn Timeline db consuming 466GB space</title>
      <link>https://community.cloudera.com/t5/Support-Questions/Yarn-Timeline-db-consuming-466GB-space/m-p/140180#M102803</link>
      <description>&lt;P&gt;yeah if you set it to 7 days he should just start cleaning older values after restart ( potentially after hitting the clean period the interval_ms thing) &lt;/P&gt;</description>
      <pubDate>Thu, 28 Jul 2016 23:20:21 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Support-Questions/Yarn-Timeline-db-consuming-466GB-space/m-p/140180#M102803</guid>
      <dc:creator>bleonhardi</dc:creator>
      <dc:date>2016-07-28T23:20:21Z</dc:date>
    </item>
  </channel>
</rss>

