[OMID-123] Allow starting Omid on machines without en or eth interfaces.

• Type: Sub-task
• Status: Resolved
• Priority: Major
• Resolution: Implemented
• Affects Version/s: 1.0.1
• Assignee: Yoni Gottesman
• Reporter: Lars Hofhansl
• Created: 26/Dec/18 11:38
• Updated: 18/Sep/23 06:11
• Resolved: 25/Dec/19 18:28

Description

Currently there's an assumption that there must be an eth* or a configured en* interface in order to bind to a specific address.

Exception in thread "main" java.lang.IllegalArgumentException: No network 'en*'/'eth*' interfaces found
at org.apache.omid.NetworkUtils.getDefaultNetworkInterface(NetworkUtils.java:52)
at org.apache.omid.tso.TSOServerConfig.<init>(TSOServerConfig.java:88)
at org.apache.omid.tso.TSOServerConfig.<init>(TSOServerConfig.java:56)
at org.apache.omid.tso.TSOServer.main(TSOServer.java:147)

The first question is: Why don't we just allow to bind to ::?
Second, we can at least provide a default way to start when no en/eth interface is available.

Issue Links

• relates to: OMID-248 Transactional Phoenix tests fail on Java 17 in getDefaultNetworkInterface
• relates to: PHOENIX-5082 Observations about the Phoenix-Omid integration