Previous change logs can be found at CHANGELOG-3.0.
See code changes and v3.1 upgrade guide for any breaking changes. Again, before running upgrades from any previous release, please make sure to read change logs below and v3.1 upgrade guide.
Note that any etcd_debugging_* metrics are experimental and subject to change.
etcd_server_slow_read_indexes_total Prometheus metric.etcd_server_quota_backend_bytes Prometheus metric.
etcd_mvcc_db_total_size_in_bytes and etcd_mvcc_db_total_size_in_use_in_bytes.etcd_server_quota_backend_bytes 2.147483648e+09 means current quota size is 2 GB.etcd_mvcc_db_total_size_in_bytes 20480 means current physically allocated DB size is 20 KB.etcd_mvcc_db_total_size_in_use_in_bytes 16384 means future DB size if defragment operation is complete.etcd_mvcc_db_total_size_in_bytes - etcd_mvcc_db_total_size_in_use_in_bytes is the number of bytes that can be saved on disk with defragment operation.etcd_mvcc_db_total_size_in_bytes Prometheus metric.
etcd_debugging_mvcc_db_total_size_in_bytes.etcd_mvcc_db_total_size_in_use_in_bytes Prometheus metric.
etcd_mvcc_db_total_size_in_bytes and etcd_mvcc_db_total_size_in_use_in_bytes.etcd_server_quota_backend_bytes 2.147483648e+09 means current quota size is 2 GB.etcd_mvcc_db_total_size_in_bytes 20480 means current physically allocated DB size is 20 KB.etcd_mvcc_db_total_size_in_use_in_bytes 16384 means future DB size if defragment operation is complete.etcd_mvcc_db_total_size_in_bytes - etcd_mvcc_db_total_size_in_use_in_bytes is the number of bytes that can be saved on disk with defragment operation.See code changes and v3.1 upgrade guide for any breaking changes. Again, before running upgrades from any previous release, please make sure to read change logs below and v3.1 upgrade guide.
Note that any etcd_debugging_* metrics are experimental and subject to change.
etcd_server_version Prometheus metric.
etcd-version-monitor.See code changes and v3.1 upgrade guide for any breaking changes. Again, before running upgrades from any previous release, please make sure to read change logs below and v3.1 upgrade guide.
[SNAPSHOT-INDEX].snap.db file on disk.See code changes and v3.1 upgrade guide for any breaking changes. Again, before running upgrades from any previous release, please make sure to read change logs below and v3.1 upgrade guide.
mvcc server panic from restore operation.
See code changes and v3.1 upgrade guide for any breaking changes. Again, before running upgrades from any previous release, please make sure to read change logs below and v3.1 upgrade guide.
*.snap.db snapshot files.
--max-snapshots flag to purge old *.snap.db files.*.snap.db files to keep maximum --max-snapshots number of files on disk.See code changes and v3.1 upgrade guide for any breaking changes. Again, before running upgrades from any previous release, please make sure to read change logs below and v3.1 upgrade guide.
Note that any etcd_debugging_* metrics are experimental and subject to change.
etcd_server_is_leader Prometheus metric.--initial-election-tick-advance flag to configure initial election tick fast-forward.
--initial-election-tick-advance=true, then local member fast-forwards election ticks to speed up "initial" leader election trigger.--initial-election-tick-advance=false.--initial-election-tick-advance at the cost of slow initial bootstrap.See code changes and v3.1 upgrade guide for any breaking changes. Again, before running upgrades from any previous release, please make sure to read change logs below and v3.1 upgrade guide.
Note that any etcd_debugging_* metrics are experimental and subject to change.
etcd_network_peer_sent_failures_total count.See code changes and v3.1 upgrade guide for any breaking changes. Again, before running upgrades from any previous release, please make sure to read change logs below and v3.1 upgrade guide.
mvcc "unsynced" watcher restore operation.
See code changes and v3.1 upgrade guide for any breaking changes. Again, before running upgrades from any previous release, please make sure to read change logs below and v3.1 upgrade guide.
See code changes and v3.1 upgrade guide for any breaking changes. Again, before running upgrades from any previous release, please make sure to read change logs below and v3.1 upgrade guide.
docker pull quay.io/coreos/etcd:v3.1 to fetch latest v3.1 versions.net/http.CloseNotifySee code changes and v3.1 upgrade guide for any breaking changes. Again, before running upgrades from any previous release, please make sure to read change logs below and v3.1 upgrade guide.
See code changes and v3.1 upgrade guide for any breaking changes. Again, before running upgrades from any previous release, please make sure to read change logs below and v3.1 upgrade guide.
See code changes and v3.1 upgrade guide for any breaking changes. Again, before running upgrades from any previous release, please make sure to read change logs below and v3.1 upgrade guide.
See code changes and v3.1 upgrade guide for any breaking changes. Again, before running upgrades from any previous release, please make sure to read change logs below and v3.1 upgrade guide.
See code changes and v3.1 upgrade guide for any breaking changes. Again, before running upgrades from any previous release, please make sure to read change logs below and v3.1 upgrade guide.
/etc/nsswitch.conf file to alpine-based Docker image.See code changes and v3.1 upgrade guide for any breaking changes. Again, before running upgrades from any previous release, please make sure to read change logs below and v3.1 upgrade guide.
See code changes and v3.1 upgrade guide for any breaking changes. Again, before running upgrades from any previous release, please make sure to read change logs below and v3.1 upgrade guide.
etcd gateway schema handling in DNS discovery.gateway, grpc-proxy.gateway, grpc-proxy.localhost:2379,2380) AND if listen URL is 0.0.0.0.See code changes and v3.1 upgrade guide for any breaking changes. Again, before running upgrades from any previous release, please make sure to read change logs below and v3.1 upgrade guide.
etcd gateway with multiple endpoints.See code changes and v3.1 upgrade guide for any breaking changes. Again, before running upgrades from any previous release, please make sure to read change logs below and v3.1 upgrade guide.
See code changes and v3.1 upgrade guide for any breaking changes. Again, before running upgrades from any previous release, please make sure to read change logs below and v3.1 upgrade guide.
etcd_grpc_requests_totaletcd_grpc_requests_failed_totaletcd_grpc_active_streamsetcd_grpc_unary_requests_duration_secondsgithub.com/ugorji/go/codec to ugorji/go@9c7f9b7, and regenerate v2 client.See security doc for more details.
TLSConfig.ServerName is ignored with user-provided certificates for backwards compatibility; to be deprecated.etcd --discovery-srv=example.com will only authenticate peers/clients when the provided certs have root domain example.com as an entry in Subject Alternative Name (SAN) field.--strict-reconfig-check flag is set by default.--log-output flag.--metrics flag.--auto-compaction-retention=10 run periodic compaction on v3 key-value store for every 10-hour.
--auto-compaction-retention=10, compactor uses revision 100 for compact revision where revision 100 is the latest revision fetched from 10 hours ago.SetEndpoints method; update endpoints at runtime.Sync method; auto-update endpoints at runtime.Lease TimeToLive API; fetch lease information.lease timetolive command.--print-value-only flag to get command.--dest-prefix flag to make-mirror command.get command responses are sorted in ascending order by default.recipes now conform to sessions defined in clientv3/concurrency./usr/local/bin/etcd*.