-
Notifications
You must be signed in to change notification settings - Fork 39k
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
etcd v3 initial change #22604
etcd v3 initial change #22604
Conversation
GCE e2e build/test failed for commit 21b84e806130aae5d328a98cde3aea80e1582c72. Please reference the list of currently known flakes when examining this failure. If you request a re-test, you must reference the issue describing the flake. |
Labelling this PR as size/XS |
GCE e2e build/test failed for commit af90a13f0a14bc3ff8f17a787397bfa6ad6c27b7. Please reference the list of currently known flakes when examining this failure. If you request a re-test, you must reference the issue describing the flake. |
GCE e2e build/test failed for commit 3afddb73ad53e2d4bb8e741a9248792c556ecb3a. Please reference the list of currently known flakes when examining this failure. If you request a re-test, you must reference the issue describing the flake. |
GCE e2e build/test failed for commit 03719896063dce058eb90b60d59665810e116a2e. Please reference the list of currently known flakes when examining this failure. If you request a re-test, you must reference the issue describing the flake. |
@hongchaodeng - can you please move Godeps update to a separate PR? It would be so much easier to review this PR then, because github doesn't support well PRs with so many files... Also, I assume that with upgraded Godeps, etcd v2 in current setup will still work, right? |
GCE e2e build/test failed for commit 03719896063dce058eb90b60d59665810e116a2e. Please reference the list of currently known flakes when examining this failure. If you request a re-test, you must reference the issue describing the flake. |
@hongchaodeng could you squash the helper commits please, I can review 2-day. |
@timothysc - I didn't review this, just because we don't want to have it in 1.2. We are explicitly not merging big changes that are not going to be picked to 1.2 now. |
@wojtek-t no worries, I had some time so just getting back into the fray, and wanted to keep an eye on this one. |
GCE e2e build/test failed for commit 66d6e033afe8f896ad8a575799a63cd3f5b850da. Please reference the list of currently known flakes when examining this failure. If you request a re-test, you must reference the issue describing the flake. |
GCE e2e build/test failed for commit d2be21e37b440455b03d36730e6d425e813a6f6e. Please reference the list of currently known flakes when examining this failure. If you request a re-test, you must reference the issue describing the flake. |
295749b
to
21f089f
Compare
I am constantly getting verify error:
@timothysc Can you help with that? |
GCE e2e build/test failed for commit 295749b5f50c3a6439e3f0c8e54c67ecb3c76820. Please reference the list of currently known flakes when examining this failure. If you request a re-test, you must reference the issue describing the flake. |
GCE e2e build/test failed for commit 21f089f27f94440ce6713630168f368c411cfaa1. Please reference the list of currently known flakes when examining this failure. If you request a re-test, you must reference the issue describing the flake. |
I've added few comments. @hongchaodeng Can't we merge first two commits as a separate PR? We could do it now. |
Add last commit "add custom storage error". |
GCE e2e build/test passed for commit d94084710cb0de99de0d0ddf44306f43cff4a8f4. |
GCE e2e build/test passed for commit 39cfb67582b0b46f98d670fa2cd2141126e20861. |
GCE e2e build/test passed for commit 6ce4bb038b2541080fa70f823f4f3b82624122ef. |
@@ -711,3 +710,21 @@ func (h *etcdHelper) addToCache(index uint64, obj runtime.Object) { | |||
metrics.ObserveNewEntry() | |||
} | |||
} | |||
|
|||
func convertToStorageErrorIfPossible(err error, key string, rv uint64) error { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
just ToStorageErr?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
is this an etcd specific func? or we might add other potential kv error types into switch cases?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
"storage/" handles only four errors in special. See here.
Not sure about other error types ATM.
@hongchaodeng PR needs rebase |
Labelling this PR as size/L |
GCE e2e build/test passed for commit 97a1ed882ce2afaebbd79e81b0a26ac50dee6169. |
GCE e2e build/test passed for commit e0ee1e0846ad3120f10b6aa9c129340062af4a04. |
GCE e2e build/test passed for commit bc8a262. |
Rebased and addressed comments. |
I moved out the storage error commit into another PR (#23295) for easy review. PTAL. |
This PR is way too long. It's github's problem -- They should have better ways to show long discussion. Anyway, I'm gonna closing this. Once #23295 is merged, I will rebase and submit another PR with more KV methods and improvement of code quality. |
Created a new PR #23387 |
This serves as a follow up on #22448.
The conversation is good! Let's keep it up while working out some real code.
I'm initiating a few things here: