[jira] [Commented] (IGNITE-13373) WAL segmentns do not released on releaseHistoryForPreloading()

["shivakumar (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/IGNITE-13373?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17249084#comment-17249084 ] 

shivakumar commented on IGNITE-13373:
-------------------------------------

Hi [~YAMolochkov]

Could you please consider this for 2.9.1 release ? It seems this code change (also IGNITE-12892) solves major blocker issue described here 

[http://apache-ignite-users.70518.x6.nabble.com/Could-not-clear-historyMap-due-to-WAL-reservation-on-cp-td34779.html]

[http://apache-ignite-users.70518.x6.nabble.com/connecting-to-visor-shell-permanently-stops-unwanted-WAL-clean-up-td34737.html]

 

Regards

Shiva

> WAL segmentns do not released on releaseHistoryForPreloading()
> --------------------------------------------------------------
>
>                 Key: IGNITE-13373
>                 URL: https://issues.apache.org/jira/browse/IGNITE-13373
>             Project: Ignite
>          Issue Type: Bug
>            Reporter: Alexander Lapin
>            Assignee: Alexander Lapin
>            Priority: Major
>              Labels: 2.9.1-rc
>             Fix For: 2.10
>
>          Time Spent: 20m
>  Remaining Estimate: 0h
>
> * Reserve/releaseHistoryForPreloading() was reworked, now we store oldest WALPointer that was reserved during reserveHistoryForPreloading in reservedForPreloading field. As a result it's possible to release wall reservation on releaseHIstoryForPreloading().
>  * searchAndReserveCheckpoints() was slightly refactored: now it returns not only an earliestValidCheckpoints but also an oldest reservedCheckpoint, so that there’s no need to recalculate it within reserveHistoryForExchange().
>  *



--
This message was sent by Atlassian Jira
(v8.3.4#803005)