Skip to content

Investigate LB limits for RPC calls

--Investigate LB limits for RPC calls (https://app.clickup.com/t/86c5kv0qp) We should have one fleet instance that supports only RPC traffic, so any other traffic should go to the remaining one!.

Load Balancer Limits and Routing for RPC Calls

1. Architecture Overview

The system uses a load balancer to route incoming requests to backend services. There are two main types of incoming requests: * RPC Requests: Routed to backend components (CC1, CC2, CC3). * HTTP/API Browser Requests: Routed to backend components (CC1, CC2, XXXX).

The diagrams illustrate that the load balancer can direct different types of traffic to different backend services or components, depending on the protocol and the routing rules.

2. Google Cloud Network Endpoint Groups (NEGs)

Network Endpoint Groups Overview

The Google Cloud Console shows two zonal NEGs: * neg-shared: 2 endpoints, used by adi-tms-fleet-nightly-neg * neg-unique: 1 endpoint, used by adi-tms-fleet-nightly-neg2

Both NEGs are in the europe-north1-a zone, using the default subnet and VPC network.

NEG Details

  • neg-shared
    • Endpoints:
      • 10.166.0.8:5024 (att-nightly-tms-backend-1b-nightly)
      • 10.166.0.7:5024 (att-nightly-tms-backend-2b-nightly)
    • Default port: 5024
    • Used by: adi-tms-fleet-nightly-neg
  • neg-unique
    • Endpoint:
      • 10.166.0.7:5024 (att-nightly-tms-backend-2b-nightly)
    • Default port: 5024
    • Used by: adi-tms-fleet-nightly-neg2

3. Load Balancer Routing Rules

The load balancer is configured with advanced host and path rules. For the host tms-fleet-nightly.attracs.com, the routing rules are as follows:

defaultService: projects/att-nightly/global/backendServices/adi-tms-fleet-nightly-neg
name: matcher1
routeRules:
- matchRules:
  - prefixMatch: /twirp/tms.fleet.v1.Fleet/
  priority: 0
  routeAction:
    weightedBackendServices:
    - backendService: projects/att-nightly/global/backendServices/adi-tms-fleet-nightly-neg
      weight: 100
- matchRules:
  - prefixMatch: /
  priority: 1
  routeAction:
    weightedBackendServices:
    - backendService: projects/att-nightly/global/backendServices/adi-tms-fleet-nightly-neg2
      weight: 100

* Requests matching /twirp/tms.fleet.v1.Fleet/ are routed to adi-tms-fleet-nightly-neg. * All other requests (/) are routed to adi-tms-fleet-nightly-neg2.

For tms-Stable: