[OAK-3418] ClusterNodeInfo uses irrelevant network interface IDs on Windows

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 1.0.21, 1.2.6, 1.3.6
• Fix Version/s: 1.0.22, 1.2.7, 1.3.7, 1.4
• Component/s: core
• Labels: resilience
• Assignee: Julian Reschke
• Reporter: Julian Reschke
• Created: 17/Sep/15 15:24
• Updated: 08/Oct/19 15:22
• Resolved: 22/Sep/15 15:37

Description

On Windows, all kinds of adapters (tunnel, VPN) return a hardware address of 00-00-00-00-00-00-00-E0 (note 8 bytes, not 6). These addresses are useless for the identification of the machine, however they get used because they are the lowest value.

A potential fix is to change the validity check to:

if (mac != null && mac.length == 6)

Issue Links

• relates to: OAK-3424 ClusterNodeInfo does not pick an existing entry on startup
• relates to: OAK-3425 Improve DocumentNodeStore startup/shutdown diagnostics