[
https://issues.apache.org/jira/browse/IGNITE-13016?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vladimir Steshin updated IGNITE-13016:
--------------------------------------
Description:
Backward checking of failed node rely on hardcoced timeout 100ms:
{code:java}
private boolean ServerImpls.isConnectionRefused(SocketAddress addr) {
try (Socket sock = new Socket()) {
sock.connect(addr, 100);
}
catch (ConnectException e) {
return true;
}
catch (IOException e) {
return false;
}
return false;
}
{code}
We should make it bound to configurable params like
IgniteConfiguration.failureDetectionTimeout.
Also, the maximal interval to chech previous node is
was:
Backward checking of failed node rely on hardcoced timeout 100ms:
{code:java}
private boolean ServerImpls.isConnectionRefused(SocketAddress addr) {
try (Socket sock = new Socket()) {
sock.connect(addr, 100);
}
catch (ConnectException e) {
return true;
}
catch (IOException e) {
return false;
}
return false;
}
{code}
We should make it bound to configurable params like
IgniteConfiguration.failureDetectionTimeout
> Remove hardcoded values/timeouts from backward checking of failed node.
> -----------------------------------------------------------------------
>
> Key: IGNITE-13016
> URL: https://issues.apache.org/jira/browse/IGNITE-13016
> Project: Ignite
> Issue Type: Sub-task
> Reporter: Vladimir Steshin
> Assignee: Vladimir Steshin
> Priority: Major
> Labels: iep-45
>
> Backward checking of failed node rely on hardcoced timeout 100ms:
> {code:java}
> private boolean ServerImpls.isConnectionRefused(SocketAddress addr) {
> try (Socket sock = new Socket()) {
> sock.connect(addr, 100);
> }
> catch (ConnectException e) {
> return true;
> }
> catch (IOException e) {
> return false;
> }
> return false;
> }
> {code}
> We should make it bound to configurable params like
> IgniteConfiguration.failureDetectionTimeout.
> Also, the maximal interval to chech previous node is
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
