You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@ignite.apache.org by "Andrey Mashenkov (Jira)" <ji...@apache.org> on 2022/06/08 14:35:00 UTC

[jira] [Updated] (IGNITE-17123) Optimize update counter assignment on backup nodes.

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

Andrey Mashenkov updated IGNITE-17123:
--------------------------------------
    Priority: Minor  (was: Major)

> Optimize update counter assignment on backup nodes.
> ---------------------------------------------------
>
>                 Key: IGNITE-17123
>                 URL: https://issues.apache.org/jira/browse/IGNITE-17123
>             Project: Ignite
>          Issue Type: Improvement
>          Components: cache
>            Reporter: Andrey Mashenkov
>            Assignee: Andrey Mashenkov
>            Priority: Minor
>             Fix For: 2.14
>
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> Update counter can be assigned to TxEntry instantly on tx commit on Remote node (for the WAL purposes) instead of allocating+iterating over a new collection (see GridDistributedTxRemoteAdapter.commitIfLocked).



--
This message was sent by Atlassian Jira
(v8.20.7#820007)