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

operation aborted because all indexes on collection dropped

    • Type: Icon: Bug Bug
    • Resolution: Done
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: 3.4.10
    • Component/s: None
    • ALL
    • Hide

      query sql is this

      db.test_alarm.aggregate([{
      $lookup:

      { from: "number_sum", localField: "number", foreignField: "compress_number", as: "compress_counts" }

      }, {
      $match:
      {
      "alarmRule":

      { "$ne": "1" }

      ,
      "username": "admin"
      }
      }, {
      $sort :

      { "create_time": -1 }

      }

      ])

      If you remove the sorting, you can query the data normally,like this:
      db.test_alarm.aggregate([
          { $lookup: 

      { from: "number_sum", localField: "number", foreignField: "compress_number", as: "compress_counts"         }

          },
          { $match: {
                  "alarmRule": 

      {                 "$ne": "1"             }

      ,
                  "username": "admin"
              }
          },
          
      ])  
      So I think it’s a sort of problem,I tested in another environment, if the query exceeds the query cache, an error will be reported:out of query cache tell me try add {allowDiskUse: true},if i add it,sql will always run

       

      but i add {allowDiskUse: true} to report error environment,The error is still “all indexes on collection dropped” 

      Please help me to solve this problem  ,Thank you very very much

      or tell me the logic of this sort sorting, under which circumstances it will report an error

       

      My English is bad, please forgive me   sorry!

       

       
       

      Show
      query sql is this db.test_alarm.aggregate([{ $lookup: { from: "number_sum", localField: "number", foreignField: "compress_number", as: "compress_counts" } }, { $match: { "alarmRule": { "$ne": "1" } , "username": "admin" } }, { $sort : { "create_time": -1 } } ]) If you remove the sorting, you can query the data normally,like this: db.test_alarm.aggregate([     { $lookup:  { from: "number_sum", localField: "number", foreignField: "compress_number", as: "compress_counts"         }     },     { $match: {             "alarmRule":  {                 "$ne": "1"             } ,             "username": "admin"         }     },      ])   So I think it’s a sort of problem,I tested in another environment, if the query exceeds the query cache, an error will be reported:out of query cache tell me try add {allowDiskUse: true},if i add it,sql will always run   but i add {allowDiskUse: true} to report error environment,The error is still “all indexes on collection dropped”  Please help me to solve this problem  ,Thank you very very much or tell me the logic of this sort sorting, under which circumstances it will report an error   My English is bad, please forgive me   sorry!      

      Hello , I created 8 million pieces of data in the environment. After I aggregate and query the two sets in the data, when I use sort to sort, mongo reports an error.
      query failed with error code 1608 and error messenge ‘collection or indexes disappeaed when cursor yielded: opertionFailed: opertion aborted because:all indexes on collection dropped’ on server xxxx:27017

            Assignee:
            Unassigned Unassigned
            Reporter:
            1028544680@qq.com fu xi
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: