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

H2O client should be able to connect to a new cluster if the previous was stopped #8969

Closed
exalate-issue-sync bot opened this issue May 12, 2023 · 3 comments
Closed

H2O client should be able to connect to a new cluster if the previous was stopped #8969

exalate-issue-sync bot opened this issue May 12, 2023 · 3 comments
Assignees
@jakubhava
Labels
fixVersion/3.28.0.1

Comments

@exalate-issue-sync
Copy link

No description provided.

@exalate-issue-sync
Copy link
Author

Michal Kurka commented: Discussed on a call - a bigger issue, we will target next major

@exalate-issue-sync
Copy link
Author

Jakub Hava commented: This is already in progress on Sparkling Water side via the client-less approach. Closing as duplicate

@h2o-ops
Copy link
Collaborator

h2o-ops commented May 14, 2023

JIRA Issue Migration Info

Jira Issue: PUBDEV-6662
Assignee: Jakub Hava
Reporter: Jakub Hava
State: Closed
Fix Version: 3.28.0.1
Attachments: N/A
Development PRs: Available

Linked PRs from JIRA

#3672

@h2o-ops h2o-ops closed this as completed May 14, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@jakubhava jakubhava

Labels
fixVersion/3.28.0.1
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@jakubhava @h2o-ops