Skip to content

Commit ddd0625

Browse files
authored
fix: remove the statement of session number limits (#1928)
Cloud Spanner no longer has the 10K "Sessions per database per node" limit. Doc fix only Fixes #1927
1 parent 56f9129 commit ddd0625

File tree

1 file changed

+3
-4
lines changed
  • google-cloud-spanner/src/main/java/com/google/cloud/spanner

1 file changed

+3
-4
lines changed

google-cloud-spanner/src/main/java/com/google/cloud/spanner/Session.java

+3-4
Original file line numberDiff line numberDiff line change
@@ -28,10 +28,9 @@
2828
* read-write/write-only transactions, create multiple sessions. Note that standalone reads and
2929
* queries use a transaction internally, and count toward the one transaction limit.
3030
*
31-
* <p>Cloud Spanner limits the number of sessions that can exist at any given time; thus, it is a
32-
* good idea to delete idle and/or unneeded sessions. Aside from explicit deletes, Cloud Spanner can
33-
* delete sessions for which no operations are sent for more than an hour, or due to internal
34-
* errors. If a session is deleted, requests to it return {@link ErrorCode#NOT_FOUND}.
31+
* <p>It is a good idea to delete idle and/or unneeded sessions. Aside from explicit deletes, Cloud
32+
* Spanner can delete sessions for which no operations are sent for more than an hour, or due to
33+
* internal errors. If a session is deleted, requests to it return {@link ErrorCode#NOT_FOUND}.
3534
*
3635
* <p>Idle sessions can be kept alive by sending a trivial SQL query periodically, for example,
3736
* {@code SELECT 1}.

0 commit comments

Comments
 (0)