You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Ignite TC Bot (Jira)" <ji...@apache.org> on 2019/12/18 12:53:00 UTC
[jira] [Commented] (IGNITE-11320) JDBC Thin: add support for
individual reconnect in case of best effort affinity mode.
[ https://issues.apache.org/jira/browse/IGNITE-11320?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16999119#comment-16999119 ]
Ignite TC Bot commented on IGNITE-11320:
----------------------------------------
{panel:title=Branch: [pull/7152/head] Base: [master] : No blockers found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
[TeamCity *--> Run :: All* Results|https://ci.ignite.apache.org/viewLog.html?buildId=4848330&buildTypeId=IgniteTests24Java8_RunAll]
> JDBC Thin: add support for individual reconnect in case of best effort affinity mode.
> -------------------------------------------------------------------------------------
>
> Key: IGNITE-11320
> URL: https://issues.apache.org/jira/browse/IGNITE-11320
> Project: Ignite
> Issue Type: Bug
> Components: jdbc
> Reporter: Alexander Lapin
> Assignee: Andrey Mashenkov
> Priority: Major
> Labels: iep-23
> Fix For: 2.9
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Currently in case of best effort affinity mode we either connect to all nodes specified by user or throw SQLException. Given logic needs to be improved.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)