quickwit-oss / quickwit-oss/quickwit
Internal GRPC error without any error log on the server side
Open
Nobody has claimed this yet.
bug
- Dominant language
- Rust
- Stars
- 11.7k
- Forks
- 597
- Avg merge
- 2d 22h
- Merged PRs (30d)
- 37
Description
We need to add logging for anything that might emit a grpc Internal error.
ERROR failed to fetch records from ingester `quickwit-indexer-9`: closing fetch stream client_id=indexer/quickwit-indexer-12/logline.0d22b12092.2024-07-22.80:01J3DJ6WE4840B0XY6N348SG6E/_ingest-source/01J3DNRHZNC8KBGJ6XCT7AWVMP index_uid=logline.0d22b12092.2024-07-22.80:01J3DJ6WE4840B0XY6N348SG6E source_id=_ingest-source shard_id=01J3DNRTXDZ7DWJ0KRZ33SX9QE error=internal error: h2 protocol error: error reading a body from connection: stream closed because of a broken pipe
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 from the reported “failed to fetch records from ingester” error and trace the Rust gRPC paths that can produce an Internal error. Identify the relevant server-side logging points and verify that the broken-pipe scenario and other Internal errors produce useful server logs; the payload names no files or tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- grpc, rust
- Domain
- distributed-systems, observability
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100