[
https://issues.apache.org/jira/browse/IGNITE-12938?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17108254#comment-17108254
]
Ignite TC Bot commented on IGNITE-12938:
----------------------------------------
{panel:title=Branch: [pull/7743/head] Base: [master] : No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
[TeamCity *--> Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=5308663&buildTypeId=IgniteTests24Java8_RunAll]
> control.sh utility commands: IdleVerify and ValidateIndexes use eventual
> payload check.
> ---------------------------------------------------------------------------------------
>
> Key: IGNITE-12938
> URL: https://issues.apache.org/jira/browse/IGNITE-12938
> Project: Ignite
> Issue Type: Improvement
> Components: general
> Affects Versions: 2.8
> Reporter: Stanilovsky Evgeny
> Assignee: Stanilovsky Evgeny
> Priority: Major
> Fix For: 2.9
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> {noformat}
> "--cache idle_verify" and "--cache validate_indexes"
> {noformat}
> commands of *control.sh* utility use eventual payload check during
> execution. This can lead to execution concurrently with active payload and no
> errors like : "Checkpoint with dirty pages started! Cluster not idle" will
> be triggered. Additionally current functional miss check on caches without
> persistence. Remove old functionality from PageMemory and move it into
> update counters usage. Running this checks with active rebalance or active
> payload may give erroneous results in cases of out of order update messages
> will be processed or some gaps eventually arises, more info [1]. This fix
> covers such problems.
> [1] https://cwiki.apache.org/confluence/display/IGNITE/Data+consistency
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
