You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Denis Chudov (Jira)" <ji...@apache.org> on 2024/10/11 10:42:00 UTC
[jira] [Updated] (IGNITE-23376) Possibility to stop replica despite into the lease state
[ https://issues.apache.org/jira/browse/IGNITE-23376?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Denis Chudov updated IGNITE-23376:
----------------------------------
Description:
h3. Motivation
In some cases, for example, recovery or manual user intervention, we ought to stop replica as soon as possible. It could be a primary replica or the other one, because we are processing operations through the primary (e.g., RW transaction) or through the other (e.g., RO transaction).
Currently, we may get an exception when trying to access a closing storage or getting some inappropriate state in the partition replica listener, etc.
h3. Implementation notes
# Probably, implementation based on busy locks for each replica will satisfy this ticket.
# We also will apply this approach to recovery procedure, which was worked around here IGNITE-23125
h3. Definition of done
The replica stop process has to be thread safe regarding other operations with replica.
was:
h3. Motivation
In some cases, for example, recovery or manual user intervention, we ought to stop replica as soon as possible. It could be a primary replica or the other one, because we are processing operations through the primary (e.g., RW transaction) or through the other (e.g., RO transaction).
Corrently, we may get an axception when trying to access a closing storage or getting some unsufficient state in the partition replica listener, e.t.c.
h3. Implementation notes
# Probably, implementation based on busy locks for each replica will satisfy this ticket.
# We also will apply this approach to recovery procedure, which was worked around here IGNITE-23125
h3. Definition of done
The replica stopp process has to be thread secure with other operations with replica.
> Possibility to stop replica despite into the lease state
> --------------------------------------------------------
>
> Key: IGNITE-23376
> URL: https://issues.apache.org/jira/browse/IGNITE-23376
> Project: Ignite
> Issue Type: Improvement
> Reporter: Vladislav Pyatkov
> Priority: Major
> Labels: ignite-3
>
> h3. Motivation
> In some cases, for example, recovery or manual user intervention, we ought to stop replica as soon as possible. It could be a primary replica or the other one, because we are processing operations through the primary (e.g., RW transaction) or through the other (e.g., RO transaction).
> Currently, we may get an exception when trying to access a closing storage or getting some inappropriate state in the partition replica listener, etc.
> h3. Implementation notes
> # Probably, implementation based on busy locks for each replica will satisfy this ticket.
> # We also will apply this approach to recovery procedure, which was worked around here IGNITE-23125
> h3. Definition of done
> The replica stop process has to be thread safe regarding other operations with replica.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)