[LU-12330] Support per-session JOBID without using the environment Created: 23/May/19 Updated: 07/Feb/24 Resolved: 25/Nov/19 |
|
| Status: | Resolved |
| Project: | Lustre |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | Lustre 2.13.0 |
| Type: | Improvement | Priority: | Minor |
| Reporter: | Neil Brown | Assignee: | Neil Brown |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Issue Links: |
|
||||||||||||||||||||||||
| Rank (Obsolete): | 9223372036854775807 | ||||||||||||||||||||||||
| Description |
|
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.
|
| Comments |
| Comment by Gerrit Updater [ 30/May/19 ] |
|
Neil Brown (neilb@suse.com) uploaded a new patch: https://review.whamcloud.com/34995 |
| Comment by Gerrit Updater [ 25/Jun/19 ] |
|
Oleg Drokin (green@whamcloud.com) merged in patch https://review.whamcloud.com/34995/ |
| Comment by James A Simmons [ 25/Jun/19 ] |
|
Shall we add addition test or just close this ticket? |
| Comment by James A Simmons [ 15/Jul/19 ] |
|
Looks like documentation for this work was added with https://review.whamcloud.com/#/c/35503 All that is left is adding test for this. |
| Comment by Gerrit Updater [ 12/Aug/20 ] |
|
Neil Brown (neilb@suse.de) uploaded a new patch: https://review.whamcloud.com/39656 |