Skip to content
Discussion options

You must be logged in to vote

All Seata processes have been stopped, so any file descriptors they held should have been released. Please check whether there are any zombie processes holding a large number of file descriptors. Restarting the Seata container also did not resolve the issue; the problem may be caused by other processes on the host affecting Seata.

Replies: 1 comment

Comment options

You must be logged in to vote
0 replies
Answer selected by funky-eyes
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
Q&A
Labels
None yet
2 participants