Chapter 1. The etcd service
The Red Hat build of MicroShift RPM includes the etcd service. The etcd service runs as a separate process. MicroShift automatically manages the etcd lifecycle.
1.1. Observe and debug the MicroShift etcd server Copy linkLink copied to clipboard!
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.scopeNoteMicroShift logs can be accessed separately from etcd logs using the
journalctl -u microshiftcommand.
1.2. Configuring the memoryLimitMB value to set parameters for the etcd server Copy linkLink copied to clipboard!
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.yamlfile to set thememoryLimitMBvalue.etcd: memoryLimitMB: 128NoteThe minimum permissible value for
memoryLimitMBon 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
memoryLimitMBvalue in/etc/microshift/config.yaml, restart MicroShift by running the following command:$ sudo systemctl restart microshiftVerify the new
memoryLimitMBvalue is in use by running the following command:$ systemctl show --property=MemoryHigh microshift-etcd.scope