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.

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

etcdserver, auth: not cache a flag of auth status #4281

Merged
merged 1 commit into from
Jan 26, 2016

Conversation

mitake
Copy link
Contributor

@mitake mitake commented Jan 26, 2016

This commit removes a flag that indicates auth is enabled or disabled
because it doesn't have an invalidation mechanism.

Fixes #3601 and #3964

@mitake
Copy link
Contributor Author

mitake commented Jan 26, 2016

This commit removes a flag that indicates auth is enabled or disabled
because it doesn't have an invalidation mechanism.

Fixes etcd-io#3601 and etcd-io#3964
@xiang90
Copy link
Contributor

xiang90 commented Jan 26, 2016

LGTM. I am not sure about the performance impact. (after this change, even if you do not enable auth, there is an overhead). Ideally, we should run a benchmark test.

@mitake
Copy link
Contributor Author

mitake commented Jan 26, 2016

OK, I'll do benchmarking. Please wait for a while.

@xiang90
Copy link
Contributor

xiang90 commented Jan 26, 2016

@mitake Thanks a lot.

@mitake
Copy link
Contributor Author

mitake commented Jan 26, 2016

I run my benchmark of 10,000 key creation (https://github.com/mitake/etcd-things/blob/master/prioritize-leader-bench/bench.go , without prioritizing leader) on the master branch and this PR. There was no significant differenct:

  • master
real    1m32.631s
user    0m1.112s
sys     0m0.453s
  • this PR
real    1m32.812s
user    0m1.162s
sys     0m0.375s

I think this PR doesn't introduce significant overhead because current auth flag checking doesn't require quorum, just local lookup. I combined this PR and #3994 , that requires quorum in the auth flag checking. Actually, the overhead was easily observed.

  • this PR + quorum auth
real    2m15.012s
user    0m0.943s
sys     0m0.639s

Anyway, if we integrate auth into etcdserver, consistent and low overhead auth mechanism will be possible.

xiang90 added a commit that referenced this pull request Jan 26, 2016
etcdserver, auth: not cache a flag of auth status
@xiang90 xiang90 merged commit dd1bbaa into etcd-io:master Jan 26, 2016
@mitake mitake deleted the remove-cached-auth-flag branch January 26, 2016 05:55
@mitake
Copy link
Contributor Author

mitake commented Jan 28, 2016

@gyuho I think this commit should be backported to the bugfix releases for reviving the auth mechanism.

@xiang90
Copy link
Contributor

xiang90 commented Jan 28, 2016

@mitake I agree. Github was down while we were back-porting commits...

@mitake
Copy link
Contributor Author

mitake commented Jan 28, 2016

@xiang90 ah, I see :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants