Opened 17 years ago

Last modified 9 years ago

#86 new enhancement

IZ488: INSTALL NOTES: Separate set of gid-ranges on a nfs-server

Reported by: fug09511 Owned by:
Priority: normal Milestone:
Component: sge Version: 5.3
Severity: Keywords: PC Linux doc
Cc:

Description

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

        Issue #:      488              Platform:     PC            Reporter: fug09511 (fug09511)
       Component:     gridengine          OS:        Linux
     Subcomponent:    doc              Version:      5.3              CC:    None defined
        Status:       NEW              Priority:     P3
      Resolution:                     Issue type:    ENHANCEMENT
                                   Target milestone: ---
      Assigned to:    markob (markob)
      QA Contact:     surajp
          URL:
       * Summary:     INSTALL NOTES: Separate set of gid-ranges on a nfs-server
   Status whiteboard:
      Attachments:

     Issue 488 blocks:
   Votes for issue 488:


   Opened: Mon Feb 10 06:18:00 -0700 2003 
------------------------


The set of gid-ranges on an execution host
exporting file-systems to other execution hosts
should be disjoint to the sets of gid-ranges of
these hosts.
Otherwise it can happen that a batchjob on a
nfs-client has the same gid as a batchjob on the
nfs-server.
As the nfs-server-process takes over the gid of
the client the batchjob on the nfs-server is
charged with the consumption of cpu of the
nfs-server-process and this can lead to an
abnormal termination of and a wrong accounting
record for this job.

   ------- Additional comments from andreas Tue Jul 20 10:07:48 -0700 2004 -------
Changed summary.
Possibly install notes are the right place for this.

   ------- Additional comments from andreas Thu Oct 21 07:25:03 -0700 2004 -------
Assign Admin/User/Install guide related issues to Mark O'Brien.

   ------- Additional comments from surajp Mon Mar 23 01:35:52 -0700 2009 -------
Reassigning to Suraj.

Change History (0)

Note: See TracTickets for help on using tickets.