<?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: Ambari view tuning guide? in Archives of Support Questions (Read Only)</title>
    <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/Ambari-view-tuning-guide/m-p/96165#M9512</link>
    <description>&lt;P&gt;Thanks &lt;A rel="user" href="https://community.cloudera.com/users/32/paul.html" nodeid="32"&gt;@Paul Codding&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;A target="_blank" href="http://docs.hortonworks.com/HDPDocuments/Ambari-2.1.2.0/bk_ambari_views_guide/content/ch_using_ambari_views.html"&gt;Link&lt;/A&gt;&lt;/P&gt;&lt;P&gt;It is recommended to increase the amount of memory available to the Ambari Server when deploying multiple views. As each view requires it's own memory footprint, increasing the Ambari Server's maximum allocable memory to 4096MB will help support multiple deployed views and concurrent use.&lt;/P&gt;&lt;P&gt;Edit the &lt;CODE&gt;/var/lib/ambari-server/ambari-env.sh&lt;/CODE&gt; file on the Ambari Server and replace the value of the &lt;CODE&gt;-Xmx2048m&lt;/CODE&gt; argument with &lt;CODE&gt;-Xmx4096m -XX:PermSize=128m -XX:MaxPermSize=128m&lt;/CODE&gt;. Then, restart the Ambari Server to apply this change:&lt;/P&gt;</description>
    <pubDate>Wed, 28 Oct 2015 03:59:04 GMT</pubDate>
    <dc:creator>nsabharwal</dc:creator>
    <dc:date>2015-10-28T03:59:04Z</dc:date>
    <item>
      <title>Ambari view tuning guide?</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/Ambari-view-tuning-guide/m-p/96164#M9511</link>
      <description>&lt;P&gt;Where can I find the ambari views tuning guide?&lt;/P&gt;</description>
      <pubDate>Fri, 16 Sep 2022 09:46:20 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/Ambari-view-tuning-guide/m-p/96164#M9511</guid>
      <dc:creator>nsabharwal</dc:creator>
      <dc:date>2022-09-16T09:46:20Z</dc:date>
    </item>
    <item>
      <title>Re: Ambari view tuning guide?</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/Ambari-view-tuning-guide/m-p/96165#M9512</link>
      <description>&lt;P&gt;Thanks &lt;A rel="user" href="https://community.cloudera.com/users/32/paul.html" nodeid="32"&gt;@Paul Codding&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;A target="_blank" href="http://docs.hortonworks.com/HDPDocuments/Ambari-2.1.2.0/bk_ambari_views_guide/content/ch_using_ambari_views.html"&gt;Link&lt;/A&gt;&lt;/P&gt;&lt;P&gt;It is recommended to increase the amount of memory available to the Ambari Server when deploying multiple views. As each view requires it's own memory footprint, increasing the Ambari Server's maximum allocable memory to 4096MB will help support multiple deployed views and concurrent use.&lt;/P&gt;&lt;P&gt;Edit the &lt;CODE&gt;/var/lib/ambari-server/ambari-env.sh&lt;/CODE&gt; file on the Ambari Server and replace the value of the &lt;CODE&gt;-Xmx2048m&lt;/CODE&gt; argument with &lt;CODE&gt;-Xmx4096m -XX:PermSize=128m -XX:MaxPermSize=128m&lt;/CODE&gt;. Then, restart the Ambari Server to apply this change:&lt;/P&gt;</description>
      <pubDate>Wed, 28 Oct 2015 03:59:04 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/Ambari-view-tuning-guide/m-p/96165#M9512</guid>
      <dc:creator>nsabharwal</dc:creator>
      <dc:date>2015-10-28T03:59:04Z</dc:date>
    </item>
    <item>
      <title>Re: Ambari view tuning guide?</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/Ambari-view-tuning-guide/m-p/96166#M9513</link>
      <description>&lt;P&gt;Hi &lt;A rel="user" href="https://community.cloudera.com/users/140/nsabharwal.html" nodeid="140"&gt;@Neeraj Sabharwal&lt;/A&gt; we are intorducing Ambari views fro the first time. We have ~50 active users who are using Hue daily and migrating all the users to Views now. I would like to get some recommendations for Ambari Views configuration. Currently we have Hive, Tez &amp;amp; File System views on a dedicated Ambari views server with 16 GB of memory allocated and permgen of 512 MB. Please provide your inputs. Thanks in advance !!&lt;/P&gt;</description>
      <pubDate>Fri, 03 Jun 2016 22:57:00 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/Ambari-view-tuning-guide/m-p/96166#M9513</guid>
      <dc:creator>sparepally1</dc:creator>
      <dc:date>2016-06-03T22:57:00Z</dc:date>
    </item>
    <item>
      <title>Re: Ambari view tuning guide?</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/Ambari-view-tuning-guide/m-p/96167#M9514</link>
      <description>&lt;P&gt;We are also migrating to ambari views with starting active users of 50 and can go upto 100 by the year end. We are configuring hive view, files view, pig view, Tez view. &lt;/P&gt;</description>
      <pubDate>Sat, 04 Jun 2016 01:53:54 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/Ambari-view-tuning-guide/m-p/96167#M9514</guid>
      <dc:creator>2rajukv</dc:creator>
      <dc:date>2016-06-04T01:53:54Z</dc:date>
    </item>
    <item>
      <title>Re: Ambari view tuning guide?</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/Ambari-view-tuning-guide/m-p/96168#M9515</link>
      <description>&lt;P&gt;please refer &lt;A href="http://docs.hortonworks.com/HDPDocuments/Ambari-2.1.2.0/bk_ambari_views_guide/content/_reverse_proxy_views.html" target="_blank"&gt;http://docs.hortonworks.com/HDPDocuments/Ambari-2.1.2.0/bk_ambari_views_guide/content/_reverse_proxy_views.html&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 07 Jun 2016 01:40:45 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/Ambari-view-tuning-guide/m-p/96168#M9515</guid>
      <dc:creator>kjilla</dc:creator>
      <dc:date>2016-06-07T01:40:45Z</dc:date>
    </item>
  </channel>
</rss>

