# 因果一致性和读写关注 通过MongoDB的[因果一致性客户端会话](https://docs.mongodb.com/manual/core/read-isolation-consistency-recency/#sessions)，读写问题的不同组合可提供不同的 [因果一致性保证](https://docs.mongodb.com/manual/core/read-isolation-consistency-recency/#causal-consistency-guarantees)。如果定义因果一致性以表示耐久性，则下表列出了各种组合提供的特定保证： | 阅读关注 | 写关注 | 阅读自己的文章 | 单调读 | 单调写 | 写跟读 | | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------- | --- | --- | --- | | \[`"majority"`]\([https://docs.mongodb.com/manual/reference/read-concern-majority/#readconcern."majority](https://docs.mongodb.com/manual/reference/read-concern-majority/#readconcern.%22majority)") | \[`"majority"`]\([https://docs.mongodb.com/manual/reference/write-concern/#writeconcern."majority](https://docs.mongodb.com/manual/reference/write-concern/#writeconcern.%22majority)") | ✅ | ✅ | ✅ | ✅ | | \[`"majority"`]\([https://docs.mongodb.com/manual/reference/read-concern-majority/#readconcern."majority](https://docs.mongodb.com/manual/reference/read-concern-majority/#readconcern.%22majority)") | [`{ w: 1 }`](https://docs.mongodb.com/manual/reference/write-concern/#writeconcern.) | | ✅ | | ✅ | | \[`"local"`]\([https://docs.mongodb.com/manual/reference/read-concern-local/#readconcern."local](https://docs.mongodb.com/manual/reference/read-concern-local/#readconcern.%22local)") | [`{ w: 1 }`](https://docs.mongodb.com/manual/reference/write-concern/#writeconcern.) | | | | | | \[`"local"`]\([https://docs.mongodb.com/manual/reference/read-concern-local/#readconcern."local](https://docs.mongodb.com/manual/reference/read-concern-local/#readconcern.%22local)") | \[`"majority"`]\([https://docs.mongodb.com/manual/reference/write-concern/#writeconcern."majority](https://docs.mongodb.com/manual/reference/write-concern/#writeconcern.%22majority)") | | | ✅ | | 如果因果一致性表示持久性，那么从表中可以看出，只有具有\[`"majority"`]\([https://docs.mongodb.com/manual/reference/read-concern-majority/#readconcern."majority")读关注度的读取操作和具有\[\`"majority"\`\](https://docs.mongodb.com/manual/reference/write-concern/#writeconcern."majority")写关注度的写入操作才能保证所有四个因果一致性保证。也就是说，](https://docs.mongodb.com/manual/reference/read-concern-majority/#readconcern.%22majority%22%29%E8%AF%BB%E5%85%B3%E6%B3%A8%E5%BA%A6%E7%9A%84%E8%AF%BB%E5%8F%96%E6%93%8D%E4%BD%9C%E5%92%8C%E5%85%B7%E6%9C%89\[%60%22majority%22%60]%28https://docs.mongodb.com/manual/reference/write-concern/#writeconcern.%22majority%22%29%E5%86%99%E5%85%B3%E6%B3%A8%E5%BA%A6%E7%9A%84%E5%86%99%E5%85%A5%E6%93%8D%E4%BD%9C%E6%89%8D%E8%83%BD%E4%BF%9D%E8%AF%81%E6%89%80%E6%9C%89%E5%9B%9B%E4%B8%AA%E5%9B%A0%E6%9E%9C%E4%B8%80%E8%87%B4%E6%80%A7%E4%BF%9D%E8%AF%81%E3%80%82%E4%B9%9F%E5%B0%B1%E6%98%AF%E8%AF%B4%EF%BC%8C) [因果一致的客户端会话](https://docs.mongodb.com/manual/core/read-isolation-consistency-recency/#sessions)只能保证以下方面的因果一致性： * \[`"majority"`]\([https://docs.mongodb.com/manual/reference/read-concern-majority/#readconcern."majority")关注阅读操作；也就是说，读取操作将返回大多数复制集成员已确认且持久的数据。](https://docs.mongodb.com/manual/reference/read-concern-majority/#readconcern.%22majority%22%29%E5%85%B3%E6%B3%A8%E9%98%85%E8%AF%BB%E6%93%8D%E4%BD%9C%EF%BC%9B%E4%B9%9F%E5%B0%B1%E6%98%AF%E8%AF%B4%EF%BC%8C%E8%AF%BB%E5%8F%96%E6%93%8D%E4%BD%9C%E5%B0%86%E8%BF%94%E5%9B%9E%E5%A4%A7%E5%A4%9A%E6%95%B0%E5%A4%8D%E5%88%B6%E9%9B%86%E6%88%90%E5%91%98%E5%B7%B2%E7%A1%AE%E8%AE%A4%E4%B8%94%E6%8C%81%E4%B9%85%E7%9A%84%E6%95%B0%E6%8D%AE%E3%80%82) * \[`"majority"`]\([https://docs.mongodb.com/manual/reference/write-concern/#writeconcern."majority")关注写操作；也就是说，写操作要求确认该操作已应用于大多数复制集的有投票权的成员。](https://docs.mongodb.com/manual/reference/write-concern/#writeconcern.%22majority%22%29%E5%85%B3%E6%B3%A8%E5%86%99%E6%93%8D%E4%BD%9C%EF%BC%9B%E4%B9%9F%E5%B0%B1%E6%98%AF%E8%AF%B4%EF%BC%8C%E5%86%99%E6%93%8D%E4%BD%9C%E8%A6%81%E6%B1%82%E7%A1%AE%E8%AE%A4%E8%AF%A5%E6%93%8D%E4%BD%9C%E5%B7%B2%E5%BA%94%E7%94%A8%E4%BA%8E%E5%A4%A7%E5%A4%9A%E6%95%B0%E5%A4%8D%E5%88%B6%E9%9B%86%E7%9A%84%E6%9C%89%E6%8A%95%E7%A5%A8%E6%9D%83%E7%9A%84%E6%88%90%E5%91%98%E3%80%82) 如果因果一致性并不意味着持久性(即，写操作可能会回滚)，则具有写顾虑的写操作也可以提供因果一致性。[`{ w: 1 }`](https://docs.mongodb.com/manual/reference/write-concern/#writeconcern.) > **\[success] 注意** > > 在某些情况下(但不一定在所有情况下)，读和写关注点的其他组合也可以满足所有四个因果一致性保证。 读关注点\[`"majority"`]\([https://docs.mongodb.com/manual/reference/read-concern-majority/#readconcern."majority")和写关注点](https://docs.mongodb.com/manual/reference/read-concern-majority/#readconcern.%22majority%22%29%E5%92%8C%E5%86%99%E5%85%B3%E6%B3%A8%E7%82%B9) \[`"majority"`]\([https://docs.mongodb.com/manual/reference/write-concern/#writeconcern."majority")确保即使在复制集中的两个成员\*短暂地\*认为它们是主要的\[情况下(例如，使用网络分区)\](https://docs.mongodb.com/manual/core/read-preference-use-cases/#edge-cases)，这四个因果一致性保证也成立](https://docs.mongodb.com/manual/reference/write-concern/#writeconcern.%22majority%22%29%E7%A1%AE%E4%BF%9D%E5%8D%B3%E4%BD%BF%E5%9C%A8%E5%A4%8D%E5%88%B6%E9%9B%86%E4%B8%AD%E7%9A%84%E4%B8%A4%E4%B8%AA%E6%88%90%E5%91%98*%E7%9F%AD%E6%9A%82%E5%9C%B0*%E8%AE%A4%E4%B8%BA%E5%AE%83%E4%BB%AC%E6%98%AF%E4%B8%BB%E8%A6%81%E7%9A%84\[%E6%83%85%E5%86%B5%E4%B8%8B%28%E4%BE%8B%E5%A6%82%EF%BC%8C%E4%BD%BF%E7%94%A8%E7%BD%91%E7%BB%9C%E5%88%86%E5%8C%BA%29]%28https://docs.mongodb.com/manual/core/read-preference-use-cases/#edge-cases%29%EF%BC%8C%E8%BF%99%E5%9B%9B%E4%B8%AA%E5%9B%A0%E6%9E%9C%E4%B8%80%E8%87%B4%E6%80%A7%E4%BF%9D%E8%AF%81%E4%B9%9F%E6%88%90%E7%AB%8B) 。尽管两个主数据库都可以完成写操作，但是只有一个主数据库能够完成写操作。[`{ w: 1 }`](https://docs.mongodb.com/manual/reference/write-concern/#writeconcern.)\[`"majority"`]\([https://docs.mongodb.com/manual/reference/write-concern/#writeconcern."majority](https://docs.mongodb.com/manual/reference/write-concern/#writeconcern.%22majority)"). 例如，考虑网络分区划分五个成员复制集的情况： ![网络分区：一侧选择了新的主节点，而旧的主节点尚未卸任。](https://docs.mongodb.com/manual/_images/network-partition-two-primaries.svg) ## 场景 为了说明读写关注点要求，在以下情况下，客户端向客户端发出了一系列操作，并对复制集进行了读写关注点的各种组合： * [阅读关注“多数”并写关注“多数”](https://docs.mongodb.com/manual/core/causal-consistency-read-write-concerns/#causal-rc-majority-wc-majority) * [阅读关注“多数”并发表关注{w：1}](https://docs.mongodb.com/manual/core/causal-consistency-read-write-concerns/#causal-rc-majority-wc-1) * [阅读关注“本地”，写关注“多数”](https://docs.mongodb.com/manual/core/causal-consistency-read-write-concerns/#causal-rc-local-wc-majority) * [阅读关注“本地”并写关注{w：1}](https://docs.mongodb.com/manual/core/causal-consistency-read-write-concerns/#causal-rc-local-wc-1) ### 阅读关注`"majority"`和写关注`"majority"` 在因果一致的会话中使用读取关注\[`"majority"`]\([https://docs.mongodb.com/manual/reference/read-concern-majority/#readconcern."majority")和写入关注](https://docs.mongodb.com/manual/reference/read-concern-majority/#readconcern.%22majority%22%29%E5%92%8C%E5%86%99%E5%85%A5%E5%85%B3%E6%B3%A8) \[`"majority"`]\([https://docs.mongodb.com/manual/reference/write-concern/#writeconcern."majority")可提供以下因果一致性保证：](https://docs.mongodb.com/manual/reference/write-concern/#writeconcern.%22majority%22%29%E5%8F%AF%E6%8F%90%E4%BE%9B%E4%BB%A5%E4%B8%8B%E5%9B%A0%E6%9E%9C%E4%B8%80%E8%87%B4%E6%80%A7%E4%BF%9D%E8%AF%81%EF%BC%9A) ✅自己读✅单调读read单调写✅写跟随读 **方案1（读关注"majority"和写关注"majority"）** 在具有两个主操作的过渡期内，由于只有**P**new操作才能满足写关注的写操作，因此客户机会话可以成功发出以下操作序列：\[`{ w: "majority" }`]\([https://docs.mongodb.com/manual/reference/write-concern/#writeconcern."majority](https://docs.mongodb.com/manual/reference/write-concern/#writeconcern.%22majority)") | 序列 | 例 | | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------ | | 1.write1\[`"majority"`]\([https://docs.mongodb.com/manual/reference/write-concern/#writeconcern."majority](https://docs.mongodb.com/manual/reference/write-concern/#writeconcern.%22majority)") 到 新的关注**P**new 2.read1>与读关心\[`"majority"`]\([https://docs.mongodb.com/manual/reference/read-concern-majority/#readconcern."majority")到\*\*S\*\*](https://docs.mongodb.com/manual/reference/read-concern-majority/#readconcern.%22majority%22%29%E5%88%B0**S**)2 3.write2\[`"majority"`]\([https://docs.mongodb.com/manual/reference/write-concern/#writeconcern."majority")到新的关注\*\*P\*\*](https://docs.mongodb.com/manual/reference/write-concern/#writeconcern.%22majority%22%29%E5%88%B0%E6%96%B0%E7%9A%84%E5%85%B3%E6%B3%A8**P**)new 4.read2与读取关注\[`"majority"`]\([https://docs.mongodb.com/manual/reference/read-concern-majority/#readconcern."majority")到\*\*S\*\*](https://docs.mongodb.com/manual/reference/read-concern-majority/#readconcern.%22majority%22%29%E5%88%B0**S**)3 | 对于项目`A`，更新`qty`为`50`。 阅读项目`A`。对于`qty`小于或等于的项目`50`， 更新`restock`到`true`。阅读项目`A`。 | ![使用读关注多数和写关注多数的具有两个原语的数据状态](https://docs.mongodb.com/manual/_images/causal-rc-majority-wc-majority.svg) | | | | ---------- | ------------------------------------------------------------------------------- | | ✅ **自己写** | read1从**S**2读取数据，该数据反映了write1之后的状态。read2从**S**1读取数据，该数据反映了write1之后是write2之后的状态。 | | ✅ **单调读** | read2从**S**3中读取反映read1之后状态的数据。 | | ✅ **单调写** | write2更新**P**new数据，以反映write1之后的状态。 | | ✅ **写跟随读** | write2更新**P**new数据，以反映read1之后的数据状态（即，较早的状态反映read1读取的数据）。 | **方案2（读取关注“多数”和写入关注“多数”）** 考虑一个替代序列，其中具有读关注的read1\[`"majority"`]\([https://docs.mongodb.com/manual/reference/read-concern-majority/#readconcern."majority")路由到\`S\`1：](https://docs.mongodb.com/manual/reference/read-concern-majority/#readconcern.%22majority%22%29%E8%B7%AF%E7%94%B1%E5%88%B0%60S%601%EF%BC%9A) | 序列 | 例 | | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------ | | 1.write1\[`"majority"`]\([https://docs.mongodb.com/manual/reference/write-concern/#writeconcern."majority](https://docs.mongodb.com/manual/reference/write-concern/#writeconcern.%22majority)") 到 新的关注**P**new 2.read1>与读关心\[`"majority"`]\([https://docs.mongodb.com/manual/reference/read-concern-majority/#readconcern."majority")到\*\*S\*\*](https://docs.mongodb.com/manual/reference/read-concern-majority/#readconcern.%22majority%22%29%E5%88%B0**S**)2 3.write2\[`"majority"`]\([https://docs.mongodb.com/manual/reference/write-concern/#writeconcern."majority")到新的关注\*\*P\*\*](https://docs.mongodb.com/manual/reference/write-concern/#writeconcern.%22majority%22%29%E5%88%B0%E6%96%B0%E7%9A%84%E5%85%B3%E6%B3%A8**P**)new 4.read2与读取关注\[`"majority"`]\([https://docs.mongodb.com/manual/reference/read-concern-majority/#readconcern."majority")到\*\*S\*\*](https://docs.mongodb.com/manual/reference/read-concern-majority/#readconcern.%22majority%22%29%E5%88%B0**S**)3 | 对于项目`A`，更新`qty`为`50`。 阅读项目`A`。对于`qty`小于或等于的项目`50`， 更新`restock`到`true`。阅读项目`A`。 | 在这个序列中，read1在**P**old上的多数提交点提前之前不能返回。在**P**old和**S**1能够与复制集的其余部分通信之前，这是不可能发生的;此时，**P**old已经退出(如果还没有)，两个成员从副本集中的其他成员同步(包括write1)。 | | | | ---------- | ---------------------------------------------------------------------------------------------------- | | ✅ **自己写** | read1反映了write11之后的数据状态，尽管在网络分区已修复并且该成员已与副本集的其他成员进行同步之后。read2从**S**3读取数据，该数据反映了write11之后是write2之后的状态。 | | ✅ **单调读** | read2从**S**3读取数据，该数据反映read1之后的状态（即，较早的状态反映在read1读取的数据中）。 | | ✅ **单调写** | write2更新**P**new数据，以反映write1之后的状态。 | | ✅ **写跟随读** | write2更新**P**new数据，以反映read1之后的数据状态（即，较早的状态反映read1读取的数据）。 | #### 读关注`"majority"`和写关注`{w: 1}` \_如果因果一致性暗示持久性，则\_在因果一致性会话中使用读关注\[`"majority"`]\([https://docs.mongodb.com/manual/reference/read-concern-majority/#readconcern."majority")和写关注](https://docs.mongodb.com/manual/reference/read-concern-majority/#readconcern.%22majority%22%29%E5%92%8C%E5%86%99%E5%85%B3%E6%B3%A8) 可提供以下因果一致性保证：[`{ w: 1 }`](https://docs.mongodb.com/manual/reference/write-concern/#writeconcern.) ❌自己读 ✅单调读read单调写. ✅写跟随读 *如果因果一致性并不意味着持久性*： ✅自己读. ✅单调读read单调写. ✅写跟随读 **方案3（“关注多数”和“关注关注” ）{w: 1}** 在过渡期内有两个初选，因为无论**P**old与**P**new能满足与写入 的写入关注，一个客户端会话可以成功地发出以下的操作序列，但不是因果关系一致\*\*，如果一致因果意味着耐久性\*\*：[`{ w: 1 }`](https://docs.mongodb.com/manual/reference/write-concern/#writeconcern.) | 序列 | 例 | | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | ------------------------------------------------------------------------------ | | 1.write1与写入关注 到 [`{ w: 1 }`](https://docs.mongodb.com/manual/reference/write-concern/#writeconcern.)**P**old 2.read11与读关心\[`"majority"`]\([https://docs.mongodb.com/manual/reference/read-concern-majority/#readconcern."majority")到\*\*S\*\*](https://docs.mongodb.com/manual/reference/read-concern-majority/#readconcern.%22majority%22%29%E5%88%B0**S**)2 3.write2到新的关注[`{ w: 1 }`](https://docs.mongodb.com/manual/reference/write-concern/#writeconcern.)**P**new 4.read2与读取关注\[`"majority"`]\([https://docs.mongodb.com/manual/reference/read-concern-majority/#readconcern."majority")到\*\*S\*\*](https://docs.mongodb.com/manual/reference/read-concern-majority/#readconcern.%22majority%22%29%E5%88%B0**S**)3 | 对于项目`A`，更新`qty`为`50`。 阅读项目`A`。对于`qty`小于或等于的项目`50`， 更新`restock`到`true`。阅读项目`A`。 | ![使用读关注多数和写关注1的具有两个原语的数据状态](https://docs.mongodb.com/manual/_images/causal-rc-majority-wc-1.svg) 按照这个顺序 * 直到**P**new上的大多数提交点超过了write1的时间，read1才会返回。 * 直到**P**new上的大多数提交点超过了write2的时间，read2才能返回。 * 当网络分区恢复时，write1将回滚。 ➤ *如果因果一致性意味着持久性* | | | | ---------- | -------------------------------------------------------- | | ❌ **自己写** | read1从**S**2读取的数据不反映write1之后的状态。 | | ✅ **单调读** | read2从**S**3读取数据，该数据反映read1之后的状态（即，较早的状态反映在read1读取的数据中）。 | | ❌ **单调写** | write2更新了**P**new数据，而不会反映write1之后的状态。 | | ✅ **写跟随读** | write2更新**P**new数据，以反映read1之后的状态（即，较早的状态反映read1读取的数据）。 | ➤ *如果因果一致性并不意味着持久性* | | | | ---------- | -------------------------------------------------------- | | ✅ **自己写** | read1从**S**2读取数据，返回反映与write1等效的状态的数据，然后回退write1。 | | ✅ **单调读** | read2从**S**3读取数据，该数据反映read1之后的状态（即，较早的状态反映在read1读取的数据中）。 | | ✅ **单调写** | write2更新了**P**new的数据，这等效于write1之后回退写1的数据。 | | ✅ **写跟随读** | write2更新**P**new数据，以反映read1之后的状态（即，较早的状态反映read1读取的数据）。 | **方案4（“关注多数”和“关注关注” ）{w: 1}** 考虑一个替代序列，其中具有读关注的读1\[`"majority"`]\([https://docs.mongodb.com/manual/reference/read-concern-majority/#readconcern."majority")路由到\`S\`1：](https://docs.mongodb.com/manual/reference/read-concern-majority/#readconcern.%22majority%22%29%E8%B7%AF%E7%94%B1%E5%88%B0%60S%601%EF%BC%9A) | 序列 | 例 | | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | ------------------------------------------------------------------------------ | | 1.write1与写入关注 到 [`{ w: 1 }`](https://docs.mongodb.com/manual/reference/write-concern/#writeconcern.)**P**old 2.read11与读关心\[`"majority"`]\([https://docs.mongodb.com/manual/reference/read-concern-majority/#readconcern."majority")到\*\*S\*\*](https://docs.mongodb.com/manual/reference/read-concern-majority/#readconcern.%22majority%22%29%E5%88%B0**S**)1 3.write2到新的关注[`{ w: 1 }`](https://docs.mongodb.com/manual/reference/write-concern/#writeconcern.)**P**new 4.read2与读取关注\[`"majority"`]\([https://docs.mongodb.com/manual/reference/read-concern-majority/#readconcern."majority")到\*\*S\*\*](https://docs.mongodb.com/manual/reference/read-concern-majority/#readconcern.%22majority%22%29%E5%88%B0**S**)3 | 对于项目`A`，更新`qty`为`50`。 阅读项目`A`。对于`qty`小于或等于的项目`50`， 更新`restock`到`true`。阅读项目`A`。 | 按此顺序： * 直到**S**1上的大多数提交点提高，read1才能返回。在**P**old和**S**1能够与复制集的其他成员进行通信之前，这是不可能发生的。此时，**P**old已经退出(如果还没有)，write1将从**P**old和**S**1回滚，两个成员将与复制集的其他成员同步。 ➤ *如果因果一致性意味着持久性* | | | | ---------- | ------------------------------------------------------------- | | ❌ **自己写** | read1读取的数据不反映已回退的write1的结果。 | | ✅ **单调读** | read2从**S**3读取数据，该数据反映read1之后的状态（即，其较早的状态反映read1读取的数据）。 | | ❌ **单调写** | write2更新关于**P**new的数据，该数据不反映write1之后的状态，该write1在write2之前但已回滚。 | | ✅ **写跟随读** | write2更新**P**new数据，以反映read1之后的状态（即，其较早的状态反映read1读取的数据）。 | ➤ *如果因果一致性并不意味着持久性* | | | | ---------- | ------------------------------------------------------- | | ✅ **自己写** | read1返回反映write1最终结果的数据，因为write1最终会回滚。 | | ✅ **单调读** | read2从**S**3读取数据，该数据反映read1之后的状态（即，其较早的状态反映read1读取的数据）。 | | ✅ **单调写** | write2更新**P**new上的数据，这等效于write1之后回退write1的数据。 | | ✅ **写跟随读** | write2更新**P**new数据，以反映read1之后的状态（即，其较早的状态反映read1读取的数据）。 | #### 读关注`"local"`和写关注`{w: 1}` 在因果一致的会话中使用读关注\[`"local"`]\([https://docs.mongodb.com/manual/reference/read-concern-local/#readconcern."local")和写关注](https://docs.mongodb.com/manual/reference/read-concern-local/#readconcern.%22local%22%29%E5%92%8C%E5%86%99%E5%85%B3%E6%B3%A8) 不能保证因果一致性。[`{ w: 1 }`](https://docs.mongodb.com/manual/reference/write-concern/#writeconcern.) ❌自己读. ❌单调读read单调写. ❌写跟随读 在某些情况下（但不一定在所有情况下），此组合可以满足所有四个因果一致性保证。 **方案5（“本地关注”和“关注关注” ）{w: 1}** 在这个短暂的时期，因为无论**P**old与 **P**new能满足与写入的写入关注，一个客户端会话可以发出以下的操作序列成功，但不是因果关系是一致的：[`{ w: 1 }`](https://docs.mongodb.com/manual/reference/write-concern/#writeconcern.) | 序列 | 例 | | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------ | | 1.write1与写入关注到 [`{ w: 1 }`](https://docs.mongodb.com/manual/reference/write-concern/#writeconcern.)**P**old 2.read11与读关心\[`"majority"`]\([https://docs.mongodb.com/manual/reference/read-concern-majority/#readconcern."majority")到\*\*S\*\*](https://docs.mongodb.com/manual/reference/read-concern-majority/#readconcern.%22majority%22%29%E5%88%B0**S**)1 3.write2到新的关注[`{ w: 1 }`](https://docs.mongodb.com/manual/reference/write-concern/#writeconcern.)**P**new 4.read2与读取关注\[`"majority"`]\([https://docs.mongodb.com/manual/reference/read-concern-majority/#readconcern."majority")到\*\*S\*\*](https://docs.mongodb.com/manual/reference/read-concern-majority/#readconcern.%22majority%22%29%E5%88%B0**S**)3 | 对于项目`A`，更新`qty`为`50`。 阅读项目`A`。对于`qty`小于或等于的项目`50`， 更新`restock`到`true`。阅读项目`A`。 | ![使用读关注本地和写关注1的具有两个主数据的数据状态](https://docs.mongodb.com/manual/_images/causal-rc-local-wc-1.svg) | | | | ----- | ----------------------------------------------------------- | | ❌自己写 | read2从**S**3读取数据，该数据仅反映write2之后的状态，而不反映write1 之后是write2的状态。 | | ❌单调读 | read2从**S**3读取数据，该数据不反映read1之后的状态（即，较早的状态不反映read1读取的数据）。 | | ❌单调写 | write2更新了**P**new数据，而不会反映write1之后的状态。 | | ❌写跟随读 | write2更新**P**new的数据，该数据不反映read1之后的状态（即，较早的状态不反映read1读取的数据）。 | #### 读关注`"local"`和写关注`"majority"` 在因果一致的会话中使用读取关注\[`"local"`]\([https://docs.mongodb.com/manual/reference/read-concern-local/#readconcern."local")和写入关注](https://docs.mongodb.com/manual/reference/read-concern-local/#readconcern.%22local%22%29%E5%92%8C%E5%86%99%E5%85%A5%E5%85%B3%E6%B3%A8) \[`"majority"`]\([https://docs.mongodb.com/manual/reference/write-concern/#writeconcern."majority")可提供以下因果一致性保证：](https://docs.mongodb.com/manual/reference/write-concern/#writeconcern.%22majority%22%29%E5%8F%AF%E6%8F%90%E4%BE%9B%E4%BB%A5%E4%B8%8B%E5%9B%A0%E6%9E%9C%E4%B8%80%E8%87%B4%E6%80%A7%E4%BF%9D%E8%AF%81%EF%BC%9A) ❌自己读 ❌单调读read单调写 ❌写跟随读 在某些情况下（但不一定在所有情况下），此组合可以满足所有四个因果一致性保证。 **方案6（“关注本地”和“关注多数”）** 在此过渡期间，因为只有`P`new才能完成与 写入有关的写入，所以客户机会话可以成功发出以下操作序列，但因果关系不一致：\[`{ w: "majority" }`]\([https://docs.mongodb.com/manual/reference/write-concern/#writeconcern."majority](https://docs.mongodb.com/manual/reference/write-concern/#writeconcern.%22majority)") | 序列 | 例 | | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------ | | 1.write1\[`"majority"`]\([https://docs.mongodb.com/manual/reference/write-concern/#writeconcern."majority](https://docs.mongodb.com/manual/reference/write-concern/#writeconcern.%22majority)") 到 新的关注**P**new 2.read1>与读关心\[`"majority"`]\([https://docs.mongodb.com/manual/reference/read-concern-majority/#readconcern."majority")到\*\*S\*\*](https://docs.mongodb.com/manual/reference/read-concern-majority/#readconcern.%22majority%22%29%E5%88%B0**S**)1 3.write2\[`"majority"`]\([https://docs.mongodb.com/manual/reference/write-concern/#writeconcern."majority")到新的关注\*\*P\*\*](https://docs.mongodb.com/manual/reference/write-concern/#writeconcern.%22majority%22%29%E5%88%B0%E6%96%B0%E7%9A%84%E5%85%B3%E6%B3%A8**P**)new 4.read2与读取关注\[`"majority"`]\([https://docs.mongodb.com/manual/reference/read-concern-majority/#readconcern."majority")到\*\*S\*\*](https://docs.mongodb.com/manual/reference/read-concern-majority/#readconcern.%22majority%22%29%E5%88%B0**S**)3 | 对于项目`A`，更新`qty`为`50`。 阅读项目`A`。对于`qty`小于或等于的项目`50`， 更新`restock`到`true`。阅读项目`A`。 | ![使用读关注本地和写关注多数的两个主数据的状态](https://docs.mongodb.com/manual/_images/causal-rc-local-wc-majority.svg) | | | | --------- | ----------------------------------------------------------- | | ❌阅读自己的文章。 | read1从**S**1读取不反映write11后状态的数据。 | | ❌单调读。 | read2从**S**3读取数据，该数据不反映read1之后的状态（即，较早的状态不反映read1读取的数据）。 | | ✅单调写 | write2更新**P**new数据，以反映write1之后的状态。 | | ❌写跟随阅读。 | write2更新**P**new的数据，该数据不反映read1之后的状态（即，较早的状态不反映read1读取的数据）。 | 译者：杨帅 校对：杨帅