Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-32493

PlanExecutor killed: CappedPositionLost after upgrading from 3.4.1 => 3.6.1

    • Type: Icon: Bug Bug
    • Resolution: Duplicate
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: 3.6.1
    • Component/s: None
    • Labels:
    • Environment:

      We tail the oplog for some of our operations. After an upgrade today from 3.4.1 => 3.6.1 our oplog tailer is failing with the following stacktrace:

      com.mongodb.MongoQueryException: Query failed with error code 175 and error message 'PlanExecutor killed: CappedPositionLost: CollectionScan died due to failure to restore tailable cursor position. Last seen record id: RecordId(6505472699941257226)' on server ip-10-0-0-131:27017
      at com.mongodb.operation.QueryHelper.translateCommandException(QueryHelper.java:31)
      at com.mongodb.operation.QueryBatchCursor.getMore(QueryBatchCursor.java:215)
      at com.mongodb.operation.QueryBatchCursor.hasNext(QueryBatchCursor.java:103)
      at com.mongodb.MongoBatchCursorAdapter.hasNext(MongoBatchCursorAdapter.java:46)
      at com.mongodb.DBCursor.hasNext(DBCursor.java:155)
      at com.mongodb.casbah.MongoCursorBase$class.hasNext(MongoCursor.scala:73)
      at com.mongodb.casbah.MongoCursor.hasNext(MongoCursor.scala:487)

      Not finding a lot of info about this out there after searching. Please advise? We have also tried 3.6.1 driver but same result. What changed and how can we work around this?

            kelsey.schubert@mongodb.com Kelsey Schubert
            davisford@gmail.com Davis Ford
            1 Vote for this issue
            14 Start watching this issue