[ 
https://issues.apache.org/jira/browse/IGNITE-12850?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17072082#comment-17072082
 ] 

Sarunas Valaskevicius edited comment on IGNITE-12850 at 3/31/20, 7:24 PM:
--------------------------------------------------------------------------

Please can you also suggest a short-term workaround as well as a proper fix?

I found that if I delete metastorage persistence directory ignite starts ok - 
why is it hardcoded to persistence true? what problems would I see if I deleted 
the metastorage before starting the node?


was (Author: sarunas):
Please can you also suggest a short-term workaround as well as a proper fix?

I found that if I delete metastorage persistence directory ignite starts ok - 
why is it hardcoded to persistence true? what problems would I see if I delete 
metastorage before starting the node?

> Ignite node cannot be started (metastorage history loading fails)
> -----------------------------------------------------------------
>
>                 Key: IGNITE-12850
>                 URL: https://issues.apache.org/jira/browse/IGNITE-12850
>             Project: Ignite
>          Issue Type: Bug
>          Components: cache
>    Affects Versions: 2.7.6
>            Reporter: Sarunas Valaskevicius
>            Priority: Blocker
>
> # metastorage is using persistence
>  # when a node is ready to write, writeBaselineTopology is called with null 
> history item, and generates base line topology history with gaps
>  # from that point, it is impossible to start the node as 
> `{color:#569e16}restoreHistory{color}` throws an exception when it is 
> processing the gap
> –
>  it seems that ignite 2.8.0 would suffer from the same issue - by looking at 
> the code
> {code:java}
> 2020-03-21_00:00:03.867 [fapi-main-0] INFO  
> o.a.i.i.p.c.GridClusterStateProcessor:117 <> - Restoring history for 
> BaselineTopology[id=9]
> 2020-03-21_00:00:03.904 [fapi-main-0] ERROR 
> o.a.ignite.internal.IgniteKernal:137 <> - Exception during start processors, 
> node will be stopped and close connections
> org.apache.ignite.IgniteCheckedException: Restoring of BaselineTopology 
> history has failed, expected history item not found for id=8
>         at 
> org.apache.ignite.internal.processors.cluster.BaselineTopologyHistory.restoreHistory(BaselineTopologyHistory.java:54)
>         at 
> org.apache.ignite.internal.processors.cluster.GridClusterStateProcessor.onReadyForRead(GridClusterStateProcessor.java:223)
>         at 
> org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager.notifyMetastorageReadyForRead(GridCacheDatabaseSharedManager.java:409)
>         at 
> org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager.readMetastore(GridCacheDatabaseSharedManager.java:675)
>         at 
> org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager.notifyMetaStorageSubscribersOnReadyForRead(GridCacheDatabaseSharedManager.java:4730)
>         at 
> org.apache.ignite.internal.IgniteKernal.start(IgniteKernal.java:1048)
>         at 
> org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start0(IgnitionEx.java:2038)
>         at 
> org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start(IgnitionEx.java:1730)
>         at org.apache.ignite.internal.IgnitionEx.start0(IgnitionEx.java:1158)
>         at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:678)
>  {code}



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

Reply via email to