Musknine commented on issue #15983: URL: https://github.com/apache/dolphinscheduler/issues/15983#issuecomment-2109171880
I have reproduced this issue. In version 3.2.x, it appears that the channel is reused and simply not closed. Keeping the connection was stored in a map seems to be intended for reusing the connection, but closing it after each use negates the purpose of reusing it and only adds complexity. We can add a logic to a handler to close the connection if no data has been transferred for a while, extending this period, for example, over 24 hours. However, upon a preliminary review of the code, versions 3.0 and 3.1 also seem to have this issue.  复现了这个问题。我看3.2.x好像就是复用channel,干脆不关闭了，将连接保存在map中应该是为了复用连接，但是每次调用就关闭根本就没有复用的意义了，反而引入了复杂度（可以加一个逻辑到一个handler里面，如果超过多久没有真正传输数据就关闭，将这个时间调大一点，比如超过24小时）. 但3.0和3.1初看代码都会有这个问题. -- 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]
