Uploaded image for project: 'Debezium'
  1. Debezium
  2. DBZ-5469

AWS DocumentDB (with MongoDB Compatibility) CappedPositionLost Failure

    XMLWordPrintable

Details

    • Bug
    • Resolution: Unresolved
    • Major
    • under-triaging
    • 2.0.0.Beta1
    • mongodb-connector
    • None
    • False
    • None
    • False

    Description

      In order to make your issue reports as actionable as possible, please provide the following information, depending on the issue type.

      Bug report

      For bug reports, provide this information, please:

      What Debezium connector do you use and what version?

      2.0.0.Beta1

      What is the connector configuration?

       

      {
       "name": "docdb-connector",
       "config":
      {      
      "connector.class" : "io.debezium.connector.mongodb.MongoDbConnector",
        "tasks.max" : "1",
           "mongodb.hosts" : "***.ap-northeast-2.docdb.amazonaws.com:27017",
           "mongodb.name" : "TEST",
           "mongodb.user" : "****",
           "mongodb.password" : "****"
           }
       } 

       

      What is the captured database version and mode of depoyment?

      Amazon DocumentDB (with MongoDB Compatibility) Mongo Version 4.0

      What behaviour do you expect?

      Connector running fine and not failing
      Not seeing this:

      Caused by: org.apache.kafka.connect.errors.ConnectException: Error while attempting to read from change stream on 'rs0/****.ap-northeast-2.docdb.amazonaws.com:27017'
      
      io.debezium.connector.mongodb.MongoDbStreamingChangeEventSource.lambda$establishConnectionToPrimary$3(MongoDbStreamingChangeEventSource.java:165)io.debezium.connector.mongodb.ConnectionContext$MongoPrimary.execute(ConnectionContext.java:286)io.debezium.connector.mongodb.MongoDbStreamingChangeEventSource.streamChangesForReplicaSet(MongoDbStreamingChangeEventSource.java:115)... 10 more
      
      Caused by: com.mongodb.MongoCommandException: Command failed with error 136:'CappedPositionLost: CollectionScan died due to position in capped collection being deleted.' on server ****.ap-northeast-2.docdb.amazonaws.com:27017. 

       

       

      What behaviour do you see?

      Failing as described above - Full logs attached

       

      Do you see the same behaviour using the latest relesead Debezium version?

      Yes

      Do you have the connector logs, ideally from start till finish?

      (You might be asked later to provide DEBUG/TRACE level log)

      <Your answer>

      How to reproduce the issue using our tutorial deployment?

      <Your answer>

      Feature request or enhancement

      For feature requests or enhancements, provide this information, please:

      Which use case/requirement will be addressed by the proposed feature?

      Debezium MongoDB connector supporting AWS DocumentDB (with MongoDB compatibility)

      Implementation ideas (optional)

      <Your answer>

      Attachments

        Activity

          People

            Unassigned Unassigned
            nishantarora Nishant Arora (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated: