[IGNITE-12801] Possible extra page release when throttling and checkpoint thread store its concurrently

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 2.9, 2.8.1
• Release Note: Fixed an issue causing a node fail with AssertionError when throttling is activated during a checkpoint
• Ignite Flags: Docs Required, Release Notes Required
• Assignee: Anton Kalashnikov
• Reporter: Anton Kalashnikov
• Created: 18/Mar/20 15:20
• Updated: 20/May/20 09:01
• Resolved: 20/May/20 09:01

Description

• User thread acquire page on write release
• Checkpoint thread sees that page was acquired
• Throttling thread sees that page was acquired
• Checkpoint thread saves page to disk and releases the page
• Throttling thread understand that the page was already saved but nonetheless release this page again. - this is not ok.

  java.lang.AssertionError: null
  at org.apache.ignite.internal.processors.cache.persistence.pagemem.PageMemoryImpl.copyPageForCheckpoint(PageMemoryImpl.java:1181)
  at org.apache.ignite.internal.processors.cache.persistence.pagemem.PageMemoryImpl.checkpointWritePage(PageMemoryImpl.java:1160)
  at org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager$WriteCheckpointPages.writePages(GridCacheDatabaseSharedManager.java:4868)
  at org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager$WriteCheckpointPages.run(GridCacheDatabaseSharedManager.java:4792)
  ... 3 common frames omitted
  

Issue Links

• is duplicated by: IGNITE-12577 High persistence load can trigger erroneous assert: "Page was pin when we resolve abs pointer, it can not be evicted".
• links to: GitHub Pull Request #7554