-
Type:
Task
-
Resolution: Done
-
Priority:
Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
Labels:
-
Environment:Linux, AWS
*Location*: http://docs.mongodb.org/manual/administration/production-notes/#readahead
*User-Agent*: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_7_5) AppleWebKit/537.31 (KHTML, like Gecko) Chrome/26.0.1410.65 Safari/537.31
*Referrer*: http://stackoverflow.com/questions/16715961/mongodb-readahead-warning
*Screen Resolution*: 1440 x 900
*repo*: docs
*source*: administration/production-notes
Linux, AWS *Location*: http://docs.mongodb.org/manual/administration/production-notes/#readahead *User-Agent*: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_7_5) AppleWebKit/537.31 (KHTML, like Gecko) Chrome/26.0.1410.65 Safari/537.31 *Referrer*: http://stackoverflow.com/questions/16715961/mongodb-readahead-warning *Screen Resolution*: 1440 x 900 *repo*: docs *source*: administration/production-notes
I'm receiving this warning when starting my MongoDB shell:
Wed Mar 20 22:40:49.850 [initandlisten]
Wed Mar 20 22:40:49.850 [initandlisten] ** WARNING: Readahead for /data is set to 2048KB
Wed Mar 20 22:40:49.850 [initandlisten] ** We suggest setting it to 256KB (512 sectors) or less
Wed Mar 20 22:40:49.850 [initandlisten] ** http://dochub.mongodb.org/core/readahead
I've used:
df /data
To find where the drive is that my data is mounted and subsequently used:
sudo blockdev --setra 256 /dev/mapper/vg0-data
to set the readahead to the 256 that was specified. I've confirmed this has worked with:
sudo blockdev --getra /dev/mapper/vg0-data
I'm still however getting the same error when starting my shell?
UPDATE
I've restarted the mongodb server instance and am still receiving this error.
UPDATE 2
My linux server is hosted on AWS and therefore uses virtual volumes. I have set the readahead value for all those volumes to 256 and still receive this error.