Better error message for FileAllocator failure

XMLWordPrintableJSON

    • Type: Improvement
    • Resolution: Done
    • Priority: Minor - P4
    • None
    • Affects Version/s: None
    • Component/s: Diagnostics, Storage
    • Storage Execution
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      In database_holder.cpp we have the following code:

              if (txn->lockState()->isWriteLocked() && FileAllocator::get()->hasFailed()) {
                  uassert(17507, "Can't take a write lock while out of disk space", false);
              }
      

      If FileAllocator may fail for other reasons (e.g.: the dbpath is on a network drive and there was a network problem) then this message is misleading.

      Something like "Can't take a write lock: FileAllocator failed" would be a better message; if we could provide more info about the failure somehow, that would be even better.

            Assignee:
            [DO NOT USE] Backlog - Storage Execution Team
            Reporter:
            Ramon Fernandez Marina
            Votes:
            0 Vote for this issue
            Watchers:
            6 Start watching this issue

              Created:
              Updated:
              Resolved: