Constant revision logs spamming console


#1

Using dependency injection to get a INamedBucketProvider, my console application is being spammed with logs regarding a revision:

info: Couchbase.Configuration.Server.Providers.ConfigProviderBase[0]
Ignoring config with rev#5321
info: Couchbase.Configuration.Server.Monitoring.ConfigMonitor[0]
Using index 2 - server Couchbase.Core.Server
info: Couchbase.Configuration.Server.Monitoring.ConfigMonitor[0]
Checking config with revision #5321
info: Couchbase.Configuration.Server.Providers.ConfigProviderBase[0]
Ignoring config with rev#5321
info: Couchbase.Configuration.Server.Monitoring.ConfigMonitor[0]
Using index 0 - server Couchbase.Core.Server
info: Couchbase.Configuration.Server.Monitoring.ConfigMonitor[0]
Checking config with revision #5321
info: Couchbase.Configuration.Server.Providers.ConfigProviderBase[0]
Ignoring config with rev#5321
info: Couchbase.Configuration.Server.Monitoring.ConfigMonitor[0]
Using index 1 - server Couchbase.Core.Server
info: Couchbase.Configuration.Server.Monitoring.ConfigMonitor[0]
Checking config with revision #5321
info: Couchbase.Configuration.Server.Providers.ConfigProviderBase[0]
Ignoring config with rev#5321
info: Couchbase.Configuration.Server.Monitoring.ConfigMonitor[0]
Using index 2 - server Couchbase.Core.Server
info: Couchbase.Configuration.Server.Monitoring.ConfigMonitor[0]
Checking config with revision #5321
info: Couchbase.Configuration.Server.Providers.ConfigProviderBase[0]
Ignoring config with rev#5321

Is this an issue? If not, is there any way to turn off these logs?

using:
Couchbase.Extension.DependencyInjection 2.0.1
CouchbaseNetClient 2.5.10
and
Couchbase Enterprise Edition 5.0.1 build 5003


#2

Hi @lukeb

The logs are to indicate when the client has received and is processing a new cluster configuration. I do agree the “skipping rev” messages could be at a lower log level. I’ve created the following ticket to review the log levels: NCBC-1691.


#3

@lukeb

In the meantime, if you lower the log level for the “Couchbase.Configuration” namespace to “Warning” that should suppress the messages. It’s what I normally do. How you do that will depend on the specific logging system you’re using.