HBase 2.1.x had been EOL before hadoop 3.3.0 was out... HBASE-22953 is only landed on branch-2.3+.
The client API between 2.1.x and 2.4.x should be very small, and you can access a 2.4.x cluster with 2.1.x client, usually. And typically there is no problem when rolling upgrading a cluster from 2.1.x to 2.4.x, the only thing is you need to upgrade master first, as we changed the storage layout for procedure data, and once master is upgraded, there is no simple way to downgrade. Thanks. Michael Wohlwend <mich...@fantasymail.de> 于2021年12月21日周二 22:46写道： > > Am Dienstag, 21. Dezember 2021, 04:00:01 CET schrieb Bryan Beaudreault: > > I have to agree anecdotally that when I first upgraded to 3.3.1 I got a > > bunch of NoSuchMethodExceptions (or similar). This was a while ago so I > > don't have specifics. It was an easy fix -- recompile hbase with > > -Dhadoop.version=3.3.1. > > > just tried it, it seems not that easy :-) > > I downloaded hbase 2.1.4 and executed (with newest maven) : > > mvn package -DskipTests -Dhadoop.profile=3.0 -Dhadoop-three.version=3.3.1 > > This breaks with a bunch of errors and exceptions after some time, which I > find > a little strange, since I thought the source vom apache just builds through > with maven. > > Same result with hbase 2.1.9 > > On the other hand, hbase 2.4.8 builds without errors. > > Now, without much reading, I don't know how much work it is to upgrade to > hbase 2.4.8 (api changes, so fix working software...) > > I'm still wondering why the build is not working. Something is too old? > > thanks for helping, > Michael > > > >
