Skip to content
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

Jump to bottom

clientv3: put at most once #8335

Merged
merged 4 commits into from
Aug 1, 2017
Merged

clientv3: put at most once #8335

merged 4 commits into from
Aug 1, 2017
+105 −60

Commits on Aug 1, 2017

  1. clientv3/integration: test client puts at most once on bad connection

    Anthony Romano committed Aug 1, 2017
    Configuration menu
    Copy the full SHA
    8385c66 View commit details
    Browse the repository at this point in the history

  2. clientv3: only retry mutable KV RPCs if no endpoints found 

    Was retrying when it shouldn't, causing multiple puts
    Anthony Romano committed Aug 1, 2017
    Configuration menu
    Copy the full SHA
    4669aaa View commit details
    Browse the repository at this point in the history

  3. ordering: use default clients to populate etcd data 

    Switching endpoints on the same client was triggering balancer
reconnect errors that should be tested in clientv3/integration.
    Anthony Romano committed Aug 1, 2017
    Configuration menu
    Copy the full SHA
    10db031 View commit details
    Browse the repository at this point in the history

  4. clientv3/integration: test Put succeeds following SetEndpoint 

    Still gets transport closing errors, but no unavailable endpoint errors.
    Anthony Romano committed Aug 1, 2017
    Configuration menu
    Copy the full SHA
    fdba9e5 View commit details
    Browse the repository at this point in the history