grpc-ecosystem / grpc-ecosystem/grpc-spring

Using service discovery - How connections to service discovery agents are handled? Can we limit it?

Open
#936 2 comments 0 reactions 0 assignees View on GitHub
feedback required question
Dominant language
Java
Stars
3.7k
Forks
858
PR merge metrics
No merged PRs in 30d

Description

I am using this lib with service discovery based on Consul. I have recentry hit Consul max connection limit per IP.
It seems that every gRPC thread has its own connection to Consul. Is it how it works? Is there an option to share connections and lower number of concurrent connections to service discovery agent?

Or maybe it is entirely spring-related topic?

Contributor guide

Open the contributing guide

Research direction

No files or tests are named. Start by tracing how service-discovery connections are handled for each gRPC thread and determine whether connections can be shared or limited; done means documenting the current behavior and agreeing on the scope of any change.

Written by the indexing model from the issue text.

Assessment

Tech stack
grpc, java, spring-boot
Domain
backend, distributed-systems
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.