New - scheduler internal host caching does not regard short hostnames vs. f

http://gridengine.sunsource.net/issues/show_bug.cgi?i
d=2398
                 Issue #|2398
                 Summary|scheduler internal host caching
does not regard short 
                        |hostnames vs. fqdn hostname
               Component|gridengine
                 Version|6.1
                Platform|All
                     URL|
              OS/Version|All
                  Status|NEW
       Status whiteboard|
                Keywords|
              Resolution|
              Issue type|DEFECT
                Priority|P3
            Subcomponent|scheduling
             Assigned to|andreas
             Reported by|andreas






------- Additional comments from andreassunsource.net Fri Oct 12 07:39:32 -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.

------------------------------------------------------------
---------
To unsubscribe, e-mail: issues-unsubscribegridengine.sunsource.net
For additional commands, e-mail: issues-helpgridengine.sunsource.net