aboutsummaryrefslogtreecommitdiff
path: root/weed/command
diff options
context:
space:
mode:
authorrustrover <154583430+rustrover@users.noreply.github.com>2024-03-09 23:35:47 +0800
committerGitHub <noreply@github.com>2024-03-09 07:35:47 -0800
commitab70aa92da9b0baf1b918656e792b2344f4a766e (patch)
treea7754362fef0b64f7daadd0dcdddaf914d08629f /weed/command
parentb544a69550d6793dc61eafccc9b850d43bee5d32 (diff)
downloadseaweedfs-ab70aa92da9b0baf1b918656e792b2344f4a766e.tar.xz
seaweedfs-ab70aa92da9b0baf1b918656e792b2344f4a766e.zip
remove repetitive words (#5364)
Diffstat (limited to 'weed/command')
-rw-r--r--weed/command/master_follower.go2
1 files changed, 1 insertions, 1 deletions
diff --git a/weed/command/master_follower.go b/weed/command/master_follower.go
index c4f0cfc3c..64583c602 100644
--- a/weed/command/master_follower.go
+++ b/weed/command/master_follower.go
@@ -52,7 +52,7 @@ var cmdMasterFollower = &Command{
In most cases, the master follower is not needed. In big data centers with thousands of volume
servers. In theory, the master may have trouble to keep up with the write requests and read requests.
- The master follower can relieve the master from from read requests, which only needs to
+ The master follower can relieve the master from read requests, which only needs to
lookup a fileId or volumeId.
The master follower currently can handle fileId lookup requests: