MongoDB - too much data for sort() with no index error
Solution 1
Try adding {community_id: 1, 'updated_at.t': -1}
index. It needs to search by community_id
first and then sort.
Solution 2
So it "feels" like you're using the index, but the index is actually a composite index. I'm not sure that the sort is "smart enough" to use only the partial index.
So two problems:
- Based on your query, I would put community_id as the first part of the index, not the second.
updated_at.t
sounds like a field on which you'll do range queries. Indexes work better if the range query is the second bit. - How many entries are going to come back from
community_id => 1
? If the number is not big, you may be able to get away with just sorting without an index.
So you may have to switch the index around and you may have to change the sort to use both community_id
and updated_at.t
. I know it seems redundant, but start there and check the Google Groups if it's still not working.
Solution 3
Even with an index, I think you can still get that error if your result set exceeds 4MB.
You can see the size by going into the mongodb console and doing this:
show dbs
# pick yours (e.g., production)
use db-production
db.articles.stats()
I ended up with results like this:
{
"ns" : "mdalert-production.encounters",
"count" : 89077,
"size" : 62974416,
"avgObjSize" : 706.9660630690302,
"storageSize" : 85170176,
"numExtents" : 8,
"nindexes" : 6,
"lastExtentSize" : 25819648,
"paddingFactor" : 1,
"flags" : 1,
"totalIndexSize" : 18808832,
"indexSizes" : {
"_id_" : 3719168,
"patient_num_1" : 3440640,
"msg_timestamp_1" : 2981888,
"practice_id_1" : 2342912,
"patient_id_1" : 3342336,
"msg_timestamp_-1" : 2981888
},
"ok" : 1
}
Vlad Zloteanu
Ruby / Python hacker. NoSQL advocate. Lead Software engineer @ Dolead. @vladzloteanu
Updated on June 24, 2022Comments
-
Vlad Zloteanu about 2 years
I am using MongoDB 1.6.3, to store a big collection (300k+ records). I added a composite index.
db['collection_name'].getIndexes() [ { "name" : "_id_", "ns" : "db_name.event_logs", "key" : { "_id" : 1 } }, { "key" : { "updated_at.t" : -1, "community_id" : 1 }, "ns" : "db_name.event_logs", "background" : true, "name" : "updated_at.t_-1_community_id_1" } ]
However, when I try to run this code:
db['collection_name'] .find({:community_id => 1}) .sort(['updated_at.t', -1]) .skip(@skip) .limit(@limit)
I am getting:
Mongo::OperationFailure (too much data for sort() with no index. add an index or specify a smaller limit)
What am I doing wrong?
-
yashan about 12 yearsThe sort column must be the last column in the index. mongodb.org/display/DOCS/….
-
Florent almost 6 yearsIsn't it db.articles.stats() ?