-
Notifications
You must be signed in to change notification settings - Fork 440
TEZ-4420: Upgrade to Hadoop 3.3.4 #213
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
|
The test issues seem to be related to mockito java.lang.NoClassDefFoundError: org/mockito/stubbing/Answer |
|
You are checking the wrong build result, mockito also was a problem, but we upgraded it and the build result got sorted. Check the result here of this test in the latest build: There is an exception: |
|
hadoop 3.3.4 cuts jax.rs from the dependency graph |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We have now conflicts with the master branch. Can try with 3.3.4, which is released now to see if things work here now
|
@abstractdog Can we upgrade hadoop to 3.3.4? I have tested hive maser with hadoop3.3.4(apache/hive#3578) , and if i change tez's hadoop dependency to 3.3.4, everything looks ok. |
|
yes, let me check this PR and have some test coverage |
9161201 to
0d2e7ed
Compare
This comment was marked as outdated.
This comment was marked as outdated.
ayushtkn
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We got a clean build, the Jackson stuff changes in hadoop, got us sorted. :-)
LGTM
|
Great! If this PR is merged into Tez 0.10.2, then we can continue to upgrade hadoop version in hive repo. |
|
Can this be merged to unblock other upgrades? |
let me take a look soon |
|
It was Hive that I thought was blocked. It would still be nice to get this moved on but I guess if it's not blocking anything then it's not as urgent. |
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
|
we are nearing code freeze for 3.3.5 btw; if there is some final blocker to upgrade, now is the time to identify it |
|
Hi @ayushtkn @abstractdog @pjfanning @steveloughran Since this PR has been stale for a month, just following up to check whether I can help in validating any other test scenarios for the upgrade. Or if not, are we good to merge this PR ? |
|
Hi @ayushtkn @abstractdog @pjfanning @steveloughran, I am driving the hive-3.2.0 release in Open Source for which we have decided to upgrade to hadoop 3.3.4. But since Tez 0.10.2 is using hadoop-3.3.1 there can be some integration issues for this stack. I know that we are currently discussing hadoop-3.3.5 release but it would take at least a couple of months to get a stable release candidate for the same which would also require a lot of testing. This will be a blocker for the 3.2.0 release and since we have started to plan our tasks around this release, I was proposing to make a Tez release 0.10.3 where we can have this hadoop version upgraded to 3.3.4. This would insure that we can start working on the 3.2.0 without any blockers. Please share your thoughts on the same. I am open to discussing this release further. Thanks, |
|
I was talking about The failure was flagged here: |
|
Hi @ayushtkn I am familiar with this error. This happens because Tez 0.10.1 is using Hadoop 3.1.3 which in turn uses jetty 9.3* which does not have this method but when we upgrade to Hadoop 3.3.4 it uses this method. So basically I am saying that if we maintained the same version of Hadoop in Hive and Tez, this would not have been the issue. Having said this, I will make sure that the 0.10.3 is validated on clusters including unit tests Ayush. |
|
3.3.4 is the one where we fixed the tez incompatibilities for you 🙂 i plan to cut the 3.3.5 rc0 this week but it's a test of the rc process (x86 and arm) rather than something we intend to bring to a vote. it'd be good to test hive and tez with the rc to see if we have caused any regressions, as now will be the time to fix. there's been a lot of dependency updates to stop CVEs, but we've left alone the ones we know cause problems downstream (jackson is on a cve-fixed 2.12.x release) |
|
@steveloughran So do you think having a new Tez release with 3.3.4 should help or not? |
|
@abstractdog @steveloughran Can you please look into this? |
|
3.3.4 should be good; if not try with a 3.3.5 snapshot (build yourself) and see if that fixes things. i'd suggest going with 3.3.4 if it works, so the 3.3.5 release isn't a blocker. you can do an upgrade after |
|
I believe from tez->hadoop point of view, we usually rely only on precommit testing (including lots of minicluster tests) TestRecovery passed locally, I'm restarting precommit tests can someone approve this PR? @rbalamohan , @jteagles |
6319f6e to
e83c806
Compare
|
💔 -1 overall
This message was automatically generated. |
|
@rbalamohan @jteagles Can you please approve this PR. Also @abstractdog are we going with the tez 0.10.3 release which will have hadoop 3.3.4. |
|
@abstractdog Upgrade to Hadoop 3.3.4 is failing tests in Tez as follows : It is failing with timed out waiting for Mini DFS Cluster to start. |
|
Any reason in the logs for the cluster not coming up? |
|
@steveloughran Not checked it yet. Will check and let you know |
|
@steveloughran @abstractdog Apologizes for getting back late. Was involved in Hive test case fixes for branch-3. Seems like this issue was intermittent. Now I see this test passing, tried it 3-4 times. Attached the snippet. We can merge this to master. +1 from my side. Tested it extensively on my local as well as on a local cluster. |
|
I see these test failures in the tez-tests module. Currently fixing it @abstractdog @steveloughran This issue comes when PowerMock library conflicts with Mockito as described here https://stackoverflow.com/questions/71973762/java-lang-nosuchmethoderror-org-mockito-answers-getlorg-mockito-stubbing-answ |
|
@abstractdog Can you please cherry-pick this commit I did in my forked branch - 944476e this will fix the tests. I cannot push these changes to your branch. |
|
Got the issue : When I debugged this tests I found this : When it tries to get from the cachedVertexStatus (size : 0) the status of vertexName "sleep" it does not find any entry and therefore returns null. And hence, @abstractdog Can you please check this from your end, maybe we need to add some config to have an entry for the Sleep vertex name in cachedVertexStatus |
|
where is the mockito ref coming from? as I don't see why it should be exported -if it is, then that is something to cut back on |
|
@amanraj2520: thanks for your work so far, if you have the bandwidth to drive this, please open a PR and assign TEZ-4420 to yourself btw: yeah, tez 0.10.3 can contain this change, I think once this is merged and we merge some other fixes, we can go for a release (in a couple of weeks/months) |
|
@abstractdog Sure assigning TEZ-4420 to myself |
|
closing this as final PR was #272 |






No description provided.