Details
-
Improvement
-
Resolution: Fixed
-
Critical
-
4.5.0
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
- relates to
-
MB-11560 Compaction: Don't write to /tmp
- Resolved
-
MB-25804 Indexer/GSI client should use configured location/quota for backfill files
- Resolved
-
MB-25805 Provide options in Web Console to specify query_tmpspace path & quota
- Resolved
-
MB-25806 Allow REST API to set query-tmpspace path/quote
- Resolved
-
DOC-2631 Document query_tmpspace & related quota settings and backfills
- Closed
- mentioned in
-
Page Loading...