[IGNITE-6096] Race between partition eviction and re-creation

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.1
• Fix Version/s: 2.3
• Assignee: Alexey Goncharuk
• Reporter: Ilya Lantukh
• Created: 17/Aug/17 09:28
• Updated: 28/Aug/17 16:40
• Resolved: 17/Aug/17 15:30

Description

There are a number of cases that aren't handled correctly, leading to assertion errors, grid hang-ups and data loss:

• PageMemoryImpl.refreshOutdatedPage(...) - if refreshed page is currently scheduled for checkpoint, it will be stored if FileStore filled with zeroes. Reading this page later will fail.
• GridCacheDatabaseSharedManager.restorePartitionState(...) - grp.offheap().onPartitionInitialCounterUpdated(...) is called under meta page write lock. If DataStore requires initialization, it will try to aquire write lock for meta page again and hang up.
• GridDhtPartitionTopologyImpl.createPartition(...) and .localPartition0(...) - if partition is present but has EVICTED state, we will try to create new partition instance. However, DataStore for old partition might still be present, and we will get AssertionError when we attempt to create new DataStore.

Issue Links

• links to: GitHub Pull Request #2463