<!-- 
RSS generated by JIRA (9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66) at Thu Feb 08 03:56:35 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-21190] Bring back --nojournal for config servers</title>
                <link>https://jira.mongodb.org/browse/SERVER-21190</link>
                <project id="10000" key="SERVER">Core Server</project>
                    <description>&lt;p&gt;Hello,&lt;/p&gt;

&lt;p&gt;Would it be possible to bring back the --nojournal option to the config servers, or is there a critical reason why this is now forbidden other than being a good practice to not use it?&lt;/p&gt;

&lt;p&gt;Although that may be a poor practice in production, it is a very useful option for test suites that require bringing up and down several servers, and care about the speed of operations and not at all about the safeguards brought by journaling.&lt;/p&gt;

&lt;p&gt;Thanks for considering it.&lt;/p&gt;</description>
                <environment></environment>
        <key id="236687">SERVER-21190</key>
            <summary>Bring back --nojournal for config servers</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="9">Done</resolution>
                                        <assignee username="schwerin@mongodb.com">Andy Schwerin</assignee>
                                    <reporter username="niemeyer">Gustavo Niemeyer</reporter>
                        <labels>
                    </labels>
                <created>Wed, 28 Oct 2015 23:01:29 +0000</created>
                <updated>Wed, 30 Nov 2016 15:29:41 +0000</updated>
                            <resolved>Wed, 30 Nov 2016 15:29:41 +0000</resolved>
                                    <version>3.2.0-rc1</version>
                                                    <component>Sharding</component>
                                        <votes>0</votes>
                                    <watches>17</watches>
                                                                                                                <comments>
                            <comment id="1445795" author="milkie" created="Wed, 30 Nov 2016 15:29:41 +0000"  >&lt;p&gt;In version 3.4, it is no longer possible to run config servers using the MMAPv1 storage engine, so it no longer makes sense to bring back --nojournal.  (Note that for WiredTiger, running without journaling enabled does not make things faster.)&lt;/p&gt;

&lt;p&gt;In version 3.2 and prior, it is possible to use the --nopreallocj option to avoid preallocating journal files for mirrored config servers at startup, which may improve the speed of tests using the MMAPv1 storage engine.  We use this option in our own test suites.&lt;/p&gt;</comment>
                            <comment id="1128134" author="niemeyer" created="Wed, 6 Jan 2016 23:06:08 +0000"  >&lt;p&gt;I&apos;m not doing anything funky here that I&apos;m aware of, and I&apos;m using SSDs. If you have magic tricks to make twelve MongoDB servers not take an awful lot of time to be brought up as a few replica sets and become healthy, I&apos;m all ears.  Gabriel Russel has the setup locally at the office to show you, if you&apos;d like to have a look. &lt;/p&gt;</comment>
                            <comment id="1128125" author="schwerin" created="Wed, 6 Jan 2016 22:59:03 +0000"  >&lt;p&gt;OK. I&apos;m still surprised. We bring up sharded clusters and shut them down dozens of times per hour on single machines as part of automated testing. Anyhow, send a pull request and I&apos;ll merge it.&lt;/p&gt;</comment>
                            <comment id="1128109" author="niemeyer" created="Wed, 6 Jan 2016 22:47:46 +0000"  >&lt;p&gt;It&apos;s not only the test times that are affected, but the bringing up of the test cluster at all. Every time the cluster has to be brought up these three MongoDB config servers alone will trash the disk with 1.3GB when being started. It was already slow before, and there are already delayed checks to wait until it all comes online and becomes healthy, but this is now driving the server to a standstill. I could add further delayed checks everywhere, and even space up the starting of each of the servers, but this doesn&apos;t feel very reasonable or productive. One of the great features of MongoDB to me has always been that it was a snappy database to deal with.. having to sit down for a long time to bring up a handful of servers every time I want to switch over to a different version of the database would be unfortunate.&lt;/p&gt;</comment>
                            <comment id="1128087" author="schwerin" created="Wed, 6 Jan 2016 22:21:20 +0000"  >&lt;p&gt;We don&apos;t want to test config servers with this combination of options, so we disabled it. If you want to, send a pull request that allows this combination of options only when the enableTestCommands server parameter is set to true. I&apos;ll merge that, since it should prevent casual users from combining those options.&lt;/p&gt;

&lt;p&gt;I&apos;m surprised that your test time is affected by config server performance. Are you testing a lot of collection creation/drop behavior?&lt;/p&gt;</comment>
                            <comment id="1128075" author="niemeyer" created="Wed, 6 Jan 2016 22:07:32 +0000"  >&lt;p&gt;I am using one config server, per replica set. Three replica sets, three config servers. It&apos;s not about testing mmap config servers as part of the Go driver.. It&apos;s about testing the Go driver at all, as explained above. WT doesn&apos;t even work with the suite right now, due to &lt;a href=&quot;https://jira.mongodb.org/browse/SERVER-21198&quot; title=&quot;Using --nojournal on 3.2 WiredTiger slows down tests by an order of magnitude&quot; class=&quot;issue-link&quot; data-issue-key=&quot;SERVER-21198&quot;&gt;&lt;del&gt;SERVER-21198&lt;/del&gt;&lt;/a&gt;. Even with that aside, the Go test suite has caught actual server bugs multiple times, &lt;a href=&quot;https://jira.mongodb.org/browse/SERVER-21403&quot; title=&quot;$snapshot can return duplicates on 3.2 in the case of an MMAPv1 document move&quot; class=&quot;issue-link&quot; data-issue-key=&quot;SERVER-21403&quot;&gt;&lt;del&gt;SERVER-21403&lt;/del&gt;&lt;/a&gt; being the most recent). So I don&apos;t understand the dismissal above.&lt;/p&gt;

&lt;p&gt;Then, besides all of that, it&apos;s unclear why there&apos;s so much resistance to allowing an option to be used, one which has always been allowed until now, rather than artificially restricting it. Right now I&apos;m manually hacking the server code so I can run tests.. Is there a good reason to make life harder over here? I don&apos;t think I&apos;ve bothered you with requests these years.. surprises me the resistance for this trivial one liner.&lt;/p&gt;

&lt;p&gt;I honestly don&apos;t understand&lt;/p&gt;</comment>
                            <comment id="1127945" author="schwerin" created="Wed, 6 Jan 2016 20:54:22 +0000"  >&lt;p&gt;If you&apos;re only doing testing, you could just run a single config server instead of three. Additionally, it doesn&apos;t seem important to test mmap config servers as part of the go driver; you could just always test using WT config servers.&lt;/p&gt;</comment>
                            <comment id="1087746" author="niemeyer" created="Fri, 13 Nov 2015 13:34:31 +0000"  >&lt;p&gt;Pretty please?  This is currently the only way I can run the full test suite in a reasonable amount of time. I expect &lt;a href=&quot;https://jira.mongodb.org/browse/SERVER-21198&quot; title=&quot;Using --nojournal on 3.2 WiredTiger slows down tests by an order of magnitude&quot; class=&quot;issue-link&quot; data-issue-key=&quot;SERVER-21198&quot;&gt;&lt;del&gt;SERVER-21198&lt;/del&gt;&lt;/a&gt; to fix the problem with WiredTiger, but even then fixing the bug here would still be the only way to get the suite to pass with MMAPv1, which is definitely helpful in terms of ensuring things are working properly (&lt;a href=&quot;https://jira.mongodb.org/browse/SERVER-21403&quot; title=&quot;$snapshot can return duplicates on 3.2 in the case of an MMAPv1 document move&quot; class=&quot;issue-link&quot; data-issue-key=&quot;SERVER-21403&quot;&gt;&lt;del&gt;SERVER-21403&lt;/del&gt;&lt;/a&gt; came out of that, for example).&lt;/p&gt;</comment>
                            <comment id="1079647" author="niemeyer" created="Wed, 4 Nov 2015 19:15:01 +0000"  >&lt;p&gt;I have changed the server code locally to allow me to provide --nojournal to config servers in 3.2 and I can confirm that using mmapv1 the amount of disk use and activity becomes the same in the config servers as it used to be in 3.0, which enables me to test 3.2 at all.&lt;/p&gt;

&lt;p&gt;There&apos;s still a problem with WiredTiger worth being fixed before 3.2 is out as being tracked in &lt;a href=&quot;https://jira.mongodb.org/browse/SERVER-21198&quot; title=&quot;Using --nojournal on 3.2 WiredTiger slows down tests by an order of magnitude&quot; class=&quot;issue-link&quot; data-issue-key=&quot;SERVER-21198&quot;&gt;&lt;del&gt;SERVER-21198&lt;/del&gt;&lt;/a&gt;, but that seems like an independent issue from this flag. I would appreciate if we could drop that artificial constraint so I can abandon my local hack.&lt;/p&gt;</comment>
                            <comment id="1078585" author="niemeyer" created="Tue, 3 Nov 2015 21:37:17 +0000"  >&lt;p&gt;As another data point, this is the directory sizes for several databases out of my test suite:&lt;/p&gt;

&lt;p&gt;Was running it with mmapv1 storage engine for testing purposes.&lt;/p&gt;

&lt;p&gt;% du -sh *&lt;br/&gt;
419M    cfg1&lt;br/&gt;
419M    cfg2&lt;br/&gt;
419M    cfg3&lt;br/&gt;
18M     db1&lt;br/&gt;
18M     db2&lt;br/&gt;
18M     rs1a&lt;br/&gt;
18M     rs1b&lt;br/&gt;
18M     rs1c&lt;br/&gt;
18M     rs2a&lt;br/&gt;
18M     rs2b&lt;br/&gt;
18M     rs2c&lt;br/&gt;
18M     rs3a&lt;br/&gt;
18M     rs3b&lt;br/&gt;
18M     rs3c&lt;br/&gt;
18M     rs4a&lt;/p&gt;

&lt;p&gt;Would appreciate if we could take back the ability to not have these 400MB directories in such a scenario for 3.2.&lt;/p&gt;</comment>
                            <comment id="1078520" author="niemeyer" created="Tue, 3 Nov 2015 20:40:55 +0000"  >&lt;p&gt;Current investigations in &lt;a href=&quot;https://jira.mongodb.org/browse/SERVER-21198&quot; title=&quot;Using --nojournal on 3.2 WiredTiger slows down tests by an order of magnitude&quot; class=&quot;issue-link&quot; data-issue-key=&quot;SERVER-21198&quot;&gt;&lt;del&gt;SERVER-21198&lt;/del&gt;&lt;/a&gt; seem indicative that --nojournal is in fact relevant in WiredTiger as well.&lt;/p&gt;

&lt;p&gt;Can we please have the flag back for config servers too?&lt;/p&gt;</comment>
                            <comment id="1073977" author="dan@10gen.com" created="Thu, 29 Oct 2015 14:10:35 +0000"  >&lt;p&gt;The journal is a reasonable requirement for config servers, and as Andy said, with WT it shouldn&apos;t have a huge impact on your test harness performance.  I think &lt;a href=&quot;https://jira.mongodb.org/browse/SERVER-21198&quot; title=&quot;Using --nojournal on 3.2 WiredTiger slows down tests by an order of magnitude&quot; class=&quot;issue-link&quot; data-issue-key=&quot;SERVER-21198&quot;&gt;&lt;del&gt;SERVER-21198&lt;/del&gt;&lt;/a&gt; is the real issue here.&lt;/p&gt;</comment>
                            <comment id="1073877" author="niemeyer" created="Thu, 29 Oct 2015 12:25:06 +0000"  >&lt;p&gt;I&apos;m using the default storage engine in the setup, which in my understanding should mean WiredTiger on 3.2.&lt;/p&gt;

&lt;p&gt;Perhaps this is a red-herring in the middle of a more important issue. I&apos;m just observing significant slow downs when running tests on 3.2, which Gabriel could reproduce yesterday. Will file a separate ticket about that.&lt;/p&gt;</comment>
                            <comment id="1073491" author="schwerin" created="Wed, 28 Oct 2015 23:17:27 +0000"  >&lt;p&gt;Are these test suites running the WiredTiger storage engine? Could they be?&lt;br/&gt;
The startup/teardown time with journaling enabled is significantly better&lt;br/&gt;
with WiredTiger than with MMAPv1. It may be a non-issue if you could be&lt;br/&gt;
using WT for your config servers.&lt;/p&gt;

&lt;p&gt;On Wed, Oct 28, 2015 at 7:02 PM Gustavo Niemeyer (JIRA) &amp;lt;jira@mongodb.org&amp;gt;&lt;/p&gt;
</comment>
                    </comments>
                <issuelinks>
                            <issuelinktype id="10010">
                    <name>Duplicate</name>
                                                                <inwardlinks description="is duplicated by">
                                        <issuelink>
            <issuekey id="263543">SERVER-22500</issuekey>
        </issuelink>
                            </inwardlinks>
                                    </issuelinktype>
                            <issuelinktype id="10012">
                    <name>Related</name>
                                                                <inwardlinks description="is related to">
                                        <issuelink>
            <issuekey id="236807">SERVER-21198</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>14.0</customfieldvalue>
                        </customfieldvalues>
                    </customfield>
                                                                <customfield id="customfield_18555" key="com.onresolve.jira.groovy.groovyrunner:scripted-field">
                        <customfieldname># of Sprints</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>1.0</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    <customfield id="customfield_10055" key="com.atlassian.jira.ext.charting:firstresponsedate">
                        <customfieldname>Date of 1st Reply</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>Wed, 28 Oct 2015 23:17:27 +0000</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                <customfield id="customfield_10052" key="com.atlassian.jira.toolkit:dayslastcommented">
                        <customfieldname>Days since reply</customfieldname>
                        <customfieldvalues>
                                        7 years, 11 weeks 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>false</customfieldvalue>
                        </customfieldvalues>
                    </customfield>
                                                                                            <customfield id="customfield_10056" key="com.atlassian.jira.toolkit:lastupdaterorcommenter">
                        <customfieldname>Last commenter</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>milkie@mongodb.com</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                <customfield id="customfield_11151" key="com.atlassian.jira.toolkit:LastCommentDate">
                        <customfieldname>Last public comment date</customfieldname>
                        <customfieldvalues>
                            7 years, 11 weeks ago
                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                    <customfield id="customfield_10051" key="com.atlassian.jira.toolkit:participants">
                        <customfieldname>Participants</customfieldname>
                        <customfieldvalues>
                                        <customfieldvalue>schwerin@mongodb.com</customfieldvalue>
            <customfieldvalue>dan@mongodb.com</customfieldvalue>
            <customfieldvalue>milkie@mongodb.com</customfieldvalue>
            <customfieldvalue>niemeyer</customfieldvalue>
    
                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                        <customfield id="customfield_14254" key="com.pyxis.greenhopper.jira:gh-lexo-rank">
                        <customfieldname>Product Rank</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>1|hrkqef:</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                <customfield id="customfield_12550" key="com.pyxis.greenhopper.jira:gh-lexo-rank">
                        <customfieldname>Rank</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>2|hre2qn:</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="750">Sharding D (12/11/15)</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|hsfig7:</customfieldvalue>

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