You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The consul name resolution component currently makes a roundtrip call to the agent each time it resolves an app id, this can be improved by maintaining an in memory cache of the resolved service nodes combined with the blocking query feature exposed by the consul api - https://www.consul.io/api-docs/features/blocking
This issue has been automatically marked as stale because it has not had activity in the last 30 days. It will be closed in the next 7 days unless it is tagged (pinned, good first issue, help wanted or triaged/resolved) or other activity occurs. Thank you for your contributions.
This issue has been automatically closed because it has not had activity in the last 37 days. If this issue is still valid, please ping a maintainer and ask them to label it as pinned, good first issue, help wanted or triaged/resolved. Thank you for your contributions.
The consul name resolution component currently makes a roundtrip call to the agent each time it resolves an app id, this can be improved by maintaining an in memory cache of the resolved service nodes combined with the blocking query feature exposed by the consul api - https://www.consul.io/api-docs/features/blocking
credit to @pkedy for the suggestion
PR - #963
The text was updated successfully, but these errors were encountered: