LeonYoah opened a new issue, #6678:
URL: https://github.com/apache/seatunnel/issues/6678

   ### Search before asking
   
   - [X] I had searched in the 
[issues](https://github.com/apache/seatunnel/issues?q=is%3Aissue+label%3A%22bug%22)
 and found no similar issues.
   
   
   ### What happened
   
   When jdbc- > s3File is executed using the local mode, it occurs 
sporadically, good and bad in most cases, but there is no problem with using 
the cluster mode: 
   
![image](https://github.com/apache/seatunnel/assets/95527066/f65fe0eb-ee49-4e61-a2e1-af19c609b326)
   
   I probably searched for this error about using aws-sdk: Connection pool shut 
down, the related issues is 
https://github.com/awslabs/amazon-sqs-java-messaging-lib/issues/96. 
   It mentions the problem of multithreaded connection pooling, so I initially 
guess whether it is possible that there is a [aggregate commit] operation after 
[S3file] executes the [sink] operation, but the [sink] operation executes the 
close method, which causes the [rename] of [commit] to report an error, 
indicating that the connection pool is closed, but why the lcoal mode is good 
and bad, the cluster mode is not a problem. 
   And I've tried the 2.3.3 local mode, and that's not the case.
   [error.txt](https://github.com/apache/seatunnel/files/14928339/error.txt)
   
   
   ### SeaTunnel Version
   
   2.3.4
   
   ### SeaTunnel Config
   
   ```conf
   env {
     execution.parallelism = 1
     job.mode = "BATCH"
   }
   
   source {
        Jdbc {
                result_table_name = "TEST_100W"
                query = "select * from SYSDBA.TEST_100W limit 10"
                fetch_size = 5000
                table_path = "SYSDBA.TEST_100W"
                driver = "com.mysql.cj.jdbc.Driver"
                url = "jdbc:mysql://10.28.23.xxx:3306/test"
                user = "test"
                password ="xxx"
        } 
   }
   sink {
     S3File {
       source_table_name = "aa"
       path = "/xugurtp/seatunnel/tmp/6af80b38f3434aceb573cc65b9cd12216a/3918"
       bucket = "s3a://xugurtp"
       fs.s3a.endpoint = "http://10.28.23.xxx:9010";
       fs.s3a.aws.credentials.provider = 
"org.apache.hadoop.fs.s3a.SimpleAWSCredentialsProvider"
       access_key = "xxxx"
       secret_key = "xxxxxxx"
       custom_filename = true
       file_name_expression = "output_params"
       file_format_type = "json"
       is_enable_transaction = false
       ##sink_columns = ["ID"]
     }
   }
   ```
   
   
   ### Running Command
   
   ```shell
   ./bin/seatunnel.sh  -e local --config job/s3_sink.conf
   ```
   
   
   ### Error Exception
   
   ```log
   2024-04-10 14:02:28,387 ERROR [.c.FileSinkAggregatedCommitter] 
[hz.main.generic-operation.thread-43] - commit aggregatedCommitInfo error, 
aggregatedCommitInfo = 
FileAggregatedCommitInfo(transactionMap={/tmp/seatunnel/seatunnel/830321799827816449/3eff006528/T_830321799827816449_3eff006528_0_1={/tmp/seatunnel/seatunnel/830321799827816449/3eff006528/T_830321799827816449_3eff006528_0_1/NON_PARTITION/output_params_0.json=/xugurtp/seatunnel/tmp/6af80b38f3434aceb573cc65b9cd12216a/3918/output_params_0.json}},
 partitionDirAndValuesMap={}) 
   java.lang.IllegalStateException: Connection pool shut down
           at 
com.amazonaws.thirdparty.apache.http.util.Asserts.check(Asserts.java:34) 
~[aws-java-sdk-bundle-1.11.271.jar:?]
           at 
com.amazonaws.thirdparty.apache.http.pool.AbstractConnPool.lease(AbstractConnPool.java:184)
 ~[aws-java-sdk-bundle-1.11.271.jar:?]
           at 
com.amazonaws.thirdparty.apache.http.impl.conn.PoolingHttpClientConnectionManager.requestConnection(PoolingHttpClientConnectionManager.java:251)
 ~[aws-java-sdk-bundle-1.11.271.jar:?]
   ```
   
   
   ### Zeta or Flink or Spark Version
   
   local模式
   
   ### Java or Scala Version
   
   1.8
   
   ### Screenshots
   
   _No response_
   
   ### Are you willing to submit PR?
   
   - [ ] Yes I am willing to submit a PR!
   
   ### Code of Conduct
   
   - [X] I agree to follow this project's [Code of 
Conduct](https://www.apache.org/foundation/policies/conduct)
   


-- 
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]

Reply via email to