[
https://issues.apache.org/jira/browse/IGNITE-11807?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ivan Rakov updated IGNITE-11807:
--------------------------------
Description:
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.
was:
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.
> 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.8
>
>
> 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
(v7.6.3#76005)
