<!-- 
RSS generated by JIRA (9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66) at Thu Feb 08 03:10:15 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-5923] Increase max document size to at least 64mb</title>
                <link>https://jira.mongodb.org/browse/SERVER-5923</link>
                <project id="10000" key="SERVER">Core Server</project>
                    <description>&lt;p&gt;There are many systems that contain highly structured data (in my case loan data) containing historic data such as prices or versions. Being forced to split these into separate top-level documents because of the document size limitation in some ways makes the database no more useful than an RDBMS and defeats the purpose of using a document-oriented database.&lt;/p&gt;

&lt;p&gt;At the very least the document size should be increased from 16mb to a more realistic 64mb. In my systems, for example, a loan&apos;s data (with historic price information) is at around 30mb per loan, and could double.&lt;/p&gt;</description>
                <environment>All platforms</environment>
        <key id="39565">SERVER-5923</key>
            <summary>Increase max document size to at least 64mb</summary>
                <type id="4" iconUrl="https://jira.mongodb.org/secure/viewavatar?size=xsmall&amp;avatarId=14710&amp;avatarType=issuetype">Improvement</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="2">Won&apos;t Fix</resolution>
                                        <assignee username="asya.kamsky@mongodb.com">Asya Kamsky</assignee>
                                    <reporter username="maverin">John Wood</reporter>
                        <labels>
                    </labels>
                <created>Thu, 24 May 2012 21:17:17 +0000</created>
                <updated>Sat, 14 Oct 2023 22:03:26 +0000</updated>
                            <resolved>Tue, 5 Feb 2019 23:28:24 +0000</resolved>
                                    <version>2.1.1</version>
                                                    <component>Performance</component>
                    <component>Storage</component>
                                        <votes>51</votes>
                                    <watches>64</watches>
                                                                                                                <comments>
                            <comment id="2142251" author="victorp" created="Fri, 8 Feb 2019 12:59:00 +0000"  >&lt;p&gt;&lt;a href=&quot;https://jira.mongodb.org/secure/ViewProfile.jspa?name=asya&quot; class=&quot;user-hover&quot; rel=&quot;asya&quot;&gt;asya&lt;/a&gt;, Please reconsider this issue.&lt;br/&gt;
 Mongo DB was at some point limited to 4MB and yet you finally decided to increase to 16MB at some point (read again the discussion on issue 431 (&lt;a href=&quot;https://jira.mongodb.org/browse/SERVER-431&quot; class=&quot;external-link&quot; rel=&quot;nofollow&quot;&gt;https://jira.mongodb.org/browse/SERVER-431&lt;/a&gt;) that was back in 2009 !). We are now 10 years later. Data is heavier. System performance has increased a lot. All that has been written is still valid as of today.&lt;/p&gt;

&lt;p&gt;Thanks&lt;/p&gt;</comment>
                            <comment id="2139042" author="asya" created="Tue, 5 Feb 2019 23:28:24 +0000"  >&lt;p&gt;Closing this ticket as we don&apos;t have plans to increase the size of document &lt;b&gt;stored&lt;/b&gt; in the database.&lt;/p&gt;

&lt;p&gt;There is a separate ticket &lt;a href=&quot;https://jira.mongodb.org/browse/SERVER-12305&quot; title=&quot;Allow command request and response BSON objects to exceed 16MB&quot; class=&quot;issue-link&quot; data-issue-key=&quot;SERVER-12305&quot;&gt;SERVER-12305&lt;/a&gt; which is tracking allowing documents which represent commands, their responses, intermediate documents etc to be larger than 16MBs.&lt;/p&gt;</comment>
                            <comment id="2051420" author="victorp" created="Mon, 5 Nov 2018 10:54:47 +0000"  >&lt;p&gt;+1 At least make this limit a conf parameter&lt;/p&gt;</comment>
                            <comment id="1631979" author="pazer" created="Wed, 26 Jul 2017 07:54:35 +0000"  >&lt;p&gt;+1 for this (or uncapping). Arbitrary limits are the devil. If I want to put a terabyte of ram in my system and query 500 mb documents, I should be able to, and not have the developers of mongodb trying to protect me from myself.&lt;/p&gt;</comment>
                            <comment id="1544374" author="salil.sabnis@cdk.com" created="Sat, 8 Apr 2017 17:26:17 +0000"  >&lt;p&gt;We have the same issue of hitting 16MB limit. Is the max document size going to be increased ? &lt;/p&gt;</comment>
                            <comment id="1428986" author="bruno.bodson" created="Tue, 8 Nov 2016 09:12:16 +0000"  >&lt;p&gt;+1. Using GridFS is not user-friendly because it stores the data in binary chunks. Redesigning my domain model will introduce lots of new references which will decrease performance. The same thing happens when increasing the document size limit. The user should be able make this trade-off by configuring the max document size limit.&lt;/p&gt;</comment>
                            <comment id="1376559" author="michael@aorato.com" created="Mon, 5 Sep 2016 07:23:52 +0000"  >&lt;p&gt;It would be great if this could be configured and even if that puts us at risk of performance we would be accountable for that and test it...&lt;/p&gt;</comment>
                            <comment id="820168" author="saganas" created="Tue, 3 Feb 2015 16:30:24 +0000"  >&lt;p&gt;We have same issue hitting 16Mb per document. I could restructure in a different way (not what I want in a model), but even then it will hit016Mb limit in 3-4 years. &lt;/p&gt;</comment>
                            <comment id="815209" author="tirramissu" created="Wed, 28 Jan 2015 09:04:52 +0000"  >&lt;p&gt;I&apos;m sure I need this.&lt;/p&gt;</comment>
                            <comment id="798290" author="pulsar" created="Tue, 6 Jan 2015 18:22:51 +0000"  >&lt;p&gt;this is an important things, we need more space too, 16mb is too limited&lt;/p&gt;</comment>
                            <comment id="714303" author="rohit.badwaik@adp.com" created="Tue, 9 Sep 2014 06:47:23 +0000"  >&lt;p&gt;+1. &lt;br/&gt;
We are reaching the limit when trying to get data for 2 delears. Afraid of what will happen with growing/changing client requirements. &lt;/p&gt;</comment>
                            <comment id="659458" author="ravi_kothiyal@birlasoft.timeinc.com" created="Tue, 15 Jul 2014 15:55:16 +0000"  >&lt;p&gt;We are also facing this issue . Love to have this feature.&lt;/p&gt;</comment>
                            <comment id="548959" author="joshhansen" created="Mon, 14 Apr 2014 19:03:11 +0000"  >&lt;p&gt;A possible interim approach would be to throw a more specific exception than OperationFailure to better enable error handling&lt;/p&gt;</comment>
                            <comment id="548928" author="joshhansen" created="Mon, 14 Apr 2014 18:50:26 +0000"  >&lt;p&gt;I just ran into this issue. I&apos;ve been using mongo to aggregate events on a website by user, and over just a few days of activity some users had exceeded the 16mb threshold. The vast majority of users will never exceed the threshold, but for those that do it would be nice to have a smooth way of handling. Making this user configurable would be great, along with some guidance on how performance might be affected with higher or lower limits.&lt;/p&gt;</comment>
                            <comment id="499844" author="itzikkg" created="Sat, 15 Feb 2014 12:04:19 +0000"  >&lt;p&gt;16 MB limitation is a real problem. within a year or two machines will have much more memory but the mongodb infrastructure will continue to regard it with old memory restrictions. &lt;br/&gt;
I think that 64 MB document limitation will not be enough for some applications as well and I wouldn&apos;t assume from that that it&apos;s a bad data model. It takes Just one document that oversize that limitation that can ruin your model. I think that it&apos;s better to know that for some situations there will performance issues , assuming that they&apos;ll be the exceptions rather than the general cases.&lt;br/&gt;
I think that it should be configurable or have a much broader limit.&lt;/p&gt;</comment>
                            <comment id="386116" author="joseph.the.techie" created="Mon, 22 Jul 2013 10:10:35 +0000"  >&lt;p&gt;How about changing in the source code and recompiling as a custom build that works with larger document size e.g. 64MB. Do committers think: A) it&apos;s just somewhat lowering the performance but it&apos;s going to work or B) There is a fundamental assumption (e.g. document size or memory issue) that makes more serious problems?&lt;/p&gt;</comment>
                            <comment id="249624" author="ian@10gen.com" created="Fri, 25 Jan 2013 14:49:21 +0000"  >&lt;p&gt;Chris, we don&apos;t have any plans to increase the limit (or make it configurable) right now, but as long as you&apos;re watching this ticket you&apos;ll get an email if/when we do schedule it.&lt;/p&gt;</comment>
                            <comment id="186385" author="jblackburn" created="Mon, 12 Nov 2012 12:05:00 +0000"  >&lt;p&gt;We&apos;re hitting 16mb limits here too.&lt;/p&gt;

&lt;p&gt;When storing time series data (even compressed, as blobs!) we inevitably need to break the data up by month to fit into the current 16MB limit.  16MB constrains the data layout significantly, as there&apos;s much additional complexity on the application side to stitch the underlying data back together.&lt;/p&gt;

&lt;p&gt;Currently we hit this limit a lot, and ideally it would be a tunable.&lt;/p&gt;

&lt;p&gt;(Note: we&apos;re sizing, and sharding our cluster such that data fits in memory on the servers.)&lt;/p&gt;</comment>
                            <comment id="162197" author="eliot" created="Mon, 10 Sep 2012 02:59:39 +0000"  >&lt;p&gt;I don&apos;t think we&apos;ll just increase it again.&lt;br/&gt;
If we change it, it would be to make it configurable or something else.&lt;/p&gt;</comment>
                            <comment id="162184" author="klukas" created="Mon, 10 Sep 2012 02:10:37 +0000"  >&lt;p&gt;I have the same problem. In rare cases the size of documents may exceed the limits. I&apos;d rather still save it somehow internally chunked or saved possibly more slowly but as a huge document, than to write work-around-code at every imaginable place. Also the proposed 64 MB could in some cases give a problem, so this limit needs to be user-configurable (in this case I would increase it much further, to really be save). I understand that there could be code errors, which could stay uncatched if there is no limit, but then I still would prefer it if this limit would be based on hardware limits (i.e. full disc) than on arbitrary limits.&lt;/p&gt;</comment>
                    </comments>
                <issuelinks>
                            <issuelinktype id="10010">
                    <name>Duplicate</name>
                                                                <inwardlinks description="is duplicated by">
                                        <issuelink>
            <issuekey id="60542">SERVER-8047</issuekey>
        </issuelink>
            <issuelink>
            <issuekey id="1155671">SERVER-46212</issuekey>
        </issuelink>
                            </inwardlinks>
                                    </issuelinktype>
                            <issuelinktype id="10012">
                    <name>Related</name>
                                            <outwardlinks description="related to">
                                        <issuelink>
            <issuekey id="1877259">SERVER-60040</issuekey>
        </issuelink>
            <issuelink>
            <issuekey id="105325">SERVER-12305</issuekey>
        </issuelink>
            <issuelink>
            <issuekey id="331509">SERVER-27013</issuekey>
        </issuelink>
                            </outwardlinks>
                                                                <inwardlinks description="is related to">
                                        <issuelink>
            <issuekey id="276987">SERVER-23482</issuekey>
        </issuelink>
                            </inwardlinks>
                                    </issuelinktype>
                    </issuelinks>
                <attachments>
                    </attachments>
                <subtasks>
                    </subtasks>
                <customfields>
                                                <customfield id="customfield_10050" key="com.atlassian.jira.toolkit:comments">
                        <customfieldname># Replies</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>20.0</customfieldvalue>
                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                <customfield id="customfield_10055" key="com.atlassian.jira.ext.charting:firstresponsedate">
                        <customfieldname>Date of 1st Reply</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>Mon, 10 Sep 2012 02:10:37 +0000</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                <customfield id="customfield_10052" key="com.atlassian.jira.toolkit:dayslastcommented">
                        <customfieldname>Days since reply</customfieldname>
                        <customfieldvalues>
                                        5 years, 5 days 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>spencer.brown@mongodb.com</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                <customfield id="customfield_11151" key="com.atlassian.jira.toolkit:LastCommentDate">
                        <customfieldname>Last public comment date</customfieldname>
                        <customfieldvalues>
                            5 years, 5 days ago
                        </customfieldvalues>
                    </customfield>
                                                                                                                        <customfield id="customfield_10000" key="com.atlassian.jira.plugin.system.customfieldtypes:radiobuttons">
                        <customfieldname>Old_Backport</customfieldname>
                        <customfieldvalues>
                                <customfieldvalue key="10000"><![CDATA[No]]></customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                <customfield id="customfield_10051" key="com.atlassian.jira.toolkit:participants">
                        <customfieldname>Participants</customfieldname>
                        <customfieldvalues>
                                        <customfieldvalue>asya.kamsky@mongodb.com</customfieldvalue>
            <customfieldvalue>bruno.bodson</customfieldvalue>
            <customfieldvalue>klukas</customfieldvalue>
            <customfieldvalue>eliot</customfieldvalue>
            <customfieldvalue>saganas</customfieldvalue>
            <customfieldvalue>pulsar</customfieldvalue>
            <customfieldvalue>ian@mongodb.com</customfieldvalue>
            <customfieldvalue>itzikkg</customfieldvalue>
            <customfieldvalue>jblackburn</customfieldvalue>
            <customfieldvalue>maverin</customfieldvalue>
            <customfieldvalue>joseph.the.techie</customfieldvalue>
            <customfieldvalue>joshhansen</customfieldvalue>
            <customfieldvalue>tirramissu</customfieldvalue>
            <customfieldvalue>pazer</customfieldvalue>
            <customfieldvalue>michael@aorato.com</customfieldvalue>
            <customfieldvalue>ravi_kothiyal@birlasoft.timeinc.com</customfieldvalue>
            <customfieldvalue>rohit.badwaik@adp.com</customfieldvalue>
            <customfieldvalue>salil.sabnis@cdk.com</customfieldvalue>
            <customfieldvalue>victorp</customfieldvalue>
    
                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                        <customfield id="customfield_14254" key="com.pyxis.greenhopper.jira:gh-lexo-rank">
                        <customfieldname>Product Rank</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>1|hrjclz:</customfieldvalue>

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

                        </customfieldvalues>
                    </customfield>
                                                                <customfield id="customfield_10558" key="com.pyxis.greenhopper.jira:gh-global-rank">
                        <customfieldname>Rank (Obsolete)</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>6501</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_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|hs9zwn:</customfieldvalue>

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