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

resetTS should use suitable status code #7411

Closed
lhy1024 opened this issue Nov 22, 2023 · 1 comment · Fixed by #7368
Closed

resetTS should use suitable status code #7411

lhy1024 opened this issue Nov 22, 2023 · 1 comment · Fixed by #7368
Assignees
Labels
severity/moderate type/bug The issue is confirmed as a bug.

Comments

@lhy1024
Copy link
Contributor

lhy1024 commented Nov 22, 2023

Bug Report

What did you do?

Test

What did you expect to see?

The server returns a suitable status code when meeting ErrEtcdTxnConflict

What did you see instead?

The server returns 403 when meeting any errors, but for temporary failure, we should return 503

https://datatracker.ietf.org/doc/html/rfc7231#section-6.6.4

What version of PD are you using (pd-server -V)?

master

@lhy1024 lhy1024 added type/bug The issue is confirmed as a bug. severity/moderate labels Nov 22, 2023
@lhy1024 lhy1024 self-assigned this Nov 22, 2023
@lhy1024
Copy link
Contributor Author

lhy1024 commented Nov 22, 2023

After discussion with @niubell, we will only fix it on master branch.

ti-chi-bot bot added a commit that referenced this issue Nov 22, 2023
close #7411

Signed-off-by: lhy1024 <admin@liudos.us>

Co-authored-by: ti-chi-bot[bot] <108142056+ti-chi-bot[bot]@users.noreply.github.com>
rleungx pushed a commit to rleungx/pd that referenced this issue Dec 1, 2023
close tikv#7411

Signed-off-by: lhy1024 <admin@liudos.us>

Co-authored-by: ti-chi-bot[bot] <108142056+ti-chi-bot[bot]@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
severity/moderate type/bug The issue is confirmed as a bug.
Projects
Development

Successfully merging a pull request may close this issue.

1 participant