After upgrading from HDP 2.6 to HDP 3.1, all Hbase cluster-members (2 masters, 2 regionservers) are running on hbase-3-1-0-0-78 - 2.0.2.3.1.0.0-78. The cluster seems operational and the existing table can be queried. But the Master has detected "2 nodes with inconsistent version": Region Servers ServerName Start time Last contact Version Requests Per Second Num. Regions hnode6-0 Wed Apr 24 18:07:12 UTC 2019 0 s 2.0.2 0 0 hnode6-1 Wed Apr 24 17:45:51 UTC 2019 1 s 2.0.2 0 3 Total:2 2 nodes with inconsistent version 0 3 Though details on both master and regionservers don't show any difference: Master: HBase Version 2.0.2.3.1.0.0-78, revision= HBase version and revision HBase Compiled Thu Dec 6 13:23:31 UTC 2018, jenkins When HBase version was compiled and by whom HBase Source Checksum 015c34650c163b249d16fc7e496a030e HBase source MD5 checksum Hadoop Version 3.1.1.3.1.0.0-78, revision=e4f82af51faec922b4804d0232a637422ec29e64 Hadoop version and revision Hadoop Compiled 2018-12-06T13:34Z, jenkins When Hadoop version was compiled and by whom Hadoop Source Checksum eab9fa2a6aa38c6362c66d8df75774 Hadoop source MD5 checksum ZooKeeper Client Version 3.4.6-78, revision=-1 ZooKeeper client version and revision Regionserver: HBase Version 2.0.2.3.1.0.0-78, revision= HBase version and revision HBase Compiled Thu Dec 6 13:23:31 UTC 2018, jenkins When HBase version was compiled and by whom HBase Source Checksum 015c34650c163b249d16fc7e496a030e HBase source MD5 checksum Hadoop Version 3.1.1.3.1.0.0-78, revision=e4f82af51faec922b4804d0232a637422ec29e64 Hadoop version and revision Hadoop Compiled 2018-12-06T13:34Z, jenkins When Hadoop version was compiled and by whom Hadoop Source Checksum eab9fa2a6aa38c6362c66d8df75774 Hadoop source MD5 checksum ZooKeeper Client Version 3.4.6-78, revision=-1 ZooKeeper client version and revision ... View more