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

Timeout Issue while Connecting Multiple Instance #1691

Open
pratiyushray opened this issue Oct 22, 2024 · 0 comments
Open

Timeout Issue while Connecting Multiple Instance #1691

pratiyushray opened this issue Oct 22, 2024 · 0 comments
Labels
kind/bug Something isn't working

Comments

@pratiyushray
Copy link

ISSUE : Timeout Issue while connecting multiple instances.

In our project, when we are fetching data from three different instances, for example Instance A, Instance B, Instance C. In this scenario, assume that it is connecting to Instance A successfully, but from Instance B after connection, it is taking more than 300 second, and then throwing error ETIMEDOUT, which is basically Timeout and after 300 seconds, it is throwing error over front end and what we want, If Instance B is failing just throw data of other instances at least.

Possible Solution

  1. Possible solution, that return Instance A data and reduce the Timeout around 30 seconds and also return Instance C data. Don't throw error for all the three Instances. If we are fetching only from one Argo Instance then it is fine to work with but if multiple instances are there then this is the issue I am facing.
@pratiyushray pratiyushray added the kind/bug Something isn't working label Oct 22, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant