This project is mirrored from https://github.com/cockroachdb/cockroach.
Pull mirroring updated .
- Jun 13, 2024
-
-
Austen McClernon authored
After #125276, which reduced gossip frequency, `TestReplicateQueueRebalanceMultiStore/multi-store` became flaky as the queue processing speed is artificially increased but gossip updates remain limited. Increase the gossip frequency to deflake the test. Fixes: #125360 Fixes: #125450 Release note: None
-
Austen McClernon authored
Introduce `kv.store_gossip.capacity_delta_threshold` and `kv.store_gossip.max_frequency`, which control the capacity delta required to trigger eager gossip for lease/range counts and the maximum frequency of eager store gossip. The defaults for these settings remained unchanged from the previously hard-coded defaults: `kv.store_gossip.capacity_delta_threshold`: 0.10 `kv.store_gossip.max_frequency`: 2s Resolves: #125227 Release note: None
-
Austen McClernon authored
Increase the relative requirement for triggering store gossip on capacity changes for lease and ranges. Previously, the requirement was a +-5% delta from the previously gossiped value, in addition to a minimum (5). Increase the relative delta from 5 to 10%. Informs: #125227 Release note: None
-
Austen McClernon authored
Previously, it was possible that stores would gossip their store descriptors rapidly on capacity changes, without limit. This patch introduces a hard frequency limit of 2s on capacity change triggered gossip. In other words, irrespective of any capacity changes that may have taken place, a store will gossip at most every 2s if satisfying the capacity delta trigger. Resolves: #125210 Release note: None
- Jun 12, 2024
-
-
RaduBerinde authored
release-24.1.1-rc: add block load semaphore, add cluster settings to control readahead
-
Radu Berinde authored
Epic: none
-
Radu Berinde authored
This change adds a limit on the number of block loads that happen in parallel, along with per-store metrics for (instantaneous) number of block loads in progress and the cumulative number of loads that had to wait because of the limit (i.e. were queued). Each store has its own limiter; the limit is distributed evenly between all stores. Epic: none
-
Radu Berinde authored
Changes: * [`b9423ee2`](https://github.com/cockroachdb/pebble/commit/b9423ee2) objstorage: add readahead configuration * [`c647ee0a`](https://github.com/cockroachdb/pebble/commit/c647ee0a) objstorage: fix preallocated handle initialization * [`27544a6c`](https://github.com/cockroachdb/pebble/commit/27544a6c) vfs: add Open options to loggingFS * [`a634c6e0`](https://github.com/cockroachdb/pebble/commit/a634c6e0) crl-release-24.1: db: more readable iterator stats * [`8948add4`](https://github.com/cockroachdb/pebble/commit/8948add4) crl-release-24.1: sstable: add LoadBlockSema option * [`31434407`](https://github.com/cockroachdb/pebble/commit/31434407) sstable: increment BlockBytes and BlockReadDuration together Release note: none. Epic: none.
-
- Jun 10, 2024
-
-
Rail Aliiev authored
release-24.1.1-rc: ci: paginate all available check runs
-
- Jun 06, 2024
-
-
Michael Erickson authored
release-24.1.1-rc: sql/stats: evict stats cache entry if user-defined types have changed
-
- Jun 04, 2024
-
-
Yahor Yuzefovich authored
release-24.1.1-rc: backupccl: skip TestDataDriven_user_defined_functions (#125086) Co-Authored-By: Michael Butler <butler@cockroachlabs.com>
-
Arul Ajmani authored
Closes https://github.com/cockroachdb/cockroach/issues/122363 Release note: None
-
Rail Aliiev authored
release-24.1.1-rc: Merge `v24.1.0` tag onto `release-24.1.1-rc` staging branch
-
Celia La authored
-
- Jun 03, 2024
-
-
Michael Erickson authored
When adding table statistics to the stats cache, we decode histogram upper bounds into datums. If the histogram column uses a user-defined type, we hydrate the type and use this to decode. In statistics builder, these histogram upper bound datums are compared against datums in spans and constraints. The comparisons assume that the datums are of equivalent type, but if the user-defined type has changed sometime after loading the stats cache entry, this might not be true. If the user-defined type has changed, we need to evict and re-load the stats cache entry so that we decode histogram datums with a freshly- hydrated type. (We were already checking UDT versions when building the optTable in sql.(*optCatalog).dataSourceForTable, but the newly-built optTable used the existing table statistics instead of refreshing those, too.) Fixes: #124181 Release note (bug fix): Fix a bug where a change to a user-defined type could cause queries against tables using that type to fail with an error message like: "histogram.go:694: span must be fully contained in the bucket" The change to the user-defined type could come directly from an ALTER TYPE statement, or indirectly from an ALTER DATABASE ADD REGION or DROP REGION statement (which implicitly change the crdb_internal_region type). This bug has existed since UDTs were introduced in v20.2.
-
Rail Aliiev authored
Previously, we used the default API request to list check runs per SHA. In some cases the number of checks is greater than the default `30` per page. This PR adds logic to fetch all check runs. Epic: none Release note: None
-
- May 31, 2024
-
-
Rail Aliiev authored
release-24.1.1-rc: acceptance: use `docker compose` (part 2)
-
Michael Butler authored
Informs #124803 Release note: none
-
Rail Aliiev authored
release-24.1.1-rc: acceptance: use `docker compose`
-
- May 30, 2024
-
-
Rail Aliiev authored
Previously, we used docker-compose (V1) to run acceptance tests. docker compose is a plugin now and not a separate command, which supports V2 compose files. See https://docs.docker.com/compose/migrate/#what-are-the-differences-between-compose-v1-and-compose-v2 for the details. * Use `--compatibility` for acceptance tests in order to use the old style hostnames with underscores, because they are hard coded in the Kerberos server keys. * Update `--ansi` argument usage. * Remove deprecated `version` header. Epic: none Release note: None
-
Rail Aliiev authored
Previously, we used `docker-compose` (V1) to run acceptance tests. `docker compose` is a plugin now and not a separate command, which supports V2 compose files. See https://docs.docker.com/compose/migrate/#what-are-the-differences-between-compose-v1-and-compose-v2 for the details. Epic: none Release note: None
-
- May 29, 2024
-
-
Yahor Yuzefovich authored
release-24.1: stats: improve TestCreateStatsProgress
-
Pavel Kalinnikov authored
release-24.1: raft: re-enable config change safety
-
Rafi Shamim authored
release-24.1: ttljob: cleanup string formatting for stats queries
-
Rafi Shamim authored
release-24.1: tree,parser: fix round-tripping of StorageParameter
-
Rafi Shamim authored
release-24.1: schemachanger_test: increase shard count
-
Pavel Kalinnikov authored
This commit adds a test which ensures a config change is not proposed if the leader has another yet unapplied config change. Epic: none Release note: none
-
Rafi Shamim authored
release-24.1: pgwire: support results_buffer_size in connection string options
-
Rail Aliiev authored
release-24.1: release: automatically detect if version is latest
-
Andrew Baptist authored
release-24.1: kvclient: change the default circuit breaker to liveness
-
Pavel Kalinnikov authored
Config changes in this raft implementation require a safety constraint: the leader must not append a config change if it hasn't applied all config changes in its log. The DisableConfChangeValidation flag disables this check under the assumption that the state machine layer provides the equivalent guarantee. However, it is hard to argue that this is true in split leaseholder/leader scenarios. This commit re-enables this check, to bring the safety back. The other two state-machine-level checks concerned with entering and leaving joint configs can still be disabled. Epic: none Release note: none
-
Rail Aliiev authored
release-24.1: Update pkg/testutils/release/cockroach_releases.yaml
-
CRL Release bot authored
Update pkg/testutils/release/cockroach_releases.yaml with recent values. Epic: None Release note: None Release justification: test-only updates
-
- May 28, 2024
-
-
Adam Storm authored
release-24.1: import: mark import.constraint_validation cluster setting unsafe
-
Adam Storm authored
Mark the bulkio.import.constraint_validation.enabled cluster setting unsafe, since it could result in inconsistent data, and as such, should never be used on production clusters. Release note: None Epic: none Release justification: Small change to guard against user misuse.
-
Adam Storm authored
release-24.1: import: add ability to disable validation checks
-
Stan Rosenberg authored
release-24.1: roachtest: --use-spot now properly defaults to "no SpotVMs"
-
Yahor Yuzefovich authored
We recently saw a test failure in `TestCreateStatsProgress` with two problems. First, due to an overload of the VM, we failed to start the stats job within 45s, so the test failed with "progress is nil" error. Second, since we didn't close the channel that block the KV server, the server couldn't shutdown properly, so the failure was reported as a timeout. This commit addresses both of these by skipping the test under race or deadlock configs (which are likely to result in an overload) and adding a deferred function that closes the channel if it hasn't been closed yet to unblock the proper server shutdown. Additionally, it replaces the single node test cluster with a single server and removes some duplicated code. Release note: None
-
Rafi Shamim authored
Release note: None
-