gRPC health-checking for mesh interface
Nobody has claimed this yet.
- Dominant language
- Scala
- Stars
- 5.3k
- Forks
- 494
- PR merge metrics
- No merged PRs in 30d
Description
gRPC has a native support for health-checking remote services as per https://github.com/grpc/grpc/blob/master/doc/health-checking.md
In our setup we've seen situation when Namerd becoming "broken" occasionally due to reasons not identified yet. In such situations it doesn't accept any new connections and all connected Linkerd instances are not able to resolve new names anymore. This is a separate issue, but having Linkerd health-checking Namerd and re-connecting to another healthy instance would've increased the stability in our case.
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 with the gRPC health-checking specification linked in the issue, then trace the mesh interface's interaction with Namerd and its handling of new connections. Determine how a health check and reconnection to another healthy instance would fit the reported failure scenario; done means the behavior is implemented and validated for a broken Namerd instance.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- grpc
- Domain
- networking
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100