Downgrade Procedure Once upgraded to MongoDB 2.6, you cannot downgrade to any version earlier than Mon- goDB 2.4. If you have text or 2dsphere indexes, you can only downgrade to MongoDB 2.4.10 or later. 

Except as described on this page, moving between 2.4 and 2.6 is a drop-in replacement: 

Step 1: Stop the existing mongod instance. For example, on Linux, run 2.6 mongod with the --shutdown option as follows: 

mongod --dbpath /var/mongod/data --shutdown 

Replace /var/mongod/data with your MongoDB dbPath . See also the Stop mongod Processes (page 225) for alternate methods of stopping a mongod instance. 

Step 2: Start the new mongod instance. Ensure you start the 2.4 mongod with the same dbPath : 

mongod --dbpath /var/mongod/data 

Replace /var/mongod/data with your MongoDB dbPath . 

See Upgrade MongoDB to 2.6 (page 866) for full upgrade instructions. 

## Download 

To download MongoDB 2.6, go to the downloads page$^{676}$. 

## Other Resources 

• All JIRA issues resolved in 2.6$^{677}$. 

• All Third Party License Notices$^{678}$. 

## 12.2.2 Release Notes for MongoDB 2.4 

March 19, 2013 

MongoDB 2.4 includes enhanced geospatial support, switch to V8 JavaScript engine, security enhancements, and text search (beta) and hashed index. 

## Minor Releases 

## 2.4 Changelog 

## 2.4.14 

• Packaging: Init script sets process ulimit to different value compared to documentation (SERVER-17780$^{679}$) 

• Security: Compute BinData length in v8 (SERVER-17647$^{680}$) 

