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

fix: lower max_total_records per batch_commit_update costs #377

Merged
merged 1 commit into from
Dec 14, 2019
Merged

Conversation

pjenvey
Copy link
Member

@pjenvey pjenvey commented Dec 13, 2019

and remove the potential, redundant touch_collection on batch commit

recalculating the mutations (see adca8d6):

total: 19998

Closes #333

and remove the potential, redundant touch_collection on batch commit

recalculating the mutations (see adca8d6):

- 4 for touch_collection: always an UPDATE on batch commit (due to
  pretouch_collection). we thought this cost 1 but it's probably 4 (see
  #333)
- 19992 (1666 max_total_records * 12, for the UPDATE case, see #333) for
  the mix of post_bsos and batch_commit
- 2 for batch delete (1 for the delete and 1 BsoExpiry update)

total: 19998

Closes #333
@jrconlin jrconlin merged commit cd76e64 into master Dec 14, 2019
@jrconlin jrconlin deleted the fix/333 branch July 30, 2020 14:54
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

Successfully merging this pull request may close these issues.

Seeing spanner 20k mutation limit errors for inserts in production
2 participants