[
https://issues.apache.org/jira/browse/IGNITE-23318?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17889220#comment-17889220
]
Ivan Bessonov commented on IGNITE-23318:
----------------------------------------
What's done here:
* Recover meta storage from persisted data, instead of recovering it from a
snapshot. This way we will only recover a limited number of data, usually it
would fit into a single mem-table. Maybe several mem-tables at worst.
To do that, I introduced index/term/configuration values into the storage, just
like it's done in partitions.
As of right now, "raft snapshots" code for meta storage is not affected, let's
do that separately.
> Unable to restart cluster multiple times.
> -----------------------------------------
>
> Key: IGNITE-23318
> URL: https://issues.apache.org/jira/browse/IGNITE-23318
> Project: Ignite
> Issue Type: Bug
> Affects Versions: 3.0
> Reporter: Iurii Gerzhedovich
> Assignee: Ivan Bessonov
> Priority: Blocker
> Labels: ignite-3
> Attachments: ignite.log
>
> Time Spent: 1h 50m
> Remaining Estimate: 0h
>
> We have TPCH benchmarks in Ignite 3
> (org.apache.ignite.internal.benchmark.TpchBenchmark). The benchmark can
> prepare data in a cluster and run benchmarks a few times on the same data set
> without data reload. During run the benchmarks I observe the following issues:
> 1. After a few such runs, I have situations when the nodes cannot assemble
> into a cluster. 100% reproducible but with a different number of restarts.
> 2. With every restart the startup logs become longer and longer.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
