TEZ-4725: Fix flaky tests in recovery, history-parser, and MRR integration suites#510
Open
maheshrajus wants to merge 1 commit into
Open
TEZ-4725: Fix flaky tests in recovery, history-parser, and MRR integration suites#510maheshrajus wants to merge 1 commit into
maheshrajus wants to merge 1 commit into
Conversation
|
🎊 +1 overall
This message was automatically generated. |
|
💔 -1 overall
This message was automatically generated. |
|
💔 -1 overall
This message was automatically generated. |
|
🎊 +1 overall
This message was automatically generated. |
Contributor
Author
|
@abstractdog @ayushtkn |
|
🎊 +1 overall
This message was automatically generated. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
TEZ-4725: Fix flaky tests in recovery, history-parser, and MRR integration suites
Root causes and fixes:
TestAMRecoveryAggregationBroadcast.testMapJoinTemporalFailure (race condition)
waitForVertexSucceeded() helper that polls DAGClient.getVertexStatus()
every 500ms (up to 60s) until the target vertices reach SUCCEEDED state.
killing the AM, ensuring the recovery log assertions always see the
expected counts.
DAGClientRPCImpl / TezClientUtils: port out of range:-1 (YARN-808 gap)
but the AM has not yet bound its RPC listener. The existing guard only
checked rpcPort==0 (protobuf default), so rpcPort==-1 reached
NetUtils.createSocketAddrForHost(), which threw
IllegalArgumentException: port out of range:-1.
rpcPort <= 0 guard
TezClient.waitNonSessionTillReady(): infinite loop on slow CI
0 or -1, getAMStatus() catches the resulting ServiceException/IOException
and returns INITIALIZING. Without a deadline the loop spun forever.
which already represents "how long the client will wait for the AM to
become contactable". On expiry a TezException is thrown with the
application ID.
TestHistoryParser.testParserWithSuccessfulJob (empty zip entry)
all vertex/task events are flushed to ATS. ATSImportTool.download() did
not close ZipOutputStream in its finally block (only FileOutputStream was
closed), leaving a truncated zip with empty entries on the disk.
TestMRRJobsDAGApi.testMultipleMRRSleepJobViaSession (DAG SUCCEEDED ≠ AM READY)
transitioned back to READY; there is a short cleanup window. On slow CI
the subsequent getAppMasterStatus() call returned RUNNING instead of READY.
the test waits for the actual state transition.
TestMRRJobsDAGApi: all @test(timeout=60000) increased to 120000
TEZ_SESSION_CLIENT_TIMEOUT_SECS (120s).