[
https://issues.apache.org/jira/browse/IGNITE-19806?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ivan Bessonov updated IGNITE-19806:
-----------------------------------
Description:
[https://github.com/sofastack/sofa-jraft/commit/30499b948ed60211a508199a220be173e7ef2be5]
First of all, we need to port it and run benchmarks. After that we should adapt
it to our multi-group approach and benchmark it once again.
Another possibility is "enabling" batch log writes first, to be more fair.
UPDATE
There's no point in migrating hybrid storage. Ignite is not yet release, and if
we need it in the future, we will port it separately.
was:
[https://github.com/sofastack/sofa-jraft/commit/30499b948ed60211a508199a220be173e7ef2be5]
First of all, we need to port it and run benchmarks. After that we should adapt
it to our multi-group approach and benchmark it once again.
Another possibility is "enabling" batch log writes first, to be more fair
> Port new log storage from jraft
> -------------------------------
>
> Key: IGNITE-19806
> URL: https://issues.apache.org/jira/browse/IGNITE-19806
> Project: Ignite
> Issue Type: Improvement
> Reporter: Ivan Bessonov
> Assignee: Ivan Bessonov
> Priority: Major
> Labels: ignite-3
>
> [https://github.com/sofastack/sofa-jraft/commit/30499b948ed60211a508199a220be173e7ef2be5]
> First of all, we need to port it and run benchmarks. After that we should
> adapt it to our multi-group approach and benchmark it once again.
> Another possibility is "enabling" batch log writes first, to be more fair.
> UPDATE
> There's no point in migrating hybrid storage. Ignite is not yet release, and
> if we need it in the future, we will port it separately.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
