<?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: Urgent !!! - Presto Query Error: Query exceeded max memory size of 50GB in Support Questions</title>
    <link>https://community.cloudera.com/t5/Support-Questions/Urgent-Presto-Query-Error-Query-exceeded-max-memory-size-of/m-p/167419#M129751</link>
    <description>&lt;P&gt;You can take a look at this post:&lt;/P&gt;&lt;P&gt;&lt;A href="https://community.hortonworks.com/articles/10485/introduction-to-presto.html" target="_blank"&gt;https://community.hortonworks.com/articles/10485/introduction-to-presto.html&lt;/A&gt;&lt;/P&gt;&lt;P&gt;Then let me answer you question:&lt;/P&gt;&lt;P&gt;Q1)How we can come to know what is optimum size of memory/ram allocation.&lt;/P&gt;&lt;P style="margin-left: 20px;"&gt;A) You can get the value from presto UI.&lt;/P&gt;&lt;P&gt;&lt;A href="http://&amp;lt;host-name&amp;gt;:8080/" target="_blank"&gt;http://&amp;lt;host-name&amp;gt;:8080/&lt;/A&gt;&lt;/P&gt;&lt;P&gt;All the queries are listed here. If you click one of them, you can see details , such as peak memory usage.&lt;/P&gt;&lt;P&gt;Q3) Is there any way to restrict user from launching such a huge query or any other preventive approach&lt;/P&gt;&lt;P style="margin-left: 20px;"&gt;A) Yes. &lt;A href="https://community.hortonworks.com/articles/10485/introduction-to-presto.html"&gt;ref url&lt;BR /&gt;&lt;/A&gt;&lt;/P&gt;&lt;P style="margin-left: 20px;"&gt;&lt;A href="https://community.hortonworks.com/articles/10485/introduction-to-presto.html"&gt;&lt;/A&gt;&lt;/P&gt;&lt;P style="margin-left: 20px;"&gt;config.properties example:&lt;/P&gt;&lt;PRE&gt;query.max-memory=30GB
query.max-memory-per-node=5GB&lt;/PRE&gt;</description>
    <pubDate>Tue, 16 Jan 2018 16:22:48 GMT</pubDate>
    <dc:creator>zzeng</dc:creator>
    <dc:date>2018-01-16T16:22:48Z</dc:date>
  </channel>
</rss>

