aboutsummaryrefslogtreecommitdiff
path: root/weed/shell/command_s3_bucket_delete.go
diff options
context:
space:
mode:
authorChris Lu <chrislusf@users.noreply.github.com>2025-12-13 12:10:15 -0800
committerGitHub <noreply@github.com>2025-12-13 12:10:15 -0800
commitd80d8be01208ffe82861b8aa50d4baf599fdfa02 (patch)
treefa6cf7c55579356d4a73514c71e0ec167eb44c47 /weed/shell/command_s3_bucket_delete.go
parent36b8b2147b55068f65f6c4cacc5645bc3453f173 (diff)
downloadseaweedfs-d80d8be01208ffe82861b8aa50d4baf599fdfa02.tar.xz
seaweedfs-d80d8be01208ffe82861b8aa50d4baf599fdfa02.zip
fix(s3): start KeepConnectedToMaster for filer discovery with filerGroup (#7732)
Fixes #7721 When S3 server is configured with a filerGroup, it creates a MasterClient to enable dynamic filer discovery. However, the KeepConnectedToMaster() background goroutine was never started, causing GetMaster() to block indefinitely in WaitUntilConnected(). This resulted in the log message: WaitUntilConnected still waiting for master connection (attempt N)... being logged repeatedly every ~20 seconds. The fix adds the missing 'go masterClient.KeepConnectedToMaster(ctx)' call to properly establish the connection to master servers. Also adds unit tests to verify WaitUntilConnected respects context cancellation.
Diffstat (limited to 'weed/shell/command_s3_bucket_delete.go')
0 files changed, 0 insertions, 0 deletions