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

Posted to issues@ignite.apache.org by "Roman Puchkovskiy (Jira)" <ji...@apache.org> on 2022/12/15 11:46:00 UTC

[jira] [Assigned] (IGNITE-18421) Fix IncomingSnapshotCopier#cancel for the case of network problems

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

Roman Puchkovskiy reassigned IGNITE-18421:
------------------------------------------

    Assignee: Roman Puchkovskiy

> Fix IncomingSnapshotCopier#cancel for the case of network problems
> ------------------------------------------------------------------
>
>                 Key: IGNITE-18421
>                 URL: https://issues.apache.org/jira/browse/IGNITE-18421
>             Project: Ignite
>          Issue Type: Bug
>            Reporter: Kirill Tkalenko
>            Assignee: Roman Puchkovskiy
>            Priority: Major
>              Labels: ignite-3
>             Fix For: 3.0.0-beta2
>
>
> Need to fix *org.apache.ignite.internal.table.distributed.raft.snapshot.incoming.IncomingSnapshotCopier#cancel* when network hangs occur.
> I think that it is enough to save the future in a variable that will be created after accessing the network, and on canceling the *IncomingSnapshotCopier*, also cancel this future.
> And also think about the *IncomingSnapshotCopier#NETWORK_TIMEOUT*.



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