[ 
https://issues.apache.org/jira/browse/GOBBLIN-1828?focusedWorklogId=859934&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-859934
 ]

ASF GitHub Bot logged work on GOBBLIN-1828:
-------------------------------------------

                Author: ASF GitHub Bot
            Created on: 01/May/23 21:27
            Start Date: 01/May/23 21:27
    Worklog Time Spent: 10m 
      Work Description: ZihanLi58 opened a new pull request, #3690:
URL: https://github.com/apache/gobblin/pull/3690

   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-1828
   
   
   ### Description
   - [ ] Here are some details about my PR, including screenshots (if 
applicable):
   
   When HDFS slowness happens, we can get stuck in creating writer phase and 
never proceed further. So we want to add a timeout guarantee there to make sure 
to fail earlier and retry in this case. 
   
   
   ### Tests
   - [ ] My PR adds the following unit tests __OR__ does not need testing for 
this extremely good reason:
   Add new unit test and run job to make sure timeout can cause the task to 
retry
   
   ### 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: 859934)
    Remaining Estimate: 0h
            Time Spent: 10m

> Implement Timeout for Creating Writer Functionality
> ---------------------------------------------------
>
>                 Key: GOBBLIN-1828
>                 URL: https://issues.apache.org/jira/browse/GOBBLIN-1828
>             Project: Apache Gobblin
>          Issue Type: Improvement
>            Reporter: Zihan Li
>            Priority: Major
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> When HDFS slowness happens, we can get stuck in creating writer phase and 
> never proceed further. So we want to add a timeout guarantee there to make 
> sure to fail earlier and retry in this case. 



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to