You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Kirill Tkalenko (Jira)" <ji...@apache.org> on 2023/05/18 10:21:00 UTC
[jira] [Updated] (IGNITE-19494) Correctly stop a replica
[ https://issues.apache.org/jira/browse/IGNITE-19494?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kirill Tkalenko updated IGNITE-19494:
-------------------------------------
Description:
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.
was:
At the moment it seems to me that we are not stopping the replica correctly, we are simply deleting its future from the map, you can see here (*org.apache.ignite.internal.replicator.ReplicaManager#stopReplicaInternal*) what looks wrong to me.
I think we need to do it right.
> Correctly stop a replica
> ------------------------
>
> Key: IGNITE-19494
> URL: https://issues.apache.org/jira/browse/IGNITE-19494
> Project: Ignite
> Issue Type: Bug
> Reporter: Kirill Tkalenko
> 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)