[
https://issues.apache.org/jira/browse/IGNITE-11599?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16807125#comment-16807125
]
Ignite TC Bot commented on IGNITE-11599:
----------------------------------------
{panel:title=--> Run :: All: Possible
Blockers|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#d04437}Platform C++ (Linux Clang){color} [[tests 0 TIMEOUT , Exit Code
, Failure on metric |https://ci.ignite.apache.org/viewLog.html?buildId=3482324]]
{color:#d04437}_Licenses Headers_{color} [[tests 0 Exit Code
|https://ci.ignite.apache.org/viewLog.html?buildId=3482331]]
{color:#d04437}JDBC Driver{color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=3482328]]
* IgniteJdbcDriverTestSuite: JdbcThinConnectionSelfTest.testInvalidEndpoint -
0,0% fails in last 366 master runs.
{panel}
[TeamCity *--> Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=3444195&buildTypeId=IgniteTests24Java8_RunAll]
> Thin client doesn't have proper retry
> -------------------------------------
>
> Key: IGNITE-11599
> URL: https://issues.apache.org/jira/browse/IGNITE-11599
> Project: Ignite
> Issue Type: Bug
> Components: thin client
> Reporter: Evgenii Zhuravlev
> Assignee: Roman Shtykh
> Priority: Major
> Fix For: 2.8
>
> Time Spent: 40m
> Remaining Estimate: 0h
>
> In case when one of the nodes from the addresses list is nor available, there
> is a chance that you will see "Ignite cluster is unavailable" even if other
> nodes are running.
> {code:java}
> List<String> addrs = new ArrayList<String>(2);
> addrs.add("127.0.0.1:10800");
> addrs.add("127.0.0.1:10801");
> ClientConfiguration cfg = new
> ClientConfiguration().setAddresses(addrs.toArray(new String[]{}));
> IgniteClient igniteClient = Ignition.startClient(cfg)
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
