quickwit-oss / quickwit-oss/quickwit
Improve logging error when no metastore is available
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- Rust
- Stars
- 11.7k
- Forks
- 597
- Avg merge
- 2d 22h
- Merged PRs (30d)
- 37
Description
When starting a node in a cluster with no metastore service available, we log this error
✘ Command failed: Failed to start server: no metastore service was found among cluster members. Try running Quickwit with additional metastore service `quickwit run --service metastore`.
2023-04-05T08:26:01.299Z ERROR quickwit_serve: No metastore service found among cluster members, stopping server.
Stream closed EOF for quickwit/quickwit-searcher-1 (quickwit)
It can make the user believe that you should add a new metastore in the case where there is already a metastore running.
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 by locating the code that discovers metastore services among cluster members and emits the reported error and log message. Reproduce node startup with an available metastore, then verify that the resulting message distinguishes an unavailable service from a missing one.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- backend, distributed-systems
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100