MicroShift is Technology Preview software only.
For more information about the support scope of Red Hat Technology Preview software, see Technology Preview Support Scope.Chapter 1. MicroShift etcd
MicroShift etcd is delivered as part of the MicroShift RPM. The etcd service is run as a separate process and the lifecycle is managed automatically by MicroShift.
MicroShift is Technology Preview only. This Technology Preview software is not supported with Red Hat production service level agreements (SLAs) and might not be functionally complete. Red Hat does not recommend using MicroShift in production. Technology Preview provides early access to upcoming product features, enabling customers to test functionality and provide feedback during the development process.
Red Hat does not support an update path from the Technology Preview version to later versions of MicroShift. A new installation is necessary.
For more information about the support scope of Red Hat Technology Preview features, read Technology Preview Features Support Scope.
1.1. Observe and debug the MicroShift etcd server
You can gather journalctl
logs to observe and debug the etcd server logs.
Prerequisites
- The MicroShift service is running.
Procedure
To get the logs for etcd, run the following command:
$ sudo journalctl -u microshift-etcd.scope
NoteMicroShift logs can be accessed separately from etcd logs using the
journalctl -u microshift
command.
1.2. Configuring the memoryLimitMB value to set parameters for the MicroShift etcd server
By default, etcd will use as much memory as necessary to handle the load on the system. In some memory constrained systems, it might be necessary to limit the amount of memory etcd is allowed to use at a given time.
Procedure
Edit the
/etc/microshift/config.yaml
file to set thememoryLimitMB
value.etcd: memoryLimitMB: 128
NoteThe minimum permissible value for
memoryLimitMB
on MicroShift is 128 MB. Values close to the minimum value are more likely to impact etcd performance. The lower the limit, the longer etcd takes to respond to queries. If the limit is too low or the etcd usage is high, queries time out.
Verification
After modifying the
memoryLimitMB
value in/etc/microshift/config.yaml
, restart MicroShift by running the following command:$ sudo systemctl restart microshift
Verify the new
memoryLimitMB
value is in use by running the following command:$ systemctl show --property=MemoryHigh microshift-etcd.scope