(kafka) branch 3.9 updated: KAFKA-17422: Adding copySegmentLatch countdown after expiration task is over (#17012)

[sh...@apache.org]

This is an automated email from the ASF dual-hosted git repository.

showuon pushed a commit to branch 3.9
in repository https://gitbox.apache.org/repos/asf/kafka.git


The following commit(s) were added to refs/heads/3.9 by this push:
     new a19792fbd74 KAFKA-17422: Adding copySegmentLatch countdown after expiration task is over (#17012)
a19792fbd74 is described below

commit a19792fbd747e761ba02a4b62a12f9ffc4340715
Author: Arpit Goyal <go...@gmail.com>
AuthorDate: Wed Aug 28 08:14:57 2024 +0530

    KAFKA-17422: Adding copySegmentLatch countdown after expiration task is over (#17012)
    
    The given test took 5 seconds as the logic was waiting completely for 5 seconds for the expiration task to be completed. Adding copySegmentLatch countdown after expiration task is over
    
    Reviewers: Luke Chen <sh...@gmail.com>, Chia-Ping Tsai <ch...@gmail.com>
---
 core/src/test/java/kafka/log/remote/RemoteLogManagerTest.java | 1 +
 1 file changed, 1 insertion(+)

diff --git a/core/src/test/java/kafka/log/remote/RemoteLogManagerTest.java b/core/src/test/java/kafka/log/remote/RemoteLogManagerTest.java
index 302b6adfe48..d6d2ff0ecbb 100644
--- a/core/src/test/java/kafka/log/remote/RemoteLogManagerTest.java
+++ b/core/src/test/java/kafka/log/remote/RemoteLogManagerTest.java
@@ -2133,6 +2133,7 @@ public class RemoteLogManagerTest {
                 // wait until copy thread has started copying segment data
                 copySegmentDataLatch.await();
                 expirationTask.cleanupExpiredRemoteLogSegments();
+                copyLogSegmentLatch.countDown();
             } catch (RemoteStorageException | ExecutionException | InterruptedException e) {
                 throw new RuntimeException(e);
             }