-
Notifications
You must be signed in to change notification settings - Fork 3.8k
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
roachtest: clearrange/checks=false failed #129026
Labels
A-storage
Relating to our storage engine (Pebble) on-disk storage.
branch-master
Failures and bugs on the master branch.
C-test-failure
Broken test (automatically or manually discovered).
O-roachtest
O-robot
Originated from a bot.
release-blocker
Indicates a release-blocker. Use with branch-release-2x.x label to denote which branch is blocked.
T-storage
Storage Team
Comments
cockroach-teamcity
added
branch-master
Failures and bugs on the master branch.
C-test-failure
Broken test (automatically or manually discovered).
O-roachtest
O-robot
Originated from a bot.
release-blocker
Indicates a release-blocker. Use with branch-release-2x.x label to denote which branch is blocked.
T-storage
Storage Team
labels
Aug 15, 2024
blathers-crl
bot
added
the
A-storage
Relating to our storage engine (Pebble) on-disk storage.
label
Aug 15, 2024
@itsbilal looks like there's an out-of-order issue with the splitting of snapshot ingest sstables |
This was referenced Aug 15, 2024
This was referenced Aug 15, 2024
itsbilal
added a commit
to itsbilal/cockroach
that referenced
this issue
Aug 15, 2024
Informs cockroachdb#129026. Epic: none Release note: None
craig bot
pushed a commit
that referenced
this issue
Aug 15, 2024
128849: roachtest: make graceful stop an option instead of a function r=DarrylWong a=renatolabs Previously, a few tests would use the `StopCockroachGracefullyOnNode` function when they wanted a graceful shutdown. However, the start/stop functions are already able to take options from the caller. In this commit, we replace the custom function to perform a graceful shutdown with a `Graceful` option that can be passed to `Stop`. This is now composable with other options that can also be passed to `Stop`. Epic: none Release note: None 129063: kvserver: disable snapshot splitting of sstables for now r=RaduBerinde a=itsbilal Informs #129026. Epic: none Release note: None Co-authored-by: Renato Costa <renato@cockroachlabs.com> Co-authored-by: Bilal Akhtar <bilal@cockroachlabs.com>
itsbilal
added a commit
to itsbilal/cockroach
that referenced
this issue
Aug 15, 2024
This change updates the snapshot strategy's sender side to iterate over points and ranges together, instead of only iterating on points first, then only ranges. This allows us to more efficiently split snapshot sstables on the receiver side. To avoid the need to add a version gate on the receiver side, we propagate a bool, RangeKeysInOrder, to the receiver which is a signal to it to enable sstable splits. Fixes cockroachdb#129026. Epic: none Release note: None
itsbilal
added a commit
to itsbilal/cockroach
that referenced
this issue
Aug 16, 2024
This change updates the snapshot strategy's sender side to iterate over points and ranges together, instead of only iterating on points first, then only ranges. This allows us to more efficiently split snapshot sstables on the receiver side. To avoid the need to add a version gate on the receiver side, we propagate a bool, RangeKeysInOrder, to the receiver which is a signal to it to enable sstable splits. Fixes cockroachdb#129026. Epic: none Release note: None
craig bot
pushed a commit
that referenced
this issue
Aug 16, 2024
129088: kvserver: reenable splitting of snapshot sstables r=aadityasondhi a=itsbilal This change updates the snapshot strategy's sender side to iterate over points and ranges together, instead of only iterating on points first, then only ranges. This allows us to more efficiently split snapshot sstables on the receiver side. To avoid the need to add a version gate on the receiver side, we propagate a bool, RangeKeysInOrder, to the receiver which is a signal to it to enable sstable splits. Fixes #129026. Epic: none Release note: None Co-authored-by: Bilal Akhtar <bilal@cockroachlabs.com>
itsbilal
added a commit
that referenced
this issue
Sep 18, 2024
This change updates the snapshot strategy's sender side to iterate over points and ranges together, instead of only iterating on points first, then only ranges. This allows us to more efficiently split snapshot sstables on the receiver side. To avoid the need to add a version gate on the receiver side, we propagate a bool, RangeKeysInOrder, to the receiver which is a signal to it to enable sstable splits. Fixes #129026. Epic: none Release note: None
itsbilal
added a commit
to itsbilal/cockroach
that referenced
this issue
Sep 30, 2024
This change updates the snapshot strategy's sender side to iterate over points and ranges together, instead of only iterating on points first, then only ranges. This allows us to more efficiently split snapshot sstables on the receiver side. To avoid the need to add a version gate on the receiver side, we propagate a bool, RangeKeysInOrder, to the receiver which is a signal to it to enable sstable splits. Fixes cockroachdb#129026. Epic: none Release note: None
itsbilal
added a commit
to itsbilal/cockroach
that referenced
this issue
Sep 30, 2024
This change updates the snapshot strategy's sender side to iterate over points and ranges together, instead of only iterating on points first, then only ranges. This allows us to more efficiently split snapshot sstables on the receiver side. To avoid the need to add a version gate on the receiver side, we propagate a bool, RangeKeysInOrder, to the receiver which is a signal to it to enable sstable splits. Fixes cockroachdb#129026. Epic: none Release note: None
itsbilal
added a commit
to itsbilal/cockroach
that referenced
this issue
Nov 7, 2024
This change updates the snapshot strategy's sender side to iterate over points and ranges together, instead of only iterating on points first, then only ranges. This allows us to more efficiently split snapshot sstables on the receiver side. To avoid the need to add a version gate on the receiver side, we propagate a bool, RangeKeysInOrder, to the receiver which is a signal to it to enable sstable splits. Fixes cockroachdb#129026. Epic: none Release note: None
itsbilal
added a commit
to itsbilal/cockroach
that referenced
this issue
Nov 7, 2024
This change updates the snapshot strategy's sender side to iterate over points and ranges together, instead of only iterating on points first, then only ranges. This allows us to more efficiently split snapshot sstables on the receiver side. To avoid the need to add a version gate on the receiver side, we propagate a bool, RangeKeysInOrder, to the receiver which is a signal to it to enable sstable splits. Fixes cockroachdb#129026. Epic: none Release note: None
blathers-crl bot
pushed a commit
that referenced
this issue
Nov 12, 2024
This change updates the snapshot strategy's sender side to iterate over points and ranges together, instead of only iterating on points first, then only ranges. This allows us to more efficiently split snapshot sstables on the receiver side. To avoid the need to add a version gate on the receiver side, we propagate a bool, RangeKeysInOrder, to the receiver which is a signal to it to enable sstable splits. Fixes #129026. Epic: none Release note: None
itsbilal
added a commit
to itsbilal/cockroach
that referenced
this issue
Nov 13, 2024
This change updates the snapshot strategy's sender side to iterate over points and ranges together, instead of only iterating on points first, then only ranges. This allows us to more efficiently split snapshot sstables on the receiver side. To avoid the need to add a version gate on the receiver side, we propagate a bool, RangeKeysInOrder, to the receiver which is a signal to it to enable sstable splits. Fixes cockroachdb#129026. Epic: none Release note: None
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
A-storage
Relating to our storage engine (Pebble) on-disk storage.
branch-master
Failures and bugs on the master branch.
C-test-failure
Broken test (automatically or manually discovered).
O-roachtest
O-robot
Originated from a bot.
release-blocker
Indicates a release-blocker. Use with branch-release-2x.x label to denote which branch is blocked.
T-storage
Storage Team
roachtest.clearrange/checks=false failed with artifacts on master @ 575cdd4696dfcac8f311d1ea546683271102f73e:
Parameters:
ROACHTEST_arch=amd64
ROACHTEST_cloud=azure
ROACHTEST_coverageBuild=false
ROACHTEST_cpu=16
ROACHTEST_encrypted=false
ROACHTEST_fs=ext4
ROACHTEST_localSSD=true
ROACHTEST_metamorphicBuild=false
ROACHTEST_ssd=0
Help
See: roachtest README
See: How To Investigate (internal)
Grafana is not yet available for azure clusters
This test on roachdash | Improve this report!
Jira issue: CRDB-41335
The text was updated successfully, but these errors were encountered: