[LU-1800] Job Stats shows statahead thread Created: 28/Aug/12 Updated: 29/May/19 Resolved: 29/May/19 |
|
| Status: | Resolved |
| Project: | Lustre |
| Component/s: | None |
| Affects Version/s: | Lustre 2.3.0, Lustre 2.4.0, Lustre 2.10.1 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major |
| Reporter: | Andreas Dilger | Assignee: | Ben Evans (Inactive) |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Severity: | 3 |
| Rank (Obsolete): | 4255 |
| Description |
|
I was just looking at lctl get_param mdt.*.job_stats to see what it showed, now that test-framework.sh enables it by default. It appears that the "ll_sa_<pid>" threads are showing up as a separate job for every "ls" being run, instead of only "ls.<uid>" as I would expect. - job_id: ll_sa_14097_0
snapshot_time: 1346211655
getattr: { samples: 5, unit: reqs }
Is it possible to do something like is done for IO, to store the jobid into the inode for the statahead, or pass the JobID on to the statahead thread, so that it doesn't send "ll_sa_*" as the process name? |
| Comments |
| Comment by Andreas Dilger [ 19/Apr/18 ] |
|
This is still an issue with 2.10.1 at least. Ben, is there any chance you could look into this? I think passing on the "parent" JobID from the process running "ls" to the statahead thread would be best. It might be possible to pass environment variables to new threads via kthread_create() at launch time, but I'm not positive. |
| Comment by Ben Evans (Inactive) [ 19/Apr/18 ] |
|
I'll take a look, is there a good reproducer I can use to see the problem? |
| Comment by Andreas Dilger [ 20/Apr/18 ] |
|
For reproducer, just enable jobstats on the client (e.g. lctl set_param jobid_var=procname_uid), run "ls -l" on a directory, and check jobstats on the server(s). |
| Comment by Ben Evans (Inactive) [ 29/May/19 ] |
|
Fixed in |