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

release-22.2.0: release-22.2: backupccl: enable restore_span.target_size #90573

Closed

Conversation

blathers-crl[bot]
Copy link

@blathers-crl blathers-crl bot commented Oct 24, 2022

Backport 1/1 commits from #89351 on behalf of @blathers-crl[bot].

/cc @cockroachdb/release


Backport 1/1 commits from #89333 on behalf of @adityamaru.

/cc @cockroachdb/release


This setting was previously disabled because of timeouts being observed when restoring our TPCCInc fixtures. The cause of those timeouts has been identified as
#88329 making it safe to re-enable merging of spans during restore. This settings prevents restore from over-splitting and leaving the cluster with a merge hangover post restore.

Informs: #86470

Release note (sql change): Sets backup.restore_span.target_size to default to 384 MiB so that restore merges upto that size of spans when reading from the backup before actually ingesting data. This should reduce the number of ranges created during restore and thereby reduce the merging of ranges that needs to occur post restore.


Release justification: bug fix.


Release justification:

This setting was previously disabled because of timeouts being
observed when restoring our TPCCInc fixtures. The cause of those
timeouts has been identified as
#88329 making it safe
to re-enable merging of spans during restore. This settings prevents
restore from over-splitting and leaving the cluster with a merge hangover
post restore.

Informs: #86470

Release note (sql change): Sets `backup.restore_span.target_size`
to default to 384 MiB so that restore merges upto that size of spans
when reading from the backup before actually ingesting data. This should
reduce the number of ranges created during restore and thereby reduce
the merging of ranges that needs to occur post restore.
@blathers-crl blathers-crl bot requested a review from a team as a code owner October 24, 2022 21:07
@blathers-crl blathers-crl bot force-pushed the blathers/backport-release-22.2.0-89351 branch from 29cd7b9 to 4f765a9 Compare October 24, 2022 21:07
@blathers-crl blathers-crl bot requested review from msbutler, benbardin, dt and stevendanna and removed request for a team October 24, 2022 21:07
@blathers-crl
Copy link
Author

blathers-crl bot commented Oct 24, 2022

Thanks for opening a backport.

Please check the backport criteria before merging:

  • Patches should only be created for serious issues or test-only changes.
  • Patches should not break backwards-compatibility.
  • Patches should change as little code as possible.
  • Patches should not change on-disk formats or node communication protocols.
  • Patches should not add new functionality.
  • Patches must not add, edit, or otherwise modify cluster versions; or add version gates.
If some of the basic criteria cannot be satisfied, ensure that the exceptional criteria are satisfied within.
  • There is a high priority need for the functionality that cannot wait until the next release and is difficult to address in another way.
  • The new functionality is additive-only and only runs for clusters which have specifically “opted in” to it (e.g. by a cluster setting).
  • New code is protected by a conditional check that is trivial to verify and ensures that it only runs for opt-in clusters.
  • The PM and TL on the team that owns the changed code have signed off that the change obeys the above rules.

Add a brief release justification to the body of your PR to justify this backport.

Some other things to consider:

  • What did we do to ensure that a user that doesn’t know & care about this backport, has no idea that it happened?
  • Will this work in a cluster of mixed patch versions? Did we test that?
  • If a user upgrades a patch version, uses this feature, and then downgrades, what happens?

@blathers-crl blathers-crl bot added blathers-backport This is a backport that Blathers created automatically. O-robot Originated from a bot. labels Oct 24, 2022
@blathers-crl blathers-crl bot closed this Oct 24, 2022
@blathers-crl blathers-crl bot deleted the blathers/backport-release-22.2.0-89351 branch October 24, 2022 21:08
@cockroach-teamcity
Copy link
Member

This change is Reviewable

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
blathers-backport This is a backport that Blathers created automatically. O-robot Originated from a bot.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants