[
https://issues.apache.org/jira/browse/IGNITE-19946?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ivan Bessonov reassigned IGNITE-19946:
--------------------------------------
Assignee: Ivan Bessonov
> Implement batch processing of Raft log entries
> ----------------------------------------------
>
> Key: IGNITE-19946
> URL: https://issues.apache.org/jira/browse/IGNITE-19946
> Project: Ignite
> Issue Type: Improvement
> Reporter: Ivan Bessonov
> Assignee: Ivan Bessonov
> Priority: Major
> Labels: ignite-3
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> Issue is created as a part of IGNITE-15568. Here we need to implement batches
> for the log specifically, so that there will be less IO while writing data
> into a shared log storage.
> Copy of the comment in that issue:
> _The actual implementation here differs from the description._
> _First of all, only the log manager is affected._
> _Second, instead of having a single event that would notify all listeners, I
> re-use the "endOfBatch" flag. This solution is not as general, and it can be
> later re-implemented using additional event, but I decided not to change the
> API too much for now._
> _Log manager internally has the information about the stripe it belongs to.
> Using that information, it's possible to perform a single write into a shared
> log storage, even when batch consists of data from several different
> replication groups._
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
