db: api: service: introduce system.client_routes table and related API endpoints#27323
Conversation
18b1447 to
2eb1966
Compare
|
v2:
|
🟢 CI State: SUCCESS
Build Details:
|
2eb1966 to
ab2f457
Compare
|
v3:
|
|
@patjed41 please review the changes (most of the changes other than adding endpoint and tests are related to raft) |
🔴 CI State: FAILURE
Failed Tests (11/88422):
Build Details:
Note: To re-trigger CI for this PR, comment: |
The new I will update |
ab2f457 to
4b6f19b
Compare
|
v4:
|
4b6f19b to
293a1f2
Compare
|
v5:
|
🔴 CI State: FAILURE
Failed Tests (10/78756):
Build Details:
Note: To re-trigger CI for this PR, comment: |
293a1f2 to
8825828
Compare
Those failures look like v6:
|
🟢 CI State: SUCCESS
Build Details:
|
|
@patjed41 Ci is green, please consider merging |
|
queued |
This feature was implemented in scylladb/scylladb#27323 Idea is to enable clients to dynamically learn address translation information from the system.client_routes table. When this table is updated drivers get CLIENT_ROUTES_CHANGE event with scope of the change. This PR adds ability to configure driver to read this table and events and maintain address translation mapping updated.
This feature was implemented in scylladb/scylladb#27323 Idea is to enable clients to dynamically learn address translation information from the system.client_routes table. When this table is updated drivers get CLIENT_ROUTES_CHANGE event with scope of the change. This PR adds ability to configure driver to read this table and events and maintain address translation mapping updated.
This feature was implemented in scylladb/scylladb#27323 Idea is to enable clients to dynamically learn address translation information from the system.client_routes table. When this table is updated drivers get CLIENT_ROUTES_CHANGE event with scope of the change. This PR adds ability to configure driver to read this table and events and maintain address translation mapping updated.
This feature was implemented in scylladb/scylladb#27323 Idea is to enable clients to dynamically learn address translation information from the system.client_routes table. When this table is updated drivers get CLIENT_ROUTES_CHANGE event with scope of the change. This PR adds ability to configure driver to read this table and events and maintain address translation mapping updated.
This feature was implemented in scylladb/scylladb#27323 Idea is to enable clients to dynamically learn address translation information from the system.client_routes table. When this table is updated drivers get CLIENT_ROUTES_CHANGE event with scope of the change. This PR adds ability to configure driver to read this table and events and maintain address translation mapping updated.
This feature was implemented in scylladb/scylladb#27323 Idea is to enable clients to dynamically learn address translation information from the system.client_routes table. When this table is updated drivers get CLIENT_ROUTES_CHANGE event with scope of the change. This PR adds ability to configure driver to read this table and events and maintain address translation mapping updated.
This feature was implemented in scylladb/scylladb#27323 Idea is to enable clients to dynamically learn address translation information from the system.client_routes table. When this table is updated drivers get CLIENT_ROUTES_CHANGE event with scope of the change. This PR adds ability to configure driver to read this table and events and maintain address translation mapping updated.
This feature was implemented in scylladb/scylladb#27323 Idea is to enable clients to dynamically learn address translation information from the system.client_routes table. When this table is updated drivers get CLIENT_ROUTES_CHANGE event with scope of the change. This PR adds ability to configure driver to read this table and events and maintain address translation mapping updated.
This feature was implemented in scylladb/scylladb#27323 Idea is to enable clients to dynamically learn address translation information from the system.client_routes table. When this table is updated drivers get CLIENT_ROUTES_CHANGE event with scope of the change. This PR adds ability to configure driver to read this table and events and maintain address translation mapping updated.
This feature was implemented in scylladb/scylladb#27323 Idea is to enable clients to dynamically learn address translation information from the system.client_routes table. When this table is updated drivers get CLIENT_ROUTES_CHANGE event with scope of the change. This PR adds ability to configure driver to read this table and events and maintain address translation mapping updated.
This feature was implemented in scylladb/scylladb#27323 Idea is to enable clients to dynamically learn address translation information from the system.client_routes table. When this table is updated drivers get CLIENT_ROUTES_CHANGE event with scope of the change. This PR adds ability to configure driver to read this table and events and maintain address translation mapping updated.
This feature was implemented in scylladb/scylladb#27323 Idea is to enable clients to dynamically learn address translation information from the system.client_routes table. When this table is updated drivers get CLIENT_ROUTES_CHANGE event with scope of the change. This PR adds ability to configure driver to read this table and events and maintain address translation mapping updated.
system.client_routesis a system table that sets the target address and ports for eachhost_id, for one or more connection (e.g., Private Link) represented byconnection_id. Cloud will write the table via REST, and drivers will read it via CQL to override values obtained fromsystem.localandsystem.peers.This patch series contains:
CLIENT_ROUTESfeature flag.system.client_routestablev2/client-routesPOST/DELETE/GET endpointsCLIENT_ROUTES_CHANGEevent that is sent to drivers whensystem.client_routesis changedRef: scylladb/scylla-enterprise#5699
For now, no automatic backport. However, the changes are planned to be release on
2025.4either as a backport or a private build.