From: redshield88888 <redshield88888@gmail.com>
To: linux-nfs@vger.kernel.org
Subject: How does the metadata-server synchronizes with data-servers ?
Date: Sun, 23 May 2010 07:04:04 +0900 [thread overview]
Message-ID: <4BF854D4.5090500@gmail.com> (raw)
Hi, all.
I've succeeded to install pNFS-enabled kernel. But I wonder that how
does pNFS behaviour.
Especially, about synchronizations between the MetaDataServer and
DataServers.
I'd read a paper of the Calsoft's. This paper said like "There is
heartbeats betweenthe MetaDataServer and DataServers".
http://www.calsoftinc.com/download_pdf/White%20Papers%20-%20pnfs.pdf
When will this heartbeat be started ? The instruction below is not describe
about this, but the heartbeat will works, w'not this ?
http://wiki.linux-nfs.org/wiki/index.php/PNFS_Setup_Instructions
next reply other threads:[~2010-05-22 22:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-22 22:04 redshield88888 [this message]
2010-05-24 13:52 ` How does the metadata-server synchronizes with data-servers ? William A. (Andy) Adamson
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=4BF854D4.5090500@gmail.com \
--to=redshield88888@gmail.com \
--cc=linux-nfs@vger.kernel.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 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).