Commit Graph

1805 Commits

Author SHA1 Message Date
13c0f75b7d Merge pull request #17877 from tjungblu/17872_status
add quota to endpoint status response
2024-05-03 13:03:23 +01:00
c4e3b61a1c Record operation from failpoint injection
Signed-off-by: Marek Siarkowicz <siarkowicz@google.com>
2024-05-01 19:20:22 +02:00
d31caaec4a Merge pull request #17793 from mneverov/fix-quorum-check
Fix remove member failed.
2024-04-30 19:52:14 +01:00
6a1e28a519 Merge pull request #17890 from serathius/robustness-lease-revoke
Add LeaseRevoke request to WAL parsing
2024-04-29 13:33:32 +02:00
133576899c gofail: show error messages returned by gofail HTTP endpoints
Upon HTTP request error from fetchFailpointsBody, PUT and DELETE,
all of them will return an error message, which would be nice for
debugging if displayed.

Simplify `Enabled()` logic (linter suggestion)

Signed-off-by: Chun-Hung Tseng <henrybear327@gmail.com>
2024-04-28 05:49:24 +08:00
1e7dd97e3b Add LeaseRevoke request to WAL parsing
Signed-off-by: Marek Siarkowicz <siarkowicz@google.com>
2024-04-27 12:04:27 +02:00
0bd7008eea Merge pull request #17878 from callthingsoff/omit_conversion_using_verb_s
all: don't convert byte slice to string when using verb %s
2024-04-26 16:43:54 +02:00
b36d9b2156 Merge pull request #17731 from serathius/robustness-wal-validate-watch
Robustness wal validate watch
2024-04-26 08:37:33 +02:00
2de719dea4 Use WAL persisted request to validate watch
Signed-off-by: Marek Siarkowicz <siarkowicz@google.com>
2024-04-25 21:11:37 +02:00
dafadd13c1 all: don't convert byte slice to string when using verb %s
This is unnecessary, as the documentation for 'go doc fmt' says:
%s the uninterpreted bytes of the string or slice

Signed-off-by: Jes Cok <xigua67damn@gmail.com>
2024-04-25 23:34:52 +08:00
bdcff246cb add quota to endpoint status response
This adds the configured backend quota bytes to the endpoint status response.
related discussion in #17821

Signed-off-by: Thomas Jungblut <tjungblu@redhat.com>
2024-04-25 16:44:20 +02:00
9027014adb Merge pull request #17827 from siyuanfoundation/flaky
robustness: Add option to not overwrite results dir.
2024-04-24 22:48:02 +02:00
3c3b76cea1 robustness: not overwrite results dir by giving each dir a unique name.
Signed-off-by: Siyuan Zhang <sizhang@google.com>
2024-04-24 12:36:55 -07:00
a601652b5d Merge pull request #17863 from ivanvc/address-remaining-var-naming-linter-warnings
Address remaining var naming linter warnings
2024-04-24 10:09:39 +01:00
96d619459b Merge pull request #17734 from MadhavJivrajani/toolchain-directive
tests: set GOTOOLCHAIN var for report validation
2024-04-24 09:25:07 +02:00
5cbc8c950e Merge pull request #17841 from henrybear327/dependencies/04_22_2024
[2024-04-22] Bump dependency updates identified by dependabot
2024-04-24 09:24:00 +02:00
7300abc552 tests/common: address var-naming lint warnings
Signed-off-by: Ivan Valdes <ivan@vald.es>
2024-04-23 20:09:06 -07:00
856847d89b tests: set GOTOOLCHAIN var for report validation
Set GOTOOLCHAIN directive in order to successfully run tests
from root. Else, go will try and download a family of releases
(of the form 1.x), which are not published binaries.

Signed-off-by: Madhav Jivrajani <madhav.jiv@gmail.com>
2024-04-23 14:44:51 +05:30
9fcde37447 Persist member data with lazyfs enabled
Discovered turning off LazyFS before creating the report might result in
empty server directory. This PR moves cluster shutdown to defer executed
after we generate report and copies the data from lazyfs directory.

Signed-off-by: Marek Siarkowicz <siarkowicz@google.com>
2024-04-23 10:19:05 +02:00
45eb0110b6 dependency: bump golang.org/x/sync from 0.6.0 to 0.7.0
Reference:
- https://github.com/etcd-io/etcd/pull/17848

Signed-off-by: Chun-Hung Tseng <henrybear327@gmail.com>
2024-04-22 19:44:58 +02:00
f696c4c749 dependency: bump github.com/prometheus/common from 0.52.3 to 0.53.0
References:
- https://github.com/etcd-io/etcd/pull/17839
- https://github.com/etcd-io/etcd/pull/17840

Signed-off-by: Chun-Hung Tseng <henrybear327@gmail.com>
2024-04-22 19:44:58 +02:00
dd4e35a585 Merge pull request #17815 from fuweid/repro-17780
[RFC] fix revision loss issue caused by compaction - 17780
2024-04-22 18:15:44 +01:00
062a0ea057 Merge pull request #17825 from serathius/robustness-qps
Don't require minimal for failpoint injection period
2024-04-22 19:03:42 +02:00
7d1d4cb3a9 Merge pull request #17835 from serathius/robustness-watch-error
Handle watch responses with error
2024-04-22 14:44:00 +02:00
3469254e26 Merge pull request #17836 from sharathsivakumar/shsi/deps_1
Manually bump dependencies
2024-04-22 12:26:27 +01:00
9e938abd91 dependency: bump golang.org/x/net from 0.23.0 to 0.24.0
Signed-off-by: Sharath Sivakumar <mailssr9@gmail.com>
2024-04-21 23:14:29 +02:00
80c5690bb9 dependency: bump go.opentelemetry.io/contrib/instrumentation/google.golang.org/grpc/otelgrpc from 0.49.0 to 0.50.0
Signed-off-by: Sharath Sivakumar <mailssr9@gmail.com>
2024-04-21 22:58:17 +02:00
a392758755 dependency: bump github.com/prometheus/client_model from 0.6.0 to 0.6.1
Signed-off-by: Sharath Sivakumar <mailssr9@gmail.com>
2024-04-21 22:54:47 +02:00
81d7b2cb3d dependency: bump github.com/prometheus/common from 0.51.1 to 0.52.3
Signed-off-by: Sharath Sivakumar <mailssr9@gmail.com>
2024-04-21 22:46:41 +02:00
fa9e9504ad Handle watch responses with error
Signed-off-by: Marek Siarkowicz <siarkowicz@google.com>
2024-04-21 20:49:49 +02:00
a097a3b39d Merge pull request #17810 from serathius/robustness-revisions-between-progress
Validate revisions between progress notify
2024-04-21 20:04:25 +02:00
7173391154 tests/e2e: reproduce #17780
Signed-off-by: Wei Fu <fuweid89@gmail.com>
2024-04-21 18:12:00 +08:00
f285330d46 Don't require minimal for failpoint injection period
Signed-off-by: Marek Siarkowicz <siarkowicz@google.com>
2024-04-20 10:34:51 +02:00
964680c8d0 Validate delivery of events between progress notifies
Simplifying bookmarkable to just validate revision order between events
and progress notifies.

Use reliable to validate if events are missing, but still report
broken resumable if first event after revision is missing. It's easier
to have one place that validates event slices.

Signed-off-by: Marek Siarkowicz <siarkowicz@google.com>
2024-04-19 10:42:54 +02:00
6b0b4ce2b3 Increase test timeout (twice of sleep interval).
Signed-off-by: Max Neverov <neverov.max@gmail.com>
2024-04-18 14:47:11 +02:00
3b16aae947 Fix remove member failed.
Signed-off-by: Max Neverov <neverov.max@gmail.com>
2024-04-17 07:55:24 +02:00
5a8c8b703b Merge pull request #17807 from serathius/robustness-resumable-revision-zero
Resumable handles watch with revision zero
2024-04-16 19:41:53 +02:00
dc187ce6e8 Validate bookmarkable checks the last event before progress notify
Signed-off-by: Marek Siarkowicz <siarkowicz@google.com>
2024-04-16 09:17:40 +02:00
6f6647271f Merge pull request #17806 from serathius/robustness-watch-filter
Add filter validation to ensure watch only includes events within selector
2024-04-16 08:52:25 +02:00
842a0f3a35 tests: fix some typos in comments
Signed-off-by: coderwander <770732124@qq.com>
2024-04-16 13:59:41 +08:00
94a47a7cbd Resumable handles watch with revision zero
Signed-off-by: Marek Siarkowicz <siarkowicz@google.com>
2024-04-15 20:23:51 +02:00
042e7d1a0c Add filter validation to ensure watch only includes events within selector
Signed-off-by: Marek Siarkowicz <siarkowicz@google.com>
2024-04-15 20:05:08 +02:00
a95a307698 Add tests to watch validation
Signed-off-by: Marek Siarkowicz <siarkowicz@google.com>
2024-04-14 21:38:03 +02:00
569693be8d Utilize WAL to patch operation history
Signed-off-by: Marek Siarkowicz <siarkowicz@google.com>
2024-04-14 12:09:38 +02:00
452445e2d8 Merge pull request #17781 from serathius/robustness-read-limit
Remove limit from read requests after a failed write
2024-04-14 12:05:23 +02:00
2e6eebef85 Merge pull request #17759 from serathius/robustness-assumptions
Add explicit checks for assumptions in robustness test validation
2024-04-13 00:19:25 +02:00
d0bf8ddca4 Improve description for Kubernetes CAS operations
Signed-off-by: Marek Siarkowicz <siarkowicz@google.com>
2024-04-12 16:18:31 +02:00
cadfc407e9 Remove limit from read requests after a failed write
Limit can cause multiple request due to pagination.
For reads after a failed write we would like to return to normal write
request as soon as possible.

Signed-off-by: Marek Siarkowicz <siarkowicz@google.com>
2024-04-12 15:01:17 +02:00
f8de338ab2 Add explicit checks for assumptions in robustness test validation
Signed-off-by: Marek Siarkowicz <siarkowicz@google.com>
2024-04-12 14:18:22 +02:00
bfbfee0afa Merge pull request #17768 from serathius/robustness-success-rate
[Robustness] Collect failed read operations to calculate request success rate
2024-04-12 09:46:20 +02:00