Skip to content

fix typo #5741

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.

Sign up for GitHub

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

Open
silentred wants to merge 1 commit into
base: master
Choose a base branch
from
+3 −3
Open

fix typo #5741

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 3 additions & 3 deletions keps/sig-api-machinery/4988-snapshottable-api-server-cache/README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -15,7 +15,7 @@
- [Consistency checking overhead](#consistency-checking-overhead)
- [Design Details](#design-details)
- [Snapshotting algorithm](#snapshotting-algorithm)
- [Hasing algorithm](#hasing-algorithm)
- [Hashing algorithm](#hashing-algorithm)
- [Test Plan](#test-plan)
- [Prerequisite testing updates](#prerequisite-testing-updates)
- [Unit tests](#unit-tests)
Expand Down Expand Up @@ -204,7 +204,7 @@ The results are promising:

Periodic execution of consistency checking will introduce additional overhead.
This load is not negligible, as it requires downloading and decoding data from etcd.
For saftly we still think it's important that feature is enabled by default,
For safty we still think it's important that feature is enabled by default,
however we want to leave an option to disable it.
For that we will introduce `DetectCacheInconsistency` feature gate in Beta.

Expand Down Expand Up @@ -240,7 +240,7 @@ At that point disabling inconsistency checks will no longer be needed.

[Clone()]: https://pkg.go.dev/github.com/google/btree#BTree.Clone

#### Hasing algorithm
#### Hashing algorithm

Every 5 minutes, for each resource, we calculate hash for each resource.
A non-consistent `LIST` request (`RV=0`) is sent to the watch cache to retrieve its latest available RV.
Expand Down