-
Notifications
You must be signed in to change notification settings - Fork 58
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Heap out of memory when using ReliableTopic with reconnect mode "ASYNC" [API-1514] #1347
Comments
If you can reproduce, can you run again and send the logs when the TRACE logging is on? const client = await Client.newHazelcastClient({
clusterName: '@FIXME YOUR CLUSTER NAME',
network: {
clusterMembers: [
'localhost:5701'
]
},
connectionStrategy: {
asyncStart: false,
reconnectMode: "ASYNC", // <----
connectionRetry: {
clusterConnectTimeoutMillis: -1
}
},
properties: {
'hazelcast.logging.level': 'TRACE'
}
}); |
Internal Jira issue: API-1514 |
Sure. This is the output:
The line cat output.txt | wc -l
3317205 |
Opened a fix PR #1377 Probably, the leak happens in the older versions of the client as well. We need to confirm. For example, the problematic |
@marinrusu1997 The memory leak is fixed. Thanks for reporting this. We appreciate it. |
Describe the bug
When using ReliableTopic and client tries to reconnect with reconnectMode "ASYNC", NodeJS process freezes and crashes with
FATAL ERROR: Reached heap limit Allocation failed - JavaScript heap out of memory
.Notice that when using reconnectMode "ON" this problem does not occur.
Expected behavior
Hazelcast client should be able to reconnect in the background and calls to
publish
should fail with error.Sample Code
Environment (please complete the following information):
Node.js client v16.14.2
Hazelcast client v5.1.0
Cluster size: 1 member running inside Docker container (Hazelcast v5.1.2)
Number of clients: 1 client
Operating system: macOS Monterey 12.5
Logs and stack traces:
The text was updated successfully, but these errors were encountered: