Skip to content

Commit

Permalink
fix: remove the statement of session number limits (#1928)
Browse files Browse the repository at this point in the history
Cloud Spanner no longer has the 10K "Sessions per database per node" limit.

Doc fix only

Fixes #1927
  • Loading branch information
rbrtwng authored Nov 18, 2022
1 parent 56f9129 commit ddd0625
Showing 1 changed file with 3 additions and 4 deletions.
Original file line number Diff line number Diff line change
Expand Up @@ -28,10 +28,9 @@
* read-write/write-only transactions, create multiple sessions. Note that standalone reads and
* queries use a transaction internally, and count toward the one transaction limit.
*
* <p>Cloud Spanner limits the number of sessions that can exist at any given time; thus, it is a
* good idea to delete idle and/or unneeded sessions. Aside from explicit deletes, Cloud Spanner can
* delete sessions for which no operations are sent for more than an hour, or due to internal
* errors. If a session is deleted, requests to it return {@link ErrorCode#NOT_FOUND}.
* <p>It is a good idea to delete idle and/or unneeded sessions. Aside from explicit deletes, Cloud
* Spanner can delete sessions for which no operations are sent for more than an hour, or due to
* internal errors. If a session is deleted, requests to it return {@link ErrorCode#NOT_FOUND}.
*
* <p>Idle sessions can be kept alive by sending a trivial SQL query periodically, for example,
* {@code SELECT 1}.
Expand Down

0 comments on commit ddd0625

Please sign in to comment.