<!-- 
RSS generated by JIRA (9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66) at Wed Feb 07 21:10:23 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>[CDRIVER-705] Use new getMore server command to read capped collections</title>
                <link>https://jira.mongodb.org/browse/CDRIVER-705</link>
                <project id="10030" key="CDRIVER">C Driver</project>
                    <description>&lt;p&gt;By looking at the implementation of _mongoc_cursor_get_more() &lt;a href=&quot;https://github.com/mongodb/mongo-c-driver/blob/53682560c307a806bb41c37232e8d4ec182df3ba/src/mongoc/mongoc-cursor.c#L574&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://github.com/mongodb/mongo-c-driver/blob/53682560c307a806bb41c37232e8d4ec182df3ba/src/mongoc/mongoc-cursor.c#L574&lt;/a&gt;&lt;br/&gt;
the code is still using OP_GET_MORE path to read from capped collections.&lt;br/&gt;
Based on this jira issue: &lt;a href=&quot;https://jira.mongodb.org/browse/SERVER-18184&quot; class=&quot;external-link&quot; rel=&quot;nofollow&quot;&gt;https://jira.mongodb.org/browse/SERVER-18184&lt;/a&gt;, it will be convenient to add support for reading from capped collection using new getMore command given the fact next version of mongodb adds support for blocking awaitData.&lt;br/&gt;
Until this is released, when tailing in capped collections, MondoDB does busy waiting creating a non-scalable scenario when there&apos;s a lot of clients waiting for data on a capped collections.&lt;br/&gt;
The mentioned Jira issue fixes this problem, but only if going thru getMore path not if using OP_GET_MORE command.&lt;br/&gt;
For that there&apos;s another issue in Jira &lt;a href=&quot;https://jira.mongodb.org/browse/SERVER-18841&quot; class=&quot;external-link&quot; rel=&quot;nofollow&quot;&gt;https://jira.mongodb.org/browse/SERVER-18841&lt;/a&gt;, but it has no resolution date.&lt;/p&gt;</description>
                <environment></environment>
        <key id="210674">CDRIVER-705</key>
            <summary>Use new getMore server command to read capped collections</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="3">Duplicate</resolution>
                                        <assignee username="jesse@mongodb.com">A. Jesse Jiryu Davis</assignee>
                                    <reporter username="jsbattig@convey.com">Jose Battig</reporter>
                        <labels>
                    </labels>
                <created>Mon, 15 Jun 2015 16:36:02 +0000</created>
                <updated>Tue, 10 Nov 2015 20:10:29 +0000</updated>
                            <resolved>Tue, 10 Nov 2015 20:10:14 +0000</resolved>
                                    <version>1.1.7</version>
                                    <fixVersion>1.3.0-beta0</fixVersion>
                                    <component>libmongoc</component>
                                        <votes>0</votes>
                                    <watches>4</watches>
                                                                                                                <comments>
                            <comment id="942341" author="jsbattig@convey.com" created="Tue, 16 Jun 2015 21:18:24 +0000"  >&lt;p&gt;Jesse, thanks.&lt;br/&gt;
We will wait then for MongoDB 3.2 general release when new C driver and keep using out custom mongo build then.&lt;/p&gt;</comment>
                            <comment id="940727" author="jesse" created="Mon, 15 Jun 2015 17:25:17 +0000"  >&lt;p&gt;Not really, Jose. With an emphasis on &lt;b&gt;estimated&lt;/b&gt;, MongoDB 3.2 should be out this year, and the compatible C Driver release will precede it by a few weeks.&lt;/p&gt;</comment>
                            <comment id="940704" author="jsbattig@convey.com" created="Mon, 15 Jun 2015 17:11:32 +0000"  >&lt;p&gt;Jesse, thanks for getting back on this so quickly!&lt;br/&gt;
Do you have an ETA on this?&lt;/p&gt;</comment>
                            <comment id="940676" author="jesse" created="Mon, 15 Jun 2015 16:59:11 +0000"  >&lt;p&gt;Thanks Jose, this will be implemented in whichever C Driver version, likely 1.3, that is released with general support for MongoDB 3.2 features. That will include the getMore command for &lt;b&gt;all&lt;/b&gt; cursor getMore operations, not just on capped collections. That release will also support the new &quot;find&quot; command and any other new features in the wire protocol.&lt;/p&gt;</comment>
                    </comments>
                <issuelinks>
                            <issuelinktype id="10010">
                    <name>Duplicate</name>
                                            <outwardlinks description="duplicates">
                                        <issuelink>
            <issuekey id="229446">CDRIVER-838</issuekey>
        </issuelink>
                            </outwardlinks>
                                                        </issuelinktype>
                            <issuelinktype id="10012">
                    <name>Related</name>
                                                                <inwardlinks description="is related to">
                                        <issuelink>
            <issuekey id="229446">CDRIVER-838</issuekey>
        </issuelink>
                            </inwardlinks>
                                    </issuelinktype>
                    </issuelinks>
                <attachments>
                    </attachments>
                <subtasks>
                    </subtasks>
                <customfields>
                                                                                                                                                                                                                                                                                                                                                                    <customfield id="customfield_15850" key="com.atlassian.jira.plugins.jira-development-integration-plugin:devsummary">
                        <customfieldname>Development</customfieldname>
                        <customfieldvalues>
                            
                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            <customfield id="customfield_12550" key="com.pyxis.greenhopper.jira:gh-lexo-rank">
                        <customfieldname>Rank</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>2|hsabpz:</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>
                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            </customfields>
    </item>
</channel>
</rss>