ignite-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Maxim Muzafarov (Jira)" <j...@apache.org>
Subject [jira] [Updated] (IGNITE-6628) Make possible to rebuild all SQL indexes programmatically with enabled persistence.
Date Thu, 03 Oct 2019 10:02:02 GMT

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

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

> 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.9
>
>
> 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
(v8.3.4#803005)

Mime
View raw message