Opened 16 years ago

Last modified 11 years ago

#297 new defect

IZ1893: endpoint not unique message should be created after connection test

Reported by: crei Owned by:
Priority: normal Milestone:
Component: sge Version: 6.0
Severity: Keywords: communication


[Imported from gridengine issuezilla]

        Issue #:      1893                Platform:     All      Reporter: crei (crei)
       Component:     gridengine             OS:        All
     Subcomponent:    communication       Version:      6.0         CC:    None defined
        Status:       NEW                 Priority:     P3
      Resolution:                        Issue type:    DEFECT
                                      Target milestone: 6.2
      Assigned to:    dom (dom)
      QA Contact:     crei
       * Summary:     endpoint not unique message should be created after connection test
   Status whiteboard:

     Issue 1893 blocks:
   Votes for issue 1893:

   Opened: Tue Nov 15 01:47:00 -0700 2005 

The commlib protocol has a weakness:

When a client (e.g. execd) is killed by -9 the server (e.g. qmaster)
will not get an error immediately for a broken connection.

When now the client is restarted the new created client gets a
"endpoint not unique" message and the server will set a flag to
check the old connection (which has the same component id) if it
still exists (by sending a sim (Status Information Message) to
the broken connection. This will result that the server will finally
destroy the broken connection to the old client.

A second try of the new started client (which got a "endpoint not unique"
error the first time) is successful.

The Problem is that the server should not send the "endpoint not unique"
message before he has checked the previous one. If this is the case the
client doesn't have to make a re-try.

   ------- Additional comments from crei Tue Dec 27 08:21:53 -0700 2005 -------
It's more a defect than an enhancment request

   ------- Additional comments from joga Thu Aug 2 08:54:28 -0700 2007 -------
planning to fix it for 6.2.

Change History (0)

Note: See TracTickets for help on using tickets.