You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Maxim Muzafarov (Jira)" <ji...@apache.org> on 2019/10/10 11:34:00 UTC

[jira] [Updated] (IGNITE-11807) Index validation control.sh command may provide false-positive error results

     [ https://issues.apache.org/jira/browse/IGNITE-11807?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Maxim Muzafarov updated IGNITE-11807:
-------------------------------------
    Fix Version/s:     (was: 2.8)
                   2.9

> Index validation control.sh command may provide false-positive error results
> ----------------------------------------------------------------------------
>
>                 Key: IGNITE-11807
>                 URL: https://issues.apache.org/jira/browse/IGNITE-11807
>             Project: Ignite
>          Issue Type: Bug
>            Reporter: Ivan Rakov
>            Priority: Major
>             Fix For: 2.9
>
>
> There are two possible issues in validate_indexes command:
> 1. In case index validation is performed under load, there's a chance that we'll fetch link from B+ tree and won't found this key in partition cache data store as per it was conurrently removed.
> We may work it around by double-checking partition update counters (before and after indexes validation procedure).
> 2. Since indexes validation is subscribed to checkpoint start (reason: we perform CRC validation of file page store pages which is sensitive to concurrent disk page writes), we may bump into the following situation:
> - User fairly stops all load
> - A few moments later users triggers validate_indexes
> - Checkpoint starts due to timeout, pages that were modified before validate_indexes start are being written to the disk
> - validate_indexes fails
> We may work it around by triggering checkpoint forcibly before start of indexes validation activities.



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