You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
My application uses an event store to keep track of events.
Initially, there's only one node (Node A) holding all the data (around 600 events, each about 4 KB).
When a second node (Node B) starts, it sends information about its latest events to Node A every 5 seconds.
Node A then transmits a maximum of 20 events (approximately 80 KB message size) to Node B.
Node B stores the received events in its local database.
The Problem:
The issue arises when Node B receives around 300 events from Node A. After this point, Node B cannot send messages to Node A anymore. However, Node B can still receive messages from Node A.
Possible Cause:
I suspect the connection between the nodes might have a buffer limit. If my application can't process data fast enough, this buffer could overflow, preventing further message exchange.
Question:
Does anyone have suggestions on how to resolve this issue? Is there a way to verify the buffer size or adjust it if possible?
Thanks for your help!
The text was updated successfully, but these errors were encountered:
Hello,
I'm facing a problem where data transfer between two nodes fails. Here's the scenario:
Use Case:
max_message_size
to 100 MB in the configuration:Application Details:
The Problem:
The issue arises when Node B receives around 300 events from Node A. After this point, Node B cannot send messages to Node A anymore. However, Node B can still receive messages from Node A.
Possible Cause:
I suspect the connection between the nodes might have a buffer limit. If my application can't process data fast enough, this buffer could overflow, preventing further message exchange.
Question:
Does anyone have suggestions on how to resolve this issue? Is there a way to verify the buffer size or adjust it if possible?
Thanks for your help!
The text was updated successfully, but these errors were encountered: