Fix MLTransactionMetadataStore.update async fail - #14532
Conversation
…eader fails sporadically
|
/pulsarbot run-failure-checks |
|
/pulsarbot run-failure-checks |
|
/pulsarbot run-failure-checks |
|
@shibd Instead of re-running checks, you will need to close and reopen this PR so that the build picks up the fix #14524 . There was a thread leak which also caused a memory leak and made the tests run extremely slow because of reduced working memory (which leads to very frequent GCs and a lot of pauses). |
@lhotari Thank your reply, I see that CI has passed. |
great! |
…eader fails sporadically (#14532) ### Motivation #14525 When update states is `TxnStatus.COMMITTED`, Not correctly `completableFuture.complete`. ### Modifications - When update states is `TxnStatus.COMMITTED`, Add return to ending. Avoid direct calls `completableFuture.complete` from other logic. ### Documentation - [x ] `no-need-doc` (cherry picked from commit c15d0ef)
…eader fails sporadically (#14532) ### Motivation #14525 When update states is `TxnStatus.COMMITTED`, Not correctly `completableFuture.complete`. ### Modifications - When update states is `TxnStatus.COMMITTED`, Add return to ending. Avoid direct calls `completableFuture.complete` from other logic. ### Documentation - [x ] `no-need-doc` (cherry picked from commit c15d0ef)
…eader fails sporadically (apache#14532) ### Motivation apache#14525 When update states is `TxnStatus.COMMITTED`, Not correctly `completableFuture.complete`. ### Modifications - When update states is `TxnStatus.COMMITTED`, Add return to ending. Avoid direct calls `completableFuture.complete` from other logic. ### Documentation - [x ] `no-need-doc`
Motivation
#14525
When update states is
TxnStatus.COMMITTED, Not correctlycompletableFuture.complete.Modifications
TxnStatus.COMMITTED, Add return to ending. Avoid direct callscompletableFuture.completefrom other logic.Documentation
no-need-doc