Opened 12 years ago

Last modified 9 years ago

#469 new defect

IZ2398: scheduler internal host caching does not regard short hostnames vs. fqdn hostname

Reported by: andreas Owned by:
Priority: normal Milestone:
Component: sge Version: 6.1
Severity: Keywords: scheduling
Cc:

Description

[Imported from gridengine issuezilla http://gridengine.sunsource.net/issues/show_bug.cgi?id=2398]

        Issue #:      2398             Platform:     All      Reporter: andreas (andreas)
       Component:     gridengine          OS:        All
     Subcomponent:    scheduling       Version:      6.1         CC:    None defined
        Status:       NEW              Priority:     P3
      Resolution:                     Issue type:    DEFECT
                                   Target milestone: ---
      Assigned to:    andreas (andreas)
      QA Contact:     andreas
          URL:
       * Summary:     scheduler internal host caching does not regard short hostnames vs. fqdn hostname
   Status whiteboard:
      Attachments:

     Issue 2398 blocks:
   Votes for issue 2398:


   Opened: Fri Oct 12 07:39:00 -0700 2007 
------------------------


DESCRIPTION:
Scheduler performs suboptimal in the following case:

(1) an execution node resolves it's own name as fqdn and thus causes the
automatically created host_conf(5) to have a long name such as
"brag.germany.sun.com"

(2) the same host is accepted in the hostgroup(5) with short name "brag", so
that the queue instance for that host inherit the short name

due to hostname strings being used by the scheduling code as to cache already
checked hosts this has an impact on dispatching performance: Reason is that
currently only strcmp() is used cache access instead of sge_hostcmp()

SUGGESTED FIX:
Short term fix is consistent use of sge_hostcmp() for host caching inside
scheduler code.

Long term fix could be to ensure queue instance hostnames inherited from
hostgroup(5) configuration are identical with host_conf(5) hostnames in case of
automated execution host object creation.

Change History (0)

Note: See TracTickets for help on using tickets.