[hotfix][dist] Disable Log4j shutdown hook in foreground mode#3634
Merged
Conversation
luoyuxia
approved these changes
Jul 10, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Purpose
Linked issue: close #xxx
#2020 disabled Log4j's shutdown hook for daemon mode so Fluss shutdown-hook logs can still be emitted during process shutdown. However, Kubernetes and Docker deployments use start-foreground, which goes through
fluss-console.shinstead offluss-daemon.sh.As a result, foreground TabletServer/Coordinator processes could still let Log4j close appenders before the Fluss shutdown hook runs, causing shutdown logs such as "Shutting down KvManager" to be lost.
Apply the same Log4j shutdown-hook setting to fluss-console.sh and add a dist script test to cover both foreground and daemon startup paths.
Brief change log
Tests
API and Format
Documentation