Skip to content

chore(spanner): use channel affinity#13231

Open
rahul2393 wants to merge 2 commits into
mainfrom
use-channel-affinity
Open

chore(spanner): use channel affinity#13231
rahul2393 wants to merge 2 commits into
mainfrom
use-channel-affinity

Conversation

@rahul2393
Copy link
Copy Markdown
Contributor

Internal reference: go/grpc-gcp-fixes#bookmark=id.q4x3oa8l672

@rahul2393 rahul2393 requested review from a team as code owners May 20, 2026 04:46
}

public static TracingFramework getActiveTracingFramework() {
synchronized (lock) {
Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

FYI: this change is unrelated, but since it was small perf change I included it here, this was on critical request path being shown up in benchmark mutex profile

Copy link
Copy Markdown
Contributor

@gemini-code-assist gemini-code-assist Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request replaces the use of logical affinity keys and explicit unbinding with direct channel ID affinity using AtomicReference for Spanner operations. This change simplifies the integration with grpc-gcp by removing the need for affinity-key map management and the associated cleanup logic. Additionally, SpannerOptions was updated to use a volatile variable for the active tracing framework, removing unnecessary synchronization. I have no feedback to provide.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant