[Bug] [connectors-v2] The Hadoop Source/Sink fails with Unable to find valid Kerberos Ticket. #7809
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…d valid Kerberos Ticket.
Contributor
Author
|
Issue: #7805 |
Closed
3 tasks
Member
|
Thanks @shashwatsai ! |
Contributor
Author
|
@Hisoka-X , please review. Seatunnel Engine Screen grab: Seatunnel Client Screen grab: source/sink paths: |
Hisoka-X
reviewed
Oct 10, 2024
Comment on lines
319
to
322
| } catch (IOException e) { | ||
| throw e; | ||
| } catch (SeaTunnelRuntimeException e) { | ||
| throw new SeaTunnelRuntimeException(e.getSeaTunnelErrorCode(), e.getParams()); |
Member
There was a problem hiding this comment.
Suggested change
| } catch (IOException e) { | |
| throw e; | |
| } catch (SeaTunnelRuntimeException e) { | |
| throw new SeaTunnelRuntimeException(e.getSeaTunnelErrorCode(), e.getParams()); | |
| } catch (IOException | SeaTunnelRuntimeException e) { | |
| throw e; |
| try { | ||
| return userGroupInformation.doAs(action); | ||
| } catch (InterruptedException e) { | ||
| Thread.currentThread().interrupt(); |
Contributor
Author
There was a problem hiding this comment.
After catching the InterruptedException, thread's interrupt status is cleared, so we need to re-interrupt the thread, for the task threads to continue. CC: @Hisoka-X
| fileSystem.setWriteChecksum(false); | ||
| } | ||
|
|
||
| private <T> T execute(PrivilegedExceptionAction<T> action) throws IOException { |
Member
There was a problem hiding this comment.
Please add some comments about why we need execute method to run action?
Contributor
Author
There was a problem hiding this comment.
Thanks, added the necessary comments.
Contributor
Author
|
Results on Non Keberoised Cluster: 
|
fcb-xiaobo
pushed a commit
to fcb-xiaobo/seatunnel
that referenced
this pull request
Oct 11, 2024
…d valid Kerberos Ticket. (apache#7809)
CosmosNi
pushed a commit
to CosmosNi/seatunnel
that referenced
this pull request
Oct 15, 2024
…d valid Kerberos Ticket. (apache#7809)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Purpose of this pull request
The Hadoop Source/Sink fails with Unable to find valid Kerberos Ticket. In HadoopFileSystemProxy, the UserGroupInformation Object is tightly bound to the security context of the initiating thread. If we try to run the privileged actions that require the subject's security context, it fails with the error,
We can attach Security Context of the Specified Subject to the thread Performing Action by using UserGroupInformation#doAs, it attaches the subject's security context for time being till the action is running.
This issue can be reproduced,
Example:
Does this PR introduce any user-facing change?
No
How was this patch tested?
Check list
New License Guide
release-note.