You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@gobblin.apache.org by "ASF GitHub Bot (Jira)" <ji...@apache.org> on 2024/01/30 00:26:00 UTC
[jira] [Work logged] (GOBBLIN-1995) Kill the writer thread when timeout happens to release the lock
[ https://issues.apache.org/jira/browse/GOBBLIN-1995?focusedWorklogId=902445&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-902445 ]
ASF GitHub Bot logged work on GOBBLIN-1995:
-------------------------------------------
Author: ASF GitHub Bot
Created on: 30/Jan/24 00:25
Start Date: 30/Jan/24 00:25
Worklog Time Spent: 10m
Work Description: ZihanLi58 opened a new pull request, #3871:
URL: https://github.com/apache/gobblin/pull/3871
Dear Gobblin maintainers,
Please accept this PR. I understand that it will not be reviewed until I have checked off all the steps below!
### JIRA
- [ ] My PR addresses the following [Gobblin JIRA](https://issues.apache.org/jira/browse/GOBBLIN/) issues and references them in the PR title. For example, "[GOBBLIN-XXX] My Gobblin PR"
- https://issues.apache.org/jira/browse/GOBBLIN-1995
### Description
- [ ] Here are some details about my PR, including screenshots (if applicable):
Now when there is timeout happens talking with HDFS, we timeout and fail the job but the thread won't be killed in this case, and all other calls to HDFS will be blocked by this hanging thread.
### Tests
- [ ] My PR adds the following unit tests __OR__ does not need testing for this extremely good reason:
### Commits
- [ ] My commits all reference JIRA issues in their subject lines, and I have squashed multiple commits if they address the same issue. In addition, my commits follow the guidelines from "[How to write a good git commit message](http://chris.beams.io/posts/git-commit/)":
1. Subject is separated from body by a blank line
2. Subject is limited to 50 characters
3. Subject does not end with a period
4. Subject uses the imperative mood ("add", not "adding")
5. Body wraps at 72 characters
6. Body explains "what" and "why", not "how"
Issue Time Tracking
-------------------
Worklog Id: (was: 902445)
Remaining Estimate: 0h
Time Spent: 10m
> Kill the writer thread when timeout happens to release the lock
> -----------------------------------------------------------------
>
> Key: GOBBLIN-1995
> URL: https://issues.apache.org/jira/browse/GOBBLIN-1995
> Project: Apache Gobblin
> Issue Type: Improvement
> Reporter: Zihan Li
> Priority: Major
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Now when there is timeout happens talking with HDFS, we timeout and fail the job but the thread won't be released in this case, and all other calls to HDFS will be blocked by this hanging thread.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)