<?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: *Closed*: Cloudbreak on Azure: Linux kernel version and impact on kerberizing in Archives of Support Questions (Read Only)</title>
    <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/Closed-Cloudbreak-on-Azure-Linux-kernel-version-and-impact/m-p/213010#M72169</link>
    <description>&lt;A rel="user" href="https://community.cloudera.com/users/3069/anaghaakhanolkar.html" nodeid="3069"&gt;@Airawat&lt;/A&gt;&lt;P&gt;Have you had the chance to have a look at this one? Thanks!&lt;/P&gt;</description>
    <pubDate>Tue, 12 Dec 2017 21:53:37 GMT</pubDate>
    <dc:creator>darvasip</dc:creator>
    <dc:date>2017-12-12T21:53:37Z</dc:date>
    <item>
      <title>*Closed*: Cloudbreak on Azure: Linux kernel version and impact on kerberizing</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/Closed-Cloudbreak-on-Azure-Linux-kernel-version-and-impact/m-p/213007#M72166</link>
      <description>&lt;P&gt;Hello,&lt;BR /&gt; &lt;BR /&gt;&lt;STRONG&gt;Issue:&lt;/STRONG&gt;&lt;BR /&gt;Around mid-November 2017, ran into an issue with datanodes not coming up, and namenode therefore not coming out of safe node when we kerberized (MIT kerberos KDC) a cluster after we provisioned via Cloudbreak.  &lt;BR /&gt;&lt;BR /&gt;&lt;STRONG&gt;Reference:&lt;BR /&gt;&lt;/STRONG&gt;&lt;A href="https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fissues.apache.org%2Fjira%2Fbrowse%2FHDFS-12029&amp;amp;data=02%7C01%7Cankhanol%40microsoft.com%7C86914eae0a894a014f3608d52ddbcb5c%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636465344403831206&amp;amp;sdata=6vWAxspOUR4g9xiBMs7DgR3uBXfB72GK%2BVE%2B3wKOEhE%3D&amp;amp;reserved=0"&gt;&lt;/A&gt;&lt;A href="https://issues.apache.org/jira/browse/HDFS-12029" target="_blank"&gt;https://issues.apache.org/jira/browse/HDFS-12029&lt;/A&gt;&lt;BR /&gt;&lt;A href="https://access.redhat.com/errata/RHBA-2017:1674"&gt;&lt;/A&gt;&lt;A href="https://access.redhat.com/errata/RHBA-2017:1674" target="_blank"&gt;https://access.redhat.com/errata/RHBA-2017:1674&lt;/A&gt;&lt;BR /&gt;&lt;A href="https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcommunity.hortonworks.com%2Farticles%2F109940%2Fafter-os-patching-all-the-datanodes-nodes-are-up-b.html&amp;amp;data=02%7C01%7Cankhanol%40microsoft.com%7C86914eae0a894a014f3608d52ddbcb5c%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636465344403831206&amp;amp;sdata=VZRW71Qros3L%2F%2F%2FuAjYL51QtlSkCCM8oVmZ1FhED6NM%3D&amp;amp;reserved=0"&gt;&lt;/A&gt;&lt;A href="https://community.hortonworks.com/articles/109940/after-os-patching-all-the-datanodes-nodes-are-up-b.html" target="_blank"&gt;https://community.hortonworks.com/articles/109940/after-os-patching-all-the-datanodes-nodes-are-up-b.html&lt;/A&gt;&lt;BR /&gt;&lt;STRONG&gt;&lt;A href="https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcommunity.hortonworks.com%2Farticles%2F109940%2Fafter-os-patching-all-the-datanodes-nodes-are-up-b.html&amp;amp;data=02%7C01%7Cankhanol%40microsoft.com%7C86914eae0a894a014f3608d52ddbcb5c%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636465344403831206&amp;amp;sdata=VZRW71Qros3L%2F%2F%2FuAjYL51QtlSkCCM8oVmZ1FhED6NM%3D&amp;amp;reserved=0"&gt;&lt;BR /&gt;&lt;/A&gt;&lt;A href="https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcommunity.hortonworks.com%2Farticles%2F109940%2Fafter-os-patching-all-the-datanodes-nodes-are-up-b.html&amp;amp;data=02%7C01%7Cankhanol%40microsoft.com%7C86914eae0a894a014f3608d52ddbcb5c%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636465344403831206&amp;amp;sdata=VZRW71Qros3L%2F%2F%2FuAjYL51QtlSkCCM8oVmZ1FhED6NM%3D&amp;amp;reserved=0"&gt;&lt;/A&gt;&lt;/STRONG&gt;&lt;STRONG&gt;Temporary Fix:&lt;BR /&gt;&lt;/STRONG&gt;&lt;A href="https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcommunity.hortonworks.com%2Farticles%2F109940%2Fafter-os-patching-all-the-datanodes-nodes-are-up-b.html&amp;amp;data=02%7C01%7Cankhanol%40microsoft.com%7C86914eae0a894a014f3608d52ddbcb5c%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636465344403831206&amp;amp;sdata=VZRW71Qros3L%2F%2F%2FuAjYL51QtlSkCCM8oVmZ1FhED6NM%3D&amp;amp;reserved=0"&gt;&lt;/A&gt;Hortonworks support was consulted, and they applied a temporary fix:&lt;BR /&gt;Updated hadoop-env.sh configs in HDFS configs in ambari as follows:&lt;/P&gt;&lt;P&gt;Original entry:&lt;/P&gt;&lt;PRE&gt;export HADOOP_OPTS="-Djava.net.preferIPv4Stack=true
${HADOOP_OPTS}"&lt;/PRE&gt;&lt;P&gt;With fix:&lt;/P&gt;&lt;PRE&gt;export HADOOP_OPTS="-Djava.net.preferIPv4Stack=true -Xss1280k ${HADOOP_OPTS}”&lt;/PRE&gt;&lt;P&gt;Restarted services and we were good to go.&lt;BR /&gt;&lt;BR /&gt;&lt;STRONG&gt;Strategic solution:&lt;/STRONG&gt;&lt;BR /&gt;Upgrade the underlying OS image to a version that includes a patch.&lt;BR /&gt;3.10.0-514.26.2.el7.x86_64
version, per the support engineer&lt;/P&gt;&lt;P&gt;Reporting this since an upgrade is being worked, should have done it earlier &lt;span class="lia-unicode-emoji" title=":disappointed_face:"&gt;😞&lt;/span&gt;&lt;/P&gt;&lt;P&gt;@pdarvasi&lt;/P&gt;</description>
      <pubDate>Mon, 04 Dec 2017 00:33:13 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/Closed-Cloudbreak-on-Azure-Linux-kernel-version-and-impact/m-p/213007#M72166</guid>
      <dc:creator>Indra</dc:creator>
      <dc:date>2017-12-04T00:33:13Z</dc:date>
    </item>
    <item>
      <title>Re: *Closed*: Cloudbreak on Azure: Linux kernel version and impact on kerberizing</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/Closed-Cloudbreak-on-Azure-Linux-kernel-version-and-impact/m-p/213008#M72167</link>
      <description>&lt;A rel="user" href="https://community.cloudera.com/users/3069/anaghaakhanolkar.html" nodeid="3069" target="_blank"&gt;@Airawat&lt;/A&gt;&lt;P&gt;I've just double-checked the new Cloudbreak 1.16.5 version in Marketplace and it seems to have the correct version:&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="43853-cb-uname.png" style="width: 802px;"&gt;&lt;img src="https://community.cloudera.com/t5/image/serverpage/image-id/16526iE1FF3DABE7305E00/image-size/medium?v=v2&amp;amp;px=400" role="button" title="43853-cb-uname.png" alt="43853-cb-uname.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;Could You please verify? Thanks! &lt;/P&gt;</description>
      <pubDate>Sun, 18 Aug 2019 03:42:43 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/Closed-Cloudbreak-on-Azure-Linux-kernel-version-and-impact/m-p/213008#M72167</guid>
      <dc:creator>darvasip</dc:creator>
      <dc:date>2019-08-18T03:42:43Z</dc:date>
    </item>
    <item>
      <title>Re: *Closed*: Cloudbreak on Azure: Linux kernel version and impact on kerberizing</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/Closed-Cloudbreak-on-Azure-Linux-kernel-version-and-impact/m-p/213009#M72168</link>
      <description>&lt;P&gt;@pdarvasi&lt;BR /&gt;Will try out and get back to you.  Thanks so much!&lt;/P&gt;</description>
      <pubDate>Wed, 06 Dec 2017 23:17:15 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/Closed-Cloudbreak-on-Azure-Linux-kernel-version-and-impact/m-p/213009#M72168</guid>
      <dc:creator>Indra</dc:creator>
      <dc:date>2017-12-06T23:17:15Z</dc:date>
    </item>
    <item>
      <title>Re: *Closed*: Cloudbreak on Azure: Linux kernel version and impact on kerberizing</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/Closed-Cloudbreak-on-Azure-Linux-kernel-version-and-impact/m-p/213010#M72169</link>
      <description>&lt;A rel="user" href="https://community.cloudera.com/users/3069/anaghaakhanolkar.html" nodeid="3069"&gt;@Airawat&lt;/A&gt;&lt;P&gt;Have you had the chance to have a look at this one? Thanks!&lt;/P&gt;</description>
      <pubDate>Tue, 12 Dec 2017 21:53:37 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/Closed-Cloudbreak-on-Azure-Linux-kernel-version-and-impact/m-p/213010#M72169</guid>
      <dc:creator>darvasip</dc:creator>
      <dc:date>2017-12-12T21:53:37Z</dc:date>
    </item>
    <item>
      <title>Re: *Closed*: Cloudbreak on Azure: Linux kernel version and impact on kerberizing</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/Closed-Cloudbreak-on-Azure-Linux-kernel-version-and-impact/m-p/213011#M72170</link>
      <description>&lt;P&gt;&lt;A rel="user" href="https://community.cloudera.com/users/10827/pdarvasi.html" nodeid="10827"&gt;@pdarvasi&lt;/A&gt; - testing it today.&lt;/P&gt;</description>
      <pubDate>Wed, 13 Dec 2017 00:46:44 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/Closed-Cloudbreak-on-Azure-Linux-kernel-version-and-impact/m-p/213011#M72170</guid>
      <dc:creator>Indra</dc:creator>
      <dc:date>2017-12-13T00:46:44Z</dc:date>
    </item>
    <item>
      <title>Re: *Closed*: Cloudbreak on Azure: Linux kernel version and impact on kerberizing</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/Closed-Cloudbreak-on-Azure-Linux-kernel-version-and-impact/m-p/213012#M72171</link>
      <description>&lt;P&gt;&lt;A rel="user" href="https://community.cloudera.com/users/10827/pdarvasi.html" nodeid="10827"&gt;@pdarvasi&lt;/A&gt;:&lt;BR /&gt;(1) Availability set (1 for multiple host groups - masters): Works fine&lt;BR /&gt;(2) Linux kernel version: is the one in your screenshot - version with patch&lt;BR /&gt;(3) Kerberos enabled post-provisioning against MIT Kerberos KDC: No issues &lt;BR /&gt;(4) Kerberos enabled at provision time with new MIT Kerberos KDC: Did not complete in 12 hours..lots of alerts, install pending, and services in invalid state and unable to start, Ambari version could not be determined...will open a separate post&lt;/P&gt;</description>
      <pubDate>Thu, 14 Dec 2017 13:45:21 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/Closed-Cloudbreak-on-Azure-Linux-kernel-version-and-impact/m-p/213012#M72171</guid>
      <dc:creator>Indra</dc:creator>
      <dc:date>2017-12-14T13:45:21Z</dc:date>
    </item>
    <item>
      <title>Re: *Closed*: Cloudbreak on Azure: Linux kernel version and impact on kerberizing</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/Closed-Cloudbreak-on-Azure-Linux-kernel-version-and-impact/m-p/213013#M72172</link>
      <description>&lt;P&gt;&lt;A rel="user" href="https://community.cloudera.com/users/3069/anaghaakhanolkar.html" nodeid="3069"&gt;@Airawat&lt;/A&gt; If you consider your original question answered, would you please consider accepting the answer? Thanks!&lt;/P&gt;</description>
      <pubDate>Fri, 15 Dec 2017 21:27:11 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/Closed-Cloudbreak-on-Azure-Linux-kernel-version-and-impact/m-p/213013#M72172</guid>
      <dc:creator>darvasip</dc:creator>
      <dc:date>2017-12-15T21:27:11Z</dc:date>
    </item>
  </channel>
</rss>

