You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Vladimir Ozerov (JIRA)" <ji...@apache.org> on 2018/01/17 08:20:03 UTC

[jira] [Updated] (IGNITE-6628) Make possible to rebuild all SQL indexes programmatically with enabled persistence.

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

Vladimir Ozerov updated IGNITE-6628:
------------------------------------
    Fix Version/s:     (was: 2.4)
                   2.5

> Make possible to rebuild all SQL indexes programmatically with enabled persistence.
> -----------------------------------------------------------------------------------
>
>                 Key: IGNITE-6628
>                 URL: https://issues.apache.org/jira/browse/IGNITE-6628
>             Project: Ignite
>          Issue Type: Improvement
>    Affects Versions: 2.0
>            Reporter: Alexei Scherbakov
>            Priority: Major
>             Fix For: 2.5
>
>
> We have unofficial way for rebuilding indexes, which is called on activation if index.bin is removed from PDS directory.
> Code is located here [1]
> I think it's ok to make it public for several cases: model is changed, index is damaged, etc...
> Also current impl has a bug: CacheEntry in [2] is not touched, polluting heap and leading to OOM.
> [1] org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager#beforeExchange
> [2] org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing#rebuildIndexesFromHash



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)