From: Andreas Dilger <adilger@whamcloud.com>
To: Sudheendra Sampath <sudheendra.sampath@gmail.com>
Cc: "lustre-devel@lists.lustre.org" <lustre-devel@lists.lustre.org>
Subject: Re: [lustre-devel] Getting client UUID from transaction code (osd_trans_create) - osd-zfs
Date: Sat, 23 Jan 2021 11:32:07 +0000 [thread overview]
Message-ID: <80AB5C3C-C916-4058-8B80-BF4380C3F65D@whamcloud.com> (raw)
In-Reply-To: <CABnqofyTN6Cr8JaMgeoke5TWG9j0JL_vMq03YPd8sYuRHXfqcw@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 696 bytes --]
On Jan 19, 2021, at 12:40, Sudheendra Sampath <sudheendra.sampath@gmail.com<mailto:sudheendra.sampath@gmail.com>> wrote:
When I have multiple 'remote' clients writing data, I am trying to find a way to recognize which client data I am writing to the underlying storage.
Appreciate if anyone in this list can point me in the right direction to access remote client UUID.
Probably the best way to do this is to set the "JobID" on the client, and then check "lctl get_param {mdt,obdfilte}r.*.job_stats" on the servers. You can find a detailed description of JobStats in the Lustre Operations Manual.
Cheers, Andreas
--
Andreas Dilger
Principal Lustre Architect
Whamcloud
[-- Attachment #1.2: Type: text/html, Size: 3224 bytes --]
[-- Attachment #2: Type: text/plain, Size: 165 bytes --]
_______________________________________________
lustre-devel mailing list
lustre-devel@lists.lustre.org
http://lists.lustre.org/listinfo.cgi/lustre-devel-lustre.org
prev parent reply other threads:[~2021-01-23 11:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-19 19:40 [lustre-devel] Getting client UUID from transaction code (osd_trans_create) - osd-zfs Sudheendra Sampath
2021-01-23 11:32 ` Andreas Dilger [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=80AB5C3C-C916-4058-8B80-BF4380C3F65D@whamcloud.com \
--to=adilger@whamcloud.com \
--cc=lustre-devel@lists.lustre.org \
--cc=sudheendra.sampath@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).