[ https://forge.continuent.org/jira/browse/SEQUOIA-872?page=all ]
Gilles Rayrat resolved SEQUOIA-872:
-----------------------------------
Resolution: Fixed
Fixed in 2.10 branch
Waiting for 3.0 port
> Driver pinger should identify controllers by a InetSocketAddress, not by
> their InetAddress
> ------------------------------------------------------------------------------------------
>
> Key: SEQUOIA-872
> URL: https://forge.continuent.org/jira/browse/SEQUOIA-872
> Project: Sequoia
> Type: Task
> Components: JDBC Driver, Core
> Versions: Sequoia 2.10.3
> Reporter: Gilles Rayrat
> Assignee: Gilles Rayrat
> Fix For: Sequoia 2.10.4
>
>
> Currently, at the driver side, controllers are identified by their
> InetAddresses + port, with useless calls to getByName() calls when receiving
> udp pongs
> This can lead to confusing double entries in the controller list held by the
> controller watcher (typically when a controller comes back)
> This issue relates the driver impact of
> https://forge.continuent.org/jira/browse/SEQUOIA-804
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://forge.continuent.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
_______________________________________________
Sequoia mailing list
[email protected]
https://forge.continuent.org/mailman/listinfo/sequoia
