I ran into the same problem. There were too many gossip reports in the magazine, and I wanted to prevent that.
Here is the solution.
https://github.com/akkadotnet/akka.net/blob/v1.1.2/src/core/Akka.Cluster/Configuration/Cluster.conf#L77
, GossipStatus, ( ):
[DEBUG][2016-12-26 1:48:36 PM][Thread 0004][[akka://mysystem/system/cluster/core/daemon#1458732427]] [Initialized] Received Akka.Cluster.GossipStatus
:
cluster {
log-info = off
}
, :
remote {
log-received-messages = on
}
cluster gossip ( @Aaronontheweb), .
, , :
[DEBUG][2016-12-26 1:41:03 PM][Thread 0008][[akka://mysystem/system/endpointManager/reliableEndpointWriter-akka.tcp%3A%2F%2Fmysystem%40127.0.0.1%3A4053-1/endpointWriter
[DEBUG][2016-12-26 1:41:04 PM][Thread 0010][[akka://mysystem/system/endpointManager/reliableEndpointWriter-akka.tcp%3A%2F%2Fmysystem%40127.0.0.1%3A4053-1/endpointWriter
[DEBUG][2016-12-26 1:41:04 PM][Thread 0009][[akka://mysystem/system/endpointManager/reliableEndpointWriter-akka.tcp%3A%2F%2Fmysystem%40127.0.0.1%3A4053-1/endpointWriter