[
https://issues.apache.org/jira/browse/IGNITE-24965?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ilya Shishkov updated IGNITE-24965:
-----------------------------------
Description:
Error in reconnect future example [1] should be corrected, eg.:
{code}
IgniteCache cache = ignite.getOrCreateCache(new
CacheConfiguration<>("myCache"));
try {
cache.put(1, "value");
} catch (IgniteClientDisconnectedException e) {
e.reconnectFuture().get(); // Wait until the client is reconnected.
// proceed
}
{code}
Moreover, we should investigate real behavior.
Links:
# https://ignite.apache.org/docs/latest/clustering/connect-client-nodes
was:
This recommendation can be harmful and should be removed from the documentation:
{quote}
However, in stable low-latency networks, you can set the parameter to ~200
milliseconds in order to detect and react to failures more quickly.
{quote}
https://ignite.apache.org/docs/latest/clustering/network-configuration#connection-timeouts
> [doc] Error in reconnect future example
> ---------------------------------------
>
> Key: IGNITE-24965
> URL: https://issues.apache.org/jira/browse/IGNITE-24965
> Project: Ignite
> Issue Type: Task
> Reporter: Ilya Shishkov
> Priority: Minor
> Labels: ignite-2, ise
>
> Error in reconnect future example [1] should be corrected, eg.:
> {code}
> IgniteCache cache = ignite.getOrCreateCache(new
> CacheConfiguration<>("myCache"));
> try {
> cache.put(1, "value");
> } catch (IgniteClientDisconnectedException e) {
> e.reconnectFuture().get(); // Wait until the client is reconnected.
> // proceed
> }
> {code}
> Moreover, we should investigate real behavior.
> Links:
> # https://ignite.apache.org/docs/latest/clustering/connect-client-nodes
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
