Skip to content

lock_object_storage_task_distribution_ms setting #866

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: antalya-25.3
Choose a base branch
from

Conversation

ianton-ru
Copy link

@ianton-ru ianton-ru commented Jun 18, 2025

Changelog category (leave one):

  • New Feature

Changelog entry (a user-readable short description of the changes that goes to CHANGELOG.md):

Setting lock_object_storage_task_distribution_ms to improve cache locality with swarm cluster

Documentation entry for user-facing changes

Solve #867
Setting lock_object_storage_task_distribution_ms prevent object to be processed on non-primary swarm nodes when primary is alive at last lock_object_storage_task_distribution_ms milliseconds.
Swarm has 2 nodes, node1 processed all objects, node2 is overloaded and processed only part objects.
Behavior before PR and default (with lock_object_storage_task_distribution_ms=0): node1 takes unprocessed objects.
Behavior with lock_object_storage_task_distribution_ms=3000 - node1 takes unprocessed objects only if node2 does not take it for 3 seconds. If node2 took something 1 second ago, node1 waits and makes new request after 2 seconds. If node2 still did not take any object, objects goes to node1. It node2 took something, node1 waits again till the end of new 3-second period.

Exclude tests:

  • Fast test
  • Integration Tests
  • Stateless tests
  • Stateful tests
  • Performance tests
  • All with ASAN
  • All with TSAN
  • All with MSAN
  • All with UBSAN
  • All with Coverage
  • All with Aarch64
  • All Regression
  • Disable CI Cache

@ianton-ru ianton-ru force-pushed the feature/cache_locality_lock branch from fd2dde7 to f1a4e00 Compare June 18, 2025 22:36
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants