<?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 gracefully stop an impalad? in Archives of Support Questions (Read Only)</title>
    <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/How-to-gracefully-stop-an-impalad/m-p/61833#M71326</link>
    <description>&lt;P&gt;Hi mauricio,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Impala currently does not support graceful node decommissioning. We're tracking work on this feature in&amp;nbsp;&lt;A href="https://issues.apache.org/jira/browse/IMPALA-1760" target="_self"&gt;IMPALA-1760&lt;/A&gt;, but we currently&amp;nbsp;are not targeting it for a particular release. Unfortunately that only leaves the option of killing the daemon.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Cheers, Lars&lt;/P&gt;</description>
    <pubDate>Tue, 14 Nov 2017 20:17:43 GMT</pubDate>
    <dc:creator>Lars Volker</dc:creator>
    <dc:date>2017-11-14T20:17:43Z</dc:date>
    <item>
      <title>How to gracefully stop an impalad?</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/How-to-gracefully-stop-an-impalad/m-p/61830#M71325</link>
      <description>&lt;P&gt;We often need to restart a node to do some quick maintenance, such as reconfiguring a disk or&amp;nbsp;changing an&amp;nbsp;OS setting&amp;nbsp;which requires a machine restart.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Also, we use Impala not only for interactive user queries but also for&amp;nbsp;many of our ETL job queries, and these slightly longer queries of course die if a single node processing fragments becomes unavailable, killing the corresponding job, exposing us to data corruption.&amp;nbsp; Therefore&amp;nbsp;we are always forced to pause all our jobs.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I know&amp;nbsp;we can gracefully decommission a node, but&amp;nbsp;it can take hours to move all the dfs data out and then back in, so not worth it when trying to do a quick restart.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;So is there a way (via CM, shell or API) to tell an impalad to simply stop taking new fragments in preparation for a restart? (we can also easily remove from haproxy so it doesn't take new queries as coordinator).&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;thanks!&lt;/P&gt;</description>
      <pubDate>Fri, 16 Sep 2022 12:31:18 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/How-to-gracefully-stop-an-impalad/m-p/61830#M71325</guid>
      <dc:creator>mauricio</dc:creator>
      <dc:date>2022-09-16T12:31:18Z</dc:date>
    </item>
    <item>
      <title>Re: How to gracefully stop an impalad?</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/How-to-gracefully-stop-an-impalad/m-p/61833#M71326</link>
      <description>&lt;P&gt;Hi mauricio,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Impala currently does not support graceful node decommissioning. We're tracking work on this feature in&amp;nbsp;&lt;A href="https://issues.apache.org/jira/browse/IMPALA-1760" target="_self"&gt;IMPALA-1760&lt;/A&gt;, but we currently&amp;nbsp;are not targeting it for a particular release. Unfortunately that only leaves the option of killing the daemon.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Cheers, Lars&lt;/P&gt;</description>
      <pubDate>Tue, 14 Nov 2017 20:17:43 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/How-to-gracefully-stop-an-impalad/m-p/61833#M71326</guid>
      <dc:creator>Lars Volker</dc:creator>
      <dc:date>2017-11-14T20:17:43Z</dc:date>
    </item>
  </channel>
</rss>

