Github user sjcorbett commented on the issue:
https://github.com/apache/brooklyn-server/pull/497
I appreciate your concern. I feel it depends on how you interpret the word
first in `getFirstReachableAddress`. Previously it related to reachability, now
it relates to the list of addresses input. My desire is to use to the latter
meaning. The mitigation is that the maximum length of time that callers will
wait is governed by the timeout argument, which in the only places this is
really used is whatever value the user has given for
`POLL_FOR_FIRST_REACHABLE_ADDRESS`, or five minutes if they didn't. The
reachability checks are still concurrent so it won't get significantly worse
when there are more addresses.
The changes forthcoming that I mentioned make how we determine reachability
and the addresses used for management of entities more flexible. In particular
users will be able to indicate whether they want a node's public or private
addresses to be preferred. It is in this scenario that I think we need to wait
until we've exhausted the preferences before choosing an address from the other
set.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
