"Received gossip status" message is always logged by DistributedData

[object]

We are going through log information recorded by our Akka services to reduce costs associated with extensive logging. Large portion of log message comes from continuous gossip status logging, that occurs in Akka.DistributedData/Replicator.cs:

private void ReceiveStatus(IImmutableDictionary<string, ByteString> otherDigests, int chunk, int totChunks)
{
            if (_log.IsDebugEnabled)
                _log.Debug("Received gossip status from [{0}], chunk {1}/{2} containing [{3}]", Sender.Path.Address, chunk + 1, totChunks, string.Join(", ", otherDigests.Keys));
            // Skipped the rest
}

The problem with this message is that it's generated with a high frequency, so large part of debug logs are filled with these messages. In our case we are getting about 7.2 million log messages every 24 hours, and about 6.1 million of them are "Received gossip" messages from Akka DistributedData.

I propose turning these messages off by default because they are helpful only under special circumstances. DistributedData uses configuration described here:

https://github.com/akkadotnet/akka.net/blob/dev/src/contrib/cluster/Akka.DistributedData/reference.conf

Adding a debug section that would control gossip logging will solve the issue.

[object]

I need to further investigate this issue, closing it for now. Will open if I confirm it.

[Aaronontheweb]

So it doesn't appear as though these logs are always on after all? Please let us know what you find in your investigation - these are easy fixes for us to make if there's indeed a bug here.

[object]

@Aaronontheweb I have written the issue and proposed extending DistributedData configuration and turn "Received gossip" off by default. I can send a PR if you want.

[Aaronontheweb]

@object A PR would be very welcome here - we can do it ourselves but we'd always prefer to let a community member take a stab at it

[object]

Great, then I will start looking into it.