<?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 How to stop HAWQ segment from the terminal? in Archives of Support Questions (Read Only)</title>
    <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/How-to-stop-HAWQ-segment-from-the-terminal/m-p/119224#M51051</link>
    <description>&lt;P&gt;I am trying to restart the HAWQ service using Ambari. However, for some reason the segments are not Stopping and the operation is timing out after 600 seconds. Is there a way to stop the segments and/or restart them from the terminal?&lt;/P&gt;&lt;P&gt;I am using HDP 2.4.2 and HAWQ 2.0.1&lt;/P&gt;</description>
    <pubDate>Mon, 09 Jan 2017 03:46:28 GMT</pubDate>
    <dc:creator>p_routray</dc:creator>
    <dc:date>2017-01-09T03:46:28Z</dc:date>
    <item>
      <title>How to stop HAWQ segment from the terminal?</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/How-to-stop-HAWQ-segment-from-the-terminal/m-p/119224#M51051</link>
      <description>&lt;P&gt;I am trying to restart the HAWQ service using Ambari. However, for some reason the segments are not Stopping and the operation is timing out after 600 seconds. Is there a way to stop the segments and/or restart them from the terminal?&lt;/P&gt;&lt;P&gt;I am using HDP 2.4.2 and HAWQ 2.0.1&lt;/P&gt;</description>
      <pubDate>Mon, 09 Jan 2017 03:46:28 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/How-to-stop-HAWQ-segment-from-the-terminal/m-p/119224#M51051</guid>
      <dc:creator>p_routray</dc:creator>
      <dc:date>2017-01-09T03:46:28Z</dc:date>
    </item>
    <item>
      <title>Re: How to stop HAWQ segment from the terminal?</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/How-to-stop-HAWQ-segment-from-the-terminal/m-p/119225#M51052</link>
      <description>&lt;P&gt;waiting for server to shut down........................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................... failed
20170108:19:26:51:311785 hawq_stop:datanode01-dev:gpadmin-[INFO]:-pg_ctl: server does not shut down
20170108:19:26:51:311785 hawq_stop:datanode01-dev:gpadmin-[ERROR]:-Segment stop failed, exit
20170108:19:36:55:313713 hawq_stop:datanode01-dev:gpadmin-[INFO]:-Prepare to do 'hawq stop'
20170108:19:36:55:313713 hawq_stop:datanode01-dev:gpadmin-[INFO]:-You can find log in:
20170108:19:36:55:313713 hawq_stop:datanode01-dev:gpadmin-[INFO]:-/home/gpadmin/hawqAdminLogs/hawq_stop_20170108.log
20170108:19:36:55:313713 hawq_stop:datanode01-dev:gpadmin-[INFO]:-GPHOME is set to:
20170108:19:36:55:313713 hawq_stop:datanode01-dev:gpadmin-[INFO]:-/usr/local/hawq/.
20170108:19:36:55:313713 hawq_stop:datanode01-dev:gpadmin-[DEBUG]:-Current user is 'gpadmin'
20170108:19:36:55:313713 hawq_stop:datanode01-dev:gpadmin-[DEBUG]:-Parsing config file:
20170108:19:36:55:313713 hawq_stop:datanode01-dev:gpadmin-[DEBUG]:-/usr/local/hawq/./etc/hawq-site.xml
20170108:19:36:55:313713 hawq_stop:datanode01-dev:gpadmin-[INFO]:-Stop hawq with args: ['stop', 'segment']
20170108:19:36:55:313713 hawq_stop:datanode01-dev:gpadmin-[INFO]:-Stop hawq segment
waiting for server to shut down........................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................... failed
20170108:19:46:56:313713 hawq_stop:datanode01-dev:gpadmin-[INFO]:-pg_ctl: server does not shut down
20170108:19:46:56:313713 hawq_stop:datanode01-dev:gpadmin-[ERROR]:-Segment stop failed, exit
20170108:19:48:12:314792 hawq_stop:datanode01-dev:gpadmin-[INFO]:-Prepare to do 'hawq stop'
20170108:19:48:12:314792 hawq_stop:datanode01-dev:gpadmin-[INFO]:-You can find log in:
20170108:19:48:12:314792 hawq_stop:datanode01-dev:gpadmin-[INFO]:-/home/gpadmin/hawqAdminLogs/hawq_stop_20170108.log
20170108:19:48:12:314792 hawq_stop:datanode01-dev:gpadmin-[INFO]:-GPHOME is set to:
20170108:19:48:12:314792 hawq_stop:datanode01-dev:gpadmin-[INFO]:-/usr/local/hawq/.
20170108:19:48:12:314792 hawq_stop:datanode01-dev:gpadmin-[DEBUG]:-Current user is 'gpadmin'
20170108:19:48:12:314792 hawq_stop:datanode01-dev:gpadmin-[DEBUG]:-Parsing config file:
20170108:19:48:12:314792 hawq_stop:datanode01-dev:gpadmin-[DEBUG]:-/usr/local/hawq/./etc/hawq-site.xml
20170108:19:48:12:314792 hawq_stop:datanode01-dev:gpadmin-[INFO]:-Stop hawq with args: ['stop', 'segment']
20170108:19:48:12:314792 hawq_stop:datanode01-dev:gpadmin-[INFO]:-Stop hawq segment
waiting for server to shut down..........................................20170108:19:48:51:314926 hawq_stop:datanode01-dev:gpadmin-[INFO]:-Prepare to do 'hawq stop'
20170108:19:48:51:314926 hawq_stop:datanode01-dev:gpadmin-[INFO]:-You can find log in:
20170108:19:48:51:314926 hawq_stop:datanode01-dev:gpadmin-[INFO]:-/home/gpadmin/hawqAdminLogs/hawq_stop_20170108.log
20170108:19:48:51:314926 hawq_stop:datanode01-dev:gpadmin-[INFO]:-GPHOME is set to:
20170108:19:48:51:314926 hawq_stop:datanode01-dev:gpadmin-[INFO]:-/usr/local/hawq/.
20170108:19:48:51:314926 hawq_stop:datanode01-dev:gpadmin-[INFO]:-Stop hawq with args: ['stop', 'segment']
.......20170108:19:48:58:314926 hawq_stop:datanode01-dev:gpadmin-[INFO]:-Stop hawq segment
waiting for server to shut down........................................................................................................................................................................................[root@datanode01-dev ~]#&lt;/P&gt;</description>
      <pubDate>Mon, 09 Jan 2017 03:51:44 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/How-to-stop-HAWQ-segment-from-the-terminal/m-p/119225#M51052</guid>
      <dc:creator>p_routray</dc:creator>
      <dc:date>2017-01-09T03:51:44Z</dc:date>
    </item>
    <item>
      <title>Re: How to stop HAWQ segment from the terminal?</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/How-to-stop-HAWQ-segment-from-the-terminal/m-p/119226#M51053</link>
      <description>&lt;P&gt;Hi Piyush , &lt;/P&gt;&lt;P&gt;You can login to the hawq segment server and can stop the segment with the following &lt;/P&gt;&lt;P&gt;ssh hawq-segment&lt;/P&gt;&lt;P&gt;su - gpadmin &lt;/P&gt;&lt;P&gt;source /usr/local/hawq/greenplum_path.sh&lt;/P&gt;&lt;P&gt;hawq stop segment &lt;/P&gt;&lt;P&gt;If it still not getting stopped ,look for the orphan segment process in the server and manually kill it (ps -ef|grep postgres ) .It would be good to the  check segment logs in the server for the details .&lt;/P&gt;&lt;P&gt;Thanks &lt;/P&gt;&lt;P&gt;Pratheesh Nair&lt;/P&gt;</description>
      <pubDate>Mon, 09 Jan 2017 03:51:55 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/How-to-stop-HAWQ-segment-from-the-terminal/m-p/119226#M51053</guid>
      <dc:creator>pratheeshnair37</dc:creator>
      <dc:date>2017-01-09T03:51:55Z</dc:date>
    </item>
    <item>
      <title>Re: How to stop HAWQ segment from the terminal?</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/How-to-stop-HAWQ-segment-from-the-terminal/m-p/119227#M51054</link>
      <description>&lt;P&gt;Killing the process(es) helped. Thanks!&lt;/P&gt;</description>
      <pubDate>Mon, 09 Jan 2017 04:04:51 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/How-to-stop-HAWQ-segment-from-the-terminal/m-p/119227#M51054</guid>
      <dc:creator>p_routray</dc:creator>
      <dc:date>2017-01-09T04:04:51Z</dc:date>
    </item>
    <item>
      <title>Re: How to stop HAWQ segment from the terminal?</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/How-to-stop-HAWQ-segment-from-the-terminal/m-p/119228#M51055</link>
      <description>&lt;P&gt;Hi Piyush,&lt;/P&gt;&lt;P&gt;Additionally, you can try using the following commands:&lt;/P&gt;&lt;P&gt;hawq stop segment -M fast&lt;/P&gt;&lt;P&gt;If the above does not work stop with option "immediate" should kill the process for you:&lt;/P&gt;&lt;P&gt;hawq stop segment -M immediate&lt;/P&gt;&lt;P&gt;If you do not provide any option with -M the stop/shutdown uses "smart" mode which does not really kill anything if there is any active connection or query.&lt;/P&gt;</description>
      <pubDate>Sat, 18 Feb 2017 01:16:59 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/How-to-stop-HAWQ-segment-from-the-terminal/m-p/119228#M51055</guid>
      <dc:creator>gbrahmi</dc:creator>
      <dc:date>2017-02-18T01:16:59Z</dc:date>
    </item>
  </channel>
</rss>

