<!-- 
RSS generated by JIRA (9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66) at Thu Feb 08 09:05:34 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>[KAFKA-93] Connector issue with high load: Query failed with error code 136 and error message &apos;Error in $cursor stage :: caused by :: errmsg: &quot;CollectionScan died due to failure to restore tailable cursor position</title>
                <link>https://jira.mongodb.org/browse/KAFKA-93</link>
                <project id="16285" key="KAFKA">Kafka Connector</project>
                    <description>&lt;p&gt;Hi, I am using MongoDB: 3.6.17 in my setup. since MongoDB version &amp;lt; 4.0 does not support change streams in database level. I am registering multiple connector instances on my setup. I have 10 connector instances listening to 10 collections in my setup. I try to load around 5000 documents in the collections. After some time I start seeing failures like. and the connector fails and the related Kafka topic does not only partial messages.&lt;/p&gt;

&lt;p&gt;Also when I look into the connector status in&#160;curl -X GET &lt;a href=&quot;http://localhost:8083/connectors/mongo-source-2/status&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;http://localhost:8083/connectors/mongo-source-2/status&lt;/a&gt;&#160;the result says its running. but the connector is in a failed state.&lt;/p&gt;

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

&lt;p&gt;2020-03-30 17:00:15,513] WARN &lt;span class=&quot;error&quot;&gt;&amp;#91;Producer clientId=confluent.monitoring.interceptor.connector-producer-mongo-source-7-0&amp;#93;&lt;/span&gt; Error while fetching metadata with correlation id 3 : {_confluent-monitoring=LEADER_NOT_AVAILABLE} (org.apache.kafka.clients.NetworkClient)&lt;br/&gt;
com.mongodb.MongoQueryException: Query failed with error code 136 and error message &apos;Error in $cursor stage :: caused by :: errmsg: &quot;CollectionScan died due to failure to restore tailable cursor position. Last seen record id: RecordId(6810047002907247540)&quot;&apos; on server mongo1:27017&lt;br/&gt;
com.mongodb.MongoQueryException: Query failed with error code 136 and error message &apos;Error in $cursor stage :: caused by :: errmsg: &quot;CollectionScan died due to position in capped collection being deleted. Last seen record id: RecordId(6810046998612279328)&quot;&apos; on server mongo1:27017&lt;br/&gt;
com.mongodb.MongoQueryException: Query failed with error code 136 and error message &apos;Error in $cursor stage :: caused by :: errmsg: &quot;CollectionScan died due to failure to restore tailable cursor position. Last seen record id: RecordId(6810047020087116556)&quot;&apos; on server mongo1:27017&lt;br/&gt;
com.mongodb.MongoQueryException: Query failed with error code 136 and error message &apos;Error in $cursor stage :: caused by :: errmsg: &quot;CollectionScan died due to position in capped collection being deleted. Last seen record id: RecordId(6810046998612281250)&quot;&apos; on server mongo1:27017&lt;br/&gt;
com.mongodb.MongoQueryException: Query failed with error code 136 and error message &apos;Error in $cursor stage :: caused by :: errmsg: &quot;CollectionScan died due to position in capped collection being deleted. Last seen record id: RecordId(6810047015792149212)&quot;&apos; on server mongo1:27017&lt;br/&gt;
com.mongodb.MongoQueryException: Query failed with error code 136 and error message &apos;Error in $cursor stage :: caused by :: errmsg: &quot;CollectionScan died due to position in capped collection being deleted. Last seen record id: RecordId(6810047020087116658)&quot;&apos; on server mongo1:27017&lt;/p&gt;</description>
                <environment>MongoDB: 3.6.17, Kafka Connector 1.1</environment>
        <key id="1297132">KAFKA-93</key>
            <summary>Connector issue with high load: Query failed with error code 136 and error message &apos;Error in $cursor stage :: caused by :: errmsg: &quot;CollectionScan died due to failure to restore tailable cursor position</summary>
                <type id="3" iconUrl="https://jira.mongodb.org/secure/viewavatar?size=xsmall&amp;avatarId=14718&amp;avatarType=issuetype">Task</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="ross@mongodb.com">Ross Lawley</assignee>
                                    <reporter username="sabari.mgn@gmail.com">Sabari Gandhi</reporter>
                        <labels>
                    </labels>
                <created>Mon, 30 Mar 2020 17:37:34 +0000</created>
                <updated>Wed, 10 Jun 2020 06:59:45 +0000</updated>
                            <resolved>Tue, 7 Apr 2020 14:41:04 +0000</resolved>
                                    <version>1.1</version>
                                                                        <votes>0</votes>
                                    <watches>2</watches>
                                                                                                                <comments>
                            <comment id="3033533" author="sabari.mgn@gmail.com" created="Thu, 9 Apr 2020 15:59:33 +0000"  >&lt;p&gt;Hi Ross, Thanks for the update. I have added myself in the watch list of &#160;&lt;a href=&quot;https://jira.mongodb.org/browse/KAFKA-76&quot; title=&quot;Reuse the postBatchResumeToken&quot; class=&quot;issue-link&quot; data-issue-key=&quot;KAFKA-76&quot;&gt;&lt;del&gt;KAFKA-76&lt;/del&gt;&lt;/a&gt;&#160;. Also, when you get a chance can you provide some information about the release cycle planned for the connectors. Thanks in advance.&lt;/p&gt;</comment>
                            <comment id="3029272" author="ross@10gen.com" created="Tue, 7 Apr 2020 14:40:03 +0000"  >&lt;p&gt;Hi &lt;a href=&quot;https://jira.mongodb.org/secure/ViewProfile.jspa?name=sabari.mgn%40gmail.com&quot; class=&quot;user-hover&quot; rel=&quot;sabari.mgn@gmail.com&quot;&gt;sabari.mgn@gmail.com&lt;/a&gt;,&lt;/p&gt;

&lt;p&gt;Thanks for the ticket.  The issue here is the connector has seen an offset but cannot restart the change stream at that resume token.  Currently, the only work around is to clear the offsets stored in Kafka.&lt;/p&gt;

&lt;p&gt;Please watch the &lt;a href=&quot;https://jira.mongodb.org/browse/KAFKA-76&quot; title=&quot;Reuse the postBatchResumeToken&quot; class=&quot;issue-link&quot; data-issue-key=&quot;KAFKA-76&quot;&gt;&lt;del&gt;KAFKA-76&lt;/del&gt;&lt;/a&gt; ticket which will use the high water mark to help insure this doesn&apos;t happen.&lt;/p&gt;

&lt;p&gt;Ross&lt;/p&gt;</comment>
                            <comment id="3013404" author="sabari.mgn@gmail.com" created="Mon, 30 Mar 2020 17:42:48 +0000"  >&lt;p&gt;I have attached configuration I have for one of my connector instances. Please read my description as:&#160;I try to load around &lt;b&gt;50000&lt;/b&gt;&#160;documents in the collections ( i am not able to edit the description to fix the typo).&#160;&lt;/p&gt;

&lt;p&gt;Because of the error above the connector is not able to recover and I see the below messages&lt;/p&gt;

&lt;p&gt;&lt;tt&gt;&lt;span class=&quot;error&quot;&gt;&amp;#91;2020-03-30 20:27:44,880&amp;#93;&lt;/span&gt; INFO Failed to resume change stream: resume of change stream was not possible, as the resume token was not found. {_data: BinData(0, &quot;825E8254BF000008E9461E5F6964002C34B0005A10046533550540C240D080F0DE7DA09C792704&quot;), _typeBits: BinData(0, &quot;01&quot;)} 280 (com.mongodb.kafka.connect.source.MongoSourceTask)&lt;/tt&gt;&lt;/p&gt;

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

&lt;p&gt;But the curl command for the connector status returns running. I am able to reproduce the scenario with 2 connector instances with high load. Please let me know for any information. Thanks in advance.&lt;/p&gt;</comment>
                    </comments>
                <issuelinks>
                            <issuelinktype id="10010">
                    <name>Duplicate</name>
                                            <outwardlinks description="duplicates">
                                        <issuelink>
            <issuekey id="1036772">KAFKA-76</issuekey>
        </issuelink>
                            </outwardlinks>
                                                        </issuelinktype>
                    </issuelinks>
                <attachments>
                            <attachment id="254190" name="connector-config.json" size="535" author="sabari.mgn@gmail.com" created="Mon, 30 Mar 2020 17:39:48 +0000"/>
                    </attachments>
                <subtasks>
                    </subtasks>
                <customfields>
                                                                                                                                                                                                                        <customfield id="customfield_13552" key="com.go2group.jira.plugin.crm:crm_generic_field">
                        <customfieldname>Case</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue><![CDATA[[5002K00000nmQQeQAM]]]></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_12550" key="com.pyxis.greenhopper.jira:gh-lexo-rank">
                        <customfieldname>Rank</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>2|hx0047:</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>