Uploaded image for project: 'Couchbase Server'
  1. Couchbase Server
  2. MB-20298

Query Service: Don't write buffer to /tmp

    XMLWordPrintable

Details

    Description

      "If there is a large scan, gsiClient buffer the scan results to /tmp."
      This is allowed to grow to 5GB of disk usage before it errors.

      We've seen issues when other components use /tmp, see MB-11560

      Writing large amounts of data to /tmp is *bad* for a number of reasons:

      1) Nowhere in our documentation or install guide do we mention that /tmp is needed by Couchbase.
      2) If /tmp isn't writable, could the query results be lost ?
      3) Are there built in checks on available disk space in /tmp ?
      4) Related to (1), while users typically configure a fast IO subsystem for the data and index directories they have no reason to do so for /tmp - and so this may be on a slow subsystem, creating a bottleneck for IO
      5) Also related to (1), we don't normally direct customers to monitor /tmp for IO and space.

      Attachments

        Issue Links

          No reviews matched the request. Check your Options in the drop-down menu of this sections header.

          Activity

            People

              ajay.bhullar Ajay Bhullar
              ianmccloy Ian McCloy (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              20 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Gerrit Reviews

                  There are no open Gerrit changes

                  PagerDuty