Vladimir Ozerov commented on IGNITE-7029:

[~tledkov-gridgain], my comments:
1) {{ConnectionPropertiesImpl}} - I think it is not good idea to resolve 
address on startup. For example, what if user had no connection when 
application was started, but then recovered it? Or what if DNS settings were 
changed in runtime, so invalid address became valid? We should not force use to 
restart his app in this case. My proposal is to call 
{{InetAddress.getAllByName}} at *connection time* and then try to connect to 
every returned address iteratively.
2) {{JdbcThinSSLUtil.createSSLSocket}} - consequence of p.1, should be fixed as 

> Add an ability to provide multiple connection addresses for thin JDBC driver
> ----------------------------------------------------------------------------
>                 Key: IGNITE-7029
>                 URL: https://issues.apache.org/jira/browse/IGNITE-7029
>             Project: Ignite
>          Issue Type: Improvement
>          Components: jdbc, sql
>    Affects Versions: 2.3
>            Reporter: Valentin Kulichenko
>            Assignee: Taras Ledkov
>            Priority: Major
> Currently we allow only to provide one address when connecting via thin JDBC 
> driver. This has to issues:
> * If node driver is connected to goes down, the driver stops working.
> * Driver has to always go though the same node - this is a bottleneck.
> As a simple solution we can allow to provide multiple addresses, like MySQL 
> does for example: 
> https://dev.mysql.com/doc/connector-j/5.1/en/connector-j-usagenotes-j2ee-concepts-managing-load-balanced-connections.html

This message was sent by Atlassian JIRA

Reply via email to