From: Ben Evans <bevans@cray.com>
To: lustre-devel@lists.lustre.org
Subject: [lustre-devel] syncronous liblustreapi calls
Date: Thu, 22 Oct 2015 14:50:54 +0000 [thread overview]
Message-ID: <D24E700D.2737%jevans@cray.com> (raw)
Is there some architectural reason behind a lack of synchronous calls to set values?
As an example, the changelog_clear operation does some preliminary checking in liblustreapi for things like non-negative ranges, and that the changelog user is formatted correctly (not that the user actually exists).
If everything checks out, it sends off an async request and tells the user everything is fine. On the MDS, many things may go wrong (such as the range being invalid, or the user not existing), and that gets written to the logs on the MDS, but there doesn?t seem to be a way of telling the user that something went wrong.
Is there some backstory on this, or is it just an architectural consequence of the way Lustre works?
-Ben Evans
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.lustre.org/pipermail/lustre-devel-lustre.org/attachments/20151022/753cd6ff/attachment.htm>
next reply other threads:[~2015-10-22 14:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-22 14:50 Ben Evans [this message]
-- strict thread matches above, loose matches on Subject: below --
2015-10-25 7:44 [lustre-devel] syncronous liblustreapi calls Dilger, Andreas
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=D24E700D.2737%jevans@cray.com \
--to=bevans@cray.com \
--cc=lustre-devel@lists.lustre.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.