Skip to content

Conversation

chrislusf
Copy link
Collaborator

What problem are we solving?

lock ring tests sometimes fail

How are we solving the problem?

need to get locks on reading

How is the PR tested?

unit tests

Checks

  • I have added unit tests if possible.
  • I will add related wiki document changes and link to this PR after merging.

@chrislusf chrislusf merged commit 95261a7 into master Jun 25, 2025
7 checks passed
@chrislusf chrislusf deleted the improve-lock-ring branch June 25, 2025 06:04
kmlebedev pushed a commit to kmlebedev/seaweedfs that referenced this pull request Jun 25, 2025
* fix flaky lock ring test

* add more tests
chrislusf added a commit that referenced this pull request Jul 3, 2025
… limit condition (#6920)

* refactor concurrentDownloadLimit

* fix loop

* fix cmdServer

* fix: resolve conversation pr 6920

* Changes logging function (#6919)

* updated logging methods for stores

* updated logging methods for stores

* updated logging methods for filer

* updated logging methods for uploader and http_util

* updated logging methods for weed server

---------

Co-authored-by: akosov <a.kosov@kryptonite.ru>

* Improve lock ring (#6921)

* fix flaky lock ring test

* add more tests

* fix: build

* fix: rm import util/version

* fix: serverOptions

* refactoring

---------

Co-authored-by: Aleksey Kosov <rusyak777@list.ru>
Co-authored-by: akosov <a.kosov@kryptonite.ru>
Co-authored-by: Chris Lu <chrislusf@users.noreply.github.com>
Co-authored-by: chrislu <chris.lu@gmail.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant