You got to love debugging JavaScript errors. Here’s one from a MongoDB map/reduce. The operation fails with this:
04:39:41 Database command 'mapreduce' failed: (
assertion: 'map invoke failed: JS Error:
TypeError: spline has no properties nofile_b:7';
assertionCode: '9014';
errmsg: 'db assertion failure';
ok: '0.0').
Examining the MongoDB log we notice that the map/reduce completes to about 70%, so this is caused by some data inside the database. In this case the issue is in the spline object being accessed by the map function. Indeed, the map tries to fetch spline.reticulated, which is hopefully a Boolean value. The error “spline has no properties” is, generally, another way of saying “spline is null”. In my case splines live in an embedded collection inside bones, and aren’t expected to be null, so I need to track down a null spline inside bone.splines.
While we can just look for a null embedded object, more generally, we can find whether a JS object has no properties with this isEmpty function from SO. Declare it in the mongodb console (use a 1-liner):
Iterate over all bones records.
Here’s the culprit, notice the null embedded spline.
You can get rid of it in different ways on the mongo console. In this case we have two splines, one to keep and another to erase.
How did we get into having this null record anyway? See https://jira.mongodb.org/browse/SERVER-831 and mongoid#2545.