This repository has been archived by the owner on Jun 1, 2021. It is now read-only.
Limit number of ReplicationDue sent per ReplicationRead #364
Comments
volkerstampa
added a commit
that referenced
this issue
Nov 30, 2016
Do not send update notifications forever to avoid spamming the application log due to akka remoting problems when partner was shutdown. closes #364
volkerstampa
added a commit
that referenced
this issue
Dec 1, 2016
- this avoids spamming the application log due to akka remoting problems when partner was shutdown. - closes #364
volkerstampa
added a commit
that referenced
this issue
Dec 5, 2016
- this avoids spamming the application log due to akka remoting problems when partner was shutdown. - closes #364
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
If
update-notificationsare enabled and location A replicates events from location B, B sendsReplicationDuemessages to A when new events are written to the log (and there is no pending replication read from A). B keeps sending theseReplicationDuemessages even after A was shutdown resulting in corresponding WARN logs from akka-remote in B's application log.To avoid spamming the application log in such circumstances the number of
ReplicationDuesent to other locations on received replication read requests should be limited.The text was updated successfully, but these errors were encountered: