blocks|key|4882383|text|当你关闭被阻止的插入(例如，通过control%2B+C或任何其他机制)，但不知何故进程没有停止，并且在你运行unblock+fsync之后，命令仍然在后台进行并被插入，或者当插入命令被阻止之后，你运行unblock+fsync，使块插入自动解锁，这可能是可能的。我在v4.4.10(比你的版本更高的版本)上测试了这一点，根据文档，它工作得很好。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4882384|首先插入一条记录|4882385|​|4882386|📷|atomic|offset|length|4882387|4882388|然后使用fsync|4882389|4882390|4882391|4882392|然后尝试再插入一条记录，该记录将被阻塞，并随后使用Ctrl+%2BC组合键终止|4882393|4882394|4882395|4882396|然后取消阻止fsync|4882397|4882398|4882399|4882400|确认第二次插入没有成功(这就是预期的行为)|4882401|4882402|4882403|4882404|您还可以检查插入之前和之后的db.serverStatus()，以查看服务器接受的"insert“命令的差异。这可以为您提供有关命令是否以某种方式到达的提示。信息如下所示|4882405|4882406|4882407|4882408|entityMap|0|IMAGE|mutability|IMMUTABLE|imageUrl|https://ask.qcloudimg.com/http-save/yehe-900000/1933e6b42abae54101930cea5238bb78.png|imageAlt|1|https://ask.qcloudimg.com/http-save/yehe-900000/6d3abeae9a33d25aad2d715552102e3e.png|2|https://ask.qcloudimg.com/http-save/yehe-900000/6cc397656e626ac7a6607ba5851de95c.png|3|https://ask.qcloudimg.com/http-save/yehe-900000/db898bb6006c41ed204fdc9c4b5014c4.png|4|https://ask.qcloudimg.com/http-save/yehe-900000/2d2fcd06e4a44e24c7de2de43064545f.png|5|https://ask.qcloudimg.com/http-save/yehe-900000/a61c86fabf2203fdbbcf37edbaccfe8a.png^0|0|0|0|0|1|0|0|0|0|0|0|1|1|0|0|0|0|0|1|2|0|0|0|0|0|1|3|0|0|0|0|0|1|4|0|0|0|0|0|1|5|0|0^^$0|@$1|2|3|4|5|6|7|1T|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|1U|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|1V|8|@]|9|@]|A|$]]|$1|F|3|G|5|H|7|1W|8|@]|9|@$I|1X|J|1Y|1|1Z]]|A|$]]|$1|K|3|E|5|6|7|20|8|@]|9|@]|A|$]]|$1|L|3|M|5|6|7|21|8|@]|9|@]|A|$]]|$1|N|3|E|5|6|7|22|8|@]|9|@]|A|$]]|$1|O|3|G|5|H|7|23|8|@]|9|@$I|24|J|25|1|26]]|A|$]]|$1|P|3|E|5|6|7|27|8|@]|9|@]|A|$]]|$1|Q|3|R|5|6|7|28|8|@]|9|@]|A|$]]|$1|S|3|E|5|6|7|29|8|@]|9|@]|A|$]]|$1|T|3|G|5|H|7|2A|8|@]|9|@$I|2B|J|2C|1|2D]]|A|$]]|$1|U|3|E|5|6|7|2E|8|@]|9|@]|A|$]]|$1|V|3|W|5|6|7|2F|8|@]|9|@]|A|$]]|$1|X|3|E|5|6|7|2G|8|@]|9|@]|A|$]]|$1|Y|3|G|5|H|7|2H|8|@]|9|@$I|2I|J|2J|1|2K]]|A|$]]|$1|Z|3|E|5|6|7|2L|8|@]|9|@]|A|$]]|$1|10|3|11|5|6|7|2M|8|@]|9|@]|A|$]]|$1|12|3|E|5|6|7|2N|8|@]|9|@]|A|$]]|$1|13|3|G|5|H|7|2O|8|@]|9|@$I|2P|J|2Q|1|2R]]|A|$]]|$1|14|3|E|5|6|7|2S|8|@]|9|@]|A|$]]|$1|15|3|16|5|6|7|2T|8|@]|9|@]|A|$]]|$1|17|3|E|5|6|7|2U|8|@]|9|@]|A|$]]|$1|18|3|G|5|H|7|2V|8|@]|9|@$I|2W|J|2X|1|2Y]]|A|$]]|$1|19|3|E|5|6|7|2Z|8|@]|9|@]|A|$]]|$1|1A|3|-4|5|6|7|30|8|@]|9|@]|A|$]]]|1B|$1C|$5|1D|1E|1F|A|$1G|1H|1I|-4]]|1J|$5|1D|1E|1F|A|$1G|1K|1I|-4]]|1L|$5|1D|1E|1F|A|$1G|1M|1I|-4]]|1N|$5|1D|1E|1F|A|$1G|1O|1I|-4]]|1P|$5|1D|1E|1F|A|$1G|1Q|1I|-4]]|1R|$5|1D|1E|1F|A|$1G|1S|1I|-4]]]]

This can be possible in a scenario when you shut down the blocked insert ( e.g. by control+ C or any other mechanism) but somehow the process did not stopped and after you ran unblock fsync the command still went through in the background and was inserted OR when the insert command was blocked and after that you ran unblock fsync which made the block insert to unblock automatically. I tested this on v 4.4.10 ( on a higher version than yours) and it works perfectly fine as per documentation.
First insert one record
<a href="https://i.stack.imgur.com/nt6bn.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/nt6bn.png" alt="enter image description here" /></a>
Then use fsync
<a href="https://i.stack.imgur.com/3Br8y.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/3Br8y.png" alt="enter image description here" /></a>
Then try to insert one more record which will get blocked and subsequently killed using Ctrl + C
<a href="https://i.stack.imgur.com/VX8BT.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/VX8BT.png" alt="enter image description here" /></a>
Then unblock fsync
<a href="https://i.stack.imgur.com/o1LoW.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/o1LoW.png" alt="enter image description here" /></a>
Verify that the second insert was not successful ( this is what the expected behavior is)
<a href="https://i.stack.imgur.com/kSV0X.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/kSV0X.png" alt="enter image description here" /></a>
You can also check the db.serverStatus() before and after to see the difference in &quot;insert&quot; commands accepted by the server. This can provide you hint as to whether the command somehow reached. The info looks like this
<a href="https://i.stack.imgur.com/ykCDl.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/ykCDl.png" alt="enter image description here" /></a>

Based on documentation, fsync with lock=true should block the writes. But what's being noticed is its still writing though its blocking the writes. Is this the expected behavior?
I installed MongoDB locally on my machine and running it as a single node replica set. MongoDB version being used is 4.2.11
<a href="https://i.stack.imgur.com/Z9RZv.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/Z9RZv.png" alt="enter image description here" /></a>
I perform fsync as shown here under.
<a href="https://i.stack.imgur.com/ohIjW.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/ohIjW.png" alt="enter image description here" /></a>
And then attempt a write, it gets blocked. I would cancel it.
<a href="https://i.stack.imgur.com/EsBqP.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/EsBqP.png" alt="enter image description here" /></a>
And then perform fsync unlock.
<a href="https://i.stack.imgur.com/CCB1J.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/CCB1J.png" alt="enter image description here" /></a>
It is expected that the write wouldn't have worked, but it is persisted any ways. Is there a bug in fsync?
<a href="https://i.stack.imgur.com/vnoZ9.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/vnoZ9.png" alt="enter image description here" /></a>

fsync MongoDB behavior

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

教程

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云智能顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云AI代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

功能1上新10个字符

功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符。

功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符。

功能5描述100个字符功能5描述100个字符功能5描述100个字符功能5描述100个字符功能5描述100个字符功能5描述100个字符

功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符

功能4上新

文章&问答评论现已支持表情

全新交互，全新视觉，新增快捷键、悬浮工具栏、高亮块等功能并同时优化现有功能，全面提升创作效率和体验

社区富文本编辑器全新改版！诚邀体验～ 

精选全网热门MCP server，让你的AI更好用 🚀

💥开发者 MCP广场重磅上线！

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

聚焦“写作效率、视觉美观与运行性能”三方面进行全面升级，为您提供更高效、稳定的创作环境

社区富文本&Markdown编辑器全新改版上线，欢迎大家体验!

诚挚邀请您参与本次调研，分享您的真实使用感受与建议。您的反馈至关重要，感谢您的支持与参与！

社区新版编辑器体验调研

根据文档，使用lock=true的fsync应该会阻止写入。但值得注意的是，尽管它阻止了写操作，但它仍然在写。这是预期的行为吗？我在本地机器上安装了MongoDB，并将其作为单节点副本集运行。正在使用的MongoDB版本为4.2.11​我执行fsync，如下所示。​​然后尝试写入，它就会被阻塞。我会取消的。​然后执行fsync解锁。​​预计写操作不会起作用，但无论如何它都是持久的。fsync中有b

问fsync MongoDB行为
EN

回答 1

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问fsync MongoDB行为EN