[jira] [Commented] (VCL-816) Nmap is very slow due to DNS

["ASF subversion and git services (JIRA)" <ji...@apache.org>]

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

ASF subversion and git services commented on VCL-816:
-----------------------------------------------------

Commit 1658844 from [~arkurth] in branch 'vcl/trunk'
[ https://svn.apache.org/r1658844 ]

VCL-816
Added "-n" switch to the command in utils.pm::nmap_port. This causes the command to run much faster.

VCL-16
Changed utils.pm::get_request_info to use cached info by default. For large cluster requests, each reservation process was retrieving the same image and other information over and over - n-squared problem.

VCL-174
Removed section from utils.pm::get_request_info which populates the natport table. This was being done by every cluster reservation for all other cluster reservations. Moved to State.pm::initialize.

Updated utils.pm::get_computer_info to only call get_computer_nathost_info if a nathostcomputermap entry exists for the computer.

> Nmap is very slow due to DNS
> ----------------------------
>
>                 Key: VCL-816
>                 URL: https://issues.apache.org/jira/browse/VCL-816
>             Project: VCL
>          Issue Type: Improvement
>          Components: vcld (backend)
>            Reporter: Andy Kurth
>            Assignee: Andy Kurth
>            Priority: Minor
>             Fix For: 2.4
>
>
> The backend code uses the nmap utility to determine if a remote node is responding to SSH.  This may take several seconds if DNS isn't configured.  There is a "-n" switch which causes the commands to run much quicker.
> The switch should probably be added.  We need to test how it works with both hostnames and IP addresses.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)