<!-- 
RSS generated by JIRA (9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66) at Thu Feb 08 05:02:02 UTC 2024

It is possible to restrict the fields that are returned in this document by specifying the 'field' parameter in your request.
For example, to request only the issue key and summary append 'field=key&field=summary' to the URL of your request.
-->
<rss version="0.92" >
<channel>
    <title>MongoDB Jira</title>
    <link>https://jira.mongodb.org</link>
    <description>This file is an XML representation of an issue</description>
    <language>en-us</language>    <build-info>
        <version>9.7.1</version>
        <build-number>970001</build-number>
        <build-date>13-04-2023</build-date>
    </build-info>


<item>
            <title>[SERVER-43021] MongoS server crashes when attempt to update single record &gt; 16MB (16793648)</title>
                <link>https://jira.mongodb.org/browse/SERVER-43021</link>
                <project id="10000" key="SERVER">Core Server</project>
                    <description>&lt;p&gt;I&apos;m not certain if this would happen every time, but it did happen to us in production.&lt;/p&gt;

&lt;p&gt;We had an object that was very close to 16MB (15.99MB according to bsonsize()), and our application went to update the record with a little more data.&lt;/p&gt;

&lt;p&gt;The mongos that was being used then crashed with the following message:&lt;/p&gt;
&lt;p/&gt;
&lt;div id=&quot;syntaxplugin&quot; class=&quot;syntaxplugin&quot; style=&quot;border: 1px dashed #bbb; border-radius: 5px !important; overflow: auto; max-height: 30em;&quot;&gt;
&lt;table cellspacing=&quot;0&quot; cellpadding=&quot;0&quot; border=&quot;0&quot; width=&quot;100%&quot; style=&quot;font-size: 1em; line-height: 1.4em !important; font-weight: normal; font-style: normal; color: black;&quot;&gt;
		&lt;tbody &gt;
				&lt;tr id=&quot;syntaxplugin_code_and_gutter&quot;&gt;
						&lt;td  style=&quot; line-height: 1.4em !important; padding: 0em; vertical-align: top;&quot;&gt;
					&lt;pre style=&quot;font-size: 1em; margin: 0 10px;  margin-top: 10px;   margin-bottom: 10px;  width: auto; padding: 0;&quot;&gt;&lt;span style=&quot;color: #009900; font-family: &apos;Consolas&apos;, &apos;Bitstream Vera Sans Mono&apos;, &apos;Courier New&apos;, Courier, monospace !important;&quot;&gt;2019&lt;/span&gt;&lt;span style=&quot;color: black; font-family: &apos;Consolas&apos;, &apos;Bitstream Vera Sans Mono&apos;, &apos;Courier New&apos;, Courier, monospace !important;&quot;&gt;-&lt;/span&gt;&lt;span style=&quot;color: #009900; font-family: &apos;Consolas&apos;, &apos;Bitstream Vera Sans Mono&apos;, &apos;Courier New&apos;, Courier, monospace !important;&quot;&gt;08&lt;/span&gt;&lt;span style=&quot;color: black; font-family: &apos;Consolas&apos;, &apos;Bitstream Vera Sans Mono&apos;, &apos;Courier New&apos;, Courier, monospace !important;&quot;&gt;-11T08:&lt;/span&gt;&lt;span style=&quot;color: #009900; font-family: &apos;Consolas&apos;, &apos;Bitstream Vera Sans Mono&apos;, &apos;Courier New&apos;, Courier, monospace !important;&quot;&gt;10&lt;/span&gt;&lt;span style=&quot;color: black; font-family: &apos;Consolas&apos;, &apos;Bitstream Vera Sans Mono&apos;, &apos;Courier New&apos;, Courier, monospace !important;&quot;&gt;:&lt;/span&gt;&lt;span style=&quot;color: #009900; font-family: &apos;Consolas&apos;, &apos;Bitstream Vera Sans Mono&apos;, &apos;Courier New&apos;, Courier, monospace !important;&quot;&gt;25.814&lt;/span&gt;&lt;span style=&quot;color: black; font-family: &apos;Consolas&apos;, &apos;Bitstream Vera Sans Mono&apos;, &apos;Courier New&apos;, Courier, monospace !important;&quot;&gt;+&lt;/span&gt;&lt;span style=&quot;color: #009900; font-family: &apos;Consolas&apos;, &apos;Bitstream Vera Sans Mono&apos;, &apos;Courier New&apos;, Courier, monospace !important;&quot;&gt;0000&lt;/span&gt;&lt;span style=&quot;color: black; font-family: &apos;Consolas&apos;, &apos;Bitstream Vera Sans Mono&apos;, &apos;Courier New&apos;, Courier, monospace !important;&quot;&gt; F ASIO     [NetworkInterfaceASIO-TaskExecutorPool-&lt;/span&gt;&lt;span style=&quot;color: #009900; font-family: &apos;Consolas&apos;, &apos;Bitstream Vera Sans Mono&apos;, &apos;Courier New&apos;, Courier, monospace !important;&quot;&gt;2&lt;/span&gt;&lt;span style=&quot;color: black; font-family: &apos;Consolas&apos;, &apos;Bitstream Vera Sans Mono&apos;, &apos;Courier New&apos;, Courier, monospace !important;&quot;&gt;-&lt;/span&gt;&lt;span style=&quot;color: #009900; font-family: &apos;Consolas&apos;, &apos;Bitstream Vera Sans Mono&apos;, &apos;Courier New&apos;, Courier, monospace !important;&quot;&gt;0&lt;/span&gt;&lt;span style=&quot;color: black; font-family: &apos;Consolas&apos;, &apos;Bitstream Vera Sans Mono&apos;, &apos;Courier New&apos;, Courier, monospace !important;&quot;&gt;] Uncaught exception in NetworkInterfaceASIO IO worker thread of type: Location10334: BSONObj size: &lt;/span&gt;&lt;span style=&quot;color: #009900; font-family: &apos;Consolas&apos;, &apos;Bitstream Vera Sans Mono&apos;, &apos;Courier New&apos;, Courier, monospace !important;&quot;&gt;16794106&lt;/span&gt;&lt;span style=&quot;color: black; font-family: &apos;Consolas&apos;, &apos;Bitstream Vera Sans Mono&apos;, &apos;Courier New&apos;, Courier, monospace !important;&quot;&gt; (&lt;/span&gt;&lt;span style=&quot;color: #009900; font-family: &apos;Consolas&apos;, &apos;Bitstream Vera Sans Mono&apos;, &apos;Courier New&apos;, Courier, monospace !important;&quot;&gt;0x10041FA&lt;/span&gt;&lt;span style=&quot;color: black; font-family: &apos;Consolas&apos;, &apos;Bitstream Vera Sans Mono&apos;, &apos;Courier New&apos;, Courier, monospace !important;&quot;&gt;) is invalid. Size must be between &lt;/span&gt;&lt;span style=&quot;color: #009900; font-family: &apos;Consolas&apos;, &apos;Bitstream Vera Sans Mono&apos;, &apos;Courier New&apos;, Courier, monospace !important;&quot;&gt;0&lt;/span&gt;&lt;span style=&quot;color: black; font-family: &apos;Consolas&apos;, &apos;Bitstream Vera Sans Mono&apos;, &apos;Courier New&apos;, Courier, monospace !important;&quot;&gt; and &lt;/span&gt;&lt;span style=&quot;color: #009900; font-family: &apos;Consolas&apos;, &apos;Bitstream Vera Sans Mono&apos;, &apos;Courier New&apos;, Courier, monospace !important;&quot;&gt;16793600&lt;/span&gt;&lt;span style=&quot;color: black; font-family: &apos;Consolas&apos;, &apos;Bitstream Vera Sans Mono&apos;, &apos;Courier New&apos;, Courier, monospace !important;&quot;&gt;(16MB) First element: update: &lt;/span&gt;&lt;span style=&quot;color: blue; font-family: &apos;Consolas&apos;, &apos;Bitstream Vera Sans Mono&apos;, &apos;Courier New&apos;, Courier, monospace !important;&quot;&gt;&quot;&amp;lt;COLLECTION_NAME&amp;gt;&quot;&lt;/span&gt;&lt;span style=&quot;color: black; font-family: &apos;Consolas&apos;, &apos;Bitstream Vera Sans Mono&apos;, &apos;Courier New&apos;, Courier, monospace !important;&quot;&gt;&lt;/span&gt;&lt;/pre&gt;
			&lt;/td&gt;
		&lt;/tr&gt;
			&lt;/tbody&gt;
&lt;/table&gt;
&lt;/div&gt;
&lt;p/&gt;
&lt;p&gt;FYI In the above and the full crash logs, the collection name is redacted to &quot;&amp;lt;COLLECTION_NAME&amp;gt;&quot;.&lt;/p&gt;

&lt;p&gt;Then our application, which tries to re-write this data periodically if the initial write fails, tried to write it a little later, and went to a different mongos server, which also crashed.&#160; This caused our cluster to be effectively unavailable since both mongos nodes had crashed.&lt;/p&gt;

&lt;p&gt;I&apos;ve attached both stack traces.&lt;/p&gt;

&lt;p&gt;&#160;&lt;/p&gt;

&lt;p&gt;Obviously we don&apos;t want to be running with DB objects at or close to 16MB, so we fixed the object in question to not be as big, but even though this isn&apos;t something we have happening all the time, it does happen occasionally and we expect to need to run our production servers with the ability for 16MB objects to gracefully fail to save in the future.&lt;/p&gt;

&lt;p&gt;Our version is technically 3.6.6-evg1, which is a custom build we have branched directly off of 3.6.6, which you can find here&#160;&lt;a href=&quot;https://github.com/evergage/mongo/commits/v3.6.6-evg1&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://github.com/evergage/mongo/commits/v3.6.6-evg1&lt;/a&gt;.&#160; The only difference is the last 3 commits you see there which just quiets some extra verbose metadata logging that was eating basically infinite log entries and we had to silence in order to run this in production.&#160; Since the changes are so minor, hopefully that means that the stack trace line numbers and such are still usable for you.&#160; Since then that bug (&lt;a href=&quot;https://jira.mongodb.org/browse/SERVER-30841?filter=21888&quot; class=&quot;external-link&quot; rel=&quot;nofollow&quot;&gt;https://jira.mongodb.org/browse/SERVER-30841?filter=21888&lt;/a&gt;) has been fixed in 3.6.8, and assuming that it silenced all the things we silenced in our custom build (3 different files), then we might be able to get off of running a custom build in the future.&lt;/p&gt;

&lt;p&gt;&#160;&lt;/p&gt;</description>
                <environment></environment>
        <key id="905193">SERVER-43021</key>
            <summary>MongoS server crashes when attempt to update single record &gt; 16MB (16793648)</summary>
                <type id="1" iconUrl="https://jira.mongodb.org/secure/viewavatar?size=xsmall&amp;avatarId=14703&amp;avatarType=issuetype">Bug</type>
                                            <priority id="3" iconUrl="https://jira.mongodb.org/images/icons/priorities/major.svg">Major - P3</priority>
                        <status id="6" iconUrl="https://jira.mongodb.org/images/icons/statuses/closed.png" description="The issue is considered finished, the resolution is correct. Issues which are closed can be reopened.">Closed</status>
                    <statusCategory id="3" key="done" colorName="success"/>
                                    <resolution id="4">Incomplete</resolution>
                                        <assignee username="matthew.saltz@mongodb.com">Matthew Saltz</assignee>
                                    <reporter username="glajchs">Scott Glajch</reporter>
                        <labels>
                    </labels>
                <created>Fri, 23 Aug 2019 19:57:39 +0000</created>
                <updated>Sun, 27 Dec 2020 15:41:36 +0000</updated>
                            <resolved>Tue, 18 Feb 2020 18:21:10 +0000</resolved>
                                    <version>3.6.6</version>
                                                    <component>Stability</component>
                                        <votes>1</votes>
                                    <watches>17</watches>
                                                                                                                <comments>
                            <comment id="2882821" author="matthew.saltz" created="Tue, 18 Feb 2020 18:21:10 +0000"  >&lt;p&gt;We haven&apos;t heard back from you for some time, so I&apos;m going to mark this ticket as resolved. If this is still an issue for you, please provide additional information and we will reopen the ticket.&lt;/p&gt;</comment>
                            <comment id="2777820" author="daniel.hatcher" created="Fri, 31 Jan 2020 21:17:05 +0000"  >&lt;p&gt;Hey Scott, have you had a chance to upload the files that Matthew asked for?&lt;/p&gt;</comment>
                            <comment id="2519756" author="matthew.saltz" created="Wed, 6 Nov 2019 14:12:54 +0000"  >&lt;p&gt;The logs for the router, shards, and config server for a short period (5 minutes I&apos;m guessing would be sufficient) prior to the crash would be great. I don&apos;t think I need other diagnostic data, but for your reference there&apos;s a diagnostic data collection guide &lt;a href=&quot;https://docs.mongodb.com/manual/administration/analyzing-mongodb-performance/index.html#full-time-diagnostic-data-capture&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;here&lt;/a&gt;. &lt;/p&gt;

&lt;p&gt;For logging levels, if you&apos;re able to set the verbosity to log level 3, that would be great - hopefully that won&apos;t create an overwhelming amount of output. If it does, let me know, and I can try to make a finer grained suggestion.&lt;/p&gt;

&lt;p&gt;Thanks!&lt;/p&gt;</comment>
                            <comment id="2518798" author="glajchs" created="Tue, 5 Nov 2019 20:19:09 +0000"  >&lt;p&gt;Sure I&apos;ll work on getting that data over to you now.&lt;/p&gt;

&lt;p&gt;We actually had this crash happen again today, so I&apos;ll see if I can grab logs for both sets of events.&lt;/p&gt;

&lt;p&gt;Is there a doc somewhere about the various types of logs and diagnostic data I should be sending you?&#160; I can just grab the logs from the mongos server in question and the shard replica set members in question around the time period of the crash, but I&apos;m not sure how far to go.&#160; Do I give you the config server logs too?&lt;br/&gt;
I know there are those &quot;diagnostic.data&quot; files, but I&apos;m unsure if I&apos;m allowed to upload those as I don&apos;t think those in a format I can easily redact.&lt;/p&gt;

&lt;p&gt;Finally if there are any logging levels you&apos;d like me to set on the mongos going forward, I&apos;ll happily set those now.&#160; Since that&apos;s been 2 crashes within a week&apos;s time, I&apos;m hopeful I could get yet another crash to happen with increased logging data.&lt;/p&gt;

&lt;p&gt;&#160;&lt;/p&gt;</comment>
                            <comment id="2518182" author="daniel.hatcher" created="Tue, 5 Nov 2019 16:12:55 +0000"  >&lt;p&gt;&lt;a href=&quot;https://jira.mongodb.org/secure/ViewProfile.jspa?name=glajchs&quot; class=&quot;user-hover&quot; rel=&quot;glajchs&quot;&gt;glajchs&lt;/a&gt;, you can use our &lt;a href=&quot;https://10gen-httpsupload.s3.amazonaws.com/upload_forms/6fd7be90-38f7-4108-b7f2-25b3ca7bad19.html&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;Secure Uploader&lt;/a&gt; instead of JIRA if the file sizes for the requested logs are too big.&lt;/p&gt;</comment>
                            <comment id="2517313" author="matthew.saltz" created="Mon, 4 Nov 2019 22:47:47 +0000"  >&lt;p&gt;Hi &lt;a href=&quot;https://jira.mongodb.org/secure/ViewProfile.jspa?name=glajchs&quot; class=&quot;user-hover&quot; rel=&quot;glajchs&quot;&gt;glajchs&lt;/a&gt;, I&apos;ve reopened the issue. Would it possible for you to provide us with the log output from that mongos leading up to the crash? Having logs from the shards might help too, if it&apos;s possible to trace exactly which operation caused this. This might help with diagnosis.&lt;/p&gt;</comment>
                            <comment id="2515246" author="glajchs" created="Sat, 2 Nov 2019 16:20:34 +0000"  >&lt;p&gt;I should note that we had just finished migrating our main (important) mongo cluster from 3.4 to 3.6, and&#160;&lt;em&gt;just to be extra careful&lt;/em&gt;, for the last step we migrated only 1 of our 5 mongos nodes to 3.6.&#160; I think if we had migrated all 5 nodes, all the mongos would have crashed and our system would be down.&lt;/p&gt;

&lt;p&gt;This is super critical to root-cause and fix, otherwise we have to abort our 3.6 upgrade (for the 2nd year in a row) and stay with 3.4.&lt;/p&gt;

&lt;p&gt;Is there a way I can re-open this bug?&lt;/p&gt;</comment>
                            <comment id="2515231" author="glajchs" created="Sat, 2 Nov 2019 14:26:31 +0000"  >&lt;p&gt;I just saw this issue happen again, this time about a day after moving our main cluster from 3.4.17-evg1 to 3.6.14.&#160; Third stack trace attached.&lt;/p&gt;</comment>
                            <comment id="2432829" author="matthew.saltz" created="Wed, 25 Sep 2019 14:30:55 +0000"  >&lt;p&gt;I&apos;ve filed a ticket (&lt;a href=&quot;https://jira.mongodb.org/browse/SERVER-43623&quot; title=&quot;Stop catching exceptions in NetworkInterfaceASIO&quot; class=&quot;issue-link&quot; data-issue-key=&quot;SERVER-43623&quot;&gt;&lt;del&gt;SERVER-43623&lt;/del&gt;&lt;/a&gt;) to make issues like the one in mongos_crash_1st easier to diagnose. Unfortunately without more information or a more specific reproducer I don&apos;t think we&apos;ll be able to make any definitive conclusions about that issue. Closing the issue, &lt;a href=&quot;https://jira.mongodb.org/secure/ViewProfile.jspa?name=glajchs&quot; class=&quot;user-hover&quot; rel=&quot;glajchs&quot;&gt;glajchs&lt;/a&gt; please feel to update and reopen if you have more information that you think would be helpful.&lt;/p&gt;</comment>
                            <comment id="2402345" author="matthew.saltz" created="Fri, 30 Aug 2019 18:57:41 +0000"  >&lt;p&gt;I noticed for the file mongos_crash_2nd.txt, the invariant you hit has since been removed by &lt;a href=&quot;https://jira.mongodb.org/browse/SERVER-40052&quot; title=&quot;Shutdown in mongos can trigger BatchWriteOp invariant&quot; class=&quot;issue-link&quot; data-issue-key=&quot;SERVER-40052&quot;&gt;&lt;del&gt;SERVER-40052&lt;/del&gt;&lt;/a&gt;, which was backported all the way to 3.6 (though I&apos;m not sure which tag it was released in). So upgrading to include that commit should fix that issue.&lt;/p&gt;

&lt;p&gt;The mongos_crash_1st is a bit harder to diagnose, since it just indicates that an &lt;a href=&quot;https://github.com/evergage/mongo/blob/5e6e97cb18f2a2f1c69c1d08ea09f82226a2e27a/src/mongo/executor/network_interface_asio.cpp#L165-L170&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;unexpected exception was thrown &lt;b&gt;somewhere&lt;/b&gt; in a networking thread&lt;/a&gt;, which doesn&apos;t really narrow things down, unfortunately. If you had a deterministic reproducer then that would help, and possibly including some of the logs preceding the crash could be helpful. &lt;a href=&quot;https://jira.mongodb.org/secure/ViewProfile.jspa?name=kaloian.manassiev&quot; class=&quot;user-hover&quot; rel=&quot;kaloian.manassiev&quot;&gt;kaloian.manassiev&lt;/a&gt; do you have a better idea of how to diagnose it?&lt;/p&gt;</comment>
                            <comment id="2387179" author="glajchs" created="Mon, 26 Aug 2019 19:36:07 +0000"  >&lt;p&gt;I understand that the mongos server is likely not crashing any time a &amp;gt;16MB record is attempted to be written, otherwise there would be a lot more crashes out in the wild.&#160; There has to be something specific about the event that happened to us, and once that is narrowed down, feel free to change the title to something (slightly) less scary.&#160; Unfortunately I don&apos;t have the full raw object as it was attempted to be written at the time, so I&apos;m not sure how I&apos;d be able to help reproduce this one better.&lt;/p&gt;

&lt;p&gt;&#160;&lt;/p&gt;

&lt;p&gt;Thanks for the very helpful synopsis of those changes @Kevin Pulo!&#160; I think for us the spam that was too much for our system was mostly centralized in change #1 and 3 there.&#160; I think that, though a bit aggressive at times, #2 there is actually something we might still be logging in our custom build.&#160; As is stated in the bug for that one, many customers find the connection logging useful to troubleshotting issues, and I can certainly agree with that.&#160; We actually have our logging service setup to help us analyze which node might be at fault (or had a blip) using those logging messages.&lt;/p&gt;

&lt;p&gt;We&apos;re currently using 3.6.6 for our raw event cluster and 3.4.19 for our core usage (much more important and real-time sensitive) cluster.&#160; We&apos;re likely going to be replacing the raw event cluster with a more purpose tailored log structured storage database soonish, but the core cluster we need to get over to 3.6.&#160; We&apos;ve tried once but had to back out of the 3.6 upgrade for performance and bug issues, but it&apos;s about time for us to address those issues and get our cluster upgraded, at which point I&apos;ll look into usage the flags available to help manage the logging levels, and will definitely use your links.&lt;/p&gt;</comment>
                            <comment id="2385644" author="kevin.pulo@10gen.com" created="Mon, 26 Aug 2019 02:43:07 +0000"  >&lt;p&gt;Hi &lt;a href=&quot;https://jira.mongodb.org/secure/ViewProfile.jspa?name=glajchs&quot; class=&quot;user-hover&quot; rel=&quot;glajchs&quot;&gt;glajchs&lt;/a&gt;, regarding your 3 logging patches:&lt;/p&gt;

&lt;ul&gt;
	&lt;li&gt;&lt;a href=&quot;https://github.com/evergage/mongo/commit/0e7551975e22890c4afa1b5c1aac5bd98d03d952&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;SERVER-30841 Increase the metadata refresh logic log levels from 0 to 1&lt;/a&gt; &amp;#8212; I can confirm that &lt;a href=&quot;https://jira.mongodb.org/browse/SERVER-30841&quot; title=&quot;Lower the amount of metadata refresh logging&quot; class=&quot;issue-link&quot; data-issue-key=&quot;SERVER-30841&quot;&gt;&lt;del&gt;SERVER-30841&lt;/del&gt;&lt;/a&gt; solves this, albeit in a more flexible way by introducing a new &quot;shardingCatalogRefresh&quot; logging component which can have its &lt;a href=&quot;https://docs.mongodb.com/manual/reference/log-messages/#configure-log-verbosity-levels&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;verbosity set independently&lt;/a&gt;.&lt;/li&gt;
&lt;/ul&gt;


&lt;ul&gt;
	&lt;li&gt;&lt;a href=&quot;https://github.com/evergage/mongo/commit/7e1bd9266969b70a1739783028430bac0cf02f74&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;Raise connection logging to level 1&lt;/a&gt; &amp;#8212; Can you confirm that using &lt;a href=&quot;https://docs.mongodb.com/manual/reference/program/mongod/#cmdoption-mongod-quiet&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;&lt;tt&gt;--quiet&lt;/tt&gt;&lt;/a&gt; or &lt;a href=&quot;https://docs.mongodb.com/manual/reference/configuration-options/#systemLog.quiet&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;&lt;tt&gt;systemLog.quiet&lt;/tt&gt;&lt;/a&gt; doesn&apos;t suit your purposes because it also suppresses other messages that you want logged?  If so, then this is &lt;a href=&quot;https://jira.mongodb.org/browse/SERVER-27663&quot; title=&quot;Informational Network component log messages should be configurable &quot; class=&quot;issue-link&quot; data-issue-key=&quot;SERVER-27663&quot;&gt;SERVER-27663&lt;/a&gt;.&lt;/li&gt;
&lt;/ul&gt;


&lt;ul&gt;
	&lt;li&gt;&lt;a href=&quot;https://github.com/evergage/mongo/commit/5e6e97cb18f2a2f1c69c1d08ea09f82226a2e27a&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;Raise metadata receipt logging to level 1&lt;/a&gt; &amp;#8212; This is &lt;a href=&quot;https://jira.mongodb.org/browse/SERVER-29109&quot; title=&quot;Client metadata log message verbosity is not parallel with connection start/end messages&quot; class=&quot;issue-link&quot; data-issue-key=&quot;SERVER-29109&quot;&gt;SERVER-29109&lt;/a&gt;.&lt;/li&gt;
&lt;/ul&gt;
</comment>
                            <comment id="2385158" author="daniel.hatcher" created="Fri, 23 Aug 2019 21:28:02 +0000"  >&lt;p&gt;Thanks for creating this ticket. This should have been resolved in 3.6.1 via &lt;a href=&quot;https://jira.mongodb.org/browse/SERVER-32372&quot; title=&quot;Mongos crashes on bulk insert where size is slightly bigger than maxBsonObjectSize&quot; class=&quot;issue-link&quot; data-issue-key=&quot;SERVER-32372&quot;&gt;&lt;del&gt;SERVER-32372&lt;/del&gt;&lt;/a&gt; but it does appear to be the same error. I&apos;ll pass this along to the appropriate team to take a look.&lt;/p&gt;</comment>
                    </comments>
                <issuelinks>
                            <issuelinktype id="10010">
                    <name>Duplicate</name>
                                                                <inwardlinks description="is duplicated by">
                                        <issuelink>
            <issuekey id="986775">SERVER-44345</issuekey>
        </issuelink>
                            </inwardlinks>
                                    </issuelinktype>
                            <issuelinktype id="10012">
                    <name>Related</name>
                                            <outwardlinks description="related to">
                                        <issuelink>
            <issuekey id="381928">SERVER-29109</issuekey>
        </issuelink>
            <issuelink>
            <issuekey id="345054">SERVER-27663</issuekey>
        </issuelink>
            <issuelink>
            <issuekey id="420424">SERVER-30841</issuekey>
        </issuelink>
                            </outwardlinks>
                                                        </issuelinktype>
                    </issuelinks>
                <attachments>
                            <attachment id="228298" name="mongos_crash_1st.txt" size="4341" author="glajchs" created="Fri, 23 Aug 2019 19:55:36 +0000"/>
                            <attachment id="228297" name="mongos_crash_2nd.txt" size="7837" author="glajchs" created="Fri, 23 Aug 2019 19:55:36 +0000"/>
                            <attachment id="236092" name="mongos_crash_3rd.txt" size="3985" author="glajchs" created="Sat, 2 Nov 2019 14:27:07 +0000"/>
                    </attachments>
                <subtasks>
                    </subtasks>
                <customfields>
                                                <customfield id="customfield_10050" key="com.atlassian.jira.toolkit:comments">
                        <customfieldname># Replies</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>13.0</customfieldvalue>
                        </customfieldvalues>
                    </customfield>
                                                                <customfield id="customfield_18555" key="com.onresolve.jira.groovy.groovyrunner:scripted-field">
                        <customfieldname># of Sprints</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>8.0</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            <customfield id="customfield_13552" key="com.go2group.jira.plugin.crm:crm_generic_field">
                        <customfieldname>Case</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue><![CDATA[[5002K00000rz6kcQAA]]]></customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                                                                            <customfield id="customfield_10055" key="com.atlassian.jira.ext.charting:firstresponsedate">
                        <customfieldname>Date of 1st Reply</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>Fri, 23 Aug 2019 21:28:02 +0000</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                <customfield id="customfield_10052" key="com.atlassian.jira.toolkit:dayslastcommented">
                        <customfieldname>Days since reply</customfieldname>
                        <customfieldvalues>
                                        3 years, 51 weeks, 1 day ago
    
                        </customfieldvalues>
                    </customfield>
                                                                <customfield id="customfield_18254" key="com.onresolve.jira.groovy.groovyrunner:scripted-field">
                        <customfieldname>Dependencies</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue><![CDATA[]]></customfieldvalue>


                        </customfieldvalues>
                    </customfield>
                                                                <customfield id="customfield_15850" key="com.atlassian.jira.plugins.jira-development-integration-plugin:devsummary">
                        <customfieldname>Development</customfieldname>
                        <customfieldvalues>
                            
                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    <customfield id="customfield_10057" key="com.atlassian.jira.toolkit:lastusercommented">
                        <customfieldname>Last comment by Customer</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>true</customfieldvalue>
                        </customfieldvalues>
                    </customfield>
                                                                                            <customfield id="customfield_10056" key="com.atlassian.jira.toolkit:lastupdaterorcommenter">
                        <customfieldname>Last commenter</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>stas.baskin@mongodb.com</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                <customfield id="customfield_11151" key="com.atlassian.jira.toolkit:LastCommentDate">
                        <customfieldname>Last public comment date</customfieldname>
                        <customfieldvalues>
                            3 years, 51 weeks, 1 day ago
                        </customfieldvalues>
                    </customfield>
                                                                                                                                                    <customfield id="customfield_10032" key="com.atlassian.jira.plugin.system.customfieldtypes:select">
                        <customfieldname>Operating System</customfieldname>
                        <customfieldvalues>
                                <customfieldvalue key="10026"><![CDATA[ALL]]></customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                <customfield id="customfield_10051" key="com.atlassian.jira.toolkit:participants">
                        <customfieldname>Participants</customfieldname>
                        <customfieldvalues>
                                        <customfieldvalue>daniel.hatcher@mongodb.com</customfieldvalue>
            <customfieldvalue>kevin.pulo@mongodb.com</customfieldvalue>
            <customfieldvalue>matthew.saltz@mongodb.com</customfieldvalue>
            <customfieldvalue>glajchs</customfieldvalue>
    
                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                        <customfield id="customfield_14254" key="com.pyxis.greenhopper.jira:gh-lexo-rank">
                        <customfieldname>Product Rank</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>1|hvmk53:</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                <customfield id="customfield_12550" key="com.pyxis.greenhopper.jira:gh-lexo-rank">
                        <customfieldname>Rank</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>2|hr85jb:</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                <customfield id="customfield_10558" key="com.pyxis.greenhopper.jira:gh-global-rank">
                        <customfieldname>Rank (Obsolete)</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>9223372036854775807</customfieldvalue>
                        </customfieldvalues>
                    </customfield>
                                                                                            <customfield id="customfield_23361" key="com.onresolve.jira.groovy.groovyrunner:scripted-field">
                        <customfieldname>Requested By</customfieldname>
                        <customfieldvalues>
                                

                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                        <customfield id="customfield_10557" key="com.pyxis.greenhopper.jira:gh-sprint">
                        <customfieldname>Sprint</customfieldname>
                        <customfieldvalues>
                                <customfieldvalue id="3198">Sharding 2019-09-09</customfieldvalue>
    <customfieldvalue id="3199">Sharding 2019-09-23</customfieldvalue>
    <customfieldvalue id="3305">Sharding 2019-10-07</customfieldvalue>
    <customfieldvalue id="3472">Sharding 2019-12-02</customfieldvalue>
    <customfieldvalue id="3473">Sharding 2019-12-16</customfieldvalue>
    <customfieldvalue id="3474">Sharding 2019-12-30</customfieldvalue>
    <customfieldvalue id="3571">Sharding 2020-02-10</customfieldvalue>
    <customfieldvalue id="3572">Sharding 2020-02-24</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                                                        <customfield id="customfield_10750" key="com.atlassian.jira.plugin.system.customfieldtypes:textarea">
                        <customfieldname>Steps To Reproduce</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>&lt;p&gt;Try to update an existing record that is very close to 16MB with some more data, brining it over the 16MB mark, using a single user update&lt;/p&gt;</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                    <customfield id="customfield_10053" key="com.atlassian.jira.ext.charting:timeinstatus">
                        <customfieldname>Time In Status</customfieldname>
                        <customfieldvalues>
                            
                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                                                                                                                                                                                                                        <customfield id="customfield_22870" key="com.onresolve.jira.groovy.groovyrunner:scripted-field">
                        <customfieldname>Triagers</customfieldname>
                        <customfieldvalues>
                                

                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                                                                                                                                    <customfield id="customfield_14350" key="com.pyxis.greenhopper.jira:gh-lexo-rank">
                        <customfieldname>serverRank</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>1|hvm6ef:</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                    </customfields>
    </item>
</channel>
</rss>