Uploaded image for project: 'Lustre'
  1. Lustre
  2. LU-12330

Support per-session JOBID without using the environment

XMLWordPrintable

    • Icon: Improvement Improvement
    • Resolution: Fixed
    • Icon: Minor Minor
    • Lustre 2.13.0
    • None
    • None
    • 9223372036854775807

      Reading from the environment of a process is something only that process should do. The current jobid code does this in the kernel and there is good reason to expect resistance to this when we resubmit the code for upstream inclusion.

      So we need a different way to provide a job-id which is common to all tasks in a job across a cluster, but not necessarily all tasks on any given node.

      A proposed way to do this is to leverage the "session-id" concept (see setsid(1)).

      If we can associate a jobid with a session-id, then every session servicing a given job can be given the same jobid. The kernel can easily get the session-id for a process, and can then use an internal mapping to map this to the correct jobid.

       

            neilb Neil Brown (Inactive)
            neilb Neil Brown (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated:
              Resolved: