chore(hbase): Add 2.6.4, remove 2.6.2

[NickLarsenNZ]

Part of stackabletech/docker-images#1372

[adwk67]

This is just a blocker until I've checked all the URLs resolve properly and that the corresponding patches - mainly the new one for 2.6.4 - all work (as they are not easily testable with integration tests).

[NickLarsenNZ]

This is just a blocker until I've checked all the URLs resolve properly and that the corresponding patches - mainly the new one for 2.6.4 - all work (as they are not easily testable with integration tests).

No problem. I copied them from 2.6.3 without much of a deeper look.

Can you think of a way we can automate this somehow?
Or at least provide some guidance on how someone else can test the same thing (we can add more instructions to the hbase bump template).

[adwk67]

This is just a blocker until I've checked all the URLs resolve properly and that the corresponding patches - mainly the new one for 2.6.4 - all work (as they are not easily testable with integration tests).

No problem. I copied them from 2.6.3 without much of a deeper look.

Can you think of a way we can automate this somehow? Or at least provide some guidance on how someone else can test the same thing (we can add more instructions to the hbase bump template).

It's basically opening up the UI and clicking on the server URLs to make sure none of them are dead:

and

The URLs are found in hbase-site.xml with hostname and info.port

<property>
  <name>hbase.master.hostname</name>
  <value>172.19.0.6</value>
</property>
<property>
  <name>hbase.master.info.port</name>
  <value>30965</value>
</property>

<property>
  <name>hbase.unsafe.regionserver.hostname</name>
  <value>172.19.0.3</value>
</property>
<property>
  <name>hbase.regionserver.info.port</name>
  <value>32269</value>
</property>

Or use the listener services:

N.B. the links use the info.port, but the link shows the port. I think that's actually intentional, but will check.