[
https://issues.apache.org/jira/browse/GOBBLIN-1828?focusedWorklogId=859945&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-859945
]
ASF GitHub Bot logged work on GOBBLIN-1828:
-------------------------------------------
Author: ASF GitHub Bot
Created on: 01/May/23 22:39
Start Date: 01/May/23 22:39
Worklog Time Spent: 10m
Work Description: dtspslhh commented on code in PR #3690:
URL: https://github.com/apache/gobblin/pull/3690#discussion_r1181943474
##########
gobblin-core/src/main/java/org/apache/gobblin/writer/PartitionedDataWriter.java:
##########
@@ -170,9 +175,12 @@ public DataWriter<D> get() {
try {
log.info(String.format("Adding one more writer to
loading cache of existing writer "
+ "with size = %d", partitionWriters.size()));
- return createPartitionWriter(key);
- } catch (IOException e) {
+ Future<DataWriter<D>> future =
createWriterPool.submit(() -> createPartitionWriter(key));
+ return future.get(writeTimeoutInterval,
TimeUnit.SECONDS);
Review Comment:
The builder shares the timeout interval with writeTimeoutInterval. I saw you
made a couple commit tuning the default writeTimeoutInterval. Will that be a
concern if we explicitly set it?
Issue Time Tracking
-------------------
Worklog Id: (was: 859945)
Time Spent: 0.5h (was: 20m)
> 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: 0.5h
> 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)
