[jira] [Commented] (MESOS-7548) net::hostname takes 5 seconds on Windows

["Andrew Schwartzmeyer (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/MESOS-7548?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16277270#comment-16277270 ] 

Andrew Schwartzmeyer commented on MESOS-7548:
---------------------------------------------

By the way, this was narrowed down:

Prior to Windows 10 Build 16299, a Docker installation alongside the use of a Hyper-V external network adapter caused this. Docker would install an external Hyper-V virtual adapter, and a manually created one would would exist due to the use of VMs. With two external adaptors, the Mesos tests would slow to a crawl due to {{net::hostname}}. Disabling either adapter would resolve the issue.

Fortunately, in build 16299 (aka "Fall Creator's Update 2017) resolves this issue.

> net::hostname takes 5 seconds on Windows
> ----------------------------------------
>
>                 Key: MESOS-7548
>                 URL: https://issues.apache.org/jira/browse/MESOS-7548
>             Project: Mesos
>          Issue Type: Bug
>         Environment: Windows 10
>            Reporter: Andrew Schwartzmeyer
>            Assignee: Andrew Schwartzmeyer
>              Labels: stout, windows
>
> We've determined that when starting the master in a unit test, instead of milliseconds, it takes upwards of five seconds to start. However, providing a set of flags where `hostname` is specified, it takes less than a second. We've determined that the `net::hostname` call on Windows is taking an inordinate amount of time, and this is problematic when every instantiation of a master or agent uses it, especially across hundreds of tests.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)