Bug 1266527 - no documentation of partitioning when master+etcd is also an active node
no documentation of partitioning when master+etcd is also an active node
Status: CLOSED WONTFIX
Product: OpenShift Container Platform
Classification: Red Hat
Component: Documentation (Show other bugs)
3.0.0
Unspecified Unspecified
low Severity medium
: ---
: ---
Assigned To: Alex Dellapenta
Vikram Goyal
Vikram Goyal
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2015-09-25 09:53 EDT by Erik M Jacobs
Modified: 2017-12-30 21:44 EST (History)
5 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2017-12-30 21:44:54 EST
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Erik M Jacobs 2015-09-25 09:53:52 EDT
There is currently no documentation of putting etcd's data on a separate partition.

In certain cases when a user has a Master with etcd that also is acting as an active/schedulable node, docker images, logging, and other activities can fill up the partition that etcd is on.

This can result (in 3.0.2 and earlier) in un-recoverable corruption of the etcd data.

Even when etcd is fixed to safely handle out-of-disk, it's probably just good practice for etcd data to be on a dedicated partition.

Note You need to log in before you can comment on or make changes to this bug.