Currently, we embed a GatewayNodeID into batch request headers so that they can be tracked for lease rebalancing decisions. In #73500, a SQLInstanceID was embedded into the TxnMeta structure, representing a gateway node (in the case of a single tenant cluster) or a SQL pod (in the case of a multitenant cluster). This could be refactored to replace passing in both a GatewayNodeID, which is 0 in a multitenant cluster, and a SQLInstanceID when creating a transaction in txn.go.
Jira issue: CRDB-11793
Currently, we embed a
GatewayNodeIDinto batch request headers so that they can be tracked for lease rebalancing decisions. In #73500, aSQLInstanceIDwas embedded into theTxnMetastructure, representing a gateway node (in the case of a single tenant cluster) or a SQL pod (in the case of a multitenant cluster). This could be refactored to replace passing in both aGatewayNodeID, which is 0 in a multitenant cluster, and aSQLInstanceIDwhen creating a transaction intxn.go.Jira issue: CRDB-11793