-
Notifications
You must be signed in to change notification settings - Fork 4.1k
kv: mass INSERTs easily run into TransactionRetryWithProtoRefreshError #98553
Copy link
Copy link
Closed
Labels
C-bugCode not up to spec/doc, specs & docs deemed correct. Solution expected to change code/behavior.Code not up to spec/doc, specs & docs deemed correct. Solution expected to change code/behavior.T-kvKV TeamKV Team
Description
Initially found using Striim.
Related COPY issue: #90656
May also go away with: #91831
When using Striim using the default settings, we usually run into TransactionRetryWithProtoRefreshError (RETRY_ASYNC_WRITE_FAILURE).
This is usually at about the 5MM row mark where rows are inserted one at a time on a single thread as follows (using the pg wire protocol):
Parse <stmt>
Bind <stmt> <args>
Execute
# ...
# Bind/Execute 255 times in total
#
Sync
This is a very common JDBC pattern.
Whilst we do have a workaround for now, we think it is beneficial to make the database more tolerant of these kinds of issues.
Jira issue: CRDB-25326
gz#16766
gz#17451
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
C-bugCode not up to spec/doc, specs & docs deemed correct. Solution expected to change code/behavior.Code not up to spec/doc, specs & docs deemed correct. Solution expected to change code/behavior.T-kvKV TeamKV Team