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

Waggle Dance fail to respond if one of the metastore becomes unresponsive #73

Closed
pradeepbhadani opened this issue May 15, 2018 · 1 comment · Fixed by #76
Closed

Waggle Dance fail to respond if one of the metastore becomes unresponsive #73

pradeepbhadani opened this issue May 15, 2018 · 1 comment · Fixed by #76
Assignees
@patduin

Comments

@pradeepbhadani
Copy link
Contributor

pradeepbhadani commented May 15, 2018 •
edited by patduin

If I have one Primary Metastore and n federated metastore and one of the metastore stop responding then client connecting to Waggle Dance thrift endpoint gets Thrift Exception and unable to query data/metadata of rest of the metastore.

Additional Info:

  • WD is running in prefixed mode.
@patduin patduin self-assigned this May 15, 2018
@patduin patduin mentioned this issue May 17, 2018
Merged
@patduin
Copy link
Contributor

patduin commented May 17, 2018

I've added a PR, problem was in the tunneled connections our connection check didn't check the actual metastore was responding at the end of the tunnel

@patduin patduin mentioned this issue Jun 7, 2018
Closed
@patduin patduin mentioned this issue Aug 1, 2018
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@patduin patduin

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Added client call to isOpen so the whole connection roundtrip is tested ExpediaGroup/waggle-dance
2 participants
@pradeepbhadani @patduin