envoyproxy/envoy

Cleaner and more generic gRPC channel cache solution for filters that use Google gRPC on data plane

Open

#13,417 opened on Oct 7, 2020

View on GitHub
 (0 comments) (0 reactions) (0 assignees)C++ (5,373 forks)batch import
area/grpchelp wanted

Repository metrics

Stars
 (27,997 stars)
PR merge metrics
 (Avg merge 8d) (378 merged PRs in 30d)

Description

Title: Cleaner and more generic gRPC channel cache solution for filters that use Google gRPC on data plane

Description: Currently Google gRPC channel used by filters are created for every request, which is not efficient and has high latency. We need to find a cleaner and more generic gRPC channel cache solution for filters that use Google gRPC on data plane. We have short-term solution for ExtAuthz filter https://github.com/envoyproxy/envoy/pull/13265

[optional Relevant Links:]

Any extra documentation required to understand the issue.

Contributor guide

Research direction
Study the existing short term fix for ExtAuthz (PR #13265) and design a reusable gRPC channel caching mechanism. Investigate how filters currently create channels per request and propose a thread safe cache that can be shared across requests and filters.
Tech stack
cppgrpc
Domain
backendnetworking
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
4
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Over 1 week
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
GitC++gRPC
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
35