[IGNITE-4799] Remove TcpDiscoverySpi.heartbeatsFrequency parameter

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 2.0
• Component/s: general
• Labels: important
• Assignee: Unassigned
• Reporter: Denis A. Magda
• Created: 07/Mar/17 19:20
• Updated: 26/Apr/17 16:14
• Resolved: 26/Apr/17 12:48

Description

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

Issue Links

• Blocked: IGNITE-5015 In TcpCommunicationSpi use IgniteConfiguration.clientFailureDetectionTimeout
• relates to: IGNITE-5062 .NET: Support new communication parameters in configuration
• relates to: IGNITE-5060 Check configuration parameters on the Integer overflowing
• relates to: IGNITE-5042 Add internal ring wide msg for status check

Sub-Tasks

• .NET: Support new communication parameters in configuration: Resolved