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

Posted to issues@ignite.apache.org by "Sergey Uttsel (Jira)" <ji...@apache.org> on 2022/07/07 10:23:00 UTC

[jira] [Updated] (IGNITE-17222) Need to propagate HLC with transaction protocol events

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

Sergey Uttsel updated IGNITE-17222:
-----------------------------------
    Description: One of source of HLC sync is a transaction protocol. Each ReplicaRequest и ReplicaResponse involved in the execution of the transaction carries the sender’s HLC and updates receiver HLC according to rules.  (was: One of source of HLC sync is a transaction protocol. Each message involved in the execution of the transaction carries the sender’s HLC and updates receiver HLC according to rules.)

> Need to propagate HLC with transaction protocol events
> ------------------------------------------------------
>
>                 Key: IGNITE-17222
>                 URL: https://issues.apache.org/jira/browse/IGNITE-17222
>             Project: Ignite
>          Issue Type: Improvement
>            Reporter: Sergey Uttsel
>            Priority: Major
>              Labels: ignite-3, transaction3_ro
>
> One of source of HLC sync is a transaction protocol. Each ReplicaRequest и ReplicaResponse involved in the execution of the transaction carries the sender’s HLC and updates receiver HLC according to rules.



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