Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

request-id: implement functionality #1

Open
6 tasks
odeke-em opened this issue Dec 11, 2024 · 0 comments
Open
6 tasks

request-id: implement functionality #1

odeke-em opened this issue Dec 11, 2024 · 0 comments
Assignees

Comments

@odeke-em
Copy link
Owner

Following https://orijtech.notion.site/x-goog-spanner-request-id-always-on-gRPC-header-to-aid-in-quick-debugging-of-errors-14aba6bc91348091a58fca7a505c9827 let's get these implemented

Requirements

  • Version being implemented
  • Implement rand_id_for_process: read from os.urandom(8) once per process
  • For each Client, increment the nth_client_id
  • Determine how to assign a channelID to a session with a unique identifier as the Cloud Spanner backend returns session_id that are non-monotonic: I've seen the values be sessions/1 depending on how many sessions are connected and that value can increase or decrease: assign channel_id
  • Determine how to assign nth_request
  • Figure out all the scenarios for retry attempts: nth_attempt
@odeke-em odeke-em self-assigned this Dec 11, 2024
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

No branches or pull requests

1 participant