[DOCS-828] conflicting recommendations for read-ahead settings on software raid Created: 29/Nov/12  Updated: 04/Sep/13  Resolved: 29/Aug/13

Status: Closed
Project: Documentation
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Bug Priority: Major - P3
Reporter: J Rassi Assignee: Jared Rosoff
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
is related to DOCS-164 Create wiki page explaining disk read... Closed
Participants:
Days since reply: 10 years, 25 weeks ago

 Description   

From http://www.mongodb.org/display/DOCS/Amazon+EC2+Quickstart

$ sudo blockdev --setra 128 /dev/md0
$ sudo blockdev --setra 128 /dev/sdh1
$ sudo blockdev --setra 128 /dev/sdh2
$ sudo blockdev --setra 128 /dev/sdh3
$ sudo blockdev --setra 128 /dev/sdh4

From http://www.mongodb.org/display/DOCS/Readahead

RAID on EC2: If you are following our Amazon EC2 guidelines, and running with multiple EBS volumes in a software RAID configuration, then the recommendation is to set the readahead to 0 on the volumes that make up the RAID array while setting the readahead to the value you want on the RAID volume itself.



 Comments   
Comment by Jared Rosoff [ 29/Aug/13 ]

EC2 quick start guide has been updated. It now conforms to the recommendations made elsewhere in our docs about Readheads.

Generated at Thu Feb 08 07:39:36 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.