Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Not working first primary master makes UI unavailble #529

Closed
kaikash opened this issue May 2, 2024 · 3 comments
Closed

Not working first primary master makes UI unavailble #529

kaikash opened this issue May 2, 2024 · 3 comments
Assignees
Labels

Comments

@kaikash
Copy link

kaikash commented May 2, 2024

Hello!

In case when first primary master doesn't work it makes UI not available, api/cluster-params/<cluster> fails with error

Oops! something went wrong. If the problem persists please report it via Bug Reporter.
{"message":"timeout of 5000ms exceeded","code":0,"yt_javascript_wrapper":{}}

It always takes the first master and makes get request to its orchid and this request fails with Connection timed out error. Seems to be because of this:

const [primary_path] = [...Object.keys(ypath.getValue(primaryMasterResult.output))];

@ma-efremoff
Copy link
Collaborator

ma-efremoff commented May 6, 2024

Are you using address of your primary master as proxy-field in your cluster-config.json?
UI uses the field for all requests (except heavy ones).

@kaikash
Copy link
Author

kaikash commented May 17, 2024

No, we are using http proxies for all communication between UI and YT. In turn, http proxy makes requests to first master orchid, which can be unavalable.

@vrozaev vrozaev self-assigned this May 31, 2024
vrozaev added a commit that referenced this issue Jun 12, 2024
…ers if first one did not responded correctrly [#529]
vrozaev added a commit that referenced this issue Jun 12, 2024
…ers if first one did not responded correctrly [#529]
vrozaev added a commit that referenced this issue Jun 12, 2024
…ers if first one did not responded correctrly [#529]
vrozaev added a commit that referenced this issue Jun 14, 2024
…ers if first one did not responded correctrly [#529]
vrozaev added a commit that referenced this issue Jun 18, 2024
…ers if first one did not responded correctrly [#529]
vrozaev added a commit that referenced this issue Jun 18, 2024
…ers if first one did not responded correctrly [#529]
@vrozaev
Copy link
Collaborator

vrozaev commented Jun 28, 2024

@kaikash should be fixed now, please check.

# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants