Details
-
Bug
-
Resolution: Fixed
-
Major
-
1.8.1
-
Security Level: Public
-
None
Description
Past experience and various anecdotal evidence shows that configuring many clients to connect to the streaming API of one node causes that node to use an excessive amount of RAM and possibly impacts the overall performance of that node either due to CPU consumption, swapping, or just general load.
Conceptually this should not be the case...this bug is meant to track the known and open issue.