<?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: strange HBase alert after HDP upgrade 2.2.4 =&amp;gt; 2.3.4 in Archives of Support Questions (Read Only)</title>
    <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/strange-HBase-alert-after-HDP-upgrade-2-2-4-gt-2-3-4/m-p/103415#M25426</link>
    <description>&lt;P&gt;Brilliant &lt;A rel="user" href="https://community.cloudera.com/users/177/pminovic.html" nodeid="177"&gt;@Predrag Minovic&lt;/A&gt; , that solved the issue. Thanks !&lt;/P&gt;</description>
    <pubDate>Mon, 18 Apr 2016 21:45:23 GMT</pubDate>
    <dc:creator>geko</dc:creator>
    <dc:date>2016-04-18T21:45:23Z</dc:date>
    <item>
      <title>strange HBase alert after HDP upgrade 2.2.4 =&gt; 2.3.4</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/strange-HBase-alert-after-HDP-upgrade-2-2-4-gt-2-3-4/m-p/103411#M25422</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;after upgrading HDP from 2.2.4 to 2.3.4.7 using Ambari 2.2.1.1 the service HBase shows a strange alert.&lt;/P&gt;&lt;P&gt;It notifies me about dead region servers, and in detail there shall be "7 out of 5 dead region servers"... hmmmm, really ?!? A total of "5" is correct, this is the number of Regionservers, and they are all up and running (and marked "green" in Ambari itself)&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="3496-hbase-state.png" style="width: 545px;"&gt;&lt;img src="https://community.cloudera.com/t5/image/serverpage/image-id/23645iEF544681254917A4/image-size/medium?v=v2&amp;amp;px=400" role="button" title="3496-hbase-state.png" alt="3496-hbase-state.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="3495-hbase-alert.png" style="width: 494px;"&gt;&lt;img src="https://community.cloudera.com/t5/image/serverpage/image-id/23646i680F7B9D488D4E50/image-size/medium?v=v2&amp;amp;px=400" role="button" title="3495-hbase-alert.png" alt="3495-hbase-alert.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;How to get rid of that wrong alert notification ?!? ...just waiting a couple of days didn't solve the problem &lt;span class="lia-unicode-emoji" title=":winking_face:"&gt;😉&lt;/span&gt;&lt;/P&gt;&lt;P&gt;Thanks, Gerd&lt;/P&gt;</description>
      <pubDate>Mon, 19 Aug 2019 12:07:42 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/strange-HBase-alert-after-HDP-upgrade-2-2-4-gt-2-3-4/m-p/103411#M25422</guid>
      <dc:creator>geko</dc:creator>
      <dc:date>2019-08-19T12:07:42Z</dc:date>
    </item>
    <item>
      <title>Re: strange HBase alert after HDP upgrade 2.2.4 =&gt; 2.3.4</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/strange-HBase-alert-after-HDP-upgrade-2-2-4-gt-2-3-4/m-p/103412#M25423</link>
      <description>&lt;P&gt;HBase ports changed in HDP-2.3.4, details &lt;A href="https://issues.apache.org/jira/browse/HBASE-10123"&gt;here&lt;/A&gt;. And region servers has logical names which include RS port. An example RS name: "sandbox.hortonworks.com,16020,1460965964168". Before, the RS port was 60020, and now it's 16020. So, if you have 5 machines running RS, before and after the upgrade there are 10 RSs  to be taken care of, and in your case HBase master may still think that RS names with 60020 are still being used. Restarting HBase (or just restarting HBase master) is supposed to remove them, and solve your issues. Before and after the restart you can check Regions servers in your Hbase Web UI (HBase --&amp;gt; Quick Links). &lt;/P&gt;&lt;P&gt;&lt;A href="http://sandbox.hortonworks.com:16030/rs-status"&gt;&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Mon, 18 Apr 2016 15:08:13 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/strange-HBase-alert-after-HDP-upgrade-2-2-4-gt-2-3-4/m-p/103412#M25423</guid>
      <dc:creator>pminovic</dc:creator>
      <dc:date>2016-04-18T15:08:13Z</dc:date>
    </item>
    <item>
      <title>Re: strange HBase alert after HDP upgrade 2.2.4 =&gt; 2.3.4</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/strange-HBase-alert-after-HDP-upgrade-2-2-4-gt-2-3-4/m-p/103413#M25424</link>
      <description>&lt;P&gt;Hi &lt;A rel="user" href="https://community.cloudera.com/users/177/pminovic.html" nodeid="177" target="_blank"&gt;@Predrag Minovic&lt;/A&gt; , thanks for answering.&lt;/P&gt;&lt;P&gt;The observation is exactly what is happening here, but even after restarting HBase multiple times this alert doesn't disappear. The output of the Dead Region servers still looks wired, because some of them are multiples and some are even not there =&amp;gt;&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="3498-hbase-regionserver-details.png" style="width: 157px;"&gt;&lt;img src="https://community.cloudera.com/t5/image/serverpage/image-id/23644i7CDA23DE25C4E514/image-size/medium?v=v2&amp;amp;px=400" role="button" title="3498-hbase-regionserver-details.png" alt="3498-hbase-regionserver-details.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;next try ?&lt;/P&gt;</description>
      <pubDate>Mon, 19 Aug 2019 12:07:28 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/strange-HBase-alert-after-HDP-upgrade-2-2-4-gt-2-3-4/m-p/103413#M25424</guid>
      <dc:creator>geko</dc:creator>
      <dc:date>2019-08-19T12:07:28Z</dc:date>
    </item>
    <item>
      <title>Re: strange HBase alert after HDP upgrade 2.2.4 =&gt; 2.3.4</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/strange-HBase-alert-after-HDP-upgrade-2-2-4-gt-2-3-4/m-p/103414#M25425</link>
      <description>&lt;P&gt;Next try: Login as user hdfs, and do "hdfs dfs -ls /apps/hbase/data/WALs". &lt;/P&gt;&lt;UL&gt;&lt;LI&gt;Move all directories (5 of them?) that refer to old port 60020 to a folder under /user/hdfs and restart the HBase master.&lt;/LI&gt;&lt;LI&gt;In the same list, identify any directories having "splitting" in their name. If there are any, check that they contain only one file each, with "meta" in its name. Move all those "splitting" directories to /user/hdfs, and restart HBase.&lt;/LI&gt;&lt;/UL&gt;</description>
      <pubDate>Mon, 18 Apr 2016 17:10:46 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/strange-HBase-alert-after-HDP-upgrade-2-2-4-gt-2-3-4/m-p/103414#M25425</guid>
      <dc:creator>pminovic</dc:creator>
      <dc:date>2016-04-18T17:10:46Z</dc:date>
    </item>
    <item>
      <title>Re: strange HBase alert after HDP upgrade 2.2.4 =&gt; 2.3.4</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/strange-HBase-alert-after-HDP-upgrade-2-2-4-gt-2-3-4/m-p/103415#M25426</link>
      <description>&lt;P&gt;Brilliant &lt;A rel="user" href="https://community.cloudera.com/users/177/pminovic.html" nodeid="177"&gt;@Predrag Minovic&lt;/A&gt; , that solved the issue. Thanks !&lt;/P&gt;</description>
      <pubDate>Mon, 18 Apr 2016 21:45:23 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/strange-HBase-alert-after-HDP-upgrade-2-2-4-gt-2-3-4/m-p/103415#M25426</guid>
      <dc:creator>geko</dc:creator>
      <dc:date>2016-04-18T21:45:23Z</dc:date>
    </item>
  </channel>
</rss>

