dark-spark2 opened a new issue #9467: Ingestion fails on 'Connection reset by peer' when using native parallel ingestion URL: https://github.com/apache/druid/issues/9467 ### Affected Version druid 0.17 ### Description When running native ingestion with "index_parallel" on druid 0.17. I receive the following error: `java.io.IOException: java.lang.RuntimeException: java.util.concurrent.ExecutionException: java.io.IOException: Connection reset by peer at org.apache.druid.java.util.common.FileUtils.copyLarge(FileUtils.java:311) ~[druid-core-0.17.0.jar:0.17.0] at org.apache.druid.indexing.common.task.batch.parallel.PartialSegmentMergeTask.fetchSegmentFile(PartialSegmentMergeTask.java:261) ~[druid-indexing-service-0.17.0.jar:0.17.0] at org.apache.druid.indexing.common.task.batch.parallel.PartialSegmentMergeTask.fetchSegmentFiles(PartialSegmentMergeTask.java:236) ~[druid-indexing-service-0.17.0.jar:0.17.0] at org.apache.druid.indexing.common.task.batch.parallel.PartialSegmentMergeTask.runTask(PartialSegmentMergeTask.java:178) ~[druid-indexing-service-0.17.0.jar:0.17.0] at org.apache.druid.indexing.common.task.batch.parallel.PartialGenericSegmentMergeTask.runTask(PartialGenericSegmentMergeTask.java:44) ~[druid-indexing-service-0.17.0.jar:0.17.0] at org.apache.druid.indexing.common.task.AbstractBatchIndexTask.run(AbstractBatchIndexTask.java:138) ~[druid-indexing-service-0.17.0.jar:0.17.0] at org.apache.druid.indexing.overlord.SingleTaskBackgroundRunner$SingleTaskBackgroundRunnerCallable.call(SingleTaskBackgroundRunner.java:419) [druid-indexing-service-0.17.0.jar:0.17.0] at org.apache.druid.indexing.overlord.SingleTaskBackgroundRunner$SingleTaskBackgroundRunnerCallable.call(SingleTaskBackgroundRunner.java:391) [druid-indexing-service-0.17.0.jar:0.17.0] at java.util.concurrent.FutureTask.run(FutureTask.java:266) [?:1.8.0_232] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) [?:1.8.0_232] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) [?:1.8.0_232]` I am sending the following task to overlord: `{ "type" : "index_parallel", "spec" : { "ioConfig" : { "type": "index_parallel", "inputSource": { "type": "s3", "prefixes": ["s3://filePAth"] }, "inputFormat": { "type": "json" } }, "dataSchema" : { "dataSource" : "test_batch", "granularitySpec" : { "type" : "uniform", "segmentGranularity" : "HOUR", "queryGranularity" : "HOUR", "intervals" : ["2018-10-06/2018-10-07"] }, "dimensionsSpec" : { "dimensions" : [ "filed1","field2","field3" ] }, "timestampSpec" : { "format" : "auto", "column" : "timestamp" }, }, "tuningConfig" : { "type": "index_parallel", "maxNumConcurrentSubTasks": 2, "partitionsSpec" : { "type": "single_dim", "targetRowsPerSegment": 100000, "partitionDimension": "field1" } } } } ` The strange thing is that when removing the "partitionSpec" everything works well. Thanks.
---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: [email protected] With regards, Apache Git Services --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
