Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-81929

Improve disk utilization experience on workstations

    • Type: Icon: Task Task
    • Resolution: Unresolved
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • Labels:
      None
    • Build

      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?

            Assignee:
            Unassigned Unassigned
            Reporter:
            memento@mongodb.com Memento Slack Bot
            Votes:
            1 Vote for this issue
            Watchers:
            6 Start watching this issue

              Created:
              Updated: