[STORM-3679] misuse of nodeId as hostname in LoadAwareShuffleGrouping

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.0.0, 2.1.0, 2.2.0
• Fix Version/s: 2.3.0
• Assignee: Ethan Li
• Reporter: Ethan Li
• Created: 21/Jul/20 19:10
• Updated: 29/Jul/20 07:24
• Resolved: 28/Jul/20 14:03

Description

LoadAwareShuffleGrouping misuses nodeId as the hostname and it causes consistent invalid DNS queries for "hostnames" like 2a1f2cf3-c701-4621-9e93-640b4e63be48-<ip>.

This causes excessive unnecessary loads on nscd and DNS. Also because of this bug, every target tasks will be treated as at least RACK_LOCAL because if an ip address can't be determined, YahooDNSToSwitchMapping treats it as DEFAULT_RACK. This doesn't impact WORKER_LOCAL and HOST_LOCAL though.