Skip to content

request-id: implement functionality #1

@odeke-em

Description

@odeke-em

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

Metadata

Metadata

Assignees

Labels

No labels
No labels

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions