-
Notifications
You must be signed in to change notification settings - Fork 181
Open
Description
I'm using a distributing cache without a backplane. There is only 1 node so this warning is irrelevant and a backplane is not necessary. It would be great to know which option to use to silence this warning. Adding that detail to the warning itself would be an improvement!
For now, could you point me to which property to lower the level for to remove this from my logs?
Error
you are using an L2 (distributed cache) without a backplane, which will potentially leave other nodes' L1s (memory caches) out-of-sync after an update (see: cache coherence). To solve this, you can use a backplane. If that is not possible, you can mitigate the situation by setting both DefaultEntryOptions.MemoryCacheDuration and TagsDefaultEntryOptions.MemoryCacheDuration to a low value: this will refresh data in the L1 from the L2 more frequently, reducing the incoherence window.
I have these options set for logging but it's not silencing the warning.
options.FactoryErrorsLogLevel = LogLevel.Error;
options.DistributedCacheErrorsLogLevel = LogLevel.Error;
options.SerializationErrorsLogLevel = LogLevel.Warning;
options.FailSafeActivationLogLevel = LogLevel.Debug;
options.DistributedCacheSyntheticTimeoutsLogLevel = LogLevel.Debug;
options.FactorySyntheticTimeoutsLogLevel = LogLevel.Debug;
options.IncoherentOptionsNormalizationLogLevel = LogLevel.None;Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
No labels