[
https://issues.apache.org/jira/browse/IGNITE-23942?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18061607#comment-18061607
]
Kirill Anisimov commented on IGNITE-23942:
------------------------------------------
[~liyuj] do you plan to continue with this activity?
> NullPointerException in RebuildIndexAction
> ------------------------------------------
>
> Key: IGNITE-23942
> URL: https://issues.apache.org/jira/browse/IGNITE-23942
> Project: Ignite
> Issue Type: Bug
> Components: sql
> Affects Versions: 2.16
> Reporter: YuJue Li
> Assignee: YuJue Li
> Priority: Minor
> Fix For: 2.18
>
> Attachments: image-2024-12-11-13-13-09-365.png
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> !image-2024-12-11-13-13-09-365.png!
> This NullPointerException caused Ignite to be unable to exit maintenance mode
> properly, resulting in Ignite being unable to start.
> We have seen the following logs:
> 2024-12-06_23:12:37.909 [WARN ] [query-#276617] [ROOT] Index
> org.apache.ignite.internal.cache.query.index.IndexName@38719ad1 of the table
> MKTTRADE (cache mktTradeCache) is corrupted, to fix this issue a rebuild is
> required. On the next restart, node will enter the maintenance mode and
> rebuild corrupted indexes.
>
> However, the cache did not enable persistence, which is the reason for
> throwing NullPointerException during subsequent maintenance tasks.
> For pure memory mode cache, there is no need to schedule the maintenance task
> of rebuilding the index, because after the node stops, all information in the
> pure memory mode cache will disappear, which means rebuilding the index is
> only meaningful for cache with persistence enabled.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
