https://jira.whamcloud.com This file is an XML representation of an issue en-us 9.4.14 940014 05-12-2023 https://jira.whamcloud.com/browse/LU-1800 Lustre <p>I was just looking at <tt>lctl get_param mdt.&#42;.job_stats</tt> to see what it showed, now that <tt>test-framework.sh</tt> enables it by default. It appears that the "<tt>ll&#95;sa&#95;&lt;pid&gt;</tt>" threads are showing up as a separate job for every "<tt>ls</tt>" being run, instead of only "<tt>ls.&lt;uid&gt;</tt>" as I would expect.</p> <div class="preformatted panel" style="border-width: 1px;"><div class="preformattedContent panelContent"> <pre>- job_id: ll_sa_14097_0 snapshot_time: 1346211655 getattr: { samples: 5, unit: reqs } </pre> </div></div> <p>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 "<tt>ll_sa_&#42;</tt>" as the process name?</p> LU-1800

Job Stats shows statahead thread

Bug Major Resolved Fixed Ben Evans Andreas Dilger Tue, 28 Aug 2012 23:45:04 +0000 Wed, 29 May 2019 17:09:29 +0000 Wed, 29 May 2019 17:09:29 +0000 Lustre 2.3.0 Lustre 2.4.0 Lustre 2.10.1 0 3 <p>This is still an issue with 2.10.1 at least.</p> <p>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 <em>might</em> be possible to pass environment variables to new threads via <tt>kthread_create()</tt> at launch time, but I'm not positive.</p> <p>I'll take a look, is there a good reproducer I can use to see the problem?</p> <p>For reproducer, just enable jobstats on the client (e.g. <tt>lctl set_param jobid_var=procname_uid</tt>), run "<tt>ls -l</tt>" on a directory, and check jobstats on the server(s). </p> <p>Fixed in <a href="https://jira.whamcloud.com/browse/LU-10698" title="Specify complex JobIDs for Lustre" class="issue-link" data-issue-key="LU-10698"><del>LU-10698</del></a></p> Development Rank 1|hzv4gf: Rank (Obsolete) 4255 Severity