-
Type:
Task
-
Resolution: Unresolved
-
Priority:
Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
None
-
DevProd Build
-
None
-
3
-
None
-
None
-
None
-
None
-
None
-
None
I have noticed myself and now will.buerger@mongodb.com is running into similar issues: the way we launch our virtual workstations, it seems we mount the user-configured amount of disk space (500G by default I think?) at /home/ubuntu. However, our defaults will put the toolchain at '/opt' (~10GB in size) and mongod will want to put data in /data/db/, both of which appear to be mounted on a separate disk with a much smaller capacity (~62GB?). In practice, if you put any reasonable amount of data into a mongod (~10-15GB), you'll run out of disk space.
Should we make it a documented/easy best practice to symlink those directories to /home/ubuntu somewhere? Or will some scripts break? Or can we somehow change up how disks are mounted so we don't run out of space as easily?