You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Anton Vinogradov (Jira)" <ji...@apache.org> on 2020/11/23 09:15:00 UTC
[jira] [Commented] (IGNITE-13646) Turn failure detection timeout
into a parameter in discovery ducktape test.
[ https://issues.apache.org/jira/browse/IGNITE-13646?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17237240#comment-17237240 ]
Anton Vinogradov commented on IGNITE-13646:
-------------------------------------------
Merged to ignite-ducktape.
> Turn failure detection timeout into a parameter in discovery ducktape test.
> ---------------------------------------------------------------------------
>
> Key: IGNITE-13646
> URL: https://issues.apache.org/jira/browse/IGNITE-13646
> Project: Ignite
> Issue Type: Bug
> Reporter: Vladimir Steshin
> Assignee: Vladimir Steshin
> Priority: Minor
> Labels: IEP-56, ducktape
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Failure detection timeout is now a parameter. Not a constant.
> Also, the value reduced for ZooKeeper tests.
> Additionally, let's use `IgniteConfiguration.localHost` instead of `TcpDiscoverySpi.localAddres`. The communication, other possible SPI use this setting too.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)