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 Belyak (JIRA)" <ji...@apache.org> on 2017/04/10 18:16:41 UTC
[jira] [Assigned] (IGNITE-4799) Remove
TcpDiscoverySpi.heartbeatsFrequency parameter
[ https://issues.apache.org/jira/browse/IGNITE-4799?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Alexander Belyak reassigned IGNITE-4799:
----------------------------------------
Assignee: Alexander Belyak (was: Yakov Zhdanov)
> Remove TcpDiscoverySpi.heartbeatsFrequency parameter
> ----------------------------------------------------
>
> Key: IGNITE-4799
> URL: https://issues.apache.org/jira/browse/IGNITE-4799
> Project: Ignite
> Issue Type: Bug
> Reporter: Denis Magda
> Assignee: Alexander Belyak
> Labels: important
> Fix For: 2.0
>
>
> {{TcpDiscoverySpi.heartbeatsFrequency}} is no longer used to adjust the heartbeats frequence. It affects the frequency of metrics messages sent over the cluster ring.
> The following has to be done as a part of 2.0 release:
> * Remove {{TcpDiscoverySpi.heartbeatsFrequency}} parameter.
> * Use {{IgniteConfiguraion.getMetricsUpdateFrequency}} to adjust the rate of metrics messages.
> * Make sure {{IgniteConfiguraion.getMetricsUpdateFrequency}} and metrics messages are not participated in the failure detection process. We have to clean up legacy code in {{ServerImpl}}.
> Refer to this discussion for more details:
> http://apache-ignite-developers.2346864.n4.nabble.com/Renaming-TcpDiscoverySpi-heartbeatsFrequency-to-TcpDiscoverySpi-metricsUpdateFrequency-td14941.html
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)