<?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: Starting Services after Rebooting OS in Archives of Support Questions (Read Only)</title>
    <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/Starting-Services-after-Rebooting-OS/m-p/168532#M25134</link>
    <description>&lt;P&gt;&lt;A rel="user" href="https://community.cloudera.com/users/200/awatson.html" nodeid="200"&gt;@Andrew Watson&lt;/A&gt;
&lt;/P&gt;&lt;P&gt;Pls check this -&lt;/P&gt;&lt;P&gt;&lt;A href="https://community.hortonworks.com/questions/4940/hdp-os-upgradepatching-best-practices.html" target="_blank"&gt;https://community.hortonworks.com/questions/4940/hdp-os-upgradepatching-best-practices.html&lt;/A&gt;&lt;/P&gt;&lt;P&gt;The hadoop services are intentionally made chkconfig off to not to get started after server reboots. This is generally avoided to make sure the services starts in the series they are defined. If not so then there might be communication issue between services.&lt;/P&gt;</description>
    <pubDate>Thu, 14 Apr 2016 01:54:12 GMT</pubDate>
    <dc:creator>sshimpi</dc:creator>
    <dc:date>2016-04-14T01:54:12Z</dc:date>
    <item>
      <title>Starting Services after Rebooting OS</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/Starting-Services-after-Rebooting-OS/m-p/168531#M25133</link>
      <description>&lt;P&gt;Hi All,&lt;/P&gt;&lt;P&gt;After applying OS patches to Data nodes, the servers must be rebooted. Once the servers are rebooted, the hadoop services running on them are not automatically coming up. You have to manually go into Ambari and tell the services to start on that host. &lt;/P&gt;&lt;P&gt;What are some best practices and recommendations as to how to automatically bring up the hadoop services after an OS reboot?&lt;/P&gt;</description>
      <pubDate>Thu, 14 Apr 2016 01:53:25 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/Starting-Services-after-Rebooting-OS/m-p/168531#M25133</guid>
      <dc:creator>awatson</dc:creator>
      <dc:date>2016-04-14T01:53:25Z</dc:date>
    </item>
    <item>
      <title>Re: Starting Services after Rebooting OS</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/Starting-Services-after-Rebooting-OS/m-p/168532#M25134</link>
      <description>&lt;P&gt;&lt;A rel="user" href="https://community.cloudera.com/users/200/awatson.html" nodeid="200"&gt;@Andrew Watson&lt;/A&gt;
&lt;/P&gt;&lt;P&gt;Pls check this -&lt;/P&gt;&lt;P&gt;&lt;A href="https://community.hortonworks.com/questions/4940/hdp-os-upgradepatching-best-practices.html" target="_blank"&gt;https://community.hortonworks.com/questions/4940/hdp-os-upgradepatching-best-practices.html&lt;/A&gt;&lt;/P&gt;&lt;P&gt;The hadoop services are intentionally made chkconfig off to not to get started after server reboots. This is generally avoided to make sure the services starts in the series they are defined. If not so then there might be communication issue between services.&lt;/P&gt;</description>
      <pubDate>Thu, 14 Apr 2016 01:54:12 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/Starting-Services-after-Rebooting-OS/m-p/168532#M25134</guid>
      <dc:creator>sshimpi</dc:creator>
      <dc:date>2016-04-14T01:54:12Z</dc:date>
    </item>
    <item>
      <title>Re: Starting Services after Rebooting OS</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/Starting-Services-after-Rebooting-OS/m-p/168533#M25135</link>
      <description>&lt;P&gt;below is one example - &lt;A href="https://docs.hortonworks.com/HDPDocuments/HDP2/HDP-2.3.0/bk_upgrading_hdp_manually/content/start-hadoop-20.html"&gt;https://docs.hortonworks.com/HDPDocuments/HDP2/HDP-2.3.0/bk_upgrading_hdp_manually/content/start-hadoop-20.html&lt;/A&gt;&lt;/P&gt;&lt;TABLE style="font-size: 15px;"&gt;&lt;TBODY&gt;&lt;TR&gt;&lt;TH&gt;Warning&lt;/TH&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD&gt;Before you start HDFS on an HA system you must start the ZooKeeper service. If you do not start the ZKFC, there can be failures.&lt;/TD&gt;&lt;/TR&gt;&lt;/TBODY&gt;&lt;/TABLE&gt;</description>
      <pubDate>Thu, 14 Apr 2016 02:00:27 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/Starting-Services-after-Rebooting-OS/m-p/168533#M25135</guid>
      <dc:creator>sshimpi</dc:creator>
      <dc:date>2016-04-14T02:00:27Z</dc:date>
    </item>
    <item>
      <title>Re: Starting Services after Rebooting OS</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/Starting-Services-after-Rebooting-OS/m-p/168534#M25136</link>
      <description>&lt;P&gt;&lt;A rel="user" href="https://community.cloudera.com/users/200/awatson.html" nodeid="200"&gt;@Andrew Watson&lt;/A&gt;&lt;/P&gt;&lt;P&gt;You could put up a script to check for the services and restart them for this period. But as &lt;A rel="user" href="https://community.cloudera.com/users/2648/sshimpi.html" nodeid="2648"&gt;@Sagar Shimpi&lt;/A&gt; pointed out, you might have to take care of some of the services.&lt;/P&gt;&lt;P&gt;Also ensure that dependent HDP dependent components like Java / Python are not upgraded during this patching. If they are to be, it needs to be tested ahead.&lt;/P&gt;</description>
      <pubDate>Thu, 14 Apr 2016 02:10:25 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/Starting-Services-after-Rebooting-OS/m-p/168534#M25136</guid>
      <dc:creator>vpoornalingam</dc:creator>
      <dc:date>2016-04-14T02:10:25Z</dc:date>
    </item>
  </channel>
</rss>

