https://etcd.io/docs/v3.1/dev-internal/Recent content in etcd internal dev on etcdHugoen-ushttps://etcd.io/docs/v3.1/dev-internal/discovery_protocol/Mon, 01 Jan 0001 00:00:00 +0000https://etcd.io/docs/v3.1/dev-internal/discovery_protocol/<p>Discovery service protocol helps new etcd member to discover all other members in cluster bootstrap phase using a shared discovery URL.</p> <p>Discovery service protocol is <em>only</em> used in cluster bootstrap phase, and cannot be used for runtime reconfiguration or cluster monitoring.</p> <p>The protocol uses a new discovery token to bootstrap one <em>unique</em> etcd cluster. Remember that one discovery token can represent only one etcd cluster. As long as discovery protocol on this token starts, even if it fails halfway, it must not be used to bootstrap another etcd cluster.</p>https://etcd.io/docs/v3.1/dev-internal/logging/Mon, 01 Jan 0001 00:00:00 +0000https://etcd.io/docs/v3.1/dev-internal/logging/<p>etcd uses the <a href="https://github.com/coreos/pkg/tree/master/capnslog" target="_blank" rel="noopener">capnslog</a> library for logging application output categorized into <em>levels</em>. A log message&rsquo;s level is determined according to these conventions:</p> <ul> <li> <p>Error: Data has been lost, a request has failed for a bad reason, or a required resource has been lost</p> <ul> <li>Examples: <ul> <li>A failure to allocate disk space for WAL</li> </ul> </li> </ul> </li> <li> <p>Warning: (Hopefully) Temporary conditions that may cause errors, but may work fine. A replica disappearing (that may reconnect) is a warning.</p>