[IGNITE-6011] EntryProcessor can make data inconsistent if fails on TX cache.

• Type: Bug
• Status: In Progress
• Priority: Major
• Resolution: Unresolved
• Component/s: cache
• Assignee: Dmitry Karachentsev
• Reporter: Andrey Mashenkov
• Created: 09/Aug/17 12:47
• Updated: 28/Feb/18 07:46

Description

I'd expect that with FULL_SYNC write mode and TX cache data always be consistent.
And if EntryProcessor fails on primary (or backup) node and pass on backup (or primary) then whole transaction will be rolled back.
But I observe old value on node where EP has failed and new value on other nodes.

PFA repro attached.

Looks like we should apply EP on lock phase and fail TX if there is any failures.

UPD: We should also check if ignite has an adequate behavior if possible when Error (not Exception) occurs, e.g. assert in user code.

Issue Links

• relates to: IGNITE-3164 Add an option to send resulting value instead of entry processor in transactional cache