[
https://issues.apache.org/jira/browse/IGNITE-12120?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ilya Kasnacheev resolved IGNITE-12120.
--------------------------------------
Fix Version/s: 2.9
Resolution: Fixed
[~sunnychanclsa] I took the liberty to also convert Cassandra warning to Log
Throttle, and check INCLUDE_SENSITIVE in cache store's message.
> Change log level in GridCacheWritebehindStore
> ---------------------------------------------
>
> Key: IGNITE-12120
> URL: https://issues.apache.org/jira/browse/IGNITE-12120
> Project: Ignite
> Issue Type: Bug
> Components: cache
> Affects Versions: 2.7.5
> Reporter: Sunny Chan
> Priority: Trivial
> Fix For: 2.9
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> In the
> [GridCacheWriteBehindStore|https://github.com/apache/ignite/blob/7e73098d4d6e3d5f78326cb11dac7e083a2312dd/modules/core/src/main/java/org/apache/ignite/internal/processors/cache/store/GridCacheWriteBehindStore.java#L893],
> when the updateStore failed to write to underlying store, it logs this as
> error:
> {{LT.error(log, e, "Unable to update underlying store: " + store);}}
> After this line logged the error, it would return false so that it would
> retry the store (by returning false).
> While later on in the updatStore function, when the writeCache overflows, it
> would log this:
> {{log.warning("Failed to update store (value will be lost as current buffer
> size is greater " + …}}
> then it will remove the failed entry.
> I think the severity of the log messages is not right, as the fail update
> would still be retried.
> So I propose to change the log severity level so that the first one would be
> a warn, and second one would be error
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
