nzw921rx commented on issue #10993: URL: https://github.com/apache/seatunnel/issues/10993#issuecomment-4611819708
@HuangZL-github Thank you for your report. I have carefully reviewed the logs you provided and found the following error. It seems to be a job exception caused by a link Kafka timeout. The evidence chain I have analyzed is as follows: 1. Job successfully scheduled from `pengdingQueue` to running ```text Job Id : 1114031989637251075 enter pending queue, current status:PENDING ,please wait task schedule Job Id : 1114031989637251075 enter pending queue, current status:PENDING ,please wait task schedule Job Id : 1114031989637251075 enter pending queue, current status:PENDING ,please wait task schedule Job Id : 1114031989637251075 enter pending queue, current status:PENDING ,please wait task schedule Job Id : 1114031989637251075 enter pending queue, current status:PENDING ,please wait task schedule Job Id : 1114031989637251075 enter pending queue, current status:PENDING ,please wait task schedule Job Id : 1114031989637251075 enter pending queue, current status:PENDING ,please wait task schedule Job Id : 1114031989637251075 enter pending queue, current status:PENDING ,please wait task schedule Job Id : 1114031989637251075 enter pending queue, current status:PENDING ,please wait task schedule Job ID: 1114031989637251075 has been scheduled and entered the next state. Current status: RUNNING ``` 2. Then when the Sink links to Kafka, timeout occurs ```java Caused by: org.apache.seatunnel.common.utils.SeaTunnelException: org.apache.kafka.common.errors.TimeoutException: Timeout expired after 60000ms while awaiting InitProducerId ``` -- 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]
