[IGNITE-5553] Ignite PDS 2: IgnitePersistentStoreDataStructuresTest testSet assertion error

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.1
• Fix Version/s: 2.7
• Component/s: data structures, persistence
• Labels: MakeTeamcityGreenAgain Muted_test test-fail
• Assignee: Pavel Pereslegin
• Reporter: Dmitry Pavlov
• Created: 20/Jun/17 09:39
• Updated: 20/Sep/18 09:24
• Resolved: 17/Sep/18 15:11

Description

Notes-4435

When IgniteSet is restored from persistence, size of set is always 0, link to test history.

Detailed description

Unlike IgniteQueue which uses separate cache key to store its size IgniteSet stores it in a field of some class.
Test from the link above shows very clearly that after restoring memory state from PDS all set values are restored correctly but size is lost.

Proposed solution

One possible solution might be to do the same thing as IgniteQueue does: size of IgniteSet must be stored is cache instead of volatile in-memory fields of random classes.

Issue Links

• is duplicated by: IGNITE-5370 IgniteSet misses its size after cluster restart with enabled PDS feature
• links to: Discussion on DevList
• links to: GitHub Pull Request #3587
• links to: TC run all.
• links to: Upsource review.