Why does the ETCD token mechanism need to carry the auth token revision?

[chuntaojun]

The revision is carried in the issued token. Each operation compares the revision. If it is less, it will trigger the client to re-apply for a token. The original idea was to use the revision mechanism to make the token expire. However, this seems too drastic. It is very likely to trigger a large-scale re-login process for clients to apply for tokens, and it is easy to overload the CPU due to the password verification logic.