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

Posted to issues@ignite.apache.org by "Pavel Voronkin (JIRA)" <ji...@apache.org> on 2019/02/06 12:29:00 UTC

[jira] [Updated] (IGNITE-11221) Refactor timeout logic in TcpDiscovery

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

Pavel Voronkin updated IGNITE-11221:
------------------------------------
    Description: 
We need to replace IgniteSpiOperationTimeoutHelper with TimeoutStrategy introduced in IGNITE-7648, cause it's mixing exception handling and timeout calculation.

We need to reuse ExponentialBackoffTimeout to encapsulate logic of calculating different sets of timeout separately and get rid of many local variables.

  was:
We need to reimplement IgniteSpiOperationTimeoutHelper, cause it's mixing exception handling and timeout calculation.

We need to reuse ExponentialBackoffTimeout to encapsulate logic of calculating different sets of timeout separately and get rid of many local variables.


> Refactor timeout logic in TcpDiscovery
> --------------------------------------
>
>                 Key: IGNITE-11221
>                 URL: https://issues.apache.org/jira/browse/IGNITE-11221
>             Project: Ignite
>          Issue Type: Bug
>            Reporter: Pavel Voronkin
>            Assignee: Stanilovsky Evgeny
>            Priority: Major
>
> We need to replace IgniteSpiOperationTimeoutHelper with TimeoutStrategy introduced in IGNITE-7648, cause it's mixing exception handling and timeout calculation.
> We need to reuse ExponentialBackoffTimeout to encapsulate logic of calculating different sets of timeout separately and get rid of many local variables.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)