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

Posted to issues@ignite.apache.org by "Alexander Lapin (Jira)" <ji...@apache.org> on 2023/05/22 08:20:00 UTC

[jira] [Assigned] (IGNITE-19494) Correctly stop a replica

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

Alexander Lapin reassigned IGNITE-19494:
----------------------------------------

    Assignee: Alexander Lapin

> Correctly stop a replica
> ------------------------
>
>                 Key: IGNITE-19494
>                 URL: https://issues.apache.org/jira/browse/IGNITE-19494
>             Project: Ignite
>          Issue Type: Bug
>            Reporter: Kirill Tkalenko
>            Assignee: Alexander Lapin
>            Priority: Major
>              Labels: ignite-3
>             Fix For: 3.0.0-beta2
>
>
> If we look at the implementation of stopping the replica in (*org.apache.ignite.internal.replicator.ReplicaManager#stopReplicaInternal*), then we simply delete the future.
> I think that this is not right, and we should wait for it or something and only after that stop it.
> Maybe I don't understand something and then we'll just close the ticket.



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