[
https://issues.apache.org/jira/browse/IGNITE-12120?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17001158#comment-17001158
]
Ignite TC Bot commented on IGNITE-12120:
----------------------------------------
{panel:title=Branch: [pull/7170/head] Base: [master] : Possible Blockers
(16)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#d04437}Platform .NET{color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=4862079]]
* exe: PersistenceTest.TestWalDisableEnable - Test has low fail rate in base
branch 0,0% and is not flaky
{color:#d04437}Streamers{color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=4862023]]
* IgniteStormStreamerSelfTestSuite:
StormIgniteStreamerSelfTest.testStormStreamerIgniteBolt - Test has low fail
rate in base branch 0,0% and is not flaky
{color:#d04437}Cache 5{color} [[tests
6|https://ci.ignite.apache.org/viewLog.html?buildId=4862062]]
* IgniteCacheTestSuite5:
IgniteCachePartitionLossPolicySelfTest.testReadWriteSafeAfterKillCrdWithPersistence[TRANSACTIONAL]
- Test has low fail rate in base branch 0,0% and is not flaky
* IgniteCacheTestSuite5:
IgniteCachePartitionLossPolicySelfTest.testReadWriteSafeWithBackupsAfterKillThreeNodesWithPersistence[TRANSACTIONAL]
- Test has low fail rate in base branch 0,0% and is not flaky
* IgniteCacheTestSuite5:
IgniteCachePartitionLossPolicySelfTest.testReadWriteSafeWithBackupsAfterKillCrdWithPersistence[TRANSACTIONAL]
- Test has low fail rate in base branch 0,0% and is not flaky
* IgniteCacheTestSuite5:
IgniteCachePartitionLossPolicySelfTest.testReadWriteSafeWithPersistence[TRANSACTIONAL]
- Test has low fail rate in base branch 0,0% and is not flaky
* IgniteCacheTestSuite5:
IgniteCachePartitionLossPolicySelfTest.testReadWriteSafeWithBackupsWithPersistence[TRANSACTIONAL]
- Test has low fail rate in base branch 0,0% and is not flaky
* IgniteCacheTestSuite5:
IgniteCachePartitionLossPolicySelfTest.testReadWriteSafeAfterKillTwoNodesWithPersistence[TRANSACTIONAL]
- Test has low fail rate in base branch 0,0% and is not flaky
{color:#d04437}Thin Client: Java{color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=4862016]]
* ClientTestSuite: ReliabilityTest.testFailover - Test has low fail rate in
base branch 0,0% and is not flaky
{color:#d04437}Cache 1{color} [[tests 5 Out Of Memory Error
|https://ci.ignite.apache.org/viewLog.html?buildId=4862058]]
* IgniteBinaryCacheTestSuite:
DataStreamProcessorPersistenceBinarySelfTest.testLocalDataStreamerDedicatedThreadPool
- Test has low fail rate in base branch 0,0% and is not flaky
* IgniteBinaryCacheTestSuite:
DataStreamProcessorPersistenceBinarySelfTest.testCustomUserUpdater - Test has
low fail rate in base branch 0,0% and is not flaky
* IgniteBinaryCacheTestSuite:
DataStreamProcessorPersistenceBinarySelfTest.testLoaderApi - Test has low fail
rate in base branch 0,0% and is not flaky
* IgniteBinaryCacheTestSuite:
DataStreamProcessorPersistenceBinarySelfTest.testReplicatedIsolated - Test has
low fail rate in base branch 0,0% and is not flaky
* IgniteBinaryCacheTestSuite:
DataStreamProcessorPersistenceBinarySelfTest.testPartitionedMultiThreaded -
Test has low fail rate in base branch 0,0% and is not flaky
{color:#d04437}Activate / Deactivate Cluster{color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=4861999]]
* IgniteStandByClusterSuite:
IgniteBaselineAffinityTopologyActivationTest.testNodeJoinsDuringPartitionMapExchange
- Test has low fail rate in base branch 0,0% and is not flaky
{panel}
[TeamCity *--> Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=4862109&buildTypeId=IgniteTests24Java8_RunAll]
> 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
> Time Spent: 10m
> 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)
