[IGNITE-752] Speed up failure detection

• Type: Bug
• Status: Closed
• Priority: Blocker
• Resolution: Fixed
• Fix Version/s: sprint-7
• Assignee: Yakov Zhdanov
• Reporter: Yakov Zhdanov
• Created: 14/Apr/15 20:24
• Updated: 14/Feb/18 14:06
• Resolved: 24/Jul/15 12:27

Description

I think we can (1) make grid configuration significantly easier and (2) speed up failure detection.

Here are disco SPI configuration properties which are responsible for failure detection:

1. reconnectCount,
2. sockTimeout,
3. networkTImeout,
4. ackTImeout,
5. maxAckTimeout,
6. heartbeatFrequency
7. maxMissedHearbeats

Same for communication SPI

1. reconnectCount,
2. maxConnTimeout,
3. connTimeout

So, we have 10 or even more properties.

We did it to address half-opened sockets problem (which is pretty common for cloud environment) and GC pauses which may happen on cluster nodes - we can increase ack timeouts to prevent them from being kicked off the topology.

By setting value for these props I set timeout for failure detection. Why do we need such great number of parameters instead of having 1 on IgniteConfiguration - nodeResponseThreshold (or failureDetectionThreshold - can anyone propose better name?).

All other parameters will be calculated automatically (I think user can still set some of them for full control over situation - need to decide if this is needed.)

Issue Links

• is related to: IGNITE-7704 Document IgniteConfiguration, TcpDiscoverySpi, TcpCommunicationSpi timeouts and their relations