mattcasters commented on issue #5970: URL: https://github.com/apache/hop/issues/5970#issuecomment-3630920214
For really high throughput systems where connections are made and closed very quickly, it's important to remember that there is a period in which a network socket is kept in time_wait state (usually 1 or 2 minutes). Database connection pooling code was removed at some point because it rarely if ever got used and usually in a bad way. However, that doesn't mean that users can't create scenarios in which a situation occurs in which a lot of connections are made and closed in succession. If it's only reading from a database, you could try to run the looping pipeline or workflow in transactional mode forcing the use of a single database connection. See also: https://hop.apache.org//manual/latest/pipeline/pipeline-run-configurations/native-local-pipeline-engine.html -- 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]
