[LUDOC-210] Clarify Jobstats documentation and add ALPS environment variable Created: 05/Dec/13  Updated: 05/Dec/14  Resolved: 09/May/14

Status: Closed
Project: Lustre Documentation
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Improvement Priority: Minor
Reporter: Ryan Haasken Assignee: Richard Henwood (Inactive)
Resolution: Fixed Votes: 0
Labels: None

Rank (Obsolete): 11916

 Description   

Cray's Application Level Placement Scheduler (ALPS) now sets an environment variable identifying the running application. That environment variable is ALPS_APP_ID. This needs to be documented in section 12.1.1 of the Lustre Manual. A row for ALPS should be added to the table in that section.

In addition, the table and its description are somewhat misleading. It sounds like the value of jobid_var can only be one of the values listed in the table, which is not true. The table just contains special values for the jobid_var and examples of the environment variables set by some job schedulers.

The table should be split into two tables, and the columns should be swapped. The first table should have a correspondence between job schedulers and environment variables. The second table should contain the two special values: procname_uid, and disable.

The description preceding the first table should read something like this:

"The following table shows the environment variables which are set by various job schedulers. Set jobid_var to the value for your job scheduler to collect statistics per job."

The description preceding the second table should be something like this:

"This table shows two special values for jobid_var and their effects."



 Comments   
Comment by Ryan Haasken [ 17/Dec/13 ]

Here is my proposed patch:

http://review.whamcloud.com/#/c/8577/

Comment by Ryan Haasken [ 23/Dec/13 ]

Patch has landed, and this issue can be resolved.

Comment by Jessica A. Popp (Inactive) [ 10/Feb/14 ]

Richard, please review the above and close the ticket if appropriate.

-Jessica

Comment by Richard Henwood (Inactive) [ 09/May/14 ]

Ryan's patch fixed this issue.

Generated at Sat Feb 10 03:41:06 UTC 2024 using Jira 9.4.14#940014-sha1:734e6822bbf0d45eff9af51f82432957f73aa32c.