yihua opened a new issue #4528: URL: https://github.com/apache/hudi/issues/4528
**Describe the problem you faced** When following the [Quick Start guide](https://github.com/apache/hudi/tree/master/hudi-kafka-connect) of Kafka Connect Sink for Hudi with Hive sync, the sink connector gets stuck after the first delta commit. **To Reproduce** Steps to reproduce the behavior: Following the [Quick Start guide](https://github.com/apache/hudi/tree/master/hudi-kafka-connect) till Step 8. **Expected behavior** * Kafka version: 3.0.0. Kafka server, Zookeeper running locally. * Confluent version: 7.0.1 Schema registry running locally. * Hudi version : 0.11.0-SNAPSHOT from master, at commit 8718c30324ccea24c847ad4c540145a161a0a331 * Spark version : 2.4.4 Docker demo setup * Hive version : Docker demo setup * Hadoop version : Apache Hive (version 2.3.3) Driver: Hive JDBC (version 1.2.1.spark2) * Storage (HDFS/S3/GCS..) : HDFS * Running on Docker? (yes/no) : yes **Additional context** It seems that timeouts happen in the connector based on the stacktrace. Steps 1-7 work fine, i.e., using local file system without Hive sync for the sink connector works. **Stacktrace** ``` [2022-01-06 13:17:50,741] DEBUG [hudi-sink|task-2] Ignored idle endpoint SocketChannelEndPoint@226b92f{/127.0.0.1:52255<->/127.0.0.1:52204,CLOSED,fill=-,flush=-,to=30007/30000}{io=1/1,kio=-1,kro=-1}->HttpConnection@729214bd[p=HttpParser{s=CLOSE,0 of -1},g=HttpGenerator@3da9dbe9{s=START}]=>HttpChannelOverHttp@431bb314{r=5,c=false,c=false/false,a=IDLE,uri=null,age=0} (org.apache.hudi.org.eclipse.jetty.io.AbstractEndPoint:419) [2022-01-06 13:17:50,922] DEBUG [hudi-sink|task-0] SocketChannelEndPoint@6a571264{/127.0.0.1:52268<->/127.0.0.1:52208,OSHUT,fill=FI,flush=-,to=30005/30000}{io=1/1,kio=1,kro=1}->HttpConnection@1a8bb631[p=HttpParser{s=CLOSE,0 of -1},g=HttpGenerator@3016b9ad{s=START}]=>HttpChannelOverHttp@2b6a185f{r=1,c=false,c=false/false,a=IDLE,uri=null,age=0} idle timeout check, elapsed: 30005 ms, remaining: -5 ms (org.apache.hudi.org.eclipse.jetty.io.IdleTimeout:156) [2022-01-06 13:17:50,922] DEBUG [hudi-sink|task-0] SocketChannelEndPoint@6a571264{/127.0.0.1:52268<->/127.0.0.1:52208,OSHUT,fill=FI,flush=-,to=30005/30000}{io=1/1,kio=1,kro=1}->HttpConnection@1a8bb631[p=HttpParser{s=CLOSE,0 of -1},g=HttpGenerator@3016b9ad{s=START}]=>HttpChannelOverHttp@2b6a185f{r=1,c=false,c=false/false,a=IDLE,uri=null,age=0} idle timeout expired (org.apache.hudi.org.eclipse.jetty.io.IdleTimeout:163) [2022-01-06 13:17:50,922] DEBUG [hudi-sink|task-0] onFail FillInterest@4b45e710{AC.ReadCB@1a8bb631{HttpConnection@1a8bb631::SocketChannelEndPoint@6a571264{/127.0.0.1:52268<->/127.0.0.1:52208,OSHUT,fill=FI,flush=-,to=30005/30000}{io=1/1,kio=1,kro=1}->HttpConnection@1a8bb631[p=HttpParser{s=CLOSE,0 of -1},g=HttpGenerator@3016b9ad{s=START}]=>HttpChannelOverHttp@2b6a185f{r=1,c=false,c=false/false,a=IDLE,uri=null,age=0}}} (org.apache.hudi.org.eclipse.jetty.io.FillInterest:134) java.util.concurrent.TimeoutException: Idle timeout expired: 30005/30000 ms at org.apache.hudi.org.eclipse.jetty.io.IdleTimeout.checkIdleTimeout(IdleTimeout.java:166) at org.apache.hudi.org.eclipse.jetty.io.IdleTimeout$1.run(IdleTimeout.java:50) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) at java.lang.Thread.run(Thread.java:748) ``` Fullstack trace: https://gist.github.com/yihua/6449b9aaada32b51b0baf7663aa0763b -- 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. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
