GrantPSpencer opened a new issue, #2872: URL: https://github.com/apache/helix/issues/2872
### Describe the bug When a write occurs, ZkBucketDataAccessor schedules a GC task to execute 60s (default ttl) from when the task was submitted. If there already exists a GC task, [updateGCTimer](https://github.com/apache/helix/blob/2add0c48e648c011740ec419a1b1ef17a5888c97/helix-core/src/main/java/org/apache/helix/manager/zk/ZkBucketDataAccessor.java#L357) attempts to cancel it reschedule it for 60s from then. With this current logic, if the time between subsequent writes is never slower than the ttl (60s), then a GC task will never be executed - the task will constantly be scheduled and then cancelled. ### To Reproduce Call compressed compressedBucketWrite every ttl / 2 seconds and observe that nodes are never cleaned up. ### Expected behavior GC should occur at some point. ### Additional context Add any other context about the problem here. -- 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: reviews-unsubscr...@helix.apache.org.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: reviews-unsubscr...@helix.apache.org For additional commands, e-mail: reviews-h...@helix.apache.org
