quickwit-oss / quickwit-oss/quickwit
Make assigning shards logs less verbose
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- Rust
- Stars
- 11.7k
- Forks
- 597
- Avg merge
- 2d 22h
- Merged PRs (30d)
- 37
Description
AFAIK, we log this message even if there is no change in the shard list. This is quite verbose.
Aug 1 10:50:10 quickwit-indexer-28 quickwit-indexer INFO quickwit_indexing::actors::indexing_pipeline: assigning shards to indexing pipeline shard_ids={ShardId("01J45KS3DJY1Q4D65N6D2Y3H2F")}
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start in the quickwit_indexing::actors::indexing_pipeline entry point referenced by the log message and inspect when shard assignment is logged. Confirm the behavior with the existing indexing tests or logging-related test setup; the work is done when unchanged shard lists no longer produce this message while actual assignments remain logged.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- observability
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100