You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Roman Puchkovskiy (Jira)" <ji...@apache.org> on 2024/10/22 06:53:00 UTC

[jira] [Updated] (IGNITE-23496) Optimize lease batch serialization

     [ https://issues.apache.org/jira/browse/IGNITE-23496?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Roman Puchkovskiy updated IGNITE-23496:
---------------------------------------
    Description: Ignite nodes update leases each 2.5 seconds, in batches. A batch might contain dozens of thousands (or more) leases. The batch is serialized to bytes and stored in the Metastorage. Current seriailzation format is not too compact; for example, having 25000 partitions (and one lease per partition) in a 3-node cluster, we get approximately 4.7Mb per batch.  (was: Currently, Java Serialization is used to persist data in DistributionZonesManager. We should not use it (see IGNITE-23135 for justification).)

> Optimize lease batch serialization
> ----------------------------------
>
>                 Key: IGNITE-23496
>                 URL: https://issues.apache.org/jira/browse/IGNITE-23496
>             Project: Ignite
>          Issue Type: Improvement
>            Reporter: Roman Puchkovskiy
>            Assignee: Roman Puchkovskiy
>            Priority: Major
>              Labels: ignite-3
>             Fix For: 3.0
>
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> Ignite nodes update leases each 2.5 seconds, in batches. A batch might contain dozens of thousands (or more) leases. The batch is serialized to bytes and stored in the Metastorage. Current seriailzation format is not too compact; for example, having 25000 partitions (and one lease per partition) in a 3-node cluster, we get approximately 4.7Mb per batch.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)