You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@hudi.apache.org by "hudi-bot (via GitHub)" <gi...@apache.org> on 2025/11/30 06:12:09 UTC

[I] TestDisruptorExecutionInSpark.testExecutor is flaky [hudi]

hudi-bot opened a new issue, #15623:
URL: https://github.com/apache/hudi/issues/15623

   This is an example:
   
   https://dev.azure.com/apache-hudi-ci-org/apache-hudi-ci/_build/results?buildId=13628&view=logs&j=600e7de6-e133-5e69-e615-50ee129b3c08&t=bbbd7bcc-ae73-56b8-887a-cd2d6deaafc7&s=859b8d9a-8fd6-5a5c-6f5e-f84f1990894e
   
   ## JIRA info
   
   - Link: https://issues.apache.org/jira/browse/HUDI-5369
   - Type: Bug
   - Epic: https://issues.apache.org/jira/browse/HUDI-4302
   
   
   ---
   
   
   ## Comments
   
   12/Dec/22 05:33;zhangyue19921010;Hi alexey. Sorry for this issue. Is there any details info for this case?
   Will have a deep look asap;;;


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: commits-unsubscribe@hudi.apache.org.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


Re: [I] TestDisruptorExecutionInSpark.testExecutor is flaky [hudi]

Posted by "nsivabalan (via GitHub)" <gi...@apache.org>.
nsivabalan closed issue #15623: TestDisruptorExecutionInSpark.testExecutor is flaky
URL: https://github.com/apache/hudi/issues/15623


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: commits-unsubscribe@hudi.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


Re: [I] TestDisruptorExecutionInSpark.testExecutor is flaky [hudi]

Posted by "nsivabalan (via GitHub)" <gi...@apache.org>.
nsivabalan commented on issue #15623:
URL: https://github.com/apache/hudi/issues/15623#issuecomment-4795456189

   Triage: this looks **fixed** on master.
   
   The specific flakiness/timeout was tracked under [HUDI-5792](https://issues.apache.org/jira/browse/HUDI-5792) and addressed in PR [#8000](https://github.com/apache/hudi/pull/8000) (commit `ca9dc9751fe0`, Feb 2023), which made `DisruptorMessageQueue.shutdown()` honor thread interrupts with a bounded `queue.shutdown(TIMEOUT_WAITING_SECS, TimeUnit.SECONDS)`. That code is still present in `hudi-common/src/main/java/org/apache/hudi/common/util/queue/DisruptorMessageQueue.java` (lines 150-157). The test was disabled by PR #7946 and re-enabled by the fix; the 2025 test refactor (#18005) kept `testExecutor` enabled with a `@Timeout`. Closing this older flake report seems reasonable — please reopen with a fresh CI link if you can still reproduce on current master.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: commits-unsubscribe@hudi.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org