[
https://issues.apache.org/jira/browse/IGNITE-23550?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17904337#comment-17904337
]
Kirill Tkalenko edited comment on IGNITE-23550 at 12/10/24 4:01 AM:
--------------------------------------------------------------------
At the moment, on the first point from the message above in IGNITE-23908, we
have removed the synchronous saving of the checksum in metastorage for each
revision update, further work on this topic will be in IGNITE-23910.
The implementation of streaming snapshot will be in IGNITE-23924.
was (Author: [email protected]):
At the moment, on the first point from the message above in IGNITE-23908, we
have removed the synchronous saving of the checksum in metastorage for each
revision update, further work on this topic will be in IGNITE-23910.
The implementation of streaming snapshot will be in GNITE-23924.
> Test and optimize metastorage snapshot transfer and recovery speed for new
> nodes
> --------------------------------------------------------------------------------
>
> Key: IGNITE-23550
> URL: https://issues.apache.org/jira/browse/IGNITE-23550
> Project: Ignite
> Issue Type: Task
> Reporter: Ivan Bessonov
> Assignee: Kirill Tkalenko
> Priority: Major
> Labels: ignite-3
> Time Spent: 20m
> Remaining Estimate: 0h
>
> Test and optimize metastorage snapshot transfer and recovery speed for new
> nodes.
> Let's assume that we have a 100Mb+ meta-storage snapshot and 100k+ entries in
> raft log replicated as log.
> How long would it take for a new node to join the cluster under these
> conditions? Will something break? What can we do to make it work?
> Goal is - the joining process should work for a long-running clusters. It
> should be pretty fast as well. Less than 10 seconds for sure, of course
> depending on the network capabilities. No timeout errors should occur if it
> takes more than 10 seconds.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
