[jira] [Updated] (HUDI-5488) Make sure Discrupt queue start first, then insert records

["Ethan Guo (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/HUDI-5488?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ethan Guo updated HUDI-5488:
----------------------------
    Fix Version/s: 0.13.0

> Make sure Discrupt queue start first, then insert records
> ---------------------------------------------------------
>
>                 Key: HUDI-5488
>                 URL: https://issues.apache.org/jira/browse/HUDI-5488
>             Project: Apache Hudi
>          Issue Type: Bug
>          Components: core
>            Reporter: Hui An
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 0.13.0
>
>
> We must to make sure to set up Disruptor's queue first, then producer can insert records to the queue. But currently we have no idea which thread start first, so this pr tries to fix it.
> CompletableFuture<Void> consuming = startConsumingAsync();
> CompletableFuture<Void> producing = startProducingAsync();
> Also, I think the test TestDisruptorExecutionInSpark#testExecutor and TestDisruptorMessageQueue#testRecordReading failures relate to this bug.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)