You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@storm.apache.org by "Ethan Li (Jira)" <ji...@apache.org> on 2020/07/21 19:11:00 UTC

[jira] [Assigned] (STORM-3679) misuse of nodeId as hostname in LoadAwareShuffleGrouping

     [ https://issues.apache.org/jira/browse/STORM-3679?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ethan Li reassigned STORM-3679:
-------------------------------

    Assignee: Ethan Li

> misuse of nodeId as hostname in LoadAwareShuffleGrouping
> --------------------------------------------------------
>
>                 Key: STORM-3679
>                 URL: https://issues.apache.org/jira/browse/STORM-3679
>             Project: Apache Storm
>          Issue Type: Bug
>    Affects Versions: 2.0.0, 2.1.0, 2.2.0
>            Reporter: Ethan Li
>            Assignee: Ethan Li
>            Priority: Major
>
>  
> 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.
>  



--
This message was sent by Atlassian Jira
(v8.3.4#803005)