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

Denis Chudov updated IGNITE-24818:
----------------------------------
    Description: 
Full transaction require passing lease start time in the command, the FSM 
compares it to the current lease start time that is saved in the storage in 
order to linearize the full transactions and primary replica changes. In 
in-memory groups, this lease start time may be lost.

Consider the case:
 * primary replica is elected, written to meta storage, its start time is 
written into in-memory partition storage;
 * in-memory storage loses the data due to some nodes' restarts (including the 
cases where majority is not lost and the group still is operable, like it is 
described in IGNITE-24772).
 * The new leader may be elected on another node, it doesn't matter because the 
primary replica is not always colocated with leader;
 * full transaction tries to commit data but is rejected (or error is occurred) 
due to the loss of lease start time in the partition storage. Full transactions 
will be inoperable for this group until the new primary is elected.

  was:
Full transaction require passing lease start time in the command, the FSM 
compares it to the current lease start time that is saved in the storage in 
order to linearize the full transactions and primary replica changes. In 
in-memory groups, this lease start time may be lost.

Consider the case:
 * primary replica is elected, written to meta storage, its start time is 
written into in-memory partition storage;
 * in-memory storage loses the data due to some nodes' restarts (including the 
cases where majority is not lost and the group still is operable, like it is 
described in IGNITE-24772).
 * The new leader may be elected on another node, this doesn't matter because 
the primary replica is not always colocated with leader;
 * full transaction tries to commit data but is rejected (or error is occurred) 
due to the loss of lease start time in the partition storage. Full transactions 
will be inoperable for this group until the new primary is elected.


> Possible rejection of full transactions in in-memory groups
> -----------------------------------------------------------
>
>                 Key: IGNITE-24818
>                 URL: https://issues.apache.org/jira/browse/IGNITE-24818
>             Project: Ignite
>          Issue Type: Bug
>            Reporter: Denis Chudov
>            Priority: Major
>
> Full transaction require passing lease start time in the command, the FSM 
> compares it to the current lease start time that is saved in the storage in 
> order to linearize the full transactions and primary replica changes. In 
> in-memory groups, this lease start time may be lost.
> Consider the case:
>  * primary replica is elected, written to meta storage, its start time is 
> written into in-memory partition storage;
>  * in-memory storage loses the data due to some nodes' restarts (including 
> the cases where majority is not lost and the group still is operable, like it 
> is described in IGNITE-24772).
>  * The new leader may be elected on another node, it doesn't matter because 
> the primary replica is not always colocated with leader;
>  * full transaction tries to commit data but is rejected (or error is 
> occurred) due to the loss of lease start time in the partition storage. Full 
> transactions will be inoperable for this group until the new primary is 
> elected.



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

Reply via email to