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

Hive: Reconnect client if connection exception is wrapped in RuntimeE… #2844

Closed
wants to merge 1 commit into from

Conversation

dengzhhu653
Copy link
Member

…xception

ALTER_TABLE.invoke(client, database, tableName, hmsTable, envContext);
wraps the internal exception into a RuntimeException and throws, the Hive client may fail to reconnect if if the internal exception is an exception that should reconnect. For example,

java.lang.RuntimeException: org.apache.thrift.transport.TTransportException: java.net.SocketTimeoutException: Read timed out
        at org.apache.iceberg.relocated.com.google.common.base.Throwables.propagate(Throwables.java:241)
        at org.apache.iceberg.common.DynMethods$UnboundMethod.invoke(DynMethods.java:80)

Reusing the timeout client may result to org.apache.thrift.TApplicationException: get_table failed: out of sequence response.

@szehon-ho
Copy link
Collaborator

I think this may not necessary anymore because of #3099, what do you think?

@dengzhhu653
Copy link
Member Author

I think this may not necessary anymore because of #3099, what do you think?

yeap, it's much better to use the proxy client for retrying, thank you for the feedback and comment.

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

Successfully merging this pull request may close these issues.

2 participants