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

NTS pool-ke should be more resilient. #1248

Closed
squell opened this issue Dec 8, 2023 · 0 comments · Fixed by #1263
Closed

NTS pool-ke should be more resilient. #1248

squell opened this issue Dec 8, 2023 · 0 comments · Fixed by #1263

Comments

@squell
Copy link
Member

squell commented Dec 8, 2023 •
edited
Loading

Right now if some "downstream" NTS-KE servers result in errors, the entire NTS-pool is "poisoned" by this (i.e. returns an error to the client, instead of just ignoring the faulty NTS-KE server).

Note, this is a different issue than #1246, although it is of course related to it.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
1 participant
@squell