[
https://issues.apache.org/jira/browse/TUBEMQ-141?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17113988#comment-17113988
]
Guocheng Zhang commented on TUBEMQ-141:
---------------------------------------
In addition, a default preferred Network interface can be added: the address is
first obtained from the default preferred Network interface, and if there is no
requirement, the address is obtained from other Network interfaces. The default
preferred network interface should be configurable by user.
I wonder if it is necessary to add the following: if there is no IP that meets
the requirements from all the Network interfaces, then try to obtain a local IP
from InetAddress class.
See if there are repetitions and unnecessary points
> Remove the requirement to provide localHostIP
> ---------------------------------------------
>
> Key: TUBEMQ-141
> URL: https://issues.apache.org/jira/browse/TUBEMQ-141
> Project: Apache TubeMQ
> Issue Type: Improvement
> Reporter: Guocheng Zhang
> Assignee: viviel
> Priority: Major
> Fix For: 0.5.0
>
> Attachments: image-2020-05-21-20-54-37-013.png
>
>
> The initial requirement to provide localHostIP during initialization is
> because we have multiple network cards and multiple IPs in our environment.
> The initial implementation is to find the first IP from the specified
> NetworkInterface and report it, but It is found that sometimes the specified
> NetworkInterface is not configured with IP, so, we consider the user is
> required to provide a local IP:
> !image-2020-05-21-20-54-37-013.png!
> After a period of use, the user feedback the API is cumbersome to use. The
> best way is to provide a configurable NetworkInterface API, so if the IP is
> not found, we can change the NetworkInterface.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
