[SERVER-81929] Improve disk utilization experience on workstations Created: 06/Oct/23  Updated: 02/Feb/24

Status: Open
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Task Priority: Major - P3
Reporter: Memento Slack Bot Assignee: Unassigned
Resolution: Unresolved Votes: 1
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Assigned Teams:
Build
Participants:

 Description   

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?



 Comments   
Comment by Alex Neben [ 13/Nov/23 ]

Sorry I should have said why I reopened this. charlie.swanson@mongodb.com reached out to me to mention that this was still an issue he would like fixed. I don't think it is a high priority atm but it still would be nice.

Generated at Thu Feb 08 06:47:46 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.