Sequence ID calibration for mis-ordered requests
draft-mzhang-nfsv4-sequence-id-calibration-03
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Zhang Mingqian , JingYang , Sai Chakravarthy Tangudu , Rijesh Kunhi Parambattu | ||
| Last updated | 2023-10-23 (Latest revision 2023-04-21) | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
This document updates RFC7862, Network File System (NFS) version 4 minor version 2, by adding two operations to prevent the client from destroying session when getting the reply of a mis-ordered request with NFS4ERR_SEQ_MISORDERED. In NFSv4 minor version 1, sequence ID is used to ensure that the size of the needed reply cache is tightly bounded. If the server gets a mis-ordered request, the client will often break the session and establish a new session with the server. This approach results in a significant burden on the client and the server. During the process of session rebuilding, IO performance will be affected. This is especially troublesome when network latency is substantial, as, for example when client and server are in different locations. This document will propose extensions to NFSv4 that would allow client reconnection to be dispensed with.
Authors
Zhang Mingqian
JingYang
Sai Chakravarthy Tangudu
Rijesh Kunhi Parambattu
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)