<!-- 
RSS generated by JIRA (9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66) at Thu Feb 08 03:36: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-14983] Ability to immediately mark the node as unable to service user queries</title>
                <link>https://jira.mongodb.org/browse/SERVER-14983</link>
                <project id="10000" key="SERVER">Core Server</project>
                    <description>&lt;p&gt;In production systems there is a common problem scenario when a particular underprovisioned mongod node becomes overloaded by a sudden load peak, causing service timeouts on the application level. In this case a plain retry strategy will add more load to the already overloaded system, frequently causing massive service degradation and prolonged periods of outage.&lt;/p&gt;

&lt;p&gt;The ideal, yet very complicated way to gracefully handle the situation is for drivers or mongoS to detect that the node is overloaded and route user traffic away from it (there is a ticket for that, I think). This way the node will be able to process its backlog and successfully get through the issue, without disrupting the service further.&lt;/p&gt;

&lt;p&gt;A simpler solution is to defer the judgement to the operator, and give him the ability to immediately mark the node as unable to service user queries.&lt;/p&gt;

&lt;p&gt;Functionally, it should be a trigger that meets the following requirements:&lt;/p&gt;
&lt;ol&gt;
	&lt;li&gt;must not block on &lt;b&gt;anything&lt;/b&gt;, and must take effect &lt;b&gt;immediately&lt;/b&gt; upon triggering&lt;/li&gt;
	&lt;li&gt;In case of error, it must be reported&lt;/li&gt;
	&lt;li&gt;If activated, mongoS and drivers must not send new user queries to that node&lt;/li&gt;
	&lt;li&gt;serverStatus and/or rs.status() must report the state of the trigger&lt;/li&gt;
	&lt;li&gt;The trigger should not require a new connection to be established&lt;/li&gt;
	&lt;li&gt;A special override should be supported to allow execution on Primary servers causing them to step down&lt;/li&gt;
&lt;/ol&gt;


&lt;p&gt;As it currently stands, we have a replSetMaintenance command, which doesn&apos;t yet satisfy 1, 5, or 6. In particular for (1), setting maintenance mode requires a global write lock, which it grabs after locking the replset mutex (see &lt;a href=&quot;https://jira.mongodb.org/browse/SERVER-14982&quot; title=&quot;replSetMaintenance command should not block&quot; class=&quot;issue-link&quot; data-issue-key=&quot;SERVER-14982&quot;&gt;&lt;del&gt;SERVER-14982&lt;/del&gt;&lt;/a&gt;).&lt;/p&gt;

&lt;p&gt;This ticket is filed to provide a functional spec for the feature that we currently don&apos;t have. It should give us flexibility with choosing a solution, should we decide to implement something else, other than the replSetMaintenance command.&lt;/p&gt;</description>
                <environment></environment>
        <key id="153981">SERVER-14983</key>
            <summary>Ability to immediately mark the node as unable to service user queries</summary>
                <type id="2" iconUrl="https://jira.mongodb.org/secure/viewavatar?size=xsmall&amp;avatarId=14711&amp;avatarType=issuetype">New Feature</type>
                                            <priority id="3" iconUrl="https://jira.mongodb.org/images/icons/priorities/major.svg">Major - P3</priority>
                        <status id="1" iconUrl="https://jira.mongodb.org/images/icons/statuses/open.png" description="">Open</status>
                    <statusCategory id="2" key="new" colorName="default"/>
                                    <resolution id="-1">Unresolved</resolution>
                                        <assignee username="backlog-server-repl">Backlog - Replication Team</assignee>
                                    <reporter username="alex.komyagin@mongodb.com">Alexander Komyagin</reporter>
                        <labels>
                    </labels>
                <created>Thu, 21 Aug 2014 04:32:56 +0000</created>
                <updated>Tue, 6 Dec 2022 05:02:30 +0000</updated>
                                            <version>2.6.4</version>
                                    <fixVersion>Needs Further Definition</fixVersion>
                                    <component>Replication</component>
                    <component>Usability</component>
                                        <votes>1</votes>
                                    <watches>16</watches>
                                                                                                                <comments>
                            <comment id="698362" author="alex.komyagin@10gen.com" created="Thu, 21 Aug 2014 14:47:14 +0000"  >&lt;p&gt;Ideally it should not require a network request, but as Eric pointed it, it&apos;s not mandatory. &lt;/p&gt;

&lt;p&gt;I apologize for omitting context here. This ticket was filed to provide a functional spec for the feature that we currently don&apos;t have. I filed separate tickets for specific issues with the setMaintenance command (see &lt;a href=&quot;https://jira.mongodb.org/browse/SERVER-13925&quot; title=&quot;Allow replSetMaintenance on primary servers&quot; class=&quot;issue-link&quot; data-issue-key=&quot;SERVER-13925&quot;&gt;SERVER-13925&lt;/a&gt; and &lt;a href=&quot;https://jira.mongodb.org/browse/SERVER-14982&quot; title=&quot;replSetMaintenance command should not block&quot; class=&quot;issue-link&quot; data-issue-key=&quot;SERVER-14982&quot;&gt;&lt;del&gt;SERVER-14982&lt;/del&gt;&lt;/a&gt;). Having a separate ticket with a functional spec will give us flexibility should we decide to implement another solution.&lt;/p&gt;</comment>
                            <comment id="698247" author="milkie" created="Thu, 21 Aug 2014 13:23:19 +0000"  >&lt;p&gt;I think a network request will be fine, since it will take a network request for drivers (or other nodes) to determine that the state of the node has changed, anyway.&lt;/p&gt;</comment>
                            <comment id="698239" author="scotthernandez" created="Thu, 21 Aug 2014 13:18:09 +0000"  >&lt;p&gt;That sounds like a separate issue wrt locking pre 2.7.&lt;/p&gt;

&lt;p&gt;Are you saying we need a mechanism which does not require a network request?&lt;/p&gt;
</comment>
                            <comment id="698195" author="milkie" created="Thu, 21 Aug 2014 12:32:00 +0000"  >&lt;p&gt;I think &quot;stepdown or maintenance mode&quot; doesn&apos;t yet satisfy 1, 5, or 6.  In particular for (1), setting maintenance mode requires a global write lock, which it grabs after locking the replset mutex.&lt;/p&gt;</comment>
                            <comment id="698179" author="scotthernandez" created="Thu, 21 Aug 2014 12:15:39 +0000"  >&lt;p&gt;How is this different than stepdown for the primary, or maintenance mode?&lt;/p&gt;</comment>
                    </comments>
                <issuelinks>
                            <issuelinktype id="10012">
                    <name>Related</name>
                                            <outwardlinks description="related to">
                                        <issuelink>
            <issuekey id="153980">SERVER-14982</issuekey>
        </issuelink>
            <issuelink>
            <issuekey id="39552">SERVER-5921</issuekey>
        </issuelink>
            <issuelink>
            <issuekey id="136255">SERVER-13925</issuekey>
        </issuelink>
            <issuelink>
            <issuekey id="171724">SERVER-16349</issuekey>
        </issuelink>
                            </outwardlinks>
                                                                <inwardlinks description="is related to">
                                                        </inwardlinks>
                                    </issuelinktype>
                    </issuelinks>
                <attachments>
                    </attachments>
                <subtasks>
                    </subtasks>
                <customfields>
                                                <customfield id="customfield_10050" key="com.atlassian.jira.toolkit:comments">
                        <customfieldname># Replies</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>5.0</customfieldvalue>
                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                                                <customfield id="customfield_12751" key="com.atlassian.jira.plugin.system.customfieldtypes:multiselect">
                        <customfieldname>Assigned Teams</customfieldname>
                        <customfieldvalues>
                                <customfieldvalue key="25128"><![CDATA[Replication]]></customfieldvalue>
    
                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    <customfield id="customfield_10055" key="com.atlassian.jira.ext.charting:firstresponsedate">
                        <customfieldname>Date of 1st Reply</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>Thu, 21 Aug 2014 12:15:39 +0000</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                <customfield id="customfield_10052" key="com.atlassian.jira.toolkit:dayslastcommented">
                        <customfieldname>Days since reply</customfieldname>
                        <customfieldvalues>
                                        9 years, 25 weeks, 6 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>alexander.golin@mongodb.com</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                <customfield id="customfield_11151" key="com.atlassian.jira.toolkit:LastCommentDate">
                        <customfieldname>Last public comment date</customfieldname>
                        <customfieldvalues>
                            9 years, 25 weeks, 6 days ago
                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                    <customfield id="customfield_10051" key="com.atlassian.jira.toolkit:participants">
                        <customfieldname>Participants</customfieldname>
                        <customfieldvalues>
                                        <customfieldvalue>alex.komyagin@mongodb.com</customfieldvalue>
            <customfieldvalue>backlog-server-repl</customfieldvalue>
            <customfieldvalue>milkie@mongodb.com</customfieldvalue>
            <customfieldvalue>scotthernandez</customfieldvalue>
    
                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                        <customfield id="customfield_14254" key="com.pyxis.greenhopper.jira:gh-lexo-rank">
                        <customfieldname>Product Rank</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>1|hrlpfz:</customfieldvalue>

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

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

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