version: 3.5.0-rc.1

Signed-off-by: Sam Batschelet <sbatsche@redhat.com>

.github/ISSUE_TEMPLATE.md

@@ -1,2 +1,2 @@
 
-Please read https://github.com/etcd-io/etcd/blob/master/Documentation/reporting_bugs.md.
+Please read https://etcd.io/docs/latest/reporting_bugs/

.github/ISSUE_TEMPLATE/distributors-application.md

@@ -0,0 +1,28 @@
+---
+name: Distributors Application
+title: Distributors Application for <YOUR DISTRIBUTION HERE>
+about: Apply for membership of security@etcd.io
+---
+
+<!--
+Please answer the following questions and provide supporting evidence for
+meeting the membership criteria.
+-->
+
+**Actively monitored security email alias for our project:**
+
+**1. Have a user base not limited to your own organization.**
+
+**2. Have a publicly verifiable track record up to present day of fixing security issues.**
+
+**3. Not be a downstream or rebuild of another distribution.**
+
+**4. Be a participant and active contributor in the community.**
+
+**5. Accept the Embargo Policy.**
+<!-- https://github.com/etcd-io/etcd/blob/main/security/security-release-process.md#disclosures -->
+
+**6. Be willing to contribute back.**
+<!-- Per https://github.com/etcd-io/etcd/blob/main/security/security-release-process.md#patch-release-and-public-communication -->
+
+**7. Have someone already on the list vouch for the person requesting membership on behalf of your distribution.**

.github/PULL_REQUEST_TEMPLATE.md

@@ -1,2 +1,2 @@
 
-Please read https://github.com/etcd-io/etcd/blob/master/CONTRIBUTING.md#contribution-flow.
+Please read https://github.com/etcd-io/etcd/blob/main/CONTRIBUTING.md#contribution-flow.

.github/SECURITY.md

@@ -1,2 +1,2 @@
 
-Please read https://github.com/etcd-io/etcd/blob/master/security/README.md.
+Please read https://github.com/etcd-io/etcd/blob/main/security/README.md.

.github/stale.yml

@@ -0,0 +1,60 @@
+# Configuration for probot-stale - https://github.com/probot/stale
+
+# Number of days of inactivity before an Issue or Pull Request becomes stale
+daysUntilStale: 90
+
+# Number of days of inactivity before an Issue or Pull Request with the stale label is closed.
+# Set to false to disable. If disabled, issues still need to be closed manually, but will remain marked as stale.
+daysUntilClose: 21
+
+# Only issues or pull requests with all of these labels are check if stale. Defaults to `[]` (disabled)
+onlyLabels: []
+
+# Issues or Pull Requests with these labels will never be considered stale. Set to `[]` to disable
+exemptLabels:
+  - "area/security"
+  - "Investigating"
+
+# Set to true to ignore issues in a project (defaults to false)
+exemptProjects: false
+
+# Set to true to ignore issues in a milestone (defaults to false)
+exemptMilestones: false
+
+# Set to true to ignore issues with an assignee (defaults to false)
+exemptAssignees: false
+
+# Label to use when marking as stale
+staleLabel: stale
+
+# Comment to post when marking as stale. Set to `false` to disable
+markComment: >
+  This issue has been automatically marked as stale because it has not had
+  recent activity. It will be closed after 21 days if no further activity
+  occurs. Thank you for your contributions.
+
+# Comment to post when removing the stale label.
+# unmarkComment: >
+#   Your comment here.
+
+# Comment to post when closing a stale Issue or Pull Request.
+# closeComment: >
+#   Your comment here.
+
+# Limit the number of actions per hour, from 1-30. Default is 30
+limitPerRun: 30
+
+# Limit to only `issues` or `pulls`
+# only: issues
+
+# Optionally, specify configuration settings that are specific to just 'issues' or 'pulls':
+# pulls:
+#   daysUntilStale: 30
+#   markComment: >
+#     This pull request has been automatically marked as stale because it has not had
+#     recent activity. It will be closed if no further activity occurs. Thank you
+#     for your contributions.
+
+# issues:
+#   exemptLabels:
+#     - confirmed

.github/workflows/asset-transparency.yaml

@@ -0,0 +1,18 @@
+name: Publish Release Assets to Asset Transparency Log
+
+on:
+  release:
+    types: [published, created, edited, released]
+
+jobs:
+  github_release_asset_transparency_log_publish_job:
+    runs-on: ubuntu-latest
+    name: Publish GitHub release asset digests to https://beta-asset.transparencylog.net
+    steps:
+    - name: Gather URLs from GitHub release and publish
+      id: asset-transparency
+      uses: transparencylog/github-releases-asset-transparency-verify-action@v11
+    - name: List verified and published URLs
+      run: echo "Verified URLs ${{ steps.asset-transparency.outputs.verified }}"
+    - name: List failed URLs
+      run: echo "Failed URLs ${{ steps.asset-transparency.outputs.failed }}"

.github/workflows/codeql-analysis.yml

@@ -0,0 +1,67 @@
+# For most projects, this workflow file will not need changing; you simply need
+# to commit it to your repository.
+#
+# You may wish to alter this file to override the set of languages analyzed,
+# or to provide custom queries or build logic.
+#
+# ******** NOTE ********
+# We have attempted to detect the languages in your repository. Please check
+# the `language` matrix defined below to confirm you have the correct set of
+# supported CodeQL languages.
+#
+name: "CodeQL"
+
+on:
+  push:
+    branches: [ main, release-0.4, release-2.0, release-2.1, release-2.2, release-2.3, release-3.0, release-3.1 ]
+  pull_request:
+    # The branches below must be a subset of the branches above
+    branches: [ main ]
+  schedule:
+    - cron: '20 14 * * 5'
+
+jobs:
+  analyze:
+    name: Analyze
+    runs-on: ubuntu-latest
+
+    strategy:
+      fail-fast: false
+      matrix:
+        language: [ 'go' ]
+        # CodeQL supports [ 'cpp', 'csharp', 'go', 'java', 'javascript', 'python' ]
+        # Learn more:
+        # https://docs.github.com/en/free-pro-team@latest/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-code-scanning#changing-the-languages-that-are-analyzed
+
+    steps:
+    - name: Checkout repository
+      uses: actions/checkout@v2
+
+    # Initializes the CodeQL tools for scanning.
+    - name: Initialize CodeQL
+      uses: github/codeql-action/init@v1
+      with:
+        languages: ${{ matrix.language }}
+        # If you wish to specify custom queries, you can do so here or in a config file.
+        # By default, queries listed here will override any specified in a config file.
+        # Prefix the list here with "+" to use these queries and those in the config file.
+        # queries: ./path/to/local/query, your-org/your-repo/queries@main
+
+    # Autobuild attempts to build any compiled languages  (C/C++, C#, or Java).
+    # If this step fails, then you should remove it and run the build manually (see below)
+    - name: Autobuild
+      uses: github/codeql-action/autobuild@v1
+
+    # ℹ️ Command-line programs to run using the OS shell.
+    # 📚 https://git.io/JvXDl
+
+    # ✏️ If the Autobuild fails above, remove it and uncomment the following three lines
+    #    and modify them (or add more) to build your code if your project
+    #    uses a compiled language
+
+    #- run: |
+    #   make bootstrap
+    #   make release
+
+    - name: Perform CodeQL Analysis
+      uses: github/codeql-action/analyze@v1

.github/workflows/e2e.yaml

@@ -0,0 +1,35 @@
+name: E2E
+on: [push, pull_request]
+jobs:
+  test:
+    runs-on: ubuntu-latest
+    strategy:
+      fail-fast: true
+      matrix:
+        target:
+        - linux-amd64-e2e
+        - linux-386-e2e
+    steps:
+    - uses: actions/checkout@v2
+    - uses: actions/setup-go@v2
+      with:
+        go-version: "^1.16"
+    - run: date
+    - env:
+        TARGET: ${{ matrix.target }}
+      run: |
+        echo "${TARGET}"
+        case "${TARGET}" in
+          linux-amd64-e2e)
+            PASSES='build release e2e' MANUAL_VER=v3.4.7 CPU='4' EXPECT_DEBUG='true' COVER='false' RACE='true' ./test.sh 2>&1 | tee test.log
+            ! egrep "(--- FAIL:|DATA RACE|panic: test timed out|appears to have leaked)" -B50 -A10 test.log
+            ;;
+          linux-386-e2e)
+            GOARCH=386 PASSES='build e2e' CPU='4' EXPECT_DEBUG='true' COVER='false' RACE='true' ./test.sh 2>&1 | tee test.log
+            ! egrep "(--- FAIL:|DATA RACE|panic: test timed out|appears to have leaked)" -B50 -A10 test.log
+            ;;
+          *)
+            echo "Failed to find target"
+            exit 1
+            ;;
+        esac

.github/workflows/functional.yaml

@@ -0,0 +1,29 @@
+name: functional-tests
+on: [push, pull_request]
+jobs:
+  test:
+    runs-on: ubuntu-latest
+    strategy:
+      fail-fast: true
+      matrix:
+        target:
+        - linux-amd64-functional
+    steps:
+    - uses: actions/checkout@v2
+    - uses: actions/setup-go@v2
+      with:
+        go-version: "^1.16"
+    - run: date
+    - env:
+        TARGET: ${{ matrix.target }}
+      run: |
+        echo "${TARGET}"
+        case "${TARGET}" in
+          linux-amd64-functional)
+            GO_BUILD_FLAGS='-v -mod=readonly' ./build && GOARCH=amd64 PASSES='functional' ./test
+            ;;
+          *)
+            echo "Failed to find target"
+            exit 1
+            ;;
+        esac

.github/workflows/grpcproxy.yaml

@@ -0,0 +1,30 @@
+name: grpcProxy-tests
+on: [push, pull_request]
+jobs:
+  test:
+    runs-on: ubuntu-latest
+    strategy:
+      fail-fast: true
+      matrix:
+        target:
+        - linux-amd64-grpcproxy
+    steps:
+    - uses: actions/checkout@v2
+    - uses: actions/setup-go@v2
+      with:
+        go-version: "^1.16"
+    - run: date
+    - env:
+        TARGET: ${{ matrix.target }}
+      run: |
+        echo "${TARGET}"
+        case "${TARGET}" in
+          linux-amd64-grpcproxy)
+            PASSES='build grpcproxy'  CPU='4' COVER='false' RACE='true' ./test.sh 2>&1 | tee test.log
+            ! egrep "(--- FAIL:|DATA RACE|panic: test timed out|appears to have leaked)" -B50 -A10 test.log
+            ;;
+          *)
+            echo "Failed to find target"
+            exit 1
+            ;;
+        esac

.github/workflows/self-hosted-linux-arm64-graviton2-tests.yml

@@ -0,0 +1,19 @@
+name: Linux ARM64 Graviton2
+on: [push, pull_request]
+
+jobs:
+  test:
+    runs-on: [self-hosted, linux, ARM64, graviton2]
+    steps:
+      - uses: actions/checkout@v2
+      - name: install dependencies
+        run: |
+          sudo amazon-linux-extras install epel
+          sudo yum install -y git gcc ShellCheck
+      - uses: actions/setup-go@v2
+        with:
+          go-version: "^1.16"
+      - run: go version
+      - run: date
+      - name: Run tests
+        run: TEST_OPTS="PASSES='fmt bom dep build unit integration_e2e'" make test

.github/workflows/self-hosted-linux-arm64-graviton2-tests.yml.md

@@ -0,0 +1,142 @@
+
+## Graviton-based self-hosted github action worker
+
+### Step 1. Create an EC2 instance with Graviton
+
+Create an AWS Graviton-based EC2 instance. For example,
+
+```
+# or download from https://github.com/aws/aws-k8s-tester/releases
+cd ${HOME}/go/src/github.com/aws/aws-k8s-tester
+go install -v ./cmd/ec2-utils
+
+# create arm64 AL2 instance
+AWS_K8S_TESTER_EC2_ON_FAILURE_DELETE=true \
+AWS_K8S_TESTER_EC2_LOG_COLOR=true \
+AWS_K8S_TESTER_EC2_REGION=us-west-2 \
+AWS_K8S_TESTER_EC2_S3_BUCKET_CREATE=true \
+AWS_K8S_TESTER_EC2_S3_BUCKET_CREATE_KEEP=true \
+AWS_K8S_TESTER_EC2_REMOTE_ACCESS_KEY_CREATE=true \
+AWS_K8S_TESTER_EC2_ASGS_FETCH_LOGS=false \
+AWS_K8S_TESTER_EC2_ASGS='{"GetRef.Name-arm64-al2-cpu":{"name":"GetRef.Name-arm64-al2-cpu","remote-access-user-name":"ec2-user","ami-type":"AL2_arm_64","image-id-ssm-parameter":"/aws/service/ami-amazon-linux-latest/amzn2-ami-hvm-arm64-gp2","instance-types":["m6g.xlarge"],"volume-size":40,"asg-min-size":1,"asg-max-size":1,"asg-desired-capacity":1}}' \
+AWS_K8S_TESTER_EC2_ROLE_CREATE=true \
+AWS_K8S_TESTER_EC2_VPC_CREATE=true \
+ec2-utils create instances --enable-prompt=true --auto-path
+```
+
+### Step 2. Install github action on the host
+
+SSH into the instance, and install the github action self-hosted runner (see [install scripts](https://github.com/etcd-io/etcd/settings/actions/runners/new?arch=arm64&os=linux)).
+
+### Step 3. Configure github action on the host
+
+SSH into the instance, and configure the github action self-hosted runner.
+
+First, we need disable ICU install (see [actions/runner issue on ARM64](https://github.com/actions/runner/issues/629)):
+
+```
+sudo yum install -y patch
+```
+
+And write this bash script:
+
+```
+#!/bin/bash -e
+
+patch -p1 <<ICU_PATCH
+diff -Naur a/bin/Runner.Listener.runtimeconfig.json b/bin/Runner.Listener.runtimeconfig.json
+--- a/bin/Runner.Listener.runtimeconfig.json	2020-07-01 02:21:09.000000000 +0000
++++ b/bin/Runner.Listener.runtimeconfig.json	2020-07-28 00:02:38.748868613 +0000
+@@ -8,7 +8,8 @@
+       }
+     ],
+     "configProperties": {
+-      "System.Runtime.TieredCompilation.QuickJit": true
++      "System.Runtime.TieredCompilation.QuickJit": true,
++      "System.Globalization.Invariant": true
+     }
+   }
+-}
+\ No newline at end of file
++}
+diff -Naur a/bin/Runner.PluginHost.runtimeconfig.json b/bin/Runner.PluginHost.runtimeconfig.json
+--- a/bin/Runner.PluginHost.runtimeconfig.json	2020-07-01 02:21:22.000000000 +0000
++++ b/bin/Runner.PluginHost.runtimeconfig.json	2020-07-28 00:02:59.358680003 +0000
+@@ -8,7 +8,8 @@
+       }
+     ],
+     "configProperties": {
+-      "System.Runtime.TieredCompilation.QuickJit": true
++      "System.Runtime.TieredCompilation.QuickJit": true,
++      "System.Globalization.Invariant": true
+     }
+   }
+-}
+\ No newline at end of file
++}
+diff -Naur a/bin/Runner.Worker.runtimeconfig.json b/bin/Runner.Worker.runtimeconfig.json
+--- a/bin/Runner.Worker.runtimeconfig.json	2020-07-01 02:21:16.000000000 +0000
++++ b/bin/Runner.Worker.runtimeconfig.json	2020-07-28 00:02:19.159028531 +0000
+@@ -8,7 +8,8 @@
+       }
+     ],
+     "configProperties": {
+-      "System.Runtime.TieredCompilation.QuickJit": true
++      "System.Runtime.TieredCompilation.QuickJit": true,
++      "System.Globalization.Invariant": true
+     }
+   }
+-}
+\ No newline at end of file
++}
+ICU_PATCH
+```
+
+And now patch the github action runner:
+
+```
+cd ${HOME}/actions-runner
+bash patch.sh
+```
+
+```
+patching file bin/Runner.Listener.runtimeconfig.json
+patching file bin/Runner.PluginHost.runtimeconfig.json
+patching file bin/Runner.Worker.runtimeconfig.json
+```
+
+And now configure:
+
+```
+sudo yum install -y wget
+INSTANCE_ID=$(wget -q -O - http://169.254.169.254/latest/meta-data/instance-id)
+echo ${INSTANCE_ID}
+
+# get token from https://github.com/etcd-io/etcd/settings/actions/runners/new?arch=arm64&os=linux
+cd ${HOME}/actions-runner
+./config.sh \
+--work "_work" \
+--name ${INSTANCE_ID} \
+--labels self-hosted,linux,ARM64,graviton2 \
+--url https://github.com/etcd-io/etcd \
+--token ...
+```
+
+And run:
+
+```
+# run this as a process in the terminal
+cd ${HOME}/actions-runner
+./run.sh
+
+# or run this as a systemd service
+cd ${HOME}/actions-runner
+sudo ./svc.sh install
+sudo ./svc.sh start
+sudo ./svc.sh status
+```
+
+### Step 4. Create github action configuration
+
+See https://github.com/etcd-io/etcd/pull/12928.
+

.github/workflows/tests.yaml

@@ -0,0 +1,60 @@
+name: Tests
+on: [push, pull_request]
+jobs:
+  test:
+    runs-on: ubuntu-latest
+    strategy:
+      fail-fast: false
+      matrix:
+        target:
+        - linux-amd64-fmt
+        - linux-amd64-integration-1-cpu
+        - linux-amd64-integration-2-cpu
+        - linux-amd64-integration-4-cpu
+        - linux-amd64-unit-4-cpu-race
+        - all-build
+        - linux-386-unit-1-cpu
+    steps:
+    - uses: actions/checkout@v2
+    - uses: actions/setup-go@v2
+      with:
+        go-version: "^1.16"
+    - run: date
+    - env:
+        TARGET: ${{ matrix.target }}
+      run: |
+        echo "${TARGET}"
+        case "${TARGET}" in
+          linux-amd64-fmt)
+            GOARCH=amd64 PASSES='fmt bom dep' ./test.sh
+            ;;
+          linux-amd64-integration-1-cpu)
+            GOARCH=amd64 CPU=1 PASSES='integration' RACE='false' ./test.sh
+            ;;
+          linux-amd64-integration-2-cpu)
+            GOARCH=amd64 CPU=2 PASSES='integration' RACE='false' ./test.sh
+            ;;
+          linux-amd64-integration-4-cpu)
+            GOARCH=amd64 CPU=4 PASSES='integration' RACE='false' ./test.sh
+            ;;
+          linux-amd64-unit-4-cpu-race)
+            GOARCH=amd64 PASSES='unit' RACE='true' CPU='4' ./test.sh -p=2
+            ;;
+          all-build)
+            GOARCH=amd64 PASSES='build' ./test.sh
+            GOARCH=386 PASSES='build' ./test.sh
+            GO_BUILD_FLAGS='-v -mod=readonly' GOOS=darwin GOARCH=amd64 ./build.sh
+            GO_BUILD_FLAGS='-v -mod=readonly' GOOS=windows GOARCH=amd64 ./build.sh
+            GO_BUILD_FLAGS='-v -mod=readonly' GOARCH=arm ./build.sh
+            GO_BUILD_FLAGS='-v -mod=readonly' GOARCH=arm64 ./build.sh
+            GO_BUILD_FLAGS='-v -mod=readonly' GOARCH=ppc64le ./build.sh
+            GO_BUILD_FLAGS='-v -mod=readonly' GOARCH=s390x ./build.sh
+            ;;
+          linux-386-unit-1-cpu)
+            GOARCH=386 PASSES='unit' RACE='false' CPU='1' ./test -p=4
+            ;;
+          *)
+            echo "Failed to find target"
+            exit 1
+            ;;
+        esac

.gitignore

@@ -7,6 +7,7 @@
 /bin
 *.etcd
 *.log
+*.swp
 /etcd
 /hack/insta-discovery/.env
 *.coverprofile
@@ -15,22 +16,8 @@ hack/tls-setup/certs
 .idea
 /contrib/raftexample/raftexample
 /contrib/raftexample/raftexample-*
-
-# TODO: use dep prune
-# https://github.com/golang/dep/issues/120#issuecomment-306518546
-vendor/**/*
-!vendor/**/
-!vendor/**/*.go
-!vendor/**/*.c
-!vendor/**/*.cpp
-!vendor/**/*.s
-!vendor/**/COPYING*
-!vendor/**/PATENTS*
-!vendor/**/NOTICE*
-!vendor/**/Licence*
-!vendor/**/License*
-!vendor/**/LICENCE*
-!vendor/**/LICENSE*
-vendor/**/*_test.go
-
+/vendor
+/tests/e2e/default.proxy
+*.tmp
 *.bak
+.gobincache/

.travis.yml

@@ -1,13 +1,13 @@
 language: go
-go_import_path: go.etcd.io/etcd
+go_import_path: go.etcd.io/etcd/v3
 
 sudo: required
 
 services: docker
 
 go:
-- 1.12.7
-- tip
+  - "1.16.3"
+  - tip
 
 notifications:
   on_success: never
@@ -15,118 +15,37 @@ notifications:
 
 env:
   matrix:
-  - TARGET=linux-amd64-fmt
-  - TARGET=linux-amd64-integration-1-cpu
-  - TARGET=linux-amd64-integration-2-cpu
-  - TARGET=linux-amd64-integration-4-cpu
-  - TARGET=linux-amd64-functional
-  - TARGET=linux-amd64-unit
-  - TARGET=all-build
-  - TARGET=linux-amd64-grpcproxy
-  - TARGET=linux-amd64-coverage
-  - TARGET=linux-amd64-fmt-unit-go-tip
-  - TARGET=linux-386-unit
+    - TARGET=linux-amd64-coverage
+    - TARGET=linux-amd64-fmt-unit-go-tip-2-cpu
 
 matrix:
   fast_finish: true
   allow_failures:
-  - go: 1.12.7
-    env: TARGET=linux-amd64-integration-4-cpu
-  - go: 1.12.7
-    env: TARGET=linux-amd64-grpcproxy
-  - go: 1.12.7
-    env: TARGET=linux-amd64-coverage
-  - go: tip
-    env: TARGET=linux-amd64-fmt-unit-go-tip
-  - go: 1.12.7
-    env: TARGET=linux-386-unit
+    - go: "1.16.3"
+      env: TARGET=linux-amd64-coverage
+    - go: tip
+      env: TARGET=linux-amd64-fmt-unit-go-tip-2-cpu
   exclude:
-  - go: tip
-    env: TARGET=linux-amd64-fmt
-  - go: tip
-    env: TARGET=linux-amd64-integration-1-cpu
-  - go: tip
-    env: TARGET=linux-amd64-integration-2-cpu
-  - go: tip
-    env: TARGET=linux-amd64-integration-4-cpu
-  - go: tip
-    env: TARGET=linux-amd64-functional
-  - go: tip
-    env: TARGET=linux-amd64-unit
-  - go: tip
-    env: TARGET=all-build
-  - go: tip
-    env: TARGET=linux-amd64-grpcproxy
-  - go: tip
-    env: TARGET=linux-amd64-coverage
-  - go: 1.12.7
-    env: TARGET=linux-amd64-fmt-unit-go-tip
-  - go: tip
-    env: TARGET=linux-386-unit
+    - go: tip
+      env: TARGET=linux-amd64-coverage
+    - go: "1.16.3"
+      env: TARGET=linux-amd64-fmt-unit-go-tip-2-cpu
 
 before_install:
-- if [[ $TRAVIS_GO_VERSION == 1.* ]]; then docker pull gcr.io/etcd-development/etcd-test:go${TRAVIS_GO_VERSION}; fi
+  - if [[ $TRAVIS_GO_VERSION == 1.* ]]; then docker pull gcr.io/etcd-development/etcd-test:go${TRAVIS_GO_VERSION}; fi
 
 install:
-- go get -t -v -d ./...
+  - date
 
 script:
- - echo "TRAVIS_GO_VERSION=${TRAVIS_GO_VERSION}"
- - >
+  - date
+  - echo "TRAVIS_GO_VERSION=${TRAVIS_GO_VERSION}"
+  - >
     case "${TARGET}" in
-      linux-amd64-fmt)
-        docker run --rm \
-          --volume=`pwd`:/go/src/go.etcd.io/etcd gcr.io/etcd-development/etcd-test:go${TRAVIS_GO_VERSION} \
-          /bin/bash -c "GOARCH=amd64 PASSES='fmt bom dep' ./test"
-        ;;
-      linux-amd64-integration-1-cpu)
-        docker run --rm \
-          --volume=`pwd`:/go/src/go.etcd.io/etcd gcr.io/etcd-development/etcd-test:go${TRAVIS_GO_VERSION} \
-          /bin/bash -c "GOARCH=amd64 CPU=1 PASSES='integration' ./test"
-        ;;
-      linux-amd64-integration-2-cpu)
-        docker run --rm \
-          --volume=`pwd`:/go/src/go.etcd.io/etcd gcr.io/etcd-development/etcd-test:go${TRAVIS_GO_VERSION} \
-          /bin/bash -c "GOARCH=amd64 CPU=2 PASSES='integration' ./test"
-        ;;
-      linux-amd64-integration-4-cpu)
-        docker run --rm \
-          --volume=`pwd`:/go/src/go.etcd.io/etcd gcr.io/etcd-development/etcd-test:go${TRAVIS_GO_VERSION} \
-          /bin/bash -c "GOARCH=amd64 CPU=4 PASSES='integration' ./test"
-        ;;
-      linux-amd64-functional)
-        docker run --rm \
-          --volume=`pwd`:/go/src/go.etcd.io/etcd gcr.io/etcd-development/etcd-test:go${TRAVIS_GO_VERSION} \
-          /bin/bash -c "./build && GOARCH=amd64 PASSES='functional' ./test"
-        ;;
-      linux-amd64-unit)
-        docker run --rm \
-          --volume=`pwd`:/go/src/go.etcd.io/etcd gcr.io/etcd-development/etcd-test:go${TRAVIS_GO_VERSION} \
-          /bin/bash -c "GOARCH=amd64 PASSES='unit' ./test"
-        ;;
-      all-build)
-        docker run --rm \
-          --volume=`pwd`:/go/src/go.etcd.io/etcd gcr.io/etcd-development/etcd-test:go${TRAVIS_GO_VERSION} \
-          /bin/bash -c "GOARCH=amd64 PASSES='build' ./test \
-            && GOARCH=386 PASSES='build' ./test \
-            && GO_BUILD_FLAGS='-v' GOOS=darwin GOARCH=amd64 ./build \
-            && GO_BUILD_FLAGS='-v' GOOS=windows GOARCH=amd64 ./build \
-            && GO_BUILD_FLAGS='-v' GOARCH=arm ./build \
-            && GO_BUILD_FLAGS='-v' GOARCH=arm64 ./build \
-            && GO_BUILD_FLAGS='-v' GOARCH=ppc64le ./build"
-        ;;
-      linux-amd64-grpcproxy)
-        sudo HOST_TMP_DIR=/tmp TEST_OPTS="PASSES='build grpcproxy'" make docker-test
-        ;;
       linux-amd64-coverage)
-        sudo HOST_TMP_DIR=/tmp make docker-test-coverage
+        sudo HOST_TMP_DIR=/tmp TEST_OPTS="VERBOSE='1'" make docker-test-coverage
         ;;
-      linux-amd64-fmt-unit-go-tip)
-        GOARCH=amd64 PASSES='fmt unit' ./test
-        ;;
-      linux-386-unit)
-        docker run --rm \
-          --volume=`pwd`:/go/src/go.etcd.io/etcd gcr.io/etcd-development/etcd-test:go${TRAVIS_GO_VERSION} \
-          /bin/bash -c "GOARCH=386 PASSES='unit' ./test"
+      linux-amd64-fmt-unit-go-tip-2-cpu)
+        GOARCH=amd64 PASSES='fmt unit' CPU='2' RACE='false' ./test.sh -p=2
         ;;
     esac

.words

@@ -1,109 +1,116 @@
-DefaultMaxRequestBytes
-ErrCodeEnhanceYourCalm
-ErrTimeout
-GoAway
-KeepAlive
-Keepalive
-MiB
-ResourceExhausted
-RPC
-RPCs
-parsedTarget
-SRV
-WithRequireLeader
-InfoLevel
+accessors
+addrConns
 args
+atomics
 backoff
+BackoffFunc
+BackoffLinearWithJitter
+Balancer
+BidiStreams
 blackhole
 blackholed
+CallOptions
 cancelable
 cancelation
+ccBalancerWrapper
+clientURLs
+clusterName
 cluster_proxy
+consistentIndex
+ConsistentIndexGetter
+DefaultMaxRequestBytes
 defragment
 defragmenting
 deleter
 dev
 /dev/null
 dev/null
+DNS
 errClientDisconnected
+ErrCodeEnhanceYourCalm
+ErrConnClosing
+ErrRequestTooLarge
+ErrTimeout
 etcd
-gRPC
+FIXME
+github
+GoAway
 goroutine
 goroutines
+gRPC
+grpcAddr
+hasleader
 healthcheck
 hostname
 iff
 inflight
+InfoLevel
+jitter
+jitter
+jitter
 keepalive
+Keepalive
+KeepAlive
 keepalives
 keyspace
+lexically
+lexicographically
+linearizable
 linearization
-liveness
 linearized
+liveness
 localhost
+__lostleader
+MaxRequestBytes
+MiB
+middleware
+mutators
 mutex
+nils
+nondeterministically
+nop
+OutputWALDir
+parsedTarget
+passthrough
+PermitWithoutStream
 prefetching
-protobuf
 prometheus
+protobuf
+racey
 rafthttp
+rebalanced
+reconnection
 repin
+ResourceExhausted
+retriable
+retriable
 rpc
+RPC
+RPCs
+saveWALAndSnap
 serializable
+ServerStreams
+SHA
+SRV
 statusError
+subConn
+subconns
+SubConns
 teardown
+TestBalancerDoNotBlockOnClose
+todo
 too_many_pings
 transactional
-uncontended
-unprefixed
-unlisting
-nondeterministically
-atomics
 transferee
-Balancer
-lexicographically
-lexically
-accessors
-unbuffered
-nils
-reconnection
-mutators
-ConsistentIndexGetter
-OutputWALDir
-WAL
-consistentIndex
-todo
-saveWALAndSnap
-
-subconns
-nop
-SubConns
-DNS
-passthrough
-ccBalancerWrapper
-rebalanced
-addrConns
-subConn
-TestBalancerDoNotBlockOnClose
-middleware
-clusterName
-jitter
-FIXME
-retriable
-github
-retriable
-jitter
-WithBackoff
-BackoffLinearWithJitter
-jitter
-WithMax
-ServerStreams
-BidiStreams
 transientFailure
-BackoffFunc
-CallOptions
-PermitWithoutStream
-__lostleader
-ErrConnClosing
+unbuffered
+uncontended
 unfreed
-grpcAddr
-clientURLs
+unlisting
+unprefixed
+WatchProgressNotifyInterval
+WAL
+WithBackoff
+WithDialer
+WithMax
+WithRequireLeader

CHANGELOG-2.3.md

@@ -1,16 +0,0 @@
-
-
-<hr>
-
-
-## [v2.3.8](https://github.com/etcd-io/etcd/releases/tag/v2.3.8) (2017-02-17)
-
-See [code changes](https://github.com/etcd-io/etcd/compare/v2.3.7...v2.3.8).
-
-### Go
-
-- Compile with [*Go 1.7.5*](https://golang.org/doc/devel/release.html#go1.7).
-
-
-<hr>
-

CHANGELOG-3.0.md

@@ -1,291 +0,0 @@
-
-
-<hr>
-
-
-## [v3.0.16](https://github.com/etcd-io/etcd/releases/tag/v3.0.16) (2016-11-13)
-
-See [code changes](https://github.com/etcd-io/etcd/compare/v3.0.15...v3.0.16) and [v3.0 upgrade guide](https://github.com/etcd-io/etcd/blob/master/Documentation/upgrades/upgrade_3_0.md) for any breaking changes.
-
-**Again, before running upgrades from any previous release, please make sure to read change logs below and [v3.0 upgrade guide](https://github.com/etcd-io/etcd/blob/master/Documentation/upgrades/upgrade_3_0.md).**
-
-### Go
-
-- Compile with [*Go 1.6.4*](https://golang.org/doc/devel/release.html#go1.6).
-
-
-<hr>
-
-
-## [v3.0.15](https://github.com/etcd-io/etcd/releases/tag/v3.0.15) (2016-11-11)
-
-See [code changes](https://github.com/etcd-io/etcd/compare/v3.0.14...v3.0.15) and [v3.0 upgrade guide](https://github.com/etcd-io/etcd/blob/master/Documentation/upgrades/upgrade_3_0.md) for any breaking changes.
-
-**Again, before running upgrades from any previous release, please make sure to read change logs below and [v3.0 upgrade guide](https://github.com/etcd-io/etcd/blob/master/Documentation/upgrades/upgrade_3_0.md).**
-
-### Fixed
-
-- Fix cancel watch request with wrong range end.
-
-### Go
-
-- Compile with [*Go 1.6.3*](https://golang.org/doc/devel/release.html#go1.6).
-
-
-<hr>
-
-
-## [v3.0.14](https://github.com/etcd-io/etcd/releases/tag/v3.0.14) (2016-11-04)
-
-See [code changes](https://github.com/etcd-io/etcd/compare/v3.0.13...v3.0.14) and [v3.0 upgrade guide](https://github.com/etcd-io/etcd/blob/master/Documentation/upgrades/upgrade_3_0.md) for any breaking changes.
-
-**Again, before running upgrades from any previous release, please make sure to read change logs below and [v3.0 upgrade guide](https://github.com/etcd-io/etcd/blob/master/Documentation/upgrades/upgrade_3_0.md).**
-
-### Added
-
-- v3 `etcdctl migrate` command now supports `--no-ttl` flag to discard keys on transform.
-
-### Go
-
-- Compile with [*Go 1.6.3*](https://golang.org/doc/devel/release.html#go1.6).
-
-
-<hr>
-
-
-## [v3.0.13](https://github.com/etcd-io/etcd/releases/tag/v3.0.13) (2016-10-24)
-
-See [code changes](https://github.com/etcd-io/etcd/compare/v3.0.12...v3.0.13) and [v3.0 upgrade guide](https://github.com/etcd-io/etcd/blob/master/Documentation/upgrades/upgrade_3_0.md) for any breaking changes.
-
-**Again, before running upgrades from any previous release, please make sure to read change logs below and [v3.0 upgrade guide](https://github.com/etcd-io/etcd/blob/master/Documentation/upgrades/upgrade_3_0.md).**
-
-### Go
-
-- Compile with [*Go 1.6.3*](https://golang.org/doc/devel/release.html#go1.6).
-
-
-<hr>
-
-
-## [v3.0.12](https://github.com/etcd-io/etcd/releases/tag/v3.0.12) (2016-10-07)
-
-See [code changes](https://github.com/etcd-io/etcd/compare/v3.0.11...v3.0.12) and [v3.0 upgrade guide](https://github.com/etcd-io/etcd/blob/master/Documentation/upgrades/upgrade_3_0.md) for any breaking changes.
-
-**Again, before running upgrades from any previous release, please make sure to read change logs below and [v3.0 upgrade guide](https://github.com/etcd-io/etcd/blob/master/Documentation/upgrades/upgrade_3_0.md).**
-
-### Go
-
-- Compile with [*Go 1.6.3*](https://golang.org/doc/devel/release.html#go1.6).
-
-
-<hr>
-
-
-## [v3.0.11](https://github.com/etcd-io/etcd/releases/tag/v3.0.11) (2016-10-07)
-
-See [code changes](https://github.com/etcd-io/etcd/compare/v3.0.10...v3.0.11) and [v3.0 upgrade guide](https://github.com/etcd-io/etcd/blob/master/Documentation/upgrades/upgrade_3_0.md) for any breaking changes.
-
-**Again, before running upgrades from any previous release, please make sure to read change logs below and [v3.0 upgrade guide](https://github.com/etcd-io/etcd/blob/master/Documentation/upgrades/upgrade_3_0.md).**
-
-### Added
-
-- Server returns previous key-value (optional)
-  - `clientv3.WithPrevKV` option
-  - v3 etcdctl `put,watch,del --prev-kv` flag
-
-### Go
-
-- Compile with [*Go 1.6.3*](https://golang.org/doc/devel/release.html#go1.6).
-
-
-<hr>
-
-
-## [v3.0.10](https://github.com/etcd-io/etcd/releases/tag/v3.0.10) (2016-09-23)
-
-See [code changes](https://github.com/etcd-io/etcd/compare/v3.0.9...v3.0.10) and [v3.0 upgrade guide](https://github.com/etcd-io/etcd/blob/master/Documentation/upgrades/upgrade_3_0.md) for any breaking changes.
-
-**Again, before running upgrades from any previous release, please make sure to read change logs below and [v3.0 upgrade guide](https://github.com/etcd-io/etcd/blob/master/Documentation/upgrades/upgrade_3_0.md).**
-
-### Go
-
-- Compile with [*Go 1.6.3*](https://golang.org/doc/devel/release.html#go1.6).
-
-
-<hr>
-
-
-## [v3.0.9](https://github.com/etcd-io/etcd/releases/tag/v3.0.9) (2016-09-15)
-
-See [code changes](https://github.com/etcd-io/etcd/compare/v3.0.8...v3.0.9) and [v3.0 upgrade guide](https://github.com/etcd-io/etcd/blob/master/Documentation/upgrades/upgrade_3_0.md) for any breaking changes.
-
-**Again, before running upgrades from any previous release, please make sure to read change logs below and [v3.0 upgrade guide](https://github.com/etcd-io/etcd/blob/master/Documentation/upgrades/upgrade_3_0.md).**
-
-### Added
-
-- Warn on domain names on listen URLs (v3.2 will reject domain names).
-
-### Go
-
-- Compile with [*Go 1.6.3*](https://golang.org/doc/devel/release.html#go1.6).
-
-
-<hr>
-
-
-## [v3.0.8](https://github.com/etcd-io/etcd/releases/tag/v3.0.8) (2016-09-09)
-
-See [code changes](https://github.com/etcd-io/etcd/compare/v3.0.7...v3.0.8) and [v3.0 upgrade guide](https://github.com/etcd-io/etcd/blob/master/Documentation/upgrades/upgrade_3_0.md) for any breaking changes.
-
-**Again, before running upgrades from any previous release, please make sure to read change logs below and [v3.0 upgrade guide](https://github.com/etcd-io/etcd/blob/master/Documentation/upgrades/upgrade_3_0.md).**
-
-### Other
-
-- Allow only IP addresses in listen URLs (domain names are rejected).
-
-### Go
-
-- Compile with [*Go 1.6.3*](https://golang.org/doc/devel/release.html#go1.6).
-
-
-<hr>
-
-
-## [v3.0.7](https://github.com/etcd-io/etcd/releases/tag/v3.0.7) (2016-08-31)
-
-See [code changes](https://github.com/etcd-io/etcd/compare/v3.0.6...v3.0.7) and [v3.0 upgrade guide](https://github.com/etcd-io/etcd/blob/master/Documentation/upgrades/upgrade_3_0.md) for any breaking changes.
-
-**Again, before running upgrades from any previous release, please make sure to read change logs below and [v3.0 upgrade guide](https://github.com/etcd-io/etcd/blob/master/Documentation/upgrades/upgrade_3_0.md).**
-
-### Other
-
-- SRV records only allow A records (RFC 2052).
-
-### Go
-
-- Compile with [*Go 1.6.3*](https://golang.org/doc/devel/release.html#go1.6).
-
-
-<hr>
-
-
-## [v3.0.6](https://github.com/etcd-io/etcd/releases/tag/v3.0.6) (2016-08-19)
-
-See [code changes](https://github.com/etcd-io/etcd/compare/v3.0.5...v3.0.6) and [v3.0 upgrade guide](https://github.com/etcd-io/etcd/blob/master/Documentation/upgrades/upgrade_3_0.md) for any breaking changes.
-
-**Again, before running upgrades from any previous release, please make sure to read change logs below and [v3.0 upgrade guide](https://github.com/etcd-io/etcd/blob/master/Documentation/upgrades/upgrade_3_0.md).**
-
-### Go
-
-- Compile with [*Go 1.6.3*](https://golang.org/doc/devel/release.html#go1.6).
-
-
-<hr>
-
-
-## [v3.0.5](https://github.com/etcd-io/etcd/releases/tag/v3.0.5) (2016-08-19)
-
-See [code changes](https://github.com/etcd-io/etcd/compare/v3.0.4...v3.0.5) and [v3.0 upgrade guide](https://github.com/etcd-io/etcd/blob/master/Documentation/upgrades/upgrade_3_0.md) for any breaking changes.
-
-**Again, before running upgrades from any previous release, please make sure to read change logs below and [v3.0 upgrade guide](https://github.com/etcd-io/etcd/blob/master/Documentation/upgrades/upgrade_3_0.md).**
-
-### Other
-
-- SRV records (e.g., infra1.example.com) must match the discovery domain (i.e., example.com) if no custom certificate authority is given.
-
-### Go
-
-- Compile with [*Go 1.6.3*](https://golang.org/doc/devel/release.html#go1.6).
-
-
-<hr>
-
-
-## [v3.0.4](https://github.com/etcd-io/etcd/releases/tag/v3.0.4) (2016-07-27)
-
-See [code changes](https://github.com/etcd-io/etcd/compare/v3.0.3...v3.0.4) and [v3.0 upgrade guide](https://github.com/etcd-io/etcd/blob/master/Documentation/upgrades/upgrade_3_0.md) for any breaking changes.
-
-**Again, before running upgrades from any previous release, please make sure to read change logs below and [v3.0 upgrade guide](https://github.com/etcd-io/etcd/blob/master/Documentation/upgrades/upgrade_3_0.md).**
-
-### Added
-
-- v2 `etcdctl ls` command now supports `--output=json`.
-- Add /var/lib/etcd directory to etcd official Docker image.
-
-### Other
-
-- v2 auth can now use common name from TLS certificate when `--client-cert-auth` is enabled.
-
-### Go
-
-- Compile with [*Go 1.6.3*](https://golang.org/doc/devel/release.html#go1.6).
-
-
-<hr>
-
-
-## [v3.0.3](https://github.com/etcd-io/etcd/releases/tag/v3.0.3) (2016-07-15)
-
-See [code changes](https://github.com/etcd-io/etcd/compare/v3.0.2...v3.0.3) and [v3.0 upgrade guide](https://github.com/etcd-io/etcd/blob/master/Documentation/upgrades/upgrade_3_0.md) for any breaking changes.
-
-**Again, before running upgrades from any previous release, please make sure to read change logs below and [v3.0 upgrade guide](https://github.com/etcd-io/etcd/blob/master/Documentation/upgrades/upgrade_3_0.md).**
-
-### Other
-
-- Revert Dockerfile to use `CMD`, instead of `ENTRYPOINT`, to support `etcdctl` run.
-  - Docker commands for v3.0.2 won't work without specifying executable binary paths.
-- v3 etcdctl default endpoints are now `127.0.0.1:2379`.
-
-### Go
-
-- Compile with [*Go 1.6.2*](https://golang.org/doc/devel/release.html#go1.6).
-
-
-<hr>
-
-
-## [v3.0.2](https://github.com/etcd-io/etcd/releases/tag/v3.0.2) (2016-07-08)
-
-See [code changes](https://github.com/etcd-io/etcd/compare/v3.0.1...v3.0.2) and [v3.0 upgrade guide](https://github.com/etcd-io/etcd/blob/master/Documentation/upgrades/upgrade_3_0.md) for any breaking changes.
-
-**Again, before running upgrades from any previous release, please make sure to read change logs below and [v3.0 upgrade guide](https://github.com/etcd-io/etcd/blob/master/Documentation/upgrades/upgrade_3_0.md).**
-
-### Other
-
-- Dockerfile uses `ENTRYPOINT`, instead of `CMD`, to run etcd without binary path specified.
-
-### Go
-
-- Compile with [*Go 1.6.2*](https://golang.org/doc/devel/release.html#go1.6).
-
-
-<hr>
-
-
-## [v3.0.1](https://github.com/etcd-io/etcd/releases/tag/v3.0.1) (2016-07-01)
-
-See [code changes](https://github.com/etcd-io/etcd/compare/v3.0.0...v3.0.1) and [v3.0 upgrade guide](https://github.com/etcd-io/etcd/blob/master/Documentation/upgrades/upgrade_3_0.md) for any breaking changes.
-
-**Again, before running upgrades from any previous release, please make sure to read change logs below and [v3.0 upgrade guide](https://github.com/etcd-io/etcd/blob/master/Documentation/upgrades/upgrade_3_0.md).**
-
-### Go
-
-- Compile with [*Go 1.6.2*](https://golang.org/doc/devel/release.html#go1.6).
-
-
-<hr>
-
-
-## [v3.0.0](https://github.com/etcd-io/etcd/releases/tag/v3.0.0) (2016-06-30)
-
-See [code changes](https://github.com/etcd-io/etcd/compare/v2.3.0...v3.0.0) and [v3.0 upgrade guide](https://github.com/etcd-io/etcd/blob/master/Documentation/upgrades/upgrade_3_0.md) for any breaking changes.
-
-**Again, before running upgrades from any previous release, please make sure to read change logs below and [v3.0 upgrade guide](https://github.com/etcd-io/etcd/blob/master/Documentation/upgrades/upgrade_3_0.md).**
-
-### Go
-
-- Compile with [*Go 1.6.2*](https://golang.org/doc/devel/release.html#go1.6).
-
-
-<hr>
-

CHANGELOG-3.1.md

@@ -1,574 +0,0 @@
-
-
-Previous change logs can be found at [CHANGELOG-3.0](https://github.com/etcd-io/etcd/blob/master/CHANGELOG-3.0.md).
-
-
-The minimum recommended etcd versions to run in **production** are 3.1.11+, 3.2.26+, and 3.3.11+.
-
-
-<hr>
-
-## [v3.1.21](https://github.com/etcd-io/etcd/releases/tag/v3.1.21) (2019-TBD)
-
-### etcdctl
-
-- [Strip out insecure endpoints from DNS SRV records when using discovery](https://github.com/etcd-io/etcd/pull/10443) with etcdctl v2
-- Add [`etcdctl endpoint health --write-out` support](https://github.com/etcd-io/etcd/pull/9540).
-  - Previously, [`etcdctl endpoint health --write-out json` did not work](https://github.com/etcd-io/etcd/issues/9532).
-  - The command output is changed. Previously, if endpoint is unreachable, the command output is
-  "\<endpoint\> is unhealthy: failed to connect: \<error message\>". This change unified the error message, all error types
-  now have the same output "\<endpoint\> is unhealthy: failed to commit proposal: \<error message\>".
-
-### Metrics, Monitoring
-
-- Fix bug where [db_compaction_total_duration_milliseconds metric incorrectly measured duration as 0](https://github.com/etcd-io/etcd/pull/10646).
-
-<hr>
-
-## [v3.1.20](https://github.com/etcd-io/etcd/releases/tag/v3.1.20) (2018-10-10)
-
-See [code changes](https://github.com/etcd-io/etcd/compare/v3.1.19...v3.1.20) and [v3.1 upgrade guide](https://github.com/etcd-io/etcd/blob/master/Documentation/upgrades/upgrade_3_1.md) 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](https://github.com/etcd-io/etcd/blob/master/Documentation/upgrades/upgrade_3_1.md).**
-
-### Improved
-
-- Improve ["became inactive" warning log](https://github.com/etcd-io/etcd/pull/10024), which indicates message send to a peer failed.
-- Improve [read index wait timeout warning log](https://github.com/etcd-io/etcd/pull/10026), which indicates that local node might have slow network.
-- Add [gRPC interceptor for debugging logs](https://github.com/etcd-io/etcd/pull/9990); enable `etcd --debug` flag to see per-request debug information.
-- Add [consistency check in snapshot status](https://github.com/etcd-io/etcd/pull/10109). If consistency check on snapshot file fails, `snapshot status` returns `"snapshot file integrity check failed..."` error.
-
-### Metrics, Monitoring
-
-See [List of metrics](https://etcd.io/docs/v3.1.12/metrics/) for all metrics per release.
-
-Note that any `etcd_debugging_*` metrics are experimental and subject to change.
-
-- Improve [`etcd_network_peer_round_trip_time_seconds`](https://github.com/etcd-io/etcd/pull/10155) Prometheus metric to track leader heartbeats.
-  - Previously, it only samples the TCP connection for snapshot messages.
-- Display all registered [gRPC metrics at start](https://github.com/etcd-io/etcd/pull/10034).
-- Add [`etcd_snap_db_fsync_duration_seconds_count`](https://github.com/etcd-io/etcd/pull/9997) Prometheus metric.
-- Add [`etcd_snap_db_save_total_duration_seconds_bucket`](https://github.com/etcd-io/etcd/pull/9997) Prometheus metric.
-- Add [`etcd_network_snapshot_send_success`](https://github.com/etcd-io/etcd/pull/9997) Prometheus metric.
-- Add [`etcd_network_snapshot_send_failures`](https://github.com/etcd-io/etcd/pull/9997) Prometheus metric.
-- Add [`etcd_network_snapshot_send_total_duration_seconds`](https://github.com/etcd-io/etcd/pull/9997) Prometheus metric.
-- Add [`etcd_network_snapshot_receive_success`](https://github.com/etcd-io/etcd/pull/9997) Prometheus metric.
-- Add [`etcd_network_snapshot_receive_failures`](https://github.com/etcd-io/etcd/pull/9997) Prometheus metric.
-- Add [`etcd_network_snapshot_receive_total_duration_seconds`](https://github.com/etcd-io/etcd/pull/9997) Prometheus metric.
-- Add [`etcd_server_id`](https://github.com/etcd-io/etcd/pull/9998) Prometheus metric.
-- Add [`etcd_server_health_success`](https://github.com/etcd-io/etcd/pull/10156) Prometheus metric.
-- Add [`etcd_server_health_failures`](https://github.com/etcd-io/etcd/pull/10156) Prometheus metric.
-- Add [`etcd_server_read_indexes_failed_total`](https://github.com/etcd-io/etcd/pull/10094) Prometheus metric.
-
-### client v3
-
-- Fix logic on [release lock key if cancelled](https://github.com/etcd-io/etcd/pull/10153) in `clientv3/concurrency` package.
-
-### Go
-
-- Compile with [*Go 1.8.7*](https://golang.org/doc/devel/release.html#go1.8).
-
-
-<hr>
-
-
-## [v3.1.19](https://github.com/etcd-io/etcd/releases/tag/v3.1.19) (2018-07-24)
-
-See [code changes](https://github.com/etcd-io/etcd/compare/v3.1.18...v3.1.19) and [v3.1 upgrade guide](https://github.com/etcd-io/etcd/blob/master/Documentation/upgrades/upgrade_3_1.md) 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](https://github.com/etcd-io/etcd/blob/master/Documentation/upgrades/upgrade_3_1.md).**
-
-### Improved
-
-- Improve [Raft Read Index timeout warning messages](https://github.com/etcd-io/etcd/pull/9897).
-
-### Metrics, Monitoring
-
-See [List of metrics](https://etcd.io/docs/v3.1.12/metrics/) for all metrics per release.
-
-Note that any `etcd_debugging_*` metrics are experimental and subject to change.
-
-- Add [`etcd_server_go_version`](https://github.com/etcd-io/etcd/pull/9957) Prometheus metric.
-- Add [`etcd_server_slow_read_indexes_total`](https://github.com/etcd-io/etcd/pull/9897) Prometheus metric.
-- Add [`etcd_server_quota_backend_bytes`](https://github.com/etcd-io/etcd/pull/9820) Prometheus metric.
-  - Use it with `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.
-- Add [`etcd_mvcc_db_total_size_in_bytes`](https://github.com/etcd-io/etcd/pull/9819) Prometheus metric.
-  - In addition to [`etcd_debugging_mvcc_db_total_size_in_bytes`](https://github.com/etcd-io/etcd/pull/9819).
-- Add [`etcd_mvcc_db_total_size_in_use_in_bytes`](https://github.com/etcd-io/etcd/pull/9256) Prometheus metric.
-  - Use it with `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.
-
-### client v3
-
-- Fix [lease keepalive interval updates when response queue is full](https://github.com/etcd-io/etcd/pull/9952).
-  - If `<-chan *clientv3LeaseKeepAliveResponse` from `clientv3.Lease.KeepAlive` was never consumed or channel is full, client was [sending keepalive request every 500ms](https://github.com/etcd-io/etcd/issues/9911) instead of expected rate of every "TTL / 3" duration.
-
-### Go
-
-- Compile with [*Go 1.8.7*](https://golang.org/doc/devel/release.html#go1.8).
-
-
-<hr>
-
-
-## [v3.1.18](https://github.com/etcd-io/etcd/releases/tag/v3.1.18) (2018-06-15)
-
-See [code changes](https://github.com/etcd-io/etcd/compare/v3.1.17...v3.1.18) and [v3.1 upgrade guide](https://github.com/etcd-io/etcd/blob/master/Documentation/upgrades/upgrade_3_1.md) 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](https://github.com/etcd-io/etcd/blob/master/Documentation/upgrades/upgrade_3_1.md).**
-
-### Metrics, Monitoring
-
-See [List of metrics](https://etcd.io/docs/v3.1.12/metrics/) for all metrics per release.
-
-Note that any `etcd_debugging_*` metrics are experimental and subject to change.
-
-- Add [`etcd_server_version`](https://github.com/etcd-io/etcd/pull/8960) Prometheus metric.
-  - To replace [Kubernetes `etcd-version-monitor`](https://github.com/etcd-io/etcd/issues/8948).
-
-### Go
-
-- Compile with [*Go 1.8.7*](https://golang.org/doc/devel/release.html#go1.8).
-
-
-<hr>
-
-
-## [v3.1.17](https://github.com/etcd-io/etcd/releases/tag/v3.1.17) (2018-06-06)
-
-See [code changes](https://github.com/etcd-io/etcd/compare/v3.1.16...v3.1.17) and [v3.1 upgrade guide](https://github.com/etcd-io/etcd/blob/master/Documentation/upgrades/upgrade_3_1.md) 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](https://github.com/etcd-io/etcd/blob/master/Documentation/upgrades/upgrade_3_1.md).**
-
-### etcd server
-
-- Fix [v3 snapshot recovery](https://github.com/etcd-io/etcd/issues/7628).
-  - A follower receives a leader snapshot to be persisted as a `[SNAPSHOT-INDEX].snap.db` file on disk.
-  - Now, server [ensures that the incoming snapshot be persisted on disk before loading it](https://github.com/etcd-io/etcd/pull/7876).
-  - Otherwise, index mismatch happens and triggers server-side panic (e.g. newer WAL entry with outdated snapshot index).
-
-### Go
-
-- Compile with [*Go 1.8.7*](https://golang.org/doc/devel/release.html#go1.8).
-
-
-<hr>
-
-
-## [v3.1.16](https://github.com/etcd-io/etcd/releases/tag/v3.1.16) (2018-05-31)
-
-See [code changes](https://github.com/etcd-io/etcd/compare/v3.1.15...v3.1.16) and [v3.1 upgrade guide](https://github.com/etcd-io/etcd/blob/master/Documentation/upgrades/upgrade_3_1.md) 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](https://github.com/etcd-io/etcd/blob/master/Documentation/upgrades/upgrade_3_1.md).**
-
-### etcd server
-
-- Fix [`mvcc` server panic from restore operation](https://github.com/etcd-io/etcd/pull/9775).
-  - Let's assume that a watcher had been requested with a future revision X and sent to node A that became network-partitioned thereafter. Meanwhile, cluster makes progress. Then when the partition gets removed, the leader sends a snapshot to node A. Previously if the snapshot's latest revision is still lower than the watch revision X,  **etcd server panicked** during snapshot restore operation.
-  - Now, this server-side panic has been fixed.
-
-### Go
-
-- Compile with [*Go 1.8.7*](https://golang.org/doc/devel/release.html#go1.8).
-
-
-<hr>
-
-
-## [v3.1.15](https://github.com/etcd-io/etcd/releases/tag/v3.1.15) (2018-05-09)
-
-See [code changes](https://github.com/etcd-io/etcd/compare/v3.1.14...v3.1.15) and [v3.1 upgrade guide](https://github.com/etcd-io/etcd/blob/master/Documentation/upgrades/upgrade_3_1.md) 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](https://github.com/etcd-io/etcd/blob/master/Documentation/upgrades/upgrade_3_1.md).**
-
-### etcd server
-
-- Purge old [`*.snap.db` snapshot files](https://github.com/etcd-io/etcd/pull/7967).
-  - Previously, etcd did not respect `--max-snapshots` flag to purge old `*.snap.db` files.
-  - Now, etcd purges old `*.snap.db` files to keep maximum `--max-snapshots` number of files on disk.
-
-### Go
-
-- Compile with [*Go 1.8.7*](https://golang.org/doc/devel/release.html#go1.8).
-
-
-<hr>
-
-
-## [v3.1.14](https://github.com/etcd-io/etcd/releases/tag/v3.1.14) (2018-04-24)
-
-See [code changes](https://github.com/etcd-io/etcd/compare/v3.1.13...v3.1.14) and [v3.1 upgrade guide](https://github.com/etcd-io/etcd/blob/master/Documentation/upgrades/upgrade_3_1.md) 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](https://github.com/etcd-io/etcd/blob/master/Documentation/upgrades/upgrade_3_1.md).**
-
-### Metrics, Monitoring
-
-See [List of metrics](https://etcd.io/docs/v3.1.12/metrics/) for all metrics per release.
-
-Note that any `etcd_debugging_*` metrics are experimental and subject to change.
-
-- Add [`etcd_server_is_leader`](https://github.com/etcd-io/etcd/pull/9587) Prometheus metric.
-
-### etcd server
-
-- Add [`--initial-election-tick-advance`](https://github.com/etcd-io/etcd/pull/9591) flag to configure initial election tick fast-forward.
-  - By default, `--initial-election-tick-advance=true`, then local member fast-forwards election ticks to speed up "initial" leader election trigger.
-  - This benefits the case of larger election ticks. For instance, cross datacenter deployment may require longer election timeout of 10-second. If true, local node does not need wait up to 10-second. Instead, forwards its election ticks to 8-second, and have only 2-second left before leader election.
-  - Major assumptions are that: cluster has no active leader thus advancing ticks enables faster leader election. Or cluster already has an established leader, and rejoining follower is likely to receive heartbeats from the leader after tick advance and before election timeout.
-  - However, when network from leader to rejoining follower is congested, and the follower does not receive leader heartbeat within left election ticks, disruptive election has to happen thus affecting cluster availabilities.
-  - Now, this can be disabled by setting `--initial-election-tick-advance=false`.
-  - Disabling this would slow down initial bootstrap process for cross datacenter deployments. Make tradeoffs by configuring `--initial-election-tick-advance` at the cost of slow initial bootstrap.
-  - If single-node, it advances ticks regardless.
-  - Address [disruptive rejoining follower node](https://github.com/etcd-io/etcd/issues/9333).
-
-### Go
-
-- Compile with [*Go 1.8.7*](https://golang.org/doc/devel/release.html#go1.8).
-
-
-<hr>
-
-
-## [v3.1.13](https://github.com/etcd-io/etcd/releases/tag/v3.1.13) (2018-03-29)
-
-See [code changes](https://github.com/etcd-io/etcd/compare/v3.1.12...v3.1.13) and [v3.1 upgrade guide](https://github.com/etcd-io/etcd/blob/master/Documentation/upgrades/upgrade_3_1.md) 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](https://github.com/etcd-io/etcd/blob/master/Documentation/upgrades/upgrade_3_1.md).**
-
-### Improved
-
-- Adjust [election timeout on server restart](https://github.com/etcd-io/etcd/pull/9415) to reduce [disruptive rejoining servers](https://github.com/etcd-io/etcd/issues/9333).
-  - Previously, etcd fast-forwards election ticks on server start, with only one tick left for leader election. This is to speed up start phase, without having to wait until all election ticks elapse. Advancing election ticks is useful for cross datacenter deployments with larger election timeouts. However, it was affecting cluster availability if the last tick elapses before leader contacts the restarted node.
-  - Now, when etcd restarts, it adjusts election ticks with more than one tick left, thus more time for leader to prevent disruptive restart.
-
-### Metrics, Monitoring
-
-See [List of metrics](https://etcd.io/docs/v3.1.12/metrics/) for all metrics per release.
-
-Note that any `etcd_debugging_*` metrics are experimental and subject to change.
-
-- Add missing [`etcd_network_peer_sent_failures_total` count](https://github.com/etcd-io/etcd/pull/9437).
-
-### Go
-
-- Compile with [*Go 1.8.7*](https://golang.org/doc/devel/release.html#go1.8).
-
-
-<hr>
-
-
-## [v3.1.12](https://github.com/etcd-io/etcd/releases/tag/v3.1.12) (2018-03-08)
-
-See [code changes](https://github.com/etcd-io/etcd/compare/v3.1.11...v3.1.12) and [v3.1 upgrade guide](https://github.com/etcd-io/etcd/blob/master/Documentation/upgrades/upgrade_3_1.md) 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](https://github.com/etcd-io/etcd/blob/master/Documentation/upgrades/upgrade_3_1.md).**
-
-### etcd server
-
-- Fix [`mvcc` "unsynced" watcher restore operation](https://github.com/etcd-io/etcd/pull/9297).
-  - "unsynced" watcher is watcher that needs to be in sync with events that have happened.
-  - That is, "unsynced" watcher is the slow watcher that was requested on old revision.
-  - "unsynced" watcher restore operation was not correctly populating its underlying watcher group.
-  - Which possibly causes [missing events from "unsynced" watchers](https://github.com/etcd-io/etcd/issues/9086).
-  - A node gets network partitioned with a watcher on a future revision, and falls behind receiving a leader snapshot after partition gets removed. When applying this snapshot, etcd watch storage moves current synced watchers to unsynced since sync watchers might have become stale during network partition. And reset synced watcher group to restart watcher routines. Previously, there was a bug when moving from synced watcher group to unsynced, thus client would miss events when the watcher was requested to the network-partitioned node.
-
-### Go
-
-- Compile with [*Go 1.8.7*](https://golang.org/doc/devel/release.html#go1.8).
-
-
-<hr>
-
-
-## [v3.1.11](https://github.com/etcd-io/etcd/releases/tag/v3.1.11) (2017-11-28)
-
-See [code changes](https://github.com/etcd-io/etcd/compare/v3.1.10...v3.1.11) and [v3.1 upgrade guide](https://github.com/etcd-io/etcd/blob/master/Documentation/upgrades/upgrade_3_1.md) 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](https://github.com/etcd-io/etcd/blob/master/Documentation/upgrades/upgrade_3_1.md).**
-
-### etcd server
-
-- [#8411](https://github.com/etcd-io/etcd/issues/8411),[#8806](https://github.com/etcd-io/etcd/pull/8806) backport "mvcc: sending events after restore"
-- [#8009](https://github.com/etcd-io/etcd/issues/8009),[#8902](https://github.com/etcd-io/etcd/pull/8902) backport coreos/bbolt v1.3.1-coreos.5
-
-### Go
-
-- Compile with [*Go 1.8.5*](https://golang.org/doc/devel/release.html#go1.8).
-
-
-<hr>
-
-
-## [v3.1.10](https://github.com/etcd-io/etcd/releases/tag/v3.1.10) (2017-07-14)
-
-See [code changes](https://github.com/etcd-io/etcd/compare/v3.1.9...v3.1.10) and [v3.1 upgrade guide](https://github.com/etcd-io/etcd/blob/master/Documentation/upgrades/upgrade_3_1.md) 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](https://github.com/etcd-io/etcd/blob/master/Documentation/upgrades/upgrade_3_1.md).**
-
-### Added
-
-- Tag docker images with minor versions.
-  - e.g. `docker pull quay.io/coreos/etcd:v3.1` to fetch latest v3.1 versions.
-
-### Go
-
-- Compile with [*Go 1.8.3*](https://golang.org/doc/devel/release.html#go1.8).
-  - Fix panic on `net/http.CloseNotify`
-
-
-<hr>
-
-
-## [v3.1.9](https://github.com/etcd-io/etcd/releases/tag/v3.1.9) (2017-06-09)
-
-See [code changes](https://github.com/etcd-io/etcd/compare/v3.1.8...v3.1.9) and [v3.1 upgrade guide](https://github.com/etcd-io/etcd/blob/master/Documentation/upgrades/upgrade_3_1.md) 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](https://github.com/etcd-io/etcd/blob/master/Documentation/upgrades/upgrade_3_1.md).**
-
-### etcd server
-
-- Allow v2 snapshot over 512MB.
-
-### Go
-
-- Compile with [*Go 1.7.6*](https://golang.org/doc/devel/release.html#go1.7).
-
-
-<hr>
-
-
-## [v3.1.8](https://github.com/etcd-io/etcd/releases/tag/v3.1.8) (2017-05-19)
-
-See [code changes](https://github.com/etcd-io/etcd/compare/v3.1.7...v3.1.8) and [v3.1 upgrade guide](https://github.com/etcd-io/etcd/blob/master/Documentation/upgrades/upgrade_3_1.md) 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](https://github.com/etcd-io/etcd/blob/master/Documentation/upgrades/upgrade_3_1.md).**
-
-### Go
-
-- Compile with [*Go 1.7.5*](https://golang.org/doc/devel/release.html#go1.7).
-
-
-<hr>
-
-
-## [v3.1.7](https://github.com/etcd-io/etcd/releases/tag/v3.1.7) (2017-04-28)
-
-See [code changes](https://github.com/etcd-io/etcd/compare/v3.1.6...v3.1.7) and [v3.1 upgrade guide](https://github.com/etcd-io/etcd/blob/master/Documentation/upgrades/upgrade_3_1.md) 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](https://github.com/etcd-io/etcd/blob/master/Documentation/upgrades/upgrade_3_1.md).**
-
-### Go
-
-- Compile with [*Go 1.7.5*](https://golang.org/doc/devel/release.html#go1.7).
-
-
-<hr>
-
-
-## [v3.1.6](https://github.com/etcd-io/etcd/releases/tag/v3.1.6) (2017-04-19)
-
-See [code changes](https://github.com/etcd-io/etcd/compare/v3.1.5...v3.1.6) and [v3.1 upgrade guide](https://github.com/etcd-io/etcd/blob/master/Documentation/upgrades/upgrade_3_1.md) 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](https://github.com/etcd-io/etcd/blob/master/Documentation/upgrades/upgrade_3_1.md).**
-
-### etcd server
-
-- Fill in Auth API response header.
-- Remove auth check in Status API.
-
-### Go
-
-- Compile with [*Go 1.7.5*](https://golang.org/doc/devel/release.html#go1.7).
-
-
-<hr>
-
-
-## [v3.1.5](https://github.com/etcd-io/etcd/releases/tag/v3.1.5) (2017-03-27)
-
-See [code changes](https://github.com/etcd-io/etcd/compare/v3.1.4...v3.1.5) and [v3.1 upgrade guide](https://github.com/etcd-io/etcd/blob/master/Documentation/upgrades/upgrade_3_1.md) 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](https://github.com/etcd-io/etcd/blob/master/Documentation/upgrades/upgrade_3_1.md).**
-
-### etcd server
-
-- Fix raft memory leak issue.
-- Fix Windows file path issues.
-
-### Other
-
-- Add `/etc/nsswitch.conf` file to alpine-based Docker image.
-
-### Go
-
-- Compile with [*Go 1.7.5*](https://golang.org/doc/devel/release.html#go1.7).
-
-
-<hr>
-
-
-## [v3.1.4](https://github.com/etcd-io/etcd/releases/tag/v3.1.4) (2017-03-22)
-
-See [code changes](https://github.com/etcd-io/etcd/compare/v3.1.3...v3.1.4) and [v3.1 upgrade guide](https://github.com/etcd-io/etcd/blob/master/Documentation/upgrades/upgrade_3_1.md) 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](https://github.com/etcd-io/etcd/blob/master/Documentation/upgrades/upgrade_3_1.md).**
-
-### Go
-
-- Compile with [*Go 1.7.5*](https://golang.org/doc/devel/release.html#go1.7).
-
-
-<hr>
-
-
-## [v3.1.3](https://github.com/etcd-io/etcd/releases/tag/v3.1.3) (2017-03-10)
-
-See [code changes](https://github.com/etcd-io/etcd/compare/v3.1.2...v3.1.3) and [v3.1 upgrade guide](https://github.com/etcd-io/etcd/blob/master/Documentation/upgrades/upgrade_3_1.md) 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](https://github.com/etcd-io/etcd/blob/master/Documentation/upgrades/upgrade_3_1.md).**
-
-### etcd gateway
-
-- Fix `etcd gateway` schema handling in DNS discovery.
-- Fix sd_notify behaviors in `gateway`, `grpc-proxy`.
-
-### gRPC Proxy
-
-- Fix sd_notify behaviors in `gateway`, `grpc-proxy`.
-
-### Other
-
-- Use machine default host when advertise URLs are default values(`localhost:2379,2380`) AND if listen URL is `0.0.0.0`.
-
-### Go
-
-- Compile with [*Go 1.7.5*](https://golang.org/doc/devel/release.html#go1.7).
-
-
-<hr>
-
-
-## [v3.1.2](https://github.com/etcd-io/etcd/releases/tag/v3.1.2) (2017-02-24)
-
-See [code changes](https://github.com/etcd-io/etcd/compare/v3.1.1...v3.1.2) and [v3.1 upgrade guide](https://github.com/etcd-io/etcd/blob/master/Documentation/upgrades/upgrade_3_1.md) 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](https://github.com/etcd-io/etcd/blob/master/Documentation/upgrades/upgrade_3_1.md).**
-
-### etcd gateway
-
-- Fix `etcd gateway` with multiple endpoints.
-
-### Other
-
-- Use IPv4 default host, by default (when IPv4 and IPv6 are available).
-
-### Go
-
-- Compile with [*Go 1.7.5*](https://golang.org/doc/devel/release.html#go1.7).
-
-
-<hr>
-
-
-## [v3.1.1](https://github.com/etcd-io/etcd/releases/tag/v3.1.1) (2017-02-17)
-
-See [code changes](https://github.com/etcd-io/etcd/compare/v3.1.0...v3.1.1) and [v3.1 upgrade guide](https://github.com/etcd-io/etcd/blob/master/Documentation/upgrades/upgrade_3_1.md) 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](https://github.com/etcd-io/etcd/blob/master/Documentation/upgrades/upgrade_3_1.md).**
-
-### Go
-
-- Compile with [*Go 1.7.5*](https://golang.org/doc/devel/release.html#go1.7).
-
-
-<hr>
-
-
-## [v3.1.0](https://github.com/etcd-io/etcd/releases/tag/v3.1.0) (2017-01-20)
-
-See [code changes](https://github.com/etcd-io/etcd/compare/v3.0.0...v3.1.0) and [v3.1 upgrade guide](https://github.com/etcd-io/etcd/blob/master/Documentation/upgrades/upgrade_3_1.md) 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](https://github.com/etcd-io/etcd/blob/master/Documentation/upgrades/upgrade_3_1.md).**
-
-### Improved
-
-- Faster linearizable reads (implements Raft [read-index](https://github.com/etcd-io/etcd/pull/6212)).
-- v3 authentication API is now stable.
-
-### Breaking Changes
-
-- Deprecated following gRPC metrics in favor of [go-grpc-prometheus](https://github.com/grpc-ecosystem/go-grpc-prometheus).
-  - `etcd_grpc_requests_total`
-  - `etcd_grpc_requests_failed_total`
-  - `etcd_grpc_active_streams`
-  - `etcd_grpc_unary_requests_duration_seconds`
-
-### Dependency
-
-- Upgrade [`github.com/ugorji/go/codec`](https://github.com/ugorji/go) to [**`ugorji/go@9c7f9b7`**](https://github.com/ugorji/go/commit/9c7f9b7a2bc3a520f7c7b30b34b7f85f47fe27b6), and [regenerate v2 `client`](https://github.com/etcd-io/etcd/pull/6945).
-
-### Security, Authentication
-
-See [security doc](https://github.com/etcd-io/etcd/blob/master/Documentation/op-guide/security.md) for more details.
-
-- SRV records (e.g., infra1.example.com) must match the discovery domain (i.e., example.com) if no custom certificate authority is given.
-  - `TLSConfig.ServerName` is ignored with user-provided certificates for backwards compatibility; to be deprecated.
-  - For example, `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.
-
-### etcd server
-
-- Automatic leadership transfer when leader steps down.
-- etcd flags
-  - `--strict-reconfig-check` flag is set by default.
-  - Add `--log-output` flag.
-  - Add `--metrics` flag.
-- etcd uses default route IP if advertise URL is not given.
-- Cluster rejects removing members if quorum will be lost.
-- Discovery now has upper limit for waiting on retries.
-- Warn on binding listeners through domain names; to be deprecated.
-- v3.0 and v3.1 with `--auto-compaction-retention=10` run periodic compaction on v3 key-value store for every 10-hour.
-  - Compactor only supports periodic compaction.
-  - Compactor records latest revisions every 5-minute, until it reaches the first compaction period (e.g. 10-hour).
-  - In order to retain key-value history of last compaction period, it uses the last revision that was fetched before compaction period, from the revision records that were collected every 5-minute.
-  - When `--auto-compaction-retention=10`, compactor uses revision 100 for compact revision where revision 100 is the latest revision fetched from 10 hours ago.
-  - If compaction succeeds or requested revision has already been compacted, it resets period timer and starts over with new historical revision records (e.g. restart revision collect and compact for the next 10-hour period).
-  - If compaction fails, it retries in 5 minutes.
-
-### client v3
-
-- Add `SetEndpoints` method; update endpoints at runtime.
-- Add `Sync` method; auto-update endpoints at runtime.
-- Add `Lease TimeToLive` API; fetch lease information.
-- replace Config.Logger field with global logger.
-- Get API responses are sorted in ascending order by default.
-
-### etcdctl v3
-
-- Add `lease timetolive` command.
-- Add `--print-value-only` flag to get command.
-- Add `--dest-prefix` flag to make-mirror command.
-- `get` command responses are sorted in ascending order by default.
-
-### gRPC Proxy
-
-- Experimental gRPC proxy feature.
-
-### Other
-
-- `recipes` now conform to sessions defined in `clientv3/concurrency`.
-- ACI has symlinks to `/usr/local/bin/etcd*`.
-
-### Go
-
-- Compile with [*Go 1.7.4*](https://golang.org/doc/devel/release.html#go1.7).
-
-
-<hr>
-

CHANGELOG-3.2.md

@@ -1,884 +0,0 @@
-
-
-Previous change logs can be found at [CHANGELOG-3.1](https://github.com/etcd-io/etcd/blob/master/CHANGELOG-3.1.md).
-
-
-The minimum recommended etcd versions to run in **production** are 3.1.11+, 3.2.26+, and 3.3.11+.
-
-
-<hr>
-
-
-## [v3.2.27](https://github.com/etcd-io/etcd/releases/tag/v3.2.27) (2019-TBD)
-
-### etcdctl
-
-- [Strip out insecure endpoints from DNS SRV records when using discovery](https://github.com/etcd-io/etcd/pull/10443) with etcdctl v2
-- Add [`etcdctl endpoint health --write-out` support](https://github.com/etcd-io/etcd/pull/9540).
-  - Previously, [`etcdctl endpoint health --write-out json` did not work](https://github.com/etcd-io/etcd/issues/9532).
-  - The command output is changed. Previously, if endpoint is unreachable, the command output is
-  "\<endpoint\> is unhealthy: failed to connect: \<error message\>". This change unified the error message, all error types
-  now have the same output "\<endpoint\> is unhealthy: failed to commit proposal: \<error message\>".
-
-### Metrics, Monitoring
-
-- Fix bug where [db_compaction_total_duration_milliseconds metric incorrectly measured duration as 0](https://github.com/etcd-io/etcd/pull/10646).
-
-<hr>
-
-
-## [v3.2.26](https://github.com/etcd-io/etcd/releases/tag/v3.2.26) (2019-01-11)
-
-See [code changes](https://github.com/etcd-io/etcd/compare/v3.2.25...v3.2.26) and [v3.2 upgrade guide](https://github.com/etcd-io/etcd/blob/master/Documentation/upgrades/upgrade_3_3.md) for any breaking changes.
-
-**Again, before running upgrades from any previous release, please make sure to read change logs below and [v3.2 upgrade guide](https://github.com/etcd-io/etcd/blob/master/Documentation/upgrades/upgrade_3_2.md).**
-
-### gRPC Proxy
-
-- Fix [memory leak in cache layer](https://github.com/etcd-io/etcd/pull/10327).
-
-### Security, Authentication
-
-- Disable [CommonName authentication for gRPC-gateway](https://github.com/etcd-io/etcd/pull/10366) gRPC-gateway proxy requests to etcd server use the etcd client server TLS certificate. If that certificate contains CommonName we do not want to use that for authentication as it could lead to permission escalation.
-
-### Go
-
-- Compile with [*Go 1.8.7*](https://golang.org/doc/devel/release.html#go1.8).
-
-
-<hr>
-
-
-## [v3.2.25](https://github.com/etcd-io/etcd/releases/tag/v3.2.25) (2018-10-10)
-
-See [code changes](https://github.com/etcd-io/etcd/compare/v3.2.24...v3.2.25) and [v3.2 upgrade guide](https://github.com/etcd-io/etcd/blob/master/Documentation/upgrades/upgrade_3_2.md) for any breaking changes.
-
-**Again, before running upgrades from any previous release, please make sure to read change logs below and [v3.2 upgrade guide](https://github.com/etcd-io/etcd/blob/master/Documentation/upgrades/upgrade_3_2.md).**
-
-### Improved
-
-- Improve ["became inactive" warning log](https://github.com/etcd-io/etcd/pull/10024), which indicates message send to a peer failed.
-- Improve [read index wait timeout warning log](https://github.com/etcd-io/etcd/pull/10026), which indicates that local node might have slow network.
-- Add [gRPC interceptor for debugging logs](https://github.com/etcd-io/etcd/pull/9990); enable `etcd --debug` flag to see per-request debug information.
-- Add [consistency check in snapshot status](https://github.com/etcd-io/etcd/pull/10109). If consistency check on snapshot file fails, `snapshot status` returns `"snapshot file integrity check failed..."` error.
-
-### Metrics, Monitoring
-
-See [List of metrics](https://etcd.io/docs/v3.2.17/metrics/) for all metrics per release.
-
-Note that any `etcd_debugging_*` metrics are experimental and subject to change.
-
-- Improve [`etcd_network_peer_round_trip_time_seconds`](https://github.com/etcd-io/etcd/pull/10155) Prometheus metric to track leader heartbeats.
-  - Previously, it only samples the TCP connection for snapshot messages.
-- Display all registered [gRPC metrics at start](https://github.com/etcd-io/etcd/pull/10032).
-- Add [`etcd_snap_db_fsync_duration_seconds_count`](https://github.com/etcd-io/etcd/pull/9997) Prometheus metric.
-- Add [`etcd_snap_db_save_total_duration_seconds_bucket`](https://github.com/etcd-io/etcd/pull/9997) Prometheus metric.
-- Add [`etcd_network_snapshot_send_success`](https://github.com/etcd-io/etcd/pull/9997) Prometheus metric.
-- Add [`etcd_network_snapshot_send_failures`](https://github.com/etcd-io/etcd/pull/9997) Prometheus metric.
-- Add [`etcd_network_snapshot_send_total_duration_seconds`](https://github.com/etcd-io/etcd/pull/9997) Prometheus metric.
-- Add [`etcd_network_snapshot_receive_success`](https://github.com/etcd-io/etcd/pull/9997) Prometheus metric.
-- Add [`etcd_network_snapshot_receive_failures`](https://github.com/etcd-io/etcd/pull/9997) Prometheus metric.
-- Add [`etcd_network_snapshot_receive_total_duration_seconds`](https://github.com/etcd-io/etcd/pull/9997) Prometheus metric.
-- Add [`etcd_server_id`](https://github.com/etcd-io/etcd/pull/9998) Prometheus metric.
-- Add [`etcd_server_health_success`](https://github.com/etcd-io/etcd/pull/10156) Prometheus metric.
-- Add [`etcd_server_health_failures`](https://github.com/etcd-io/etcd/pull/10156) Prometheus metric.
-- Add [`etcd_server_read_indexes_failed_total`](https://github.com/etcd-io/etcd/pull/10094) Prometheus metric.
-
-### client v3
-
-- Fix logic on [release lock key if cancelled](https://github.com/etcd-io/etcd/pull/10153) in `clientv3/concurrency` package.
-
-### Go
-
-- Compile with [*Go 1.8.7*](https://golang.org/doc/devel/release.html#go1.8).
-
-
-<hr>
-
-
-## [v3.2.24](https://github.com/etcd-io/etcd/releases/tag/v3.2.24) (2018-07-24)
-
-See [code changes](https://github.com/etcd-io/etcd/compare/v3.2.23...v3.2.24) and [v3.2 upgrade guide](https://github.com/etcd-io/etcd/blob/master/Documentation/upgrades/upgrade_3_2.md) for any breaking changes.
-
-**Again, before running upgrades from any previous release, please make sure to read change logs below and [v3.2 upgrade guide](https://github.com/etcd-io/etcd/blob/master/Documentation/upgrades/upgrade_3_2.md).**
-
-### Improved
-
-- Improve [Raft Read Index timeout warning messages](https://github.com/etcd-io/etcd/pull/9897).
-
-### Metrics, Monitoring
-
-See [List of metrics](https://etcd.io/docs/v3.2.27/metrics/) for all metrics per release.
-
-Note that any `etcd_debugging_*` metrics are experimental and subject to change.
-
-- Add [`etcd_server_go_version`](https://github.com/etcd-io/etcd/pull/9957) Prometheus metric.
-- Add [`etcd_server_heartbeat_send_failures_total`](https://github.com/etcd-io/etcd/pull/9942) Prometheus metric.
-- Add [`etcd_server_slow_apply_total`](https://github.com/etcd-io/etcd/pull/9942) Prometheus metric.
-- Add [`etcd_disk_backend_defrag_duration_seconds`](https://github.com/etcd-io/etcd/pull/9942) Prometheus metric.
-- Add [`etcd_mvcc_hash_duration_seconds`](https://github.com/etcd-io/etcd/pull/9942) Prometheus metric.
-- Add [`etcd_server_slow_read_indexes_total`](https://github.com/etcd-io/etcd/pull/9897) Prometheus metric.
-- Add [`etcd_server_quota_backend_bytes`](https://github.com/etcd-io/etcd/pull/9820) Prometheus metric.
-  - Use it with `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.
-- Add [`etcd_mvcc_db_total_size_in_bytes`](https://github.com/etcd-io/etcd/pull/9819) Prometheus metric.
-  - In addition to [`etcd_debugging_mvcc_db_total_size_in_bytes`](https://github.com/etcd-io/etcd/pull/9819).
-- Add [`etcd_mvcc_db_total_size_in_use_in_bytes`](https://github.com/etcd-io/etcd/pull/9256) Prometheus metric.
-  - Use it with `etcd_mvcc_db_total_size_in_bytes` and `etcd_server_quota_backend_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.
-
-### gRPC Proxy
-
-- Add [flags for specifying TLS for connecting to proxy](https://github.com/etcd-io/etcd/pull/9894):
-  - Add `grpc-proxy start --cert-file`, `grpc-proxy start --key-file` and `grpc-proxy start --trusted-ca-file` flags.
-- Add [`grpc-proxy start --metrics-addr` flag for specifying a separate metrics listen address](https://github.com/etcd-io/etcd/pull/9894).
-
-### client v3
-
-- Fix [lease keepalive interval updates when response queue is full](https://github.com/etcd-io/etcd/pull/9952).
-  - If `<-chan *clientv3LeaseKeepAliveResponse` from `clientv3.Lease.KeepAlive` was never consumed or channel is full, client was [sending keepalive request every 500ms](https://github.com/etcd-io/etcd/issues/9911) instead of expected rate of every "TTL / 3" duration.
-
-### Go
-
-- Compile with [*Go 1.8.7*](https://golang.org/doc/devel/release.html#go1.8).
-
-
-<hr>
-
-
-## [v3.2.23](https://github.com/etcd-io/etcd/releases/tag/v3.2.23) (2018-06-15)
-
-See [code changes](https://github.com/etcd-io/etcd/compare/v3.2.22...v3.2.23) and [v3.2 upgrade guide](https://github.com/etcd-io/etcd/blob/master/Documentation/upgrades/upgrade_3_2.md) for any breaking changes.
-
-**Again, before running upgrades from any previous release, please make sure to read change logs below and [v3.2 upgrade guide](https://github.com/etcd-io/etcd/blob/master/Documentation/upgrades/upgrade_3_2.md).**
-
-### Improved
-
-- Improve [slow request apply warning log](https://github.com/etcd-io/etcd/pull/9288).
-  - e.g. `read-only range request "key:\"/a\" range_end:\"/b\" " with result "range_response_count:3 size:96" took too long (97.966µs) to execute`.
-  - Redact [request value field](https://github.com/etcd-io/etcd/pull/9822).
-  - Provide [response size](https://github.com/etcd-io/etcd/pull/9826).
-- Add [backoff on watch retries on transient errors](https://github.com/etcd-io/etcd/pull/9840).
-
-### Metrics, Monitoring
-
-See [List of metrics](https://etcd.io/docs/v3.2.27/metrics/) for all metrics per release.
-
-Note that any `etcd_debugging_*` metrics are experimental and subject to change.
-
-- Add [`etcd_server_version`](https://github.com/etcd-io/etcd/pull/8960) Prometheus metric.
-  - To replace [Kubernetes `etcd-version-monitor`](https://github.com/etcd-io/etcd/issues/8948).
-
-### Go
-
-- Compile with [*Go 1.8.7*](https://golang.org/doc/devel/release.html#go1.8).
-
-
-<hr>
-
-
-## [v3.2.22](https://github.com/etcd-io/etcd/releases/tag/v3.2.22) (2018-06-06)
-
-See [code changes](https://github.com/etcd-io/etcd/compare/v3.2.21...v3.2.22) and [v3.2 upgrade guide](https://github.com/etcd-io/etcd/blob/master/Documentation/upgrades/upgrade_3_2.md) for any breaking changes.
-
-**Again, before running upgrades from any previous release, please make sure to read change logs below and [v3.2 upgrade guide](https://github.com/etcd-io/etcd/blob/master/Documentation/upgrades/upgrade_3_2.md).**
-
-### Security, Authentication
-
-- Support TLS cipher suite whitelisting.
-  - To block [weak cipher suites](https://github.com/etcd-io/etcd/issues/8320).
-  - TLS handshake fails when client hello is requested with invalid cipher suites.
-  - Add [`etcd --cipher-suites`](https://github.com/etcd-io/etcd/pull/9801) flag.
-  - If empty, Go auto-populates the list.
-
-### Go
-
-- Compile with [*Go 1.8.7*](https://golang.org/doc/devel/release.html#go1.8).
-
-
-<hr>
-
-
-## [v3.2.21](https://github.com/etcd-io/etcd/releases/tag/v3.2.21) (2018-05-31)
-
-See [code changes](https://github.com/etcd-io/etcd/compare/v3.2.20...v3.2.21) and [v3.2 upgrade guide](https://github.com/etcd-io/etcd/blob/master/Documentation/upgrades/upgrade_3_2.md) for any breaking changes.
-
-**Again, before running upgrades from any previous release, please make sure to read change logs below and [v3.2 upgrade guide](https://github.com/etcd-io/etcd/blob/master/Documentation/upgrades/upgrade_3_2.md).**
-
-### etcd server
-
-- Fix [auth storage panic when simple token provider is disabled](https://github.com/etcd-io/etcd/pull/8695).
-- Fix [`mvcc` server panic from restore operation](https://github.com/etcd-io/etcd/pull/9775).
-  - Let's assume that a watcher had been requested with a future revision X and sent to node A that became network-partitioned thereafter. Meanwhile, cluster makes progress. Then when the partition gets removed, the leader sends a snapshot to node A. Previously if the snapshot's latest revision is still lower than the watch revision X,  **etcd server panicked** during snapshot restore operation.
-  - Now, this server-side panic has been fixed.
-
-### Go
-
-- Compile with [*Go 1.8.7*](https://golang.org/doc/devel/release.html#go1.8).
-
-
-<hr>
-
-
-## [v3.2.20](https://github.com/etcd-io/etcd/releases/tag/v3.2.20) (2018-05-09)
-
-See [code changes](https://github.com/etcd-io/etcd/compare/v3.2.19...v3.2.20) and [v3.2 upgrade guide](https://github.com/etcd-io/etcd/blob/master/Documentation/upgrades/upgrade_3_2.md) for any breaking changes.
-
-**Again, before running upgrades from any previous release, please make sure to read change logs below and [v3.2 upgrade guide](https://github.com/etcd-io/etcd/blob/master/Documentation/upgrades/upgrade_3_2.md).**
-
-### etcd server
-
-- Purge old [`*.snap.db` snapshot files](https://github.com/etcd-io/etcd/pull/7967).
-  - Previously, etcd did not respect `--max-snapshots` flag to purge old `*.snap.db` files.
-  - Now, etcd purges old `*.snap.db` files to keep maximum `--max-snapshots` number of files on disk.
-
-### Go
-
-- Compile with [*Go 1.8.7*](https://golang.org/doc/devel/release.html#go1.8).
-
-
-<hr>
-
-
-## [v3.2.19](https://github.com/etcd-io/etcd/releases/tag/v3.2.19) (2018-04-24)
-
-See [code changes](https://github.com/etcd-io/etcd/compare/v3.2.18...v3.2.19) and [v3.2 upgrade guide](https://github.com/etcd-io/etcd/blob/master/Documentation/upgrades/upgrade_3_2.md) for any breaking changes.
-
-**Again, before running upgrades from any previous release, please make sure to read change logs below and [v3.2 upgrade guide](https://github.com/etcd-io/etcd/blob/master/Documentation/upgrades/upgrade_3_2.md).**
-
-### Metrics, Monitoring
-
-See [List of metrics](https://etcd.io/docs/v3.2.27/metrics/) for all metrics per release.
-
-Note that any `etcd_debugging_*` metrics are experimental and subject to change.
-
-- Fix [`etcd_debugging_server_lease_expired_total`](https://github.com/etcd-io/etcd/pull/9557) Prometheus metric.
-- Fix [race conditions in v2 server stat collecting](https://github.com/etcd-io/etcd/pull/9562).
-- Add [`etcd_server_is_leader`](https://github.com/etcd-io/etcd/pull/9587) Prometheus metric.
-
-### Security, Authentication
-
-- Fix [TLS reload](https://github.com/etcd-io/etcd/pull/9570) when [certificate SAN field only includes IP addresses but no domain names](https://github.com/etcd-io/etcd/issues/9541).
-  - In Go, server calls `(*tls.Config).GetCertificate` for TLS reload if and only if server's `(*tls.Config).Certificates` field is not empty, or `(*tls.ClientHelloInfo).ServerName` is not empty with a valid SNI from the client. Previously, etcd always populates `(*tls.Config).Certificates` on the initial client TLS handshake, as non-empty. Thus, client was always expected to supply a matching SNI in order to pass the TLS verification and to trigger `(*tls.Config).GetCertificate` to reload TLS assets.
-  - However, a certificate whose SAN field does [not include any domain names but only IP addresses](https://github.com/etcd-io/etcd/issues/9541) would request `*tls.ClientHelloInfo` with an empty `ServerName` field, thus failing to trigger the TLS reload on initial TLS handshake; this becomes a problem when expired certificates need to be replaced online.
-  - Now, `(*tls.Config).Certificates` is created empty on initial TLS client handshake, first to trigger `(*tls.Config).GetCertificate`, and then to populate rest of the certificates on every new TLS connection, even when client SNI is empty (e.g. cert only includes IPs).
-
-### etcd server
-
-- Add [`etcd --initial-election-tick-advance`](https://github.com/etcd-io/etcd/pull/9591) flag to configure initial election tick fast-forward.
-  - By default, `etcd --initial-election-tick-advance=true`, then local member fast-forwards election ticks to speed up "initial" leader election trigger.
-  - This benefits the case of larger election ticks. For instance, cross datacenter deployment may require longer election timeout of 10-second. If true, local node does not need wait up to 10-second. Instead, forwards its election ticks to 8-second, and have only 2-second left before leader election.
-  - Major assumptions are that: cluster has no active leader thus advancing ticks enables faster leader election. Or cluster already has an established leader, and rejoining follower is likely to receive heartbeats from the leader after tick advance and before election timeout.
-  - However, when network from leader to rejoining follower is congested, and the follower does not receive leader heartbeat within left election ticks, disruptive election has to happen thus affecting cluster availabilities.
-  - Now, this can be disabled by setting `--initial-election-tick-advance=false`.
-  - Disabling this would slow down initial bootstrap process for cross datacenter deployments. Make tradeoffs by configuring `--initial-election-tick-advance` at the cost of slow initial bootstrap.
-  - If single-node, it advances ticks regardless.
-  - Address [disruptive rejoining follower node](https://github.com/etcd-io/etcd/issues/9333).
-
-### Go
-
-- Compile with [*Go 1.8.7*](https://golang.org/doc/devel/release.html#go1.8).
-
-
-<hr>
-
-
-## [v3.2.18](https://github.com/etcd-io/etcd/releases/tag/v3.2.18) (2018-03-29)
-
-See [code changes](https://github.com/etcd-io/etcd/compare/v3.2.17...v3.2.18) and [v3.2 upgrade guide](https://github.com/etcd-io/etcd/blob/master/Documentation/upgrades/upgrade_3_2.md) for any breaking changes.
-
-**Again, before running upgrades from any previous release, please make sure to read change logs below and [v3.2 upgrade guide](https://github.com/etcd-io/etcd/blob/master/Documentation/upgrades/upgrade_3_2.md).**
-
-### Improved
-
-- Adjust [election timeout on server restart](https://github.com/etcd-io/etcd/pull/9415) to reduce [disruptive rejoining servers](https://github.com/etcd-io/etcd/issues/9333).
-  - Previously, etcd fast-forwards election ticks on server start, with only one tick left for leader election. This is to speed up start phase, without having to wait until all election ticks elapse. Advancing election ticks is useful for cross datacenter deployments with larger election timeouts. However, it was affecting cluster availability if the last tick elapses before leader contacts the restarted node.
-  - Now, when etcd restarts, it adjusts election ticks with more than one tick left, thus more time for leader to prevent disruptive restart.
-
-### Metrics, Monitoring
-
-See [List of metrics](https://etcd.io/docs/v3.2.27/metrics/) for all metrics per release.
-
-Note that any `etcd_debugging_*` metrics are experimental and subject to change.
-
-- Add missing [`etcd_network_peer_sent_failures_total` count](https://github.com/etcd-io/etcd/pull/9437).
-
-### Go
-
-- Compile with [*Go 1.8.7*](https://golang.org/doc/devel/release.html#go1.8).
-
-
-<hr>
-
-
-## [v3.2.17](https://github.com/etcd-io/etcd/releases/tag/v3.2.17) (2018-03-08)
-
-See [code changes](https://github.com/etcd-io/etcd/compare/v3.2.16...v3.2.17) and [v3.2 upgrade guide](https://github.com/etcd-io/etcd/blob/master/Documentation/upgrades/upgrade_3_2.md) for any breaking changes.
-
-**Again, before running upgrades from any previous release, please make sure to read change logs below and [v3.2 upgrade guide](https://github.com/etcd-io/etcd/blob/master/Documentation/upgrades/upgrade_3_2.md).**
-
-### etcd server
-
-- Fix [server panic on invalid Election Proclaim/Resign HTTP(S) requests](https://github.com/etcd-io/etcd/pull/9379).
-  - Previously, wrong-formatted HTTP requests to Election API could trigger panic in etcd server.
-  - e.g. `curl -L http://localhost:2379/v3/election/proclaim -X POST -d '{"value":""}'`, `curl -L http://localhost:2379/v3/election/resign -X POST -d '{"value":""}'`.
-- Prevent [overflow by large `TTL` values for `Lease` `Grant`](https://github.com/etcd-io/etcd/pull/9399).
-  - `TTL` parameter to `Grant` request is unit of second.
-  - Leases with too large `TTL` values exceeding `math.MaxInt64` [expire in unexpected ways](https://github.com/etcd-io/etcd/issues/9374).
-  - Server now returns `rpctypes.ErrLeaseTTLTooLarge` to client, when the requested `TTL` is larger than *9,000,000,000 seconds* (which is >285 years).
-  - Again, etcd `Lease` is meant for short-periodic keepalives or sessions, in the range of seconds or minutes. Not for hours or days!
-- Enable etcd server [`raft.Config.CheckQuorum` when starting with `ForceNewCluster`](https://github.com/etcd-io/etcd/pull/9347).
-
-### Proxy v2
-
-- Fix [v2 proxy leaky HTTP requests](https://github.com/etcd-io/etcd/pull/9336).
-
-### Go
-
-- Compile with [*Go 1.8.7*](https://golang.org/doc/devel/release.html#go1.8).
-
-
-<hr>
-
-
-## [v3.2.16](https://github.com/etcd-io/etcd/releases/tag/v3.2.16) (2018-02-12)
-
-See [code changes](https://github.com/etcd-io/etcd/compare/v3.2.15...v3.2.16) and [v3.2 upgrade guide](https://github.com/etcd-io/etcd/blob/master/Documentation/upgrades/upgrade_3_2.md) for any breaking changes.
-
-**Again, before running upgrades from any previous release, please make sure to read change logs below and [v3.2 upgrade guide](https://github.com/etcd-io/etcd/blob/master/Documentation/upgrades/upgrade_3_2.md).**
-
-### etcd server
-
-- Fix [`mvcc` "unsynced" watcher restore operation](https://github.com/etcd-io/etcd/pull/9297).
-  - "unsynced" watcher is watcher that needs to be in sync with events that have happened.
-  - That is, "unsynced" watcher is the slow watcher that was requested on old revision.
-  - "unsynced" watcher restore operation was not correctly populating its underlying watcher group.
-  - Which possibly causes [missing events from "unsynced" watchers](https://github.com/etcd-io/etcd/issues/9086).
-  - A node gets network partitioned with a watcher on a future revision, and falls behind receiving a leader snapshot after partition gets removed. When applying this snapshot, etcd watch storage moves current synced watchers to unsynced since sync watchers might have become stale during network partition. And reset synced watcher group to restart watcher routines. Previously, there was a bug when moving from synced watcher group to unsynced, thus client would miss events when the watcher was requested to the network-partitioned node.
-
-### Go
-
-- Compile with [*Go 1.8.5*](https://golang.org/doc/devel/release.html#go1.8).
-
-
-<hr>
-
-
-## [v3.2.15](https://github.com/etcd-io/etcd/releases/tag/v3.2.15) (2018-01-22)
-
-See [code changes](https://github.com/etcd-io/etcd/compare/v3.2.14...v3.2.15) and [v3.2 upgrade guide](https://github.com/etcd-io/etcd/blob/master/Documentation/upgrades/upgrade_3_2.md) for any breaking changes.
-
-**Again, before running upgrades from any previous release, please make sure to read change logs below and [v3.2 upgrade guide](https://github.com/etcd-io/etcd/blob/master/Documentation/upgrades/upgrade_3_2.md).**
-
-### etcd server
-
-- Prevent [server panic from member update/add](https://github.com/etcd-io/etcd/pull/9174) with [wrong scheme URLs](https://github.com/etcd-io/etcd/issues/9173).
-- Log [user context cancel errors on stream APIs in debug level with TLS](https://github.com/etcd-io/etcd/pull/9178).
-
-### Go
-
-- Compile with [*Go 1.8.5*](https://golang.org/doc/devel/release.html#go1.8).
-
-
-<hr>
-
-
-## [v3.2.14](https://github.com/etcd-io/etcd/releases/tag/v3.2.14) (2018-01-11)
-
-See [code changes](https://github.com/etcd-io/etcd/compare/v3.2.13...v3.2.14) and [v3.2 upgrade guide](https://github.com/etcd-io/etcd/blob/master/Documentation/upgrades/upgrade_3_2.md) for any breaking changes.
-
-**Again, before running upgrades from any previous release, please make sure to read change logs below and [v3.2 upgrade guide](https://github.com/etcd-io/etcd/blob/master/Documentation/upgrades/upgrade_3_2.md).**
-
-### Improved
-
-- Log [user context cancel errors on stream APIs in debug level](https://github.com/etcd-io/etcd/pull/9105).
-
-### etcd server
-
-- Fix [`mvcc/backend.defragdb` nil-pointer dereference on create bucket failure](https://github.com/etcd-io/etcd/pull/9119).
-
-### Go
-
-- Compile with [*Go 1.8.5*](https://golang.org/doc/devel/release.html#go1.8).
-
-
-<hr>
-
-
-## [v3.2.13](https://github.com/etcd-io/etcd/releases/tag/v3.2.13) (2018-01-02)
-
-See [code changes](https://github.com/etcd-io/etcd/compare/v3.2.12...v3.2.13) and [v3.2 upgrade guide](https://github.com/etcd-io/etcd/blob/master/Documentation/upgrades/upgrade_3_2.md) for any breaking changes.
-
-**Again, before running upgrades from any previous release, please make sure to read change logs below and [v3.2 upgrade guide](https://github.com/etcd-io/etcd/blob/master/Documentation/upgrades/upgrade_3_2.md).**
-
-### etcd server
-
-- Remove [verbose error messages on stream cancel and gRPC info-level logs](https://github.com/etcd-io/etcd/pull/9080) in server-side.
-- Fix [gRPC server panic on `GracefulStop` TLS-enabled server](https://github.com/etcd-io/etcd/pull/8987).
-
-### Go
-
-- Compile with [*Go 1.8.5*](https://golang.org/doc/devel/release.html#go1.8).
-
-
-<hr>
-
-
-## [v3.2.12](https://github.com/etcd-io/etcd/releases/tag/v3.2.12) (2017-12-20)
-
-See [code changes](https://github.com/etcd-io/etcd/compare/v3.2.11...v3.2.12) and [v3.2 upgrade guide](https://github.com/etcd-io/etcd/blob/master/Documentation/upgrades/upgrade_3_2.md) for any breaking changes.
-
-**Again, before running upgrades from any previous release, please make sure to read change logs below and [v3.2 upgrade guide](https://github.com/etcd-io/etcd/blob/master/Documentation/upgrades/upgrade_3_2.md).**
-
-### Dependency
-
-- Upgrade [`google.golang.org/grpc`](https://github.com/grpc/grpc-go/releases/tag) from [**`v1.7.4`**](https://github.com/grpc/grpc-go/releases/tag/v1.7.4) to [**`v1.7.5`**](https://github.com/grpc/grpc-go/releases/tag/v1.7.5).
-- Upgrade [`github.com/grpc-ecosystem/grpc-gateway`](https://github.com/grpc-ecosystem/grpc-gateway/releases) from [**`v1.3`**](https://github.com/grpc-ecosystem/grpc-gateway/releases/tag/v1.3) to [**`v1.3.0`**](https://github.com/grpc-ecosystem/grpc-gateway/releases/tag/v1.3.0).
-
-### etcd server
-
-- Fix [error message of `Revision` compactor](https://github.com/etcd-io/etcd/pull/8999) in server-side.
-
-### client v3
-
-- Add [`MaxCallSendMsgSize` and `MaxCallRecvMsgSize`](https://github.com/etcd-io/etcd/pull/9047) fields to [`clientv3.Config`](https://godoc.org/github.com/etcd-io/etcd/clientv3#Config).
-  - Fix [exceeded response size limit error in client-side](https://github.com/etcd-io/etcd/issues/9043).
-  - Address [kubernetes#51099](https://github.com/kubernetes/kubernetes/issues/51099).
-    - In previous versions(v3.2.10, v3.2.11), client response size was limited to only 4 MiB.
-  - `MaxCallSendMsgSize` default value is 2 MiB, if not configured.
-  - `MaxCallRecvMsgSize` default value is `math.MaxInt32`, if not configured.
-
-### Go
-
-- Compile with [*Go 1.8.5*](https://golang.org/doc/devel/release.html#go1.8).
-
-
-<hr>
-
-
-## [v3.2.11](https://github.com/etcd-io/etcd/releases/tag/v3.2.11) (2017-12-05)
-
-See [code changes](https://github.com/etcd-io/etcd/compare/v3.2.10...v3.2.11) and [v3.2 upgrade guide](https://github.com/etcd-io/etcd/blob/master/Documentation/upgrades/upgrade_3_2.md) for any breaking changes.
-
-**Again, before running upgrades from any previous release, please make sure to read change logs below and [v3.2 upgrade guide](https://github.com/etcd-io/etcd/blob/master/Documentation/upgrades/upgrade_3_2.md).**
-
-### Dependency
-
-- Upgrade [`google.golang.org/grpc`](https://github.com/grpc/grpc-go/releases/tag) from [**`v1.7.3`**](https://github.com/grpc/grpc-go/releases/tag/v1.7.3) to [**`v1.7.4`**](https://github.com/grpc/grpc-go/releases/tag/v1.7.4).
-
-### Security, Authentication
-
-See [security doc](https://github.com/etcd-io/etcd/blob/master/Documentation/op-guide/security.md) for more details.
-
-- Log [more details on TLS handshake failures](https://github.com/etcd-io/etcd/pull/8952/files).
-
-### client v3
-
-- Fix racey grpc-go's server handler transport `WriteStatus` call to prevent [TLS-enabled etcd server crash](https://github.com/etcd-io/etcd/issues/8904).
-- Add [gRPC RPC failure warnings](https://github.com/etcd-io/etcd/pull/8939) to help debug such issues in the future.
-
-### Documentation
-
-- Remove `--listen-metrics-urls` flag in monitoring document (non-released in `v3.2.x`, planned for `v3.3.x`).
-
-### Go
-
-- Compile with [*Go 1.8.5*](https://golang.org/doc/devel/release.html#go1.8).
-
-
-<hr>
-
-
-## [v3.2.10](https://github.com/etcd-io/etcd/releases/tag/v3.2.10) (2017-11-16)
-
-See [code changes](https://github.com/etcd-io/etcd/compare/v3.2.9...v3.2.10) and [v3.2 upgrade guide](https://github.com/etcd-io/etcd/blob/master/Documentation/upgrades/upgrade_3_2.md) for any breaking changes.
-
-**Again, before running upgrades from any previous release, please make sure to read change logs below and [v3.2 upgrade guide](https://github.com/etcd-io/etcd/blob/master/Documentation/upgrades/upgrade_3_2.md).**
-
-### Dependency
-
-- Upgrade [`google.golang.org/grpc`](https://github.com/grpc/grpc-go/releases/tag) from [**`v1.2.1`**](https://github.com/grpc/grpc-go/releases/tag/v1.2.1) to [**`v1.7.3`**](https://github.com/grpc/grpc-go/releases/tag/v1.7.3).
-- Upgrade [`github.com/grpc-ecosystem/grpc-gateway`](https://github.com/grpc-ecosystem/grpc-gateway/releases) from [**`v1.2.0`**](https://github.com/grpc-ecosystem/grpc-gateway/releases/tag/v1.2.0) to [**`v1.3`**](https://github.com/grpc-ecosystem/grpc-gateway/releases/tag/v1.3).
-
-### Security, Authentication
-
-See [security doc](https://github.com/etcd-io/etcd/blob/master/Documentation/op-guide/security.md) for more details.
-
-- Revert [discovery SRV auth `ServerName` with `*.{ROOT_DOMAIN}`](https://github.com/etcd-io/etcd/pull/8651) to support non-wildcard subject alternative names in the certs (see [issue #8445](https://github.com/etcd-io/etcd/issues/8445) for more contexts).
-  - For instance, `etcd --discovery-srv=etcd.local` will only authenticate peers/clients when the provided certs have root domain `etcd.local` (**not `*.etcd.local`**) as an entry in Subject Alternative Name (SAN) field.
-
-### etcd server
-
-- Replace backend key-value database `boltdb/bolt` with [`coreos/bbolt`](https://github.com/coreos/bbolt/releases) to address [backend database size issue](https://github.com/etcd-io/etcd/issues/8009).
-
-### client v3
-
-- Rewrite balancer to handle [network partitions](https://github.com/etcd-io/etcd/issues/8711).
-
-### Go
-
-- Compile with [*Go 1.8.5*](https://golang.org/doc/devel/release.html#go1.8).
-
-
-<hr>
-
-
-## [v3.2.9](https://github.com/etcd-io/etcd/releases/tag/v3.2.9) (2017-10-06)
-
-See [code changes](https://github.com/etcd-io/etcd/compare/v3.2.8...v3.2.9) and [v3.2 upgrade guide](https://github.com/etcd-io/etcd/blob/master/Documentation/upgrades/upgrade_3_2.md) for any breaking changes.
-
-**Again, before running upgrades from any previous release, please make sure to read change logs below and [v3.2 upgrade guide](https://github.com/etcd-io/etcd/blob/master/Documentation/upgrades/upgrade_3_2.md).**
-
-### Security, Authentication
-
-See [security doc](https://github.com/etcd-io/etcd/blob/master/Documentation/op-guide/security.md) for more details.
-
-- Update `golang.org/x/crypto/bcrypt` (see [golang/crypto@6c586e1](https://github.com/golang/crypto/commit/6c586e17d90a7d08bbbc4069984180dce3b04117)).
-- Fix discovery SRV bootstrapping to [authenticate `ServerName` with `*.{ROOT_DOMAIN}`](https://github.com/etcd-io/etcd/pull/8651), in order to support sub-domain wildcard matching (see [issue #8445](https://github.com/etcd-io/etcd/issues/8445) for more contexts).
-  - For instance, `etcd --discovery-srv=etcd.local` will only authenticate peers/clients when the provided certs have root domain `*.etcd.local` as an entry in Subject Alternative Name (SAN) field.
-
-### Go
-
-- Compile with [*Go 1.8.4*](https://golang.org/doc/devel/release.html#go1.8).
-
-
-<hr>
-
-
-## [v3.2.8](https://github.com/etcd-io/etcd/releases/tag/v3.2.8) (2017-09-29)
-
-See [code changes](https://github.com/etcd-io/etcd/compare/v3.2.7...v3.2.8) and [v3.2 upgrade guide](https://github.com/etcd-io/etcd/blob/master/Documentation/upgrades/upgrade_3_2.md) for any breaking changes.
-
-**Again, before running upgrades from any previous release, please make sure to read change logs below and [v3.2 upgrade guide](https://github.com/etcd-io/etcd/blob/master/Documentation/upgrades/upgrade_3_2.md).**
-
-### client v2
-
-- Fix v2 client failover to next endpoint on mutable operation.
-
-### gRPC Proxy
-
-- Handle [`KeysOnly` flag](https://github.com/etcd-io/etcd/pull/8552).
-
-### Go
-
-- Compile with [*Go 1.8.3*](https://golang.org/doc/devel/release.html#go1.8).
-
-
-<hr>
-
-
-## [v3.2.7](https://github.com/etcd-io/etcd/releases/tag/v3.2.7) (2017-09-01)
-
-See [code changes](https://github.com/etcd-io/etcd/compare/v3.2.6...v3.2.7) and [v3.2 upgrade guide](https://github.com/etcd-io/etcd/blob/master/Documentation/upgrades/upgrade_3_2.md) for any breaking changes.
-
-**Again, before running upgrades from any previous release, please make sure to read change logs below and [v3.2 upgrade guide](https://github.com/etcd-io/etcd/blob/master/Documentation/upgrades/upgrade_3_2.md).**
-
-### Security, Authentication
-
-- Fix [server-side auth so concurrent auth operations do not return old revision error](https://github.com/etcd-io/etcd/pull/8306).
-
-### client v3
-
-- Fix [`concurrency/stm` Put with serializable snapshot](https://github.com/etcd-io/etcd/pull/8439).
-  - Use store revision from first fetch to resolve write conflicts instead of modified revision.
-
-### Go
-
-- Compile with [*Go 1.8.3*](https://golang.org/doc/devel/release.html#go1.8).
-
-
-<hr>
-
-
-## [v3.2.6](https://github.com/etcd-io/etcd/releases/tag/v3.2.6) (2017-08-21)
-
-See [code changes](https://github.com/etcd-io/etcd/compare/v3.2.5...v3.2.6) and [v3.2 upgrade guide](https://github.com/etcd-io/etcd/blob/master/Documentation/upgrades/upgrade_3_2.md) for any breaking changes.
-
-**Again, before running upgrades from any previous release, please make sure to read change logs below and [v3.2 upgrade guide](https://github.com/etcd-io/etcd/blob/master/Documentation/upgrades/upgrade_3_2.md).**
-
-### etcd server
-
-- Fix watch restore from snapshot.
-- Fix multiple URLs for `--listen-peer-urls` flag.
-- Add `--enable-pprof` flag to etcd configuration file format.
-
-### Metrics, Monitoring
-
-See [List of metrics](https://etcd.io/docs/v3.2.27/metrics/) for all metrics per release.
-
-Note that any `etcd_debugging_*` metrics are experimental and subject to change.
-
-- Fix `etcd_debugging_mvcc_keys_total` inconsistency.
-
-### Go
-
-- Compile with [*Go 1.8.3*](https://golang.org/doc/devel/release.html#go1.8).
-
-
-<hr>
-
-
-## [v3.2.5](https://github.com/etcd-io/etcd/releases/tag/v3.2.5) (2017-08-04)
-
-See [code changes](https://github.com/etcd-io/etcd/compare/v3.2.4...v3.2.5) and [v3.2 upgrade guide](https://github.com/etcd-io/etcd/blob/master/Documentation/upgrades/upgrade_3_2.md) for any breaking changes.
-
-**Again, before running upgrades from any previous release, please make sure to read change logs below and [v3.2 upgrade guide](https://github.com/etcd-io/etcd/blob/master/Documentation/upgrades/upgrade_3_2.md).**
-
-### etcdctl v3
-
-- Return non-zero exit code on unhealthy `endpoint health`.
-
-### Security, Authentication
-
-See [security doc](https://github.com/etcd-io/etcd/blob/master/Documentation/op-guide/security.md) for more details.
-
-- [Server supports reverse-lookup on wildcard DNS `SAN`](https://github.com/etcd-io/etcd/pull/8281). For instance, if peer cert contains only DNS names (no IP addresses) in Subject Alternative Name (SAN) field, server first reverse-lookups the remote IP address to get a list of names mapping to that address (e.g. `nslookup IPADDR`). Then accepts the connection if those names have a matching name with peer cert's DNS names (either by exact or wildcard match). If none is matched, server forward-lookups each DNS entry in peer cert (e.g. look up `example.default.svc` when the entry is `*.example.default.svc`), and accepts connection only when the host's resolved addresses have the matching IP address with the peer's remote IP address. For example, peer B's CSR (with `cfssl`) SAN field is `["*.example.default.svc", "*.example.default.svc.cluster.local"]` when peer B's remote IP address is `10.138.0.2`. When peer B tries to join the cluster, peer A reverse-lookup the IP `10.138.0.2` to get the list of host names. And either exact or wildcard match the host names with peer B's cert DNS names in Subject Alternative Name (SAN) field. If none of reverse/forward lookups worked, it returns an error `"tls: "10.138.0.2" does not match any of DNSNames ["*.example.default.svc","*.example.default.svc.cluster.local"]`. See [issue#8268](https://github.com/etcd-io/etcd/issues/8268) for more detail.
-
-### Metrics, Monitoring
-
-See [List of metrics](https://etcd.io/docs/v3.2.27/metrics/) for all metrics per release.
-
-Note that any `etcd_debugging_*` metrics are experimental and subject to change.
-
-- Fix unreachable `/metrics` endpoint when `--enable-v2=false`.
-
-### gRPC Proxy
-
-- Handle [`PrevKv` flag](https://github.com/etcd-io/etcd/pull/8366).
-
-### Other
-
-- Add container registry `gcr.io/etcd-development/etcd`.
-
-### Go
-
-- Compile with [*Go 1.8.3*](https://golang.org/doc/devel/release.html#go1.8).
-
-
-<hr>
-
-
-## [v3.2.4](https://github.com/etcd-io/etcd/releases/tag/v3.2.4) (2017-07-19)
-
-See [code changes](https://github.com/etcd-io/etcd/compare/v3.2.3...v3.2.4) and [v3.2 upgrade guide](https://github.com/etcd-io/etcd/blob/master/Documentation/upgrades/upgrade_3_2.md) for any breaking changes.
-
-**Again, before running upgrades from any previous release, please make sure to read change logs below and [v3.2 upgrade guide](https://github.com/etcd-io/etcd/blob/master/Documentation/upgrades/upgrade_3_2.md).**
-
-### etcd server
-
-- Do not block on active client stream when stopping server
-
-### gRPC proxy
-
-- Fix gRPC proxy Snapshot RPC error handling
-
-### Go
-
-- Compile with [*Go 1.8.3*](https://golang.org/doc/devel/release.html#go1.8).
-
-
-<hr>
-
-
-## [v3.2.3](https://github.com/etcd-io/etcd/releases/tag/v3.2.3) (2017-07-14)
-
-See [code changes](https://github.com/etcd-io/etcd/compare/v3.2.2...v3.2.3) and [v3.2 upgrade guide](https://github.com/etcd-io/etcd/blob/master/Documentation/upgrades/upgrade_3_2.md) for any breaking changes.
-
-**Again, before running upgrades from any previous release, please make sure to read change logs below and [v3.2 upgrade guide](https://github.com/etcd-io/etcd/blob/master/Documentation/upgrades/upgrade_3_2.md).**
-
-### client v3
-
-- Let clients establish unlimited streams
-
-### Other
-
-- Tag docker images with minor versions
-  - e.g. `docker pull quay.io/coreos/etcd:v3.2` to fetch latest v3.2 versions
-
-### Go
-
-- Compile with [*Go 1.8.3*](https://golang.org/doc/devel/release.html#go1.8).
-
-
-<hr>
-
-
-## [v3.2.2](https://github.com/etcd-io/etcd/releases/tag/v3.2.2) (2017-07-07)
-
-See [code changes](https://github.com/etcd-io/etcd/compare/v3.2.1...v3.2.2) and [v3.2 upgrade guide](https://github.com/etcd-io/etcd/blob/master/Documentation/upgrades/upgrade_3_2.md) for any breaking changes.
-
-**Again, before running upgrades from any previous release, please make sure to read change logs below and [v3.2 upgrade guide](https://github.com/etcd-io/etcd/blob/master/Documentation/upgrades/upgrade_3_2.md).**
-
-### Improved
-
-- Rate-limit lease revoke on expiration.
-- Extend leases on promote to avoid queueing effect on lease expiration.
-
-### Security, Authentication
-
-See [security doc](https://github.com/etcd-io/etcd/blob/master/Documentation/op-guide/security.md) for more details.
-
-- [Server accepts connections if IP matches, without checking DNS entries](https://github.com/etcd-io/etcd/pull/8223). For instance, if peer cert contains IP addresses and DNS names in Subject Alternative Name (SAN) field, and the remote IP address matches one of those IP addresses, server just accepts connection without further checking the DNS names. For example, peer B's CSR (with `cfssl`) SAN field is `["invalid.domain", "10.138.0.2"]` when peer B's remote IP address is `10.138.0.2` and `invalid.domain` is a invalid host. When peer B tries to join the cluster, peer A successfully authenticates B, since Subject Alternative Name (SAN) field has a valid matching IP address. See [issue#8206](https://github.com/etcd-io/etcd/issues/8206) for more detail.
-
-### etcd server
-
-- Accept connection with matched IP SAN but no DNS match.
-  - Don't check DNS entries in certs if there's a matching IP.
-
-### gRPC gateway
-
-- Use user-provided listen address to connect to gRPC gateway.
-  - `net.Listener` rewrites IPv4 0.0.0.0 to IPv6 [::], breaking IPv6 disabled hosts.
-  - Only v3.2.0, v3.2.1 are affected.
-
-### Go
-
-- Compile with [*Go 1.8.3*](https://golang.org/doc/devel/release.html#go1.8).
-
-
-<hr>
-
-
-## [v3.2.1](https://github.com/etcd-io/etcd/releases/tag/v3.2.1) (2017-06-23)
-
-See [code changes](https://github.com/etcd-io/etcd/compare/v3.2.0...v3.2.1) and [v3.2 upgrade guide](https://github.com/etcd-io/etcd/blob/master/Documentation/upgrades/upgrade_3_2.md) for any breaking changes.
-
-**Again, before running upgrades from any previous release, please make sure to read change logs below and [v3.2 upgrade guide](https://github.com/etcd-io/etcd/blob/master/Documentation/upgrades/upgrade_3_2.md).**
-
-### etcd server
-
-- Fix backend database in-memory index corruption issue on restore (only 3.2.0 is affected).
-
-### gRPC gateway
-
-- Fix Txn marshaling.
-
-### Metrics, Monitoring
-
-See [List of metrics](https://etcd.io/docs/v3.2.27/metrics/) for all metrics per release.
-
-Note that any `etcd_debugging_*` metrics are experimental and subject to change.
-
-- Fix backend database size debugging metrics.
-
-### Go
-
-- Compile with [*Go 1.8.3*](https://golang.org/doc/devel/release.html#go1.8).
-
-
-<hr>
-
-
-## [v3.2.0](https://github.com/etcd-io/etcd/releases/tag/v3.2.0) (2017-06-09)
-
-See [code changes](https://github.com/etcd-io/etcd/compare/v3.1.0...v3.2.0) and [v3.2 upgrade guide](https://github.com/etcd-io/etcd/blob/master/Documentation/upgrades/upgrade_3_2.md) for any breaking changes.
-
-**Again, before running upgrades from any previous release, please make sure to read change logs below and [v3.2 upgrade guide](https://github.com/etcd-io/etcd/blob/master/Documentation/upgrades/upgrade_3_2.md).**
-
-### Improved
-
-- Improve backend read concurrency.
-
-### Breaking Changes
-
-- Increased [`--snapshot-count` default value from 10,000 to 100,000](https://github.com/etcd-io/etcd/pull/7160).
-  - Higher snapshot count means it holds Raft entries in memory for longer before discarding old entries.
-  - It is a trade-off between less frequent snapshotting and [higher memory usage](https://github.com/kubernetes/kubernetes/issues/60589#issuecomment-371977156).
-  - User lower `--snapshot-count` value for lower memory usage.
-  - User higher `--snapshot-count` value for better availabilities of slow followers (less frequent snapshots from leader).
-- `clientv3.Lease.TimeToLive` returns `LeaseTimeToLiveResponse.TTL == -1` on lease not found.
-- `clientv3.NewFromConfigFile` is moved to `clientv3/yaml.NewConfig`.
-- `embed.Etcd.Peers` field is now `[]*peerListener`.
-- Rejects domains names for `--listen-peer-urls` and `--listen-client-urls` (3.1 only prints out warnings), since [domain name is invalid for network interface binding](https://github.com/etcd-io/etcd/issues/6336).
-
-### Dependency
-
-- Upgrade [`google.golang.org/grpc`](https://github.com/grpc/grpc-go/releases) from [**`v1.0.4`**](https://github.com/grpc/grpc-go/releases/tag/v1.0.4) to [**`v1.2.1`**](https://github.com/grpc/grpc-go/releases/tag/v1.2.1).
-- Upgrade [`github.com/grpc-ecosystem/grpc-gateway`](https://github.com/grpc-ecosystem/grpc-gateway/releases) to [**`v1.2.0`**](https://github.com/grpc-ecosystem/grpc-gateway/releases/tag/v1.2.0).
-
-### Metrics, Monitoring
-
-See [List of metrics](https://etcd.io/docs/v3.2.27/metrics/) for all metrics per release.
-
-Note that any `etcd_debugging_*` metrics are experimental and subject to change.
-
-- Add [`etcd_disk_backend_snapshot_duration_seconds`](https://github.com/etcd-io/etcd/pull/7892)
-- Add `etcd_debugging_server_lease_expired_total` metrics.
-
-### Security, Authentication
-
-See [security doc](https://github.com/etcd-io/etcd/blob/master/Documentation/op-guide/security.md) for more details.
-
-- [TLS certificates get reloaded on every client connection](https://github.com/etcd-io/etcd/pull/7829). This is useful when replacing expiry certs without stopping etcd servers; it can be done by overwriting old certs with new ones. Refreshing certs for every connection should not have too much overhead, but can be improved in the future, with caching layer. Example tests can be found [here](https://github.com/etcd-io/etcd/blob/b041ce5d514a4b4aaeefbffb008f0c7570a18986/integration/v3_grpc_test.go#L1601-L1757).
-- [Server denies incoming peer certs with wrong IP `SAN`](https://github.com/etcd-io/etcd/pull/7687). For instance, if peer cert contains any IP addresses in Subject Alternative Name (SAN) field, server authenticates a peer only when the remote IP address matches one of those IP addresses. This is to prevent unauthorized endpoints from joining the cluster.  For example, peer B's CSR (with `cfssl`) SAN field is `["*.example.default.svc", "*.example.default.svc.cluster.local", "10.138.0.27"]` when peer B's actual IP address is `10.138.0.2`, not `10.138.0.27`. When peer B tries to join the cluster, peer A will reject B with the error `x509: certificate is valid for 10.138.0.27, not 10.138.0.2`, because B's remote IP address does not match the one in Subject Alternative Name (SAN) field.
-- [Server resolves TLS `DNSNames` when checking `SAN`](https://github.com/etcd-io/etcd/pull/7767). For instance, if peer cert contains only DNS names (no IP addresses) in Subject Alternative Name (SAN) field, server authenticates a peer only when forward-lookups (`dig b.com`) on those DNS names have matching IP with the remote IP address.  For example, peer B's CSR (with `cfssl`) SAN field is `["b.com"]` when peer B's remote IP address is `10.138.0.2`. When peer B tries to join the cluster, peer A looks up the incoming host `b.com` to get the list of IP addresses (e.g. `dig b.com`). And rejects B if the list does not contain the IP `10.138.0.2`, with the error `tls: 10.138.0.2 does not match any of DNSNames ["b.com"]`.
-- Auth support JWT token.
-
-### etcd server
-
-- RPCs
-  - Add Election, Lock service.
-- Native client `etcdserver/api/v3client`
-  - client "embedded" in the server.
-- Logging, monitoring
-  - Server warns large snapshot operations.
-- Add `etcd --enable-v2` flag to enable v2 API server.
-  - `etcd --enable-v2=true` by default.
-- Add `etcd --auth-token` flag.
-- v3.2 compactor runs [every hour](https://github.com/etcd-io/etcd/pull/7875).
-  - Compactor only supports periodic compaction.
-  - Compactor continues to record latest revisions every 5-minute.
-  - For every hour, it uses the last revision that was fetched before compaction period, from the revision records that were collected every 5-minute.
-  - That is, for every hour, compactor discards historical data created before compaction period.
-  - The retention window of compaction period moves to next hour.
-  - For instance, when hourly writes are 100 and `--auto-compaction-retention=10`, v3.1 compacts revision 1000, 2000, and 3000 for every 10-hour, while v3.2 compacts revision 1000, 1100, and 1200 for every 1-hour.
-  - If compaction succeeds or requested revision has already been compacted, it resets period timer and removes used compacted revision from historical revision records (e.g. start next revision collect and compaction from previously collected revisions).
-  - If compaction fails, it retries in 5 minutes.
-- Allow snapshot over 512MB.
-
-### client v3
-
-- STM prefetching.
-- Add namespace feature.
-- Add `ErrOldCluster` with server version checking.
-- Translate `WithPrefix()` into `WithFromKey()` for empty key.
-
-### etcdctl v3
-
-- Add `check perf` command.
-- Add `etcdctl --from-key` flag to role grant-permission command.
-- `lock` command takes an optional command to execute.
-
-### gRPC Proxy
-
-- Proxy endpoint discovery.
-- Namespaces.
-- Coalesce lease requests.
-
-### etcd gateway
-
-- Support [DNS SRV priority](https://github.com/etcd-io/etcd/pull/7882) for [smart proxy routing](https://github.com/etcd-io/etcd/issues/4378).
-
-### Other
-
-- v3 client
-  - concurrency package's elections updated to match RPC interfaces.
-  - let client dial endpoints not in the balancer.
-- Release
-  - Annotate acbuild with supports-systemd-notify.
-  - Add `nsswitch.conf` to Docker container image.
-  - Add ppc64le, arm64(experimental) builds.
-
-### Go
-
-- Compile with [*Go 1.8.3*](https://golang.org/doc/devel/release.html#go1.8).
-
-
-<hr>
-

CHANGELOG-3.3.md

@@ -1,734 +0,0 @@
-
-
-Previous change logs can be found at [CHANGELOG-3.2](https://github.com/etcd-io/etcd/blob/master/CHANGELOG-3.2.md).
-
-
-The minimum recommended etcd versions to run in **production** are 3.1.11+, 3.2.26+, and 3.3.11+.
-
-
-<hr>
-
-
-## [v3.3.14](https://github.com/etcd-io/etcd/releases/tag/v3.3.14) (2019-TBD)
-
-See [code changes](https://github.com/etcd-io/etcd/compare/v3.3.13...v3.3.14) and [v3.3 upgrade guide](https://github.com/etcd-io/etcd/blob/master/Documentation/upgrades/upgrade_3_3.md) for any breaking changes.
-
-**Again, before running upgrades from any previous release, please make sure to read change logs below and [v3.3 upgrade guide](https://github.com/etcd-io/etcd/blob/master/Documentation/upgrades/upgrade_3_3.md).**
-
-### etcd server
-
-- Fix [race condition in `rafthttp` transport pause/resume](https://github.com/etcd-io/etcd/pull/10826).
-
-### client v3
-
-- Fix [gRPC panic "send on closed channel](https://github.com/etcd-io/etcd/issues/9956) by upgrading [`google.golang.org/grpc`](https://github.com/grpc/grpc-go/releases) from [**`v1.7.5`**](https://github.com/grpc/grpc-go/releases/tag/v1.7.5) to [**`v1.23.0`**](https://github.com/grpc/grpc-go/releases/tag/v1.23.0).
-- Rewrite [client balancer](https://github.com/etcd-io/etcd/pull/9860) with [new gRPC balancer interface](https://github.com/etcd-io/etcd/issues/9106).
-  - Upgrade [gRPC to v1.23.0](https://github.com/etcd-io/etcd/pull/10911).
-  - Improve [client balancer failover against secure endpoints](https://github.com/etcd-io/etcd/pull/10911).
-    - Fix ["kube-apiserver 1.13.x refuses to work when first etcd-server is not available" (kubernetes#72102)](https://github.com/kubernetes/kubernetes/issues/72102).
-
-### etcdctl v3
-
-- Add [`etcdctl endpoint health --write-out` support](https://github.com/etcd-io/etcd/pull/9540).
-  - Previously, [`etcdctl endpoint health --write-out json` did not work](https://github.com/etcd-io/etcd/issues/9532).
-  - The command output is changed. Previously, if endpoint is unreachable, the command output is
-  "\<endpoint\> is unhealthy: failed to connect: \<error message\>". This change unified the error message, all error types
-  now have the same output "\<endpoint\> is unhealthy: failed to commit proposal: \<error message\>".
-- Add [missing newline in `etcdctl endpoint health`](https://github.com/etcd-io/etcd/pull/10793).
-
-
-<hr>
-
-
-## [v3.3.13](https://github.com/etcd-io/etcd/releases/tag/v3.3.13) (2019-05-02)
-
-See [code changes](https://github.com/etcd-io/etcd/compare/v3.3.12...v3.3.13) and [v3.3 upgrade guide](https://github.com/etcd-io/etcd/blob/master/Documentation/upgrades/upgrade_3_3.md) for any breaking changes.
-
-**Again, before running upgrades from any previous release, please make sure to read change logs below and [v3.3 upgrade guide](https://github.com/etcd-io/etcd/blob/master/Documentation/upgrades/upgrade_3_3.md).**
-
-### Improved
-
-- Improve [heartbeat send failure logging](https://github.com/etcd-io/etcd/pull/10663).
-- Add [`Verify` function to perform corruption check on WAL contents](https://github.com/etcd-io/etcd/pull/10603).
-
-### Metrics, Monitoring
-
-See [List of metrics](https://etcd.readthedocs.io/en/latest/operate.html#v3-3) for all metrics per release.
-
-Note that any `etcd_debugging_*` metrics are experimental and subject to change.
-
-- Fix bug where [db_compaction_total_duration_milliseconds metric incorrectly measured duration as 0](https://github.com/etcd-io/etcd/pull/10646).
-
-### client v3
-
-- Fix [`(*Client).Endpoints()` method race condition](https://github.com/etcd-io/etcd/pull/10595).
-
-### Package `wal`
-
-- Add [`Verify` function to perform corruption check on WAL contents](https://github.com/etcd-io/etcd/pull/10603).
-
-### Dependency
-
-- Migrate [`github.com/ugorji/go/codec`](https://github.com/ugorji/go/releases) to [**`github.com/json-iterator/go`**](https://github.com/json-iterator/go) (See [#10667](https://github.com/etcd-io/etcd/pull/10667) for more).
-- Migrate [`github.com/ghodss/yaml`](https://github.com/ghodss/yaml/releases) to [**`sigs.k8s.io/yaml`**](https://github.com/kubernetes-sigs/yaml) (See [#10718](https://github.com/etcd-io/etcd/pull/10718) for more).
-
-### Go
-
-- Compile with [*Go 1.10.8*](https://golang.org/doc/devel/release.html#go1.10).
-
-
-<hr>
-
-
-## [v3.3.12](https://github.com/etcd-io/etcd/releases/tag/v3.3.12) (2019-02-07)
-
-See [code changes](https://github.com/etcd-io/etcd/compare/v3.3.11...v3.3.12) and [v3.3 upgrade guide](https://github.com/etcd-io/etcd/blob/master/Documentation/upgrades/upgrade_3_3.md) for any breaking changes.
-
-**Again, before running upgrades from any previous release, please make sure to read change logs below and [v3.3 upgrade guide](https://github.com/etcd-io/etcd/blob/master/Documentation/upgrades/upgrade_3_3.md).**
-
-### etcdctl
-
-- [Strip out insecure endpoints from DNS SRV records when using discovery](https://github.com/etcd-io/etcd/pull/10443) with etcdctl v2
-
-### Go
-
-- Compile with [*Go 1.10.8*](https://golang.org/doc/devel/release.html#go1.10).
-
-
-<hr>
-
-
-## [v3.3.11](https://github.com/etcd-io/etcd/releases/tag/v3.3.11) (2019-01-11)
-
-See [code changes](https://github.com/etcd-io/etcd/compare/v3.3.10...v3.3.11) and [v3.3 upgrade guide](https://github.com/etcd-io/etcd/blob/master/Documentation/upgrades/upgrade_3_3.md) for any breaking changes.
-
-**Again, before running upgrades from any previous release, please make sure to read change logs below and [v3.3 upgrade guide](https://github.com/etcd-io/etcd/blob/master/Documentation/upgrades/upgrade_3_3.md).**
-
-### gRPC Proxy
-
-- Fix [memory leak in cache layer](https://github.com/etcd-io/etcd/pull/10327).
-
-### Security, Authentication
-
-- Disable [CommonName authentication for gRPC-gateway](https://github.com/etcd-io/etcd/pull/10366) gRPC-gateway proxy requests to etcd server use the etcd client server TLS certificate. If that certificate contains CommonName we do not want to use that for authentication as it could lead to permission escalation.
-
-### Go
-
-- Compile with [*Go 1.10.7*](https://golang.org/doc/devel/release.html#go1.10).
-
-
-<hr>
-
-
-## [v3.3.10](https://github.com/etcd-io/etcd/releases/tag/v3.3.10) (2018-10-10)
-
-See [code changes](https://github.com/etcd-io/etcd/compare/v3.3.9...v3.3.10) and [v3.3 upgrade guide](https://github.com/etcd-io/etcd/blob/master/Documentation/upgrades/upgrade_3_3.md) for any breaking changes.
-
-**Again, before running upgrades from any previous release, please make sure to read change logs below and [v3.3 upgrade guide](https://github.com/etcd-io/etcd/blob/master/Documentation/upgrades/upgrade_3_3.md).**
-
-### Improved
-
-- Improve ["became inactive" warning log](https://github.com/etcd-io/etcd/pull/10024), which indicates message send to a peer failed.
-- Improve [read index wait timeout warning log](https://github.com/etcd-io/etcd/pull/10026), which indicates that local node might have slow network.
-- Add [gRPC interceptor for debugging logs](https://github.com/etcd-io/etcd/pull/9990); enable `etcd --debug` flag to see per-request debug information.
-- Add [consistency check in snapshot status](https://github.com/etcd-io/etcd/pull/10109). If consistency check on snapshot file fails, `snapshot status` returns `"snapshot file integrity check failed..."` error.
-
-### Metrics, Monitoring
-
-See [List of metrics](https://etcd.io/docs/v3.3.12/metrics/) for all metrics per release.
-
-Note that any `etcd_debugging_*` metrics are experimental and subject to change.
-
-- Improve [`etcd_network_peer_round_trip_time_seconds`](https://github.com/etcd-io/etcd/pull/10155) Prometheus metric to track leader heartbeats.
-  - Previously, it only samples the TCP connection for snapshot messages.
-- Add [`etcd_snap_db_fsync_duration_seconds_count`](https://github.com/etcd-io/etcd/pull/9997) Prometheus metric.
-- Add [`etcd_snap_db_save_total_duration_seconds_bucket`](https://github.com/etcd-io/etcd/pull/9997) Prometheus metric.
-- Add [`etcd_network_snapshot_send_success`](https://github.com/etcd-io/etcd/pull/9997) Prometheus metric.
-- Add [`etcd_network_snapshot_send_failures`](https://github.com/etcd-io/etcd/pull/9997) Prometheus metric.
-- Add [`etcd_network_snapshot_send_total_duration_seconds`](https://github.com/etcd-io/etcd/pull/9997) Prometheus metric.
-- Add [`etcd_network_snapshot_receive_success`](https://github.com/etcd-io/etcd/pull/9997) Prometheus metric.
-- Add [`etcd_network_snapshot_receive_failures`](https://github.com/etcd-io/etcd/pull/9997) Prometheus metric.
-- Add [`etcd_network_snapshot_receive_total_duration_seconds`](https://github.com/etcd-io/etcd/pull/9997) Prometheus metric.
-- Add [`etcd_server_id`](https://github.com/etcd-io/etcd/pull/9998) Prometheus metric.
-- Add [`etcd_server_health_success`](https://github.com/etcd-io/etcd/pull/10156) Prometheus metric.
-- Add [`etcd_server_health_failures`](https://github.com/etcd-io/etcd/pull/10156) Prometheus metric.
-- Add [`etcd_server_read_indexes_failed_total`](https://github.com/etcd-io/etcd/pull/10094) Prometheus metric.
-
-### client v3
-
-- Fix logic on [release lock key if cancelled](https://github.com/etcd-io/etcd/pull/10153) in `clientv3/concurrency` package.
-
-### Go
-
-- Compile with [*Go 1.10.4*](https://golang.org/doc/devel/release.html#go1.10).
-
-
-<hr>
-
-
-## [v3.3.9](https://github.com/etcd-io/etcd/releases/tag/v3.3.9) (2018-07-24)
-
-See [code changes](https://github.com/etcd-io/etcd/compare/v3.3.8...v3.3.9) and [v3.3 upgrade guide](https://github.com/etcd-io/etcd/blob/master/Documentation/upgrades/upgrade_3_3.md) for any breaking changes.
-
-**Again, before running upgrades from any previous release, please make sure to read change logs below and [v3.3 upgrade guide](https://github.com/etcd-io/etcd/blob/master/Documentation/upgrades/upgrade_3_3.md).**
-
-### Improved
-
-- Improve [Raft Read Index timeout warning messages](https://github.com/etcd-io/etcd/pull/9897).
-
-### Security, Authentication
-
-- Compile with [*Go 1.10.3*](https://golang.org/doc/devel/release.html#go1.10) to support [crypto/x509 "Name Constraints"](https://github.com/etcd-io/etcd/issues/9912).
-
-### Metrics, Monitoring
-
-See [List of metrics](https://etcd.io/docs/v3.3.12/metrics/) for all metrics per release.
-
-Note that any `etcd_debugging_*` metrics are experimental and subject to change.
-
-- Add [`etcd_server_go_version`](https://github.com/etcd-io/etcd/pull/9957) Prometheus metric.
-- Add [`etcd_server_heartbeat_send_failures_total`](https://github.com/etcd-io/etcd/pull/9940) Prometheus metric.
-- Add [`etcd_server_slow_apply_total`](https://github.com/etcd-io/etcd/pull/9940) Prometheus metric.
-- Add [`etcd_disk_backend_defrag_duration_seconds`](https://github.com/etcd-io/etcd/pull/9940) Prometheus metric.
-- Add [`etcd_mvcc_hash_duration_seconds`](https://github.com/etcd-io/etcd/pull/9940) Prometheus metric.
-- Add [`etcd_mvcc_hash_rev_duration_seconds`](https://github.com/etcd-io/etcd/pull/9940) Prometheus metric.
-- Add [`etcd_server_slow_read_indexes_total`](https://github.com/etcd-io/etcd/pull/9897) Prometheus metric.
-- Add [`etcd_server_quota_backend_bytes`](https://github.com/etcd-io/etcd/pull/9820) Prometheus metric.
-  - Use it with `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.
-- Add [`etcd_mvcc_db_total_size_in_bytes`](https://github.com/etcd-io/etcd/pull/9819) Prometheus metric.
-  - In addition to [`etcd_debugging_mvcc_db_total_size_in_bytes`](https://github.com/etcd-io/etcd/pull/9819).
-- Add [`etcd_mvcc_db_total_size_in_use_in_bytes`](https://github.com/etcd-io/etcd/pull/9256) Prometheus metric.
-  - Use it with `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.
-
-### client v3
-
-- Fix [lease keepalive interval updates when response queue is full](https://github.com/etcd-io/etcd/pull/9952).
-  - If `<-chan *clientv3LeaseKeepAliveResponse` from `clientv3.Lease.KeepAlive` was never consumed or channel is full, client was [sending keepalive request every 500ms](https://github.com/etcd-io/etcd/issues/9911) instead of expected rate of every "TTL / 3" duration.
-
-### Go
-
-- Compile with [*Go 1.10.3*](https://golang.org/doc/devel/release.html#go1.10).
-
-
-<hr>
-
-
-## [v3.3.8](https://github.com/etcd-io/etcd/releases/tag/v3.3.8) (2018-06-15)
-
-See [code changes](https://github.com/etcd-io/etcd/compare/v3.3.7...v3.3.8) and [v3.3 upgrade guide](https://github.com/etcd-io/etcd/blob/master/Documentation/upgrades/upgrade_3_3.md) for any breaking changes.
-
-**Again, before running upgrades from any previous release, please make sure to read change logs below and [v3.3 upgrade guide](https://github.com/etcd-io/etcd/blob/master/Documentation/upgrades/upgrade_3_3.md).**
-
-### Improved
-
-- Improve [slow request apply warning log](https://github.com/etcd-io/etcd/pull/9288).
-  - e.g. `read-only range request "key:\"/a\" range_end:\"/b\" " with result "range_response_count:3 size:96" took too long (97.966µs) to execute`.
-  - Redact [request value field](https://github.com/etcd-io/etcd/pull/9822).
-  - Provide [response size](https://github.com/etcd-io/etcd/pull/9826).
-- Add [backoff on watch retries on transient errors](https://github.com/etcd-io/etcd/pull/9840).
-
-### Go
-
-- Compile with [*Go 1.9.7*](https://golang.org/doc/devel/release.html#go1.9).
-
-
-<hr>
-
-
-## [v3.3.7](https://github.com/etcd-io/etcd/releases/tag/v3.3.7) (2018-06-06)
-
-See [code changes](https://github.com/etcd-io/etcd/compare/v3.3.6...v3.3.7) and [v3.3 upgrade guide](https://github.com/etcd-io/etcd/blob/master/Documentation/upgrades/upgrade_3_3.md) for any breaking changes.
-
-**Again, before running upgrades from any previous release, please make sure to read change logs below and [v3.3 upgrade guide](https://github.com/etcd-io/etcd/blob/master/Documentation/upgrades/upgrade_3_3.md).**
-
-### Security, Authentication
-
-- Support TLS cipher suite whitelisting.
-  - To block [weak cipher suites](https://github.com/etcd-io/etcd/issues/8320).
-  - TLS handshake fails when client hello is requested with invalid cipher suites.
-  - Add [`etcd --cipher-suites`](https://github.com/etcd-io/etcd/pull/9801) flag.
-  - If empty, Go auto-populates the list.
-
-### etcdctl v3
-
-- Fix [`etcdctl move-leader` command for TLS-enabled endpoints](https://github.com/etcd-io/etcd/pull/9807).
-
-### Go
-
-- Compile with [*Go 1.9.6*](https://golang.org/doc/devel/release.html#go1.9).
-
-
-<hr>
-
-
-## [v3.3.6](https://github.com/etcd-io/etcd/releases/tag/v3.3.6) (2018-05-31)
-
-See [code changes](https://github.com/etcd-io/etcd/compare/v3.3.5...v3.3.6) and [v3.3 upgrade guide](https://github.com/etcd-io/etcd/blob/master/Documentation/upgrades/upgrade_3_3.md) for any breaking changes.
-
-**Again, before running upgrades from any previous release, please make sure to read change logs below and [v3.3 upgrade guide](https://github.com/etcd-io/etcd/blob/master/Documentation/upgrades/upgrade_3_3.md).**
-
-### etcd server
-
-- Allow [empty auth token](https://github.com/etcd-io/etcd/pull/9369).
-  - Previously, when auth token is an empty string, it returns [`failed to initialize the etcd server: auth: invalid auth options` error](https://github.com/etcd-io/etcd/issues/9349).
-- Fix [auth storage panic on server lease revoke routine with JWT token](https://github.com/etcd-io/etcd/issues/9695).
-- Fix [`mvcc` server panic from restore operation](https://github.com/etcd-io/etcd/pull/9775).
-  - Let's assume that a watcher had been requested with a future revision X and sent to node A that became network-partitioned thereafter. Meanwhile, cluster makes progress. Then when the partition gets removed, the leader sends a snapshot to node A. Previously if the snapshot's latest revision is still lower than the watch revision X,  **etcd server panicked** during snapshot restore operation.
-  - Now, this server-side panic has been fixed.
-
-### Go
-
-- Compile with [*Go 1.9.6*](https://golang.org/doc/devel/release.html#go1.9).
-
-
-<hr>
-
-
-## [v3.3.5](https://github.com/etcd-io/etcd/releases/tag/v3.3.5) (2018-05-09)
-
-See [code changes](https://github.com/etcd-io/etcd/compare/v3.3.4...v3.3.5) and [v3.3 upgrade guide](https://github.com/etcd-io/etcd/blob/master/Documentation/upgrades/upgrade_3_3.md) for any breaking changes.
-
-**Again, before running upgrades from any previous release, please make sure to read change logs below and [v3.3 upgrade guide](https://github.com/etcd-io/etcd/blob/master/Documentation/upgrades/upgrade_3_3.md).**
-
-### etcdctl v3
-
-- Fix [`etcdctl watch [key] [range_end] -- [exec-command…]`](https://github.com/etcd-io/etcd/pull/9688) parsing.
-  - Previously,  `ETCDCTL_API=3 ./bin/etcdctl watch foo -- echo watch event received` panicked.
-
-### Go
-
-- Compile with [*Go 1.9.6*](https://golang.org/doc/devel/release.html#go1.9).
-
-
-<hr>
-
-
-## [v3.3.4](https://github.com/etcd-io/etcd/releases/tag/v3.3.4) (2018-04-24)
-
-See [code changes](https://github.com/etcd-io/etcd/compare/v3.3.3...v3.3.4) and [v3.3 upgrade guide](https://github.com/etcd-io/etcd/blob/master/Documentation/upgrades/upgrade_3_3.md) for any breaking changes.
-
-**Again, before running upgrades from any previous release, please make sure to read change logs below and [v3.3 upgrade guide](https://github.com/etcd-io/etcd/blob/master/Documentation/upgrades/upgrade_3_3.md).**
-
-### Metrics, Monitoring
-
-See [List of metrics](https://etcd.io/docs/v3.3.12/metrics/) for all metrics per release.
-
-Note that any `etcd_debugging_*` metrics are experimental and subject to change.
-
-- Add [`etcd_server_is_leader`](https://github.com/etcd-io/etcd/pull/9587) Prometheus metric.
-- Fix [`etcd_debugging_server_lease_expired_total`](https://github.com/etcd-io/etcd/pull/9557) Prometheus metric.
-- Fix [race conditions in v2 server stat collecting](https://github.com/etcd-io/etcd/pull/9562).
-
-### Security, Authentication
-
-- Fix [TLS reload](https://github.com/etcd-io/etcd/pull/9570) when [certificate SAN field only includes IP addresses but no domain names](https://github.com/etcd-io/etcd/issues/9541).
-  - In Go, server calls `(*tls.Config).GetCertificate` for TLS reload if and only if server's `(*tls.Config).Certificates` field is not empty, or `(*tls.ClientHelloInfo).ServerName` is not empty with a valid SNI from the client. Previously, etcd always populates `(*tls.Config).Certificates` on the initial client TLS handshake, as non-empty. Thus, client was always expected to supply a matching SNI in order to pass the TLS verification and to trigger `(*tls.Config).GetCertificate` to reload TLS assets.
-  - However, a certificate whose SAN field does [not include any domain names but only IP addresses](https://github.com/etcd-io/etcd/issues/9541) would request `*tls.ClientHelloInfo` with an empty `ServerName` field, thus failing to trigger the TLS reload on initial TLS handshake; this becomes a problem when expired certificates need to be replaced online.
-  - Now, `(*tls.Config).Certificates` is created empty on initial TLS client handshake, first to trigger `(*tls.Config).GetCertificate`, and then to populate rest of the certificates on every new TLS connection, even when client SNI is empty (e.g. cert only includes IPs).
-
-### etcd server
-
-- Add [`etcd --initial-election-tick-advance`](https://github.com/etcd-io/etcd/pull/9591) flag to configure initial election tick fast-forward.
-  - By default, `etcd --initial-election-tick-advance=true`, then local member fast-forwards election ticks to speed up "initial" leader election trigger.
-  - This benefits the case of larger election ticks. For instance, cross datacenter deployment may require longer election timeout of 10-second. If true, local node does not need wait up to 10-second. Instead, forwards its election ticks to 8-second, and have only 2-second left before leader election.
-  - Major assumptions are that: cluster has no active leader thus advancing ticks enables faster leader election. Or cluster already has an established leader, and rejoining follower is likely to receive heartbeats from the leader after tick advance and before election timeout.
-  - However, when network from leader to rejoining follower is congested, and the follower does not receive leader heartbeat within left election ticks, disruptive election has to happen thus affecting cluster availabilities.
-  - Now, this can be disabled by setting `--initial-election-tick-advance=false`.
-  - Disabling this would slow down initial bootstrap process for cross datacenter deployments. Make tradeoffs by configuring `etcd --initial-election-tick-advance` at the cost of slow initial bootstrap.
-  - If single-node, it advances ticks regardless.
-  - Address [disruptive rejoining follower node](https://github.com/etcd-io/etcd/issues/9333).
-
-### Package `embed`
-
-- Add [`embed.Config.InitialElectionTickAdvance`](https://github.com/etcd-io/etcd/pull/9591) to enable/disable initial election tick fast-forward.
-  - `embed.NewConfig()` would return `*embed.Config` with `InitialElectionTickAdvance` as true by default.
-
-### Go
-
-- Compile with [*Go 1.9.5*](https://golang.org/doc/devel/release.html#go1.9).
-
-
-<hr>
-
-
-## [v3.3.3](https://github.com/etcd-io/etcd/releases/tag/v3.3.3) (2018-03-29)
-
-See [code changes](https://github.com/etcd-io/etcd/compare/v3.3.2...v3.3.3) and [v3.3 upgrade guide](https://github.com/etcd-io/etcd/blob/master/Documentation/upgrades/upgrade_3_3.md) for any breaking changes.
-
-**Again, before running upgrades from any previous release, please make sure to read change logs below and [v3.3 upgrade guide](https://github.com/etcd-io/etcd/blob/master/Documentation/upgrades/upgrade_3_3.md).**
-
-### Improved
-
-- Adjust [election timeout on server restart](https://github.com/etcd-io/etcd/pull/9415) to reduce [disruptive rejoining servers](https://github.com/etcd-io/etcd/issues/9333).
-  - Previously, etcd fast-forwards election ticks on server start, with only one tick left for leader election. This is to speed up start phase, without having to wait until all election ticks elapse. Advancing election ticks is useful for cross datacenter deployments with larger election timeouts. However, it was affecting cluster availability if the last tick elapses before leader contacts the restarted node.
-  - Now, when etcd restarts, it adjusts election ticks with more than one tick left, thus more time for leader to prevent disruptive restart.
-- Adjust [periodic compaction retention window](https://github.com/etcd-io/etcd/pull/9485).
-  - e.g. `etcd --auto-compaction-mode=revision --auto-compaction-retention=1000` automatically `Compact` on `"latest revision" - 1000` every 5-minute (when latest revision is 30000, compact on revision 29000).
-  - e.g. Previously, `etcd --auto-compaction-mode=periodic --auto-compaction-retention=72h` automatically `Compact` with 72-hour retention windown for every 7.2-hour. **Now, `Compact` happens, for every 1-hour but still with 72-hour retention window.**
-  - e.g. Previously, `etcd --auto-compaction-mode=periodic --auto-compaction-retention=30m` automatically `Compact` with 30-minute retention windown for every 3-minute. **Now, `Compact` happens, for every 30-minute but still with 30-minute retention window.**
-  - Periodic compactor keeps recording latest revisions for every compaction period when given period is less than 1-hour, or for every 1-hour when given compaction period is greater than 1-hour (e.g. 1-hour when `etcd --auto-compaction-mode=periodic --auto-compaction-retention=24h`).
-  - For every compaction period or 1-hour, compactor uses the last revision that was fetched before compaction period, to discard historical data.
-  - The retention window of compaction period moves for every given compaction period or hour.
-  - For instance, when hourly writes are 100 and `etcd --auto-compaction-mode=periodic --auto-compaction-retention=24h`, `v3.2.x`, `v3.3.0`, `v3.3.1`, and `v3.3.2` compact revision 2400, 2640, and 2880 for every 2.4-hour, while `v3.3.3` *or later* compacts revision 2400, 2500, 2600 for every 1-hour.
-  - Futhermore, when `etcd --auto-compaction-mode=periodic --auto-compaction-retention=30m` and writes per minute are about 1000, `v3.3.0`, `v3.3.1`, and `v3.3.2` compact revision 30000, 33000, and 36000, for every 3-minute, while `v3.3.3` *or later* compacts revision 30000, 60000, and 90000, for every 30-minute.
-
-### Metrics, Monitoring
-
-See [List of metrics](https://etcd.io/docs/v3.3.12/metrics/) for all metrics per release.
-
-Note that any `etcd_debugging_*` metrics are experimental and subject to change.
-
-- Add missing [`etcd_network_peer_sent_failures_total` count](https://github.com/etcd-io/etcd/pull/9437).
-
-### Go
-
-- Compile with [*Go 1.9.5*](https://golang.org/doc/devel/release.html#go1.9).
-
-
-<hr>
-
-
-## [v3.3.2](https://github.com/etcd-io/etcd/releases/tag/v3.3.2) (2018-03-08)
-
-See [code changes](https://github.com/etcd-io/etcd/compare/v3.3.1...v3.3.2) and [v3.3 upgrade guide](https://github.com/etcd-io/etcd/blob/master/Documentation/upgrades/upgrade_3_3.md) for any breaking changes.
-
-**Again, before running upgrades from any previous release, please make sure to read change logs below and [v3.3 upgrade guide](https://github.com/etcd-io/etcd/blob/master/Documentation/upgrades/upgrade_3_3.md).**
-
-### etcd server
-
-- Fix [server panic on invalid Election Proclaim/Resign HTTP(S) requests](https://github.com/etcd-io/etcd/pull/9379).
-  - Previously, wrong-formatted HTTP requests to Election API could trigger panic in etcd server.
-  - e.g. `curl -L http://localhost:2379/v3/election/proclaim -X POST -d '{"value":""}'`, `curl -L http://localhost:2379/v3/election/resign -X POST -d '{"value":""}'`.
-- Fix [revision-based compaction retention parsing](https://github.com/etcd-io/etcd/pull/9339).
-  - Previously, `etcd --auto-compaction-mode revision --auto-compaction-retention 1` was [translated to revision retention 3600000000000](https://github.com/etcd-io/etcd/issues/9337).
-  - Now, `etcd --auto-compaction-mode revision --auto-compaction-retention 1` is correctly parsed as revision retention 1.
-- Prevent [overflow by large `TTL` values for `Lease` `Grant`](https://github.com/etcd-io/etcd/pull/9399).
-  - `TTL` parameter to `Grant` request is unit of second.
-  - Leases with too large `TTL` values exceeding `math.MaxInt64` [expire in unexpected ways](https://github.com/etcd-io/etcd/issues/9374).
-  - Server now returns `rpctypes.ErrLeaseTTLTooLarge` to client, when the requested `TTL` is larger than *9,000,000,000 seconds* (which is >285 years).
-  - Again, etcd `Lease` is meant for short-periodic keepalives or sessions, in the range of seconds or minutes. Not for hours or days!
-- Enable etcd server [`raft.Config.CheckQuorum` when starting with `ForceNewCluster`](https://github.com/etcd-io/etcd/pull/9347).
-
-### Proxy v2
-
-- Fix [v2 proxy leaky HTTP requests](https://github.com/etcd-io/etcd/pull/9336).
-
-### Go
-
-- Compile with [*Go 1.9.4*](https://golang.org/doc/devel/release.html#go1.9).
-
-
-<hr>
-
-
-## [v3.3.1](https://github.com/etcd-io/etcd/releases/tag/v3.3.1) (2018-02-12)
-
-See [code changes](https://github.com/etcd-io/etcd/compare/v3.3.0...v3.3.1) and [v3.3 upgrade guide](https://github.com/etcd-io/etcd/blob/master/Documentation/upgrades/upgrade_3_3.md) for any breaking changes.
-
-**Again, before running upgrades from any previous release, please make sure to read change logs below and [v3.3 upgrade guide](https://github.com/etcd-io/etcd/blob/master/Documentation/upgrades/upgrade_3_3.md).**
-
-### Improved
-
-- Add [warnings on requests taking too long](https://github.com/etcd-io/etcd/pull/9288).
-  - e.g. `etcdserver: read-only range request "key:\"\\000\" range_end:\"\\000\" " took too long [3.389041388s] to execute`
-
-### etcd server
-
-- Fix [`mvcc` "unsynced" watcher restore operation](https://github.com/etcd-io/etcd/pull/9281).
-  - "unsynced" watcher is watcher that needs to be in sync with events that have happened.
-  - That is, "unsynced" watcher is the slow watcher that was requested on old revision.
-  - "unsynced" watcher restore operation was not correctly populating its underlying watcher group.
-  - Which possibly causes [missing events from "unsynced" watchers](https://github.com/etcd-io/etcd/issues/9086).
-  - A node gets network partitioned with a watcher on a future revision, and falls behind receiving a leader snapshot after partition gets removed. When applying this snapshot, etcd watch storage moves current synced watchers to unsynced since sync watchers might have become stale during network partition. And reset synced watcher group to restart watcher routines. Previously, there was a bug when moving from synced watcher group to unsynced, thus client would miss events when the watcher was requested to the network-partitioned node.
-
-### Go
-
-- Compile with [*Go 1.9.4*](https://golang.org/doc/devel/release.html#go1.9).
-
-
-<hr>
-
-
-## [v3.3.0](https://github.com/etcd-io/etcd/releases/tag/v3.3.0) (2018-02-01)
-
-See [code changes](https://github.com/etcd-io/etcd/compare/v3.2.0...v3.3.0) and [v3.3 upgrade guide](https://github.com/etcd-io/etcd/blob/master/Documentation/upgrades/upgrade_3_3.md) for any breaking changes.
-
-**Again, before running upgrades from any previous release, please make sure to read change logs below and [v3.3 upgrade guide](https://github.com/etcd-io/etcd/blob/master/Documentation/upgrades/upgrade_3_3.md).**
-
-- [v3.3.0-rc.4](https://github.com/etcd-io/etcd/releases/tag/v3.3.0-rc.4) (2018-01-22), see [code changes](https://github.com/etcd-io/etcd/compare/v3.3.0-rc.3...v3.3.0-rc.4).
-- [v3.3.0-rc.3](https://github.com/etcd-io/etcd/releases/tag/v3.3.0-rc.3) (2018-01-17), see [code changes](https://github.com/etcd-io/etcd/compare/v3.3.0-rc.2...v3.3.0-rc.3).
-- [v3.3.0-rc.2](https://github.com/etcd-io/etcd/releases/tag/v3.3.0-rc.2) (2018-01-11), see [code changes](https://github.com/etcd-io/etcd/compare/v3.3.0-rc.1...v3.3.0-rc.2).
-- [v3.3.0-rc.1](https://github.com/etcd-io/etcd/releases/tag/v3.3.0-rc.1) (2018-01-02), see [code changes](https://github.com/etcd-io/etcd/compare/v3.3.0-rc.0...v3.3.0-rc.1).
-- [v3.3.0-rc.0](https://github.com/etcd-io/etcd/releases/tag/v3.3.0-rc.0) (2017-12-20), see [code changes](https://github.com/etcd-io/etcd/compare/v3.2.0...v3.3.0-rc.0).
-
-### Improved
-
-- Use [`coreos/bbolt`](https://github.com/coreos/bbolt/releases) to replace [`boltdb/bolt`](https://github.com/boltdb/bolt#project-status).
-  - Fix [etcd database size grows until `mvcc: database space exceeded`](https://github.com/etcd-io/etcd/issues/8009).
-- [Support database size larger than 8GiB](https://github.com/etcd-io/etcd/pull/7525) (8GiB is now a suggested maximum size for normal environments)
-- [Reduce memory allocation](https://github.com/etcd-io/etcd/pull/8428) on [Range operations](https://github.com/etcd-io/etcd/pull/8475).
-- [Rate limit](https://github.com/etcd-io/etcd/pull/8099) and [randomize](https://github.com/etcd-io/etcd/pull/8101) lease revoke on restart or leader elections.
-  - Prevent [spikes in Raft proposal rate](https://github.com/etcd-io/etcd/issues/8096).
-- Support `clientv3` balancer failover under [network faults/partitions](https://github.com/etcd-io/etcd/issues/8711).
-- Better warning on [mismatched `etcd --initial-cluster`](https://github.com/etcd-io/etcd/pull/8083) flag.
-  - etcd compares `etcd --initial-advertise-peer-urls` against corresponding `etcd --initial-cluster` URLs with forward-lookup.
-  - If resolved IP addresses of `etcd --initial-advertise-peer-urls` and `etcd --initial-cluster` do not match (e.g. [due to DNS error](https://github.com/etcd-io/etcd/pull/9210)), etcd will exit with errors.
-    - v3.2 error: `etcd --initial-cluster must include s1=https://s1.test:2380 given --initial-advertise-peer-urls=https://s1.test:2380`.
-    - v3.3 error: `failed to resolve https://s1.test:2380 to match --initial-cluster=s1=https://s1.test:2380 (failed to resolve "https://s1.test:2380" (error ...))`.
-
-### Breaking Changes
-
-- Require [`google.golang.org/grpc`](https://github.com/grpc/grpc-go/releases) [**`v1.7.4`**](https://github.com/grpc/grpc-go/releases/tag/v1.7.4) or [**`v1.7.5`**](https://github.com/grpc/grpc-go/releases/tag/v1.7.5).
-  - Deprecate [`metadata.Incoming/OutgoingContext`](https://github.com/etcd-io/etcd/pull/7896).
-  - Deprecate `grpclog.Logger`, upgrade to [`grpclog.LoggerV2`](https://github.com/etcd-io/etcd/pull/8533).
-  - Deprecate [`grpc.ErrClientConnTimeout`](https://github.com/etcd-io/etcd/pull/8505) errors in `clientv3`.
-  - Use [`MaxRecvMsgSize` and `MaxSendMsgSize`](https://github.com/etcd-io/etcd/pull/8437) to limit message size, in etcd server.
-- Translate [gRPC status error in v3 client `Snapshot` API](https://github.com/etcd-io/etcd/pull/9038).
-- v3 `etcdctl` [`lease timetolive LEASE_ID`](https://github.com/etcd-io/etcd/issues/9028) on expired lease now prints [`"lease LEASE_ID already expired"`](https://github.com/etcd-io/etcd/pull/9047).
-  - <=3.2 prints `"lease LEASE_ID granted with TTL(0s), remaining(-1s)"`.
-- Replace [gRPC gateway](https://github.com/grpc-ecosystem/grpc-gateway) endpoint `/v3alpha` with [`/v3beta`](https://github.com/etcd-io/etcd/pull/8880).
-  - To deprecate [`/v3alpha`](https://github.com/etcd-io/etcd/issues/8125) in v3.4.
-  - In v3.3, `curl -L http://localhost:2379/v3alpha/kv/put -X POST -d '{"key": "Zm9v", "value": "YmFy"}'` still works as a fallback to `curl -L http://localhost:2379/v3beta/kv/put -X POST -d '{"key": "Zm9v", "value": "YmFy"}'`, but `curl -L http://localhost:2379/v3alpha/kv/put -X POST -d '{"key": "Zm9v", "value": "YmFy"}'` won't work in v3.4. Use `curl -L http://localhost:2379/v3beta/kv/put -X POST -d '{"key": "Zm9v", "value": "YmFy"}'` instead.
-- Change `etcd --auto-compaction-retention` flag to [accept string values](https://github.com/etcd-io/etcd/pull/8563) with [finer granularity](https://github.com/etcd-io/etcd/issues/8503).
-  - Now that `etcd --auto-compaction-retention` accepts string values, etcd configuration YAML file `auto-compaction-retention` field must be changed to `string` type.
-  - Previously, `--config-file etcd.config.yaml` can have `auto-compaction-retention: 24` field, now must be `auto-compaction-retention: "24"` or `auto-compaction-retention: "24h"`.
-  - If configured as `etcd --auto-compaction-mode periodic --auto-compaction-retention "24h"`, the time duration value for `etcd --auto-compaction-retention` flag must be valid for [`time.ParseDuration`](https://golang.org/pkg/time/#ParseDuration) function in Go.
-
-### Dependency
-
-- Upgrade [`boltdb/bolt`](https://github.com/boltdb/bolt#project-status) from [**`v1.3.0`**](https://github.com/boltdb/bolt/releases/tag/v1.3.0) to [`coreos/bbolt`](https://github.com/coreos/bbolt/releases) [**`v1.3.1-coreos.6`**](https://github.com/coreos/bbolt/releases/tag/v1.3.1-coreos.6).
-- Upgrade [`google.golang.org/grpc`](https://github.com/grpc/grpc-go/releases) from [**`v1.2.1`**](https://github.com/grpc/grpc-go/releases/tag/v1.2.1) to [**`v1.7.5`**](https://github.com/grpc/grpc-go/releases/tag/v1.7.5).
-- Upgrade [`github.com/ugorji/go/codec`](https://github.com/ugorji/go) to [**`v1.1`**](https://github.com/ugorji/go/releases/tag/v1.1), and [regenerate v2 `client`](https://github.com/etcd-io/etcd/pull/8721).
-- Upgrade [`github.com/ugorji/go/codec`](https://github.com/ugorji/go) to [**`ugorji/go@54210f4e0`**](https://github.com/ugorji/go/commit/54210f4e076c57f351166f0ed60e67d3fca57a36), and [regenerate v2 `client`](https://github.com/etcd-io/etcd/pull/8574).
-- Upgrade [`github.com/grpc-ecosystem/grpc-gateway`](https://github.com/grpc-ecosystem/grpc-gateway/releases) from [**`v1.2.2`**](https://github.com/grpc-ecosystem/grpc-gateway/releases/tag/v1.2.2) to [**`v1.3.0`**](https://github.com/grpc-ecosystem/grpc-gateway/releases/tag/v1.3.0).
-- Upgrade [`golang.org/x/crypto/bcrypt`](https://github.com/golang/crypto) to [**`golang/crypto@6c586e17d`**](https://github.com/golang/crypto/commit/6c586e17d90a7d08bbbc4069984180dce3b04117).
-
-### Metrics, Monitoring
-
-See [List of metrics](https://etcd.io/docs/v3.3.12/metrics/) for all metrics per release.
-
-Note that any `etcd_debugging_*` metrics are experimental and subject to change.
-
-- Add [`etcd --listen-metrics-urls`](https://github.com/etcd-io/etcd/pull/8242) flag for additional `/metrics` and `/health` endpoints.
-  - Useful for [bypassing critical APIs when monitoring etcd](https://github.com/etcd-io/etcd/issues/8060).
-- Add [`etcd_server_version`](https://github.com/etcd-io/etcd/pull/8960) Prometheus metric.
-  - To replace [Kubernetes `etcd-version-monitor`](https://github.com/etcd-io/etcd/issues/8948).
-- Add [`etcd_debugging_mvcc_db_compaction_keys_total`](https://github.com/etcd-io/etcd/pull/8280) Prometheus metric.
-- Add [`etcd_debugging_server_lease_expired_total`](https://github.com/etcd-io/etcd/pull/8064) Prometheus metric.
-  - To improve [lease revoke monitoring](https://github.com/etcd-io/etcd/issues/8050).
-- Document [Prometheus 2.0 rules](https://github.com/etcd-io/etcd/pull/8879).
-- Initialize gRPC server [metrics with zero values](https://github.com/etcd-io/etcd/pull/8878).
-- Fix [range/put/delete operation metrics](https://github.com/etcd-io/etcd/pull/8054) with transaction.
-  - `etcd_debugging_mvcc_range_total`
-  - `etcd_debugging_mvcc_put_total`
-  - `etcd_debugging_mvcc_delete_total`
-  - `etcd_debugging_mvcc_txn_total`
-- Fix [`etcd_debugging_mvcc_keys_total`](https://github.com/etcd-io/etcd/pull/8390) on restore.
-- Fix [`etcd_debugging_mvcc_db_total_size_in_bytes`](https://github.com/etcd-io/etcd/pull/8120) on restore.
-  - Also change to [`prometheus.NewGaugeFunc`](https://github.com/etcd-io/etcd/pull/8150).
-
-### Security, Authentication
-
-See [security doc](https://github.com/etcd-io/etcd/blob/master/Documentation/op-guide/security.md) for more details.
-
-- Add [CRL based connection rejection](https://github.com/etcd-io/etcd/pull/8124) to manage [revoked certs](https://github.com/etcd-io/etcd/issues/4034).
-- Document [TLS authentication changes](https://github.com/etcd-io/etcd/pull/8895).
-  - [Server accepts connections if IP matches, without checking DNS entries](https://github.com/etcd-io/etcd/pull/8223). For instance, if peer cert contains IP addresses and DNS names in Subject Alternative Name (SAN) field, and the remote IP address matches one of those IP addresses, server just accepts connection without further checking the DNS names.
-  - [Server supports reverse-lookup on wildcard DNS `SAN`](https://github.com/etcd-io/etcd/pull/8281). For instance, if peer cert contains only DNS names (no IP addresses) in Subject Alternative Name (SAN) field, server first reverse-lookups the remote IP address to get a list of names mapping to that address (e.g. `nslookup IPADDR`). Then accepts the connection if those names have a matching name with peer cert's DNS names (either by exact or wildcard match). If none is matched, server forward-lookups each DNS entry in peer cert (e.g. look up `example.default.svc` when the entry is `*.example.default.svc`), and accepts connection only when the host's resolved addresses have the matching IP address with the peer's remote IP address.
-- Add [`etcd --peer-cert-allowed-cn`](https://github.com/etcd-io/etcd/pull/8616) flag.
-  - To support [CommonName(CN) based auth](https://github.com/etcd-io/etcd/issues/8262) for inter peer connection.
-- [Swap priority](https://github.com/etcd-io/etcd/pull/8594) of cert CommonName(CN) and username + password.
-  - To address ["username and password specified in the request should take priority over CN in the cert"](https://github.com/etcd-io/etcd/issues/8584).
-- Protect [lease revoke with auth](https://github.com/etcd-io/etcd/pull/8031).
-- Provide user's role on [auth permission error](https://github.com/etcd-io/etcd/pull/8164).
-- Fix [auth store panic with disabled token](https://github.com/etcd-io/etcd/pull/8695).
-
-### etcd server
-
-- Add [`etcd --experimental-initial-corrupt-check`](https://github.com/etcd-io/etcd/pull/8554) flag to [check cluster database hashes before serving client/peer traffic](https://github.com/etcd-io/etcd/issues/8313).
-  - `etcd --experimental-initial-corrupt-check=false` by default.
-  - v3.4 will enable `--initial-corrupt-check=true` by default.
-- Add [`etcd --experimental-corrupt-check-time`](https://github.com/etcd-io/etcd/pull/8420) flag to [raise corrupt alarm monitoring](https://github.com/etcd-io/etcd/issues/7125).
-  - `etcd --experimental-corrupt-check-time=0s` disabled by default.
-- Add [`etcd --experimental-enable-v2v3`](https://github.com/etcd-io/etcd/pull/8407) flag to [emulate v2 API with v3](https://github.com/etcd-io/etcd/issues/6925).
-  - `etcd --experimental-enable-v2v3=false` by default.
-- Add [`etcd --max-txn-ops`](https://github.com/etcd-io/etcd/pull/7976) flag to [configure maximum number operations in transaction](https://github.com/etcd-io/etcd/issues/7826).
-- Add [`etcd --max-request-bytes`](https://github.com/etcd-io/etcd/pull/7968) flag to [configure maximum client request size](https://github.com/etcd-io/etcd/issues/7923).
-  - If not configured, it defaults to 1.5 MiB.
-- Add [`etcd --client-crl-file`, `--peer-crl-file`](https://github.com/etcd-io/etcd/pull/8124) flags for [Certificate revocation list](https://github.com/etcd-io/etcd/issues/4034).
-- Add [`etcd --peer-cert-allowed-cn`](https://github.com/etcd-io/etcd/pull/8616) flag to support [CN-based auth for inter-peer connection](https://github.com/etcd-io/etcd/issues/8262).
-- Add [`etcd --listen-metrics-urls`](https://github.com/etcd-io/etcd/pull/8242) flag for additional `/metrics` and `/health` endpoints.
-  - Support [additional (non) TLS `/metrics` endpoints for a TLS-enabled cluster](https://github.com/etcd-io/etcd/pull/8282).
-  - e.g. `etcd --listen-metrics-urls=https://localhost:2378,http://localhost:9379` to serve `/metrics` and `/health` on secure port 2378 and insecure port 9379.
-  - Useful for [bypassing critical APIs when monitoring etcd](https://github.com/etcd-io/etcd/issues/8060).
-- Add [`etcd --auto-compaction-mode`](https://github.com/etcd-io/etcd/pull/8123) flag to [support revision-based compaction](https://github.com/etcd-io/etcd/issues/8098).
-- Change `etcd --auto-compaction-retention` flag to [accept string values](https://github.com/etcd-io/etcd/pull/8563) with [finer granularity](https://github.com/etcd-io/etcd/issues/8503).
-  - Now that `etcd --auto-compaction-retention` accepts string values, etcd configuration YAML file `auto-compaction-retention` field must be changed to `string` type.
-  - Previously, `etcd --config-file etcd.config.yaml` can have `auto-compaction-retention: 24` field, now must be `auto-compaction-retention: "24"` or `auto-compaction-retention: "24h"`.
-  - If configured as `--auto-compaction-mode periodic --auto-compaction-retention "24h"`, the time duration value for `etcd --auto-compaction-retention` flag must be valid for [`time.ParseDuration`](https://golang.org/pkg/time/#ParseDuration) function in Go.
-  - e.g. `etcd --auto-compaction-mode=revision --auto-compaction-retention=1000` automatically `Compact` on `"latest revision" - 1000` every 5-minute (when latest revision is 30000, compact on revision 29000).
-  - e.g. `etcd --auto-compaction-mode=periodic --auto-compaction-retention=72h` automatically `Compact` with 72-hour retention windown, for every 7.2-hour.
-  - e.g. `etcd --auto-compaction-mode=periodic --auto-compaction-retention=30m` automatically `Compact` with 30-minute retention windown, for every 3-minute.
-  - Periodic compactor continues to record latest revisions for every 1/10 of given compaction period (e.g. 1-hour when `etcd --auto-compaction-mode=periodic --auto-compaction-retention=10h`).
-  - For every 1/10 of given compaction period, compactor uses the last revision that was fetched before compaction period, to discard historical data.
-  - The retention window of compaction period moves for every 1/10 of given compaction period.
-  - For instance, when hourly writes are 100 and `--auto-compaction-retention=10`, v3.1 compacts revision 1000, 2000, and 3000 for every 10-hour, while v3.2.x, v3.3.0, v3.3.1, and v3.3.2 compact revision 1000, 1100, and 1200 for every 1-hour. Futhermore, when writes per minute are 1000, v3.3.0, v3.3.1, and v3.3.2 with `--auto-compaction-mode=periodic --auto-compaction-retention=30m` compact revision 30000, 33000, and 36000, for every 3-minute with more finer granularity.
-  - Whether compaction succeeds or not, this process repeats for every 1/10 of given compaction period. If compaction succeeds, it just removes compacted revision from historical revision records.
-- Add [`etcd --grpc-keepalive-min-time`, `etcd --grpc-keepalive-interval`, `etcd --grpc-keepalive-timeout`](https://github.com/etcd-io/etcd/pull/8535) flags to configure server-side keepalive policies.
-- Serve [`/health` endpoint as unhealthy](https://github.com/etcd-io/etcd/pull/8272) when [alarm (e.g. `NOSPACE`) is raised or there's no leader](https://github.com/etcd-io/etcd/issues/8207).
-  - Define [`etcdhttp.Health`](https://godoc.org/github.com/coreos/etcd/etcdserver/api/etcdhttp#Health) struct with JSON encoder.
-  - Note that `"health"` field is [`string` type, not `bool`](https://github.com/etcd-io/etcd/pull/9143).
-    - e.g. `{"health":"false"}`, `{"health":"true"}`
-  - [Remove `"errors"` field](https://github.com/etcd-io/etcd/pull/9162) since `v3.3.0-rc.3` (did exist only in `v3.3.0-rc.0`, `v3.3.0-rc.1`, `v3.3.0-rc.2`).
-- Move [logging setup to embed package](https://github.com/etcd-io/etcd/pull/8810)
-  - Disable gRPC server info-level logs by default (can be enabled with `etcd --debug` flag).
-- Use [monotonic time in Go 1.9](https://github.com/etcd-io/etcd/pull/8507) for `lease` package.
-- Warn on [empty hosts in advertise URLs](https://github.com/etcd-io/etcd/pull/8384).
-  - Address [advertise client URLs accepts empty hosts](https://github.com/etcd-io/etcd/issues/8379).
-  - etcd v3.4 will exit on this error.
-    - e.g. `etcd --advertise-client-urls=http://:2379`.
-- Warn on [shadowed environment variables](https://github.com/etcd-io/etcd/pull/8385).
-  - Address [error on shadowed environment variables](https://github.com/etcd-io/etcd/issues/8380).
-  - etcd v3.4 will exit on this error.
-
-### API
-
-- Support [ranges in transaction comparisons](https://github.com/etcd-io/etcd/pull/8025) for [disconnected linearized reads](https://github.com/etcd-io/etcd/issues/7924).
-- Add [nested transactions](https://github.com/etcd-io/etcd/pull/8102) to extend [proxy use cases](https://github.com/etcd-io/etcd/issues/7857).
-- Add [lease comparison target in transaction](https://github.com/etcd-io/etcd/pull/8324).
-- Add [lease list](https://github.com/etcd-io/etcd/pull/8358).
-- Add [hash by revision](https://github.com/etcd-io/etcd/pull/8263) for [better corruption checking against boltdb](https://github.com/etcd-io/etcd/issues/8016).
-
-### client v3
-
-- Add [health balancer](https://github.com/etcd-io/etcd/pull/8545) to fix [watch API hangs](https://github.com/etcd-io/etcd/issues/7247), improve [endpoint switch under network faults](https://github.com/etcd-io/etcd/issues/7941).
-- [Refactor balancer](https://github.com/etcd-io/etcd/pull/8840) and add [client-side keepalive pings](https://github.com/etcd-io/etcd/pull/8199) to handle [network partitions](https://github.com/etcd-io/etcd/issues/8711).
-- Add [`MaxCallSendMsgSize` and `MaxCallRecvMsgSize`](https://github.com/etcd-io/etcd/pull/9047) fields to [`clientv3.Config`](https://godoc.org/github.com/coreos/etcd/clientv3#Config).
-  - Fix [exceeded response size limit error in client-side](https://github.com/etcd-io/etcd/issues/9043).
-  - Address [kubernetes#51099](https://github.com/kubernetes/kubernetes/issues/51099).
-    - In previous versions(v3.2.10, v3.2.11), client response size was limited to only 4 MiB.
-  - `MaxCallSendMsgSize` default value is 2 MiB, if not configured.
-  - `MaxCallRecvMsgSize` default value is `math.MaxInt32`, if not configured.
-- Accept [`Compare_LEASE`](https://github.com/etcd-io/etcd/pull/8324) in [`clientv3.Compare`](https://godoc.org/github.com/coreos/etcd/clientv3#Compare).
-- Add [`LeaseValue` helper](https://github.com/etcd-io/etcd/pull/8488) to `Cmp` `LeaseID` values in `Txn`.
-- Add [`MoveLeader`](https://github.com/etcd-io/etcd/pull/8153) to `Maintenance`.
-- Add [`HashKV`](https://github.com/etcd-io/etcd/pull/8351) to `Maintenance`.
-- Add [`Leases`](https://github.com/etcd-io/etcd/pull/8358) to `Lease`.
-- Add [`clientv3/ordering`](https://github.com/etcd-io/etcd/pull/8092) for enforce [ordering in serialized requests](https://github.com/etcd-io/etcd/issues/7623).
-- Fix ["put at-most-once" violation](https://github.com/etcd-io/etcd/pull/8335).
-- Fix [`WatchResponse.Canceled`](https://github.com/etcd-io/etcd/pull/8283) on [compacted watch request](https://github.com/etcd-io/etcd/issues/8231).
-- Fix [`concurrency/stm` `Put` with serializable snapshot](https://github.com/etcd-io/etcd/pull/8439).
-  - Use store revision from first fetch to resolve write conflicts instead of modified revision.
-
-### etcdctl v3
-
-- Add [`etcdctl --discovery-srv`](https://github.com/etcd-io/etcd/pull/8462) flag.
-- Add [`etcdctl --keepalive-time`, `--keepalive-timeout`](https://github.com/etcd-io/etcd/pull/8663) flags.
-- Add [`etcdctl lease list`](https://github.com/etcd-io/etcd/pull/8358) command.
-- Add [`etcdctl lease keep-alive --once`](https://github.com/etcd-io/etcd/pull/8775) flag.
-- Make [`lease timetolive LEASE_ID`](https://github.com/etcd-io/etcd/issues/9028) on expired lease print [`lease LEASE_ID already expired`](https://github.com/etcd-io/etcd/pull/9047).
-  - <=3.2 prints `lease LEASE_ID granted with TTL(0s), remaining(-1s)`.
-- Add [`etcdctl snapshot restore --wal-dir`](https://github.com/etcd-io/etcd/pull/9124) flag.
-- Add [`etcdctl defrag --data-dir`](https://github.com/etcd-io/etcd/pull/8367) flag.
-- Add [`etcdctl move-leader`](https://github.com/etcd-io/etcd/pull/8153) command.
-- Add [`etcdctl endpoint hashkv`](https://github.com/etcd-io/etcd/pull/8351) command.
-- Add [`etcdctl endpoint --cluster`](https://github.com/etcd-io/etcd/pull/8143) flag, equivalent to [v2 `etcdctl cluster-health`](https://github.com/etcd-io/etcd/issues/8117).
-- Make `etcdctl endpoint health` command terminate with [non-zero exit code on unhealthy status](https://github.com/etcd-io/etcd/pull/8342).
-- Add [`etcdctl lock --ttl`](https://github.com/etcd-io/etcd/pull/8370) flag.
-- Support [`etcdctl watch [key] [range_end] -- [exec-command…]`](https://github.com/etcd-io/etcd/pull/8919), equivalent to [v2 `etcdctl exec-watch`](https://github.com/etcd-io/etcd/issues/8814).
-  - Make `etcdctl watch -- [exec-command]` set environmental variables [`ETCD_WATCH_REVISION`, `ETCD_WATCH_EVENT_TYPE`, `ETCD_WATCH_KEY`, `ETCD_WATCH_VALUE`](https://github.com/etcd-io/etcd/pull/9142) for each event.
-- Support [`etcdctl watch` with environmental variables `ETCDCTL_WATCH_KEY` and `ETCDCTL_WATCH_RANGE_END`](https://github.com/etcd-io/etcd/pull/9142).
-- Enable [`clientv3.WithRequireLeader(context.Context)` for `watch`](https://github.com/etcd-io/etcd/pull/8672) command.
-- Print [`"del"` instead of `"delete"`](https://github.com/etcd-io/etcd/pull/8297) in `txn` interactive mode.
-- Print [`ETCD_INITIAL_ADVERTISE_PEER_URLS` in `member add`](https://github.com/etcd-io/etcd/pull/8332).
-
-### etcdctl v3
-
-- Handle [empty key permission](https://github.com/etcd-io/etcd/pull/8514) in `etcdctl`.
-
-### etcdctl v2
-
-- Add [`etcdctl backup --with-v3`](https://github.com/etcd-io/etcd/pull/8479) flag.
-
-### gRPC Proxy
-
-- Add [`grpc-proxy start --experimental-leasing-prefix`](https://github.com/etcd-io/etcd/pull/8341) flag.
-  - For disconnected linearized reads.
-  - Based on [V system leasing](https://github.com/etcd-io/etcd/issues/6065).
-  - See ["Disconnected consistent reads with etcd" blog post](https://coreos.com/blog/coreos-labs-disconnected-consistent-reads-with-etcd).
-- Add [`grpc-proxy start --experimental-serializable-ordering`](https://github.com/etcd-io/etcd/pull/8315) flag.
-  - To ensure serializable reads have monotonically increasing store revisions across endpoints.
-- Add [`grpc-proxy start --metrics-addr`](https://github.com/etcd-io/etcd/pull/8242) flag for an additional `/metrics` endpoint.
-  - Set `--metrics-addr=http://[HOST]:9379` to serve `/metrics` in insecure port 9379.
-- Serve [`/health` endpoint in grpc-proxy](https://github.com/etcd-io/etcd/pull/8322).
-- Add [`grpc-proxy start --debug`](https://github.com/etcd-io/etcd/pull/8994) flag.
-- Add [`grpc-proxy start --max-send-bytes`](https://github.com/etcd-io/etcd/pull/9250) flag to [configure maximum client request size](https://github.com/etcd-io/etcd/issues/7923).
-- Add [`grpc-proxy start --max-recv-bytes`](https://github.com/etcd-io/etcd/pull/9250) flag to [configure maximum client request size](https://github.com/etcd-io/etcd/issues/7923).
-- Fix [Snapshot API error handling](https://github.com/etcd-io/etcd/commit/dbd16d52fbf81e5fd806d21ff5e9148d5bf203ab).
-- Fix [KV API `PrevKv` flag handling](https://github.com/etcd-io/etcd/pull/8366).
-- Fix [KV API `KeysOnly` flag handling](https://github.com/etcd-io/etcd/pull/8552).
-
-### gRPC gateway
-
-- Replace [gRPC gateway](https://github.com/grpc-ecosystem/grpc-gateway) endpoint `/v3alpha` with [`/v3beta`](https://github.com/etcd-io/etcd/pull/8880).
-  - To deprecate [`/v3alpha`](https://github.com/etcd-io/etcd/issues/8125) in v3.4.
-  - In v3.3, `curl -L http://localhost:2379/v3alpha/kv/put -X POST -d '{"key": "Zm9v", "value": "YmFy"}'` still works as a fallback to `curl -L http://localhost:2379/v3beta/kv/put -X POST -d '{"key": "Zm9v", "value": "YmFy"}'`, but `curl -L http://localhost:2379/v3alpha/kv/put -X POST -d '{"key": "Zm9v", "value": "YmFy"}'` won't work in v3.4. Use `curl -L http://localhost:2379/v3beta/kv/put -X POST -d '{"key": "Zm9v", "value": "YmFy"}'` instead.
-- Support ["authorization" token](https://github.com/etcd-io/etcd/pull/7999).
-- Support [websocket for bi-directional streams](https://github.com/etcd-io/etcd/pull/8257).
-  - Fix [`Watch` API with gRPC gateway](https://github.com/etcd-io/etcd/issues/8237).
-- Upgrade gRPC gateway to [v1.3.0](https://github.com/etcd-io/etcd/issues/8838).
-
-### etcd server
-
-- Fix [backend database in-memory index corruption](https://github.com/etcd-io/etcd/pull/8127) issue on restore (only 3.2.0 is affected).
-- Fix [watch restore from snapshot](https://github.com/etcd-io/etcd/pull/8427).
-- Fix [`mvcc/backend.defragdb` nil-pointer dereference on create bucket failure](https://github.com/etcd-io/etcd/pull/9119).
-- Fix [server crash](https://github.com/etcd-io/etcd/pull/8010) on [invalid transaction request from gRPC gateway](https://github.com/etcd-io/etcd/issues/7889).
-- Prevent [server panic from member update/add](https://github.com/etcd-io/etcd/pull/9174) with [wrong scheme URLs](https://github.com/etcd-io/etcd/issues/9173).
-- Make [peer dial timeout longer](https://github.com/etcd-io/etcd/pull/8599).
-  - See [coreos/etcd-operator#1300](https://github.com/etcd-io/etcd-operator/issues/1300) for more detail.
-- Make server [wait up to request time-out](https://github.com/etcd-io/etcd/pull/8267) with [pending RPCs](https://github.com/etcd-io/etcd/issues/8224).
-- Fix [`grpc.Server` panic on `GracefulStop`](https://github.com/etcd-io/etcd/pull/8987) with [TLS-enabled server](https://github.com/etcd-io/etcd/issues/8916).
-- Fix ["multiple peer URLs cannot start" issue](https://github.com/etcd-io/etcd/issues/8383).
-- Fix server-side auth so [concurrent auth operations do not return old revision error](https://github.com/etcd-io/etcd/pull/8442).
-- Handle [WAL renaming failure on Windows](https://github.com/etcd-io/etcd/pull/8286).
-- Upgrade [`coreos/go-systemd`](https://github.com/coreos/go-systemd/releases) to `v15` (see https://github.com/coreos/go-systemd/releases/tag/v15).
-- [Put back `/v2/machines`](https://github.com/etcd-io/etcd/pull/8062) endpoint for python-etcd wrapper.
-
-### client v2
-
-- [Fail-over v2 client](https://github.com/etcd-io/etcd/pull/8519) to next endpoint on [oneshot failure](https://github.com/etcd-io/etcd/issues/8515).
-
-### Package `raft`
-
-- Add [non-voting member](https://github.com/etcd-io/etcd/pull/8751).
-  - To implement [Raft thesis 4.2.1 Catching up new servers](https://github.com/etcd-io/etcd/issues/8568).
-  - `Learner` node does not vote or promote itself.
-
-### Other
-
-- Support previous two minor versions (see our [new release policy](https://github.com/etcd-io/etcd/pull/8805)).
-- `v3.3.x` is the last release cycle that supports `ACI`.
-  - [AppC was officially suspended](https://github.com/appc/spec#-disclaimer-), as of late 2016.
-  - [`acbuild`](https://github.com/containers/build#this-project-is-currently-unmaintained) is not maintained anymore.
-  - `*.aci` files won't be available from etcd v3.4 release.
-- Add container registry [`gcr.io/etcd-development/etcd`](https://gcr.io/etcd-development/etcd).
-  - [quay.io/coreos/etcd](https://quay.io/coreos/etcd) is still supported as secondary.
-
-### Go
-
-- Require [*Go 1.9+*](https://github.com/etcd-io/etcd/issues/6174).
-- Compile with [*Go 1.9.3*](https://golang.org/doc/devel/release.html#go1.9).
-- Deprecate [`golang.org/x/net/context`](https://github.com/etcd-io/etcd/pull/8511).
-
-
-<hr>
-

CHANGELOG-3.4.md

@@ -1,557 +0,0 @@
-
-
-Previous change logs can be found at [CHANGELOG-3.3](https://github.com/etcd-io/etcd/blob/master/CHANGELOG-3.3.md).
-
-
-<hr>
-
-
-## v3.4.0 (2019-08-30)
-
-See [code changes](https://github.com/etcd-io/etcd/compare/v3.3.0...v3.4.0) and [v3.4 upgrade guide](https://github.com/etcd-io/etcd/blob/master/Documentation/upgrades/upgrade_3_4.md) for any breaking changes.
-
-**Again, before running upgrades from any previous release, please make sure to read change logs below and [v3.4 upgrade guide](https://github.com/etcd-io/etcd/blob/master/Documentation/upgrades/upgrade_3_4.md).**
-
-### Documentation
-
-- etcd now has a new website! Please visit https://etcd.io.
-
-### Improved
-
-- Add Raft learner: [etcd#10725](https://github.com/etcd-io/etcd/pull/10725), [etcd#10727](https://github.com/etcd-io/etcd/pull/10727), [etcd#10730](https://github.com/etcd-io/etcd/pull/10730).
-  - User guide: [runtime-configuration document](https://github.com/etcd-io/etcd/blob/master/Documentation/op-guide/runtime-configuration.md#add-a-new-member-as-learner).
-  - API change: [API reference document](https://github.com/etcd-io/etcd/blob/master/Documentation/dev-guide/api_reference_v3.md).
-  - More details on implementation: [learner design document](https://github.com/etcd-io/etcd/blob/master/Documentation/learning/design-learner.md) and [implementation task list](https://github.com/etcd-io/etcd/issues/10537).
-- Rewrite [client balancer](https://github.com/etcd-io/etcd/pull/9860) with [new gRPC balancer interface](https://github.com/etcd-io/etcd/issues/9106).
-  - Upgrade [gRPC to v1.23.0](https://github.com/etcd-io/etcd/pull/10911).
-  - Improve [client balancer failover against secure endpoints](https://github.com/etcd-io/etcd/pull/10911).
-    - Fix ["kube-apiserver 1.13.x refuses to work when first etcd-server is not available" (kubernetes#72102)](https://github.com/kubernetes/kubernetes/issues/72102).
-  - Fix [gRPC panic "send on closed channel](https://github.com/etcd-io/etcd/issues/9956).
-- Add [backoff on watch retries on transient errors](https://github.com/etcd-io/etcd/pull/9840).
-- Add [jitter to watch progress notify](https://github.com/etcd-io/etcd/pull/9278) to prevent [spikes in `etcd_network_client_grpc_sent_bytes_total`](https://github.com/etcd-io/etcd/issues/9246).
-- Improve [read index wait timeout warning log](https://github.com/etcd-io/etcd/pull/10026), which indicates that local node might have slow network.
-- Improve [slow request apply warning log](https://github.com/etcd-io/etcd/pull/9288).
-  - e.g. `read-only range request "key:\"/a\" range_end:\"/b\" " with result "range_response_count:3 size:96" took too long (97.966µs) to execute`.
-  - Redact [request value field](https://github.com/etcd-io/etcd/pull/9822).
-  - Provide [response size](https://github.com/etcd-io/etcd/pull/9826).
-- Improve ["became inactive" warning log](https://github.com/etcd-io/etcd/pull/10024), which indicates message send to a peer failed.
-- Improve [TLS setup error logging](https://github.com/etcd-io/etcd/pull/9518) to help debug [TLS-enabled cluster configuring issues](https://github.com/etcd-io/etcd/issues/9400).
-- Improve [long-running concurrent read transactions under light write workloads](https://github.com/etcd-io/etcd/pull/9296).
-  - Previously, periodic commit on pending writes blocks incoming read transactions, even if there is no pending write.
-  - Now, periodic commit operation does not block concurrent read transactions, thus improves long-running read transaction performance.
-  - Rebased [etcd#10523](https://github.com/etcd-io/etcd/pull/10523).
-- Improve [Raft Read Index timeout warning messages](https://github.com/etcd-io/etcd/pull/9897).
-- Adjust [election timeout on server restart](https://github.com/etcd-io/etcd/pull/9415) to reduce [disruptive rejoining servers](https://github.com/etcd-io/etcd/issues/9333).
-  - Previously, etcd fast-forwards election ticks on server start, with only one tick left for leader election. This is to speed up start phase, without having to wait until all election ticks elapse. Advancing election ticks is useful for cross datacenter deployments with larger election timeouts. However, it was affecting cluster availability if the last tick elapses before leader contacts the restarted node.
-  - Now, when etcd restarts, it adjusts election ticks with more than one tick left, thus more time for leader to prevent disruptive restart.
-- Add [Raft Pre-Vote feature](https://github.com/etcd-io/etcd/pull/9352) to reduce [disruptive rejoining servers](https://github.com/etcd-io/etcd/issues/9333).
-  - For instance, a flaky(or rejoining) member may drop in and out, and start campaign. This member will end up with a higher term, and ignore all incoming messages with lower term. In this case, a new leader eventually need to get elected, thus disruptive to cluster availability. Raft implements Pre-Vote phase to prevent this kind of disruptions. If enabled, Raft runs an additional phase of election to check if pre-candidate can get enough votes to win an election.
-- Adjust [periodic compaction retention window](https://github.com/etcd-io/etcd/pull/9485).
-  - e.g. `etcd --auto-compaction-mode=revision --auto-compaction-retention=1000` automatically `Compact` on `"latest revision" - 1000` every 5-minute (when latest revision is 30000, compact on revision 29000).
-  - e.g. Previously, `etcd --auto-compaction-mode=periodic --auto-compaction-retention=24h` automatically `Compact` with 24-hour retention windown for every 2.4-hour. Now, `Compact` happens for every 1-hour.
-  - e.g. Previously, `etcd --auto-compaction-mode=periodic --auto-compaction-retention=30m` automatically `Compact` with 30-minute retention windown for every 3-minute. Now, `Compact` happens for every 30-minute.
-  - Periodic compactor keeps recording latest revisions for every compaction period when given period is less than 1-hour, or for every 1-hour when given compaction period is greater than 1-hour (e.g. 1-hour when `etcd --auto-compaction-mode=periodic --auto-compaction-retention=24h`).
-  - For every compaction period or 1-hour, compactor uses the last revision that was fetched before compaction period, to discard historical data.
-  - The retention window of compaction period moves for every given compaction period or hour.
-  - For instance, when hourly writes are 100 and `etcd --auto-compaction-mode=periodic --auto-compaction-retention=24h`, `v3.2.x`, `v3.3.0`, `v3.3.1`, and `v3.3.2` compact revision 2400, 2640, and 2880 for every 2.4-hour, while `v3.3.3` *or later* compacts revision 2400, 2500, 2600 for every 1-hour.
-  - Futhermore, when `etcd --auto-compaction-mode=periodic --auto-compaction-retention=30m` and writes per minute are about 1000, `v3.3.0`, `v3.3.1`, and `v3.3.2` compact revision 30000, 33000, and 36000, for every 3-minute, while `v3.3.3` *or later* compacts revision 30000, 60000, and 90000, for every 30-minute.
-- Improve [lease expire/revoke operation performance](https://github.com/etcd-io/etcd/pull/9418), address [lease scalability issue](https://github.com/etcd-io/etcd/issues/9496).
-- Make [Lease `Lookup` non-blocking with concurrent `Grant`/`Revoke`](https://github.com/etcd-io/etcd/pull/9229).
-- Make etcd server return `raft.ErrProposalDropped` on internal Raft proposal drop in [v3 applier](https://github.com/etcd-io/etcd/pull/9549) and [v2 applier](https://github.com/etcd-io/etcd/pull/9558).
-  - e.g. a node is removed from cluster, or [`raftpb.MsgProp` arrives at current leader while there is an ongoing leadership transfer](https://github.com/etcd-io/etcd/issues/8975).
-- Add [`snapshot`](https://github.com/etcd-io/etcd/pull/9118) package for easier snapshot workflow (see [`godoc.org/github.com/etcd/clientv3/snapshot`](https://godoc.org/github.com/etcd-io/etcd/clientv3/snapshot) for more).
-- Improve [functional tester](https://github.com/etcd-io/etcd/tree/master/functional) coverage: [proxy layer to run network fault tests in CI](https://github.com/etcd-io/etcd/pull/9081), [TLS is enabled both for server and client](https://github.com/etcd-io/etcd/pull/9534), [liveness mode](https://github.com/etcd-io/etcd/issues/9230), [shuffle test sequence](https://github.com/etcd-io/etcd/issues/9381), [membership reconfiguration failure cases](https://github.com/etcd-io/etcd/pull/9564), [disastrous quorum loss and snapshot recover from a seed member](https://github.com/etcd-io/etcd/pull/9565), [embedded etcd](https://github.com/etcd-io/etcd/pull/9572).
-- Improve [index compaction blocking](https://github.com/etcd-io/etcd/pull/9511) by using a copy on write clone to avoid holding the lock for the traversal of the entire index.
-- Update [JWT methods](https://github.com/etcd-io/etcd/pull/9883) to allow for use of any supported signature method/algorithm.
-- Add [Lease checkpointing](https://github.com/etcd-io/etcd/pull/9924) to persist remaining TTLs to the consensus log periodically so that long lived leases progress toward expiry in the presence of leader elections and server restarts.
-  - Enabled by experimental flag "--experimental-enable-lease-checkpoint".
-- Add [gRPC interceptor for debugging logs](https://github.com/etcd-io/etcd/pull/9990); enable `etcd --debug` flag to see per-request debug information.
-- Add [consistency check in snapshot status](https://github.com/etcd-io/etcd/pull/10109). If consistency check on snapshot file fails, `snapshot status` returns `"snapshot file integrity check failed..."` error.
-- Add [`Verify` function to perform corruption check on WAL contents](https://github.com/etcd-io/etcd/pull/10603).
-- Improve [heartbeat send failure logging](https://github.com/etcd-io/etcd/pull/10663).
-- Support [users with no password](https://github.com/etcd-io/etcd/pull/9817) for reducing security risk introduced by leaked password. The users can only be authenticated with CommonName based auth.
-- Add flag `--experimental-peer-skip-client-san-verification` to [skip verification of peer client address](https://github.com/etcd-io/etcd/pull/10524)
-
-### Breaking Changes
-
-- Require [*Go 1.12+*](https://github.com/etcd-io/etcd/pull/10045).
-- Use [Go module](https://github.com/etcd-io/etcd/pull/10063) for dependency management.
-- Move [`"github.com/coreos/etcd"`](https://github.com/etcd-io/etcd/issues/9965) to [`"github.com/etcd-io/etcd"`](https://github.com/etcd-io/etcd/issues/9965).
-  - Change import path to `"go.etcd.io/etcd"`.
-  - e.g. `import "go.etcd.io/etcd/raft"`.
-- Make [`ETCDCTL_API=3 etcdctl` default](https://github.com/etcd-io/etcd/issues/9600).
-  - Now, `etcdctl set foo bar` must be `ETCDCTL_API=2 etcdctl set foo bar`.
-  - Now, `ETCDCTL_API=3 etcdctl put foo bar` could be just `etcdctl put foo bar`.
-- **Remove `etcd --ca-file` flag**, instead [use `etcd --trusted-ca-file`](https://github.com/etcd-io/etcd/pull/9470) (`etcd --ca-file` flag has been marked deprecated since v2.1).
-- **Remove `etcd --peer-ca-file` flag**, instead [use `etcd --peer-trusted-ca-file`](https://github.com/etcd-io/etcd/pull/9470) (`etcd --peer-ca-file` flag has been marked deprecated since v2.1).
-- **Remove `pkg/transport.TLSInfo.CAFile` field**, instead [use `pkg/transport.TLSInfo.TrustedCAFile`](https://github.com/etcd-io/etcd/pull/9470) (`CAFile` field has been marked deprecated since v2.1).
-- Deprecated `latest` [release container](https://console.cloud.google.com/gcr/images/etcd-development/GLOBAL/etcd) tag.
-  - **`docker pull gcr.io/etcd-development/etcd:latest` would not be up-to-date**.
-- Deprecated [minor](https://semver.org/) version [release container](https://console.cloud.google.com/gcr/images/etcd-development/GLOBAL/etcd) tags.
-  - `docker pull gcr.io/etcd-development/etcd:v3.3` would still work.
-  - **`docker pull gcr.io/etcd-development/etcd:v3.4` would not work**.
-  - Use **`docker pull gcr.io/etcd-development/etcd:v3.4.x`** instead, with the exact patch version.
-- Drop [ACIs from official release](https://github.com/etcd-io/etcd/pull/9059).
-  - [AppC was officially suspended](https://github.com/appc/spec#-disclaimer-), as of late 2016.
-  - [`acbuild`](https://github.com/containers/build#this-project-is-currently-unmaintained) is not maintained anymore.
-  - `*.aci` files are not available from `v3.4` release.
-- Exit on [empty hosts in advertise URLs](https://github.com/etcd-io/etcd/pull/8786).
-  - Address [advertise client URLs accepts empty hosts](https://github.com/etcd-io/etcd/issues/8379).
-  - e.g. exit with error on `--advertise-client-urls=http://:2379`.
-  - e.g. exit with error on `--initial-advertise-peer-urls=http://:2380`.
-- Exit on [shadowed environment variables](https://github.com/etcd-io/etcd/pull/9382).
-  - Address [error on shadowed environment variables](https://github.com/etcd-io/etcd/issues/8380).
-  - e.g. exit with error on `ETCD_NAME=abc etcd --name=def`.
-  - e.g. exit with error on `ETCD_INITIAL_CLUSTER_TOKEN=abc etcd --initial-cluster-token=def`.
-  - e.g. exit with error on `ETCDCTL_ENDPOINTS=abc.com ETCDCTL_API=3 etcdctl endpoint health --endpoints=def.com`.
-- Change [`etcdserverpb.AuthRoleRevokePermissionRequest/key,range_end` fields type from `string` to `bytes`](https://github.com/etcd-io/etcd/pull/9433).
-- Deprecating `etcd_debugging_mvcc_db_total_size_in_bytes` Prometheus metric (to be removed in v3.5). Use [`etcd_mvcc_db_total_size_in_bytes`](https://github.com/etcd-io/etcd/pull/9819) instead.
-- Deprecating `etcd_debugging_mvcc_put_total` Prometheus metric (to be removed in v3.5). Use [`etcd_mvcc_put_total`](https://github.com/etcd-io/etcd/pull/10962) instead.
-- Deprecating `etcd_debugging_mvcc_delete_total` Prometheus metric (to be removed in v3.5). Use [`etcd_mvcc_delete_total`](https://github.com/etcd-io/etcd/pull/10962) instead.
-- Deprecating `etcd_debugging_mvcc_range_total` Prometheus metric (to be removed in v3.5). Use [`etcd_mvcc_range_total`](https://github.com/etcd-io/etcd/pull/10968) instead.
-- Deprecating `etcd_debugging_mvcc_txn_total`Prometheus metric  (to be removed in v3.5). Use [`etcd_mvcc_txn_total`](https://github.com/etcd-io/etcd/pull/10968) instead.
-- Rename `etcdserver.ServerConfig.SnapCount` field to `etcdserver.ServerConfig.SnapshotCount`, to be consistent with the flag name `etcd --snapshot-count`.
-- Rename `embed.Config.SnapCount` field to [`embed.Config.SnapshotCount`](https://github.com/etcd-io/etcd/pull/9745), to be consistent with the flag name `etcd --snapshot-count`.
-- Change [`embed.Config.CorsInfo` in `*cors.CORSInfo` type to `embed.Config.CORS` in `map[string]struct{}` type](https://github.com/etcd-io/etcd/pull/9490).
-- Remove [`embed.Config.SetupLogging`](https://github.com/etcd-io/etcd/pull/9572).
-  - Now logger is set up automatically based on [`embed.Config.Logger`, `embed.Config.LogOutputs`, `embed.Config.Debug` fields](https://github.com/etcd-io/etcd/pull/9572).
-- Rename [`etcd --log-output` to `etcd --log-outputs`](https://github.com/etcd-io/etcd/pull/9624) to support multiple log outputs.
-  - **`etcd --log-output`** will be deprecated in v3.5.
-- Rename [**`embed.Config.LogOutput`** to **`embed.Config.LogOutputs`**](https://github.com/etcd-io/etcd/pull/9624) to support multiple log outputs.
-- Change [**`embed.Config.LogOutputs`** type from `string` to `[]string`](https://github.com/etcd-io/etcd/pull/9579) to support multiple log outputs.
-  - Now that `etcd --log-outputs` accepts multiple writers, etcd configuration YAML file `log-outputs` field must be changed to `[]string` type.
-  - Previously, `etcd --config-file etcd.config.yaml` can have `log-outputs: default` field, now must be `log-outputs: [default]`.
-- Deprecating [`etcd --debug`](https://github.com/etcd-io/etcd/pull/10947) flag. Use `etcd --log-level=debug` flag instead.
-  - v3.5 will deprecate `etcd --debug` flag in favor of `etcd --log-level=debug`.
-- Change v3 `etcdctl snapshot` exit codes with [`snapshot` package](https://github.com/etcd-io/etcd/pull/9118/commits/df689f4280e1cce4b9d61300be13ca604d41670a).
-  - Exit on error with exit code 1 (no more exit code 5 or 6 on `snapshot save/restore` commands).
-- Migrate dependency management tool from `glide` to [`golang/dep`](https://github.com/etcd-io/etcd/pull/9155).
-  - <= 3.3 puts `vendor` directory under `cmd/vendor` directory to [prevent conflicting transitive dependencies](https://github.com/etcd-io/etcd/issues/4913).
-  - 3.4 moves `cmd/vendor` directory to `vendor` at repository root.
-  - Remove recursive symlinks in `cmd` directory.
-  - Now `go get/install/build` on `etcd` packages (e.g. `clientv3`, `tools/benchmark`) enforce builds with etcd `vendor` directory.
-- Replace [gRPC gateway](https://github.com/grpc-ecosystem/grpc-gateway) endpoint `/v3beta` with [`/v3`](https://github.com/etcd-io/etcd/pull/9298).
-  - Deprecated [`/v3alpha`](https://github.com/etcd-io/etcd/pull/9298).
-  - To deprecate [`/v3beta`](https://github.com/etcd-io/etcd/issues/9189) in v3.5.
-  - In v3.4, `curl -L http://localhost:2379/v3beta/kv/put -X POST -d '{"key": "Zm9v", "value": "YmFy"}'` still works as a fallback to `curl -L http://localhost:2379/v3/kv/put -X POST -d '{"key": "Zm9v", "value": "YmFy"}'`, but `curl -L http://localhost:2379/v3beta/kv/put -X POST -d '{"key": "Zm9v", "value": "YmFy"}'` won't work in v3.5. Use `curl -L http://localhost:2379/v3/kv/put -X POST -d '{"key": "Zm9v", "value": "YmFy"}'` instead.
-- Change [`wal` package function signatures](https://github.com/etcd-io/etcd/pull/9572) to support [structured logger and logging to file](https://github.com/etcd-io/etcd/issues/9438) in server-side.
-  - Previously, `Open(dirpath string, snap walpb.Snapshot) (*WAL, error)`, now `Open(lg *zap.Logger, dirpath string, snap walpb.Snapshot) (*WAL, error)`.
-  - Previously, `OpenForRead(dirpath string, snap walpb.Snapshot) (*WAL, error)`, now `OpenForRead(lg *zap.Logger, dirpath string, snap walpb.Snapshot) (*WAL, error)`.
-  - Previously, `Repair(dirpath string) bool`, now `Repair(lg *zap.Logger, dirpath string) bool`.
-  - Previously, `Create(dirpath string, metadata []byte) (*WAL, error)`, now `Create(lg *zap.Logger, dirpath string, metadata []byte) (*WAL, error)`.
-- Remove [`pkg/cors` package](https://github.com/etcd-io/etcd/pull/9490).
-- Move internal packages to `etcdserver`.
-  - `"github.com/coreos/etcd/alarm"` to `"go.etcd.io/etcd/etcdserver/api/v3alarm"`.
-  - `"github.com/coreos/etcd/compactor"` to `"go.etcd.io/etcd/etcdserver/api/v3compactor"`.
-  - `"github.com/coreos/etcd/discovery"` to `"go.etcd.io/etcd/etcdserver/api/v2discovery"`.
-  - `"github.com/coreos/etcd/etcdserver/auth"` to `"go.etcd.io/etcd/etcdserver/api/v2auth"`.
-  - `"github.com/coreos/etcd/etcdserver/membership"` to `"go.etcd.io/etcd/etcdserver/api/membership"`.
-  - `"github.com/coreos/etcd/etcdserver/stats"` to `"go.etcd.io/etcd/etcdserver/api/v2stats"`.
-  - `"github.com/coreos/etcd/error"` to `"go.etcd.io/etcd/etcdserver/api/v2error"`.
-  - `"github.com/coreos/etcd/rafthttp"` to `"go.etcd.io/etcd/etcdserver/api/rafthttp"`.
-  - `"github.com/coreos/etcd/snap"` to `"go.etcd.io/etcd/etcdserver/api/snap"`.
-  - `"github.com/coreos/etcd/store"` to `"go.etcd.io/etcd/etcdserver/api/v2store"`.
-- Change [snapshot file permissions](https://github.com/etcd-io/etcd/pull/9977): On Linux, the snapshot file changes from readable by all (mode 0644) to readable by the user only (mode 0600).
-- Change [`pkg/adt.IntervalTree` from `struct` to `interface`](https://github.com/etcd-io/etcd/pull/10959).
-  - See [`pkg/adt` README](https://github.com/etcd-io/etcd/tree/master/pkg/adt) and [`pkg/adt` godoc](https://godoc.org/go.etcd.io/etcd/pkg/adt).
-- Release branch `/version` defines version `3.4.x-pre`, instead of `3.4.y+git`.
-  - Use `3.4.5-pre`, instead of `3.4.4+git`.
-
-### Dependency
-
-- Upgrade [`github.com/coreos/bbolt`](https://github.com/etcd-io/bbolt/releases) from [**`v1.3.1-coreos.6`**](https://github.com/etcd-io/bbolt/releases/tag/v1.3.1-coreos.6) to [`go.etcd.io/bbolt`](https://github.com/etcd-io/bbolt/releases) [**`v1.3.3`**](https://github.com/etcd-io/bbolt/releases/tag/v1.3.3).
-- Upgrade [`google.golang.org/grpc`](https://github.com/grpc/grpc-go/releases) from [**`v1.7.5`**](https://github.com/grpc/grpc-go/releases/tag/v1.7.5) to [**`v1.23.0`**](https://github.com/grpc/grpc-go/releases/tag/v1.23.0).
-- Migrate [`github.com/ugorji/go/codec`](https://github.com/ugorji/go/releases) to [**`github.com/json-iterator/go`**](https://github.com/json-iterator/go), to [regenerate v2 `client`](https://github.com/etcd-io/etcd/pull/9494) (See [#10667](https://github.com/etcd-io/etcd/pull/10667) for more).
-- Migrate [`github.com/ghodss/yaml`](https://github.com/ghodss/yaml/releases) to [**`sigs.k8s.io/yaml`**](https://github.com/kubernetes-sigs/yaml) (See [#10687](https://github.com/etcd-io/etcd/pull/10687) for more).
-- Upgrade [`golang.org/x/crypto`](https://github.com/golang/crypto) from [**`crypto@9419663f5`**](https://github.com/golang/crypto/commit/9419663f5a44be8b34ca85f08abc5fe1be11f8a3) to [**`crypto@0709b304e793`**](https://github.com/golang/crypto/commit/0709b304e793a5edb4a2c0145f281ecdc20838a4).
-- Upgrade [`golang.org/x/net`](https://github.com/golang/net) from [**`net@66aacef3d`**](https://github.com/golang/net/commit/66aacef3dd8a676686c7ae3716979581e8b03c47) to [**`net@adae6a3d119a`**](https://github.com/golang/net/commit/adae6a3d119ae4890b46832a2e88a95adc62b8e7).
-- Upgrade [`golang.org/x/sys`](https://github.com/golang/sys) from [**`sys@ebfc5b463`**](https://github.com/golang/sys/commit/ebfc5b4631820b793c9010c87fd8fef0f39eb082) to [**`sys@56ede360e`**](https://github.com/golang/sys/commit/56ede360ec1c541828fb88741b3f1049406d28f5).
-- Upgrade [`golang.org/x/text`](https://github.com/golang/text) from [**`text@b19bf474d`**](https://github.com/golang/text/commit/b19bf474d317b857955b12035d2c5acb57ce8b01) to [**`v0.3.0`**](https://github.com/golang/text/releases/tag/v0.3.0).
-- Upgrade [`golang.org/x/time`](https://github.com/golang/time) from [**`time@c06e80d93`**](https://github.com/golang/time/commit/c06e80d9300e4443158a03817b8a8cb37d230320) to [**`time@fbb02b229`**](https://github.com/golang/time/commit/fbb02b2291d28baffd63558aa44b4b56f178d650).
-- Upgrade [`github.com/golang/protobuf`](https://github.com/golang/protobuf/releases) from [**`golang/protobuf@1e59b77b5`**](https://github.com/golang/protobuf/commit/1e59b77b52bf8e4b449a57e6f79f21226d571845) to [**`v1.3.2`**](https://github.com/golang/protobuf/releases/tag/v1.3.2).
-- Upgrade [`gopkg.in/yaml.v2`](https://github.com/go-yaml/yaml/releases) from [**`yaml@cd8b52f82`**](https://github.com/go-yaml/yaml/commit/cd8b52f8269e0feb286dfeef29f8fe4d5b397e0b) to [**`yaml@5420a8b67`**](https://github.com/go-yaml/yaml/commit/5420a8b6744d3b0345ab293f6fcba19c978f1183).
-- Upgrade [`github.com/dgrijalva/jwt-go`](https://github.com/dgrijalva/jwt-go/releases) from [**`v3.0.0`**](https://github.com/dgrijalva/jwt-go/releases/tag/v3.0.0) to [**`v3.2.0`**](https://github.com/dgrijalva/jwt-go/releases/tag/v3.2.0).
-- Upgrade [`github.com/soheilhy/cmux`](https://github.com/soheilhy/cmux/releases) from [**`v0.1.3`**](https://github.com/soheilhy/cmux/releases/tag/v0.1.3) to [**`v0.1.4`**](https://github.com/soheilhy/cmux/releases/tag/v0.1.4).
-- Upgrade [`github.com/google/btree`](https://github.com/google/btree/releases) from [**`google/btree@925471ac9`**](https://github.com/google/btree/commit/925471ac9e2131377a91e1595defec898166fe49) to [**`v1.0.0`**](https://github.com/google/btree/releases/tag/v1.0.0).
-- Upgrade [`github.com/spf13/cobra`](https://github.com/spf13/cobra/releases) from [**`spf13/cobra@1c44ec8d3`**](https://github.com/spf13/cobra/commit/1c44ec8d3f1552cac48999f9306da23c4d8a288b) to [**`v0.0.3`**](https://github.com/spf13/cobra/releases/tag/v0.0.3).
-- Upgrade [`github.com/spf13/pflag`](https://github.com/spf13/pflag/releases) from [**`v1.0.0`**](https://github.com/spf13/pflag/releases/tag/v1.0.0) to [**`spf13/pflag@1ce0cc6db`**](https://github.com/spf13/pflag/commit/1ce0cc6db4029d97571db82f85092fccedb572ce).
-- Upgrade [`github.com/coreos/go-systemd`](https://github.com/coreos/go-systemd/releases) from [**`v15`**](https://github.com/coreos/go-systemd/releases/tag/v15) to [**`v17`**](https://github.com/coreos/go-systemd/releases/tag/v17).
-- Upgrade [`github.com/prometheus/client_golang`](https://github.com/prometheus/client_golang/releases) from [**``prometheus/client_golang@5cec1d042``**](https://github.com/prometheus/client_golang/commit/5cec1d0429b02e4323e042eb04dafdb079ddf568) to [**`v1.0.0`**](https://github.com/prometheus/client_golang/releases/tag/v1.0.0).
-- Upgrade [`github.com/grpc-ecosystem/go-grpc-prometheus`](https://github.com/grpc-ecosystem/go-grpc-prometheus/releases) from [**``grpc-ecosystem/go-grpc-prometheus@0dafe0d49``**](https://github.com/grpc-ecosystem/go-grpc-prometheus/commit/0dafe0d496ea71181bf2dd039e7e3f44b6bd11a7) to [**`v1.2.0`**](https://github.com/grpc-ecosystem/go-grpc-prometheus/releases/tag/v1.2.0).
-- Upgrade [`github.com/grpc-ecosystem/grpc-gateway`](https://github.com/grpc-ecosystem/grpc-gateway/releases) from [**`v1.3.1`**](https://github.com/grpc-ecosystem/grpc-gateway/releases/tag/v1.3.1) to [**`v1.4.1`**](https://github.com/grpc-ecosystem/grpc-gateway/releases/tag/v1.4.1).
-- Migrate [`github.com/kr/pty`](https://github.com/kr/pty/releases) to [**`github.com/creack/pty`**](https://github.com/creack/pty/releases/tag/v1.1.7), as the later has replaced the original module.
-- Upgrade [`github.com/gogo/protobuf`](https://github.com/gogo/protobuf/releases) from [**`v1.0.0`**](https://github.com/gogo/protobuf/releases/tag/v1.0.0) to [**`v1.2.1`**](https://github.com/gogo/protobuf/releases/tag/v1.2.1).
-
-### Metrics, Monitoring
-
-Note that any `etcd_debugging_*` metrics are experimental and subject to change.
-
-- Add [`etcd_snap_db_fsync_duration_seconds_count`](https://github.com/etcd-io/etcd/pull/9997) Prometheus metric.
-- Add [`etcd_snap_db_save_total_duration_seconds_bucket`](https://github.com/etcd-io/etcd/pull/9997) Prometheus metric.
-- Add [`etcd_network_snapshot_send_success`](https://github.com/etcd-io/etcd/pull/9997) Prometheus metric.
-- Add [`etcd_network_snapshot_send_failures`](https://github.com/etcd-io/etcd/pull/9997) Prometheus metric.
-- Add [`etcd_network_snapshot_send_total_duration_seconds`](https://github.com/etcd-io/etcd/pull/9997) Prometheus metric.
-- Add [`etcd_network_snapshot_receive_success`](https://github.com/etcd-io/etcd/pull/9997) Prometheus metric.
-- Add [`etcd_network_snapshot_receive_failures`](https://github.com/etcd-io/etcd/pull/9997) Prometheus metric.
-- Add [`etcd_network_snapshot_receive_total_duration_seconds`](https://github.com/etcd-io/etcd/pull/9997) Prometheus metric.
-- Add [`etcd_network_active_peers`](https://github.com/etcd-io/etcd/pull/9762) Prometheus metric.
-  - Let's say `"7339c4e5e833c029"` server `/metrics` returns `etcd_network_active_peers{Local="7339c4e5e833c029",Remote="729934363faa4a24"} 1` and `etcd_network_active_peers{Local="7339c4e5e833c029",Remote="b548c2511513015"} 1`. This indicates that the local node `"7339c4e5e833c029"` currently has two active remote peers `"729934363faa4a24"` and `"b548c2511513015"` in a 3-node cluster. If the node `"b548c2511513015"` is down, the local node `"7339c4e5e833c029"` will show `etcd_network_active_peers{Local="7339c4e5e833c029",Remote="729934363faa4a24"} 1` and `etcd_network_active_peers{Local="7339c4e5e833c029",Remote="b548c2511513015"} 0`.
-- Add [`etcd_network_disconnected_peers_total`](https://github.com/etcd-io/etcd/pull/9762) Prometheus metric.
-  - If a remote peer `"b548c2511513015"` is down, the local node `"7339c4e5e833c029"` server `/metrics` would return `etcd_network_disconnected_peers_total{Local="7339c4e5e833c029",Remote="b548c2511513015"} 1`, while active peer metrics will show `etcd_network_active_peers{Local="7339c4e5e833c029",Remote="729934363faa4a24"} 1` and `etcd_network_active_peers{Local="7339c4e5e833c029",Remote="b548c2511513015"} 0`.
-- Add [`etcd_network_server_stream_failures_total`](https://github.com/etcd-io/etcd/pull/9760) Prometheus metric.
-  - e.g. `etcd_network_server_stream_failures_total{API="lease-keepalive",Type="receive"} 1`
-  - e.g. `etcd_network_server_stream_failures_total{API="watch",Type="receive"} 1`
-- Improve [`etcd_network_peer_round_trip_time_seconds`](https://github.com/etcd-io/etcd/pull/10155) Prometheus metric to track leader heartbeats.
-  - Previously, it only samples the TCP connection for snapshot messages.
-- Increase [`etcd_network_peer_round_trip_time_seconds`](https://github.com/etcd-io/etcd/pull/9762) Prometheus metric histogram upper-bound.
-  - Previously, highest bucket only collects requests taking 0.8192 seconds or more.
-  - Now, highest buckets collect 0.8192 seconds, 1.6384 seconds, and 3.2768 seconds or more.
-- Add [`etcd_server_is_leader`](https://github.com/etcd-io/etcd/pull/9587) Prometheus metric.
-- Add [`etcd_server_id`](https://github.com/etcd-io/etcd/pull/9998) Prometheus metric.
-- Add [`etcd_cluster_version`](https://github.com/etcd-io/etcd/pull/10257) Prometheus metric.
-- Add [`etcd_server_version`](https://github.com/etcd-io/etcd/pull/8960) Prometheus metric.
-  - To replace [Kubernetes `etcd-version-monitor`](https://github.com/etcd-io/etcd/issues/8948).
-- Add [`etcd_server_go_version`](https://github.com/etcd-io/etcd/pull/9957) Prometheus metric.
-- Add [`etcd_server_health_success`](https://github.com/etcd-io/etcd/pull/10156) Prometheus metric.
-- Add [`etcd_server_health_failures`](https://github.com/etcd-io/etcd/pull/10156) Prometheus metric.
-- Add [`etcd_server_read_indexes_failed_total`](https://github.com/etcd-io/etcd/pull/10094) Prometheus metric.
-- Add [`etcd_server_heartbeat_send_failures_total`](https://github.com/etcd-io/etcd/pull/9761) Prometheus metric.
-- Add [`etcd_server_slow_apply_total`](https://github.com/etcd-io/etcd/pull/9761) Prometheus metric.
-- Add [`etcd_server_slow_read_indexes_total`](https://github.com/etcd-io/etcd/pull/9897) Prometheus metric.
-- Add [`etcd_server_quota_backend_bytes`](https://github.com/etcd-io/etcd/pull/9820) Prometheus metric.
-  - Use it with `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.
-- Add [`etcd_mvcc_db_total_size_in_use_in_bytes`](https://github.com/etcd-io/etcd/pull/9256) Prometheus metric.
-  - Use it with `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.
-- Add [`etcd_snap_fsync_duration_seconds`](https://github.com/etcd-io/etcd/pull/9762) Prometheus metric.
-- Add [`etcd_disk_backend_defrag_duration_seconds`](https://github.com/etcd-io/etcd/pull/9761) Prometheus metric.
-- Add [`etcd_mvcc_hash_duration_seconds`](https://github.com/etcd-io/etcd/pull/9761) Prometheus metric.
-- Add [`etcd_mvcc_hash_rev_duration_seconds`](https://github.com/etcd-io/etcd/pull/9761) Prometheus metric.
-- Add [`etcd_debugging_disk_backend_commit_rebalance_duration_seconds`](https://github.com/etcd-io/etcd/pull/9834) Prometheus metric.
-- Add [`etcd_debugging_disk_backend_commit_spill_duration_seconds`](https://github.com/etcd-io/etcd/pull/9834) Prometheus metric.
-- Add [`etcd_debugging_disk_backend_commit_write_duration_seconds`](https://github.com/etcd-io/etcd/pull/9834) Prometheus metric.
-- Add [`etcd_debugging_lease_granted_total`](https://github.com/etcd-io/etcd/pull/9778) Prometheus metric.
-- Add [`etcd_debugging_lease_revoked_total`](https://github.com/etcd-io/etcd/pull/9778) Prometheus metric.
-- Add [`etcd_debugging_lease_renewed_total`](https://github.com/etcd-io/etcd/pull/9778) Prometheus metric.
-- Add [`etcd_debugging_lease_ttl_total`](https://github.com/etcd-io/etcd/pull/9778) Prometheus metric.
-- Add [`etcd_server_is_learner`](https://github.com/etcd-io/etcd/pull/10731) Prometheus metric.
-- Add [`etcd_server_learner_promote_failures`](https://github.com/etcd-io/etcd/pull/10731) Prometheus metric.
-- Add [`etcd_server_learner_promote_successes`](https://github.com/etcd-io/etcd/pull/10731) Prometheus metric.
-- Increase [`etcd_debugging_mvcc_index_compaction_pause_duration_milliseconds`](https://github.com/etcd-io/etcd/pull/9762) Prometheus metric histogram upper-bound.
-  - Previously, highest bucket only collects requests taking 1.024 seconds or more.
-  - Now, highest buckets collect 1.024 seconds, 2.048 seconds, and 4.096 seconds or more.
-- Fix missing [`etcd_network_peer_sent_failures_total`](https://github.com/etcd-io/etcd/pull/9437) Prometheus metric count.
-- Fix [`etcd_debugging_server_lease_expired_total`](https://github.com/etcd-io/etcd/pull/9557) Prometheus metric.
-- Fix [race conditions in v2 server stat collecting](https://github.com/etcd-io/etcd/pull/9562).
-- Change [gRPC proxy to expose etcd server endpoint /metrics](https://github.com/etcd-io/etcd/pull/10618).
-  - The metrics that were exposed via the proxy were not etcd server members but instead the proxy itself.
-- Fix bug where [db_compaction_total_duration_milliseconds metric incorrectly measured duration as 0](https://github.com/etcd-io/etcd/pull/10646).
-- Deprecating `etcd_debugging_mvcc_db_total_size_in_bytes` Prometheus metric (to be removed in v3.5). Use [`etcd_mvcc_db_total_size_in_bytes`](https://github.com/etcd-io/etcd/pull/9819) instead.
-- Deprecating `etcd_debugging_mvcc_put_total` Prometheus metric (to be removed in v3.5). Use [`etcd_mvcc_put_total`](https://github.com/etcd-io/etcd/pull/10962) instead.
-- Deprecating `etcd_debugging_mvcc_delete_total` Prometheus metric (to be removed in v3.5). Use [`etcd_mvcc_delete_total`](https://github.com/etcd-io/etcd/pull/10962) instead.
-- Deprecating `etcd_debugging_mvcc_range_total` Prometheus metric (to be removed in v3.5). Use [`etcd_mvcc_range_total`](https://github.com/etcd-io/etcd/pull/10968) instead.
-- Deprecating `etcd_debugging_mvcc_txn_total`Prometheus metric  (to be removed in v3.5). Use [`etcd_mvcc_txn_total`](https://github.com/etcd-io/etcd/pull/10968) instead.
-
-### Security, Authentication
-
-See [security doc](https://github.com/etcd-io/etcd/blob/master/Documentation/op-guide/security.md) for more details.
-
-- Support TLS cipher suite whitelisting.
-  - To block [weak cipher suites](https://github.com/etcd-io/etcd/issues/8320).
-  - TLS handshake fails when client hello is requested with invalid cipher suites.
-  - Add [`etcd --cipher-suites`](https://github.com/etcd-io/etcd/pull/9801) flag.
-  - If empty, Go auto-populates the list.
-- Add [`etcd --host-whitelist`](https://github.com/etcd-io/etcd/pull/9372) flag, [`etcdserver.Config.HostWhitelist`](https://github.com/etcd-io/etcd/pull/9372), and [`embed.Config.HostWhitelist`](https://github.com/etcd-io/etcd/pull/9372), to prevent ["DNS Rebinding"](https://en.wikipedia.org/wiki/DNS_rebinding) attack.
-  - Any website can simply create an authorized DNS name, and direct DNS to `"localhost"` (or any other address). Then, all HTTP endpoints of etcd server listening on `"localhost"` becomes accessible, thus vulnerable to [DNS rebinding attacks (CVE-2018-5702)](https://bugs.chromium.org/p/project-zero/issues/detail?id=1447#c2).
-  - Client origin enforce policy works as follow:
-    - If client connection is secure via HTTPS, allow any hostnames..
-    - If client connection is not secure and `"HostWhitelist"` is not empty, only allow HTTP requests whose Host field is listed in whitelist.
-  - By default, `"HostWhitelist"` is `"*"`, which means insecure server allows all client HTTP requests.
-  - Note that the client origin policy is enforced whether authentication is enabled or not, for tighter controls.
-  - When specifying hostnames, loopback addresses are not added automatically. To allow loopback interfaces, add them to whitelist manually (e.g. `"localhost"`, `"127.0.0.1"`, etc.).
-  - e.g. `etcd --host-whitelist example.com`, then the server will reject all HTTP requests whose Host field is not `example.com` (also rejects requests to `"localhost"`).
-- Support [`etcd --cors`](https://github.com/etcd-io/etcd/pull/9490) in v3 HTTP requests (gRPC gateway).
-- Support [`ttl` field for `etcd` Authentication JWT token](https://github.com/etcd-io/etcd/pull/8302).
-  - e.g. `etcd --auth-token jwt,pub-key=<pub key path>,priv-key=<priv key path>,sign-method=<sign method>,ttl=5m`.
-- Allow empty token provider in [`etcdserver.ServerConfig.AuthToken`](https://github.com/etcd-io/etcd/pull/9369).
-- Fix [TLS reload](https://github.com/etcd-io/etcd/pull/9570) when [certificate SAN field only includes IP addresses but no domain names](https://github.com/etcd-io/etcd/issues/9541).
-  - In Go, server calls `(*tls.Config).GetCertificate` for TLS reload if and only if server's `(*tls.Config).Certificates` field is not empty, or `(*tls.ClientHelloInfo).ServerName` is not empty with a valid SNI from the client. Previously, etcd always populates `(*tls.Config).Certificates` on the initial client TLS handshake, as non-empty. Thus, client was always expected to supply a matching SNI in order to pass the TLS verification and to trigger `(*tls.Config).GetCertificate` to reload TLS assets.
-  - However, a certificate whose SAN field does [not include any domain names but only IP addresses](https://github.com/etcd-io/etcd/issues/9541) would request `*tls.ClientHelloInfo` with an empty `ServerName` field, thus failing to trigger the TLS reload on initial TLS handshake; this becomes a problem when expired certificates need to be replaced online.
-  - Now, `(*tls.Config).Certificates` is created empty on initial TLS client handshake, first to trigger `(*tls.Config).GetCertificate`, and then to populate rest of the certificates on every new TLS connection, even when client SNI is empty (e.g. cert only includes IPs).
-
-### etcd server
-
-- Add [`rpctypes.ErrLeaderChanged`](https://github.com/etcd-io/etcd/pull/10094).
-  - Now linearizable requests with read index would fail fast when there is a leadership change, instead of waiting until context timeout.
-- Add [`etcd --initial-election-tick-advance`](https://github.com/etcd-io/etcd/pull/9591) flag to configure initial election tick fast-forward.
-  - By default, `etcd --initial-election-tick-advance=true`, then local member fast-forwards election ticks to speed up "initial" leader election trigger.
-  - This benefits the case of larger election ticks. For instance, cross datacenter deployment may require longer election timeout of 10-second. If true, local node does not need wait up to 10-second. Instead, forwards its election ticks to 8-second, and have only 2-second left before leader election.
-  - Major assumptions are that: cluster has no active leader thus advancing ticks enables faster leader election. Or cluster already has an established leader, and rejoining follower is likely to receive heartbeats from the leader after tick advance and before election timeout.
-  - However, when network from leader to rejoining follower is congested, and the follower does not receive leader heartbeat within left election ticks, disruptive election has to happen thus affecting cluster availabilities.
-  - Now, this can be disabled by setting `etcd --initial-election-tick-advance=false`.
-  - Disabling this would slow down initial bootstrap process for cross datacenter deployments. Make tradeoffs by configuring `etcd --initial-election-tick-advance` at the cost of slow initial bootstrap.
-  - If single-node, it advances ticks regardless.
-  - Address [disruptive rejoining follower node](https://github.com/etcd-io/etcd/issues/9333).
-- Add [`etcd --pre-vote`](https://github.com/etcd-io/etcd/pull/9352) flag to enable to run an additional Raft election phase.
-  - For instance, a flaky(or rejoining) member may drop in and out, and start campaign. This member will end up with a higher term, and ignore all incoming messages with lower term. In this case, a new leader eventually need to get elected, thus disruptive to cluster availability. Raft implements Pre-Vote phase to prevent this kind of disruptions. If enabled, Raft runs an additional phase of election to check if pre-candidate can get enough votes to win an election.
-  - `etcd --pre-vote=false` by default.
-  - v3.5 will enable `etcd --pre-vote=true` by default.
-- Add [`etcd --discovery-srv-name`](https://github.com/etcd-io/etcd/pull/8690) flag to support custom DNS SRV name with discovery.
-  - If not given, etcd queries `_etcd-server-ssl._tcp.[YOUR_HOST]` and `_etcd-server._tcp.[YOUR_HOST]`.
-  - If `etcd --discovery-srv-name="foo"`, then query `_etcd-server-ssl-foo._tcp.[YOUR_HOST]` and `_etcd-server-foo._tcp.[YOUR_HOST]`.
-  - Useful for operating multiple etcd clusters under the same domain.
-- Support TLS cipher suite whitelisting.
-  - To block [weak cipher suites](https://github.com/etcd-io/etcd/issues/8320).
-  - TLS handshake fails when client hello is requested with invalid cipher suites.
-  - Add [`etcd --cipher-suites`](https://github.com/etcd-io/etcd/pull/9801) flag.
-  - If empty, Go auto-populates the list.
-- Support [`etcd --cors`](https://github.com/etcd-io/etcd/pull/9490) in v3 HTTP requests (gRPC gateway).
-- Rename [`etcd --log-output` to `etcd --log-outputs`](https://github.com/etcd-io/etcd/pull/9624) to support multiple log outputs.
-  - **`etcd --log-output` will be deprecated in v3.5**.
-- Add [`etcd --logger`](https://github.com/etcd-io/etcd/pull/9572) flag to support [structured logger and multiple log outputs](https://github.com/etcd-io/etcd/issues/9438) in server-side.
-  - **`etcd --logger=capnslog` will be deprecated in v3.5**.
-  - Main motivation is to promote automated etcd monitoring, rather than looking back server logs when it starts breaking. Future development will make etcd log as few as possible, and make etcd easier to monitor with metrics and alerts.
-  - `etcd --logger=capnslog --log-outputs=default` is the default setting and same as previous etcd server logging format.
-  - `etcd --logger=zap --log-outputs=default` is not supported when `etcd --logger=zap`.
-    - Use `etcd --logger=zap --log-outputs=stderr` instead.
-    - Or, use `etcd --logger=zap --log-outputs=systemd/journal` to send logs to the local systemd journal.
-    - Previously, if etcd parent process ID (PPID) is 1 (e.g. run with systemd), `etcd --logger=capnslog --log-outputs=default` redirects server logs to local systemd journal. And if write to journald fails, it writes to `os.Stderr` as a fallback.
-    - However, even with PPID 1, it can fail to dial systemd journal (e.g. run embedded etcd with Docker container). Then, [every single log write will fail](https://github.com/etcd-io/etcd/pull/9729) and fall back to `os.Stderr`, which is inefficient.
-    - To avoid this problem, systemd journal logging must be configured manually.
-  - `etcd --logger=zap --log-outputs=stderr` will log server operations in [JSON-encoded format](https://godoc.org/go.uber.org/zap#NewProductionEncoderConfig) and writes logs to `os.Stderr`. Use this to override journald log redirects.
-  - `etcd --logger=zap --log-outputs=stdout` will log server operations in [JSON-encoded format](https://godoc.org/go.uber.org/zap#NewProductionEncoderConfig) and writes logs to `os.Stdout` Use this to override journald log redirects.
-  - `etcd --logger=zap --log-outputs=a.log` will log server operations in [JSON-encoded format](https://godoc.org/go.uber.org/zap#NewProductionEncoderConfig) and writes logs to the specified file `a.log`.
-  - `etcd --logger=zap --log-outputs=a.log,b.log,c.log,stdout` [writes server logs to multiple files `a.log`, `b.log` and `c.log` at the same time](https://github.com/etcd-io/etcd/pull/9579) and outputs to `os.Stderr`, in [JSON-encoded format](https://godoc.org/go.uber.org/zap#NewProductionEncoderConfig).
-  - `etcd --logger=zap --log-outputs=/dev/null` will discard all server logs.
-- Add [`etcd --log-level`](https://github.com/etcd-io/etcd/pull/10947) flag to support log level.
-  - v3.5 will deprecate `etcd --debug` flag in favor of `etcd --log-level=debug`.
-- Add [`etcd --backend-batch-limit`](https://github.com/etcd-io/etcd/pull/10283) flag.
-- Add [`etcd --backend-batch-interval`](https://github.com/etcd-io/etcd/pull/10283) flag.
-- Fix [`mvcc` "unsynced" watcher restore operation](https://github.com/etcd-io/etcd/pull/9281).
-  - "unsynced" watcher is watcher that needs to be in sync with events that have happened.
-  - That is, "unsynced" watcher is the slow watcher that was requested on old revision.
-  - "unsynced" watcher restore operation was not correctly populating its underlying watcher group.
-  - Which possibly causes [missing events from "unsynced" watchers](https://github.com/etcd-io/etcd/issues/9086).
-  - A node gets network partitioned with a watcher on a future revision, and falls behind receiving a leader snapshot after partition gets removed. When applying this snapshot, etcd watch storage moves current synced watchers to unsynced since sync watchers might have become stale during network partition. And reset synced watcher group to restart watcher routines. Previously, there was a bug when moving from synced watcher group to unsynced, thus client would miss events when the watcher was requested to the network-partitioned node.
-- Fix [`mvcc` server panic from restore operation](https://github.com/etcd-io/etcd/pull/9775).
-  - Let's assume that a watcher had been requested with a future revision X and sent to node A that became network-partitioned thereafter. Meanwhile, cluster makes progress. Then when the partition gets removed, the leader sends a snapshot to node A. Previously if the snapshot's latest revision is still lower than the watch revision X,  **etcd server panicked** during snapshot restore operation.
-  - Now, this server-side panic has been fixed.
-- Fix [server panic on invalid Election Proclaim/Resign HTTP(S) requests](https://github.com/etcd-io/etcd/pull/9379).
-  - Previously, wrong-formatted HTTP requests to Election API could trigger panic in etcd server.
-  - e.g. `curl -L http://localhost:2379/v3/election/proclaim -X POST -d '{"value":""}'`, `curl -L http://localhost:2379/v3/election/resign -X POST -d '{"value":""}'`.
-- Fix [revision-based compaction retention parsing](https://github.com/etcd-io/etcd/pull/9339).
-  - Previously, `etcd --auto-compaction-mode revision --auto-compaction-retention 1` was [translated to revision retention 3600000000000](https://github.com/etcd-io/etcd/issues/9337).
-  - Now, `etcd --auto-compaction-mode revision --auto-compaction-retention 1` is correctly parsed as revision retention 1.
-- Prevent [overflow by large `TTL` values for `Lease` `Grant`](https://github.com/etcd-io/etcd/pull/9399).
-  - `TTL` parameter to `Grant` request is unit of second.
-  - Leases with too large `TTL` values exceeding `math.MaxInt64` [expire in unexpected ways](https://github.com/etcd-io/etcd/issues/9374).
-  - Server now returns `rpctypes.ErrLeaseTTLTooLarge` to client, when the requested `TTL` is larger than *9,000,000,000 seconds* (which is >285 years).
-  - Again, etcd `Lease` is meant for short-periodic keepalives or sessions, in the range of seconds or minutes. Not for hours or days!
-- Fix [expired lease revoke](https://github.com/etcd-io/etcd/pull/10693).
-  - Fix ["the key is not deleted when the bound lease expires"](https://github.com/etcd-io/etcd/issues/10686).
-- Enable etcd server [`raft.Config.CheckQuorum` when starting with `ForceNewCluster`](https://github.com/etcd-io/etcd/pull/9347).
-- Allow [non-WAL files in `etcd --wal-dir` directory](https://github.com/etcd-io/etcd/pull/9743).
-  - Previously, existing files such as [`lost+found`](https://github.com/etcd-io/etcd/issues/7287) in WAL directory prevent etcd server boot.
-  - Now, WAL directory that contains only `lost+found` or a file that's not suffixed with `.wal` is considered non-initialized.
-- Fix [`ETCD_CONFIG_FILE` env variable parsing in `etcd`](https://github.com/etcd-io/etcd/pull/10762).
-- Fix [race condition in `rafthttp` transport pause/resume](https://github.com/etcd-io/etcd/pull/10826).
-- Fix [server crash from creating an empty role](https://github.com/etcd-io/etcd/pull/10907).
-  - Previously, creating a role with an empty name crashed etcd server with an error code `Unavailable`.
-  - Now, creating a role with an empty name is not allowed with an error code `InvalidArgument`.
-
-### API
-
-- Add `isLearner` field to `etcdserverpb.Member`, `etcdserverpb.MemberAddRequest` and `etcdserverpb.StatusResponse` as part of [raft learner implementation](https://github.com/etcd-io/etcd/pull/10725).
-- Add `MemberPromote` rpc to `etcdserverpb.Cluster` interface and the corresponding `MemberPromoteRequest` and `MemberPromoteResponse` as part of [raft learner implementation](https://github.com/etcd-io/etcd/pull/10725).
-- Add [`snapshot`](https://github.com/etcd-io/etcd/pull/9118) package for snapshot restore/save operations (see [`godoc.org/github.com/etcd/clientv3/snapshot`](https://godoc.org/github.com/coreos/etcd/clientv3/snapshot) for more).
-- Add [`watch_id` field to `etcdserverpb.WatchCreateRequest`](https://github.com/etcd-io/etcd/pull/9065) to allow user-provided watch ID to `mvcc`.
-  - Corresponding `watch_id` is returned via `etcdserverpb.WatchResponse`, if any.
-- Add [`fragment` field to `etcdserverpb.WatchCreateRequest`](https://github.com/etcd-io/etcd/pull/9291) to request etcd server to [split watch events](https://github.com/etcd-io/etcd/issues/9294) when the total size of events exceeds `etcd --max-request-bytes` flag value plus gRPC-overhead 512 bytes.
-  - The default server-side request bytes limit is `embed.DefaultMaxRequestBytes` which is 1.5 MiB plus gRPC-overhead 512 bytes.
-  - If watch response events exceed this server-side request limit and watch request is created with `fragment` field `true`, the server will split watch events into a set of chunks, each of which is a subset of watch events below server-side request limit.
-  - Useful when client-side has limited bandwidths.
-  - For example, watch response contains 10 events, where each event is 1 MiB. And server `etcd --max-request-bytes` flag value is 1 MiB. Then, server will send 10 separate fragmented events to the client.
-  - For example, watch response contains 5 events, where each event is 2 MiB. And server `etcd --max-request-bytes` flag value is 1 MiB and `clientv3.Config.MaxCallRecvMsgSize` is 1 MiB. Then, server will try to send 5 separate fragmented events to the client, and the client will error with `"code = ResourceExhausted desc = grpc: received message larger than max (...)"`.
-  - Client must implement fragmented watch event merge (which `clientv3` does in etcd v3.4).
-- Add [`raftAppliedIndex` field to `etcdserverpb.StatusResponse`](https://github.com/etcd-io/etcd/pull/9176) for current Raft applied index.
-- Add [`errors` field to `etcdserverpb.StatusResponse`](https://github.com/etcd-io/etcd/pull/9206) for server-side error.
-  - e.g. `"etcdserver: no leader", "NOSPACE", "CORRUPT"`
-- Add [`dbSizeInUse` field to `etcdserverpb.StatusResponse`](https://github.com/etcd-io/etcd/pull/9256) for actual DB size after compaction.
-- Add [`WatchRequest.WatchProgressRequest`](https://github.com/etcd-io/etcd/pull/9869).
-  - To manually trigger broadcasting watch progress event (empty watch response with latest header) to all associated watch streams.
-  - Think of it as `WithProgressNotify` that can be triggered manually.
-
-Note: **v3.5 will deprecate `etcd --log-package-levels` flag for `capnslog`**; `etcd --logger=zap --log-outputs=stderr` will the default. **v3.5 will deprecate `[CLIENT-URL]/config/local/log` endpoint.**
-
-### Package `embed`
-
-- Add [`embed.Config.CipherSuites`](https://github.com/etcd-io/etcd/pull/9801) to specify a list of supported cipher suites for TLS handshake between client/server  and peers.
-  - If empty, Go auto-populates the list.
-  - Both `embed.Config.ClientTLSInfo.CipherSuites` and `embed.Config.CipherSuites` cannot be non-empty at the same time.
-  - If not empty, specify either `embed.Config.ClientTLSInfo.CipherSuites` or `embed.Config.CipherSuites`.
-- Add [`embed.Config.InitialElectionTickAdvance`](https://github.com/etcd-io/etcd/pull/9591) to enable/disable initial election tick fast-forward.
-  - `embed.NewConfig()` would return `*embed.Config` with `InitialElectionTickAdvance` as true by default.
-- Define [`embed.CompactorModePeriodic`](https://godoc.org/github.com/etcd-io/etcd/embed#pkg-variables) for `compactor.ModePeriodic`.
-- Define [`embed.CompactorModeRevision`](https://godoc.org/github.com/etcd-io/etcd/embed#pkg-variables) for `compactor.ModeRevision`.
-- Change [`embed.Config.CorsInfo` in `*cors.CORSInfo` type to `embed.Config.CORS` in `map[string]struct{}` type](https://github.com/etcd-io/etcd/pull/9490).
-- Remove [`embed.Config.SetupLogging`](https://github.com/etcd-io/etcd/pull/9572).
-  - Now logger is set up automatically based on [`embed.Config.Logger`, `embed.Config.LogOutputs`, `embed.Config.Debug` fields](https://github.com/etcd-io/etcd/pull/9572).
-- Add [`embed.Config.Logger`](https://github.com/etcd-io/etcd/pull/9518) to support [structured logger `zap`](https://github.com/uber-go/zap) in server-side.
-- Add [`embed.Config.LogLevel`](https://github.com/etcd-io/etcd/pull/10947).
-- Rename `embed.Config.SnapCount` field to [`embed.Config.SnapshotCount`](https://github.com/etcd-io/etcd/pull/9745), to be consistent with the flag name `etcd --snapshot-count`.
-- Rename [**`embed.Config.LogOutput`** to **`embed.Config.LogOutputs`**](https://github.com/etcd-io/etcd/pull/9624) to support multiple log outputs.
-- Change [**`embed.Config.LogOutputs`** type from `string` to `[]string`](https://github.com/etcd-io/etcd/pull/9579) to support multiple log outputs.
-- Add [`embed.Config.BackendBatchLimit`](https://github.com/etcd-io/etcd/pull/10283) field.
-- Add [`embed.Config.BackendBatchInterval`](https://github.com/etcd-io/etcd/pull/10283) field.
-
-### Package `integration`
-
-- Add [`CLUSTER_DEBUG` to enable test cluster logging](https://github.com/etcd-io/etcd/pull/9678).
-  - Deprecated `capnslog` in integration tests.
-
-### client v3
-
-- Add [`MemberAddAsLearner`](https://github.com/etcd-io/etcd/pull/10725) to `Clientv3.Cluster` interface. This API is used to add a learner member to etcd cluster.
-- Add [`MemberPromote`](https://github.com/etcd-io/etcd/pull/10727) to `Clientv3.Cluster` interface. This API is used to promote a learner member in etcd cluster.
-- Client may receive [`rpctypes.ErrLeaderChanged`](https://github.com/etcd-io/etcd/pull/10094) from server.
-  - Now linearizable requests with read index would fail fast when there is a leadership change, instead of waiting until context timeout.
-- Add [`WithFragment` `OpOption`](https://github.com/etcd-io/etcd/pull/9291) to support [watch events fragmentation](https://github.com/etcd-io/etcd/issues/9294) when the total size of events exceeds `etcd --max-request-bytes` flag value plus gRPC-overhead 512 bytes.
-  - Watch fragmentation is disabled by default.
-  - The default server-side request bytes limit is `embed.DefaultMaxRequestBytes` which is 1.5 MiB plus gRPC-overhead 512 bytes.
-  - If watch response events exceed this server-side request limit and watch request is created with `fragment` field `true`, the server will split watch events into a set of chunks, each of which is a subset of watch events below server-side request limit.
-  - Useful when client-side has limited bandwidths.
-  - For example, watch response contains 10 events, where each event is 1 MiB. And server `etcd --max-request-bytes` flag value is 1 MiB. Then, server will send 10 separate fragmented events to the client.
-  - For example, watch response contains 5 events, where each event is 2 MiB. And server `etcd --max-request-bytes` flag value is 1 MiB and `clientv3.Config.MaxCallRecvMsgSize` is 1 MiB. Then, server will try to send 5 separate fragmented events to the client, and the client will error with `"code = ResourceExhausted desc = grpc: received message larger than max (...)"`.
-- Add [`Watcher.RequestProgress` method](https://github.com/etcd-io/etcd/pull/9869).
-  - To manually trigger broadcasting watch progress event (empty watch response with latest header) to all associated watch streams.
-  - Think of it as `WithProgressNotify` that can be triggered manually.
-- Fix [lease keepalive interval updates when response queue is full](https://github.com/etcd-io/etcd/pull/9952).
-  - If `<-chan *clientv3LeaseKeepAliveResponse` from `clientv3.Lease.KeepAlive` was never consumed or channel is full, client was [sending keepalive request every 500ms](https://github.com/etcd-io/etcd/issues/9911) instead of expected rate of every "TTL / 3" duration.
-- Change [snapshot file permissions](https://github.com/etcd-io/etcd/pull/9977): On Linux, the snapshot file changes from readable by all (mode 0644) to readable by the user only (mode 0600).
-- Client may choose to send keepalive pings to server using [`PermitWithoutStream`](https://github.com/etcd-io/etcd/pull/10146).
-  - By setting `PermitWithoutStream` to true, client can send keepalive pings to server without any active streams(RPCs). In other words, it allows sending keepalive pings with unary or simple RPC calls.
-  - `PermitWithoutStream` is set to false by default.
-- Fix logic on [release lock key if cancelled](https://github.com/etcd-io/etcd/pull/10153) in `clientv3/concurrency` package.
-- Fix [`(*Client).Endpoints()` method race condition](https://github.com/etcd-io/etcd/pull/10595).
-
-### etcdctl v3
-
-- Make [`ETCDCTL_API=3 etcdctl` default](https://github.com/etcd-io/etcd/issues/9600).
-  - Now, `etcdctl set foo bar` must be `ETCDCTL_API=2 etcdctl set foo bar`.
-  - Now, `ETCDCTL_API=3 etcdctl put foo bar` could be just `etcdctl put foo bar`.
-- Add [`etcdctl member add --learner` and `etcdctl member promote`](https://github.com/etcd-io/etcd/pull/10725) to add and promote raft learner member in etcd cluster.
-- Add [`etcdctl --password`](https://github.com/etcd-io/etcd/pull/9730) flag.
-  - To support [`:` character in user name](https://github.com/etcd-io/etcd/issues/9691).
-  - e.g. `etcdctl --user user --password password get foo`
-- Add [`etcdctl user add --new-user-password`](https://github.com/etcd-io/etcd/pull/9730) flag.
-- Add [`etcdctl check datascale`](https://github.com/etcd-io/etcd/pull/9185) command.
-- Add [`etcdctl check datascale --auto-compact, --auto-defrag`](https://github.com/etcd-io/etcd/pull/9351) flags.
-- Add [`etcdctl check perf --auto-compact, --auto-defrag`](https://github.com/etcd-io/etcd/pull/9330) flags.
-- Add [`etcdctl defrag --cluster`](https://github.com/etcd-io/etcd/pull/9390) flag.
-- Add ["raft applied index" field to `endpoint status`](https://github.com/etcd-io/etcd/pull/9176).
-- Add ["errors" field to `endpoint status`](https://github.com/etcd-io/etcd/pull/9206).
-- Add [`etcdctl endpoint health --write-out` support](https://github.com/etcd-io/etcd/pull/9540).
-  - Previously, [`etcdctl endpoint health --write-out json` did not work](https://github.com/etcd-io/etcd/issues/9532).
-- Add [missing newline in `etcdctl endpoint health`](https://github.com/etcd-io/etcd/pull/10793).
-- Fix [`etcdctl watch [key] [range_end] -- [exec-command…]`](https://github.com/etcd-io/etcd/pull/9688) parsing.
-  - Previously,  `ETCDCTL_API=3 etcdctl watch foo -- echo watch event received` panicked.
-- Fix [`etcdctl move-leader` command for TLS-enabled endpoints](https://github.com/etcd-io/etcd/pull/9807).
-- Add [`progress` command to `etcdctl watch --interactive`](https://github.com/etcd-io/etcd/pull/9869).
-  - To manually trigger broadcasting watch progress event (empty watch response with latest header) to all associated watch streams.
-  - Think of it as `WithProgressNotify` that can be triggered manually.
-- Add [timeout](https://github.com/etcd-io/etcd/pull/10301) to `etcdctl snapshot
-  save`.
-  - User can specify timeout of `etcdctl snapshot save` command using flag `--command-timeout`.
-  - Fix etcdctl to [strip out insecure endpoints from DNS SRV records when using discovery](https://github.com/etcd-io/etcd/pull/10443)
-
-### gRPC proxy
-
-- Fix [etcd server panic from restore operation](https://github.com/etcd-io/etcd/pull/9775).
-  - Let's assume that a watcher had been requested with a future revision X and sent to node A that became network-partitioned thereafter. Meanwhile, cluster makes progress. Then when the partition gets removed, the leader sends a snapshot to node A. Previously if the snapshot's latest revision is still lower than the watch revision X,  **etcd server panicked** during snapshot restore operation.
-  - Especially, gRPC proxy was affected, since it detects a leader loss with a key `"proxy-namespace__lostleader"` and a watch revision `"int64(math.MaxInt64 - 2)"`.
-  - Now, this server-side panic has been fixed.
-- Fix [memory leak in cache layer](https://github.com/etcd-io/etcd/pull/10327).
-- Change [gRPC proxy to expose etcd server endpoint /metrics](https://github.com/etcd-io/etcd/pull/10618).
-  - The metrics that were exposed via the proxy were not etcd server members but instead the proxy itself.
-
-### gRPC gateway
-
-- Replace [gRPC gateway](https://github.com/grpc-ecosystem/grpc-gateway) endpoint `/v3beta` with [`/v3`](https://github.com/etcd-io/etcd/pull/9298).
-  - Deprecated [`/v3alpha`](https://github.com/etcd-io/etcd/pull/9298).
-  - To deprecate [`/v3beta`](https://github.com/etcd-io/etcd/issues/9189) in v3.5.
-  - In v3.4, `curl -L http://localhost:2379/v3beta/kv/put -X POST -d '{"key": "Zm9v", "value": "YmFy"}'` still works as a fallback to `curl -L http://localhost:2379/v3/kv/put -X POST -d '{"key": "Zm9v", "value": "YmFy"}'`, but `curl -L http://localhost:2379/v3beta/kv/put -X POST -d '{"key": "Zm9v", "value": "YmFy"}'` won't work in v3.5. Use `curl -L http://localhost:2379/v3/kv/put -X POST -d '{"key": "Zm9v", "value": "YmFy"}'` instead.
-- Add API endpoints [`/{v3beta,v3}/lease/leases, /{v3beta,v3}/lease/revoke, /{v3beta,v3}/lease/timetolive`](https://github.com/etcd-io/etcd/pull/9450).
-  - To deprecate [`/{v3beta,v3}/kv/lease/leases, /{v3beta,v3}/kv/lease/revoke, /{v3beta,v3}/kv/lease/timetolive`](https://github.com/etcd-io/etcd/issues/9430) in v3.5.
-- Support [`etcd --cors`](https://github.com/etcd-io/etcd/pull/9490) in v3 HTTP requests (gRPC gateway).
-
-### Package `raft`
-
-- Fix [deadlock during PreVote migration process](https://github.com/etcd-io/etcd/pull/8525).
-- Add [`raft.ErrProposalDropped`](https://github.com/etcd-io/etcd/pull/9067).
-  - Now [`(r *raft) Step` returns `raft.ErrProposalDropped`](https://github.com/etcd-io/etcd/pull/9137) if a proposal has been ignored.
-  - e.g. a node is removed from cluster, or [`raftpb.MsgProp` arrives at current leader while there is an ongoing leadership transfer](https://github.com/etcd-io/etcd/issues/8975).
-- Improve [Raft `becomeLeader` and `stepLeader`](https://github.com/etcd-io/etcd/pull/9073) by keeping track of latest `pb.EntryConfChange` index.
-  - Previously record `pendingConf` boolean field scanning the entire tail of the log, which can delay hearbeat send.
-- Fix [missing learner nodes on `(n *node) ApplyConfChange`](https://github.com/etcd-io/etcd/pull/9116).
-- Add [`raft.Config.MaxUncommittedEntriesSize`](https://github.com/etcd-io/etcd/pull/10167) to limit the total size of the uncommitted entries in bytes.
-  - Once exceeded, raft returns `raft.ErrProposalDropped` error.
-  - Prevent [unbounded Raft log growth](https://github.com/cockroachdb/cockroach/issues/27772).
-  - There was a bug in [PR#10167](https://github.com/etcd-io/etcd/pull/10167) but fixed via [PR#10199](https://github.com/etcd-io/etcd/pull/10199).
-- Add [`raft.Ready.CommittedEntries` pagination using `raft.Config.MaxSizePerMsg`](https://github.com/etcd-io/etcd/pull/9982).
-  - This prevents out-of-memory errors if the raft log has become very large and commits all at once.
-  - Fix [correctness bug in CommittedEntries pagination](https://github.com/etcd-io/etcd/pull/10063).
-- Optimize [message send flow control](https://github.com/etcd-io/etcd/pull/9985).
-  - Leader now sends more append entries if it has more non-empty entries to send after updating flow control information.
-  - Now, Raft allows multiple in-flight append messages.
-- Optimize [memory allocation when boxing slice in `maybeCommit`](https://github.com/etcd-io/etcd/pull/10679).
-  - By boxing a heap-allocated slice header instead of the slice header on the stack, we can avoid an allocation when passing through the sort.Interface interface.
-- Avoid [memory allocation in Raft entry `String` method](https://github.com/etcd-io/etcd/pull/10680).
-- Avoid [multiple memory allocations when merging stable and unstable log](https://github.com/etcd-io/etcd/pull/10684).
-- Extract [progress tracking into own component](https://github.com/etcd-io/etcd/pull/10683).
-  - Add [package `raft/tracker`](https://github.com/etcd-io/etcd/pull/10807).
-  - Optimize [string representation of `Progress`](https://github.com/etcd-io/etcd/pull/10882).
-- Make [relationship between `node` and `RawNode` explicit](https://github.com/etcd-io/etcd/pull/10803).
-- Prevent [learners from becoming leader](https://github.com/etcd-io/etcd/pull/10822).
-- Add [package `raft/quorum` to reason about committed indexes as well as vote outcomes for both majority and joint quorums](https://github.com/etcd-io/etcd/pull/10779).
-  - Bundle [Voters and Learner into `raft/tracker.Config` struct](https://github.com/etcd-io/etcd/pull/10865).
-- Use [membership sets in progress tracking](https://github.com/etcd-io/etcd/pull/10779).
-- Implement [joint quorum computation](https://github.com/etcd-io/etcd/pull/10779).
-- Refactor [`raft/node.go` to centralize configuration change application](https://github.com/etcd-io/etcd/pull/10865).
-- Allow [voter to become learner through snapshot](https://github.com/etcd-io/etcd/pull/10864).
-- Add [package `raft/confchange` to internally support joint consensus](https://github.com/etcd-io/etcd/pull/10779).
-- Use [`RawNode` for node's event loop](https://github.com/etcd-io/etcd/pull/10892).
-- Add [`RawNode.Bootstrap` method](https://github.com/etcd-io/etcd/pull/10892).
-- Add [`raftpb.ConfChangeV2` to use joint quorums](https://github.com/etcd-io/etcd/pull/10914).
-  - `raftpb.ConfChange` continues to work as today: it allows carrying out a single configuration change. A `pb.ConfChange` proposal gets added to the Raft log as such and is thus also observed by the app during Ready handling, and fed back to ApplyConfChange.
-  - `raftpb.ConfChangeV2` allows joint configuration changes but will continue to carry out configuration changes in "one phase" (i.e. without ever entering a joint config) when this is possible.
-  - `raftpb.ConfChangeV2` messages initiate configuration changes. They support both the simple "one at a time" membership change protocol and full Joint Consensus allowing for arbitrary changes in membership.
-- Change [`raftpb.ConfState.Nodes` to `raftpb.ConfState.Voters`](https://github.com/etcd-io/etcd/pull/10914).
-
-### Package `wal`
-
-- Add [`Verify` function to perform corruption check on WAL contents](https://github.com/etcd-io/etcd/pull/10603).
-- Fix [`wal` directory cleanup on creation failures](https://github.com/etcd-io/etcd/pull/10689).
-
-### Tooling
-
-- Add [`etcd-dump-logs --entry-type`](https://github.com/etcd-io/etcd/pull/9628) flag to support WAL log filtering by entry type.
-- Add [`etcd-dump-logs --stream-decoder`](https://github.com/etcd-io/etcd/pull/9790) flag to support custom decoder.
-
-### Go
-
-- Require [*Go 1.12+*](https://github.com/etcd-io/etcd/pull/10045).
-- Compile with [*Go 1.12*](https://golang.org/doc/devel/release.html#go1.12).
-
-### Dockerfile
-
-- [Rebase etcd image from Alpine to Debian](https://github.com/etcd-io/etcd/pull/10805) to improve security and maintenance effort for etcd release.
-
-<hr>
-

CHANGELOG-3.5.md

@@ -1,80 +0,0 @@
-
-
-Previous change logs can be found at [CHANGELOG-3.4](https://github.com/etcd-io/etcd/blob/master/CHANGELOG-3.4.md).
-
-
-<hr>
-
-
-## v3.5.0 (TBD)
-
-See [code changes](https://github.com/etcd-io/etcd/compare/v3.4.0...v3.5.0) and [v3.5 upgrade guide](https://github.com/etcd-io/etcd/blob/master/Documentation/upgrades/upgrade_3_5.md) for any breaking changes.
-
-**Again, before running upgrades from any previous release, please make sure to read change logs below and [v3.5 upgrade guide](https://github.com/etcd-io/etcd/blob/master/Documentation/upgrades/upgrade_3_5.md).**
-
-### Breaking Changes
-
-- [gRPC gateway](https://github.com/grpc-ecosystem/grpc-gateway) only supports [`/v3`](TODO) endpoint.
-  - Deprecated [`/v3beta`](https://github.com/etcd-io/etcd/pull/9298).
-  - `curl -L http://localhost:2379/v3beta/kv/put -X POST -d '{"key": "Zm9v", "value": "YmFy"}'` does work in v3.5. Use `curl -L http://localhost:2379/v3/kv/put -X POST -d '{"key": "Zm9v", "value": "YmFy"}'` instead.
-- **`etcd --experimental-enable-v2v3` flag has been deprecated.** Use **`etcd --enable-v2v3`** instead.
-  - Change [`etcd --experimental-enable-v2v3`](TODO) flag to `etcd --enable-v2v3`; v2 storage emulation is now stable.
-- **`etcd --debug` flag has been deprecated.** Use **`etcd --log-level=debug`** instead.
-- Remove [`embed.Config.Debug`](https://github.com/etcd-io/etcd/pull/10947).
-- **`etcd --log-output` flag has been deprecated.** Use **`etcd --log-outputs`** instead.
-- **`etcd --logger=zap --log-outputs=stderr`** is now the default.
-- **`etcd --logger=capnslog` flag value has been deprecated.**
-- **`etcd --logger=zap --log-outputs=default` flag value is not supported.**.
-  - Use `etcd --logger=zap --log-outputs=stderr`.
-  - Or, use `etcd --logger=zap --log-outputs=systemd/journal` to send logs to the local systemd journal.
-  - Previously, if etcd parent process ID (PPID) is 1 (e.g. run with systemd), `etcd --logger=capnslog --log-outputs=default` redirects server logs to local systemd journal. And if write to journald fails, it writes to `os.Stderr` as a fallback.
-  - However, even with PPID 1, it can fail to dial systemd journal (e.g. run embedded etcd with Docker container). Then, [every single log write will fail](https://github.com/etcd-io/etcd/pull/9729) and fall back to `os.Stderr`, which is inefficient.
-  - To avoid this problem, systemd journal logging must be configured manually.
-- **`etcd --log-outputs=stderr`** is now the default.
-- **`etcd --log-package-levels` flag for `capnslog` has been deprecated.** Now, **`etcd --logger=zap --log-outputs=stderr`** is the default.
-- **`[CLIENT-URL]/config/local/log` endpoint has been deprecated, as is `etcd --log-package-levels` flag.**
-  - `curl http://127.0.0.1:2379/config/local/log -XPUT -d '{"Level":"DEBUG"}'` won't work.
-  - Please use `etcd --logger=zap --log-outputs=stderr` instead.
-- Deprecated `etcd_debugging_mvcc_db_total_size_in_bytes` Prometheus metric. Use `etcd_mvcc_db_total_size_in_bytes` instead.
-- Deprecated `etcd_debugging_mvcc_put_total` Prometheus metric. Use `etcd_mvcc_put_total` instead.
-- Deprecated `etcd_debugging_mvcc_delete_total` Prometheus metric. Use `etcd_mvcc_delete_total` instead.
-- Deprecated `etcd_debugging_mvcc_txn_total` Prometheus metric. Use `etcd_mvcc_txn_total` instead.
-- Deprecated `etcd_debugging_mvcc_range_total` Prometheus metric. Use `etcd_mvcc_range_total` instead.
-- Master branch `/version` outputs `3.5.0-pre`, instead of `3.4.0+git`.
-
-### Metrics, Monitoring
-
-Note that any `etcd_debugging_*` metrics are experimental and subject to change.
-
-- Deprecated `etcd_debugging_mvcc_db_total_size_in_bytes` Prometheus metric. Use `etcd_mvcc_db_total_size_in_bytes` instead.
-- Deprecated `etcd_debugging_mvcc_put_total` Prometheus metric. Use `etcd_mvcc_put_total` instead.
-- Deprecated `etcd_debugging_mvcc_delete_total` Prometheus metric. Use `etcd_mvcc_delete_total` instead.
-- Deprecated `etcd_debugging_mvcc_txn_total` Prometheus metric. Use `etcd_mvcc_txn_total` instead.
-- Deprecated `etcd_debugging_mvcc_range_total` Prometheus metric. Use `etcd_mvcc_range_total` instead.
-
-### etcd server
-
-- [`etcd --enable-v2v3`](TODO) flag is now stable.
-  - `etcd --experimental-enable-v2v3` has been deprecated.
-  - Added [more v2v3 integration tests](https://github.com/etcd-io/etcd/pull/9634).
-  - `etcd --enable-v2=true --enable-v2v3=''` by default, to enable v2 API server that is backed by **v2 store**.
-  - `etcd --enable-v2=true --enable-v2v3=/aaa` to enable v2 API server that is backed by **v3 storage**.
-  - `etcd --enable-v2=false --enable-v2v3=''` to disable v2 API server.
-  - `etcd --enable-v2=false --enable-v2v3=/aaa` to disable v2 API server. TODO: error?
-  - Automatically [create parent directory if it does not exist](https://github.com/etcd-io/etcd/pull/9626) (fix [issue#9609](https://github.com/etcd-io/etcd/issues/9609)).
-  - v4.0 will configure `etcd --enable-v2=true --enable-v2v3=/aaa` to enable v2 API server that is backed by **v3 storage**.
-
-### Package `embed`
-
-- Remove [`embed.Config.Debug`](https://github.com/etcd-io/etcd/pull/10947).
-  - Use `embed.Config.LogLevel` instead.
-
-### gRPC gateway
-
-- [gRPC gateway](https://github.com/grpc-ecosystem/grpc-gateway) only supports [`/v3`](TODO) endpoint.
-  - Deprecated [`/v3beta`](https://github.com/etcd-io/etcd/pull/9298).
-  - `curl -L http://localhost:2379/v3beta/kv/put -X POST -d '{"key": "Zm9v", "value": "YmFy"}'` does work in v3.5. Use `curl -L http://localhost:2379/v3/kv/put -X POST -d '{"key": "Zm9v", "value": "YmFy"}'` instead.
-
-
-<hr>
-

CHANGELOG-4.0.md

@@ -1,48 +0,0 @@
-
-
-Previous change logs can be found at [CHANGELOG-3.x](https://github.com/etcd-io/etcd/blob/master/CHANGELOG-3.x.md).
-
-
-<hr>
-
-
-## v4.0.0 (TBD)
-
-See [code changes](https://github.com/etcd-io/etcd/compare/v3.5.0...v4.0.0) and [v4.0 upgrade guide](https://github.com/etcd-io/etcd/blob/master/Documentation/upgrades/upgrade_4_0.md) for any breaking changes.
-
-**Again, before running upgrades from any previous release, please make sure to read change logs below and [v4.0 upgrade guide](https://github.com/etcd-io/etcd/blob/master/Documentation/upgrades/upgrade_4_0.md).**
-
-### Breaking Changes
-
-- [Secure etcd by default](https://github.com/etcd-io/etcd/issues/9475)?
-- Change `/health` endpoint output.
-  - Previously, `{"health":"true"}`.
-  - Now, `{"health":true}`.
-  - Breaks [Kubernetes `kubectl get componentstatuses` command](https://github.com/kubernetes/kubernetes/issues/58240).
-- Deprecate [`etcd --proxy*`](TODO) flags; **no more v2 proxy**.
-- Deprecate [v2 storage backend](https://github.com/etcd-io/etcd/issues/9232); **no more v2 store**.
-  - v2 API is still supported via [v2 emulation](TODO).
-- Deprecate [`etcdctl backup`](TODO) command.
-- `clientv3.Client.KeepAlive(ctx context.Context, id LeaseID) (<-chan *LeaseKeepAliveResponse, error)` is now [`clientv4.Client.KeepAlive(ctx context.Context, id LeaseID) <-chan *LeaseKeepAliveResponse`](TODO).
-  - Similar to `Watch`, [`KeepAlive` does not return errors](https://github.com/etcd-io/etcd/issues/7488).
-  - If there's an unknown server error, kill all open channels and create a new stream on the next `KeepAlive` call.
-- Rename `github.com/coreos/client` to `github.com/coreos/clientv2`.
-- [`etcd --experimental-initial-corrupt-check`](TODO) has been  deprecated.
-  - Use [`etcd --initial-corrupt-check`](TODO) instead.
-- [`etcd --experimental-corrupt-check-time`](TODO) has been  deprecated.
-  - Use [`etcd --corrupt-check-time`](TODO) instead.
-
-### etcd server
-
-- [`etcd --initial-corrupt-check`](TODO) flag is now stable (`etcd --experimental-initial-corrupt-check` has been  deprecated).
-  - `etcd --initial-corrupt-check=true` by default, to check cluster database hashes before serving client/peer traffic.
-- [`etcd --corrupt-check-time`](TODO) flag is now stable (`etcd --experimental-corrupt-check-time` has been  deprecated).
-  - `etcd --corrupt-check-time=12h` by default, to check cluster database hashes for every 12-hour.
-
-### Go
-
-- Require [*Go 2*](https://blog.golang.org/go2draft)?
-
-
-<hr>
-

CONTRIBUTING.md

@@ -6,6 +6,7 @@ etcd is Apache 2.0 licensed and accepts contributions via GitHub pull requests.
 
 - Email: [etcd-dev](https://groups.google.com/forum/?hl=en#!forum/etcd-dev)
 - IRC: #[etcd](irc://irc.freenode.org:6667/#etcd) IRC channel on freenode.org
+- Slack: [#etcd](https://kubernetes.slack.com/messages/C3HD8ARJ5/details/)
 
 ## Getting started
 
@@ -14,13 +15,13 @@ etcd is Apache 2.0 licensed and accepts contributions via GitHub pull requests.
 
 ## Reporting bugs and creating issues
 
-Reporting bugs is one of the best ways to contribute. However, a good bug report has some very specific qualities, so please read over our short document on [reporting bugs](https://github.com/etcd-io/etcd/blob/master/Documentation/reporting_bugs.md) before submitting a bug report. This document might contain links to known issues, another good reason to take a look there before reporting a bug.
+Reporting bugs is one of the best ways to contribute. However, a good bug report has some very specific qualities, so please read over our short document on [reporting bugs](https://etcd.io/docs/latest/reporting_bugs) before submitting a bug report. This document might contain links to known issues, another good reason to take a look there before reporting a bug.
 
 ## Contribution flow
 
 This is a rough outline of what a contributor's workflow looks like:
 
-- Create a topic branch from where to base the contribution. This is usually master.
+- Create a topic branch from where to base the contribution. This is usually main.
 - Make commits of logical units.
 - Make sure commit messages are in the proper format (see below).
 - Push changes in a topic branch to a personal fork of the repository.

Dockerfile-release.amd64

@@ -1,7 +1,8 @@
-FROM k8s.gcr.io/debian-base:v1.0.0
+FROM k8s.gcr.io/build-image/debian-base:buster-v1.4.0
 
 ADD etcd /usr/local/bin/
 ADD etcdctl /usr/local/bin/
+ADD etcdutl /usr/local/bin/
 RUN mkdir -p /var/etcd/
 RUN mkdir -p /var/lib/etcd/
 

Dockerfile-release.arm64

@@ -1,9 +1,11 @@
-FROM k8s.gcr.io/debian-base-arm64:v1.0.0
+FROM k8s.gcr.io/build-image/debian-base-arm64:buster-v1.4.0
 
 ADD etcd /usr/local/bin/
 ADD etcdctl /usr/local/bin/
+ADD etcdutl /usr/local/bin/
 ADD var/etcd /var/etcd
 ADD var/lib/etcd /var/lib/etcd
+ENV ETCD_UNSUPPORTED_ARCH=arm64
 
 EXPOSE 2379 2380
 

Dockerfile-release.ppc64le

@@ -1,7 +1,8 @@
-FROM k8s.gcr.io/debian-base-ppc64le:v1.0.0
+FROM k8s.gcr.io/build-image/debian-base-ppc64le:buster-v1.4.0
 
 ADD etcd /usr/local/bin/
 ADD etcdctl /usr/local/bin/
+ADD etcdutl /usr/local/bin/
 ADD var/etcd /var/etcd
 ADD var/lib/etcd /var/lib/etcd
 

Dockerfile-release.s390x

@@ -0,0 +1,12 @@
+FROM k8s.gcr.io/build-image/debian-base-s390x:buster-v1.4.0
+
+ADD etcd /usr/local/bin/
+ADD etcdctl /usr/local/bin/
+ADD etcdutl /usr/local/bin/
+ADD var/etcd /var/etcd
+ADD var/lib/etcd /var/lib/etcd
+
+EXPOSE 2379 2380
+
+# Define default command.
+CMD ["/usr/local/bin/etcd"]

Documentation/README.md

@@ -1 +0,0 @@
-docs.md

Documentation/README.md

@@ -0,0 +1,6 @@
+# The etcd documentation
+
+etcd is a distributed key-value store designed to reliably and quickly preserve and provide access to critical data. It enables reliable distributed coordination through distributed locking, leader elections, and write barriers. An etcd cluster is intended for high availability and permanent data storage and retrieval.
+
+These documents have moved to the [etcd-io/website repo](https://github.com/etcd-io/website/), and can be viewed live at [https://etcd.io/docs/latest/](https://etcd.io/docs/latest/).
+

Documentation/benchmarks/README.md

@@ -1,18 +0,0 @@
-# Benchmarks
-
-etcd benchmarks will be published regularly and tracked for each release below:
-
-- [etcd v2.1.0-alpha][2.1]
-- [etcd v2.2.0-rc][2.2]
-- [etcd v3 demo][3.0]
-
-# Memory Usage Benchmarks
-
-It records expected memory usage in different scenarios.
-
-- [etcd v2.2.0-rc][2.2-mem]
-
-[2.1]: etcd-2-1-0-alpha-benchmarks.md
-[2.2]: etcd-2-2-0-rc-benchmarks.md
-[2.2-mem]: etcd-2-2-0-rc-memory-benchmarks.md
-[3.0]: etcd-3-demo-benchmarks.md

Documentation/benchmarks/etcd-2-1-0-alpha-benchmarks.md

@@ -1,56 +0,0 @@
----
-title: Benchmarking etcd v2.1.0
----
-
-## Physical machines
-
-GCE n1-highcpu-2 machine type
-
-- 1x dedicated local SSD mounted under /var/lib/etcd
-- 1x dedicated slow disk for the OS
-- 1.8 GB memory
-- 2x CPUs
-- etcd version 2.1.0 alpha
-
-## etcd Cluster
-
-3 etcd members, each runs on a single machine
-
-## Testing
-
-Bootstrap another machine and use the [hey HTTP benchmark tool][hey] to send requests to each etcd member. Check the [benchmark hacking guide][hack-benchmark] for detailed instructions.
-
-## Performance
-
-### reading one single key
-
-| key size in bytes | number of clients | target etcd server | read QPS | 90th Percentile Latency (ms) |
-|-------------------|-------------------|--------------------|----------|---------------|
-| 64                | 1                 | leader only        | 1534     | 0.7        |
-| 64                | 64                | leader only        | 10125    | 9.1      |
-| 64                | 256               | leader only        | 13892    | 27.1      |
-| 256               | 1                 | leader only        | 1530     | 0.8       |
-| 256               | 64                | leader only        | 10106    | 10.1      |
-| 256               | 256               | leader only        | 14667    | 27.0      |
-| 64                | 64                | all servers        | 24200    | 3.9      |
-| 64                | 256               | all servers        | 33300    | 11.8      |
-| 256               | 64                | all servers        | 24800    | 3.9      |
-| 256               | 256               | all servers        | 33000    | 11.5      |
-
-### writing one single key
-
-| key size in bytes | number of clients | target etcd server | write QPS | 90th Percentile Latency (ms) |
-|-------------------|-------------------|--------------------|-----------|---------------|
-| 64                | 1                 | leader only        | 60        | 21.4 |
-| 64                | 64                | leader only        | 1742      | 46.8 |
-| 64                | 256               | leader only        | 3982      | 90.5 |
-| 256               | 1                 | leader only        | 58        | 20.3 |
-| 256               | 64                | leader only        | 1770      | 47.8 |
-| 256               | 256               | leader only        | 4157      | 105.3 |
-| 64                | 64                | all servers        | 1028      | 123.4 |
-| 64                | 256               | all servers        | 3260      | 123.8 |
-| 256               | 64                | all servers        | 1033      | 121.5 |
-| 256               | 256               | all servers        | 3061      | 119.3 |
-
-[hey]: https://github.com/rakyll/hey
-[hack-benchmark]: https://github.com/coreos/etcd/tree/master/hack/benchmark

Documentation/benchmarks/etcd-2-2-0-benchmarks.md

@@ -1,71 +0,0 @@
----
-title: Benchmarking etcd v2.2.0
----
-
-## Physical Machines
-
-GCE n1-highcpu-2 machine type
-
-- 1x dedicated local SSD mounted as etcd data directory
-- 1x dedicated slow disk for the OS
-- 1.8 GB memory
-- 2x CPUs
-
-## etcd Cluster
-
-3 etcd 2.2.0 members, each runs on a single machine.
-
-Detailed versions:
-
-```
-etcd Version: 2.2.0
-Git SHA: e4561dd
-Go Version: go1.5
-Go OS/Arch: linux/amd64
-```
-
-## Testing
-
-Bootstrap another machine, outside of the etcd cluster, and run the [`hey` HTTP benchmark tool](https://github.com/rakyll/hey) with a connection reuse patch to send requests to each etcd cluster member. See the [benchmark instructions](../../hack/benchmark/) for the patch and the steps to reproduce our procedures.
-
-The performance is calculated through results of 100 benchmark rounds.
-
-## Performance
-
-### Single Key Read Performance
-
-| key size in bytes | number of clients | target etcd server | average read QPS | read QPS stddev | average 90th Percentile Latency (ms) | latency stddev |
-|-------------------|-------------------|--------------------|------------------|-----------------|--------------------------------------|----------------|
-| 64 | 1 | leader only | 2303 | 200 | 0.49 | 0.06 |
-| 64 | 64 | leader only | 15048 | 685 | 7.60 | 0.46 |
-| 64 | 256 | leader only | 14508 | 434 | 29.76 | 1.05 |
-| 256 | 1 | leader only | 2162 | 214 | 0.52 | 0.06 |
-| 256 | 64 | leader only | 14789 | 792 | 7.69| 0.48 |
-| 256 | 256 | leader only | 14424 | 512 | 29.92 | 1.42 |
-| 64 | 64 | all servers | 45752 | 2048 | 2.47 | 0.14 |
-| 64 | 256 | all servers | 46592 | 1273 | 10.14 | 0.59 |
-| 256 | 64 | all servers | 45332 | 1847 | 2.48| 0.12 |
-| 256 | 256 | all servers | 46485 | 1340 | 10.18 | 0.74 |
-
-### Single Key Write Performance
-
-| key size in bytes | number of clients | target etcd server | average write QPS | write QPS stddev | average 90th Percentile Latency (ms) | latency stddev |
-|-------------------|-------------------|--------------------|------------------|-----------------|--------------------------------------|----------------|
-| 64 | 1 | leader only | 55 | 4 | 24.51 | 13.26 |
-| 64 | 64 | leader only | 2139 | 125 | 35.23 | 3.40 |
-| 64 | 256 | leader only | 4581 | 581 | 70.53 | 10.22 |
-| 256 | 1 | leader only | 56 | 4 | 22.37| 4.33 |
-| 256 | 64 | leader only | 2052 | 151 | 36.83 | 4.20 |
-| 256 | 256 | leader only | 4442 | 560 | 71.59 | 10.03 |
-| 64 | 64 | all servers | 1625 | 85 | 58.51 | 5.14 |
-| 64 | 256 | all servers | 4461 | 298 | 89.47 | 36.48 |
-| 256 | 64 | all servers | 1599 | 94 | 60.11| 6.43 |
-| 256 | 256 | all servers | 4315 | 193 | 88.98 | 7.01 |
-
-## Performance Changes
-
-- Because etcd now records metrics for each API call, read QPS performance seems to see a minor decrease in most scenarios. This minimal performance impact was judged a reasonable investment for the breadth of monitoring and debugging information returned.
-
-- Write QPS to cluster leaders seems to be increased by a small margin. This is because the main loop and entry apply loops were decoupled in the etcd raft logic, eliminating several blocks between them.
-
-- Write QPS to all members seems to be increased by a significant margin, because followers now receive the latest commit index sooner, and commit proposals more quickly.

Documentation/benchmarks/etcd-2-2-0-rc-benchmarks.md

@@ -1,76 +0,0 @@
----
-title: Benchmarking etcd v2.2.0-rc
----
-
-## Physical machine
-
-GCE n1-highcpu-2 machine type
-
-- 1x dedicated local SSD mounted under /var/lib/etcd
-- 1x dedicated slow disk for the OS
-- 1.8 GB memory
-- 2x CPUs
-
-## etcd Cluster
-
-3 etcd 2.2.0-rc members, each runs on a single machine.
-
-Detailed versions:
-
-```
-etcd Version: 2.2.0-alpha.1+git
-Git SHA: 59a5a7e
-Go Version: go1.4.2
-Go OS/Arch: linux/amd64
-```
-
-Also, we use 3 etcd 2.1.0 alpha-stage members to form cluster to get base performance. etcd's commit head is at [c7146bd5][c7146bd5], which is the same as the one that we use in [etcd 2.1 benchmark][etcd-2.1-benchmark].
-
-## Testing
-
-Bootstrap another machine and use the [hey HTTP benchmark tool][hey] to send requests to each etcd member. Check the [benchmark hacking guide][hack-benchmark] for detailed instructions.
-
-## Performance
-
-### reading one single key
-
-| key size in bytes | number of clients | target etcd server | read QPS | 90th Percentile Latency (ms) |
-|-------------------|-------------------|--------------------|----------|---------------|
-| 64                | 1                 | leader only        | 2804 (-5%) | 0.4 (+0%) |
-| 64                | 64                | leader only        | 17816 (+0%) | 5.7 (-6%) |
-| 64                | 256               | leader only        | 18667 (-6%) | 20.4 (+2%) |
-| 256               | 1                 | leader only        | 2181 (-15%) | 0.5 (+25%) |
-| 256               | 64                | leader only        | 17435 (-7%) | 6.0 (+9%) |
-| 256               | 256               | leader only        | 18180 (-8%) | 21.3 (+3%) |
-| 64                | 64                | all servers        | 46965 (-4%) | 2.1 (+0%) |
-| 64                | 256               | all servers        | 55286 (-6%) | 7.4 (+6%) |
-| 256               | 64                | all servers        | 46603 (-6%) | 2.1 (+5%) |
-| 256               | 256               | all servers        | 55291 (-6%) | 7.3 (+4%) |
-
-### writing one single key
-
-| key size in bytes | number of clients | target etcd server | write QPS | 90th Percentile Latency (ms) |
-|-------------------|-------------------|--------------------|-----------|---------------|
-| 64                | 1                 | leader only        | 76 (+22%)  | 19.4 (-15%) |
-| 64                | 64                | leader only        | 2461 (+45%) | 31.8 (-32%) |
-| 64                | 256               | leader only        | 4275 (+1%) | 69.6 (-10%) |
-| 256               | 1                 | leader only        | 64 (+20%)  | 16.7 (-30%) |
-| 256               | 64                | leader only        | 2385 (+30%) | 31.5 (-19%) |
-| 256               | 256               | leader only        | 4353 (-3%) | 74.0 (+9%) |
-| 64                | 64                | all servers        | 2005 (+81%) | 49.8 (-55%) |
-| 64                | 256               | all servers        | 4868 (+35%) | 81.5 (-40%) |
-| 256               | 64                | all servers        | 1925 (+72%) | 47.7 (-59%) |
-| 256               | 256               | all servers        | 4975 (+36%) | 70.3 (-36%) |
-
-### performance changes explanation
-
-- read QPS in most scenarios is decreased by 5~8%. The reason is that etcd records store metrics for each store operation. The metrics is important for monitoring and debugging, so this is acceptable.
-
-- write QPS to leader is increased by 20~30%. This is because we decouple raft main loop and entry apply loop, which avoids them blocking each other.
-
-- write QPS to all servers is increased by 30~80% because follower could receive latest commit index earlier and commit proposals faster.
-
-[hey]: https://github.com/rakyll/hey
-[c7146bd5]: https://github.com/coreos/etcd/commits/c7146bd5f2c73716091262edc638401bb8229144
-[etcd-2.1-benchmark]: etcd-2-1-0-alpha-benchmarks.md
-[hack-benchmark]: ../../hack/benchmark/

Documentation/benchmarks/etcd-2-2-0-rc-memory-benchmarks.md

@@ -1,51 +0,0 @@
----
-title: Benchmarking etcd v2.2.0-rc-memory
----
-
-## Physical machine
-
-GCE n1-standard-2 machine type
-
-- 1x dedicated local SSD mounted under /var/lib/etcd
-- 1x dedicated slow disk for the OS
-- 7.5 GB memory
-- 2x CPUs
-
-## etcd
-
-```
-etcd Version: 2.2.0-rc.0+git
-Git SHA: 103cb5c
-Go Version: go1.5
-Go OS/Arch: linux/amd64
-```
-
-## Testing
-
-Start 3-member etcd cluster, each of which uses 2 cores.
-
-The length of key name is always 64 bytes, which is a reasonable length of average key bytes.
-
-## Memory Maximal Usage
-
-- etcd may use maximal memory if one follower is dead and the leader keeps sending snapshots.
-- `max RSS` is the maximal memory usage recorded in 3 runs.
-
-| value bytes | key number  | data size(MB) | max RSS(MB) | max RSS/data rate on leader |
-|-------------|-------------|---------------|-------------|-----------------------------|
-| 128  | 50000  | 6 | 433 | 72x |
-| 128  | 100000 | 12 | 659 | 54x |
-| 128  | 200000 | 24 | 1466 | 61x |
-| 1024 | 50000  | 48 | 1253 | 26x |
-| 1024 | 100000 | 96 | 2344 | 24x |
-| 1024 | 200000 | 192 | 4361 | 22x |
-
-## Data Size Threshold
-
-- When etcd reaches data size threshold, it may trigger leader election easily and drop part of proposals.
-- For most cases, the etcd cluster should work smoothly if it doesn't hit the threshold. If it doesn't work well due to insufficient resources, decrease its data size.
-
-| value bytes | key number limitation | suggested data size threshold(MB) | consumed RSS(MB) |
-|-------------|-----------------------|-----------------------------------|------------------|
-| 128 | 400K | 48 | 2400 |
-| 1024 | 300K | 292 | 6500 |

Documentation/benchmarks/etcd-3-demo-benchmarks.md

@@ -1,46 +0,0 @@
----
-title: Benchmarking etcd v3
----
-
-## Physical machines
-
-GCE n1-highcpu-2 machine type
-
-- 1x dedicated local SSD mounted under /var/lib/etcd
-- 1x dedicated slow disk for the OS
-- 1.8 GB memory
-- 2x CPUs
-- etcd version 2.2.0
-
-## etcd Cluster
-
-1 etcd member running in v3 demo mode
-
-## Testing
-
-Use [etcd v3 benchmark tool][etcd-v3-benchmark].
-
-## Performance
-
-### reading one single key
-
-| key size in bytes | number of clients | read QPS | 90th Percentile Latency (ms) |
-|-------------------|-------------------|----------|---------------|
-| 256               | 1                 | 2716  | 0.4      |
-| 256               | 64                | 16623 | 6.1      |
-| 256               | 256               | 16622 | 21.7     |
-
-The performance is nearly the same as the one with empty server handler.
-
-### reading one single key after putting
-
-| key size in bytes | number of clients | read QPS | 90th Percentile Latency (ms) |
-|-------------------|-------------------|----------|---------------|
-| 256               | 1                 | 2269  | 0.5      |
-| 256               | 64                | 13582 | 8.6      |
-| 256               | 256               | 13262 | 47.5     |
-
-The performance with empty server handler is not affected by one put. So the
-performance downgrade should be caused by storage package.
-
-[etcd-v3-benchmark]: ../../tools/benchmark/

Documentation/benchmarks/etcd-3-watch-memory-benchmark.md

@@ -1,79 +0,0 @@
----
-title: Watch Memory Usage Benchmark
----
-
-*NOTE*: The watch features are under active development, and their memory usage may change as that development progresses. We do not expect it to significantly increase beyond the figures stated below.
-
-A primary goal of etcd is supporting a very large number of watchers doing a massively large amount of watching. etcd aims to support O(10k) clients, O(100K) watch streams (O(10) streams per client) and O(10M) total watchings (O(100) watching per stream). The memory consumed by each individual watching accounts for the largest portion of etcd's overall usage, and is therefore the focus of current and future optimizations.
-
-
-Three related components of etcd watch consume physical memory: each `grpc.Conn`, each watch stream, and each instance of the watching activity. `grpc.Conn` maintains the actual TCP connection and other gRPC connection state. Each `grpc.Conn` consumes O(10kb) of memory, and might have multiple watch streams attached. 
-
-Each watch stream is an independent HTTP2 connection which consumes another O(10kb) of memory. 
-Multiple watchings might share one watch stream. 
-
-Watching is the actual struct that tracks the changes on the key-value store. Each watching should only consume < O(1kb).
-
-```
-                                          +-------+
-                                          | watch |
-                              +---------> | foo   |
-                              |           +-------+
-                       +------+-----+
-                       |   stream   |
-      +--------------> |            |
-      |                +------+-----+     +-------+
-      |                       |           | watch |
-      |                       +---------> | bar   |
-+-----+------+                            +-------+
-|            |         +------------+
-|   conn     +-------> |   stream   |
-|            |         |            |
-+-----+------+         +------------+
-      |
-      |
-      |
-      |                +------------+
-      +--------------> |   stream   |
-                       |            |
-                       +------------+
-```
-
-The theoretical memory consumption of watch can be approximated with the formula:
-`memory = c1 * number_of_conn + c2 * avg_number_of_stream_per_conn + c3 * avg_number_of_watch_stream`
-
-## Testing Environment
-
-etcd version
-- git head https://github.com/coreos/etcd/commit/185097ffaa627b909007e772c175e8fefac17af3
-
-GCE n1-standard-2 machine type
-- 7.5 GB memory
-- 2x CPUs
-
-## Overall memory usage
-
-The overall memory usage captures how much [RSS][rss] etcd consumes with the client watchers. While the result may vary by as much as 10%, it is still meaningful, since the goal is to learn about the rough memory usage and the pattern of allocations.
-
-With the benchmark result, we can calculate roughly that `c1 = 17kb`, `c2 = 18kb` and `c3 = 350bytes`. So each additional client connection consumes 17kb of memory and each additional stream consumes 18kb of memory, and each additional watching only cause 350bytes. A single etcd server can maintain millions of watchings with a few GB of memory in normal case.
-
-
-| clients | streams per client | watchings per stream | total watching | memory usage |
-|---------|---------|-----------|----------------|--------------|
-| 1k |  1 |   1 |   1k |   50MB |
-| 2k |  1 |   1 |   2k |   90MB |
-| 5k |  1 |   1 |   5k |  200MB |
-| 1k | 10 |   1 |  10k |  217MB |
-| 2k | 10 |   1 |  20k |  417MB |
-| 5k | 10 |   1 |  50k |  980MB |
-| 1k | 50 |   1 |  50k | 1001MB |
-| 2k | 50 |   1 | 100k | 1960MB |
-| 5k | 50 |   1 | 250k | 4700MB |
-| 1k | 50 |  10 | 500k | 1171MB |
-| 2k | 50 |  10 |   1M | 2371MB |
-| 5k | 50 |  10 | 2.5M | 5710MB |
-| 1k | 50 | 100 |   5M | 2380MB |
-| 2k | 50 | 100 |  10M | 4672MB |
-| 5k | 50 | 100 |  25M |  *OOM* |
-
-[rss]: https://en.wikipedia.org/wiki/Resident_set_size

Documentation/benchmarks/etcd-storage-memory-benchmark.md

@@ -1,100 +0,0 @@
----
-title: Storage Memory Usage Benchmark
----
-
-<!---todo: link storage to storage design doc-->
-Two components of etcd storage consume physical memory. The etcd process allocates an *in-memory index* to speed key lookup. The process's *page cache*, managed by the operating system, stores recently-accessed data from disk for quick re-use.
-
-The in-memory index holds all the keys in a [B-tree][btree] data structure, along with pointers to the on-disk data (the values). Each key in the B-tree may contain multiple pointers, pointing to different versions of its values. The theoretical memory consumption of the in-memory index can hence be approximated with the formula:
-
-`N * (c1 + avg_key_size) + N * (avg_versions_of_key) * (c2 + size_of_pointer)`
-
-where `c1` is the key metadata overhead and `c2` is the version metadata overhead.
-
-The graph shows the detailed structure of the in-memory index B-tree.
-
-```
-
-
-                                In mem index
-
-                               +------------+
-                               | key || ... |
-  +--------------+             |     ||     |
-  |              |             +------------+
-  |              |             | v1  || ... |
-  |   disk    <----------------|     ||     | Tree Node
-  |              |             +------------+
-  |              |             | v2  || ... |
-  |           <----------------+     ||     |
-  |              |             +------------+
-  +--------------+       +-----+    |   |   |
-                         |     |    |   |   |
-                         |     +------------+
-                         |
-                         |
-                         ^
-                      ------+
-                      | ... |
-                      |     |
-                      +-----+
-                      | ... | Tree Node
-                      |     |
-                      +-----+
-                      | ... |
-                      |     |
-                      ------+
-```
-
-[Page cache memory][pagecache] is managed by the operating system and is not covered in detail in this document.
-
-## Testing Environment
-
-etcd version
-- git head https://github.com/coreos/etcd/commit/776e9fb7be7eee5e6b58ab977c8887b4fe4d48db
-
-GCE n1-standard-2 machine type
-
-- 7.5 GB memory
-- 2x CPUs
-
-## In-memory index memory usage
-
-In this test, we only benchmark the memory usage of the in-memory index. The goal is to find `c1` and `c2` mentioned above and to understand the hard limit of memory consumption of the storage.
-
-We calculate the memory usage consumption via the Go runtime.ReadMemStats. We calculate the total allocated bytes difference before creating the index and after creating the index. It cannot perfectly reflect the memory usage of the in-memory index itself but can show the rough consumption pattern. 
-
-| N    | versions | key size | memory usage |
-|------|----------|----------|--------------|
-| 100K | 1        | 64bytes  | 22MB         |
-| 100K | 5        | 64bytes  | 39MB         |
-| 1M   | 1        | 64bytes  | 218MB        |
-| 1M   | 5        | 64bytes  | 432MB        |
-| 100K | 1        | 256bytes | 41MB         |
-| 100K | 5        | 256bytes | 65MB         |
-| 1M   | 1        | 256bytes | 409MB        |
-| 1M   | 5        | 256bytes | 506MB        |
-
-
-Based on the result, we can calculate `c1=120bytes`, `c2=30bytes`. We only need two sets of data to calculate `c1` and `c2`, since they are the only unknown variable in the formula. The `c1=120bytes` and `c2=30bytes` are the average value of the 4 sets of `c1` and `c2` we calculated. The key metadata overhead is still relatively nontrivial (50%) for small key-value pairs. However, this is a significant improvement over the old store, which had at least 1000% overhead.
-
-## Overall memory usage
-
-The overall memory usage captures how much RSS etcd consumes with the storage. The value size should have very little impact on the overall memory usage of etcd, since we keep values on disk and only retain hot values in memory, managed by the OS page cache.
-
-| N    | versions | key size | value size | memory usage |
-|------|----------|----------|------------|--------------|
-| 100K | 1        | 64bytes  | 256bytes   | 40MB         |
-| 100K | 5        | 64bytes  | 256bytes   | 89MB         |
-| 1M   | 1        | 64bytes  | 256bytes   | 470MB        |
-| 1M   | 5        | 64bytes  | 256bytes   | 880MB        |
-| 100K | 1        | 64bytes  | 1KB        | 102MB        |
-| 100K | 5        | 64bytes  | 1KB        | 164MB        |
-| 1M   | 1        | 64bytes  | 1KB        | 587MB        |
-| 1M   | 5        | 64bytes  | 1KB        | 836MB        |
-
-Based on the result, we know the value size does not significantly impact the memory consumption. There is some minor increase due to more data held in the OS page cache.
-
-[btree]: https://en.wikipedia.org/wiki/B-tree
-[pagecache]: https://en.wikipedia.org/wiki/Page_cache
-

Documentation/branch_management.md

@@ -1,28 +0,0 @@
----
-title: Branch management
----
-
-## Guide
-
-* New development occurs on the [master branch][master].
-* Master branch should always have a green build!
-* Backwards-compatible bug fixes should target the master branch and subsequently be ported to stable branches.
-* Once the master branch is ready for release, it will be tagged and become the new stable branch.
-
-The etcd team has adopted a *rolling release model* and supports two stable versions of etcd.
-
-### Master branch
-
-The `master` branch is our development branch. All new features land here first.
-
-To try new and experimental features, pull `master` and play with it. Note that `master` may not be stable because new features may introduce bugs.
-
-Before the release of the next stable version, feature PRs will be frozen. A [release manager](./dev-internal/release.md#release-management) will be assigned to major/minor version and will lead the etcd community in test, bug-fix and documentation of the release for one to two weeks.
-
-### Stable branches
-
-All branches with prefix `release-` are considered _stable_ branches.
-
-After every minor release (http://semver.org/), we will have a new stable branch for that release, managed by a [patch release manager](./dev-internal/release.md#release-management). We will keep fixing the backwards-compatible bugs for the latest two stable releases. A _patch_ release to each supported release branch, incorporating any bug fixes, will be once every two weeks, given any patches.
-
-[master]: https://github.com/coreos/etcd/tree/master

Documentation/demo.md

@@ -1,456 +0,0 @@
----
-title: Demo
----
-
-This series of examples shows the basic procedures for working with an etcd cluster.
-
-## Set up a cluster
-
-<img src="https://storage.googleapis.com/etcd/demo/01_etcd_clustering_2016051001.gif" alt="01_etcd_clustering_2016050601"/>
-
-On each etcd node, specify the cluster members:
-
-```
-TOKEN=token-01
-CLUSTER_STATE=new
-NAME_1=machine-1
-NAME_2=machine-2
-NAME_3=machine-3
-HOST_1=10.240.0.17
-HOST_2=10.240.0.18
-HOST_3=10.240.0.19
-CLUSTER=${NAME_1}=http://${HOST_1}:2380,${NAME_2}=http://${HOST_2}:2380,${NAME_3}=http://${HOST_3}:2380
-```
-
-Run this on each machine:
-
-```
-# For machine 1
-THIS_NAME=${NAME_1}
-THIS_IP=${HOST_1}
-etcd --data-dir=data.etcd --name ${THIS_NAME} \
-	--initial-advertise-peer-urls http://${THIS_IP}:2380 --listen-peer-urls http://${THIS_IP}:2380 \
-	--advertise-client-urls http://${THIS_IP}:2379 --listen-client-urls http://${THIS_IP}:2379 \
-	--initial-cluster ${CLUSTER} \
-	--initial-cluster-state ${CLUSTER_STATE} --initial-cluster-token ${TOKEN}
-
-# For machine 2
-THIS_NAME=${NAME_2}
-THIS_IP=${HOST_2}
-etcd --data-dir=data.etcd --name ${THIS_NAME} \
-	--initial-advertise-peer-urls http://${THIS_IP}:2380 --listen-peer-urls http://${THIS_IP}:2380 \
-	--advertise-client-urls http://${THIS_IP}:2379 --listen-client-urls http://${THIS_IP}:2379 \
-	--initial-cluster ${CLUSTER} \
-	--initial-cluster-state ${CLUSTER_STATE} --initial-cluster-token ${TOKEN}
-
-# For machine 3
-THIS_NAME=${NAME_3}
-THIS_IP=${HOST_3}
-etcd --data-dir=data.etcd --name ${THIS_NAME} \
-	--initial-advertise-peer-urls http://${THIS_IP}:2380 --listen-peer-urls http://${THIS_IP}:2380 \
-	--advertise-client-urls http://${THIS_IP}:2379 --listen-client-urls http://${THIS_IP}:2379 \
-	--initial-cluster ${CLUSTER} \
-	--initial-cluster-state ${CLUSTER_STATE} --initial-cluster-token ${TOKEN}
-```
-
-Or use our public discovery service:
-
-```
-curl https://discovery.etcd.io/new?size=3
-https://discovery.etcd.io/a81b5818e67a6ea83e9d4daea5ecbc92
-
-# grab this token
-TOKEN=token-01
-CLUSTER_STATE=new
-NAME_1=machine-1
-NAME_2=machine-2
-NAME_3=machine-3
-HOST_1=10.240.0.17
-HOST_2=10.240.0.18
-HOST_3=10.240.0.19
-DISCOVERY=https://discovery.etcd.io/a81b5818e67a6ea83e9d4daea5ecbc92
-
-THIS_NAME=${NAME_1}
-THIS_IP=${HOST_1}
-etcd --data-dir=data.etcd --name ${THIS_NAME} \
-	--initial-advertise-peer-urls http://${THIS_IP}:2380 --listen-peer-urls http://${THIS_IP}:2380 \
-	--advertise-client-urls http://${THIS_IP}:2379 --listen-client-urls http://${THIS_IP}:2379 \
-	--discovery ${DISCOVERY} \
-	--initial-cluster-state ${CLUSTER_STATE} --initial-cluster-token ${TOKEN}
-
-THIS_NAME=${NAME_2}
-THIS_IP=${HOST_2}
-etcd --data-dir=data.etcd --name ${THIS_NAME} \
-	--initial-advertise-peer-urls http://${THIS_IP}:2380 --listen-peer-urls http://${THIS_IP}:2380 \
-	--advertise-client-urls http://${THIS_IP}:2379 --listen-client-urls http://${THIS_IP}:2379 \
-	--discovery ${DISCOVERY} \
-	--initial-cluster-state ${CLUSTER_STATE} --initial-cluster-token ${TOKEN}
-
-THIS_NAME=${NAME_3}
-THIS_IP=${HOST_3}
-etcd --data-dir=data.etcd --name ${THIS_NAME} \
-	--initial-advertise-peer-urls http://${THIS_IP}:2380 --listen-peer-urls http://${THIS_IP}:2380 \
-	--advertise-client-urls http://${THIS_IP}:2379 --listen-client-urls http://${THIS_IP}:2379 \
-	--discovery ${DISCOVERY} \
-	--initial-cluster-state ${CLUSTER_STATE} --initial-cluster-token ${TOKEN}
-```
-
-Now etcd is ready! To connect to etcd with etcdctl:
-
-```
-export ETCDCTL_API=3
-HOST_1=10.240.0.17
-HOST_2=10.240.0.18
-HOST_3=10.240.0.19
-ENDPOINTS=$HOST_1:2379,$HOST_2:2379,$HOST_3:2379
-
-etcdctl --endpoints=$ENDPOINTS member list
-```
-
-
-## Access etcd
-
-<img src="https://storage.googleapis.com/etcd/demo/02_etcdctl_access_etcd_2016051001.gif" alt="02_etcdctl_access_etcd_2016051001"/>
-
-`put` command to write:
-
-```
-etcdctl --endpoints=$ENDPOINTS put foo "Hello World!"
-```
-
-`get` to read from etcd:
-
-```
-etcdctl --endpoints=$ENDPOINTS get foo
-etcdctl --endpoints=$ENDPOINTS --write-out="json" get foo
-```
-
-
-## Get by prefix
-
-<img src="https://storage.googleapis.com/etcd/demo/03_etcdctl_get_by_prefix_2016050501.gif" alt="03_etcdctl_get_by_prefix_2016050501"/>
-
-```
-etcdctl --endpoints=$ENDPOINTS put web1 value1
-etcdctl --endpoints=$ENDPOINTS put web2 value2
-etcdctl --endpoints=$ENDPOINTS put web3 value3
-
-etcdctl --endpoints=$ENDPOINTS get web --prefix
-```
-
-
-## Delete
-
-<img src="https://storage.googleapis.com/etcd/demo/04_etcdctl_delete_2016050601.gif" alt="04_etcdctl_delete_2016050601"/>
-
-```
-etcdctl --endpoints=$ENDPOINTS put key myvalue
-etcdctl --endpoints=$ENDPOINTS del key
-
-etcdctl --endpoints=$ENDPOINTS put k1 value1
-etcdctl --endpoints=$ENDPOINTS put k2 value2
-etcdctl --endpoints=$ENDPOINTS del k --prefix
-```
-
-
-## Transactional write
-
-`txn` to wrap multiple requests into one transaction:
-
-<img src="https://storage.googleapis.com/etcd/demo/05_etcdctl_transaction_2016050501.gif" alt="05_etcdctl_transaction_2016050501"/>
-
-```
-etcdctl --endpoints=$ENDPOINTS put user1 bad
-etcdctl --endpoints=$ENDPOINTS txn --interactive
-
-compares:
-value("user1") = "bad"      
-
-success requests (get, put, delete):
-del user1  
-
-failure requests (get, put, delete):
-put user1 good
-```
-
-
-## Watch
-
-`watch` to get notified of future changes:
-
-<img src="https://storage.googleapis.com/etcd/demo/06_etcdctl_watch_2016050501.gif" alt="06_etcdctl_watch_2016050501"/>
-
-```
-etcdctl --endpoints=$ENDPOINTS watch stock1
-etcdctl --endpoints=$ENDPOINTS put stock1 1000
-
-etcdctl --endpoints=$ENDPOINTS watch stock --prefix
-etcdctl --endpoints=$ENDPOINTS put stock1 10
-etcdctl --endpoints=$ENDPOINTS put stock2 20
-```
-
-
-## Lease
-
-`lease` to write with TTL:
-
-<img src="https://storage.googleapis.com/etcd/demo/07_etcdctl_lease_2016050501.gif" alt="07_etcdctl_lease_2016050501"/>
-
-```
-etcdctl --endpoints=$ENDPOINTS lease grant 300
-# lease 2be7547fbc6a5afa granted with TTL(300s)
-
-etcdctl --endpoints=$ENDPOINTS put sample value --lease=2be7547fbc6a5afa
-etcdctl --endpoints=$ENDPOINTS get sample
-
-etcdctl --endpoints=$ENDPOINTS lease keep-alive 2be7547fbc6a5afa
-etcdctl --endpoints=$ENDPOINTS lease revoke 2be7547fbc6a5afa
-# or after 300 seconds
-etcdctl --endpoints=$ENDPOINTS get sample
-```
-
-
-## Distributed locks
-
-`lock` for distributed lock:
-
-<img src="https://storage.googleapis.com/etcd/demo/08_etcdctl_lock_2016050501.gif" alt="08_etcdctl_lock_2016050501"/>
-
-```
-etcdctl --endpoints=$ENDPOINTS lock mutex1
-
-# another client with the same name blocks
-etcdctl --endpoints=$ENDPOINTS lock mutex1
-```
-
-
-## Elections
-
-`elect` for leader election:
-
-<img src="https://storage.googleapis.com/etcd/demo/09_etcdctl_elect_2016050501.gif" alt="09_etcdctl_elect_2016050501"/>
-
-```
-etcdctl --endpoints=$ENDPOINTS elect one p1
-
-# another client with the same name blocks
-etcdctl --endpoints=$ENDPOINTS elect one p2
-```
-
-
-## Cluster status
-
-Specify the initial cluster configuration for each machine:
-
-<img src="https://storage.googleapis.com/etcd/demo/10_etcdctl_endpoint_2016050501.gif" alt="10_etcdctl_endpoint_2016050501"/>
-
-```
-etcdctl --write-out=table --endpoints=$ENDPOINTS endpoint status
-
-+------------------+------------------+---------+---------+-----------+-----------+------------+
-|     ENDPOINT     |        ID        | VERSION | DB SIZE | IS LEADER | RAFT TERM | RAFT INDEX |
-+------------------+------------------+---------+---------+-----------+-----------+------------+
-| 10.240.0.17:2379 | 4917a7ab173fabe7 | 3.0.0   | 45 kB   | true      |         4 |      16726 |
-| 10.240.0.18:2379 | 59796ba9cd1bcd72 | 3.0.0   | 45 kB   | false     |         4 |      16726 |
-| 10.240.0.19:2379 | 94df724b66343e6c | 3.0.0   | 45 kB   | false     |         4 |      16726 |
-+------------------+------------------+---------+---------+-----------+-----------+------------+
-```
-
-```
-etcdctl --endpoints=$ENDPOINTS endpoint health
-
-10.240.0.17:2379 is healthy: successfully committed proposal: took = 3.345431ms
-10.240.0.19:2379 is healthy: successfully committed proposal: took = 3.767967ms
-10.240.0.18:2379 is healthy: successfully committed proposal: took = 4.025451ms
-```
-
-
-## Snapshot
-
-`snapshot` to save point-in-time snapshot of etcd database:
-
-<img src="https://storage.googleapis.com/etcd/demo/11_etcdctl_snapshot_2016051001.gif" alt="11_etcdctl_snapshot_2016051001"/>
-
-```
-etcdctl --endpoints=$ENDPOINTS snapshot save my.db
-
-Snapshot saved at my.db
-```
-
-```
-etcdctl --write-out=table --endpoints=$ENDPOINTS snapshot status my.db
-
-+---------+----------+------------+------------+
-|  HASH   | REVISION | TOTAL KEYS | TOTAL SIZE |
-+---------+----------+------------+------------+
-| c55e8b8 |        9 |         13 | 25 kB      |
-+---------+----------+------------+------------+
-```
-
-
-## Migrate
-
-`migrate` to transform etcd v2 to v3 data:
-
-<img src="https://storage.googleapis.com/etcd/demo/12_etcdctl_migrate_2016061602.gif" alt="12_etcdctl_migrate_2016061602"/>
-
-```
-# write key in etcd version 2 store
-export ETCDCTL_API=2
-etcdctl --endpoints=http://$ENDPOINT set foo bar
-
-# read key in etcd v2
-etcdctl --endpoints=$ENDPOINTS --output="json" get foo
-
-# stop etcd node to migrate, one by one
-
-# migrate v2 data
-export ETCDCTL_API=3
-etcdctl --endpoints=$ENDPOINT migrate --data-dir="default.etcd" --wal-dir="default.etcd/member/wal"
-
-# restart etcd node after migrate, one by one
-
-# confirm that the key got migrated
-etcdctl --endpoints=$ENDPOINTS get /foo
-```
-
-
-## Member
-
-`member` to add,remove,update membership:
-
-<img src="https://storage.googleapis.com/etcd/demo/13_etcdctl_member_2016062301.gif" alt="13_etcdctl_member_2016062301"/>
-
-```
-# For each machine
-TOKEN=my-etcd-token-1
-CLUSTER_STATE=new
-NAME_1=etcd-node-1
-NAME_2=etcd-node-2
-NAME_3=etcd-node-3
-HOST_1=10.240.0.13
-HOST_2=10.240.0.14
-HOST_3=10.240.0.15
-CLUSTER=${NAME_1}=http://${HOST_1}:2380,${NAME_2}=http://${HOST_2}:2380,${NAME_3}=http://${HOST_3}:2380
-
-# For node 1
-THIS_NAME=${NAME_1}
-THIS_IP=${HOST_1}
-etcd --data-dir=data.etcd --name ${THIS_NAME} \
-	--initial-advertise-peer-urls http://${THIS_IP}:2380 \
-	--listen-peer-urls http://${THIS_IP}:2380 \
-	--advertise-client-urls http://${THIS_IP}:2379 \
-	--listen-client-urls http://${THIS_IP}:2379 \
-	--initial-cluster ${CLUSTER} \
-	--initial-cluster-state ${CLUSTER_STATE} \
-	--initial-cluster-token ${TOKEN}
-
-# For node 2
-THIS_NAME=${NAME_2}
-THIS_IP=${HOST_2}
-etcd --data-dir=data.etcd --name ${THIS_NAME} \
-	--initial-advertise-peer-urls http://${THIS_IP}:2380 \
-	--listen-peer-urls http://${THIS_IP}:2380 \
-	--advertise-client-urls http://${THIS_IP}:2379 \
-	--listen-client-urls http://${THIS_IP}:2379 \
-	--initial-cluster ${CLUSTER} \
-	--initial-cluster-state ${CLUSTER_STATE} \
-	--initial-cluster-token ${TOKEN}
-
-# For node 3
-THIS_NAME=${NAME_3}
-THIS_IP=${HOST_3}
-etcd --data-dir=data.etcd --name ${THIS_NAME} \
-	--initial-advertise-peer-urls http://${THIS_IP}:2380 \
-	--listen-peer-urls http://${THIS_IP}:2380 \
-	--advertise-client-urls http://${THIS_IP}:2379 \
-	--listen-client-urls http://${THIS_IP}:2379 \
-	--initial-cluster ${CLUSTER} \
-	--initial-cluster-state ${CLUSTER_STATE} \
-	--initial-cluster-token ${TOKEN}
-```
-
-Then replace a member with `member remove` and `member add` commands:
-
-```
-# get member ID
-export ETCDCTL_API=3
-HOST_1=10.240.0.13
-HOST_2=10.240.0.14
-HOST_3=10.240.0.15
-etcdctl --endpoints=${HOST_1}:2379,${HOST_2}:2379,${HOST_3}:2379 member list
-
-# remove the member
-MEMBER_ID=278c654c9a6dfd3b
-etcdctl --endpoints=${HOST_1}:2379,${HOST_2}:2379,${HOST_3}:2379 \
-	member remove ${MEMBER_ID}
-
-# add a new member (node 4)
-export ETCDCTL_API=3
-NAME_1=etcd-node-1
-NAME_2=etcd-node-2
-NAME_4=etcd-node-4
-HOST_1=10.240.0.13
-HOST_2=10.240.0.14
-HOST_4=10.240.0.16 # new member
-etcdctl --endpoints=${HOST_1}:2379,${HOST_2}:2379 \
-	member add ${NAME_4} \
-	--peer-urls=http://${HOST_4}:2380
-```
-
-Next, start the new member with `--initial-cluster-state existing` flag:
-
-```
-# [WARNING] If the new member starts from the same disk space,
-# make sure to remove the data directory of the old member
-#
-# restart with 'existing' flag
-TOKEN=my-etcd-token-1
-CLUSTER_STATE=existing
-NAME_1=etcd-node-1
-NAME_2=etcd-node-2
-NAME_4=etcd-node-4
-HOST_1=10.240.0.13
-HOST_2=10.240.0.14
-HOST_4=10.240.0.16 # new member
-CLUSTER=${NAME_1}=http://${HOST_1}:2380,${NAME_2}=http://${HOST_2}:2380,${NAME_4}=http://${HOST_4}:2380
-
-THIS_NAME=${NAME_4}
-THIS_IP=${HOST_4}
-etcd --data-dir=data.etcd --name ${THIS_NAME} \
-	--initial-advertise-peer-urls http://${THIS_IP}:2380 \
-	--listen-peer-urls http://${THIS_IP}:2380 \
-	--advertise-client-urls http://${THIS_IP}:2379 \
-	--listen-client-urls http://${THIS_IP}:2379 \
-	--initial-cluster ${CLUSTER} \
-	--initial-cluster-state ${CLUSTER_STATE} \
-	--initial-cluster-token ${TOKEN}
-```
-
-
-## Auth
-
-`auth`,`user`,`role` for authentication:
-
-<img src="https://storage.googleapis.com/etcd/demo/14_etcdctl_auth_2016062301.gif" alt="14_etcdctl_auth_2016062301"/>
-
-```
-export ETCDCTL_API=3
-ENDPOINTS=localhost:2379
-
-etcdctl --endpoints=${ENDPOINTS} role add root
-etcdctl --endpoints=${ENDPOINTS} role grant-permission root readwrite foo
-etcdctl --endpoints=${ENDPOINTS} role get root
-
-etcdctl --endpoints=${ENDPOINTS} user add root
-etcdctl --endpoints=${ENDPOINTS} user grant-role root root
-etcdctl --endpoints=${ENDPOINTS} user get root
-
-etcdctl --endpoints=${ENDPOINTS} auth enable
-# now all client requests go through auth
-
-etcdctl --endpoints=${ENDPOINTS} --user=root:123 put foo bar
-etcdctl --endpoints=${ENDPOINTS} get foo
-etcdctl --endpoints=${ENDPOINTS} --user=root:123 get foo
-etcdctl --endpoints=${ENDPOINTS} --user=root:123 get foo1
-```

Documentation/dev-guide/api_concurrency_reference_v3.md

@@ -1,168 +0,0 @@
-### etcd concurrency API Reference
-
-
-This is a generated documentation. Please read the proto files for more.
-
-
-##### service `Lock` (etcdserver/api/v3lock/v3lockpb/v3lock.proto)
-
-The lock service exposes client-side locking facilities as a gRPC interface.
-
-| Method | Request Type | Response Type | Description |
-| ------ | ------------ | ------------- | ----------- |
-| Lock | LockRequest | LockResponse | Lock acquires a distributed shared lock on a given named lock. On success, it will return a unique key that exists so long as the lock is held by the caller. This key can be used in conjunction with transactions to safely ensure updates to etcd only occur while holding lock ownership. The lock is held until Unlock is called on the key or the lease associate with the owner expires. |
-| Unlock | UnlockRequest | UnlockResponse | Unlock takes a key returned by Lock and releases the hold on lock. The next Lock caller waiting for the lock will then be woken up and given ownership of the lock. |
-
-
-
-##### message `LockRequest` (etcdserver/api/v3lock/v3lockpb/v3lock.proto)
-
-| Field | Description | Type |
-| ----- | ----------- | ---- |
-| name | name is the identifier for the distributed shared lock to be acquired. | bytes |
-| lease | lease is the ID of the lease that will be attached to ownership of the lock. If the lease expires or is revoked and currently holds the lock, the lock is automatically released. Calls to Lock with the same lease will be treated as a single acquisition; locking twice with the same lease is a no-op. | int64 |
-
-
-
-##### message `LockResponse` (etcdserver/api/v3lock/v3lockpb/v3lock.proto)
-
-| Field | Description | Type |
-| ----- | ----------- | ---- |
-| header |  | etcdserverpb.ResponseHeader |
-| key | key is a key that will exist on etcd for the duration that the Lock caller owns the lock. Users should not modify this key or the lock may exhibit undefined behavior. | bytes |
-
-
-
-##### message `UnlockRequest` (etcdserver/api/v3lock/v3lockpb/v3lock.proto)
-
-| Field | Description | Type |
-| ----- | ----------- | ---- |
-| key | key is the lock ownership key granted by Lock. | bytes |
-
-
-
-##### message `UnlockResponse` (etcdserver/api/v3lock/v3lockpb/v3lock.proto)
-
-| Field | Description | Type |
-| ----- | ----------- | ---- |
-| header |  | etcdserverpb.ResponseHeader |
-
-
-
-##### service `Election` (etcdserver/api/v3election/v3electionpb/v3election.proto)
-
-The election service exposes client-side election facilities as a gRPC interface.
-
-| Method | Request Type | Response Type | Description |
-| ------ | ------------ | ------------- | ----------- |
-| Campaign | CampaignRequest | CampaignResponse | Campaign waits to acquire leadership in an election, returning a LeaderKey representing the leadership if successful. The LeaderKey can then be used to issue new values on the election, transactionally guard API requests on leadership still being held, and resign from the election. |
-| Proclaim | ProclaimRequest | ProclaimResponse | Proclaim updates the leader's posted value with a new value. |
-| Leader | LeaderRequest | LeaderResponse | Leader returns the current election proclamation, if any. |
-| Observe | LeaderRequest | LeaderResponse | Observe streams election proclamations in-order as made by the election's elected leaders. |
-| Resign | ResignRequest | ResignResponse | Resign releases election leadership so other campaigners may acquire leadership on the election. |
-
-
-
-##### message `CampaignRequest` (etcdserver/api/v3election/v3electionpb/v3election.proto)
-
-| Field | Description | Type |
-| ----- | ----------- | ---- |
-| name | name is the election's identifier for the campaign. | bytes |
-| lease | lease is the ID of the lease attached to leadership of the election. If the lease expires or is revoked before resigning leadership, then the leadership is transferred to the next campaigner, if any. | int64 |
-| value | value is the initial proclaimed value set when the campaigner wins the election. | bytes |
-
-
-
-##### message `CampaignResponse` (etcdserver/api/v3election/v3electionpb/v3election.proto)
-
-| Field | Description | Type |
-| ----- | ----------- | ---- |
-| header |  | etcdserverpb.ResponseHeader |
-| leader | leader describes the resources used for holding leadereship of the election. | LeaderKey |
-
-
-
-##### message `LeaderKey` (etcdserver/api/v3election/v3electionpb/v3election.proto)
-
-| Field | Description | Type |
-| ----- | ----------- | ---- |
-| name | name is the election identifier that correponds to the leadership key. | bytes |
-| key | key is an opaque key representing the ownership of the election. If the key is deleted, then leadership is lost. | bytes |
-| rev | rev is the creation revision of the key. It can be used to test for ownership of an election during transactions by testing the key's creation revision matches rev. | int64 |
-| lease | lease is the lease ID of the election leader. | int64 |
-
-
-
-##### message `LeaderRequest` (etcdserver/api/v3election/v3electionpb/v3election.proto)
-
-| Field | Description | Type |
-| ----- | ----------- | ---- |
-| name | name is the election identifier for the leadership information. | bytes |
-
-
-
-##### message `LeaderResponse` (etcdserver/api/v3election/v3electionpb/v3election.proto)
-
-| Field | Description | Type |
-| ----- | ----------- | ---- |
-| header |  | etcdserverpb.ResponseHeader |
-| kv | kv is the key-value pair representing the latest leader update. | mvccpb.KeyValue |
-
-
-
-##### message `ProclaimRequest` (etcdserver/api/v3election/v3electionpb/v3election.proto)
-
-| Field | Description | Type |
-| ----- | ----------- | ---- |
-| leader | leader is the leadership hold on the election. | LeaderKey |
-| value | value is an update meant to overwrite the leader's current value. | bytes |
-
-
-
-##### message `ProclaimResponse` (etcdserver/api/v3election/v3electionpb/v3election.proto)
-
-| Field | Description | Type |
-| ----- | ----------- | ---- |
-| header |  | etcdserverpb.ResponseHeader |
-
-
-
-##### message `ResignRequest` (etcdserver/api/v3election/v3electionpb/v3election.proto)
-
-| Field | Description | Type |
-| ----- | ----------- | ---- |
-| leader | leader is the leadership to relinquish by resignation. | LeaderKey |
-
-
-
-##### message `ResignResponse` (etcdserver/api/v3election/v3electionpb/v3election.proto)
-
-| Field | Description | Type |
-| ----- | ----------- | ---- |
-| header |  | etcdserverpb.ResponseHeader |
-
-
-
-##### message `Event` (mvcc/mvccpb/kv.proto)
-
-| Field | Description | Type |
-| ----- | ----------- | ---- |
-| type | type is the kind of event. If type is a PUT, it indicates new data has been stored to the key. If type is a DELETE, it indicates the key was deleted. | EventType |
-| kv | kv holds the KeyValue for the event. A PUT event contains current kv pair. A PUT event with kv.Version=1 indicates the creation of a key. A DELETE/EXPIRE event contains the deleted key with its modification revision set to the revision of deletion. | KeyValue |
-| prev_kv | prev_kv holds the key-value pair before the event happens. | KeyValue |
-
-
-
-##### message `KeyValue` (mvcc/mvccpb/kv.proto)
-
-| Field | Description | Type |
-| ----- | ----------- | ---- |
-| key | key is the key in bytes. An empty key is not allowed. | bytes |
-| create_revision | create_revision is the revision of last creation on this key. | int64 |
-| mod_revision | mod_revision is the revision of last modification on this key. | int64 |
-| version | version is the version of the key. A deletion resets the version to zero and any modification of the key increases its version. | int64 |
-| value | value is the value held by the key, in bytes. | bytes |
-| lease | lease is the ID of the lease that attached to key. When the attached lease expires, the key will be deleted. If lease is 0, then no lease is attached to the key. | int64 |
-
-
-

Documentation/dev-guide/api_grpc_gateway.md

@@ -1,137 +0,0 @@
----
-title: Why gRPC gateway
----
-
-etcd v3 uses [gRPC][grpc] for its messaging protocol. The etcd project includes a gRPC-based [Go client][go-client] and a command line utility, [etcdctl][etcdctl], for communicating with an etcd cluster through gRPC. For languages with no gRPC support, etcd provides a JSON [gRPC gateway][grpc-gateway]. This gateway serves a RESTful proxy that translates HTTP/JSON requests into gRPC messages.
-
-## Using gRPC gateway
-
-The gateway accepts a [JSON mapping][json-mapping] for etcd's [protocol buffer][api-ref] message definitions. Note that `key` and `value` fields are defined as byte arrays and therefore must be base64 encoded in JSON. The following examples use `curl`, but any HTTP/JSON client should work all the same.
-
-### Notes
-
-gRPC gateway endpoint has changed since etcd v3.3:
-
-- etcd v3.2 or before uses only `[CLIENT-URL]/v3alpha/*`.
-- etcd v3.3 uses `[CLIENT-URL]/v3beta/*` while keeping `[CLIENT-URL]/v3alpha/*`.
-- etcd v3.4 uses `[CLIENT-URL]/v3/*` while keeping `[CLIENT-URL]/v3beta/*`.
-  - **`[CLIENT-URL]/v3alpha/*` is deprecated**.
-- etcd v3.5 or later uses only `[CLIENT-URL]/v3/*`.
-  - **`[CLIENT-URL]/v3beta/*` is deprecated**.
-
-gRPC-gateway does not support authentication using TLS Common Name.
-
-### Put and get keys
-
-Use the `/v3/kv/range` and `/v3/kv/put` services to read and write keys:
-
-```bash
-<<COMMENT
-https://www.base64encode.org/
-foo is 'Zm9v' in Base64
-bar is 'YmFy'
-COMMENT
-
-curl -L http://localhost:2379/v3/kv/put \
-  -X POST -d '{"key": "Zm9v", "value": "YmFy"}'
-# {"header":{"cluster_id":"12585971608760269493","member_id":"13847567121247652255","revision":"2","raft_term":"3"}}
-
-curl -L http://localhost:2379/v3/kv/range \
-  -X POST -d '{"key": "Zm9v"}'
-# {"header":{"cluster_id":"12585971608760269493","member_id":"13847567121247652255","revision":"2","raft_term":"3"},"kvs":[{"key":"Zm9v","create_revision":"2","mod_revision":"2","version":"1","value":"YmFy"}],"count":"1"}
-
-# get all keys prefixed with "foo"
-curl -L http://localhost:2379/v3/kv/range \
-  -X POST -d '{"key": "Zm9v", "range_end": "Zm9w"}'
-# {"header":{"cluster_id":"12585971608760269493","member_id":"13847567121247652255","revision":"2","raft_term":"3"},"kvs":[{"key":"Zm9v","create_revision":"2","mod_revision":"2","version":"1","value":"YmFy"}],"count":"1"}
-```
-
-### Watch keys
-
-Use the `/v3/watch` service to watch keys:
-
-```bash
-curl -N http://localhost:2379/v3/watch \
-  -X POST -d '{"create_request": {"key":"Zm9v"} }' &
-# {"result":{"header":{"cluster_id":"12585971608760269493","member_id":"13847567121247652255","revision":"1","raft_term":"2"},"created":true}}
-
-curl -L http://localhost:2379/v3/kv/put \
-  -X POST -d '{"key": "Zm9v", "value": "YmFy"}' >/dev/null 2>&1
-# {"result":{"header":{"cluster_id":"12585971608760269493","member_id":"13847567121247652255","revision":"2","raft_term":"2"},"events":[{"kv":{"key":"Zm9v","create_revision":"2","mod_revision":"2","version":"1","value":"YmFy"}}]}}
-```
-
-### Transactions
-
-Issue a transaction with `/v3/kv/txn`:
-
-```bash
-# target CREATE
-curl -L http://localhost:2379/v3/kv/txn \
-  -X POST \
-  -d '{"compare":[{"target":"CREATE","key":"Zm9v","createRevision":"2"}],"success":[{"requestPut":{"key":"Zm9v","value":"YmFy"}}]}'
-# {"header":{"cluster_id":"12585971608760269493","member_id":"13847567121247652255","revision":"3","raft_term":"2"},"succeeded":true,"responses":[{"response_put":{"header":{"revision":"3"}}}]}
-```
-
-```bash
-# target VERSION
-curl -L http://localhost:2379/v3/kv/txn \
-  -X POST \
-  -d '{"compare":[{"version":"4","result":"EQUAL","target":"VERSION","key":"Zm9v"}],"success":[{"requestRange":{"key":"Zm9v"}}]}'
-# {"header":{"cluster_id":"14841639068965178418","member_id":"10276657743932975437","revision":"6","raft_term":"3"},"succeeded":true,"responses":[{"response_range":{"header":{"revision":"6"},"kvs":[{"key":"Zm9v","create_revision":"2","mod_revision":"6","version":"4","value":"YmF6"}],"count":"1"}}]}
-```
-
-### Authentication
-
-Set up authentication with the `/v3/auth` service:
-
-```bash
-# create root user
-curl -L http://localhost:2379/v3/auth/user/add \
-  -X POST -d '{"name": "root", "password": "pass"}'
-# {"header":{"cluster_id":"14841639068965178418","member_id":"10276657743932975437","revision":"1","raft_term":"2"}}
-
-# create root role
-curl -L http://localhost:2379/v3/auth/role/add \
-  -X POST -d '{"name": "root"}'
-# {"header":{"cluster_id":"14841639068965178418","member_id":"10276657743932975437","revision":"1","raft_term":"2"}}
-
-# grant root role
-curl -L http://localhost:2379/v3/auth/user/grant \
-  -X POST -d '{"user": "root", "role": "root"}'
-# {"header":{"cluster_id":"14841639068965178418","member_id":"10276657743932975437","revision":"1","raft_term":"2"}}
-
-# enable auth
-curl -L http://localhost:2379/v3/auth/enable -X POST -d '{}'
-# {"header":{"cluster_id":"14841639068965178418","member_id":"10276657743932975437","revision":"1","raft_term":"2"}}
-```
-
-Authenticate with etcd for an authentication token using `/v3/auth/authenticate`:
-
-```bash
-# get the auth token for the root user
-curl -L http://localhost:2379/v3/auth/authenticate \
-  -X POST -d '{"name": "root", "password": "pass"}'
-# {"header":{"cluster_id":"14841639068965178418","member_id":"10276657743932975437","revision":"1","raft_term":"2"},"token":"sssvIpwfnLAcWAQH.9"}
-```
-
-Set the `Authorization` header to the authentication token to fetch a key using authentication credentials:
-
-```bash
-curl -L http://localhost:2379/v3/kv/put \
-  -H 'Authorization : sssvIpwfnLAcWAQH.9' \
-  -X POST -d '{"key": "Zm9v", "value": "YmFy"}'
-# {"header":{"cluster_id":"14841639068965178418","member_id":"10276657743932975437","revision":"2","raft_term":"2"}}
-```
-
-## Swagger
-
-Generated [Swagger][swagger] API definitions can be found at [rpc.swagger.json][swagger-doc].
-
-[api-ref]: ./api_reference_v3.md
-[go-client]: https://github.com/coreos/etcd/tree/master/clientv3
-[etcdctl]: https://github.com/coreos/etcd/tree/master/etcdctl
-[grpc]: https://www.grpc.io/
-[grpc-gateway]: https://github.com/grpc-ecosystem/grpc-gateway
-[json-mapping]: https://developers.google.com/protocol-buffers/docs/proto3#json
-[swagger]: http://swagger.io/
-[swagger-doc]: apispec/swagger/rpc.swagger.json

Documentation/dev-guide/apispec/swagger/v3election.swagger.json

@@ -1,13 +1,9 @@
 {
   "swagger": "2.0",
   "info": {
-    "title": "etcdserver/api/v3election/v3electionpb/v3election.proto",
+    "title": "server/etcdserver/api/v3election/v3electionpb/v3election.proto",
     "version": "version not set"
   },
-  "schemes": [
-    "http",
-    "https"
-  ],
   "consumes": [
     "application/json"
   ],
@@ -18,13 +14,19 @@
     "/v3/election/campaign": {
       "post": {
         "summary": "Campaign waits to acquire leadership in an election, returning a LeaderKey\nrepresenting the leadership if successful. The LeaderKey can then be used\nto issue new values on the election, transactionally guard API requests on\nleadership still being held, and resign from the election.",
-        "operationId": "Campaign",
+        "operationId": "Election_Campaign",
         "responses": {
           "200": {
             "description": "A successful response.",
             "schema": {
               "$ref": "#/definitions/v3electionpbCampaignResponse"
             }
+          },
+          "default": {
+            "description": "An unexpected error response",
+            "schema": {
+              "$ref": "#/definitions/runtimeError"
+            }
           }
         },
         "parameters": [
@@ -45,13 +47,19 @@
     "/v3/election/leader": {
       "post": {
         "summary": "Leader returns the current election proclamation, if any.",
-        "operationId": "Leader",
+        "operationId": "Election_Leader",
         "responses": {
           "200": {
             "description": "A successful response.",
             "schema": {
               "$ref": "#/definitions/v3electionpbLeaderResponse"
             }
+          },
+          "default": {
+            "description": "An unexpected error response",
+            "schema": {
+              "$ref": "#/definitions/runtimeError"
+            }
           }
         },
         "parameters": [
@@ -72,12 +80,27 @@
     "/v3/election/observe": {
       "post": {
         "summary": "Observe streams election proclamations in-order as made by the election's\nelected leaders.",
-        "operationId": "Observe",
+        "operationId": "Election_Observe",
         "responses": {
           "200": {
             "description": "A successful response.(streaming responses)",
             "schema": {
-              "$ref": "#/x-stream-definitions/v3electionpbLeaderResponse"
+              "type": "object",
+              "properties": {
+                "result": {
+                  "$ref": "#/definitions/v3electionpbLeaderResponse"
+                },
+                "error": {
+                  "$ref": "#/definitions/runtimeStreamError"
+                }
+              },
+              "title": "Stream result of v3electionpbLeaderResponse"
+            }
+          },
+          "default": {
+            "description": "An unexpected error response",
+            "schema": {
+              "$ref": "#/definitions/runtimeError"
             }
           }
         },
@@ -99,13 +122,19 @@
     "/v3/election/proclaim": {
       "post": {
         "summary": "Proclaim updates the leader's posted value with a new value.",
-        "operationId": "Proclaim",
+        "operationId": "Election_Proclaim",
         "responses": {
           "200": {
             "description": "A successful response.",
             "schema": {
               "$ref": "#/definitions/v3electionpbProclaimResponse"
             }
+          },
+          "default": {
+            "description": "An unexpected error response",
+            "schema": {
+              "$ref": "#/definitions/runtimeError"
+            }
           }
         },
         "parameters": [
@@ -126,13 +155,19 @@
     "/v3/election/resign": {
       "post": {
         "summary": "Resign releases election leadership so other campaigners may acquire\nleadership on the election.",
-        "operationId": "Resign",
+        "operationId": "Election_Resign",
         "responses": {
           "200": {
             "description": "A successful response.",
             "schema": {
               "$ref": "#/definitions/v3electionpbResignResponse"
             }
+          },
+          "default": {
+            "description": "An unexpected error response",
+            "schema": {
+              "$ref": "#/definitions/runtimeError"
+            }
           }
         },
         "parameters": [
@@ -224,6 +259,27 @@
         }
       }
     },
+    "runtimeError": {
+      "type": "object",
+      "properties": {
+        "error": {
+          "type": "string"
+        },
+        "code": {
+          "type": "integer",
+          "format": "int32"
+        },
+        "message": {
+          "type": "string"
+        },
+        "details": {
+          "type": "array",
+          "items": {
+            "$ref": "#/definitions/protobufAny"
+          }
+        }
+      }
+    },
     "runtimeStreamError": {
       "type": "object",
       "properties": {
@@ -367,19 +423,5 @@
         }
       }
     }
-  },
-  "x-stream-definitions": {
-    "v3electionpbLeaderResponse": {
-      "type": "object",
-      "properties": {
-        "result": {
-          "$ref": "#/definitions/v3electionpbLeaderResponse"
-        },
-        "error": {
-          "$ref": "#/definitions/runtimeStreamError"
-        }
-      },
-      "title": "Stream result of v3electionpbLeaderResponse"
-    }
   }
 }

Documentation/dev-guide/apispec/swagger/v3lock.swagger.json

@@ -1,13 +1,9 @@
 {
   "swagger": "2.0",
   "info": {
-    "title": "etcdserver/api/v3lock/v3lockpb/v3lock.proto",
+    "title": "server/etcdserver/api/v3lock/v3lockpb/v3lock.proto",
     "version": "version not set"
   },
-  "schemes": [
-    "http",
-    "https"
-  ],
   "consumes": [
     "application/json"
   ],
@@ -18,13 +14,19 @@
     "/v3/lock/lock": {
       "post": {
         "summary": "Lock acquires a distributed shared lock on a given named lock.\nOn success, it will return a unique key that exists so long as the\nlock is held by the caller. This key can be used in conjunction with\ntransactions to safely ensure updates to etcd only occur while holding\nlock ownership. The lock is held until Unlock is called on the key or the\nlease associate with the owner expires.",
-        "operationId": "Lock",
+        "operationId": "Lock_Lock",
         "responses": {
           "200": {
             "description": "A successful response.",
             "schema": {
               "$ref": "#/definitions/v3lockpbLockResponse"
             }
+          },
+          "default": {
+            "description": "An unexpected error response",
+            "schema": {
+              "$ref": "#/definitions/runtimeError"
+            }
           }
         },
         "parameters": [
@@ -45,13 +47,19 @@
     "/v3/lock/unlock": {
       "post": {
         "summary": "Unlock takes a key returned by Lock and releases the hold on lock. The\nnext Lock caller waiting for the lock will then be woken up and given\nownership of the lock.",
-        "operationId": "Unlock",
+        "operationId": "Lock_Unlock",
         "responses": {
           "200": {
             "description": "A successful response.",
             "schema": {
               "$ref": "#/definitions/v3lockpbUnlockResponse"
             }
+          },
+          "default": {
+            "description": "An unexpected error response",
+            "schema": {
+              "$ref": "#/definitions/runtimeError"
+            }
           }
         },
         "parameters": [
@@ -96,6 +104,39 @@
         }
       }
     },
+    "protobufAny": {
+      "type": "object",
+      "properties": {
+        "type_url": {
+          "type": "string"
+        },
+        "value": {
+          "type": "string",
+          "format": "byte"
+        }
+      }
+    },
+    "runtimeError": {
+      "type": "object",
+      "properties": {
+        "error": {
+          "type": "string"
+        },
+        "code": {
+          "type": "integer",
+          "format": "int32"
+        },
+        "message": {
+          "type": "string"
+        },
+        "details": {
+          "type": "array",
+          "items": {
+            "$ref": "#/definitions/protobufAny"
+          }
+        }
+      }
+    },
     "v3lockpbLockRequest": {
       "type": "object",
       "properties": {

Documentation/dev-guide/experimental_apis.md

@@ -1,9 +0,0 @@
----
-title: Experimental APIs and features
----
-
-For the most part, the etcd project is stable, but we are still moving fast! We believe in the release fast philosophy. We want to get early feedback on features still in development and stabilizing. Thus, there are, and will be more, experimental features and APIs. We plan to improve these features based on the early feedback from the community, or abandon them if there is little interest, in the next few releases. Please do not rely on any experimental features or APIs in production environment.
-
-## The current experimental API/features are:
-
-- [KV ordering](https://godoc.org/github.com/etcd-io/etcd/clientv3/ordering) wrapper. When an etcd client switches endpoints, responses to serializable reads may go backward in time if the new endpoint is lagging behind the rest of the cluster. The ordering wrapper caches the current cluster revision from response headers. If a response revision is less than the cached revision, the client selects another endpoint and reissues the read. Enable in grpcproxy with `--experimental-serializable-ordering`.

Documentation/dev-guide/grpc_naming.md

@@ -1,67 +0,0 @@
----
-title: gRPC naming and discovery
----
-
-etcd provides a gRPC resolver to support an alternative name system that fetches endpoints from etcd for discovering gRPC services. The underlying mechanism is based on watching updates to keys prefixed with the service name.
-
-## Using etcd discovery with go-grpc
-
-The etcd client provides a gRPC resolver for resolving gRPC endpoints with an etcd backend. The resolver is initialized with an etcd client and given a target for resolution:
-
-```go
-import (
-	"go.etcd.io/etcd/clientv3"
-	etcdnaming "go.etcd.io/etcd/clientv3/naming"
-
-	"google.golang.org/grpc"
-)
-
-...
-
-cli, cerr := clientv3.NewFromURL("http://localhost:2379")
-r := &etcdnaming.GRPCResolver{Client: cli}
-b := grpc.RoundRobin(r)
-conn, gerr := grpc.Dial("my-service", grpc.WithBalancer(b), grpc.WithBlock(), ...)
-```
-
-## Managing service endpoints
-
-The etcd resolver treats all keys under the prefix of the resolution target following a "/" (e.g., "my-service/") with JSON-encoded go-grpc `naming.Update` values as potential service endpoints. Endpoints are added to the service by creating new keys and removed from the service by deleting keys.
-
-### Adding an endpoint
-
-New endpoints can be added to the service through `etcdctl`:
-
-```sh
-ETCDCTL_API=3 etcdctl put my-service/1.2.3.4 '{"Addr":"1.2.3.4","Metadata":"..."}'
-```
-
-The etcd client's `GRPCResolver.Update` method can also register new endpoints with a key matching the `Addr`:
-
-```go
-r.Update(context.TODO(), "my-service", naming.Update{Op: naming.Add, Addr: "1.2.3.4", Metadata: "..."})
-```
-
-### Deleting an endpoint
-
-Hosts can be deleted from the service through `etcdctl`:
-
-```sh
-ETCDCTL_API=3 etcdctl del my-service/1.2.3.4
-```
-
-The etcd client's `GRPCResolver.Update` method also supports deleting endpoints:
-
-```go
-r.Update(context.TODO(), "my-service", naming.Update{Op: naming.Delete, Addr: "1.2.3.4"})
-```
-
-### Registering an endpoint with a lease
-
-Registering an endpoint with a lease ensures that if the host can't maintain a keepalive heartbeat (e.g., its machine fails), it will be removed from the service:
-
-```sh
-lease=`ETCDCTL_API=3 etcdctl lease grant 5 | cut -f2 -d' '`
-ETCDCTL_API=3 etcdctl put --lease=$lease my-service/1.2.3.4 '{"Addr":"1.2.3.4","Metadata":"..."}'
-ETCDCTL_API=3 etcdctl lease keep-alive $lease
-```

Documentation/dev-guide/interacting_v3.md

@@ -1,499 +0,0 @@
----
-title: Interacting with etcd
----
-
-Users mostly interact with etcd by putting or getting the value of a key. This section describes how to do that by using etcdctl, a command line tool for interacting with etcd server. The concepts described here should apply to the gRPC APIs or client library APIs.
-
-The API version used by etcdctl to speak to etcd may be set to version `2` or `3` via the `ETCDCTL_API` environment variable. By default, etcdctl on master (3.4) uses the v3 API and earlier versions (3.3 and earlier) default to the v2 API.
-
-Note that any key that was created using the v2 API will not be able to be queried via the v3 API.  A v3 API ```etcdctl get``` of a v2 key will exit with 0 and no key data, this is the expected behaviour.
-
-
-```bash
-export ETCDCTL_API=3
-```
-
-## Find versions
-
-etcdctl version and Server API version can be useful in finding the appropriate commands to be used for performing various operations on etcd.
-
-Here is the command to find the versions:
-
-```bash
-$ etcdctl version
-etcdctl version: 3.1.0-alpha.0+git
-API version: 3.1
-```
-
-## Write a key
-
-Applications store keys into the etcd cluster by writing to keys. Every stored key is replicated to all etcd cluster members through the Raft protocol to achieve consistency and reliability.
-
-Here is the command to set the value of key `foo` to `bar`:
-
-```bash
-$ etcdctl put foo bar
-OK
-```
-
-Also a key can be set for a specified interval of time by attaching lease to it.
-
-Here is the command to set the value of key `foo1` to `bar1` for 10s.
-
-```bash
-$ etcdctl put foo1 bar1 --lease=1234abcd
-OK
-```
-
-Note: The lease id `1234abcd` in the above command refers to id returned on creating the lease of 10s. This id can then be attached to the key.
-
-## Read keys
-
-Applications can read values of keys from an etcd cluster. Queries may read a single key, or a range of keys.
-
-Suppose the etcd cluster has stored the following keys:
-
-```bash
-foo = bar
-foo1 = bar1
-foo2 = bar2
-foo3 = bar3
-```
-
-Here is the command to read the value of key `foo`:
-
-```bash
-$ etcdctl get foo
-foo
-bar
-```
-
-Here is the command to read the value of key `foo` in hex format:
-
-```bash
-$ etcdctl get foo --hex
-\x66\x6f\x6f          # Key
-\x62\x61\x72          # Value
-```
-
-Here is the command to read only the value of key `foo`:
-
-```bash
-$ etcdctl get foo --print-value-only
-bar
-```
-
-Here is the command to range over the keys from `foo` to `foo3`:
-
-```bash
-$ etcdctl get foo foo3
-foo
-bar
-foo1
-bar1
-foo2
-bar2
-```
-
-Note that `foo3` is excluded since the range is over the half-open interval `[foo, foo3)`, excluding `foo3`.
-
-Here is the command to range over all keys prefixed with `foo`:
-
-```bash
-$ etcdctl get --prefix foo
-foo
-bar
-foo1
-bar1
-foo2
-bar2
-foo3
-bar3
-```
-
-Here is the command to range over all keys prefixed with `foo`, limiting the number of results to 2:
-
-```bash
-$ etcdctl get --prefix --limit=2 foo
-foo
-bar
-foo1
-bar1
-```
-
-## Read past version of keys
-
-Applications may want to read superseded versions of a key. For example, an application may wish to roll back to an old configuration by accessing an earlier version of a key. Alternatively, an application may want a consistent view over multiple keys through multiple requests by accessing key history.
-Since every modification to the etcd cluster key-value store increments the global revision of an etcd cluster, an application can read superseded keys by providing an older etcd revision.
-
-Suppose an etcd cluster already has the following keys:
-
-```bash
-foo = bar         # revision = 2
-foo1 = bar1       # revision = 3
-foo = bar_new     # revision = 4
-foo1 = bar1_new   # revision = 5
-```
-
-Here are an example to access the past versions of keys:
-
-```bash
-$ etcdctl get --prefix foo # access the most recent versions of keys
-foo
-bar_new
-foo1
-bar1_new
-
-$ etcdctl get --prefix --rev=4 foo # access the versions of keys at revision 4
-foo
-bar_new
-foo1
-bar1
-
-$ etcdctl get --prefix --rev=3 foo # access the versions of keys at revision 3
-foo
-bar
-foo1
-bar1
-
-$ etcdctl get --prefix --rev=2 foo # access the versions of keys at revision 2
-foo
-bar
-
-$ etcdctl get --prefix --rev=1 foo # access the versions of keys at revision 1
-```
-
-## Read keys which are greater than or equal to the byte value of the specified key
-
-Applications may want to read keys which are greater than or equal to the byte value of the specified key.
-
-Suppose an etcd cluster already has the following keys:
-
-```bash
-a = 123
-b = 456
-z = 789
-```
-
-Here is the command to read keys which are greater than or equal to the byte value of key `b` :
-
-```bash
-$ etcdctl get --from-key b
-b
-456
-z
-789
-```
-
-## Delete keys
-
-Applications can delete a key or a range of keys from an etcd cluster.
-
-Suppose an etcd cluster already has the following keys:
-
-```bash
-foo = bar
-foo1 = bar1
-foo3 = bar3
-zoo = val
-zoo1 = val1
-zoo2 = val2
-a = 123
-b = 456
-z = 789
-```
-
-Here is the command to delete key `foo`:
-
-```bash
-$ etcdctl del foo
-1 # one key is deleted
-```
-
-Here is the command to delete keys ranging from `foo` to `foo9`:
-
-```bash
-$ etcdctl del foo foo9
-2 # two keys are deleted
-```
-
-Here is the command to delete key `zoo` with the deleted key value pair returned:
-
-```bash
-$ etcdctl del --prev-kv zoo
-1   # one key is deleted
-zoo # deleted key
-val # the value of the deleted key
-```
-
-Here is the command to delete keys having prefix as `zoo`:
-
-```bash
-$ etcdctl del --prefix zoo
-2 # two keys are deleted
-```
-
-Here is the command to delete keys which are greater than or equal to the byte value of key `b` :
-
-```bash
-$ etcdctl del --from-key b
-2 # two keys are deleted
-```
-
-## Watch key changes
-
-Applications can watch on a key or a range of keys to monitor for any updates.
-
-Here is the command to watch on key `foo`:
-
-```bash
-$ etcdctl watch foo
-# in another terminal: etcdctl put foo bar
-PUT
-foo
-bar
-```
-
-Here is the command to watch on key `foo` in hex format:
-
-```bash
-$ etcdctl watch foo --hex
-# in another terminal: etcdctl put foo bar
-PUT
-\x66\x6f\x6f          # Key
-\x62\x61\x72          # Value
-```
-
-Here is the command to watch on a range key from `foo` to `foo9`:
-
-```bash
-$ etcdctl watch foo foo9
-# in another terminal: etcdctl put foo bar
-PUT
-foo
-bar
-# in another terminal: etcdctl put foo1 bar1
-PUT
-foo1
-bar1
-```
-
-Here is the command to watch on keys having prefix `foo`:
-
-```bash
-$ etcdctl watch --prefix foo
-# in another terminal: etcdctl put foo bar
-PUT
-foo
-bar
-# in another terminal: etcdctl put fooz1 barz1
-PUT
-fooz1
-barz1
-```
-
-Here is the command to watch on multiple keys `foo` and `zoo`:
-
-```bash
-$ etcdctl watch -i
-$ watch foo
-$ watch zoo
-# in another terminal: etcdctl put foo bar
-PUT
-foo
-bar
-# in another terminal: etcdctl put zoo val
-PUT
-zoo
-val
-```
-
-## Watch historical changes of keys
-
-Applications may want to watch for historical changes of keys in etcd. For example, an application may wish to receive all the modifications of a key; if the application stays connected to etcd, then `watch` is good enough. However, if the application or etcd fails, a change may happen during the failure, and the application will not receive the update in real time. To guarantee the update is delivered, the application must be able to watch for historical changes to keys. To do this, an application can specify a historical revision on a watch, just like reading past version of keys.
-
-Suppose we finished the following sequence of operations:
-
-```bash
-$ etcdctl put foo bar         # revision = 2
-OK
-$ etcdctl put foo1 bar1       # revision = 3
-OK
-$ etcdctl put foo bar_new     # revision = 4
-OK
-$ etcdctl put foo1 bar1_new   # revision = 5
-OK
-```
-
-Here is an example to watch the historical changes:
-
-```bash
-# watch for changes on key `foo` since revision 2
-$ etcdctl watch --rev=2 foo
-PUT
-foo
-bar
-PUT
-foo
-bar_new
-```
-
-```bash
-# watch for changes on key `foo` since revision 3
-$ etcdctl watch --rev=3 foo
-PUT
-foo
-bar_new
-```
-
-Here is an example to watch only from the last historical change:
-
-```bash
-# watch for changes on key `foo` and return last revision value along with modified value
-$ etcdctl watch --prev-kv foo
-# in another terminal: etcdctl put foo bar_latest
-PUT
-foo         # key
-bar_new     # last value of foo key before modification
-foo         # key
-bar_latest  # value of foo key after modification
-```
-
-## Watch progress
-
-Applications may want to check the progress of a watch to determine how up-to-date the watch stream is. For example, if a watch is used to update a cache, it can be useful to know if the cache is stale compared to the revision from a quorum read. 
-
-Progress requests can be issued using the "progress" command in interactive watch session to ask the etcd server to send a progress notify update in the watch stream:
-
-```bash
-$ etcdctl watch -i
-$ watch a
-$ progress
-progress notify: 1
-# in another terminal: etcdctl put x 0
-# in another terminal: etcdctl put y 1
-$ progress
-progress notify: 3
-```
-
-Note: The revision number in the progress notify response is the revision from the local etcd server node that the watch stream is connected to. If this node is partitioned and not part of quorum, this progress notify revision might be lower than 
-than the revision returned by a quorum read against a non-partitioned etcd server node.
-
-## Compacted revisions
-
-As we mentioned, etcd keeps revisions so that applications can read past versions of keys. However, to avoid accumulating an unbounded amount of history, it is important to compact past revisions. After compacting, etcd removes historical revisions, releasing resources for future use. All superseded data with revisions before the compacted revision will be unavailable.
-
-Here is the command to compact the revisions:
-
-```bash
-$ etcdctl compact 5
-compacted revision 5
-
-# any revisions before the compacted one are not accessible
-$ etcdctl get --rev=4 foo
-Error:  rpc error: code = 11 desc = etcdserver: mvcc: required revision has been compacted
-```
-
-Note: The current revision of etcd server can be found using get command on any key (existent or non-existent) in json format. Example is shown below for mykey which does not exist in etcd server:
-
-```bash
-$ etcdctl get mykey -w=json
-{"header":{"cluster_id":14841639068965178418,"member_id":10276657743932975437,"revision":15,"raft_term":4}}
-```
-
-## Grant leases
-
-Applications can grant leases for keys from an etcd cluster. When a key is attached to a lease, its lifetime is bound to the lease's lifetime which in turn is governed by a time-to-live (TTL). Each lease has a minimum time-to-live (TTL) value specified by the application at grant time. The lease's actual TTL value is at least the minimum TTL and is chosen by the etcd cluster. Once a lease's TTL elapses, the lease expires and all attached keys are deleted.
-
-Here is the command to grant a lease:
-
-```bash
-# grant a lease with 10 second TTL
-$ etcdctl lease grant 10
-lease 32695410dcc0ca06 granted with TTL(10s)
-
-# attach key foo to lease 32695410dcc0ca06
-$ etcdctl put --lease=32695410dcc0ca06 foo bar
-OK
-```
-
-## Revoke leases
-
-Applications revoke leases by lease ID. Revoking a lease deletes all of its attached keys.
-
-Suppose we finished the following sequence of operations:
-
-```bash
-$ etcdctl lease grant 10
-lease 32695410dcc0ca06 granted with TTL(10s)
-$ etcdctl put --lease=32695410dcc0ca06 foo bar
-OK
-```
-
-Here is the command to revoke the same lease:
-
-```bash
-$ etcdctl lease revoke 32695410dcc0ca06
-lease 32695410dcc0ca06 revoked
-
-$ etcdctl get foo
-# empty response since foo is deleted due to lease revocation
-```
-
-## Keep leases alive
-
-Applications can keep a lease alive by refreshing its TTL so it does not expire.
-
-Suppose we finished the following sequence of operations:
-
-```bash
-$ etcdctl lease grant 10
-lease 32695410dcc0ca06 granted with TTL(10s)
-```
-
-Here is the command to keep the same lease alive:
-
-```bash
-$ etcdctl lease keep-alive 32695410dcc0ca06
-lease 32695410dcc0ca06 keepalived with TTL(10)
-lease 32695410dcc0ca06 keepalived with TTL(10)
-lease 32695410dcc0ca06 keepalived with TTL(10)
-...
-```
-
-## Get lease information
-
-Applications may want to know about lease information, so that they can be renewed or to check if the lease still exists or it has expired. Applications may also want to know the keys to which a particular lease is attached.
-
-Suppose we finished the following sequence of operations:
-
-```bash
-# grant a lease with 500 second TTL
-$ etcdctl lease grant 500
-lease 694d5765fc71500b granted with TTL(500s)
-
-# attach key zoo1 to lease 694d5765fc71500b
-$ etcdctl put zoo1 val1 --lease=694d5765fc71500b
-OK
-
-# attach key zoo2 to lease 694d5765fc71500b
-$ etcdctl put zoo2 val2 --lease=694d5765fc71500b
-OK
-```
-
-Here is the command to get information about the lease:
-
-```bash
-$ etcdctl lease timetolive 694d5765fc71500b
-lease 694d5765fc71500b granted with TTL(500s), remaining(258s)
-```
-
-Here is the command to get information about the lease along with the keys attached with the lease:
-
-```bash
-$ etcdctl lease timetolive --keys 694d5765fc71500b
-lease 694d5765fc71500b granted with TTL(500s), remaining(132s), attached keys([zoo2 zoo1])
-
-# if the lease has expired or does not exist it will give the below response:
-Error:  etcdserver: requested lease not found
-```

Documentation/dev-guide/limit.md

@@ -1,11 +0,0 @@
----
-title: System limits
----
-
-## Request size limit
-
-etcd is designed to handle small key value pairs typical for metadata. Larger requests will work, but may increase the latency of other requests. By default, the maximum size of any request is 1.5 MiB. This limit is configurable through `--max-request-bytes` flag for etcd server.
-
-## Storage size limit
-
-The default storage size limit is 2GB, configurable with `--quota-backend-bytes` flag. 8GB is a suggested maximum size for normal environments and etcd warns at startup if the configured value exceeds it.

Documentation/dev-guide/local_cluster.md

@@ -1,151 +0,0 @@
----
-title: Set up a local cluster
----
-
-For testing and development deployments, the quickest and easiest way is to configure a local cluster. For a production deployment, refer to the [clustering][clustering] section.
-
-## Local standalone cluster
-
-### Starting a cluster
-
-Run the following to deploy an etcd cluster as a standalone cluster:
-
-```
-$ ./etcd
-...
-```
-
-If the `etcd` binary is not present in the current working directory, it might be located either at `$GOPATH/bin/etcd` or at `/usr/local/bin/etcd`. Run the command appropriately.
-
-The running etcd member listens on `localhost:2379` for client requests.
-
-### Interacting with the cluster
-
-Use `etcdctl` to interact with the running cluster:
-
-1. Store an example key-value pair in the cluster:
-
-    ```
-      $ ./etcdctl put foo bar
-      OK
-    ```
-
-    If OK is printed, storing key-value pair is successful.
-
-2. Retrieve the value of `foo`:
-
-    ```
-    $ ./etcdctl get foo
-    bar
-    ```
-
-    If `bar` is returned, interaction with the etcd cluster is working as expected.
-
-## Local multi-member cluster
-
-### Starting a cluster
-
-A `Procfile` at the base of the etcd git repository is provided to easily configure a local multi-member cluster. To start a multi-member cluster, navigate to the root of the etcd source tree and perform the following:
-
-1. Install `goreman` to control Procfile-based applications:
-
-    ```
-    $ go get github.com/mattn/goreman
-    ```
-
-2. Start a cluster with `goreman` using etcd's stock Procfile:
-
-    ```
-    $ goreman -f Procfile start
-    ```
-
-    The members start running. They listen on `localhost:2379`, `localhost:22379`, and `localhost:32379` respectively for client requests.
-
-### Interacting with the cluster
-
-Use `etcdctl` to interact with the running cluster:
-
-1. Print the list of members:
-
-    ```
-    $ etcdctl --write-out=table --endpoints=localhost:2379 member list
-    ```
-    The list of etcd members are displayed as follows:
-
-    ```
-    +------------------+---------+--------+------------------------+------------------------+
-    |        ID        | STATUS  |  NAME  |       PEER ADDRS       |      CLIENT ADDRS      |
-    +------------------+---------+--------+------------------------+------------------------+
-    | 8211f1d0f64f3269 | started | infra1 | http://127.0.0.1:2380  | http://127.0.0.1:2379  |
-    | 91bc3c398fb3c146 | started | infra2 | http://127.0.0.1:22380 | http://127.0.0.1:22379 |
-    | fd422379fda50e48 | started | infra3 | http://127.0.0.1:32380 | http://127.0.0.1:32379 |
-    +------------------+---------+--------+------------------------+------------------------+
-    ```
-
-2. Store an example key-value pair in the cluster:
-
-    ```
-    $ etcdctl put foo bar
-    OK
-    ```
-
-    If OK is printed, storing key-value pair is successful.
-
-### Testing fault tolerance  
-
-To exercise etcd's fault tolerance, kill a member and attempt to retrieve the key.
-
-1. Identify the process name of the member to be stopped.
-
-    The `Procfile` lists the properties of the multi-member cluster. For example, consider the member with the process name, `etcd2`.
-
-2. Stop the member:
-
-    ```
-    # kill etcd2
-    $ goreman run stop etcd2
-    ```
-
-3. Store a key:
-
-    ```
-    $ etcdctl put key hello
-    OK
-    ```
-
-4.  Retrieve the key that is stored in the previous step:
-
-    ```
-    $ etcdctl get key
-    hello
-    ```
-
-5. Retrieve a key from the stopped member:
-
-    ```
-    $ etcdctl --endpoints=localhost:22379 get key
-    ```
-
-    The command should display an error caused by connection failure:
-
-    ```
-    2017/06/18 23:07:35 grpc: Conn.resetTransport failed to create client transport: connection error: desc = "transport: dial tcp 127.0.0.1:22379: getsockopt: connection refused"; Reconnecting to "localhost:22379"
-    Error:  grpc: timed out trying to connect
-    ```
-6. Restart the stopped member:
-
-    ```
-    $ goreman run restart etcd2
-    ```
-
-7. Get the key from the restarted member:
-
-    ```
-    $ etcdctl --endpoints=localhost:22379 get key
-    hello
-    ```
-
-    Restarting the member re-establish the connection. `etcdctl` will now be able to retrieve the key successfully. To learn more about interacting with etcd, read [interacting with etcd section][interacting].
-
-[interacting]: ./interacting_v3.md
-[clustering]: ../op-guide/clustering.md

Documentation/dev-internal/discovery_protocol.md

@@ -1,115 +0,0 @@
----
-title: Discovery service protocol
----
-
-Discovery service protocol helps new etcd member to discover all other members in cluster bootstrap phase using a shared discovery URL.
-
-Discovery service protocol is _only_ used in cluster bootstrap phase, and cannot be used for runtime reconfiguration or cluster monitoring.
-
-The protocol uses a new discovery token to bootstrap one _unique_ 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.
-
-The rest of this article will walk through the discovery process with examples that correspond to a self-hosted discovery cluster. The public discovery service, discovery.etcd.io, functions the same way, but with a layer of polish to abstract away ugly URLs, generate UUIDs automatically, and provide some protections against excessive requests. At its core, the public discovery service still uses an etcd cluster as the data store as described in this document.
-
-## Protocol workflow
-
-The idea of discovery protocol is to use an internal etcd cluster to coordinate bootstrap of a new cluster. First, all new members interact with discovery service and help to generate the expected member list. Then each new member bootstraps its server using this list, which performs the same functionality as -initial-cluster flag.
-
-In the following example workflow, we will list each step of protocol in curl format for ease of understanding.
-
-By convention the etcd discovery protocol uses the key prefix `_etcd/registry`. If `http://example.com` hosts an etcd cluster for discovery service, a full URL to discovery keyspace will be `http://example.com/v2/keys/_etcd/registry`. We will use this as the URL prefix in the example.
-
-### Creating a new discovery token
-
-Generate a unique token that will identify the new cluster. This will be used as a unique prefix in discovery keyspace in the following steps. An easy way to do this is to use `uuidgen`:
-
-```
-UUID=$(uuidgen)
-```
-
-### Specifying the expected cluster size
-
-The discovery token expects a cluster size that must be specified. The size is used by the discovery service to know when it has found all members that will initially form the cluster.
-
-```
-curl -X PUT http://example.com/v2/keys/_etcd/registry/${UUID}/_config/size -d value=${cluster_size}
-```
-
-Usually the cluster size is 3, 5 or 7. Check [optimal cluster size][cluster-size] for more details.
-
-### Bringing up etcd processes
-
-Given the discovery URL, use it as `-discovery` flag and bring up etcd processes. Every etcd process will follow this next few steps internally if given a `-discovery` flag.
-
-### Registering itself
-
-The first thing for etcd process is to register itself into the discovery URL as a member. This is done by creating member ID as a key in the discovery URL.
-
-```
-curl -X PUT http://example.com/v2/keys/_etcd/registry/${UUID}/${member_id}?prevExist=false -d value="${member_name}=${member_peer_url_1}&${member_name}=${member_peer_url_2}"
-```
-
-### Checking the status
-
-It checks the expected cluster size and registration status in discovery URL, and decides what the next action is.
-
-```
-curl -X GET http://example.com/v2/keys/_etcd/registry/${UUID}/_config/size
-curl -X GET http://example.com/v2/keys/_etcd/registry/${UUID}
-```
-
-If registered members are still not enough, it will wait for left members to appear.
-
-If the number of registered members is bigger than the expected size N, it treats the first N registered members as the member list for the cluster. If the member itself is in the member list, the discovery procedure succeeds and it fetches all peers through the member list. If it is not in the member list, the discovery procedure finishes with the failure that the cluster has been full.
-
-In etcd implementation, the member may check the cluster status even before registering itself. So it could fail quickly if the cluster has been full.
-
-### Waiting for all members
-
-The wait process is described in detail in the [etcd API documentation][api].
-
-```
-curl -X GET http://example.com/v2/keys/_etcd/registry/${UUID}?wait=true&waitIndex=${current_etcd_index}
-```
-
-It keeps waiting until finding all members.
-
-## Public discovery service
-
-CoreOS Inc. hosts a public discovery service at https://discovery.etcd.io/ , which provides some nice features for ease of use.
-
-### Mask key prefix
-
-Public discovery service will redirect `https://discovery.etcd.io/${UUID}` to etcd cluster behind for the key at `/v2/keys/_etcd/registry`. It masks register key prefix for short and readable discovery url.
-
-### Get new token
-
-```
-GET /new
-
-Sent query:
-	size=${cluster_size}
-Possible status codes:
-	200 OK
-	400 Bad Request
-200 Body:
-	generated discovery url
-```
-
-The generation process in the service follows the steps from [Creating a New Discovery Token][new-discovery-token] to [Specifying the Expected Cluster Size][expected-cluster-size].
-
-### Check discovery status
-
-```
-GET /${UUID}
-```
-
-The status for this discovery token, including the machines that have been registered, can be checked by requesting the value of the UUID.
-
-### Open-source repository
-
-The repository is located at https://github.com/coreos/discovery.etcd.io. It could be used to build a custom discovery service.
-
-[api]: ../v2/api.md#waiting-for-a-change
-[cluster-size]: ../v2/admin_guide.md#optimal-cluster-size
-[expected-cluster-size]: #specifying-the-expected-cluster-size
-[new-discovery-token]: #creating-a-new-discovery-token

Documentation/dev-internal/logging.md

@@ -1,31 +0,0 @@
----
-title: Logging conventions
----
-
-etcd uses the [capnslog][capnslog] library for logging application output categorized into *levels*. A log message's level is determined according to these conventions:
-
-* Error: Data has been lost, a request has failed for a bad reason, or a required resource has been lost
-  * Examples:
-    * A failure to allocate disk space for WAL
-
-* Warning: (Hopefully) Temporary conditions that may cause errors, but may work fine. A replica disappearing (that may reconnect) is a warning.
-  * Examples:
-    * Failure to send raft message to a remote peer
-    * Failure to receive heartbeat message within the configured election timeout
-
-* Notice: Normal, but important (uncommon) log information.
-  * Examples:
-    * Add a new node into the cluster
-    * Add a new user into auth subsystem
-
-* Info: Normal, working log information, everything is fine, but helpful notices for auditing or common operations.
-  * Examples:
-    * Startup configuration
-    * Start to do snapshot
-
-* Debug: Everything is still fine, but even common operations may be logged, and less helpful but more quantity of notices.
-  * Examples:
-    * Send a normal message to a remote peer
-    * Write a log entry to disk
-
-[capnslog]: https://github.com/coreos/pkg/tree/master/capnslog

Documentation/dev-internal/release.md

@@ -1,162 +0,0 @@
----
-title: etcd release guide
----
-
-The guide talks about how to release a new version of etcd.
-
-The procedure includes some manual steps for sanity checking, but it can probably be further scripted. Please keep this document up-to-date if making changes to the release process.
-
-## Release management
-
-etcd community members are assigned to manage the release each etcd major/minor version as well as manage patches
-and to each stable release branch. The managers are responsible for communicating the timelines and status of each
-release and for ensuring the stability of the release branch.
-
-| Releases | Manager |
-| -------- | ------- |
-| 3.1 patch (post 3.1.0) | Joe Betz [@jpbetz](https://github.com/jpbetz) |
-| 3.2 patch (post 3.2.0) | Joe Betz [@jpbetz](https://github.com/jpbetz) |
-| 3.3 patch (post 3.3.0) | Gyuho Lee [@gyuho](https://github.com/gyuho) |
-
-## Prepare release
-
-Set desired version as environment variable for following steps. Here is an example to release 2.3.0:
-
-```
-export VERSION=v2.3.0
-export PREV_VERSION=v2.2.5
-```
-
-All releases version numbers follow the format of [semantic versioning 2.0.0](http://semver.org/).
-
-### Major, minor version release, or its pre-release
-
-- Ensure the relevant milestone on GitHub is complete. All referenced issues should be closed, or moved elsewhere.
-- Remove this release from [roadmap](https://github.com/etcd-io/etcd/blob/master/ROADMAP.md), if necessary.
-- Ensure the latest upgrade documentation is available.
-- Bump [hardcoded MinClusterVerion in the repository](https://github.com/etcd-io/etcd/blob/master/version/version.go#L29), if necessary.
-- Add feature capability maps for the new version, if necessary.
-
-### Patch version release
-
-- To request a backport, devlopers submit cherrypick PRs targeting the release branch. The commits should not include merge commits. The commits should be restricted to bug fixes and security patches.
-- The cherrypick PRs should target the appropriate release branch (`base:release-<major>-<minor>`). `hack/patch/cherrypick.sh` may be used to automatically generate cherrypick PRs.
-- The release patch manager reviews the cherrypick PRs. Please discuss carefully what is backported to the patch release. Each patch release should be strictly better than it's predecessor.
-- The release patch manager will cherry-pick these commits starting from the oldest one into stable branch.
-
-## Write release note
-
-- Write introduction for the new release. For example, what major bug we fix, what new features we introduce or what performance improvement we make.
-- Put `[GH XXXX]` at the head of change line to reference Pull Request that introduces the change. Moreover, add a link on it to jump to the Pull Request.
-- Find PRs with `release-note` label and explain them in `NEWS` file, as a straightforward summary of changes for end-users.
-
-## Tag version
-
-- Bump [hardcoded Version in the repository](https://github.com/etcd-io/etcd/blob/master/version/version.go#L30) to the latest version `${VERSION}`.
-- Ensure all tests on CI system are passed.
-- Manually check etcd is buildable in Linux, Darwin and Windows.
-- Manually check upgrade etcd cluster of previous minor version works well.
-- Manually check new features work well.
-- Add a signed tag through `git tag -s ${VERSION}`.
-- Sanity check tag correctness through `git show tags/$VERSION`.
-- Push the tag to GitHub through `git push origin tags/$VERSION`. This assumes `origin` corresponds to "https://github.com/etcd-io/etcd".
-
-## Build release binaries and images
-
-- Ensure `acbuild` is available.
-- Ensure `docker` is available.
-
-Run release script in root directory:
-
-```
-TAG=gcr.io/etcd-development/etcd ./scripts/release.sh ${VERSION}
-```
-
-It generates all release binaries and images under directory ./release.
-
-## Sign binaries, images, and source code
-
-etcd project key must be used to sign the generated binaries and images.`$SUBKEYID` is the key ID of etcd project Yubikey. Connect the key and run `gpg2 --card-status` to get the ID.
-
-The following commands are used for public release sign:
-
-```
-cd release
-for i in etcd-*{.zip,.tar.gz}; do gpg2 --default-key $SUBKEYID --armor --output ${i}.asc --detach-sign ${i}; done
-for i in etcd-*{.zip,.tar.gz}; do gpg2 --verify ${i}.asc ${i}; done
-
-# sign zipped source code files
-wget https://github.com/etcd-io/etcd/archive/${VERSION}.zip
-gpg2 --armor --default-key $SUBKEYID --output ${VERSION}.zip.asc --detach-sign ${VERSION}.zip
-gpg2 --verify ${VERSION}.zip.asc ${VERSION}.zip
-
-wget https://github.com/etcd-io/etcd/archive/${VERSION}.tar.gz
-gpg2 --armor --default-key $SUBKEYID --output ${VERSION}.tar.gz.asc --detach-sign ${VERSION}.tar.gz
-gpg2 --verify ${VERSION}.tar.gz.asc ${VERSION}.tar.gz
-```
-
-The public key for GPG signing can be found at [CoreOS Application Signing Key](https://coreos.com/security/app-signing-key)
-
-
-## Publish release page in GitHub
-
-- Set release title as the version name.
-- Follow the format of previous release pages.
-- Attach the generated binaries and signatures.
-- Select whether it is a pre-release.
-- Publish the release!
-
-## Publish docker image in gcr.io
-
-- Push docker image:
-
-```
-gcloud docker -- login -u _json_key -p "$(cat /etc/gcp-key-etcd.json)" https://gcr.io
-
-for TARGET_ARCH in "-arm64" "-ppc64le" ""; do
-  gcloud docker -- push gcr.io/etcd-development/etcd:${VERSION}${TARGET_ARCH}
-done
-```
-
-- Add `latest` tag to the new image on [gcr.io](https://console.cloud.google.com/gcr/images/etcd-development/GLOBAL/etcd?project=etcd-development&authuser=1) if this is a stable release.
-
-## Publish docker image in Quay.io
-
-- Build docker images with quay.io:
-
-```
-for TARGET_ARCH in "amd64" "arm64" "ppc64le"; do
-  TAG=quay.io/coreos/etcd GOARCH=${TARGET_ARCH} \
-    BINARYDIR=release/etcd-${VERSION}-linux-${TARGET_ARCH} \
-    BUILDDIR=release \
-    ./scripts/build-docker ${VERSION}
-done
-```
-
-- Push docker image:
-
-```
-docker login quay.io
-
-for TARGET_ARCH in "-arm64" "-ppc64le" ""; do
-  docker push quay.io/coreos/etcd:${VERSION}${TARGET_ARCH}
-done
-```
-
-- Add `latest` tag to the new image on [quay.io](https://quay.io/repository/coreos/etcd?tag=latest&tab=tags) if this is a stable release.
-
-## Announce to the etcd-dev Googlegroup
-
-- Follow the format of [previous release emails](https://groups.google.com/forum/#!forum/etcd-dev).
-- Make sure to include a list of authors that contributed since the previous release - something like the following might be handy:
-
-```
-git log ...${PREV_VERSION} --pretty=format:"%an" | sort | uniq | tr '\n' ',' | sed -e 's#,#, #g' -e 's#, $##'
-```
-
-- Send email to etcd-dev@googlegroups.com
-
-## Post release
-
-- Create new stable branch through `git push origin ${VERSION_MAJOR}.${VERSION_MINOR}` if this is a major stable release. This assumes `origin` corresponds to "https://github.com/etcd-io/etcd".
-- Bump [hardcoded Version in the repository](https://github.com/etcd-io/etcd/blob/master/version/version.go#L30) to the version `${VERSION}+git`.

Documentation/dl_build.md

@@ -1,69 +0,0 @@
----
-title: Download and build
----
-
-## System requirements
-
-The etcd performance benchmarks run etcd on 8 vCPU, 16GB RAM, 50GB SSD GCE instances, but any relatively modern machine with low latency storage and a few gigabytes of memory should suffice for most use cases. Applications with large v2 data stores will require more memory than a large v3 data store since data is kept in anonymous memory instead of memory mapped from a file. For running etcd on a cloud provider, see the [Example hardware configuration][example-hardware-configurations] documentation.
-
-## Download the pre-built binary
-
-The easiest way to get etcd is to use one of the pre-built release binaries which are available for OSX, Linux, Windows, appc, and Docker. Instructions for using these binaries are on the [GitHub releases page][github-release].
-
-## Build the latest version
-
-For those wanting to try the very latest version, build etcd from the `master` branch. [Go](https://golang.org/) version 1.9+ is required to build the latest version of etcd. To ensure etcd is built against well-tested libraries, etcd vendors its dependencies for official release binaries. However, etcd's vendoring is also optional to avoid potential import conflicts when embedding the etcd server or using the etcd client.
-
-To build `etcd` from the `master` branch without a `GOPATH` using the official `build` script:
-
-```sh
-$ git clone https://github.com/etcd-io/etcd.git
-$ cd etcd
-$ ./build
-```
-
-To build a vendored `etcd` from the `master` branch via `go get`:
-
-```sh
-# GOPATH should be set
-$ echo $GOPATH
-/Users/example/go
-$ go get -v go.etcd.io/etcd
-$ go get -v go.etcd.io/etcd/etcdctl
-```
-
-## Test the installation
-
-Check the etcd binary is built correctly by starting etcd and setting a key.
-
-### Starting etcd
-
-If etcd is built without using `go get`, run the following:
-
-```sh
-$ ./bin/etcd
-```
-If etcd is built using `go get`, run the following:
-
-```sh
-$ $GOPATH/bin/etcd
-```
-
-### Setting a key
-
-Run the following:
-
-```sh
-$ ./bin/etcdctl put foo bar
-OK
-```
-
-(or `$GOPATH/bin/etcdctl put foo bar` if etcdctl was installed with `go get`)
-
-If OK is printed, then etcd is working!
-
-[github-release]: https://github.com/etcd-io/etcd/releases/
-[go]: https://golang.org/doc/install
-[build-script]: ../build
-[cmd-directory]: ../cmd
-[example-hardware-configurations]: op-guide/hardware.md#example-hardware-configurations

Documentation/docs.md

@@ -1,118 +0,0 @@
-# Documentation
-
-etcd is a distributed key-value store designed to reliably and quickly preserve and provide access to critical data. It enables reliable distributed coordination through distributed locking, leader elections, and write barriers. An etcd cluster is intended for high availability and permanent data storage and retrieval.
-
-## Getting started
-
-New etcd users and developers should get started by [downloading and building][download_build] etcd. After getting etcd, follow this [quick demo][demo] to see the basics of creating and working with an etcd cluster.
-
-## Developing with etcd
-
-The easiest way to get started using etcd as a distributed key-value store is to [set up a local cluster][local_cluster].
-
- - [Setting up local clusters][local_cluster]
- - [Interacting with etcd][interacting]
- - gRPC [etcd core][api_ref] and [etcd concurrency][api_concurrency_ref] API references
- - [HTTP JSON API through the gRPC gateway][api_grpc_gateway]
- - [gRPC naming and discovery][grpc_naming]
- - [Client][namespace_client] and [proxy][namespace_proxy] namespacing
- - [Embedding etcd][embed_etcd]
- - [Experimental features and APIs][experimental]
- - [System limits][system-limit]
-
-## Operating etcd clusters
-
-Administrators who need a fault-tolerant etcd cluster for either development or production should begin with a [cluster on multiple machines][clustering].
-
-### Setting up etcd
-
- - [Configuration flags][conf]
- - [Multi-member cluster][clustering]
- - [gRPC proxy][grpc_proxy]
- - [L4 gateway][gateway]
-
-### System configuration
-
- - [Supported systems][supported_platforms]
- - [Hardware recommendations][hardware]
- - [Performance benchmarking][performance]
- - [Tuning][tuning]
-
-### Platform guides
-
- - [Amazon Web Services][aws_platform]
- - [Container Linux, systemd][container_linux_platform]
- - [FreeBSD][freebsd_platform]
- - [Docker container][container_docker]
- - [rkt container][container_rkt]
-
-### Security
-
- - [TLS][security]
- - [Role-based access control][authentication]
-
-### Maintenance and troubleshooting
-
- - [Frequently asked questions][faq]
- - [Monitoring][monitoring]
- - [Maintenance][maintenance]
- - [Failure modes][failures]
- - [Disaster recovery][recovery]
- - [Upgrading][upgrading]
-
-## Learning
-
-To learn more about the concepts and internals behind etcd, read the following pages:
-
- - [Why etcd?][why]
- - [Understand data model][data_model]
- - [Understand APIs][understand_apis]
- - [Glossary][glossary]
- - Design
-   - [Auth subsystem][design-auth-v3]
-   - [Client][design-client]
-   - [Learner][design-learner]
-
-[api_ref]: dev-guide/api_reference_v3.md
-[api_concurrency_ref]: dev-guide/api_concurrency_reference_v3.md
-[api_grpc_gateway]: dev-guide/api_grpc_gateway.md
-[clustering]: op-guide/clustering.md
-[conf]: op-guide/configuration.md
-[system-limit]: dev-guide/limit.md
-[faq]: faq.md
-[why]: learning/why.md
-[data_model]: learning/data_model.md
-[demo]: demo.md
-[download_build]: dl_build.md
-[embed_etcd]: https://godoc.org/github.com/etcd-io/etcd/embed
-[grpc_naming]: dev-guide/grpc_naming.md
-[failures]: op-guide/failures.md
-[gateway]: op-guide/gateway.md
-[glossary]: learning/glossary.md
-[namespace_client]: https://godoc.org/github.com/etcd-io/etcd/clientv3/namespace
-[namespace_proxy]: op-guide/grpc_proxy.md#namespacing
-[grpc_proxy]: op-guide/grpc_proxy.md
-[hardware]: op-guide/hardware.md
-[interacting]: dev-guide/interacting_v3.md
-[local_cluster]: dev-guide/local_cluster.md
-[performance]: op-guide/performance.md
-[recovery]: op-guide/recovery.md
-[maintenance]: op-guide/maintenance.md
-[security]: op-guide/security.md
-[monitoring]: op-guide/monitoring.md
-[v2_migration]: op-guide/v2-migration.md
-[container_rkt]: op-guide/container.md#rkt
-[container_docker]: op-guide/container.md#docker
-[understand_apis]: learning/api.md
-[versioning]: op-guide/versioning.md
-[supported_platforms]: op-guide/supported-platform.md
-[container_linux_platform]: platforms/container-linux-systemd.md
-[freebsd_platform]: platforms/freebsd.md
-[aws_platform]: platforms/aws.md
-[experimental]: dev-guide/experimental_apis.md
-[authentication]: op-guide/authentication.md
-[design-auth-v3]: learning/design-auth-v3.md
-[design-client]: learning/design-client.md
-[design-learner]: learning/design-learner.md
-[tuning]: tuning.md
-[upgrading]: upgrades/upgrading-etcd.md

Documentation/etcd-mixin/test.yaml

@@ -1,85 +0,0 @@
-rule_files:
-  - mixin.yaml
-
-evaluation_interval: 1m
-
-tests:
-  - interval: 1m
-    input_series:
-      - series: 'up{job="etcd",instance="10.10.10.0"}'
-        values: '1 1 1 1 1 1 1 1 1 1 1 1 0 0 0 0'
-      - series: 'up{job="etcd",instance="10.10.10.1"}'
-        values: '1 1 1 1 1 1 1 1 0 0 0 0 0 0 0 0'
-      - series: 'up{job="etcd",instance="10.10.10.2"}'
-        values: '1 1 1 1 0 0 0 0 0 0 0 0 0 0 0 0'
-    alert_rule_test:
-      - eval_time: 3m
-        alertname: etcdInsufficientMembers
-      - eval_time: 5m
-        alertname: etcdInsufficientMembers
-      - eval_time: 5m
-        alertname: etcdMembersDown
-      - eval_time: 7m
-        alertname: etcdMembersDown
-        exp_alerts:
-          - exp_labels:
-              job: etcd
-              severity: critical
-            exp_annotations:
-              message: 'etcd cluster "etcd": members are down (1).'
-      - eval_time: 7m
-        alertname: etcdInsufficientMembers
-      - eval_time: 11m
-        alertname: etcdInsufficientMembers
-        exp_alerts:
-          - exp_labels:
-              job: etcd
-              severity: critical
-            exp_annotations:
-              message: 'etcd cluster "etcd": insufficient members (1).'
-      - eval_time: 15m
-        alertname: etcdInsufficientMembers
-        exp_alerts:
-          - exp_labels:
-              job: etcd
-              severity: critical
-            exp_annotations:
-              message: 'etcd cluster "etcd": insufficient members (0).'
-
-  - interval: 1m
-    input_series:
-      - series: 'up{job="etcd",instance="10.10.10.0"}'
-        values: '1 1 1 1 1 1 1 1 1 1 1 1 0 0 0 0'
-      - series: 'up{job="etcd",instance="10.10.10.1"}'
-        values: '1 1 1 1 1 1 1 1 0 0 0 0 0 0 0 0'
-      - series: 'up{job="etcd",instance="10.10.10.2"}'
-        values: '1 1 1 1 0 0 0 0'
-    alert_rule_test:
-      - eval_time: 10m
-        alertname: etcdMembersDown
-        exp_alerts:
-          - exp_labels:
-              job: etcd
-              severity: critical
-            exp_annotations:
-              message: 'etcd cluster "etcd": members are down (2).'
-
-  - interval: 1m
-    input_series:
-      - series: 'up{job="etcd",instance="10.10.10.0"}'
-        values: '1 1 1 1 1 1 1 1 1 1 1 1 0 0 0 0'
-      - series: 'up{job="etcd",instance="10.10.10.1"}'
-        values: '1 1 1 1 1 1 1 1 0 0 0 0 0 0 0 0'
-      - series: 'etcd_network_peer_sent_failures_total{To="member-1",job="etcd",endpoint="test"}'
-        values: '0 0 1 2 3 4 5 6 7 8 9 10'
-    alert_rule_test:
-      - eval_time: 4m
-        alertname: etcdMembersDown
-      - eval_time: 6m
-        alertname: etcdMembersDown
-        exp_alerts:
-          - exp_labels:
-              job: etcd
-              severity: critical
-            exp_annotations:
-              message: 'etcd cluster "etcd": members are down (1).'

Documentation/faq.md

@@ -1,165 +0,0 @@
----
-title: Frequently Asked Questions (FAQ)
----
-
-## etcd, general
-
-### Do clients have to send requests to the etcd leader?
-
-[Raft][raft] is leader-based; the leader handles all client requests which need cluster consensus. However, the client does not need to know which node is the leader. Any request that requires consensus sent to a follower is automatically forwarded to the leader. Requests that do not require consensus (e.g., serialized reads) can be processed by any cluster member.
-
-## Configuration
-
-### What is the difference between listen-<client,peer>-urls, advertise-client-urls or initial-advertise-peer-urls?
-
-`listen-client-urls` and `listen-peer-urls` specify the local addresses etcd server binds to for accepting incoming connections. To listen on a port for all interfaces, specify `0.0.0.0` as the listen IP address.
-
-`advertise-client-urls` and `initial-advertise-peer-urls` specify the addresses etcd clients or other etcd members should use to contact the etcd server. The advertise addresses must be reachable from the remote machines. Do not advertise addresses like `localhost` or `0.0.0.0` for a production setup since these addresses are unreachable from remote machines.
-
-### Why doesn't changing `--listen-peer-urls` or `--initial-advertise-peer-urls` update the advertised peer URLs in `etcdctl member list`?
-
-A member's advertised peer URLs come from `--initial-advertise-peer-urls` on initial cluster boot. Changing the listen peer URLs or the initial advertise peers after booting the member won't affect the exported advertise peer URLs since changes must go through quorum to avoid membership configuration split brain. Use `etcdctl member update` to update a member's peer URLs.
-
-## Deployment
-
-### System requirements
-
-Since etcd writes data to disk, its performance strongly depends on disk performance. For this reason, SSD is highly recommended. To assess whether a disk is fast enough for etcd, one possibility is using a disk benchmarking tool such as [fio][fio]. For an example on how to do that, read [here][fio-blog-post]. To prevent performance degradation or unintentionally overloading the key-value store, etcd enforces a configurable storage size quota set to 2GB by default. To avoid swapping or running out of memory, the machine should have at least as much RAM to cover the quota. 8GB is a suggested maximum size for normal environments and etcd warns at startup if the configured value exceeds it. At CoreOS, an etcd cluster is usually deployed on dedicated CoreOS Container Linux machines with dual-core processors, 2GB of RAM, and 80GB of SSD *at the very least*. **Note that performance is intrinsically workload dependent; please test before production deployment**. See [hardware][hardware-setup] for more recommendations.
-
-Most stable production environment is Linux operating system with amd64 architecture; see [supported platform][supported-platform] for more.
-
-### Why an odd number of cluster members?
-
-An etcd cluster needs a majority of nodes, a quorum, to agree on updates to the cluster state. For a cluster with n members, quorum is (n/2)+1. For any odd-sized cluster, adding one node will always increase the number of nodes necessary for quorum. Although adding a node to an odd-sized cluster appears better since there are more machines, the fault tolerance is worse since exactly the same number of nodes may fail without losing quorum but there are more nodes that can fail. If the cluster is in a state where it can't tolerate any more failures, adding a node before removing nodes is dangerous because if the new node fails to register with the cluster (e.g., the address is misconfigured), quorum will be permanently lost.
-
-### What is maximum cluster size?
-
-Theoretically, there is no hard limit. However, an etcd cluster probably should have no more than seven nodes. [Google Chubby lock service][chubby], similar to etcd and widely deployed within Google for many years, suggests running five nodes. A 5-member etcd cluster can tolerate two member failures, which is enough in most cases. Although larger clusters provide better fault tolerance, the write performance suffers because data must be replicated across more machines.
-
-### What is failure tolerance?
-
-An etcd cluster operates so long as a member quorum can be established. If quorum is lost through transient network failures (e.g., partitions), etcd automatically and safely resumes once the network recovers and restores quorum; Raft enforces cluster consistency. For power loss, etcd persists the Raft log to disk; etcd replays the log to the point of failure and resumes cluster participation. For permanent hardware failure, the node may be removed from the cluster through [runtime reconfiguration][runtime reconfiguration].
-
-It is recommended to have an odd number of members in a cluster. An odd-size cluster tolerates the same number of failures as an even-size cluster but with fewer nodes. The difference can be seen by comparing even and odd sized clusters:
-
-| Cluster Size | Majority | Failure Tolerance |
-|:-:|:-:|:-:|
-| 1 | 1 | 0 |
-| 2 | 2 | 0 |
-| 3 | 2 | 1 |
-| 4 | 3 | 1 |
-| 5 | 3 | 2 |
-| 6 | 4 | 2 |
-| 7 | 4 | 3 |
-| 8 | 5 | 3 |
-| 9 | 5 | 4 |
-
-Adding a member to bring the size of cluster up to an even number doesn't buy additional fault tolerance. Likewise, during a network partition, an odd number of members guarantees that there will always be a majority partition that can continue to operate and be the source of truth when the partition ends.
-
-### Does etcd work in cross-region or cross data center deployments?
-
-Deploying etcd across regions improves etcd's fault tolerance since members are in separate failure domains. The cost is higher consensus request latency from crossing data center boundaries. Since etcd relies on a member quorum for consensus, the latency from crossing data centers will be somewhat pronounced because at least a majority of cluster members must respond to consensus requests. Additionally, cluster data must be replicated across all peers, so there will be bandwidth cost as well.
-
-With longer latencies, the default etcd configuration may cause frequent elections or heartbeat timeouts. See [tuning] for adjusting timeouts for high latency deployments.
-
-## Operation
-
-### How to backup a etcd cluster?
-
-etcdctl provides a `snapshot` command to create backups. See [backup][backup] for more details.
-
-### Should I add a member before removing an unhealthy member?
-
-When replacing an etcd node, it's important  to remove the member first and then add its replacement.
-
-etcd employs distributed consensus based on a quorum model; (n+1)/2 members, a majority, must agree on a proposal before it can be committed to the cluster. These proposals include key-value updates and membership changes. This model totally avoids any possibility of split brain inconsistency. The downside is permanent quorum loss is catastrophic.
-
-How this applies to membership: If a 3-member cluster has 1 downed member, it can still make forward progress because the quorum is 2 and 2 members are still live. However, adding a new member to a 3-member cluster will increase the quorum to 3 because 3 votes are required for a majority of 4 members. Since the quorum increased, this extra member buys nothing in terms of fault tolerance; the cluster is still one node failure away from being unrecoverable.
-
-Additionally, that new member is risky because it may turn out to be misconfigured or incapable of joining the cluster. In that case, there's no way to recover quorum because the cluster has two members down and two members up, but needs three votes to change membership to undo the botched membership addition. etcd will by default reject member add attempts that could take down the cluster in this manner.
-
-On the other hand, if the downed member is removed from cluster membership first, the number of members becomes 2 and the quorum remains at 2. Following that removal by adding a new member will also keep the quorum steady at 2. So, even if the new node can't be brought up, it's still possible to remove the new member through quorum on the remaining live members.
-
-### Why won't etcd accept my membership changes?
-
-etcd sets `strict-reconfig-check` in order to reject reconfiguration requests that would cause quorum loss. Abandoning quorum is really risky (especially when the cluster is already unhealthy). Although it may be tempting to disable quorum checking if there's quorum loss to add a new member, this could lead to full fledged cluster inconsistency. For many applications, this will make the problem even worse ("disk geometry corruption" being a candidate for most terrifying).
-
-### Why does etcd lose its leader from disk latency spikes?
-
-This is intentional; disk latency is part of leader liveness. Suppose the cluster leader takes a minute to fsync a raft log update to disk, but the etcd cluster has a one second election timeout. Even though the leader can process network messages within the election interval (e.g., send heartbeats), it's effectively unavailable because it can't commit any new proposals; it's waiting on the slow disk. If the cluster frequently loses its leader due to disk latencies, try [tuning][tuning] the disk settings or etcd time parameters.
-
-### What does the etcd warning "request ignored (cluster ID mismatch)" mean?
-
-Every new etcd cluster generates a new cluster ID based on the initial cluster configuration and a user-provided unique `initial-cluster-token` value. By having unique cluster ID's, etcd is protected from cross-cluster interaction which could corrupt the cluster.
-
-Usually this warning happens after tearing down an old cluster, then reusing some of the peer addresses for the new cluster. If any etcd process from the old cluster is still running it will try to contact the new cluster. The new cluster will recognize a cluster ID mismatch, then ignore the request and emit this warning. This warning is often cleared by ensuring peer addresses among distinct clusters are disjoint.
-
-### What does "mvcc: database space exceeded" mean and how do I fix it?
-
-The [multi-version concurrency control][api-mvcc] data model in etcd keeps an exact history of the keyspace. Without periodically compacting this history (e.g., by setting `--auto-compaction`), etcd will eventually exhaust its storage space. If etcd runs low on storage space, it raises a space quota alarm to protect the cluster from further writes. So long as the alarm is raised, etcd responds to write requests with the error `mvcc: database space exceeded`.
-
-To recover from the low space quota alarm:
-
-1. [Compact][maintenance-compact] etcd's history.
-2. [Defragment][maintenance-defragment] every etcd endpoint.
-3. [Disarm][maintenance-disarm] the alarm.
-
-### What does the etcd warning "etcdserver/api/v3rpc: transport: http2Server.HandleStreams failed to read frame: read tcp 127.0.0.1:2379->127.0.0.1:43020: read: connection reset by peer" mean?
-
-This is gRPC-side warning when a server receives a TCP RST flag with client-side streams being prematurely closed. For example, a client closes its connection, while gRPC server has not yet processed all HTTP/2 frames in the TCP queue. Some data may have been lost in server side, but it is ok so long as client connection has already been closed.
-
-Only [old versions of gRPC](https://github.com/grpc/grpc-go/issues/1362) log this. etcd [>=v3.2.13 by default log this with DEBUG level](https://github.com/etcd-io/etcd/pull/9080), thus only visible with `--debug` flag enabled.
-
-## Performance
-
-### How should I benchmark etcd?
-
-Try the [benchmark] tool. Current [benchmark results][benchmark-result] are available for comparison.
-
-### What does the etcd warning "apply entries took too long" mean?
-
-After a majority of etcd members agree to commit a request, each etcd server applies the request to its data store and persists the result to disk. Even with a slow mechanical disk or a virtualized network disk, such as Amazon’s EBS or Google’s PD, applying a request should normally take fewer than 50 milliseconds. If the average apply duration exceeds 100 milliseconds, etcd will warn that entries are taking too long to apply.
-
-Usually this issue is caused by a slow disk. The disk could be experiencing contention among etcd and other applications, or the disk is too simply slow (e.g., a shared virtualized disk). To rule out a slow disk from causing this warning, monitor  [backend_commit_duration_seconds][backend_commit_metrics] (p99 duration should be less than 25ms) to confirm the disk is reasonably fast. If the disk is too slow, assigning a dedicated disk to etcd or using faster disk will typically solve the problem.
-
-The second most common cause is CPU starvation. If monitoring of the machine’s CPU usage shows heavy utilization, there may not be enough compute capacity for etcd. Moving etcd to dedicated machine, increasing process resource isolation  cgroups, or renicing the etcd server process into a higher priority can usually solve the problem.
-
-Expensive user requests which access too many keys (e.g., fetching the entire keyspace) can also cause long apply latencies. Accessing fewer than a several hundred keys per request, however, should always be performant.
-
-If none of the above suggestions clear the warnings, please [open an issue][new_issue] with detailed logging, monitoring, metrics and optionally workload information.
-
-### What does the etcd warning "failed to send out heartbeat on time" mean?
-
-etcd uses a leader-based consensus protocol for consistent data replication and log execution. Cluster members elect a single leader, all other members become followers. The elected leader must periodically send heartbeats to its followers to maintain its leadership. Followers infer leader failure if no heartbeats are received within an election interval and trigger an election. If a leader doesn’t send its heartbeats in time but is still running, the election is spurious and likely caused by insufficient resources. To catch these soft failures, if the leader skips two heartbeat intervals, etcd will warn it failed to send a heartbeat on time.
-
-Usually this issue is caused by a slow disk. Before the leader sends heartbeats attached with metadata, it may need to persist the metadata to disk. The disk could be experiencing contention among etcd and other applications, or the disk is too simply slow (e.g., a shared virtualized disk). To rule out a slow disk from causing this warning, monitor  [wal_fsync_duration_seconds][wal_fsync_duration_seconds] (p99 duration should be less than 10ms) to confirm the disk is reasonably fast. If the disk is too slow, assigning a dedicated disk to etcd or using faster disk will typically solve the problem. To tell whether a disk is fast enough for etcd, a benchmarking tool such as [fio][fio] can be used. Read [here][fio-blog-post] for an example.
-
-The second most common cause is CPU starvation. If monitoring of the machine’s CPU usage shows heavy utilization, there may not be enough compute capacity for etcd. Moving etcd to dedicated machine, increasing process resource isolation  with cgroups, or renicing the etcd server process into a higher priority can usually solve the problem.
-
-A slow network can also cause this issue. If network metrics among the etcd machines shows long latencies or high drop rate, there may not be enough network capacity for etcd. Moving etcd members to a less congested network will typically solve the problem. However, if the etcd cluster is deployed across data centers, long latency between members is expected. For such deployments, tune the `heartbeat-interval` configuration to roughly match the round trip time between the machines, and the `election-timeout` configuration to be at least 5 * `heartbeat-interval`. See [tuning documentation][tuning] for detailed information.
-
-If none of the above suggestions clear the warnings, please [open an issue][new_issue] with detailed logging, monitoring, metrics and optionally workload information.
-
-### What does the etcd warning "snapshotting is taking more than x seconds to finish ..." mean?
-
-etcd sends a snapshot of its complete key-value store to refresh slow followers and for [backups][backup]. Slow snapshot transfer times increase MTTR; if the cluster is ingesting data with high throughput, slow followers may livelock by needing a new snapshot before finishing receiving a snapshot. To catch slow snapshot performance, etcd warns when sending a snapshot takes more than thirty seconds and exceeds the expected transfer time for a 1Gbps connection.
-
-
-[hardware-setup]: ./op-guide/hardware.md
-[supported-platform]: ./op-guide/supported-platform.md
-[wal_fsync_duration_seconds]: ./metrics.md#disk
-[tuning]: ./tuning.md
-[new_issue]: https://github.com/etcd-io/etcd/issues/new
-[backend_commit_metrics]: ./metrics.md#disk
-[raft]: https://raft.github.io/raft.pdf
-[backup]: https://github.com/etcd-io/etcd/blob/master/Documentation/op-guide/recovery.md#snapshotting-the-keyspace
-[chubby]: http://static.googleusercontent.com/media/research.google.com/en//archive/chubby-osdi06.pdf
-[runtime reconfiguration]: https://github.com/etcd-io/etcd/blob/master/Documentation/op-guide/runtime-configuration.md
-[benchmark]: https://github.com/coreos/etcd/tree/master/tools/benchmark
-[benchmark-result]: https://github.com/etcd-io/etcd/blob/master/Documentation/op-guide/performance.md
-[api-mvcc]: learning/api.md#revisions
-[maintenance-compact]:  op-guide/maintenance.md#history-compaction
-[maintenance-defragment]: op-guide/maintenance.md#defragmentation
-[maintenance-disarm]: ../etcdctl/README.md#alarm-disarm
-[fio]: https://github.com/axboe/fio
-[fio-blog-post]: https://www.ibm.com/blogs/bluemix/2019/04/using-fio-to-tell-whether-your-storage-is-fast-enough-for-etcd/

Documentation/integrations.md

@@ -1,179 +0,0 @@
----
-title: Libraries and tools
----
-
-**Tools**
-
-- [etcdctl](https://github.com/etcd-io/etcd/tree/master/etcdctl) - A command line client for etcd
-- [etcd-backup](https://github.com/fanhattan/etcd-backup) - A powerful command line utility for dumping/restoring etcd - Supports v2
-- [etcd-dump](https://npmjs.org/package/etcd-dump) - Command line utility for dumping/restoring etcd.
-- [etcd-fs](https://github.com/xetorthio/etcd-fs) - FUSE filesystem for etcd
-- [etcddir](https://github.com/rekby/etcddir) - Realtime sync etcd and local directory. Work with windows and linux.
-- [etcd-browser](https://github.com/henszey/etcd-browser) - A web-based key/value editor for etcd using AngularJS
-- [etcd-lock](https://github.com/datawisesystems/etcd-lock) - Master election & distributed r/w lock implementation using etcd - Supports v2
-- [etcd-console](https://github.com/matishsiao/etcd-console) - A web-base key/value editor for etcd using PHP
-- [etcd-viewer](https://github.com/nikfoundas/etcd-viewer) - An etcd key-value store editor/viewer written in Java
-- [etcdtool](https://github.com/mickep76/etcdtool) - Export/Import/Edit etcd directory as JSON/YAML/TOML and Validate directory using JSON schema
-- [etcd-rest](https://github.com/mickep76/etcd-rest) - Create generic REST API in Go using etcd as a backend with validation using JSON schema
-- [etcdsh](https://github.com/kamilhark/etcdsh) - A command line client with support of command history and tab completion. Supports v2
-- [etcdloadtest](https://github.com/sinsharat/etcdloadtest) - A command line load test client for etcd version 3.0 and above.
-- [lucas](https://github.com/ringtail/lucas) - A web-based key-value viewer for kubernetes etcd3.0+ cluster.
-
-**Go libraries**
-
-- [etcd/clientv3](https://github.com/etcd-io/etcd/blob/master/clientv3) - the officially maintained Go client for v3
-- [etcd/client](https://github.com/etcd-io/etcd/blob/master/client) - the officially maintained Go client for v2
-- [go-etcd](https://github.com/coreos/go-etcd) - the deprecated official client. May be useful for older (<2.0.0) versions of etcd.
-- [encWrapper](https://github.com/lumjjb/etcd/tree/enc_wrapper/clientwrap/encwrapper) - encWrapper is an encryption wrapper for the etcd client Keys API/KV.
-
-**Java libraries**
-
-- [coreos/jetcd](https://github.com/etcd-io/jetcd) - Supports v3
-- [boonproject/etcd](https://github.com/boonproject/boon/blob/master/etcd/README.md) - Supports v2, Async/Sync and waits
-- [justinsb/jetcd](https://github.com/justinsb/jetcd)
-- [diwakergupta/jetcd](https://github.com/diwakergupta/jetcd) - Supports v2
-- [jurmous/etcd4j](https://github.com/jurmous/etcd4j) - Supports v2, Async/Sync, waits and SSL
-- [AdoHe/etcd4j](http://github.com/AdoHe/etcd4j) - Supports v2 (enhance for real production cluster)
-- [cdancy/etcd-rest](https://github.com/cdancy/etcd-rest) - Uses jclouds to provide a complete implementation of v2 API.
-
-**Scala libraries**
-
-- [maciej/etcd-client](https://github.com/maciej/etcd-client) - Supports v2. Akka HTTP-based fully async client
-- [eiipii/etcdhttpclient](https://bitbucket.org/eiipii/etcdhttpclient) - Supports v2. Async HTTP client based on Netty and Scala Futures.
-
-**Perl libraries**
-
-- [hexfusion/perl-net-etcd](https://github.com/hexfusion/perl-net-etcd) - Supports v3 grpc gateway HTTP API
-- [robn/p5-etcd](https://github.com/robn/p5-etcd) - Supports v2
-
-**Python libraries**
-
-- [kragniz/python-etcd3](https://github.com/kragniz/python-etcd3) - Client for v3
-- [jplana/python-etcd](https://github.com/jplana/python-etcd) - Supports v2
-- [russellhaering/txetcd](https://github.com/russellhaering/txetcd) - a Twisted Python library
-- [cholcombe973/autodock](https://github.com/cholcombe973/autodock) - A docker deployment automation tool
-- [lisael/aioetcd](https://github.com/lisael/aioetcd) - (Python 3.4+) Asyncio coroutines client (Supports v2)
-- [txaio-etcd](https://github.com/crossbario/txaio-etcd) - Asynchronous etcd v3-only client library for Twisted (today) and asyncio (future)
-- [dims/etcd3-gateway](https://github.com/dims/etcd3-gateway) - etcd v3 API library using the HTTP grpc gateway
-- [aioetcd3](https://github.com/gaopeiliang/aioetcd3) - (Python 3.6+) etcd v3 API for asyncio
-- [Revolution1/etcd3-py](https://github.com/Revolution1/etcd3-py) - (python2.7 and python3.5+) Python client for etcd v3, using gRPC-JSON-Gateway
-
-**Node libraries**
-
-- [mixer/etcd3](https://github.com/mixer/etcd3) - Supports v3
-- [stianeikeland/node-etcd](https://github.com/stianeikeland/node-etcd) - Supports v2 (w Coffeescript)
-- [lavagetto/nodejs-etcd](https://github.com/lavagetto/nodejs-etcd) - Supports v2
-- [deedubs/node-etcd-config](https://github.com/deedubs/node-etcd-config) - Supports v2
-
-**Ruby libraries**
-
-- [iconara/etcd-rb](https://github.com/iconara/etcd-rb)
-- [jpfuentes2/etcd-ruby](https://github.com/jpfuentes2/etcd-ruby)
-- [ranjib/etcd-ruby](https://github.com/ranjib/etcd-ruby) - Supports v2
-- [davissp14/etcdv3-ruby](https://github.com/davissp14/etcdv3-ruby) - Supports v3
-
-**C libraries**
-
-- [apache/celix/etcdlib](https://github.com/apache/celix/tree/develop/etcdlib) - Supports v2
-- [jdarcy/etcd-api](https://github.com/jdarcy/etcd-api) - Supports v2
-- [shafreeck/cetcd](https://github.com/shafreeck/cetcd) - Supports v2
-
-**C++ libraries**
-- [edwardcapriolo/etcdcpp](https://github.com/edwardcapriolo/etcdcpp) - Supports v2
-- [suryanathan/etcdcpp](https://github.com/suryanathan/etcdcpp) - Supports v2 (with waits)
-- [nokia/etcd-cpp-api](https://github.com/nokia/etcd-cpp-api) - Supports v2
-- [nokia/etcd-cpp-apiv3](https://github.com/nokia/etcd-cpp-apiv3) - Supports v3
-
-**Clojure libraries**
-
-- [aterreno/etcd-clojure](https://github.com/aterreno/etcd-clojure)
-- [dwwoelfel/cetcd](https://github.com/dwwoelfel/cetcd) - Supports v2
-- [rthomas/clj-etcd](https://github.com/rthomas/clj-etcd) - Supports v2
-
-**Erlang libraries**
-
-- [marshall-lee/etcd.erl](https://github.com/marshall-lee/etcd.erl) - Supports v2
-- [zhongwencool/eetcd](https://github.com/zhongwencool/eetcd) - Supports v3+ (GRPC only)
-
-**.Net Libraries**
-
-- [wangjia184/etcdnet](https://github.com/wangjia184/etcdnet) - Supports v2
-- [drusellers/etcetera](https://github.com/drusellers/etcetera)
-- [shubhamranjan/dotnet-etcd](https://github.com/shubhamranjan/dotnet-etcd) - Supports v3+ (GRPC only)
-
-**PHP Libraries**
-
-- [linkorb/etcd-php](https://github.com/linkorb/etcd-php)
-- [activecollab/etcd](https://github.com/activecollab/etcd)
-- [ouqiang/etcd-php](https://github.com/ouqiang/etcd-php) - Client for v3 gRPC gateway
-
-**Haskell libraries**
-
-- [wereHamster/etcd-hs](https://github.com/wereHamster/etcd-hs)
-
-**R libraries**
-
-- [ropensci/etseed](https://github.com/ropensci/etseed)
-
-**Nim libraries**
-
-- [etcd_client](https://github.com/FedericoCeratto/nim-etcd-client)
-
-**Tcl libraries**
-
-- [efrecon/etcd-tcl](https://github.com/efrecon/etcd-tcl) - Supports v2, except wait.
-
-**Rust libraries**
-
-- [jimmycuadra/rust-etcd](https://github.com/jimmycuadra/rust-etcd) - Supports v2
-
-**Gradle Plugins**
-
-- [gradle-etcd-rest-plugin](https://github.com/cdancy/gradle-etcd-rest-plugin) - Supports v2
-
-**Chef Integration**
-
-- [coderanger/etcd-chef](https://github.com/coderanger/etcd-chef)
-
-**Chef Cookbook**
-
-- [spheromak/etcd-cookbook](https://github.com/spheromak/etcd-cookbook)
-
-**BOSH Releases**
-
-- [cloudfoundry-community/etcd-boshrelease](https://github.com/cloudfoundry-community/etcd-boshrelease)
-- [cloudfoundry/cf-release](https://github.com/cloudfoundry/cf-release/tree/master/jobs/etcd)
-
-**Projects using etcd**
-- [etcd Raft users](../raft/README.md#notable-users) - projects using etcd's raft library implementation.
-- [apache/celix](https://github.com/apache/celix) - an implementation of the OSGi specification adapted to C and C++
-- [binocarlos/yoda](https://github.com/binocarlos/yoda) - etcd + ZeroMQ
-- [blox/blox](https://github.com/blox/blox) - a collection of open source projects for container management and orchestration with AWS ECS
-- [calavera/active-proxy](https://github.com/calavera/active-proxy) - HTTP Proxy configured with etcd
-- [chain/chain](https://github.com/chain/chain) - software designed to operate and connect to highly scalable permissioned blockchain networks
-- [derekchiang/etcdplus](https://github.com/derekchiang/etcdplus) - A set of distributed synchronization primitives built upon etcd
-- [go-discover](https://github.com/flynn/go-discover) - service discovery in Go
-- [gleicon/goreman](https://github.com/gleicon/goreman/tree/etcd) - Branch of the Go Foreman clone with etcd support
-- [garethr/hiera-etcd](https://github.com/garethr/hiera-etcd) - Puppet hiera backend using etcd
-- [mattn/etcd-vim](https://github.com/mattn/etcd-vim) - SET and GET keys from inside vim
-- [mattn/etcdenv](https://github.com/mattn/etcdenv) - "env" shebang with etcd integration
-- [kelseyhightower/confd](https://github.com/kelseyhightower/confd) - Manage local app config files using templates and data from etcd
-- [configdb](https://git.autistici.org/ai/configdb/tree/master) - A REST relational abstraction on top of arbitrary database backends, aimed at storing configs and inventories.
-- [kubernetes/kubernetes](https://github.com/kubernetes/kubernetes) - Container cluster manager introduced by Google.
-- [mailgun/vulcand](https://github.com/mailgun/vulcand) - HTTP proxy that uses etcd as a configuration backend.
-- [duedil-ltd/discodns](https://github.com/duedil-ltd/discodns) - Simple DNS nameserver using etcd as a database for names and records.
-- [skynetservices/skydns](https://github.com/skynetservices/skydns) - RFC compliant DNS server
-- [xordataexchange/crypt](https://github.com/xordataexchange/crypt) - Securely store values in etcd using GPG encryption
-- [spf13/viper](https://github.com/spf13/viper) - Go configuration library, reads values from ENV, pflags, files, and etcd with optional encryption
-- [lytics/metafora](https://github.com/lytics/metafora) - Go distributed task library
-- [ryandoyle/nss-etcd](https://github.com/ryandoyle/nss-etcd) - A GNU libc NSS module for resolving names from etcd.
-- [Gru](https://github.com/dnaeon/gru) - Orchestration made easy with Go
-- [Vitess](http://vitess.io/) - Vitess is a database clustering system for horizontal scaling of MySQL.
-- [lclarkmichalek/etcdhcp](https://github.com/lclarkmichalek/etcdhcp) - DHCP server that uses etcd for persistence and coordination.
-- [openstack/networking-vpp](https://github.com/openstack/networking-vpp) - A networking driver that programs the [FD.io VPP dataplane](https://wiki.fd.io/view/VPP) to provide [OpenStack](https://www.openstack.org/) cloud virtual networking
-- [OpenStack](https://github.com/openstack/governance/blob/master/reference/base-services.rst) - OpenStack services can rely on etcd as a base service.
-- [CoreDNS](https://github.com/coredns/coredns/tree/master/plugin/etcd) - CoreDNS is a DNS server that chains plugins, part of CNCF and Kubernetes
-- [Uber M3](https://github.com/m3db/m3) - M3: Uber’s Open Source, Large-scale Metrics Platform for Prometheus
-- [Rook](https://github.com/rook/rook) - Storage Orchestration for Kubernetes
-- [Patroni](https://github.com/zalando/patroni) - A template for PostgreSQL High Availability with ZooKeeper, etcd, or Consul
-- [Trillian](https://github.com/google/trillian) - Trillian implements a Merkle tree whose contents are served from a data storage layer, to allow scalability to extremely large trees.

Documentation/learning/api.md

@@ -1,483 +0,0 @@
----
-title: etcd3 API
----
-
-This document is meant to give an overview of the etcd3 API's central design. It is by no means all encompassing, but intended to focus on the basic ideas needed to understand etcd without the distraction of less common API calls. All etcd3 API's are defined in [gRPC services][grpc-service], which categorize remote procedure calls (RPCs) understood by the etcd server. A full listing of all etcd RPCs are documented in markdown in the [gRPC API listing][grpc-api].
-
-## gRPC Services
-
-Every API request sent to an etcd server is a gRPC remote procedure call. RPCs in etcd3 are categorized based on functionality into services.
-
-Services important for dealing with etcd's key space include:
-* KV - Creates, updates, fetches, and deletes key-value pairs.
-* Watch - Monitors changes to keys.
-* Lease - Primitives for consuming client keep-alive messages.
-
-Services which manage the cluster itself include:
-* Auth - Role based authentication mechanism for authenticating users.
-* Cluster - Provides membership information and configuration facilities.
-* Maintenance - Takes recovery snapshots, defragments the store, and returns per-member status information.
-
-### Requests and Responses
-
-All RPCs in etcd3 follow the same format. Each RPC has a function `Name` which takes `NameRequest` as an argument and returns `NameResponse` as a response. For example, here is the `Range` RPC description:
-
-```protobuf
-service KV {
-  Range(RangeRequest) returns (RangeResponse)
-  ...
-}
-```
-
-### Response header
-
-All Responses from etcd API have an attached response header which includes cluster metadata for the response:
-
-```proto
-message ResponseHeader {
-  uint64 cluster_id = 1;
-  uint64 member_id = 2;
-  int64 revision = 3;
-  uint64 raft_term = 4;
-}
-```
-
-* Cluster_ID - the ID of the cluster generating the response.
-* Member_ID - the ID of the member generating the response.
-* Revision - the revision of the key-value store when generating the response.
-* Raft_Term - the Raft term of the member when generating the response.
-
-An application may read the `Cluster_ID` or `Member_ID` field to ensure it is communicating with the intended cluster (member).
-
-Applications can use the `Revision` field to know the latest revision of the key-value store. This is especially useful when applications specify a historical revision to make a `time travel query` and wish to know the latest revision at the time of the request.
-
-Applications can use `Raft_Term` to detect when the cluster completes a new leader election.
-
-## Key-Value API
-
-The Key-Value API manipulates key-value pairs stored inside etcd. The majority of requests made to etcd are usually key-value requests.
-
-### System primitives
-
-### Key-Value pair
-
-A key-value pair is the smallest unit that the key-value API can manipulate. Each key-value pair has a number of fields, defined in [protobuf format][kv-proto]:
-
-```protobuf
-message KeyValue {
-  bytes key = 1;
-  int64 create_revision = 2;
-  int64 mod_revision = 3;
-  int64 version = 4;
-  bytes value = 5;
-  int64 lease = 6;
-}
-```
-
-* Key - key in bytes. An empty key is not allowed.
-* Value - value in bytes.
-* Version - version is the version of the key. A deletion resets the version to zero and any modification of the key increases its version.
-* Create_Revision - revision of the last creation on the key.
-* Mod_Revision - revision of the last modification on the key.
-* Lease - the ID of the lease attached to the key. If lease is 0, then no lease is attached to the key.
-
-
-In addition to just the key and value, etcd attaches additional revision metadata as part of the key message. This revision information orders keys by time of creation and modification, which is useful for managing concurrency for distributed synchronization. The etcd client's [distributed shared locks][locks] use the creation revision to wait for lock ownership. Similarly, the modification revision is used for detecting [software transactional memory][STM] read set conflicts and waiting on [leader election][elections] updates.
-
-#### Revisions
-
-etcd maintains a 64-bit cluster-wide counter, the store revision, that is incremented each time the key space is modified. The revision serves as a global logical clock, sequentially ordering all updates to the store. The change represented by a new revision is incremental; the data associated with a revision is the data that changed the store. Internally, a new revision means writing the changes to the backend's B+tree, keyed by the incremented revision.
-
-Revisions become more valuable when considering etcd3's [multi-version concurrency control][mvcc] backend. The MVCC model means that the key-value store can be viewed from past revisions since historical key revisions are retained. The retention policy for this history can be configured by cluster administrators for fine-grained storage management; usually etcd3 discards old revisions of keys on a timer. A typical etcd3 cluster retains superseded key data for hours. This also provides reliable handling for long client disconnection, not just transient network disruptions: watchers simply resume from the last observed historical revision. Similarly, to read from the store at a particular point-in-time, read requests can be tagged with a revision to return keys from a view of the key space at the point-in-time that revision was committed.
-
-#### Key ranges
-
-The etcd3 data model indexes all keys over a flat binary key space. This differs from other key-value store systems that use a hierarchical system of organizing keys into directories. Instead of listing keys by directory, keys are listed by key intervals `[a, b)`.
-
-These intervals are often referred to as "ranges" in etcd3. Operations over ranges are more powerful than operations on directories. Like a hierarchical store, intervals support single key lookups via `[a, a+1)` (e.g., ['a', 'a\x00') looks up 'a') and directory lookups by encoding keys by directory depth. In addition to those operations, intervals can also encode prefixes; for example  the interval `['a', 'b')` looks up all keys prefixed by the string 'a'.
-
-By convention, ranges for a request are denoted by the fields `key` and `range_end`. The `key` field is the first key of the range and should be non-empty. The `range_end` is the key following the last key of the range. If `range_end` is not given or empty, the range is defined to contain only the key argument. If `range_end` is `key` plus one (e.g., "aa"+1 == "ab", "a\xff"+1 == "b"), then the range represents all keys prefixed with key. If both `key` and `range_end` are '\0', then range represents all keys. If `range_end` is '\0', the range is all keys greater than or equal to the key argument.
-
-### Range
-
-Keys are fetched from the key-value store using the `Range` API call, which takes a `RangeRequest`:
-
-```protobuf
-message RangeRequest {
-  enum SortOrder {
-	NONE = 0; // default, no sorting
-	ASCEND = 1; // lowest target value first
-	DESCEND = 2; // highest target value first
-  }
-  enum SortTarget {
-	KEY = 0;
-	VERSION = 1;
-	CREATE = 2;
-	MOD = 3;
-	VALUE = 4;
-  }
-
-  bytes key = 1;
-  bytes range_end = 2;
-  int64 limit = 3;
-  int64 revision = 4;
-  SortOrder sort_order = 5;
-  SortTarget sort_target = 6;
-  bool serializable = 7;
-  bool keys_only = 8;
-  bool count_only = 9;
-  int64 min_mod_revision = 10;
-  int64 max_mod_revision = 11;
-  int64 min_create_revision = 12;
-  int64 max_create_revision = 13;
-}
-```
-
-* Key, Range_End - The key range to fetch.
-* Limit - the maximum number of keys returned for the request. When limit is set to 0, it is treated as no limit.
-* Revision - the point-in-time of the key-value store to use for the range. If revision is less or equal to zero, the range is over the latest key-value store. If the revision is compacted, ErrCompacted is returned as a response.
-* Sort_Order - the ordering for sorted requests.
-* Sort_Target - the key-value field to sort.
-* Serializable - sets the range request to use serializable member-local reads. By default, Range is linearizable; it reflects the current consensus of the cluster. For better performance and availability, in exchange for possible stale reads, a serializable range request is served locally without needing to reach consensus with other nodes in the cluster.
-* Keys_Only - return only the keys and not the values.
-* Count_Only - return only the count of the keys in the range.
-* Min_Mod_Revision - the lower bound for key mod revisions; filters out lesser mod revisions.
-* Max_Mod_Revision - the upper bound for key mod revisions; filters out greater mod revisions.
-* Min_Create_Revision - the lower bound for key create revisions; filters out lesser create revisions.
-* Max_Create_Revision - the upper bound for key create revisions; filters out greater create revisions.
-
-The client receives a `RangeResponse` message from the `Range` call:
-
-```protobuf
-message RangeResponse {
-  ResponseHeader header = 1;
-  repeated mvccpb.KeyValue kvs = 2;
-  bool more = 3;
-  int64 count = 4;
-}
-```
-
-* Kvs - the list of key-value pairs matched by the range request. When `Count_Only` is set, `Kvs` is empty.
-* More - indicates if there are more keys to return in the requested range if `limit` is set.
-* Count - the total number of keys satisfying the range request.
-
-### Put
-
-Keys are saved into the key-value store by issuing a `Put` call, which takes a `PutRequest`:
-
-```protobuf
-message PutRequest {
-  bytes key = 1;
-  bytes value = 2;
-  int64 lease = 3;
-  bool prev_kv = 4;
-  bool ignore_value = 5;
-  bool ignore_lease = 6;
-}
-```
-
-* Key - the name of the key to put into the key-value store.
-* Value - the value, in bytes, to associate with the key in the key-value store.
-* Lease - the lease ID to associate with the key in the key-value store. A lease value of 0 indicates no lease.
-* Prev_Kv - when set, responds with the key-value pair data before the update from this `Put` request.
-* Ignore_Value - when set, update the key without changing its current value. Returns an error if the key does not exist.
-* Ignore_Lease - when set, update the key without changing its current lease. Returns an error if the key does not exist.
-
-The client receives a `PutResponse` message from the `Put` call:
-
-```protobuf
-message PutResponse {
-  ResponseHeader header = 1;
-  mvccpb.KeyValue prev_kv = 2;
-}
-```
-
-* Prev_Kv - the key-value pair overwritten by the `Put`, if `Prev_Kv` was set in the `PutRequest`.
-
-### Delete Range
-
-Ranges of keys are deleted using the `DeleteRange` call, which takes a `DeleteRangeRequest`:
-
-```protobuf
-message DeleteRangeRequest {
-  bytes key = 1;
-  bytes range_end = 2;
-  bool prev_kv = 3;
-}
-```
-
-* Key, Range_End - The key range to delete.
-* Prev_Kv - when set, return the contents of the deleted key-value pairs.
-
-The client receives a `DeleteRangeResponse` message from the `DeleteRange` call:
-
-```protobuf
-message DeleteRangeResponse {
-  ResponseHeader header = 1;
-  int64 deleted = 2;
-  repeated mvccpb.KeyValue prev_kvs = 3;
-}
-```
-
-* Deleted - number of keys deleted.
-* Prev_Kv - a list of all key-value pairs deleted by the `DeleteRange` operation.
-
-### Transaction
-
-A transaction is an atomic If/Then/Else construct over the key-value store. It provides a primitive for grouping requests together in atomic blocks (i.e., then/else) whose execution is guarded (i.e., if) based on the contents of the key-value store. Transactions can be used for protecting keys from unintended concurrent updates, building compare-and-swap operations, and developing higher-level concurrency control.
-
-A transaction can atomically process multiple requests in a single request. For modifications to the key-value store, this means the store's revision is incremented only once for the transaction and all events generated by the transaction will have the same revision. However, modifications to the same key multiple times within a single transaction are forbidden.
-
-All transactions are guarded by a conjunction of comparisons, similar to an `If` statement. Each comparison checks a single key in the store. It may check for the absence or presence of a value, compare with a given value, or check a key's revision or version. Two different comparisons may apply to the same or different keys. All comparisons are applied atomically; if all comparisons are true, the transaction is said to succeed and etcd applies the transaction's then / `success` request block, otherwise it is said to fail and applies the else / `failure` request block.
-
-Each comparison is encoded as a `Compare` message:
-
-```protobuf
-message Compare {
-  enum CompareResult {
-    EQUAL = 0;
-    GREATER = 1;
-    LESS = 2;
-    NOT_EQUAL = 3;
-  }
-  enum CompareTarget {
-    VERSION = 0;
-    CREATE = 1;
-    MOD = 2;
-    VALUE= 3;
-  }
-  CompareResult result = 1;
-  // target is the key-value field to inspect for the comparison.
-  CompareTarget target = 2;
-  // key is the subject key for the comparison operation.
-  bytes key = 3;
-  oneof target_union {
-    int64 version = 4;
-    int64 create_revision = 5;
-    int64 mod_revision = 6;
-    bytes value = 7;
-  }
-}
-```
-
-* Result - the kind of logical comparison operation (e.g., equal, less than, etc).
-* Target - the key-value field to be compared. Either the key's version, create revision, modification revision, or value.
-* Key - the key for the comparison.
-* Target_Union - the user-specified data for the comparison.
-
-After processing the comparison block, the transaction applies a block of requests. A block is a list of `RequestOp` messages:
-
-```protobuf
-message RequestOp {
-  // request is a union of request types accepted by a transaction.
-  oneof request {
-    RangeRequest request_range = 1;
-    PutRequest request_put = 2;
-    DeleteRangeRequest request_delete_range = 3;
-  }
-}
-```
-
-* Request_Range - a `RangeRequest`.
-* Request_Put - a `PutRequest`. The keys must be unique. It may not share keys with any other Puts or Deletes.
-* Request_Delete_Range - a `DeleteRangeRequest`. It may not share keys with any Puts or Deletes requests.
-
-All together, a transaction is issued with a `Txn` API call, which takes a `TxnRequest`:
-
-```protobuf
-message TxnRequest {
-  repeated Compare compare = 1;
-  repeated RequestOp success = 2;
-  repeated RequestOp failure = 3;
-}
-```
-
-* Compare - A list of predicates representing a conjunction of terms for guarding the transaction.
-* Success - A list of requests to process if all compare tests evaluate to true.
-* Failure - A list of requests to process if any compare test evaluates to false.
-
-The client receives a `TxnResponse` message from the `Txn` call:
-
-```protobuf
-message TxnResponse {
-  ResponseHeader header = 1;
-  bool succeeded = 2;
-  repeated ResponseOp responses = 3;
-}
-```
-
-* Succeeded - Whether `Compare` evaluated to true or false.
-* Responses - A list of responses corresponding to the results from applying the `Success` block if succeeded is true or the `Failure` if succeeded is false.
-
-The `Responses` list corresponds to the results from the applied `RequestOp` list, with each response encoded as a `ResponseOp`:
-
-```protobuf
-message ResponseOp {
-  oneof response {
-    RangeResponse response_range = 1;
-    PutResponse response_put = 2;
-    DeleteRangeResponse response_delete_range = 3;
-  }
-}
-```
-
-## Watch API
-
-The `Watch` API provides an event-based interface for asynchronously monitoring changes to keys. An etcd3 watch waits for changes to keys by continuously watching from a given revision, either current or historical, and streams key updates back to the client.
-
-### Events
-
-Every change to every key is represented with `Event` messages. An `Event` message provides both the update's data and the type of update:
-
-```protobuf
-message Event {
-  enum EventType {
-    PUT = 0;
-    DELETE = 1;
-  }
-  EventType type = 1;
-  KeyValue kv = 2;
-  KeyValue prev_kv = 3;
-}
-```
-
-* Type - The kind of event. A PUT type indicates new data has been stored to the key. A DELETE indicates the key was deleted.
-* KV - The KeyValue associated with the event. A PUT event contains current kv pair. A PUT event with kv.Version=1 indicates the creation of a key. A DELETE event contains the deleted key with its modification revision set to the revision of deletion.
-* Prev_KV - The key-value pair for the key from the revision immediately before the event. To save bandwidth, it is only filled out if the watch has explicitly enabled it.
-
-### Watch streams
-
-Watches are long-running requests and use gRPC streams to stream event data. A watch stream is bi-directional; the client writes to the stream to establish watches and reads to receive watch events. A single watch stream can multiplex many distinct watches by tagging events with per-watch identifiers. This multiplexing helps reducing the memory footprint and connection overhead on the core etcd cluster.
-
-Watches make three guarantees about events:
-* Ordered - events are ordered by revision; an event will never appear on a watch if it precedes an event in time that has already been posted.
-* Reliable - a sequence of events will never drop any subsequence of events; if there are events ordered in time as a < b < c, then if the watch receives events a and c, it is guaranteed to receive b.
-* Atomic - a list of events is guaranteed to encompass complete revisions; updates in the same revision over multiple keys will not be split over several lists of events.
-
-A client creates a watch by sending a `WatchCreateRequest` over a stream returned by `Watch`:
-
-```protobuf
-message WatchCreateRequest {
-  bytes key = 1;
-  bytes range_end = 2;
-  int64 start_revision = 3;
-  bool progress_notify = 4;
-
-  enum FilterType {
-    NOPUT = 0;
-    NODELETE = 1;
-  }
-  repeated FilterType filters = 5;
-  bool prev_kv = 6;
-}
-```
-
-* Key, Range_End - The key range to watch.
-* Start_Revision - An optional revision for where to inclusively begin watching. If not given, it will stream events following the revision of the watch creation response header revision. The entire available event history can be watched starting from the last compaction revision.
-* Progress_Notify - When set, the watch will periodically receive a WatchResponse with no events, if there are no recent events. It is useful when clients wish to recover a disconnected watcher starting from a recent known revision. The etcd server decides how often to send notifications based on current server load.
-* Filters - A list of event types to filter away at server side.
-* Prev_Kv - When set, the watch receives the key-value data from before the event happens. This is useful for knowing what data has been overwritten.
-
-In response to a `WatchCreateRequest` or if there is a new event for some established watch, the client receives a `WatchResponse`:
-
-```protobuf
-message WatchResponse {
-  ResponseHeader header = 1;
-  int64 watch_id = 2;
-  bool created = 3;
-  bool canceled = 4;
-  int64 compact_revision = 5;
-
-  repeated mvccpb.Event events = 11;
-}
-```
-
-* Watch_ID - the ID of the watch that corresponds to the response.
-* Created - set to true if the response is for a create watch request. The client should store the ID and expect to receive events for the watch on the stream. All events sent to the created watcher will have the same watch_id.
-* Canceled - set to true if the response is for a cancel watch request. No further events will be sent to the canceled watcher.
-* Compact_Revision - set to the minimum historical revision available to etcd if a watcher tries watching at a compacted revision. This happens when creating a watcher at a compacted revision or the watcher cannot catch up with the progress of the key-value store. The watcher will be canceled; creating new watches with the same start_revision will fail.
-* Events - a list of new events in sequence corresponding to the given watch ID.
-
-If the client wishes to stop receiving events for a watch, it issues a `WatchCancelRequest`:
-
-```protobuf
-message WatchCancelRequest {
-   int64 watch_id = 1;
-}
-```
-
-* Watch_ID - the ID of the watch to cancel so that no more events are transmitted.
-
-## Lease API
-
-Leases are a mechanism for detecting client liveness. The cluster grants leases with a time-to-live. A lease expires if the etcd cluster does not receive a keepAlive within a given TTL period.
-
-To tie leases into the key-value store, each key may be attached to at most one lease. When a lease expires or is revoked, all keys attached to that lease will be deleted. Each expired key generates a delete event in the event history.
-
-### Obtaining leases
-
-Leases are obtained through the `LeaseGrant` API call, which takes a `LeaseGrantRequest`:
-
-```protobuf
-message LeaseGrantRequest {
-  int64 TTL = 1;
-  int64 ID = 2;
-}
-```
-
-* TTL - the advisory time-to-live, in seconds.
-* ID - the requested ID for the lease. If ID is set to 0, etcd will choose an ID.
-
-The client receives a `LeaseGrantResponse` from the `LeaseGrant` call:
-
-```protobuf
-message LeaseGrantResponse {
-  ResponseHeader header = 1;
-  int64 ID = 2;
-  int64 TTL = 3;
-}
-```
-
-* ID - the lease ID for the granted lease.
-* TTL - is the server selected time-to-live, in seconds, for the lease.
-
-```protobuf
-message LeaseRevokeRequest {
-  int64 ID = 1;
-}
-```
-
-* ID - the lease ID to revoke. When the lease is revoked, all attached keys are deleted.
-
-### Keep alives
-
-Leases are refreshed using a bi-directional stream created with the `LeaseKeepAlive` API call. When the client wishes to refresh a lease, it sends a `LeaseKeepAliveRequest` over the stream:
-
-```protobuf
-message LeaseKeepAliveRequest {
-  int64 ID = 1;
-}
-```
-
-* ID - the lease ID for the lease to keep alive.
-
-The keep alive stream responds with a `LeaseKeepAliveResponse`:
-
-```protobuf
-message LeaseKeepAliveResponse {
-  ResponseHeader header = 1;
-  int64 ID = 2;
-  int64 TTL = 3;
-}
-```
-
-* ID - the lease that was refreshed with a new TTL.
-* TTL - the new time-to-live, in seconds, that the lease has remaining.
-
-[elections]: https://github.com/etcd-io/etcd/blob/master/clientv3/concurrency/election.go
-[kv-proto]: https://github.com/etcd-io/etcd/blob/master/mvcc/mvccpb/kv.proto
-[grpc-api]: ../dev-guide/api_reference_v3.md
-[grpc-service]: https://github.com/etcd-io/etcd/blob/master/etcdserver/etcdserverpb/rpc.proto
-[locks]: https://github.com/etcd-io/etcd/blob/master/clientv3/concurrency/mutex.go
-[mvcc]: https://en.wikipedia.org/wiki/Multiversion_concurrency_control
-[stm]: https://github.com/etcd-io/etcd/blob/master/clientv3/concurrency/stm.go

Documentation/learning/api_guarantees.md

@@ -1,66 +0,0 @@
----
-title: KV API guarantees
----
-
-etcd is a consistent and durable key value store with [mini-transaction][txn] support. The key value store is exposed through the KV APIs. etcd tries to ensure the strongest consistency and durability guarantees for a distributed system. This specification enumerates the KV API guarantees made by etcd.
-
-### APIs to consider
-
-* Read APIs
-    * range
-    * watch
-* Write APIs
-    * put
-    * delete
-* Combination (read-modify-write) APIs
-    * txn
-
-### etcd specific definitions
-
-#### Operation completed
-
-An etcd operation is considered complete when it is committed through consensus, and therefore “executed” -- permanently stored -- by the etcd storage engine. The client knows an operation is completed when it receives a response from the etcd server. Note that the client may be uncertain about the status of an operation if it times out, or there is a network disruption between the client and the etcd member. etcd may also abort operations when there is a leader election. etcd does not send `abort` responses to  clients’ outstanding requests in this event.
-
-#### Revision
-
-An etcd operation that modifies the key value store is assigned a single increasing revision. A transaction operation might modify the key value store multiple times, but only one revision is assigned. The revision attribute of a key value pair that was modified by the operation has the same value as the revision of the operation. The revision can be used as a logical clock for key value store. A key value pair that has a larger revision is modified after a key value pair with a smaller revision. Two key value pairs that have the same revision are modified by an operation "concurrently".
-
-### Guarantees provided
-
-#### Atomicity
-
-All API requests are atomic; an operation either completes entirely or not at all. For watch requests, all events generated by one operation will be in one watch response. Watch never observes partial events for a single operation.
-
-#### Consistency
-
-All API calls ensure [sequential consistency][seq_consistency], the strongest consistency guarantee available from distributed systems. No matter which etcd member server a client makes requests to, a client reads the same events in the same order. If two members complete the same number of operations, the state of the two members is consistent.
-
-For watch operations, etcd guarantees to return the same value for the same key across all members for the same revision. For range operations, etcd has a similar guarantee for [linearized][Linearizability] access; serialized access may be behind the quorum state, so that the later revision is not yet available.
-
-As with all distributed systems, it is impossible for etcd to ensure [strict consistency][strict_consistency]. etcd does not guarantee that it will return to a read the “most recent” value (as measured by a wall clock when a request is completed) available on any cluster member.
-
-#### Isolation
-
-etcd ensures [serializable isolation][serializable_isolation], which is the highest isolation level available in distributed systems. Read operations will never observe any intermediate data.
-
-#### Durability
-
-Any completed operations are durable. All accessible data is also durable data. A read will never return data that has not been made durable.
-
-#### Linearizability
-
-Linearizability (also known as Atomic Consistency or External Consistency) is a consistency level between strict consistency and sequential consistency. 
-
-For linearizability, suppose each operation receives a timestamp from a loosely synchronized global clock. Operations are linearized if and only if they always complete as though they were executed in a sequential order and each operation appears to complete in the order specified by the program. Likewise, if an operation’s timestamp precedes another, that operation must also precede the other operation in the sequence.
-
-For example, consider a client completing a write at time point 1 (*t1*). A client issuing a read at *t2* (for *t2* > *t1*) should receive a value at least as recent as the previous write, completed at *t1*. However, the read might actually complete only by *t3*. Linearizability guarantees the read returns the most current value. Without linearizability guarantee, the returned value, current at *t2* when the read began, might be "stale" by *t3* because a concurrent write might happen between *t2* and *t3*.
-
-etcd does not ensure linearizability for watch operations. Users are expected to verify the revision of watch responses to ensure correct ordering.
-
-etcd ensures linearizability for all other operations by default. Linearizability comes with a cost, however, because linearized requests must go through the Raft consensus process. To obtain lower latencies and higher throughput for read requests, clients can configure a request’s consistency mode to `serializable`, which may access stale data with respect to quorum, but removes the performance penalty of linearized accesses' reliance on live consensus.
-
-[seq_consistency]: https://en.wikipedia.org/wiki/Consistency_model#Sequential_consistency
-[strict_consistency]: https://en.wikipedia.org/wiki/Consistency_model#Strict_consistency
-[serializable_isolation]: https://en.wikipedia.org/wiki/Isolation_(database_systems)#Serializable
-[Linearizability]: #Linearizability
-[txn]: api.md#transactions

Documentation/learning/data_model.md

@@ -1,27 +0,0 @@
----
-title: Data model
----
-
-etcd is designed to reliably store infrequently updated data and provide reliable watch queries. etcd exposes previous versions of key-value pairs to support inexpensive snapshots and watch history events (“time travel queries”). A persistent, multi-version, concurrency-control data model is a good fit for these use cases.
-
-etcd stores data in a multiversion [persistent][persistent-ds] key-value store. The persistent key-value store preserves the previous version of a key-value pair when its value is superseded with new data. The key-value store is effectively immutable; its operations do not update the structure in-place, but instead always generate a new updated structure. All past versions of keys are still accessible and watchable after modification. To prevent the data store from growing indefinitely over time and from maintaining old versions, the store may be compacted to shed the oldest versions of superseded data.
-
-### Logical view
-
-The store’s logical view is a flat binary key space. The key space has a lexically sorted index on byte string keys so range queries are inexpensive.
-
-The key space maintains multiple **revisions**. Each atomic mutative operation (e.g., a transaction operation may contain multiple operations) creates a new revision on the key space. All data held by previous revisions remains unchanged. Old versions of key can still be accessed through previous revisions. Likewise, revisions are indexed as well; ranging over revisions with watchers is efficient. If the store is compacted to save space, revisions before the compact revision will be removed. Revisions are monotonically increasing over the lifetime of a cluster.
-
-A key's life spans a generation, from creation to deletion. Each key may have one or multiple generations. Creating a key increments the **version** of that key, starting at 1 if the key does not exist at the current revision. Deleting a key generates a key tombstone, concluding the key’s current generation by resetting its version to 0. Each modification of a key increments its version; so, versions are monotonically increasing within a key's generation. Once a compaction happens, any generation ended before the compaction revision will be removed, and values set before the compaction revision except the latest one will be removed.
-
-### Physical view
-
-etcd stores the physical data as key-value pairs in a persistent [b+tree][b+tree]. Each revision of the store’s state only contains the delta from its previous revision to be efficient. A single revision may correspond to multiple keys in the tree.
-
-The key of key-value pair is a 3-tuple (major, sub, type). Major is the store revision holding the key. Sub differentiates among  keys within the same revision. Type is an optional suffix for special value (e.g., `t` if the value contains a tombstone). The value of the key-value pair contains the modification from previous revision, thus one delta from previous revision. The b+tree is ordered by key in lexical byte-order. Ranged lookups over revision deltas are fast; this enables quickly finding modifications from one specific revision to another. Compaction removes out-of-date keys-value pairs.
-
-etcd also keeps a secondary in-memory [btree][btree] index to speed up range queries over keys. The keys in the btree index are the keys of the store exposed to user. The value is a pointer to the modification of the persistent b+tree. Compaction removes dead pointers.
-
-[persistent-ds]: https://en.wikipedia.org/wiki/Persistent_data_structure
-[btree]: https://en.wikipedia.org/wiki/B-tree
-[b+tree]: https://en.wikipedia.org/wiki/B%2B_tree

Documentation/learning/design-auth-v3.md

@@ -1,79 +0,0 @@
----
-title: etcd v3 authentication design
----
-
-## Why not reuse the v2 auth system?
-
-The v3 protocol uses gRPC as its transport instead of a RESTful interface like v2. This new protocol provides an opportunity to iterate on and improve the v2 design. For example, v3 auth has connection based authentication, rather than v2's slower per-request authentication. Additionally, v2 auth's semantics tend to be unwieldy in practice with respect to reasoning about consistency, which will be described in the next sections. For v3, there is a well-defined description and implementation of the authentication mechanism which fixes the deficiencies in the v2 auth system.
-
-### Functionality requirements
-
-* Per connection authentication, not per request
-   * User ID + password based authentication implemented for the gRPC API
-   * Authentication must be refreshed after auth policy changes
-* Its functionality should be as simple and useful as v2
-   * v3 provides a flat key space, unlike the directory structure of v2. Permission checking will be provided as interval matching.
-* It should have stronger consistency guarantees than v2 auth
-
-### Main required changes
-
-* A client must create a dedicated connection only for authentication before sending authenticated requests
-* Add permission information (user ID and authorized revision) to the Raft commands (`etcdserverpb.InternalRaftRequest`)
-* Every request is permission checked in the state machine layer, rather than API layer
-
-### Permission metadata consistency
-
-The metadata for auth should also be stored and managed in the storage controlled by etcd's Raft protocol like other data stored in etcd. It is required for not sacrificing availability and consistency of the entire etcd cluster. If reading or writing the metadata (e.g. permission information) needs an agreement of every node (more than quorum), single node failure can stop the entire cluster. Requiring all nodes to agree at once means that checking ordinary read/write requests cannot be completed if any cluster member is down, even if the cluster has an available quorum. This unanimous scheme ultimately degrades cluster availability; quorum based consensus from raft should suffice since agreement follows from consistent ordering.
-
-The authentication mechanism in the etcd v2 protocol has a tricky part because the metadata consistency should work as in the above, but does not: each permission check is processed by the etcd member that receives the client request (etcdserver/api/v2http/client.go), including follower members. Therefore, it's possible the check may be based on stale metadata.
-
-
-This staleness means that auth configuration cannot be reflected as soon as operators execute etcdctl. Therefore there is no way to know how long the stale metadata is active. Practically, the configuration change is reflected immediately after the command execution. However, in some cases of heavy load, the inconsistent state can be prolonged and it might result in counter-intuitive situations for users and developers. It requires a workaround like this: https://github.com/etcd-io/etcd/pull/4317#issuecomment-179037582
-
-### Inconsistent permissions are unsafe for linearized requests
-
-Inconsistent authentication state is most serious for writes. Even if an operator disables write on a user, if the write is only ordered with respect to the key value store but not the authentication system, it's possible the write will complete successfully. Without ordering on both the auth store and the key-value store, the system will be susceptible to stale permission attacks.
-
-Therefore, the permission checking logic should be added to the state machine of etcd. Each state machine should check the requests based on its permission information in the apply phase (so the auth information must not be stale).
-
-## Design and implementation
-
-### Authentication
-
-At first, a client must create a gRPC connection only to authenticate its user ID and password. An etcd server will respond with an authentication reply. The response will be an authentication token on success or an error on failure. The client can use its authentication token to present its credentials to etcd when making API requests.
-
-The client connection used to request the authentication token is typically thrown away; it cannot carry the new token's credentials. This is because gRPC doesn't provide a way for adding per RPC credential after creation of the connection (calling `grpc.Dial()`). Therefore, a client cannot assign a token to its connection that is obtained through the connection. The client needs a new connection for using the token.
-
-#### Notes on the implementation of `Authenticate()` RPC
-
-`Authenticate()` RPC generates an authentication token based on a given user name and password. etcd saves and checks a configured password and a given password using Go's `bcrypt` package. By design, `bcrypt`'s password checking mechanism is computationally expensive, taking nearly 100ms on an ordinary x64 server. Therefore, performing this check in the state machine apply phase would cause performance trouble: the entire etcd cluster can only serve almost 10 `Authenticate()` requests per second.
-
-For good performance, the v3 auth mechanism checks passwords in etcd's API layer, where it can be parallelized outside of raft. However, this can lead to potential time-of-check/time-of-use (TOCTOU) permission lapses:
-1. client A sends a request `Authenticate()`
-1. the API layer processes the password checking part of `Authenticate()`
-1. another client B sends a request of `ChangePassword()` and the server completes it
-1. the state machine layer processes the part of getting a revision number for the `Authenticate()` from A
-1. the server returns a success to A
-1. now A is authenticated on an obsolete password
-
-For avoiding such a situation, the API layer performs *version number validation* based on the revision number of the auth store. During password checking, the API layer saves the revision number of auth store. After successful password checking, the API layer compares the saved revision number and the latest revision number. If the numbers differ, it means someone else updated the auth metadata. So it retries the checking. With this mechanism, the successful password checking based on the obsolete password can be avoided.
-
-### Resolving a token in the API layer
-
-After authenticating with `Authenticate()`, a client can create a gRPC connection as it would without auth. In addition to the existing initialization process, the client must associate the token with the newly created connection. `grpc.WithPerRPCCredentials()` provides the functionality for this purpose.
-
-Every authenticated request from the client has a token. The token can be obtained with `grpc.metadata.FromIncomingContext()` in the server side. The server can obtain who is issuing the request and when the user was authorized. The information will be filled by the API layer in the header (`etcdserverpb.RequestHeader.Username` and `etcdserverpb.RequestHeader.AuthRevision`) of a raft log entry (`etcdserverpb.InternalRaftRequest`).
-
-### Checking permission in the state machine
-
-The auth info in `etcdserverpb.RequestHeader` is checked in the apply phase of the state machine. This step checks the user is granted permission to requested keys on the latest revision of auth store.
-
-### Two types of tokens: simple and JWT
-
-There are two kinds of token types: simple and JWT. The simple token isn't designed for production use cases. Its tokens aren't cryptographically signed and servers must statefully track token-user correspondence; it is meant for development testing.  JWT tokens should be used for production deployments since it is cryptographically signed and verified. From the implementation perspective, JWT is stateless. Its token can include metadata including username and revision, so servers don't need to remember correspondence between tokens and the metadata.
-
-## Notes on the difference between KVS models and file system models
-
-etcd v3 is a KVS, not a file system. So the permissions can be granted to the users in form of an exact key name or a key range like `["start key", "end key")`. It means that granting a permission of a nonexistent key is possible. Users should care about unintended permission granting. In a case of file system like system (e.g. Chubby or ZooKeeper), an inode like data structure can include the permission information. So granting permission to a nonexist key won't be possible (except the case of sticky bits).
-
-The etcd v3 model requires multiple lookup of the metadata unlike the file system like systems. The worst case lookup cost will be sum the user's total granted keys and intervals. The cost cannot be avoided because v3's flat key space is completely different from Unix's file system model (every inode includes permission metadata). Practically the cost won’t be a serious problem because the metadata is small enough to benefit from caching.

Documentation/learning/design-client.md

@@ -1,138 +0,0 @@
----
-title: etcd client design
----
-
-etcd Client Design
-==================
-
-*Gyuho Lee (github.com/gyuho, Amazon Web Services, Inc.), Joe Betz (github.com/jpbetz, Google Inc.)*
-
-
-Introduction
-============
-
-etcd server has proven its robustness with years of failure injection testing. Most complex application logic is already handled by etcd server and its data stores (e.g. cluster membership is transparent to clients, with Raft-layer forwarding proposals to leader). Although server components are correct, its composition with client requires a different set of intricate protocols to guarantee its correctness and high availability under faulty conditions. Ideally, etcd server provides one logical cluster view of many physical machines, and client implements automatic failover between replicas. This documents client architectural decisions and its implementation details.
-
-
-Glossary
-========
-
-*clientv3*: etcd Official Go client for etcd v3 API.
-
-*clientv3-grpc1.0*: Official client implementation, with [`grpc-go v1.0.x`](https://github.com/grpc/grpc-go/releases/tag/v1.0.0), which is used in latest etcd v3.1.
-
-*clientv3-grpc1.7*: Official client implementation, with [`grpc-go v1.7.x`](https://github.com/grpc/grpc-go/releases/tag/v1.7.0), which is used in latest etcd v3.2 and v3.3.
-
-*clientv3-grpc1.23*: Official client implementation, with [`grpc-go v1.23.x`](https://github.com/grpc/grpc-go/releases/tag/v1.23.0), which is used in latest etcd v3.4.
-
-*Balancer*: etcd client load balancer that implements retry and failover mechanism. etcd client should automatically balance loads between multiple endpoints.
-
-*Endpoints*: A list of etcd server endpoints that clients can connect to. Typically, 3 or 5 client URLs of an etcd cluster.
-
-*Pinned endpoint*: When configured with multiple endpoints, <= v3.3 client balancer chooses only one endpoint to establish a TCP connection, in order to conserve total open connections to etcd cluster. In v3.4, balancer round-robins pinned endpoints for every request, thus distributing loads more evenly.
-
-*Client Connection*: TCP connection that has been established to an etcd server, via gRPC Dial.
-
-*Sub Connection*: gRPC SubConn interface. Each sub-connection contains a list of addresses. Balancer creates a SubConn from a list of resolved addresses. gRPC ClientConn can map to multiple SubConn (e.g. example.com resolves to `10.10.10.1` and `10.10.10.2` of two sub-connections). etcd v3.4 balancer employs internal resolver to establish one sub-connection for each endpoint.
-
-*Transient disconnect*: When gRPC server returns a status error of [`code Unavailable`](https://godoc.org/google.golang.org/grpc/codes#Code).
-
-
-Client Requirements
-===================
-
-*Correctness*. Requests may fail in the presence of server faults. However, it never violates consistency guarantees: global ordering properties, never write corrupted data, at-most once semantics for mutable operations, watch never observes partial events, and so on.
-
-*Liveness*. Servers may fail or disconnect briefly. Clients should make progress in either way. Clients should [never deadlock](https://github.com/etcd-io/etcd/issues/8980) waiting for a server to come back from offline, unless configured to do so. Ideally, clients detect unavailable servers with HTTP/2 ping and failover to other nodes with clear error messages.
-
-*Effectiveness*. Clients should operate effectively with minimum resources: previous TCP connections should be [gracefully closed](https://github.com/etcd-io/etcd/issues/9212) after endpoint switch. Failover mechanism should effectively predict the next replica to connect, without wastefully retrying on failed nodes.
-
-*Portability*. Official client should be clearly documented and its implementation be applicable to other language bindings. Error handling between different language bindings should be consistent. Since etcd is fully committed to gRPC, implementation should be closely aligned with gRPC long-term design goals (e.g. pluggable retry policy should be compatible with [gRPC retry](https://github.com/grpc/proposal/blob/master/A6-client-retries.md)). Upgrades between two client versions should be non-disruptive.
-
-
-Client Overview
-===============
-
-etcd client implements the following components:
-
-* balancer that establishes gRPC connections to an etcd cluster,
-* API client that sends RPCs to an etcd server, and
-* error handler that decides whether to retry a failed request or switch endpoints.
-
-Languages may differ in how to establish an initial connection (e.g. configure TLS), how to encode and send Protocol Buffer messages to server, how to handle stream RPCs, and so on. However, errors returned from etcd server will be the same. So should be error handling and retry policy.
-
-For example, etcd server may return `"rpc error: code = Unavailable desc = etcdserver: request timed out"`, which is transient error that expects retries. Or return `rpc error: code = InvalidArgument desc = etcdserver: key is not provided`, which means request was invalid and should not be retried. Go client can parse errors with `google.golang.org/grpc/status.FromError`, and Java client with `io.grpc.Status.fromThrowable`.
-
-
-clientv3-grpc1.0: Balancer Overview
------------------------------------
-
-`clientv3-grpc1.0` maintains multiple TCP connections when configured with multiple etcd endpoints. Then pick one address and use it to send all client requests. The pinned address is maintained until the client object is closed (see *Figure 1*). When the client receives an error, it randomly picks another and retries.
-
-![client-balancer-figure-01.png](img/client-balancer-figure-01.png)
-
-
-clientv3-grpc1.0: Balancer Limitation
--------------------------------------
-
-`clientv3-grpc1.0` opening multiple TCP connections may provide faster balancer failover but requires more resources. The balancer does not understand node’s health status or cluster membership. So, it is possible that balancer gets stuck with one failed or partitioned node.
-
-
-clientv3-grpc1.7: Balancer Overview
-------------------------------------
-
-`clientv3-grpc1.7` maintains only one TCP connection to a chosen etcd server. When given multiple cluster endpoints, a client first tries to connect to them all. As soon as one connection is up, balancer pins the address, closing others (see *Figure 2*). The pinned address is to be maintained until the client object is closed. An error, from server or client network fault, is sent to client error handler (see *Figure 3*).
-
-![client-balancer-figure-02.png](img/client-balancer-figure-02.png)
-
-![client-balancer-figure-03.png](img/client-balancer-figure-03.png)
-
-The client error handler takes an error from gRPC server, and decides whether to retry on the same endpoint, or to switch to other addresses, based on the error code and message (see *Figure 4* and *Figure 5*).
-
-![client-balancer-figure-04.png](img/client-balancer-figure-04.png)
-
-![client-balancer-figure-05.png](img/client-balancer-figure-05.png)
-
-Stream RPCs, such as Watch and KeepAlive, are often requested with no timeouts. Instead, client can send periodic HTTP/2 pings to check the status of a pinned endpoint; if the server does not respond to the ping, balancer switches to other endpoints (see *Figure 6*).
-
-![client-balancer-figure-06.png](img/client-balancer-figure-06.png)
-
-
-clientv3-grpc1.7: Balancer Limitation
--------------------------------------
-
-`clientv3-grpc1.7` balancer sends HTTP/2 keepalives to detect disconnects from streaming requests. It is a simple gRPC server ping mechanism and does not reason about cluster membership, thus unable to detect network partitions. Since partitioned gRPC server can still respond to client pings, balancer may get stuck with a partitioned node. Ideally, keepalive ping detects partition and triggers endpoint switch, before request time-out (see [etcd#8673](https://github.com/etcd-io/etcd/issues/8673) and *Figure 7*).
-
-![client-balancer-figure-07.png](img/client-balancer-figure-07.png)
-
-`clientv3-grpc1.7` balancer maintains a list of unhealthy endpoints. Disconnected addresses are added to “unhealthy” list, and considered unavailable until after wait duration, which is hard coded as dial timeout with default value 5-second. Balancer can have false positives on which endpoints are unhealthy. For instance, endpoint A may come back right after being blacklisted, but still unusable for next 5 seconds (see *Figure 8*).
-
-`clientv3-grpc1.0` suffered the same problems above.
-
-![client-balancer-figure-08.png](img/client-balancer-figure-08.png)
-
-Upstream gRPC Go had already migrated to new balancer interface. For example, `clientv3-grpc1.7` underlying balancer implementation uses new gRPC balancer and tries to be consistent with old balancer behaviors. While its compatibility has been maintained reasonably well, etcd client still [suffered from subtle breaking changes](https://github.com/grpc/grpc-go/issues/1649). Furthermore, gRPC maintainer recommends to [not rely on the old balancer interface](https://github.com/grpc/grpc-go/issues/1942#issuecomment-375368665). In general, to get better support from upstream, it is best to be in sync with latest gRPC releases. And new features, such as retry policy, may not be backported to gRPC 1.7 branch. Thus, both etcd server and client must migrate to latest gRPC versions.
-
-
-clientv3-grpc1.23: Balancer Overview
-------------------------------------
-
-`clientv3-grpc1.7` is so tightly coupled with old gRPC interface, that every single gRPC dependency upgrade broke client behavior. Majority of development and debugging efforts were devoted to fixing those client behavior changes. As a result, its implementation has become overly complicated with bad assumptions on server connectivities.
-
-The primary goal of `clientv3-grpc1.23` is to simplify balancer failover logic; rather than maintaining a list of unhealthy endpoints, which may be stale, simply roundrobin to the next endpoint whenever client gets disconnected from the current endpoint. It does not assume endpoint status. Thus, no more complicated status tracking is needed (see *Figure 8* and above). Upgrading to `clientv3-grpc1.23` should be no issue; all changes were internal while keeping all the backward compatibilities.
-
-Internally, when given multiple endpoints, `clientv3-grpc1.23` creates multiple sub-connections (one sub-connection per each endpoint), while `clientv3-grpc1.7` creates only one connection to a pinned endpoint (see *Figure 9*). For instance, in 5-node cluster, `clientv3-grpc1.23` balancer would require 5 TCP connections, while `clientv3-grpc1.7` only requires one. By preserving the pool of TCP connections, `clientv3-grpc1.23` may consume more resources but provide more flexible load balancer with better failover performance. The default balancing policy is round robin but can be easily extended to support other types of balancers (e.g. power of two, pick leader, etc.). `clientv3-grpc1.23` uses gRPC resolver group and implements balancer picker policy, in order to delegate complex balancing work to upstream gRPC. On the other hand, `clientv3-grpc1.7` manually handles each gRPC connection and balancer failover, which complicates the implementation. `clientv3-grpc1.23` implements retry in the gRPC interceptor chain that automatically handles gRPC internal errors and enables more advanced retry policies like backoff, while `clientv3-grpc1.7` manually interprets gRPC errors for retries.
-
-![client-balancer-figure-09.png](img/client-balancer-figure-09.png)
-
-
-clientv3-grpc1.23: Balancer Limitation
---------------------------------------
-
-Improvements can be made by caching the status of each endpoint. For instance, balancer can ping each server in advance to maintain a list of healthy candidates, and use this information when doing round-robin. Or when disconnected, balancer can prioritize healthy endpoints. This may complicate the balancer implementation, thus can be addressed in later versions.
-
-Client-side keepalive ping still does not reason about network partitions. Streaming request may get stuck with a partitioned node. Advanced health checking service need to be implemented to understand the cluster membership (see [etcd#8673](https://github.com/etcd-io/etcd/issues/8673) for more detail).
-
-![client-balancer-figure-07.png](img/client-balancer-figure-07.png)
-
-Currently, retry logic is handled manually as an interceptor. This may be simplified via [official gRPC retries](https://github.com/grpc/proposal/blob/master/A6-client-retries.md).

Documentation/learning/design-learner.md

@@ -1,119 +0,0 @@
----
-title: etcd learner design
----
-
-etcd Learner
-============
-
-*Gyuho Lee (github.com/gyuho, Amazon Web Services, Inc.), Joe Betz (github.com/jpbetz, Google Inc.)*
-
-
-Background
-==========
-
-Membership reconfiguration has been one of the biggest operational challenges. Let’s review common challenges.
-
-A newly joined etcd member starts with no data, thus demanding more updates from leader until it catches up with leader’s logs. Then leader’s network is more likely to be overloaded, blocking or dropping leader heartbeats to followers. In such case, a follower may election-timeout to start a new leader election. That is, a cluster with a new member is more vulnerable to leader election. Both leader election and the subsequent update propagation to the new member are prone to causing periods of cluster unavailability (see *Figure 1*).
-
-![server-learner-figure-01](img/server-learner-figure-01.png)
-
-What if network partition happens? It depends on leader partition. If the leader still maintains the active quorum, the cluster would continue to operate (see *Figure 2*).
-
-![server-learner-figure-02](img/server-learner-figure-02.png)
-
-What if the leader becomes isolated from the rest of the cluster? Leader monitors progress of each follower. When leader loses connectivity from the quorum, it reverts back to follower which will affect the cluster availability (see *Figure 3*).
-
-![server-learner-figure-03](img/server-learner-figure-03.png)
-
-When a new node is added to 3 node cluster, the cluster size becomes 4 and the quorum size becomes 3. What if a new node had joined the cluster, and then network partition happens? It depends on which partition the new member gets located after partition. If the new node happens to be located in the same partition as leader’s, the leader still maintains the active quorum of 3. No leadership election happens, and no cluster availability gets affected (see *Figure 4*).
-
-![server-learner-figure-04](img/server-learner-figure-04.png)
-
-If the cluster is 2-and-2 partitioned, then neither of partition maintains the quorum of 3. In this case, leadership election happens (see *Figure 5*).
-
-![server-learner-figure-05](img/server-learner-figure-05.png)
-
-What if network partition happens first, and then a new member gets added? A partitioned 3-node cluster already has one disconnected follower. When a new member is added, the quorum changes from 2 to 3. Now, this cluster has only 2 active nodes out 4, thus losing quorum and starting a new leadership election (see *Figure 6*).
-
-![server-learner-figure-06](img/server-learner-figure-06.png)
-
-Since member add operation can change the size of quorum, it is always recommended to “member remove” first to replace an unhealthy node.
-
-Adding a new member to a 1-node cluster changes the quorum size to 2, immediately causing a leader election when the previous leader finds out quorum is not active. This is because “member add” operation is a 2-step process where user needs to apply “member add” command first, and then starts the new node process (see *Figure 7*).
-
-![server-learner-figure-07](img/server-learner-figure-07.png)
-
-An even worse case is when an added member is misconfigured. Membership reconfiguration is a two-step process: “etcdctl member add” and starting an etcd server process with the given peer URL. That is, “member add” command is applied regardless of URL, even when the URL value is invalid. If the first step is applied with invalid URLs, the second step cannot even start the new etcd. Once the cluster loses quorum, there is no way to revert the membership change (see *Figure 8*).
-
-![server-learner-figure-08](img/server-learner-figure-08.png)
-
-Same applies to a multi-node cluster. For example, the cluster has two members down (one is failed, the other is misconfigured) and two members up, but now it requires at least 3 votes to change the cluster membership (see *Figure 9*).
-
-![server-learner-figure-09](img/server-learner-figure-09.png)
-
-As seen above, a simple misconfiguration can fail the whole cluster into an inoperative state. In such case, an operator need manually recreate the cluster with `etcd --force-new-cluster` flag. As etcd has become a mission-critical service for Kubernetes, even the slightest outage may have significant impact on users. What can we better to make etcd such operations easier? Among other things, leader election is most critical to cluster availability: Can we make membership reconfiguration less disruptive by not changing the size of quorum? Can a new node be idle, only requesting the minimum updates from leader, until it catches up? Can membership misconfiguration be always reversible and handled in a more secure way (wrong member add command run should never fail the cluster)? Should an user worry about network topology when adding a new member? Can member add API work regardless of the location of nodes and ongoing network partitions?
-
-Raft Learner
-============
-
-In order to mitigate such availability gaps in the previous section, [Raft §4.2.1](https://github.com/ongardie/dissertation/blob/master/stanford.pdf) introduces a new node state “Learner”, which joins the cluster as a **non-voting member** until it catches up to leader’s logs.
-
-Features in v3.4
-----------------
-
-An operator should do the minimum amount of work possible to add a new learner node. `member add --learner` command to add a new learner, which joins cluster as a non-voting member but still receives all data from leader (see *Figure 10*).
-
-![server-learner-figure-10](img/server-learner-figure-10.png)
-
-When a learner has caught up with leader’s progress, the learner can be promoted to a voting member using `member promote` API, which then counts towards the quorum (see *Figure 11*).
-
-![server-learner-figure-11](img/server-learner-figure-11.png)
-
-etcd server validates promote request to ensure its operational safety. Only after its log has caught up to leader’s can learner be promoted to a voting member (see *Figure 12*).
-
-![server-learner-figure-12](img/server-learner-figure-12.png)
-
-Learner only serves as a standby node until promoted: Leadership cannot be transferred to learner. Learner rejects client reads and writes (client balancer should not route requests to learner). Which means learner does not need issue Read Index requests to leader. Such limitation simplifies the initial learner implementation in v3.4 release (see *Figure 13*).
-
-![server-learner-figure-13](img/server-learner-figure-13.png)
-
-In addition, etcd limits the total number of learners that a cluster can have, and avoids overloading the leader with log replication. Learner never promotes itself. While etcd provides learner status information and safety checks, cluster operator must make the final decision whether to promote learner or not.
-
-Features in v3.5
-----------------
-
-*Make learner state only and default*: Defaulting a new member state to learner will greatly improve membership reconfiguration safety, because learner does not change the size of quorum. Misconfiguration will always be reversible without losing the quorum.
-
-*Make voting-member promotion fully automatic*: Once a learner catches up to leader’s logs, a cluster can automatically promote the learner. etcd requires certain thresholds to be defined by the user, and once the requirements are satisfied, learner promotes itself to a voting member. From a user’s perspective, “member add” command would work the same way as today but with greater safety provided by learner feature.
-
-*Make learner standby failover node*: A learner joins as a standby node, and gets automatically promoted when the cluster availability is affected.
-
-*Make learner read-only*: A learner can serve as a read-only node that never gets promoted. In a weak consistency mode, learner only receives data from leader and never process writes. Serving reads locally without consensus overhead would greatly decrease the workloads to leader but may serve stale data. In a strong consistency mode, learner requests read index from leader to serve latest data, but still rejects writes.
-
-Learner vs. Mirror Maker
-========================
-
-etcd implements “mirror maker” using watch API to continuously relay key creates and updates to a separate cluster. Mirroring usually has low latency overhead once it completes initial synchronization. Learner and mirroring overlap in that both can be used to replicate existing data for read-only. However, mirroring does not guarantee linearizability. During network disconnects, previous key-values might have been discarded, and clients are expected to verify watch responses for correct ordering. Thus, there is no ordering guarantee in mirror. Use mirror for minimum latency (e.g. cross data center) at the costs of consistency. Use learner to retain all historical data and its ordering.
-
-Appendix: Learner Implementation in v3.4
-========================================
-
-*Expose "Learner" node type to "MemberAdd" API.*
-
-etcd client adds a flag to “MemberAdd” API for learner node. And etcd server handler applies membership change entry with `pb.ConfChangeAddLearnerNode` type. Once the command has been applied, a server joins the cluster with `etcd --initial-cluster-state=existing` flag. This learner node can neither vote nor count as quorum.
-
-etcd server must not transfer leadership to learner, since it may still lag behind and does not count as quorum. etcd server limits the number of learners that cluster can have to one: the more learners we have, the more data the leader has to propagate. Clients may talk to learner node, but learner rejects all requests other than serializable read and member status API. This is for simplicity of initial implementation. In the future, learner can be extended as a read-only server that continuously mirrors cluster data. Client balancer must provide helper function to exclude learner node endpoint. Otherwise, request sent to learner may fail. Client sync member call should factor into learner node type. So should client endpoints update call.
-
-`MemberList` and `MemberStatus` responses should indicate which node is learner.
-
-*Add "MemberPromote" API.*
-
-Internally in Raft, second `MemberAdd` call to learner node promotes it to a voting member. Leader maintains the progress of each follower and learner. If learner has not completed its snapshot message, reject promote request. Only accept promote request if and only if: The learner node is in a healthy state. The learner is in sync with leader or the delta is within the threshold (e.g. the number of entries to replicate to learner is less than 1/10 of snapshot count, which means it is less likely that even after promotion leader would not need send snapshot to the learner). All these logic are hard-coded in `etcdserver` package and not configurable.
-
-Reference
-=========
-
-- Original github issue: [etcd#9161](https://github.com/etcd-io/etcd/issues/9161)
-- Use case: [etcd#3715](https://github.com/etcd-io/etcd/issues/3715)
-- Use case: [etcd#8888](https://github.com/etcd-io/etcd/issues/8888)
-- Use case: [etcd#10114](https://github.com/etcd-io/etcd/issues/10114)

Documentation/learning/glossary.md

@@ -1,99 +0,0 @@
----
-title: Glossary
----
-
-This document defines the various terms used in etcd documentation, command line and source code.
-
-## Alarm
-
-The etcd server raises an alarm whenever the cluster needs operator intervention to remain reliable.
-
-## Authentication
-
-Authentication manages user access permissions for etcd resources.
-
-## Client
-
-A client connects to the etcd cluster to issue service requests such as fetching key-value pairs, writing data, or watching for updates.
-
-## Cluster
-
-Cluster consists of several members.
-
-The node in each member follows raft consensus protocol to replicate logs. Cluster receives proposals from members, commits them and apply to local store.
-
-## Compaction
-
-Compaction discards all etcd event history and superseded keys prior to a given revision. It is used to reclaim storage space in the etcd backend database.
-
-## Election
-
-The etcd cluster holds elections among its members to choose a leader as part of the raft consensus protocol.
-
-## Endpoint
-
-A URL pointing to an etcd service or resource.
-
-## Key
-
-A user-defined identifier for storing and retrieving user-defined values in etcd.
-
-## Key range
-
-A set of keys containing either an individual key, a lexical interval for all x such that a < x <= b, or all keys greater than a given key.
-
-## Keyspace
-
-The set of all keys in an etcd cluster.
-
-## Lease
-
-A short-lived renewable contract that deletes keys associated with it on its expiry.
-
-## Member
-
-A logical etcd server that participates in serving an etcd cluster.
-
-## Modification Revision
-
-The first revision to hold the last write to a given key.
-
-## Peer
-
-Peer is another member of the same cluster.
-
-## Proposal
-
-A proposal is a request (for example a write request, a configuration change request) that needs to go through raft protocol.
-
-## Quorum
-
-The number of active members needed for consensus to modify the cluster state. etcd requires a member majority to reach quorum.
-
-## Revision
-
-A 64-bit cluster-wide counter that is incremented each time the keyspace is modified.
-
-## Role
-
-A unit of permissions over a set of key ranges which may be granted to a set of users for access control.
-
-## Snapshot
-
-A point-in-time backup of the etcd cluster state.
-
-## Store
-
-The physical storage backing the cluster keyspace.
-
-## Transaction
-
-An atomically executed set of operations. All modified keys in a transaction share the same modification revision.
-
-## Key Version
-
-The number of writes to a key since it was created, starting at 1. The version of a nonexistent or deleted key is 0.
-
-## Watcher
-
-A client opens a watcher to observe updates on a given key range.

Documentation/learning/why.md

@@ -1,118 +0,0 @@
----
-title: etcd versus other key-value stores
----
-
-The name "etcd" originated from two ideas, the unix "/etc" folder and "d"istributed systems. The "/etc" folder is a place to store configuration data for a single system whereas etcd stores configuration information for large scale distributed systems. Hence, a "d"istributed "/etc" is "etcd".
-
-etcd is designed as a general substrate for large scale distributed systems. These are systems that will never tolerate split-brain operation and are willing to sacrifice availability to achieve this end. etcd stores metadata in a consistent and fault-tolerant way. An etcd cluster is meant to provide key-value storage with best of class stability, reliability, scalability and performance.
-
-Distributed systems use etcd as a consistent key-value store for configuration management, service discovery, and coordinating distributed work. Many [organizations][production-users] use etcd to implement production systems such as container schedulers, service discovery services, and distributed data storage. Common distributed patterns using etcd include [leader election][etcd-etcdctl-elect], [distributed locks][etcd-etcdctl-lock], and monitoring machine liveness.
-
-## Use cases
-
-- Container Linux by CoreOS: Applications running on [Container Linux][container-linux] get automatic, zero-downtime Linux kernel updates. Container Linux uses [locksmith] to coordinate updates. Locksmith implements a distributed semaphore over etcd to ensure only a subset of a cluster is rebooting at any given time.
-- [Kubernetes][kubernetes] stores configuration data into etcd for service discovery and cluster management; etcd's consistency is crucial for correctly scheduling and operating services. The Kubernetes API server persists cluster state into etcd. It uses etcd's watch API to monitor the cluster and roll out critical configuration changes.
-
-## Comparison chart
-
-Perhaps etcd already seems like a good fit, but as with all technological decisions, proceed with caution. Please note this documentation is written by the etcd team. Although the ideal is a disinterested comparison of technology and features, the authors’ expertise and biases obviously favor etcd. Use only as directed.
-
-The table below is a handy quick reference for spotting the differences among etcd and its most popular alternatives at a glance. Further commentary and details for each column are in the sections following the table.
-
-|  | etcd | ZooKeeper | Consul | NewSQL (Cloud Spanner, CockroachDB, TiDB) |
-| --- | --- | --- | --- | --- |
-| Concurrency Primitives |  [Lock RPCs][etcd-v3lock], [Election RPCs][etcd-v3election], [command line locks][etcd-etcdctl-lock], [command line elections][etcd-etcdctl-elect], [recipes][etcd-recipe]  in go | External [curator recipes][curator] in Java | [Native lock API][consul-lock] | [Rare][newsql-leader], if any |
-| Linearizable Reads | [Yes][etcd-linread] | No | [Yes][consul-linread] | Sometimes |
-| Multi-version Concurrency Control | [Yes][etcd-mvcc] | No | No | Sometimes |
-| Transactions | [Field compares, Read, Write][etcd-txn] | [Version checks, Write][zk-txn] | [Field compare, Lock, Read, Write][consul-txn]  | SQL-style |
-| Change Notification | [Historical and current key intervals][etcd-watch] | [Current keys and directories][zk-watch] | [Current keys and prefixes][consul-watch] | Triggers (sometimes) |
-| User permissions | [Role based][etcd-rbac] | [ACLs][zk-acl] | [ACLs][consul-acl] | Varies (per-table [GRANT][cockroach-grant], per-database [roles][spanner-roles]) |
-| HTTP/JSON API | [Yes][etcd-json] | No | [Yes][consul-json] | Rarely |
-| Membership Reconfiguration | [Yes][etcd-reconfig] | [>3.5.0][zk-reconfig] | [Yes][consul-reconfig] | Yes |
-| Maximum reliable database size | Several gigabytes | Hundreds of megabytes (sometimes several gigabytes) | Hundreds of MBs | Terabytes+ |
-| Minimum read linearization latency | Network RTT | No read linearization | RTT + fsync | Clock barriers (atomic, NTP) |
-
-### ZooKeeper
-
-ZooKeeper solves the same problem as etcd: distributed system coordination and metadata storage. However, etcd has the luxury of hindsight taken from engineering and operational experience with ZooKeeper’s design and implementation. The lessons learned from Zookeeper certainly informed etcd’s design, helping it support large scale systems like Kubernetes. The improvements etcd made over Zookeeper include:
-
-* Dynamic cluster membership reconfiguration
-* Stable read/write under high load
-* A multi-version concurrency control data model
-* Reliable key monitoring which never silently drop events
-* Lease primitives decoupling connections from sessions
-* APIs for safe distributed shared locks
-
-Furthermore, etcd supports a wide range of languages and frameworks out of the box. Whereas Zookeeper has its own custom Jute RPC protocol, which is totally unique to Zookeeper and limits its [supported language bindings][zk-bindings], etcd’s client protocol is built from [gRPC][grpc], a popular RPC framework with language bindings for go, C++, Java, and more. Likewise, gRPC can be serialized into JSON over HTTP, so even general command line utilities like `curl` can talk to it. Since systems can select from a variety of choices, they are built on etcd with native tooling rather than around etcd with a single fixed set of technologies.
-
-When considering features, support, and stability, new applications planning to use Zookeeper for a consistent key value store would do well to choose etcd instead.
-
-### Consul
-
-Consul is an end-to-end service discovery framework. It provides built-in health checking, failure detection, and DNS services. In addition, Consul exposes a key value store with RESTful HTTP APIs. [As it stands in Consul 1.0][dbtester-comparison-results], the storage system does not scale as well as other systems like etcd or Zookeeper in key-value operations; systems requiring millions of keys will suffer from high latencies and memory pressure. The key value API is missing, most notably, multi-version keys, conditional transactions, and reliable streaming watches.
-
-etcd and Consul solve different problems. If looking for a distributed consistent key value store, etcd is a better choice over Consul. If looking for end-to-end cluster service discovery, etcd will not have enough features; choose Kubernetes, Consul, or SmartStack.
-
-### NewSQL (Cloud Spanner, CockroachDB, TiDB)
-
-Both etcd and NewSQL databases (e.g., [Cockroach][cockroach], [TiDB][tidb], [Google Spanner][spanner]) provide strong data consistency guarantees with high availability. However, the significantly different system design parameters lead to significantly different client APIs and performance characteristics.
-
-NewSQL databases are meant to horizontally scale across data centers. These systems typically partition data across multiple consistent replication groups (shards), potentially distant, storing data sets on the order of terabytes and above. This sort of scaling makes them poor candidates for distributed coordination as they have long latencies from waiting on clocks and expect updates with mostly localized dependency graphs. The data is organized into tables, including SQL-style query facilities with richer semantics than etcd, but at the cost of additional complexity for processing, planning, and optimizing queries.
-
-In short, choose etcd for storing metadata or coordinating distributed applications. If storing more than a few GB of data or if full SQL queries are needed, choose a NewSQL database.
-
-## Using etcd for metadata
-
-etcd replicates all data within a single consistent replication group. For storing up to a few GB of data with consistent ordering, this is the most efficient approach. Each modification of cluster state, which may change multiple keys, is assigned a global unique ID, called a revision in etcd, from a monotonically increasing counter for reasoning over ordering. Since there’s only a single replication group, the modification request only needs to go through the raft protocol to commit. By limiting consensus to one replication group, etcd gets distributed consistency with a simple protocol while achieving low latency and high throughput.
-
-The replication behind etcd cannot horizontally scale because it lacks data sharding. In contrast, NewSQL databases usually shard data across multiple consistent replication groups, storing data sets on the order of terabytes and above. However, to assign each modification a global unique and increasing ID, each request must go through an additional coordination protocol among replication groups. This extra coordination step may potentially conflict on the global ID, forcing ordered requests to retry. The result is a more complicated approach with typically worse performance than etcd for strict ordering.
-
-If an application reasons primarily about metadata or metadata ordering, such as to coordinate processes, choose etcd. If the application needs a large data store spanning multiple data centers and does not heavily depend on strong global ordering properties, choose a NewSQL database.
-
-## Using etcd for distributed coordination
-
-etcd has distributed coordination primitives such as event watches, leases, elections, and distributed shared locks out of the box. These primitives are both maintained and supported by the etcd developers; leaving these primitives to external libraries shirks the responsibility of developing foundational distributed software, essentially leaving the system incomplete. NewSQL databases usually expect these distributed coordination primitives to be authored by third parties. Likewise, ZooKeeper famously has a separate and independent [library][curator] of coordination recipes. Consul, which provides a native locking API, goes so far as to apologize that it’s “[not a bulletproof method][consul-bulletproof]”.
-
-In theory, it’s possible to build these primitives atop any storage systems providing strong consistency. However, the algorithms tend to be subtle; it is easy to develop a locking algorithm that appears to work, only to suddenly break due to  thundering herd and timing skew. Furthermore, other primitives supported by etcd, such as transactional memory depend on etcd’s MVCC data model; simple strong consistency is not enough.
-
-For distributed coordination, choosing etcd can help prevent operational headaches and save engineering effort.
-
-[production-users]: ../production-users.md
-[grpc]: https://www.grpc.io
-[consul-bulletproof]: https://www.consul.io/docs/internals/sessions.html
-[curator]: http://curator.apache.org/
-[cockroach]: https://github.com/cockroachdb/cockroach
-[spanner]: https://cloud.google.com/spanner/
-[tidb]: https://github.com/pingcap/tidb
-[etcd-v3lock]: https://godoc.org/github.com/etcd-io/etcd/etcdserver/api/v3lock/v3lockpb
-[etcd-v3election]: https://godoc.org/github.com/coreos/etcd-io/etcdserver/api/v3election/v3electionpb
-[etcd-etcdctl-lock]: ../../etcdctl/README.md#lock-lockname-command-arg1-arg2-
-[etcd-etcdctl-elect]: ../../etcdctl/README.md#elect-options-election-name-proposal
-[etcd-mvcc]: data_model.md
-[etcd-recipe]: https://godoc.org/github.com/etcd-io/etcd/contrib/recipes
-[consul-lock]: https://www.consul.io/docs/commands/lock.html
-[newsql-leader]: http://dl.acm.org/citation.cfm?id=2960999
-[etcd-reconfig]: ../op-guide/runtime-configuration.md
-[zk-reconfig]: https://zookeeper.apache.org/doc/trunk/zookeeperReconfig.html
-[consul-reconfig]: https://www.consul.io/docs/guides/servers.html
-[etcd-linread]: api_guarantees.md#linearizability
-[consul-linread]: https://www.consul.io/docs/agent/http.html#consistency
-[etcd-json]: ../dev-guide/api_grpc_gateway.md
-[consul-json]: https://www.consul.io/docs/agent/http.html#formatted-json-output
-[etcd-txn]: api.md#transaction
-[zk-txn]: https://zookeeper.apache.org/doc/r3.4.3/api/org/apache/zookeeper/ZooKeeper.html#multi(java.lang.Iterable)
-[consul-txn]: https://www.consul.io/docs/agent/http/kv.html#txn
-[etcd-watch]: api.md#watch-streams
-[zk-watch]: https://zookeeper.apache.org/doc/trunk/zookeeperProgrammers.html#ch_zkWatches
-[consul-watch]: https://www.consul.io/docs/agent/watches.html
-[etcd-commonname]: ../op-guide/authentication.md#using-tls-common-name
-[etcd-rbac]: ../op-guide/authentication.md#working-with-roles
-[zk-acl]: https://zookeeper.apache.org/doc/r3.1.2/zookeeperProgrammers.html#sc_ZooKeeperAccessControl
-[consul-acl]: https://www.consul.io/docs/internals/acl.html
-[cockroach-grant]: https://www.cockroachlabs.com/docs/stable/grant.html
-[spanner-roles]: https://cloud.google.com/spanner/docs/iam#roles
-[zk-bindings]: https://zookeeper.apache.org/doc/r3.1.2/zookeeperProgrammers.html#ch_bindings
-[container-linux]: https://coreos.com/why
-[locksmith]: https://github.com/coreos/locksmith
-[kubernetes]: https://kubernetes.io/docs/concepts/overview/what-is-kubernetes/
-[dbtester-comparison-results]: https://github.com/coreos/dbtester/tree/master/test-results/2018Q1-02-etcd-zookeeper-consul

Documentation/metrics.md

@@ -1,118 +0,0 @@
----
-title: Metrics
----
-
-etcd uses [Prometheus][prometheus] for metrics reporting. The metrics can be used for real-time monitoring and debugging. etcd does not persist its metrics; if a member restarts, the metrics will be reset.
-
-The simplest way to see the available metrics is to cURL the metrics endpoint `/metrics`. The format is described [here](http://prometheus.io/docs/instrumenting/exposition_formats/).
-
-Follow the [Prometheus getting started doc][prometheus-getting-started] to spin up a Prometheus server to collect etcd metrics.
-
-The naming of metrics follows the suggested [Prometheus best practices][prometheus-naming]. A metric name has an `etcd` or `etcd_debugging` prefix as its namespace and a subsystem prefix (for example `wal` and `etcdserver`).
-
-## etcd namespace metrics
-
-The metrics under the `etcd` prefix are for monitoring and alerting. They are stable high level metrics. If there is any change of these metrics, it will be included in release notes.
-
-Metrics that are etcd2 related are documented [v2 metrics guide][v2-http-metrics].
-
-### Server
-
-These metrics describe the status of the etcd server. In order to detect outages or problems for troubleshooting, the server metrics of every production etcd cluster should be closely monitored.
-
-All these metrics are prefixed with `etcd_server_`
-
-| Name                      | Description                                              | Type    |
-|---------------------------|----------------------------------------------------------|---------|
-| has_leader                | Whether or not a leader exists. 1 is existence, 0 is not.| Gauge   |
-| leader_changes_seen_total | The number of leader changes seen.                       | Counter |
-| proposals_committed_total | The total number of consensus proposals committed.       | Gauge   |
-| proposals_applied_total   | The total number of consensus proposals applied.         | Gauge   |
-| proposals_pending         | The current number of pending proposals.                 | Gauge   |
-| proposals_failed_total    | The total number of failed proposals seen.               | Counter |
-
-`has_leader` indicates whether the member has a leader. If a member does not have a leader, it is
-totally unavailable. If all the members in the cluster do not have any leader, the entire cluster
-is totally unavailable.
-
-`leader_changes_seen_total` counts the number of leader changes the member has seen since its start. Rapid leadership changes impact the performance of etcd significantly. It also signals that the leader is unstable, perhaps due to network connectivity issues or excessive load hitting the etcd cluster.
-
-`proposals_committed_total` records the total number of consensus proposals committed. This gauge should increase over time if the cluster is healthy. Several healthy members of an etcd cluster may have different total committed proposals at once. This discrepancy may be due to recovering from peers after starting, lagging behind the leader, or being the leader and therefore having the most commits. It is important to monitor this metric across all the members in the cluster; a consistently large lag between a single member and its leader indicates that member is slow or unhealthy.
-
-`proposals_applied_total` records the total number of consensus proposals applied. The etcd server applies every committed proposal asynchronously. The difference between `proposals_committed_total` and `proposals_applied_total` should usually be small (within a few thousands even under high load). If the difference between them continues to rise, it indicates that the etcd server is overloaded. This might happen when applying expensive queries like heavy range queries or large txn operations.
-
-`proposals_pending` indicates how many proposals are queued to commit. Rising pending proposals suggests there is a high client load or the member cannot commit proposals.
-
-`proposals_failed_total` are normally related to two issues: temporary failures related to a leader election or longer downtime caused by a loss of quorum in the cluster.
-
-### Disk
-
-These metrics describe the status of the disk operations.
-
-All these metrics are prefixed with `etcd_disk_`.
-
-| Name                               | Description                                           | Type      |
-|------------------------------------|-------------------------------------------------------|-----------|
-| wal_fsync_duration_seconds         | The latency distributions of fsync called by wal      | Histogram |
-| backend_commit_duration_seconds    | The latency distributions of commit called by backend.| Histogram |
-
-A `wal_fsync` is called when etcd persists its log entries to disk before applying them.
-
-A `backend_commit` is called when etcd commits an incremental snapshot of its most recent changes to disk.
-
-High disk operation latencies (`wal_fsync_duration_seconds` or `backend_commit_duration_seconds`) often indicate disk issues. It may cause high request latency or make the cluster unstable.
-
-### Network
-
-These metrics describe the status of the network.
-
-All these metrics are prefixed with `etcd_network_`
-
-| Name                      | Description                                                        | Type          |
-|---------------------------|--------------------------------------------------------------------|---------------|
-| peer_sent_bytes_total           | The total number of bytes sent to the peer with ID `To`.         | Counter(To)   |
-| peer_received_bytes_total       | The total number of bytes received from the peer with ID `From`. | Counter(From) |
-| peer_sent_failures_total        | The total number of send failures from the peer with ID `To`.         | Counter(To)   |
-| peer_received_failures_total    | The total number of receive failures from the peer with ID `From`. | Counter(From) |
-| peer_round_trip_time_seconds    | Round-Trip-Time histogram between peers.                         | Histogram(To) |
-| client_grpc_sent_bytes_total    | The total number of bytes sent to grpc clients.                  | Counter   |
-| client_grpc_received_bytes_total| The total number of bytes received to grpc clients.              | Counter   |
-
-`peer_sent_bytes_total` counts the total number of bytes sent to a specific peer. Usually the leader member sends more data than other members since it is responsible for transmitting replicated data.
-
-`peer_received_bytes_total` counts the total number of bytes received from a specific peer. Usually follower members receive data only from the leader member.
-
-### gRPC requests
-
-These metrics are exposed via [go-grpc-prometheus][go-grpc-prometheus].
-
-## etcd_debugging namespace metrics
-
-The metrics under the `etcd_debugging` prefix are for debugging. They are very implementation dependent and volatile. They might be changed or removed without any warning in new etcd releases. Some of the metrics might be moved to the `etcd` prefix when they become more stable.
-
-
-### Snapshot
-
-| Name                                       | Description                                                | Type      |
-|--------------------------------------------|------------------------------------------------------------|-----------|
-| snapshot_save_total_duration_seconds      | The total latency distributions of save called by snapshot | Histogram |
-
-Abnormally high snapshot duration (`snapshot_save_total_duration_seconds`) indicates disk issues and might cause the cluster to be unstable.
-
-## Prometheus supplied metrics
-
-The Prometheus client library provides a number of metrics under the `go` and `process` namespaces. There are a few that are particularly interesting.
-
-| Name                              | Description                                | Type         |
-|-----------------------------------|--------------------------------------------|--------------|
-| process_open_fds                  | Number of open file descriptors.           | Gauge        |
-| process_max_fds                   | Maximum number of open file descriptors.   | Gauge        |
-
-Heavy file descriptor (`process_open_fds`) usage (i.e., near the process's file descriptor limit, `process_max_fds`) indicates a potential file descriptor exhaustion issue. If the file descriptors are exhausted, etcd may panic because it cannot create new WAL files.
-
-[glossary-proposal]: learning/glossary.md#proposal
-[prometheus]: http://prometheus.io/
-[prometheus-getting-started]: http://prometheus.io/docs/introduction/getting_started/
-[prometheus-naming]: http://prometheus.io/docs/practices/naming/
-[v2-http-metrics]: v2/metrics.md#http-requests
-[go-grpc-prometheus]: https://github.com/grpc-ecosystem/go-grpc-prometheus

Documentation/metrics/latest

@@ -1,975 +0,0 @@
-# server version: etcd_server_version{server_version="3.3.0+git"}
-
-# name: "etcd_debugging_disk_backend_commit_rebalance_duration_seconds"
-# description: "The latency distributions of commit.rebalance called by bboltdb backend."
-# type: "histogram"
-etcd_debugging_disk_backend_commit_rebalance_duration_seconds_bucket{le="0.001"}
-etcd_debugging_disk_backend_commit_rebalance_duration_seconds_bucket{le="0.002"}
-etcd_debugging_disk_backend_commit_rebalance_duration_seconds_bucket{le="0.004"}
-etcd_debugging_disk_backend_commit_rebalance_duration_seconds_bucket{le="0.008"}
-etcd_debugging_disk_backend_commit_rebalance_duration_seconds_bucket{le="0.016"}
-etcd_debugging_disk_backend_commit_rebalance_duration_seconds_bucket{le="0.032"}
-etcd_debugging_disk_backend_commit_rebalance_duration_seconds_bucket{le="0.064"}
-etcd_debugging_disk_backend_commit_rebalance_duration_seconds_bucket{le="0.128"}
-etcd_debugging_disk_backend_commit_rebalance_duration_seconds_bucket{le="0.256"}
-etcd_debugging_disk_backend_commit_rebalance_duration_seconds_bucket{le="0.512"}
-etcd_debugging_disk_backend_commit_rebalance_duration_seconds_bucket{le="1.024"}
-etcd_debugging_disk_backend_commit_rebalance_duration_seconds_bucket{le="2.048"}
-etcd_debugging_disk_backend_commit_rebalance_duration_seconds_bucket{le="4.096"}
-etcd_debugging_disk_backend_commit_rebalance_duration_seconds_bucket{le="8.192"}
-etcd_debugging_disk_backend_commit_rebalance_duration_seconds_bucket{le="+Inf"}
-etcd_debugging_disk_backend_commit_rebalance_duration_seconds_sum
-etcd_debugging_disk_backend_commit_rebalance_duration_seconds_count
-
-# name: "etcd_debugging_disk_backend_commit_spill_duration_seconds"
-# description: "The latency distributions of commit.spill called by bboltdb backend."
-# type: "histogram"
-etcd_debugging_disk_backend_commit_spill_duration_seconds_bucket{le="0.001"}
-etcd_debugging_disk_backend_commit_spill_duration_seconds_bucket{le="0.002"}
-etcd_debugging_disk_backend_commit_spill_duration_seconds_bucket{le="0.004"}
-etcd_debugging_disk_backend_commit_spill_duration_seconds_bucket{le="0.008"}
-etcd_debugging_disk_backend_commit_spill_duration_seconds_bucket{le="0.016"}
-etcd_debugging_disk_backend_commit_spill_duration_seconds_bucket{le="0.032"}
-etcd_debugging_disk_backend_commit_spill_duration_seconds_bucket{le="0.064"}
-etcd_debugging_disk_backend_commit_spill_duration_seconds_bucket{le="0.128"}
-etcd_debugging_disk_backend_commit_spill_duration_seconds_bucket{le="0.256"}
-etcd_debugging_disk_backend_commit_spill_duration_seconds_bucket{le="0.512"}
-etcd_debugging_disk_backend_commit_spill_duration_seconds_bucket{le="1.024"}
-etcd_debugging_disk_backend_commit_spill_duration_seconds_bucket{le="2.048"}
-etcd_debugging_disk_backend_commit_spill_duration_seconds_bucket{le="4.096"}
-etcd_debugging_disk_backend_commit_spill_duration_seconds_bucket{le="8.192"}
-etcd_debugging_disk_backend_commit_spill_duration_seconds_bucket{le="+Inf"}
-etcd_debugging_disk_backend_commit_spill_duration_seconds_sum
-etcd_debugging_disk_backend_commit_spill_duration_seconds_count
-
-# name: "etcd_debugging_disk_backend_commit_write_duration_seconds"
-# description: "The latency distributions of commit.write called by bboltdb backend."
-# type: "histogram"
-etcd_debugging_disk_backend_commit_write_duration_seconds_bucket{le="0.001"}
-etcd_debugging_disk_backend_commit_write_duration_seconds_bucket{le="0.002"}
-etcd_debugging_disk_backend_commit_write_duration_seconds_bucket{le="0.004"}
-etcd_debugging_disk_backend_commit_write_duration_seconds_bucket{le="0.008"}
-etcd_debugging_disk_backend_commit_write_duration_seconds_bucket{le="0.016"}
-etcd_debugging_disk_backend_commit_write_duration_seconds_bucket{le="0.032"}
-etcd_debugging_disk_backend_commit_write_duration_seconds_bucket{le="0.064"}
-etcd_debugging_disk_backend_commit_write_duration_seconds_bucket{le="0.128"}
-etcd_debugging_disk_backend_commit_write_duration_seconds_bucket{le="0.256"}
-etcd_debugging_disk_backend_commit_write_duration_seconds_bucket{le="0.512"}
-etcd_debugging_disk_backend_commit_write_duration_seconds_bucket{le="1.024"}
-etcd_debugging_disk_backend_commit_write_duration_seconds_bucket{le="2.048"}
-etcd_debugging_disk_backend_commit_write_duration_seconds_bucket{le="4.096"}
-etcd_debugging_disk_backend_commit_write_duration_seconds_bucket{le="8.192"}
-etcd_debugging_disk_backend_commit_write_duration_seconds_bucket{le="+Inf"}
-etcd_debugging_disk_backend_commit_write_duration_seconds_sum
-etcd_debugging_disk_backend_commit_write_duration_seconds_count
-
-# name: "etcd_debugging_lease_granted_total"
-# description: "The total number of granted leases."
-# type: "counter"
-etcd_debugging_lease_granted_total
-
-# name: "etcd_debugging_lease_renewed_total"
-# description: "The number of renewed leases seen by the leader."
-# type: "counter"
-etcd_debugging_lease_renewed_total
-
-# name: "etcd_debugging_lease_revoked_total"
-# description: "The total number of revoked leases."
-# type: "counter"
-etcd_debugging_lease_revoked_total
-
-# name: "etcd_debugging_lease_ttl_total"
-# description: "Bucketed histogram of lease TTLs."
-# type: "histogram"
-etcd_debugging_lease_ttl_total_bucket{le="1"}
-etcd_debugging_lease_ttl_total_bucket{le="2"}
-etcd_debugging_lease_ttl_total_bucket{le="4"}
-etcd_debugging_lease_ttl_total_bucket{le="8"}
-etcd_debugging_lease_ttl_total_bucket{le="16"}
-etcd_debugging_lease_ttl_total_bucket{le="32"}
-etcd_debugging_lease_ttl_total_bucket{le="64"}
-etcd_debugging_lease_ttl_total_bucket{le="128"}
-etcd_debugging_lease_ttl_total_bucket{le="256"}
-etcd_debugging_lease_ttl_total_bucket{le="512"}
-etcd_debugging_lease_ttl_total_bucket{le="1024"}
-etcd_debugging_lease_ttl_total_bucket{le="2048"}
-etcd_debugging_lease_ttl_total_bucket{le="4096"}
-etcd_debugging_lease_ttl_total_bucket{le="8192"}
-etcd_debugging_lease_ttl_total_bucket{le="16384"}
-etcd_debugging_lease_ttl_total_bucket{le="32768"}
-etcd_debugging_lease_ttl_total_bucket{le="65536"}
-etcd_debugging_lease_ttl_total_bucket{le="131072"}
-etcd_debugging_lease_ttl_total_bucket{le="262144"}
-etcd_debugging_lease_ttl_total_bucket{le="524288"}
-etcd_debugging_lease_ttl_total_bucket{le="1.048576e+06"}
-etcd_debugging_lease_ttl_total_bucket{le="2.097152e+06"}
-etcd_debugging_lease_ttl_total_bucket{le="4.194304e+06"}
-etcd_debugging_lease_ttl_total_bucket{le="8.388608e+06"}
-etcd_debugging_lease_ttl_total_bucket{le="+Inf"}
-etcd_debugging_lease_ttl_total_sum
-etcd_debugging_lease_ttl_total_count
-
-# name: "etcd_debugging_mvcc_db_compaction_keys_total"
-# description: "Total number of db keys compacted."
-# type: "counter"
-etcd_debugging_mvcc_db_compaction_keys_total
-
-# name: "etcd_debugging_mvcc_db_compaction_pause_duration_milliseconds"
-# description: "Bucketed histogram of db compaction pause duration."
-# type: "histogram"
-etcd_debugging_mvcc_db_compaction_pause_duration_milliseconds_bucket{le="1"}
-etcd_debugging_mvcc_db_compaction_pause_duration_milliseconds_bucket{le="2"}
-etcd_debugging_mvcc_db_compaction_pause_duration_milliseconds_bucket{le="4"}
-etcd_debugging_mvcc_db_compaction_pause_duration_milliseconds_bucket{le="8"}
-etcd_debugging_mvcc_db_compaction_pause_duration_milliseconds_bucket{le="16"}
-etcd_debugging_mvcc_db_compaction_pause_duration_milliseconds_bucket{le="32"}
-etcd_debugging_mvcc_db_compaction_pause_duration_milliseconds_bucket{le="64"}
-etcd_debugging_mvcc_db_compaction_pause_duration_milliseconds_bucket{le="128"}
-etcd_debugging_mvcc_db_compaction_pause_duration_milliseconds_bucket{le="256"}
-etcd_debugging_mvcc_db_compaction_pause_duration_milliseconds_bucket{le="512"}
-etcd_debugging_mvcc_db_compaction_pause_duration_milliseconds_bucket{le="1024"}
-etcd_debugging_mvcc_db_compaction_pause_duration_milliseconds_bucket{le="2048"}
-etcd_debugging_mvcc_db_compaction_pause_duration_milliseconds_bucket{le="4096"}
-etcd_debugging_mvcc_db_compaction_pause_duration_milliseconds_bucket{le="+Inf"}
-etcd_debugging_mvcc_db_compaction_pause_duration_milliseconds_sum
-etcd_debugging_mvcc_db_compaction_pause_duration_milliseconds_count
-
-# name: "etcd_debugging_mvcc_db_compaction_total_duration_milliseconds"
-# description: "Bucketed histogram of db compaction total duration."
-# type: "histogram"
-etcd_debugging_mvcc_db_compaction_total_duration_milliseconds_bucket{le="100"}
-etcd_debugging_mvcc_db_compaction_total_duration_milliseconds_bucket{le="200"}
-etcd_debugging_mvcc_db_compaction_total_duration_milliseconds_bucket{le="400"}
-etcd_debugging_mvcc_db_compaction_total_duration_milliseconds_bucket{le="800"}
-etcd_debugging_mvcc_db_compaction_total_duration_milliseconds_bucket{le="1600"}
-etcd_debugging_mvcc_db_compaction_total_duration_milliseconds_bucket{le="3200"}
-etcd_debugging_mvcc_db_compaction_total_duration_milliseconds_bucket{le="6400"}
-etcd_debugging_mvcc_db_compaction_total_duration_milliseconds_bucket{le="12800"}
-etcd_debugging_mvcc_db_compaction_total_duration_milliseconds_bucket{le="25600"}
-etcd_debugging_mvcc_db_compaction_total_duration_milliseconds_bucket{le="51200"}
-etcd_debugging_mvcc_db_compaction_total_duration_milliseconds_bucket{le="102400"}
-etcd_debugging_mvcc_db_compaction_total_duration_milliseconds_bucket{le="204800"}
-etcd_debugging_mvcc_db_compaction_total_duration_milliseconds_bucket{le="409600"}
-etcd_debugging_mvcc_db_compaction_total_duration_milliseconds_bucket{le="819200"}
-etcd_debugging_mvcc_db_compaction_total_duration_milliseconds_bucket{le="+Inf"}
-etcd_debugging_mvcc_db_compaction_total_duration_milliseconds_sum
-etcd_debugging_mvcc_db_compaction_total_duration_milliseconds_count
-
-# name: "etcd_debugging_mvcc_db_total_size_in_bytes"
-# description: "Total size of the underlying database physically allocated in bytes."
-# type: "gauge"
-etcd_debugging_mvcc_db_total_size_in_bytes
-
-# name: "etcd_debugging_mvcc_delete_total"
-# description: "Total number of deletes seen by this member."
-# type: "counter"
-etcd_debugging_mvcc_delete_total
-
-# name: "etcd_debugging_mvcc_events_total"
-# description: "Total number of events sent by this member."
-# type: "counter"
-etcd_debugging_mvcc_events_total
-
-# name: "etcd_debugging_mvcc_index_compaction_pause_duration_milliseconds"
-# description: "Bucketed histogram of index compaction pause duration."
-# type: "histogram"
-etcd_debugging_mvcc_index_compaction_pause_duration_milliseconds_bucket{le="0.5"}
-etcd_debugging_mvcc_index_compaction_pause_duration_milliseconds_bucket{le="1"}
-etcd_debugging_mvcc_index_compaction_pause_duration_milliseconds_bucket{le="2"}
-etcd_debugging_mvcc_index_compaction_pause_duration_milliseconds_bucket{le="4"}
-etcd_debugging_mvcc_index_compaction_pause_duration_milliseconds_bucket{le="8"}
-etcd_debugging_mvcc_index_compaction_pause_duration_milliseconds_bucket{le="16"}
-etcd_debugging_mvcc_index_compaction_pause_duration_milliseconds_bucket{le="32"}
-etcd_debugging_mvcc_index_compaction_pause_duration_milliseconds_bucket{le="64"}
-etcd_debugging_mvcc_index_compaction_pause_duration_milliseconds_bucket{le="128"}
-etcd_debugging_mvcc_index_compaction_pause_duration_milliseconds_bucket{le="256"}
-etcd_debugging_mvcc_index_compaction_pause_duration_milliseconds_bucket{le="512"}
-etcd_debugging_mvcc_index_compaction_pause_duration_milliseconds_bucket{le="1024"}
-etcd_debugging_mvcc_index_compaction_pause_duration_milliseconds_bucket{le="2048"}
-etcd_debugging_mvcc_index_compaction_pause_duration_milliseconds_bucket{le="4096"}
-etcd_debugging_mvcc_index_compaction_pause_duration_milliseconds_bucket{le="+Inf"}
-etcd_debugging_mvcc_index_compaction_pause_duration_milliseconds_sum
-etcd_debugging_mvcc_index_compaction_pause_duration_milliseconds_count
-
-# name: "etcd_debugging_mvcc_keys_total"
-# description: "Total number of keys."
-# type: "gauge"
-etcd_debugging_mvcc_keys_total
-
-# name: "etcd_debugging_mvcc_pending_events_total"
-# description: "Total number of pending events to be sent."
-# type: "gauge"
-etcd_debugging_mvcc_pending_events_total
-
-# name: "etcd_debugging_mvcc_put_total"
-# description: "Total number of puts seen by this member."
-# type: "counter"
-etcd_debugging_mvcc_put_total
-
-# name: "etcd_debugging_mvcc_range_total"
-# description: "Total number of ranges seen by this member."
-# type: "counter"
-etcd_debugging_mvcc_range_total
-
-# name: "etcd_debugging_mvcc_slow_watcher_total"
-# description: "Total number of unsynced slow watchers."
-# type: "gauge"
-etcd_debugging_mvcc_slow_watcher_total
-
-# name: "etcd_debugging_mvcc_txn_total"
-# description: "Total number of txns seen by this member."
-# type: "counter"
-etcd_debugging_mvcc_txn_total
-
-# name: "etcd_debugging_mvcc_watch_stream_total"
-# description: "Total number of watch streams."
-# type: "gauge"
-etcd_debugging_mvcc_watch_stream_total
-
-# name: "etcd_debugging_mvcc_watcher_total"
-# description: "Total number of watchers."
-# type: "gauge"
-etcd_debugging_mvcc_watcher_total
-
-# name: "etcd_debugging_server_lease_expired_total"
-# description: "The total number of expired leases."
-# type: "counter"
-etcd_debugging_server_lease_expired_total
-
-# name: "etcd_debugging_snap_save_marshalling_duration_seconds"
-# description: "The marshalling cost distributions of save called by snapshot."
-# type: "histogram"
-etcd_debugging_snap_save_marshalling_duration_seconds_bucket{le="0.001"}
-etcd_debugging_snap_save_marshalling_duration_seconds_bucket{le="0.002"}
-etcd_debugging_snap_save_marshalling_duration_seconds_bucket{le="0.004"}
-etcd_debugging_snap_save_marshalling_duration_seconds_bucket{le="0.008"}
-etcd_debugging_snap_save_marshalling_duration_seconds_bucket{le="0.016"}
-etcd_debugging_snap_save_marshalling_duration_seconds_bucket{le="0.032"}
-etcd_debugging_snap_save_marshalling_duration_seconds_bucket{le="0.064"}
-etcd_debugging_snap_save_marshalling_duration_seconds_bucket{le="0.128"}
-etcd_debugging_snap_save_marshalling_duration_seconds_bucket{le="0.256"}
-etcd_debugging_snap_save_marshalling_duration_seconds_bucket{le="0.512"}
-etcd_debugging_snap_save_marshalling_duration_seconds_bucket{le="1.024"}
-etcd_debugging_snap_save_marshalling_duration_seconds_bucket{le="2.048"}
-etcd_debugging_snap_save_marshalling_duration_seconds_bucket{le="4.096"}
-etcd_debugging_snap_save_marshalling_duration_seconds_bucket{le="8.192"}
-etcd_debugging_snap_save_marshalling_duration_seconds_bucket{le="+Inf"}
-etcd_debugging_snap_save_marshalling_duration_seconds_sum
-etcd_debugging_snap_save_marshalling_duration_seconds_count
-
-# name: "etcd_debugging_snap_save_total_duration_seconds"
-# description: "The total latency distributions of save called by snapshot."
-# type: "histogram"
-etcd_debugging_snap_save_total_duration_seconds_bucket{le="0.001"}
-etcd_debugging_snap_save_total_duration_seconds_bucket{le="0.002"}
-etcd_debugging_snap_save_total_duration_seconds_bucket{le="0.004"}
-etcd_debugging_snap_save_total_duration_seconds_bucket{le="0.008"}
-etcd_debugging_snap_save_total_duration_seconds_bucket{le="0.016"}
-etcd_debugging_snap_save_total_duration_seconds_bucket{le="0.032"}
-etcd_debugging_snap_save_total_duration_seconds_bucket{le="0.064"}
-etcd_debugging_snap_save_total_duration_seconds_bucket{le="0.128"}
-etcd_debugging_snap_save_total_duration_seconds_bucket{le="0.256"}
-etcd_debugging_snap_save_total_duration_seconds_bucket{le="0.512"}
-etcd_debugging_snap_save_total_duration_seconds_bucket{le="1.024"}
-etcd_debugging_snap_save_total_duration_seconds_bucket{le="2.048"}
-etcd_debugging_snap_save_total_duration_seconds_bucket{le="4.096"}
-etcd_debugging_snap_save_total_duration_seconds_bucket{le="8.192"}
-etcd_debugging_snap_save_total_duration_seconds_bucket{le="+Inf"}
-etcd_debugging_snap_save_total_duration_seconds_sum
-etcd_debugging_snap_save_total_duration_seconds_count
-
-# name: "etcd_debugging_store_expires_total"
-# description: "Total number of expired keys."
-# type: "counter"
-etcd_debugging_store_expires_total
-
-# name: "etcd_debugging_store_reads_total"
-# description: "Total number of reads action by (get/getRecursive), local to this member."
-# type: "counter"
-etcd_debugging_store_reads_total{action="getRecursive"}
-
-# name: "etcd_debugging_store_watch_requests_total"
-# description: "Total number of incoming watch requests (new or reestablished)."
-# type: "counter"
-etcd_debugging_store_watch_requests_total
-
-# name: "etcd_debugging_store_watchers"
-# description: "Count of currently active watchers."
-# type: "gauge"
-etcd_debugging_store_watchers
-
-# name: "etcd_debugging_store_writes_total"
-# description: "Total number of writes (e.g. set/compareAndDelete) seen by this member."
-# type: "counter"
-etcd_debugging_store_writes_total{action="create"}
-etcd_debugging_store_writes_total{action="set"}
-
-# name: "etcd_disk_backend_commit_duration_seconds"
-# description: "The latency distributions of commit called by backend."
-# type: "histogram"
-etcd_disk_backend_commit_duration_seconds_bucket{le="0.001"}
-etcd_disk_backend_commit_duration_seconds_bucket{le="0.002"}
-etcd_disk_backend_commit_duration_seconds_bucket{le="0.004"}
-etcd_disk_backend_commit_duration_seconds_bucket{le="0.008"}
-etcd_disk_backend_commit_duration_seconds_bucket{le="0.016"}
-etcd_disk_backend_commit_duration_seconds_bucket{le="0.032"}
-etcd_disk_backend_commit_duration_seconds_bucket{le="0.064"}
-etcd_disk_backend_commit_duration_seconds_bucket{le="0.128"}
-etcd_disk_backend_commit_duration_seconds_bucket{le="0.256"}
-etcd_disk_backend_commit_duration_seconds_bucket{le="0.512"}
-etcd_disk_backend_commit_duration_seconds_bucket{le="1.024"}
-etcd_disk_backend_commit_duration_seconds_bucket{le="2.048"}
-etcd_disk_backend_commit_duration_seconds_bucket{le="4.096"}
-etcd_disk_backend_commit_duration_seconds_bucket{le="8.192"}
-etcd_disk_backend_commit_duration_seconds_bucket{le="+Inf"}
-etcd_disk_backend_commit_duration_seconds_sum
-etcd_disk_backend_commit_duration_seconds_count
-
-# name: "etcd_disk_backend_defrag_duration_seconds"
-# description: "The latency distribution of backend defragmentation."
-# type: "histogram"
-etcd_disk_backend_defrag_duration_seconds_bucket{le="0.1"}
-etcd_disk_backend_defrag_duration_seconds_bucket{le="0.2"}
-etcd_disk_backend_defrag_duration_seconds_bucket{le="0.4"}
-etcd_disk_backend_defrag_duration_seconds_bucket{le="0.8"}
-etcd_disk_backend_defrag_duration_seconds_bucket{le="1.6"}
-etcd_disk_backend_defrag_duration_seconds_bucket{le="3.2"}
-etcd_disk_backend_defrag_duration_seconds_bucket{le="6.4"}
-etcd_disk_backend_defrag_duration_seconds_bucket{le="12.8"}
-etcd_disk_backend_defrag_duration_seconds_bucket{le="25.6"}
-etcd_disk_backend_defrag_duration_seconds_bucket{le="51.2"}
-etcd_disk_backend_defrag_duration_seconds_bucket{le="102.4"}
-etcd_disk_backend_defrag_duration_seconds_bucket{le="204.8"}
-etcd_disk_backend_defrag_duration_seconds_bucket{le="409.6"}
-etcd_disk_backend_defrag_duration_seconds_bucket{le="+Inf"}
-etcd_disk_backend_defrag_duration_seconds_sum
-etcd_disk_backend_defrag_duration_seconds_count
-
-# name: "etcd_disk_backend_snapshot_duration_seconds"
-# description: "The latency distribution of backend snapshots."
-# type: "histogram"
-etcd_disk_backend_snapshot_duration_seconds_bucket{le="0.01"}
-etcd_disk_backend_snapshot_duration_seconds_bucket{le="0.02"}
-etcd_disk_backend_snapshot_duration_seconds_bucket{le="0.04"}
-etcd_disk_backend_snapshot_duration_seconds_bucket{le="0.08"}
-etcd_disk_backend_snapshot_duration_seconds_bucket{le="0.16"}
-etcd_disk_backend_snapshot_duration_seconds_bucket{le="0.32"}
-etcd_disk_backend_snapshot_duration_seconds_bucket{le="0.64"}
-etcd_disk_backend_snapshot_duration_seconds_bucket{le="1.28"}
-etcd_disk_backend_snapshot_duration_seconds_bucket{le="2.56"}
-etcd_disk_backend_snapshot_duration_seconds_bucket{le="5.12"}
-etcd_disk_backend_snapshot_duration_seconds_bucket{le="10.24"}
-etcd_disk_backend_snapshot_duration_seconds_bucket{le="20.48"}
-etcd_disk_backend_snapshot_duration_seconds_bucket{le="40.96"}
-etcd_disk_backend_snapshot_duration_seconds_bucket{le="81.92"}
-etcd_disk_backend_snapshot_duration_seconds_bucket{le="163.84"}
-etcd_disk_backend_snapshot_duration_seconds_bucket{le="327.68"}
-etcd_disk_backend_snapshot_duration_seconds_bucket{le="655.36"}
-etcd_disk_backend_snapshot_duration_seconds_bucket{le="+Inf"}
-etcd_disk_backend_snapshot_duration_seconds_sum
-etcd_disk_backend_snapshot_duration_seconds_count
-
-# name: "etcd_disk_wal_fsync_duration_seconds"
-# description: "The latency distributions of fsync called by WAL."
-# type: "histogram"
-etcd_disk_wal_fsync_duration_seconds_bucket{le="0.001"}
-etcd_disk_wal_fsync_duration_seconds_bucket{le="0.002"}
-etcd_disk_wal_fsync_duration_seconds_bucket{le="0.004"}
-etcd_disk_wal_fsync_duration_seconds_bucket{le="0.008"}
-etcd_disk_wal_fsync_duration_seconds_bucket{le="0.016"}
-etcd_disk_wal_fsync_duration_seconds_bucket{le="0.032"}
-etcd_disk_wal_fsync_duration_seconds_bucket{le="0.064"}
-etcd_disk_wal_fsync_duration_seconds_bucket{le="0.128"}
-etcd_disk_wal_fsync_duration_seconds_bucket{le="0.256"}
-etcd_disk_wal_fsync_duration_seconds_bucket{le="0.512"}
-etcd_disk_wal_fsync_duration_seconds_bucket{le="1.024"}
-etcd_disk_wal_fsync_duration_seconds_bucket{le="2.048"}
-etcd_disk_wal_fsync_duration_seconds_bucket{le="4.096"}
-etcd_disk_wal_fsync_duration_seconds_bucket{le="8.192"}
-etcd_disk_wal_fsync_duration_seconds_bucket{le="+Inf"}
-etcd_disk_wal_fsync_duration_seconds_sum
-etcd_disk_wal_fsync_duration_seconds_count
-
-# name: "etcd_mvcc_db_total_size_in_bytes"
-# description: "Total size of the underlying database physically allocated in bytes."
-# type: "gauge"
-etcd_mvcc_db_total_size_in_bytes
-
-# name: "etcd_mvcc_db_total_size_in_use_in_bytes"
-# description: "Total size of the underlying database logically in use in bytes."
-# type: "gauge"
-etcd_mvcc_db_total_size_in_use_in_bytes
-
-# name: "etcd_mvcc_hash_duration_seconds"
-# description: "The latency distribution of storage hash operation."
-# type: "histogram"
-etcd_mvcc_hash_duration_seconds_bucket{le="0.01"}
-etcd_mvcc_hash_duration_seconds_bucket{le="0.02"}
-etcd_mvcc_hash_duration_seconds_bucket{le="0.04"}
-etcd_mvcc_hash_duration_seconds_bucket{le="0.08"}
-etcd_mvcc_hash_duration_seconds_bucket{le="0.16"}
-etcd_mvcc_hash_duration_seconds_bucket{le="0.32"}
-etcd_mvcc_hash_duration_seconds_bucket{le="0.64"}
-etcd_mvcc_hash_duration_seconds_bucket{le="1.28"}
-etcd_mvcc_hash_duration_seconds_bucket{le="2.56"}
-etcd_mvcc_hash_duration_seconds_bucket{le="5.12"}
-etcd_mvcc_hash_duration_seconds_bucket{le="10.24"}
-etcd_mvcc_hash_duration_seconds_bucket{le="20.48"}
-etcd_mvcc_hash_duration_seconds_bucket{le="40.96"}
-etcd_mvcc_hash_duration_seconds_bucket{le="81.92"}
-etcd_mvcc_hash_duration_seconds_bucket{le="163.84"}
-etcd_mvcc_hash_duration_seconds_bucket{le="+Inf"}
-etcd_mvcc_hash_duration_seconds_sum
-etcd_mvcc_hash_duration_seconds_count
-
-# name: "etcd_mvcc_hash_rev_duration_seconds"
-# description: "The latency distribution of storage hash by revision operation."
-# type: "histogram"
-etcd_mvcc_hash_rev_duration_seconds_bucket{le="0.01"}
-etcd_mvcc_hash_rev_duration_seconds_bucket{le="0.02"}
-etcd_mvcc_hash_rev_duration_seconds_bucket{le="0.04"}
-etcd_mvcc_hash_rev_duration_seconds_bucket{le="0.08"}
-etcd_mvcc_hash_rev_duration_seconds_bucket{le="0.16"}
-etcd_mvcc_hash_rev_duration_seconds_bucket{le="0.32"}
-etcd_mvcc_hash_rev_duration_seconds_bucket{le="0.64"}
-etcd_mvcc_hash_rev_duration_seconds_bucket{le="1.28"}
-etcd_mvcc_hash_rev_duration_seconds_bucket{le="2.56"}
-etcd_mvcc_hash_rev_duration_seconds_bucket{le="5.12"}
-etcd_mvcc_hash_rev_duration_seconds_bucket{le="10.24"}
-etcd_mvcc_hash_rev_duration_seconds_bucket{le="20.48"}
-etcd_mvcc_hash_rev_duration_seconds_bucket{le="40.96"}
-etcd_mvcc_hash_rev_duration_seconds_bucket{le="81.92"}
-etcd_mvcc_hash_rev_duration_seconds_bucket{le="163.84"}
-etcd_mvcc_hash_rev_duration_seconds_bucket{le="+Inf"}
-etcd_mvcc_hash_rev_duration_seconds_sum
-etcd_mvcc_hash_rev_duration_seconds_count
-
-# name: "etcd_network_active_peers"
-# description: "The current number of active peer connections."
-# type: "gauge"
-etcd_network_active_peers{Local="LOCAL_NODE_ID",Remote="REMOTE_PEER_NODE_ID"}
-
-# name: "etcd_network_client_grpc_received_bytes_total"
-# description: "The total number of bytes received from grpc clients."
-# type: "counter"
-etcd_network_client_grpc_received_bytes_total
-
-# name: "etcd_network_client_grpc_sent_bytes_total"
-# description: "The total number of bytes sent to grpc clients."
-# type: "counter"
-etcd_network_client_grpc_sent_bytes_total
-
-# name: "etcd_network_peer_received_bytes_total"
-# description: "The total number of bytes received from peers."
-# type: "counter"
-etcd_network_peer_received_bytes_total{From="REMOTE_PEER_NODE_ID"}
-
-# name: "etcd_network_peer_round_trip_time_seconds"
-# description: "Round-Trip-Time histogram between peers"
-# type: "histogram"
-etcd_network_peer_round_trip_time_seconds_bucket{To="REMOTE_PEER_NODE_ID",le="+Inf"}
-etcd_network_peer_round_trip_time_seconds_bucket{To="REMOTE_PEER_NODE_ID",le="0.0001"}
-etcd_network_peer_round_trip_time_seconds_bucket{To="REMOTE_PEER_NODE_ID",le="0.0002"}
-etcd_network_peer_round_trip_time_seconds_bucket{To="REMOTE_PEER_NODE_ID",le="0.0004"}
-etcd_network_peer_round_trip_time_seconds_bucket{To="REMOTE_PEER_NODE_ID",le="0.0008"}
-etcd_network_peer_round_trip_time_seconds_bucket{To="REMOTE_PEER_NODE_ID",le="0.0016"}
-etcd_network_peer_round_trip_time_seconds_bucket{To="REMOTE_PEER_NODE_ID",le="0.0032"}
-etcd_network_peer_round_trip_time_seconds_bucket{To="REMOTE_PEER_NODE_ID",le="0.0064"}
-etcd_network_peer_round_trip_time_seconds_bucket{To="REMOTE_PEER_NODE_ID",le="0.0128"}
-etcd_network_peer_round_trip_time_seconds_bucket{To="REMOTE_PEER_NODE_ID",le="0.0256"}
-etcd_network_peer_round_trip_time_seconds_bucket{To="REMOTE_PEER_NODE_ID",le="0.0512"}
-etcd_network_peer_round_trip_time_seconds_bucket{To="REMOTE_PEER_NODE_ID",le="0.1024"}
-etcd_network_peer_round_trip_time_seconds_bucket{To="REMOTE_PEER_NODE_ID",le="0.2048"}
-etcd_network_peer_round_trip_time_seconds_bucket{To="REMOTE_PEER_NODE_ID",le="0.4096"}
-etcd_network_peer_round_trip_time_seconds_bucket{To="REMOTE_PEER_NODE_ID",le="0.8192"}
-etcd_network_peer_round_trip_time_seconds_bucket{To="REMOTE_PEER_NODE_ID",le="1.6384"}
-etcd_network_peer_round_trip_time_seconds_bucket{To="REMOTE_PEER_NODE_ID",le="3.2768"}
-etcd_network_peer_round_trip_time_seconds_count{To="REMOTE_PEER_NODE_ID"}
-etcd_network_peer_round_trip_time_seconds_sum{To="REMOTE_PEER_NODE_ID"}
-
-# name: "etcd_network_peer_sent_bytes_total"
-# description: "The total number of bytes sent to peers."
-# type: "counter"
-etcd_network_peer_sent_bytes_total{To="REMOTE_PEER_NODE_ID"}
-
-# name: "etcd_server_go_version"
-# description: "Which Go version server is running with. 1 for 'server_go_version' label with current version."
-# type: "gauge"
-etcd_server_go_version{server_go_version="go1.11.1"}
-
-# name: "etcd_server_has_leader"
-# description: "Whether or not a leader exists. 1 is existence, 0 is not."
-# type: "gauge"
-etcd_server_has_leader
-
-# name: "etcd_server_health_failures"
-# description: "The total number of failed health checks"
-# type: "counter"
-etcd_server_health_failures
-
-# name: "etcd_server_health_success"
-# description: "The total number of successful health checks"
-# type: "counter"
-etcd_server_health_success
-
-# name: "etcd_server_heartbeat_send_failures_total"
-# description: "The total number of leader heartbeat send failures (likely overloaded from slow disk)."
-# type: "counter"
-etcd_server_heartbeat_send_failures_total
-
-# name: "etcd_server_id"
-# description: "Server or member ID in hexadecimal format. 1 for 'server_id' label with current ID."
-# type: "gauge"
-etcd_server_id{server_id="221ed218fa16d1fe"}
-etcd_server_id{server_id="3f1ca865609d428d"}
-
-# name: "etcd_server_is_leader"
-# description: "Whether or not this member is a leader. 1 if is, 0 otherwise."
-# type: "gauge"
-etcd_server_is_leader
-
-# name: "etcd_server_leader_changes_seen_total"
-# description: "The number of leader changes seen."
-# type: "counter"
-etcd_server_leader_changes_seen_total
-
-# name: "etcd_server_is_learner"
-# description: "Whether or not this member is a learner. 1 if is, 0 otherwise."
-# type: "gauge"
-etcd_server_is_learner
-
-# name: "etcd_server_learner_promote_failures"
-# description: "The total number of failed learner promotions (likely learner not ready) while this member is leader."
-# type: "counter"
-etcd_server_learner_promote_failures
-
-# name: "etcd_server_learner_promote_successes"
-# description: "The total number of successful learner promotions while this member is leader."
-# type: "counter"
-etcd_server_learner_promote_successes
-
-# name: "etcd_server_proposals_applied_total"
-# description: "The total number of consensus proposals applied."
-# type: "gauge"
-etcd_server_proposals_applied_total
-
-# name: "etcd_server_proposals_committed_total"
-# description: "The total number of consensus proposals committed."
-# type: "gauge"
-etcd_server_proposals_committed_total
-
-# name: "etcd_server_proposals_failed_total"
-# description: "The total number of failed proposals seen."
-# type: "counter"
-etcd_server_proposals_failed_total
-
-# name: "etcd_server_proposals_pending"
-# description: "The current number of pending proposals to commit."
-# type: "gauge"
-etcd_server_proposals_pending
-
-# name: "etcd_server_quota_backend_bytes"
-# description: "Current backend storage quota size in bytes."
-# type: "gauge"
-etcd_server_quota_backend_bytes
-
-# name: "etcd_server_read_indexes_failed_total"
-# description: "The total number of failed read indexes seen."
-# type: "counter"
-etcd_server_read_indexes_failed_total
-
-# name: "etcd_server_slow_apply_total"
-# description: "The total number of slow apply requests (likely overloaded from slow disk)."
-# type: "counter"
-etcd_server_slow_apply_total
-
-# name: "etcd_server_slow_read_indexes_total"
-# description: "The total number of pending read indexes not in sync with leader's or timed out read index requests."
-# type: "counter"
-etcd_server_slow_read_indexes_total
-
-# name: "etcd_server_version"
-# description: "Which version is running. 1 for 'server_version' label with current version."
-# type: "gauge"
-etcd_server_version{server_version="3.3.0+git"}
-
-# name: "etcd_snap_db_fsync_duration_seconds"
-# description: "The latency distributions of fsyncing .snap.db file"
-# type: "histogram"
-etcd_snap_db_fsync_duration_seconds_bucket{le="0.001"}
-etcd_snap_db_fsync_duration_seconds_bucket{le="0.002"}
-etcd_snap_db_fsync_duration_seconds_bucket{le="0.004"}
-etcd_snap_db_fsync_duration_seconds_bucket{le="0.008"}
-etcd_snap_db_fsync_duration_seconds_bucket{le="0.016"}
-etcd_snap_db_fsync_duration_seconds_bucket{le="0.032"}
-etcd_snap_db_fsync_duration_seconds_bucket{le="0.064"}
-etcd_snap_db_fsync_duration_seconds_bucket{le="0.128"}
-etcd_snap_db_fsync_duration_seconds_bucket{le="0.256"}
-etcd_snap_db_fsync_duration_seconds_bucket{le="0.512"}
-etcd_snap_db_fsync_duration_seconds_bucket{le="1.024"}
-etcd_snap_db_fsync_duration_seconds_bucket{le="2.048"}
-etcd_snap_db_fsync_duration_seconds_bucket{le="4.096"}
-etcd_snap_db_fsync_duration_seconds_bucket{le="8.192"}
-etcd_snap_db_fsync_duration_seconds_bucket{le="+Inf"}
-etcd_snap_db_fsync_duration_seconds_sum
-etcd_snap_db_fsync_duration_seconds_count
-
-# name: "etcd_snap_db_save_total_duration_seconds"
-# description: "The total latency distributions of v3 snapshot save"
-# type: "histogram"
-etcd_snap_db_save_total_duration_seconds_bucket{le="0.1"}
-etcd_snap_db_save_total_duration_seconds_bucket{le="0.2"}
-etcd_snap_db_save_total_duration_seconds_bucket{le="0.4"}
-etcd_snap_db_save_total_duration_seconds_bucket{le="0.8"}
-etcd_snap_db_save_total_duration_seconds_bucket{le="1.6"}
-etcd_snap_db_save_total_duration_seconds_bucket{le="3.2"}
-etcd_snap_db_save_total_duration_seconds_bucket{le="6.4"}
-etcd_snap_db_save_total_duration_seconds_bucket{le="12.8"}
-etcd_snap_db_save_total_duration_seconds_bucket{le="25.6"}
-etcd_snap_db_save_total_duration_seconds_bucket{le="51.2"}
-etcd_snap_db_save_total_duration_seconds_bucket{le="+Inf"}
-etcd_snap_db_save_total_duration_seconds_sum
-etcd_snap_db_save_total_duration_seconds_count
-
-# name: "etcd_snap_fsync_duration_seconds"
-# description: "The latency distributions of fsync called by snap."
-# type: "histogram"
-etcd_snap_fsync_duration_seconds_bucket{le="0.001"}
-etcd_snap_fsync_duration_seconds_bucket{le="0.002"}
-etcd_snap_fsync_duration_seconds_bucket{le="0.004"}
-etcd_snap_fsync_duration_seconds_bucket{le="0.008"}
-etcd_snap_fsync_duration_seconds_bucket{le="0.016"}
-etcd_snap_fsync_duration_seconds_bucket{le="0.032"}
-etcd_snap_fsync_duration_seconds_bucket{le="0.064"}
-etcd_snap_fsync_duration_seconds_bucket{le="0.128"}
-etcd_snap_fsync_duration_seconds_bucket{le="0.256"}
-etcd_snap_fsync_duration_seconds_bucket{le="0.512"}
-etcd_snap_fsync_duration_seconds_bucket{le="1.024"}
-etcd_snap_fsync_duration_seconds_bucket{le="2.048"}
-etcd_snap_fsync_duration_seconds_bucket{le="4.096"}
-etcd_snap_fsync_duration_seconds_bucket{le="8.192"}
-etcd_snap_fsync_duration_seconds_bucket{le="+Inf"}
-etcd_snap_fsync_duration_seconds_sum
-etcd_snap_fsync_duration_seconds_count
-
-# name: "go_gc_duration_seconds"
-# description: "A summary of the GC invocation durations."
-# type: "summary"
-go_gc_duration_seconds{quantile="0"}
-go_gc_duration_seconds{quantile="0.25"}
-go_gc_duration_seconds{quantile="0.5"}
-go_gc_duration_seconds{quantile="0.75"}
-go_gc_duration_seconds{quantile="1"}
-go_gc_duration_seconds_sum
-go_gc_duration_seconds_count
-
-# name: "go_goroutines"
-# description: "Number of goroutines that currently exist."
-# type: "gauge"
-go_goroutines
-
-# name: "go_memstats_alloc_bytes"
-# description: "Number of bytes allocated and still in use."
-# type: "gauge"
-go_memstats_alloc_bytes
-
-# name: "go_memstats_alloc_bytes_total"
-# description: "Total number of bytes allocated, even if freed."
-# type: "counter"
-go_memstats_alloc_bytes_total
-
-# name: "go_memstats_buck_hash_sys_bytes"
-# description: "Number of bytes used by the profiling bucket hash table."
-# type: "gauge"
-go_memstats_buck_hash_sys_bytes
-
-# name: "go_memstats_frees_total"
-# description: "Total number of frees."
-# type: "counter"
-go_memstats_frees_total
-
-# name: "go_memstats_gc_sys_bytes"
-# description: "Number of bytes used for garbage collection system metadata."
-# type: "gauge"
-go_memstats_gc_sys_bytes
-
-# name: "go_memstats_heap_alloc_bytes"
-# description: "Number of heap bytes allocated and still in use."
-# type: "gauge"
-go_memstats_heap_alloc_bytes
-
-# name: "go_memstats_heap_idle_bytes"
-# description: "Number of heap bytes waiting to be used."
-# type: "gauge"
-go_memstats_heap_idle_bytes
-
-# name: "go_memstats_heap_inuse_bytes"
-# description: "Number of heap bytes that are in use."
-# type: "gauge"
-go_memstats_heap_inuse_bytes
-
-# name: "go_memstats_heap_objects"
-# description: "Number of allocated objects."
-# type: "gauge"
-go_memstats_heap_objects
-
-# name: "go_memstats_heap_released_bytes_total"
-# description: "Total number of heap bytes released to OS."
-# type: "counter"
-go_memstats_heap_released_bytes_total
-
-# name: "go_memstats_heap_sys_bytes"
-# description: "Number of heap bytes obtained from system."
-# type: "gauge"
-go_memstats_heap_sys_bytes
-
-# name: "go_memstats_last_gc_time_seconds"
-# description: "Number of seconds since 1970 of last garbage collection."
-# type: "gauge"
-go_memstats_last_gc_time_seconds
-
-# name: "go_memstats_lookups_total"
-# description: "Total number of pointer lookups."
-# type: "counter"
-go_memstats_lookups_total
-
-# name: "go_memstats_mallocs_total"
-# description: "Total number of mallocs."
-# type: "counter"
-go_memstats_mallocs_total
-
-# name: "go_memstats_mcache_inuse_bytes"
-# description: "Number of bytes in use by mcache structures."
-# type: "gauge"
-go_memstats_mcache_inuse_bytes
-
-# name: "go_memstats_mcache_sys_bytes"
-# description: "Number of bytes used for mcache structures obtained from system."
-# type: "gauge"
-go_memstats_mcache_sys_bytes
-
-# name: "go_memstats_mspan_inuse_bytes"
-# description: "Number of bytes in use by mspan structures."
-# type: "gauge"
-go_memstats_mspan_inuse_bytes
-
-# name: "go_memstats_mspan_sys_bytes"
-# description: "Number of bytes used for mspan structures obtained from system."
-# type: "gauge"
-go_memstats_mspan_sys_bytes
-
-# name: "go_memstats_next_gc_bytes"
-# description: "Number of heap bytes when next garbage collection will take place."
-# type: "gauge"
-go_memstats_next_gc_bytes
-
-# name: "go_memstats_other_sys_bytes"
-# description: "Number of bytes used for other system allocations."
-# type: "gauge"
-go_memstats_other_sys_bytes
-
-# name: "go_memstats_stack_inuse_bytes"
-# description: "Number of bytes in use by the stack allocator."
-# type: "gauge"
-go_memstats_stack_inuse_bytes
-
-# name: "go_memstats_stack_sys_bytes"
-# description: "Number of bytes obtained from system for stack allocator."
-# type: "gauge"
-go_memstats_stack_sys_bytes
-
-# name: "go_memstats_sys_bytes"
-# description: "Number of bytes obtained by system. Sum of all system allocations."
-# type: "gauge"
-go_memstats_sys_bytes
-
-# name: "grpc_server_handled_total"
-# description: "Total number of RPCs completed on the server, regardless of success or failure."
-# type: "counter"
-# gRPC codes: 
-#  - "Aborted"
-#  - "AlreadyExists"
-#  - "Canceled"
-#  - "DataLoss"
-#  - "DeadlineExceeded"
-#  - "FailedPrecondition"
-#  - "Internal"
-#  - "InvalidArgument"
-#  - "NotFound"
-#  - "OK"
-#  - "OutOfRange"
-#  - "PermissionDenied"
-#  - "ResourceExhausted"
-#  - "Unauthenticated"
-#  - "Unavailable"
-#  - "Unimplemented"
-#  - "Unknown"
-grpc_server_handled_total{grpc_code="CODE",grpc_method="Alarm",grpc_service="etcdserverpb.Maintenance",grpc_type="unary"}
-grpc_server_handled_total{grpc_code="CODE",grpc_method="AuthDisable",grpc_service="etcdserverpb.Auth",grpc_type="unary"}
-grpc_server_handled_total{grpc_code="CODE",grpc_method="AuthEnable",grpc_service="etcdserverpb.Auth",grpc_type="unary"}
-grpc_server_handled_total{grpc_code="CODE",grpc_method="Authenticate",grpc_service="etcdserverpb.Auth",grpc_type="unary"}
-grpc_server_handled_total{grpc_code="CODE",grpc_method="Check",grpc_service="grpc.health.v1.Health",grpc_type="unary"}
-grpc_server_handled_total{grpc_code="CODE",grpc_method="Compact",grpc_service="etcdserverpb.KV",grpc_type="unary"}
-grpc_server_handled_total{grpc_code="CODE",grpc_method="Defragment",grpc_service="etcdserverpb.Maintenance",grpc_type="unary"}
-grpc_server_handled_total{grpc_code="CODE",grpc_method="DeleteRange",grpc_service="etcdserverpb.KV",grpc_type="unary"}
-grpc_server_handled_total{grpc_code="CODE",grpc_method="Hash",grpc_service="etcdserverpb.Maintenance",grpc_type="unary"}
-grpc_server_handled_total{grpc_code="CODE",grpc_method="HashKV",grpc_service="etcdserverpb.Maintenance",grpc_type="unary"}
-grpc_server_handled_total{grpc_code="CODE",grpc_method="LeaseGrant",grpc_service="etcdserverpb.Lease",grpc_type="unary"}
-grpc_server_handled_total{grpc_code="CODE",grpc_method="LeaseKeepAlive",grpc_service="etcdserverpb.Lease",grpc_type="bidi_stream"}
-grpc_server_handled_total{grpc_code="CODE",grpc_method="LeaseLeases",grpc_service="etcdserverpb.Lease",grpc_type="unary"}
-grpc_server_handled_total{grpc_code="CODE",grpc_method="LeaseRevoke",grpc_service="etcdserverpb.Lease",grpc_type="unary"}
-grpc_server_handled_total{grpc_code="CODE",grpc_method="LeaseTimeToLive",grpc_service="etcdserverpb.Lease",grpc_type="unary"}
-grpc_server_handled_total{grpc_code="CODE",grpc_method="MemberAdd",grpc_service="etcdserverpb.Cluster",grpc_type="unary"}
-grpc_server_handled_total{grpc_code="CODE",grpc_method="MemberList",grpc_service="etcdserverpb.Cluster",grpc_type="unary"}
-grpc_server_handled_total{grpc_code="CODE",grpc_method="MemberRemove",grpc_service="etcdserverpb.Cluster",grpc_type="unary"}
-grpc_server_handled_total{grpc_code="CODE",grpc_method="MemberUpdate",grpc_service="etcdserverpb.Cluster",grpc_type="unary"}
-grpc_server_handled_total{grpc_code="CODE",grpc_method="MoveLeader",grpc_service="etcdserverpb.Maintenance",grpc_type="unary"}
-grpc_server_handled_total{grpc_code="CODE",grpc_method="Put",grpc_service="etcdserverpb.KV",grpc_type="unary"}
-grpc_server_handled_total{grpc_code="CODE",grpc_method="Range",grpc_service="etcdserverpb.KV",grpc_type="unary"}
-grpc_server_handled_total{grpc_code="CODE",grpc_method="RoleAdd",grpc_service="etcdserverpb.Auth",grpc_type="unary"}
-grpc_server_handled_total{grpc_code="CODE",grpc_method="RoleDelete",grpc_service="etcdserverpb.Auth",grpc_type="unary"}
-grpc_server_handled_total{grpc_code="CODE",grpc_method="RoleGet",grpc_service="etcdserverpb.Auth",grpc_type="unary"}
-grpc_server_handled_total{grpc_code="CODE",grpc_method="RoleGrantPermission",grpc_service="etcdserverpb.Auth",grpc_type="unary"}
-grpc_server_handled_total{grpc_code="CODE",grpc_method="RoleList",grpc_service="etcdserverpb.Auth",grpc_type="unary"}
-grpc_server_handled_total{grpc_code="CODE",grpc_method="RoleRevokePermission",grpc_service="etcdserverpb.Auth",grpc_type="unary"}
-grpc_server_handled_total{grpc_code="CODE",grpc_method="Snapshot",grpc_service="etcdserverpb.Maintenance",grpc_type="server_stream"}
-grpc_server_handled_total{grpc_code="CODE",grpc_method="Status",grpc_service="etcdserverpb.Maintenance",grpc_type="unary"}
-grpc_server_handled_total{grpc_code="CODE",grpc_method="Txn",grpc_service="etcdserverpb.KV",grpc_type="unary"}
-grpc_server_handled_total{grpc_code="CODE",grpc_method="UserAdd",grpc_service="etcdserverpb.Auth",grpc_type="unary"}
-grpc_server_handled_total{grpc_code="CODE",grpc_method="UserChangePassword",grpc_service="etcdserverpb.Auth",grpc_type="unary"}
-grpc_server_handled_total{grpc_code="CODE",grpc_method="UserDelete",grpc_service="etcdserverpb.Auth",grpc_type="unary"}
-grpc_server_handled_total{grpc_code="CODE",grpc_method="UserGet",grpc_service="etcdserverpb.Auth",grpc_type="unary"}
-grpc_server_handled_total{grpc_code="CODE",grpc_method="UserGrantRole",grpc_service="etcdserverpb.Auth",grpc_type="unary"}
-grpc_server_handled_total{grpc_code="CODE",grpc_method="UserList",grpc_service="etcdserverpb.Auth",grpc_type="unary"}
-grpc_server_handled_total{grpc_code="CODE",grpc_method="UserRevokeRole",grpc_service="etcdserverpb.Auth",grpc_type="unary"}
-grpc_server_handled_total{grpc_code="CODE",grpc_method="Watch",grpc_service="etcdserverpb.Watch",grpc_type="bidi_stream"}
-
-# name: "grpc_server_msg_received_total"
-# description: "Total number of RPC stream messages received on the server."
-# type: "counter"
-grpc_server_msg_received_total{grpc_method="Alarm",grpc_service="etcdserverpb.Maintenance",grpc_type="unary"}
-grpc_server_msg_received_total{grpc_method="AuthDisable",grpc_service="etcdserverpb.Auth",grpc_type="unary"}
-grpc_server_msg_received_total{grpc_method="AuthEnable",grpc_service="etcdserverpb.Auth",grpc_type="unary"}
-grpc_server_msg_received_total{grpc_method="Authenticate",grpc_service="etcdserverpb.Auth",grpc_type="unary"}
-grpc_server_msg_received_total{grpc_method="Check",grpc_service="grpc.health.v1.Health",grpc_type="unary"}
-grpc_server_msg_received_total{grpc_method="Compact",grpc_service="etcdserverpb.KV",grpc_type="unary"}
-grpc_server_msg_received_total{grpc_method="Defragment",grpc_service="etcdserverpb.Maintenance",grpc_type="unary"}
-grpc_server_msg_received_total{grpc_method="DeleteRange",grpc_service="etcdserverpb.KV",grpc_type="unary"}
-grpc_server_msg_received_total{grpc_method="Hash",grpc_service="etcdserverpb.Maintenance",grpc_type="unary"}
-grpc_server_msg_received_total{grpc_method="HashKV",grpc_service="etcdserverpb.Maintenance",grpc_type="unary"}
-grpc_server_msg_received_total{grpc_method="LeaseGrant",grpc_service="etcdserverpb.Lease",grpc_type="unary"}
-grpc_server_msg_received_total{grpc_method="LeaseKeepAlive",grpc_service="etcdserverpb.Lease",grpc_type="bidi_stream"}
-grpc_server_msg_received_total{grpc_method="LeaseLeases",grpc_service="etcdserverpb.Lease",grpc_type="unary"}
-grpc_server_msg_received_total{grpc_method="LeaseRevoke",grpc_service="etcdserverpb.Lease",grpc_type="unary"}
-grpc_server_msg_received_total{grpc_method="LeaseTimeToLive",grpc_service="etcdserverpb.Lease",grpc_type="unary"}
-grpc_server_msg_received_total{grpc_method="MemberAdd",grpc_service="etcdserverpb.Cluster",grpc_type="unary"}
-grpc_server_msg_received_total{grpc_method="MemberList",grpc_service="etcdserverpb.Cluster",grpc_type="unary"}
-grpc_server_msg_received_total{grpc_method="MemberRemove",grpc_service="etcdserverpb.Cluster",grpc_type="unary"}
-grpc_server_msg_received_total{grpc_method="MemberUpdate",grpc_service="etcdserverpb.Cluster",grpc_type="unary"}
-grpc_server_msg_received_total{grpc_method="MoveLeader",grpc_service="etcdserverpb.Maintenance",grpc_type="unary"}
-grpc_server_msg_received_total{grpc_method="Put",grpc_service="etcdserverpb.KV",grpc_type="unary"}
-grpc_server_msg_received_total{grpc_method="Range",grpc_service="etcdserverpb.KV",grpc_type="unary"}
-grpc_server_msg_received_total{grpc_method="RoleAdd",grpc_service="etcdserverpb.Auth",grpc_type="unary"}
-grpc_server_msg_received_total{grpc_method="RoleDelete",grpc_service="etcdserverpb.Auth",grpc_type="unary"}
-grpc_server_msg_received_total{grpc_method="RoleGet",grpc_service="etcdserverpb.Auth",grpc_type="unary"}
-grpc_server_msg_received_total{grpc_method="RoleGrantPermission",grpc_service="etcdserverpb.Auth",grpc_type="unary"}
-grpc_server_msg_received_total{grpc_method="RoleList",grpc_service="etcdserverpb.Auth",grpc_type="unary"}
-grpc_server_msg_received_total{grpc_method="RoleRevokePermission",grpc_service="etcdserverpb.Auth",grpc_type="unary"}
-grpc_server_msg_received_total{grpc_method="Snapshot",grpc_service="etcdserverpb.Maintenance",grpc_type="server_stream"}
-grpc_server_msg_received_total{grpc_method="Status",grpc_service="etcdserverpb.Maintenance",grpc_type="unary"}
-grpc_server_msg_received_total{grpc_method="Txn",grpc_service="etcdserverpb.KV",grpc_type="unary"}
-grpc_server_msg_received_total{grpc_method="UserAdd",grpc_service="etcdserverpb.Auth",grpc_type="unary"}
-grpc_server_msg_received_total{grpc_method="UserChangePassword",grpc_service="etcdserverpb.Auth",grpc_type="unary"}
-grpc_server_msg_received_total{grpc_method="UserDelete",grpc_service="etcdserverpb.Auth",grpc_type="unary"}
-grpc_server_msg_received_total{grpc_method="UserGet",grpc_service="etcdserverpb.Auth",grpc_type="unary"}
-grpc_server_msg_received_total{grpc_method="UserGrantRole",grpc_service="etcdserverpb.Auth",grpc_type="unary"}
-grpc_server_msg_received_total{grpc_method="UserList",grpc_service="etcdserverpb.Auth",grpc_type="unary"}
-grpc_server_msg_received_total{grpc_method="UserRevokeRole",grpc_service="etcdserverpb.Auth",grpc_type="unary"}
-grpc_server_msg_received_total{grpc_method="Watch",grpc_service="etcdserverpb.Watch",grpc_type="bidi_stream"}
-
-# name: "grpc_server_msg_sent_total"
-# description: "Total number of gRPC stream messages sent by the server."
-# type: "counter"
-grpc_server_msg_sent_total{grpc_method="Alarm",grpc_service="etcdserverpb.Maintenance",grpc_type="unary"}
-grpc_server_msg_sent_total{grpc_method="AuthDisable",grpc_service="etcdserverpb.Auth",grpc_type="unary"}
-grpc_server_msg_sent_total{grpc_method="AuthEnable",grpc_service="etcdserverpb.Auth",grpc_type="unary"}
-grpc_server_msg_sent_total{grpc_method="Authenticate",grpc_service="etcdserverpb.Auth",grpc_type="unary"}
-grpc_server_msg_sent_total{grpc_method="Check",grpc_service="grpc.health.v1.Health",grpc_type="unary"}
-grpc_server_msg_sent_total{grpc_method="Compact",grpc_service="etcdserverpb.KV",grpc_type="unary"}
-grpc_server_msg_sent_total{grpc_method="Defragment",grpc_service="etcdserverpb.Maintenance",grpc_type="unary"}
-grpc_server_msg_sent_total{grpc_method="DeleteRange",grpc_service="etcdserverpb.KV",grpc_type="unary"}
-grpc_server_msg_sent_total{grpc_method="Hash",grpc_service="etcdserverpb.Maintenance",grpc_type="unary"}
-grpc_server_msg_sent_total{grpc_method="HashKV",grpc_service="etcdserverpb.Maintenance",grpc_type="unary"}
-grpc_server_msg_sent_total{grpc_method="LeaseGrant",grpc_service="etcdserverpb.Lease",grpc_type="unary"}
-grpc_server_msg_sent_total{grpc_method="LeaseKeepAlive",grpc_service="etcdserverpb.Lease",grpc_type="bidi_stream"}
-grpc_server_msg_sent_total{grpc_method="LeaseLeases",grpc_service="etcdserverpb.Lease",grpc_type="unary"}
-grpc_server_msg_sent_total{grpc_method="LeaseRevoke",grpc_service="etcdserverpb.Lease",grpc_type="unary"}
-grpc_server_msg_sent_total{grpc_method="LeaseTimeToLive",grpc_service="etcdserverpb.Lease",grpc_type="unary"}
-grpc_server_msg_sent_total{grpc_method="MemberAdd",grpc_service="etcdserverpb.Cluster",grpc_type="unary"}
-grpc_server_msg_sent_total{grpc_method="MemberList",grpc_service="etcdserverpb.Cluster",grpc_type="unary"}
-grpc_server_msg_sent_total{grpc_method="MemberRemove",grpc_service="etcdserverpb.Cluster",grpc_type="unary"}
-grpc_server_msg_sent_total{grpc_method="MemberUpdate",grpc_service="etcdserverpb.Cluster",grpc_type="unary"}
-grpc_server_msg_sent_total{grpc_method="MoveLeader",grpc_service="etcdserverpb.Maintenance",grpc_type="unary"}
-grpc_server_msg_sent_total{grpc_method="Put",grpc_service="etcdserverpb.KV",grpc_type="unary"}
-grpc_server_msg_sent_total{grpc_method="Range",grpc_service="etcdserverpb.KV",grpc_type="unary"}
-grpc_server_msg_sent_total{grpc_method="RoleAdd",grpc_service="etcdserverpb.Auth",grpc_type="unary"}
-grpc_server_msg_sent_total{grpc_method="RoleDelete",grpc_service="etcdserverpb.Auth",grpc_type="unary"}
-grpc_server_msg_sent_total{grpc_method="RoleGet",grpc_service="etcdserverpb.Auth",grpc_type="unary"}
-grpc_server_msg_sent_total{grpc_method="RoleGrantPermission",grpc_service="etcdserverpb.Auth",grpc_type="unary"}
-grpc_server_msg_sent_total{grpc_method="RoleList",grpc_service="etcdserverpb.Auth",grpc_type="unary"}
-grpc_server_msg_sent_total{grpc_method="RoleRevokePermission",grpc_service="etcdserverpb.Auth",grpc_type="unary"}
-grpc_server_msg_sent_total{grpc_method="Snapshot",grpc_service="etcdserverpb.Maintenance",grpc_type="server_stream"}
-grpc_server_msg_sent_total{grpc_method="Status",grpc_service="etcdserverpb.Maintenance",grpc_type="unary"}
-grpc_server_msg_sent_total{grpc_method="Txn",grpc_service="etcdserverpb.KV",grpc_type="unary"}
-grpc_server_msg_sent_total{grpc_method="UserAdd",grpc_service="etcdserverpb.Auth",grpc_type="unary"}
-grpc_server_msg_sent_total{grpc_method="UserChangePassword",grpc_service="etcdserverpb.Auth",grpc_type="unary"}
-grpc_server_msg_sent_total{grpc_method="UserDelete",grpc_service="etcdserverpb.Auth",grpc_type="unary"}
-grpc_server_msg_sent_total{grpc_method="UserGet",grpc_service="etcdserverpb.Auth",grpc_type="unary"}
-grpc_server_msg_sent_total{grpc_method="UserGrantRole",grpc_service="etcdserverpb.Auth",grpc_type="unary"}
-grpc_server_msg_sent_total{grpc_method="UserList",grpc_service="etcdserverpb.Auth",grpc_type="unary"}
-grpc_server_msg_sent_total{grpc_method="UserRevokeRole",grpc_service="etcdserverpb.Auth",grpc_type="unary"}
-grpc_server_msg_sent_total{grpc_method="Watch",grpc_service="etcdserverpb.Watch",grpc_type="bidi_stream"}
-
-# name: "grpc_server_started_total"
-# description: "Total number of RPCs started on the server."
-# type: "counter"
-grpc_server_started_total{grpc_method="Alarm",grpc_service="etcdserverpb.Maintenance",grpc_type="unary"}
-grpc_server_started_total{grpc_method="AuthDisable",grpc_service="etcdserverpb.Auth",grpc_type="unary"}
-grpc_server_started_total{grpc_method="AuthEnable",grpc_service="etcdserverpb.Auth",grpc_type="unary"}
-grpc_server_started_total{grpc_method="Authenticate",grpc_service="etcdserverpb.Auth",grpc_type="unary"}
-grpc_server_started_total{grpc_method="Check",grpc_service="grpc.health.v1.Health",grpc_type="unary"}
-grpc_server_started_total{grpc_method="Compact",grpc_service="etcdserverpb.KV",grpc_type="unary"}
-grpc_server_started_total{grpc_method="Defragment",grpc_service="etcdserverpb.Maintenance",grpc_type="unary"}
-grpc_server_started_total{grpc_method="DeleteRange",grpc_service="etcdserverpb.KV",grpc_type="unary"}
-grpc_server_started_total{grpc_method="Hash",grpc_service="etcdserverpb.Maintenance",grpc_type="unary"}
-grpc_server_started_total{grpc_method="HashKV",grpc_service="etcdserverpb.Maintenance",grpc_type="unary"}
-grpc_server_started_total{grpc_method="LeaseGrant",grpc_service="etcdserverpb.Lease",grpc_type="unary"}
-grpc_server_started_total{grpc_method="LeaseKeepAlive",grpc_service="etcdserverpb.Lease",grpc_type="bidi_stream"}
-grpc_server_started_total{grpc_method="LeaseLeases",grpc_service="etcdserverpb.Lease",grpc_type="unary"}
-grpc_server_started_total{grpc_method="LeaseRevoke",grpc_service="etcdserverpb.Lease",grpc_type="unary"}
-grpc_server_started_total{grpc_method="LeaseTimeToLive",grpc_service="etcdserverpb.Lease",grpc_type="unary"}
-grpc_server_started_total{grpc_method="MemberAdd",grpc_service="etcdserverpb.Cluster",grpc_type="unary"}
-grpc_server_started_total{grpc_method="MemberList",grpc_service="etcdserverpb.Cluster",grpc_type="unary"}
-grpc_server_started_total{grpc_method="MemberRemove",grpc_service="etcdserverpb.Cluster",grpc_type="unary"}
-grpc_server_started_total{grpc_method="MemberUpdate",grpc_service="etcdserverpb.Cluster",grpc_type="unary"}
-grpc_server_started_total{grpc_method="MoveLeader",grpc_service="etcdserverpb.Maintenance",grpc_type="unary"}
-grpc_server_started_total{grpc_method="Put",grpc_service="etcdserverpb.KV",grpc_type="unary"}
-grpc_server_started_total{grpc_method="Range",grpc_service="etcdserverpb.KV",grpc_type="unary"}
-grpc_server_started_total{grpc_method="RoleAdd",grpc_service="etcdserverpb.Auth",grpc_type="unary"}
-grpc_server_started_total{grpc_method="RoleDelete",grpc_service="etcdserverpb.Auth",grpc_type="unary"}
-grpc_server_started_total{grpc_method="RoleGet",grpc_service="etcdserverpb.Auth",grpc_type="unary"}
-grpc_server_started_total{grpc_method="RoleGrantPermission",grpc_service="etcdserverpb.Auth",grpc_type="unary"}
-grpc_server_started_total{grpc_method="RoleList",grpc_service="etcdserverpb.Auth",grpc_type="unary"}
-grpc_server_started_total{grpc_method="RoleRevokePermission",grpc_service="etcdserverpb.Auth",grpc_type="unary"}
-grpc_server_started_total{grpc_method="Snapshot",grpc_service="etcdserverpb.Maintenance",grpc_type="server_stream"}
-grpc_server_started_total{grpc_method="Status",grpc_service="etcdserverpb.Maintenance",grpc_type="unary"}
-grpc_server_started_total{grpc_method="Txn",grpc_service="etcdserverpb.KV",grpc_type="unary"}
-grpc_server_started_total{grpc_method="UserAdd",grpc_service="etcdserverpb.Auth",grpc_type="unary"}
-grpc_server_started_total{grpc_method="UserChangePassword",grpc_service="etcdserverpb.Auth",grpc_type="unary"}
-grpc_server_started_total{grpc_method="UserDelete",grpc_service="etcdserverpb.Auth",grpc_type="unary"}
-grpc_server_started_total{grpc_method="UserGet",grpc_service="etcdserverpb.Auth",grpc_type="unary"}
-grpc_server_started_total{grpc_method="UserGrantRole",grpc_service="etcdserverpb.Auth",grpc_type="unary"}
-grpc_server_started_total{grpc_method="UserList",grpc_service="etcdserverpb.Auth",grpc_type="unary"}
-grpc_server_started_total{grpc_method="UserRevokeRole",grpc_service="etcdserverpb.Auth",grpc_type="unary"}
-grpc_server_started_total{grpc_method="Watch",grpc_service="etcdserverpb.Watch",grpc_type="bidi_stream"}
-

Documentation/metrics/v3.1.0

@@ -1,511 +0,0 @@
-# server version: unknown
-
-# name: "etcd_debugging_mvcc_db_compaction_pause_duration_milliseconds"
-# description: "Bucketed histogram of db compaction pause duration."
-# type: "histogram"
-etcd_debugging_mvcc_db_compaction_pause_duration_milliseconds_bucket{le="1"}
-etcd_debugging_mvcc_db_compaction_pause_duration_milliseconds_bucket{le="2"}
-etcd_debugging_mvcc_db_compaction_pause_duration_milliseconds_bucket{le="4"}
-etcd_debugging_mvcc_db_compaction_pause_duration_milliseconds_bucket{le="8"}
-etcd_debugging_mvcc_db_compaction_pause_duration_milliseconds_bucket{le="16"}
-etcd_debugging_mvcc_db_compaction_pause_duration_milliseconds_bucket{le="32"}
-etcd_debugging_mvcc_db_compaction_pause_duration_milliseconds_bucket{le="64"}
-etcd_debugging_mvcc_db_compaction_pause_duration_milliseconds_bucket{le="128"}
-etcd_debugging_mvcc_db_compaction_pause_duration_milliseconds_bucket{le="256"}
-etcd_debugging_mvcc_db_compaction_pause_duration_milliseconds_bucket{le="512"}
-etcd_debugging_mvcc_db_compaction_pause_duration_milliseconds_bucket{le="1024"}
-etcd_debugging_mvcc_db_compaction_pause_duration_milliseconds_bucket{le="2048"}
-etcd_debugging_mvcc_db_compaction_pause_duration_milliseconds_bucket{le="4096"}
-etcd_debugging_mvcc_db_compaction_pause_duration_milliseconds_bucket{le="+Inf"}
-etcd_debugging_mvcc_db_compaction_pause_duration_milliseconds_sum
-etcd_debugging_mvcc_db_compaction_pause_duration_milliseconds_count
-
-# name: "etcd_debugging_mvcc_db_compaction_total_duration_milliseconds"
-# description: "Bucketed histogram of db compaction total duration."
-# type: "histogram"
-etcd_debugging_mvcc_db_compaction_total_duration_milliseconds_bucket{le="100"}
-etcd_debugging_mvcc_db_compaction_total_duration_milliseconds_bucket{le="200"}
-etcd_debugging_mvcc_db_compaction_total_duration_milliseconds_bucket{le="400"}
-etcd_debugging_mvcc_db_compaction_total_duration_milliseconds_bucket{le="800"}
-etcd_debugging_mvcc_db_compaction_total_duration_milliseconds_bucket{le="1600"}
-etcd_debugging_mvcc_db_compaction_total_duration_milliseconds_bucket{le="3200"}
-etcd_debugging_mvcc_db_compaction_total_duration_milliseconds_bucket{le="6400"}
-etcd_debugging_mvcc_db_compaction_total_duration_milliseconds_bucket{le="12800"}
-etcd_debugging_mvcc_db_compaction_total_duration_milliseconds_bucket{le="25600"}
-etcd_debugging_mvcc_db_compaction_total_duration_milliseconds_bucket{le="51200"}
-etcd_debugging_mvcc_db_compaction_total_duration_milliseconds_bucket{le="102400"}
-etcd_debugging_mvcc_db_compaction_total_duration_milliseconds_bucket{le="204800"}
-etcd_debugging_mvcc_db_compaction_total_duration_milliseconds_bucket{le="409600"}
-etcd_debugging_mvcc_db_compaction_total_duration_milliseconds_bucket{le="819200"}
-etcd_debugging_mvcc_db_compaction_total_duration_milliseconds_bucket{le="+Inf"}
-etcd_debugging_mvcc_db_compaction_total_duration_milliseconds_sum
-etcd_debugging_mvcc_db_compaction_total_duration_milliseconds_count
-
-# name: "etcd_debugging_mvcc_db_total_size_in_bytes"
-# description: "Total size of the underlying database in bytes."
-# type: "gauge"
-etcd_debugging_mvcc_db_total_size_in_bytes
-
-# name: "etcd_debugging_mvcc_delete_total"
-# description: "Total number of deletes seen by this member."
-# type: "counter"
-etcd_debugging_mvcc_delete_total
-
-# name: "etcd_debugging_mvcc_events_total"
-# description: "Total number of events sent by this member."
-# type: "counter"
-etcd_debugging_mvcc_events_total
-
-# name: "etcd_debugging_mvcc_index_compaction_pause_duration_milliseconds"
-# description: "Bucketed histogram of index compaction pause duration."
-# type: "histogram"
-etcd_debugging_mvcc_index_compaction_pause_duration_milliseconds_bucket{le="0.5"}
-etcd_debugging_mvcc_index_compaction_pause_duration_milliseconds_bucket{le="1"}
-etcd_debugging_mvcc_index_compaction_pause_duration_milliseconds_bucket{le="2"}
-etcd_debugging_mvcc_index_compaction_pause_duration_milliseconds_bucket{le="4"}
-etcd_debugging_mvcc_index_compaction_pause_duration_milliseconds_bucket{le="8"}
-etcd_debugging_mvcc_index_compaction_pause_duration_milliseconds_bucket{le="16"}
-etcd_debugging_mvcc_index_compaction_pause_duration_milliseconds_bucket{le="32"}
-etcd_debugging_mvcc_index_compaction_pause_duration_milliseconds_bucket{le="64"}
-etcd_debugging_mvcc_index_compaction_pause_duration_milliseconds_bucket{le="128"}
-etcd_debugging_mvcc_index_compaction_pause_duration_milliseconds_bucket{le="256"}
-etcd_debugging_mvcc_index_compaction_pause_duration_milliseconds_bucket{le="512"}
-etcd_debugging_mvcc_index_compaction_pause_duration_milliseconds_bucket{le="1024"}
-etcd_debugging_mvcc_index_compaction_pause_duration_milliseconds_bucket{le="+Inf"}
-etcd_debugging_mvcc_index_compaction_pause_duration_milliseconds_sum
-etcd_debugging_mvcc_index_compaction_pause_duration_milliseconds_count
-
-# name: "etcd_debugging_mvcc_keys_total"
-# description: "Total number of keys."
-# type: "gauge"
-etcd_debugging_mvcc_keys_total
-
-# name: "etcd_debugging_mvcc_pending_events_total"
-# description: "Total number of pending events to be sent."
-# type: "gauge"
-etcd_debugging_mvcc_pending_events_total
-
-# name: "etcd_debugging_mvcc_put_total"
-# description: "Total number of puts seen by this member."
-# type: "counter"
-etcd_debugging_mvcc_put_total
-
-# name: "etcd_debugging_mvcc_range_total"
-# description: "Total number of ranges seen by this member."
-# type: "counter"
-etcd_debugging_mvcc_range_total
-
-# name: "etcd_debugging_mvcc_slow_watcher_total"
-# description: "Total number of unsynced slow watchers."
-# type: "gauge"
-etcd_debugging_mvcc_slow_watcher_total
-
-# name: "etcd_debugging_mvcc_txn_total"
-# description: "Total number of txns seen by this member."
-# type: "counter"
-etcd_debugging_mvcc_txn_total
-
-# name: "etcd_debugging_mvcc_watch_stream_total"
-# description: "Total number of watch streams."
-# type: "gauge"
-etcd_debugging_mvcc_watch_stream_total
-
-# name: "etcd_debugging_mvcc_watcher_total"
-# description: "Total number of watchers."
-# type: "gauge"
-etcd_debugging_mvcc_watcher_total
-
-# name: "etcd_debugging_snap_save_marshalling_duration_seconds"
-# description: "The marshalling cost distributions of save called by snapshot."
-# type: "histogram"
-etcd_debugging_snap_save_marshalling_duration_seconds_bucket{le="0.001"}
-etcd_debugging_snap_save_marshalling_duration_seconds_bucket{le="0.002"}
-etcd_debugging_snap_save_marshalling_duration_seconds_bucket{le="0.004"}
-etcd_debugging_snap_save_marshalling_duration_seconds_bucket{le="0.008"}
-etcd_debugging_snap_save_marshalling_duration_seconds_bucket{le="0.016"}
-etcd_debugging_snap_save_marshalling_duration_seconds_bucket{le="0.032"}
-etcd_debugging_snap_save_marshalling_duration_seconds_bucket{le="0.064"}
-etcd_debugging_snap_save_marshalling_duration_seconds_bucket{le="0.128"}
-etcd_debugging_snap_save_marshalling_duration_seconds_bucket{le="0.256"}
-etcd_debugging_snap_save_marshalling_duration_seconds_bucket{le="0.512"}
-etcd_debugging_snap_save_marshalling_duration_seconds_bucket{le="1.024"}
-etcd_debugging_snap_save_marshalling_duration_seconds_bucket{le="2.048"}
-etcd_debugging_snap_save_marshalling_duration_seconds_bucket{le="4.096"}
-etcd_debugging_snap_save_marshalling_duration_seconds_bucket{le="8.192"}
-etcd_debugging_snap_save_marshalling_duration_seconds_bucket{le="+Inf"}
-etcd_debugging_snap_save_marshalling_duration_seconds_sum
-etcd_debugging_snap_save_marshalling_duration_seconds_count
-
-# name: "etcd_debugging_snap_save_total_duration_seconds"
-# description: "The total latency distributions of save called by snapshot."
-# type: "histogram"
-etcd_debugging_snap_save_total_duration_seconds_bucket{le="0.001"}
-etcd_debugging_snap_save_total_duration_seconds_bucket{le="0.002"}
-etcd_debugging_snap_save_total_duration_seconds_bucket{le="0.004"}
-etcd_debugging_snap_save_total_duration_seconds_bucket{le="0.008"}
-etcd_debugging_snap_save_total_duration_seconds_bucket{le="0.016"}
-etcd_debugging_snap_save_total_duration_seconds_bucket{le="0.032"}
-etcd_debugging_snap_save_total_duration_seconds_bucket{le="0.064"}
-etcd_debugging_snap_save_total_duration_seconds_bucket{le="0.128"}
-etcd_debugging_snap_save_total_duration_seconds_bucket{le="0.256"}
-etcd_debugging_snap_save_total_duration_seconds_bucket{le="0.512"}
-etcd_debugging_snap_save_total_duration_seconds_bucket{le="1.024"}
-etcd_debugging_snap_save_total_duration_seconds_bucket{le="2.048"}
-etcd_debugging_snap_save_total_duration_seconds_bucket{le="4.096"}
-etcd_debugging_snap_save_total_duration_seconds_bucket{le="8.192"}
-etcd_debugging_snap_save_total_duration_seconds_bucket{le="+Inf"}
-etcd_debugging_snap_save_total_duration_seconds_sum
-etcd_debugging_snap_save_total_duration_seconds_count
-
-# name: "etcd_debugging_store_expires_total"
-# description: "Total number of expired keys."
-# type: "counter"
-etcd_debugging_store_expires_total
-
-# name: "etcd_debugging_store_reads_total"
-# description: "Total number of reads action by (get/getRecursive), local to this member."
-# type: "counter"
-etcd_debugging_store_reads_total{action="getRecursive"}
-
-# name: "etcd_debugging_store_watch_requests_total"
-# description: "Total number of incoming watch requests (new or reestablished)."
-# type: "counter"
-etcd_debugging_store_watch_requests_total
-
-# name: "etcd_debugging_store_watchers"
-# description: "Count of currently active watchers."
-# type: "gauge"
-etcd_debugging_store_watchers
-
-# name: "etcd_debugging_store_writes_total"
-# description: "Total number of writes (e.g. set/compareAndDelete) seen by this member."
-# type: "counter"
-etcd_debugging_store_writes_total{action="create"}
-etcd_debugging_store_writes_total{action="set"}
-
-# name: "etcd_disk_backend_commit_duration_seconds"
-# description: "The latency distributions of commit called by backend."
-# type: "histogram"
-etcd_disk_backend_commit_duration_seconds_bucket{le="0.001"}
-etcd_disk_backend_commit_duration_seconds_bucket{le="0.002"}
-etcd_disk_backend_commit_duration_seconds_bucket{le="0.004"}
-etcd_disk_backend_commit_duration_seconds_bucket{le="0.008"}
-etcd_disk_backend_commit_duration_seconds_bucket{le="0.016"}
-etcd_disk_backend_commit_duration_seconds_bucket{le="0.032"}
-etcd_disk_backend_commit_duration_seconds_bucket{le="0.064"}
-etcd_disk_backend_commit_duration_seconds_bucket{le="0.128"}
-etcd_disk_backend_commit_duration_seconds_bucket{le="0.256"}
-etcd_disk_backend_commit_duration_seconds_bucket{le="0.512"}
-etcd_disk_backend_commit_duration_seconds_bucket{le="1.024"}
-etcd_disk_backend_commit_duration_seconds_bucket{le="2.048"}
-etcd_disk_backend_commit_duration_seconds_bucket{le="4.096"}
-etcd_disk_backend_commit_duration_seconds_bucket{le="8.192"}
-etcd_disk_backend_commit_duration_seconds_bucket{le="+Inf"}
-etcd_disk_backend_commit_duration_seconds_sum
-etcd_disk_backend_commit_duration_seconds_count
-
-# name: "etcd_disk_wal_fsync_duration_seconds"
-# description: "The latency distributions of fsync called by wal."
-# type: "histogram"
-etcd_disk_wal_fsync_duration_seconds_bucket{le="0.001"}
-etcd_disk_wal_fsync_duration_seconds_bucket{le="0.002"}
-etcd_disk_wal_fsync_duration_seconds_bucket{le="0.004"}
-etcd_disk_wal_fsync_duration_seconds_bucket{le="0.008"}
-etcd_disk_wal_fsync_duration_seconds_bucket{le="0.016"}
-etcd_disk_wal_fsync_duration_seconds_bucket{le="0.032"}
-etcd_disk_wal_fsync_duration_seconds_bucket{le="0.064"}
-etcd_disk_wal_fsync_duration_seconds_bucket{le="0.128"}
-etcd_disk_wal_fsync_duration_seconds_bucket{le="0.256"}
-etcd_disk_wal_fsync_duration_seconds_bucket{le="0.512"}
-etcd_disk_wal_fsync_duration_seconds_bucket{le="1.024"}
-etcd_disk_wal_fsync_duration_seconds_bucket{le="2.048"}
-etcd_disk_wal_fsync_duration_seconds_bucket{le="4.096"}
-etcd_disk_wal_fsync_duration_seconds_bucket{le="8.192"}
-etcd_disk_wal_fsync_duration_seconds_bucket{le="+Inf"}
-etcd_disk_wal_fsync_duration_seconds_sum
-etcd_disk_wal_fsync_duration_seconds_count
-
-# name: "etcd_grpc_proxy_cache_hits_total"
-# description: "Total number of cache hits"
-# type: "gauge"
-etcd_grpc_proxy_cache_hits_total
-
-# name: "etcd_grpc_proxy_cache_misses_total"
-# description: "Total number of cache misses"
-# type: "gauge"
-etcd_grpc_proxy_cache_misses_total
-
-# name: "etcd_grpc_proxy_events_coalescing_total"
-# description: "Total number of events coalescing"
-# type: "counter"
-etcd_grpc_proxy_events_coalescing_total
-
-# name: "etcd_grpc_proxy_watchers_coalescing_total"
-# description: "Total number of current watchers coalescing"
-# type: "gauge"
-etcd_grpc_proxy_watchers_coalescing_total
-
-# name: "etcd_network_client_grpc_received_bytes_total"
-# description: "The total number of bytes received from grpc clients."
-# type: "counter"
-etcd_network_client_grpc_received_bytes_total
-
-# name: "etcd_network_client_grpc_sent_bytes_total"
-# description: "The total number of bytes sent to grpc clients."
-# type: "counter"
-etcd_network_client_grpc_sent_bytes_total
-
-# name: "etcd_network_peer_received_bytes_total"
-# description: "The total number of bytes received from peers."
-# type: "counter"
-etcd_network_peer_received_bytes_total{From="REMOTE_PEER_NODE_ID"}
-
-# name: "etcd_network_peer_round_trip_time_seconds"
-# description: "Round-Trip-Time histogram between peers."
-# type: "histogram"
-etcd_network_peer_round_trip_time_seconds_bucket{To="REMOTE_PEER_NODE_ID",le="+Inf"}
-etcd_network_peer_round_trip_time_seconds_bucket{To="REMOTE_PEER_NODE_ID",le="0.0001"}
-etcd_network_peer_round_trip_time_seconds_bucket{To="REMOTE_PEER_NODE_ID",le="0.0002"}
-etcd_network_peer_round_trip_time_seconds_bucket{To="REMOTE_PEER_NODE_ID",le="0.0004"}
-etcd_network_peer_round_trip_time_seconds_bucket{To="REMOTE_PEER_NODE_ID",le="0.0008"}
-etcd_network_peer_round_trip_time_seconds_bucket{To="REMOTE_PEER_NODE_ID",le="0.0016"}
-etcd_network_peer_round_trip_time_seconds_bucket{To="REMOTE_PEER_NODE_ID",le="0.0032"}
-etcd_network_peer_round_trip_time_seconds_bucket{To="REMOTE_PEER_NODE_ID",le="0.0064"}
-etcd_network_peer_round_trip_time_seconds_bucket{To="REMOTE_PEER_NODE_ID",le="0.0128"}
-etcd_network_peer_round_trip_time_seconds_bucket{To="REMOTE_PEER_NODE_ID",le="0.0256"}
-etcd_network_peer_round_trip_time_seconds_bucket{To="REMOTE_PEER_NODE_ID",le="0.0512"}
-etcd_network_peer_round_trip_time_seconds_bucket{To="REMOTE_PEER_NODE_ID",le="0.1024"}
-etcd_network_peer_round_trip_time_seconds_bucket{To="REMOTE_PEER_NODE_ID",le="0.2048"}
-etcd_network_peer_round_trip_time_seconds_bucket{To="REMOTE_PEER_NODE_ID",le="0.4096"}
-etcd_network_peer_round_trip_time_seconds_bucket{To="REMOTE_PEER_NODE_ID",le="0.8192"}
-etcd_network_peer_round_trip_time_seconds_count{To="REMOTE_PEER_NODE_ID"}
-etcd_network_peer_round_trip_time_seconds_sum{To="REMOTE_PEER_NODE_ID"}
-
-# name: "etcd_network_peer_sent_bytes_total"
-# description: "The total number of bytes sent to peers."
-# type: "counter"
-etcd_network_peer_sent_bytes_total{To="REMOTE_PEER_NODE_ID"}
-
-# name: "etcd_server_has_leader"
-# description: "Whether or not a leader exists. 1 is existence, 0 is not."
-# type: "gauge"
-etcd_server_has_leader
-
-# name: "etcd_server_leader_changes_seen_total"
-# description: "The number of leader changes seen."
-# type: "counter"
-etcd_server_leader_changes_seen_total
-
-# name: "etcd_server_proposals_applied_total"
-# description: "The total number of consensus proposals applied."
-# type: "gauge"
-etcd_server_proposals_applied_total
-
-# name: "etcd_server_proposals_committed_total"
-# description: "The total number of consensus proposals committed."
-# type: "gauge"
-etcd_server_proposals_committed_total
-
-# name: "etcd_server_proposals_failed_total"
-# description: "The total number of failed proposals seen."
-# type: "counter"
-etcd_server_proposals_failed_total
-
-# name: "etcd_server_proposals_pending"
-# description: "The current number of pending proposals to commit."
-# type: "gauge"
-etcd_server_proposals_pending
-
-# name: "go_gc_duration_seconds"
-# description: "A summary of the GC invocation durations."
-# type: "summary"
-go_gc_duration_seconds{quantile="0"}
-go_gc_duration_seconds{quantile="0.25"}
-go_gc_duration_seconds{quantile="0.5"}
-go_gc_duration_seconds{quantile="0.75"}
-go_gc_duration_seconds{quantile="1"}
-go_gc_duration_seconds_sum
-go_gc_duration_seconds_count
-
-# name: "go_goroutines"
-# description: "Number of goroutines that currently exist."
-# type: "gauge"
-go_goroutines
-
-# name: "go_memstats_alloc_bytes"
-# description: "Number of bytes allocated and still in use."
-# type: "gauge"
-go_memstats_alloc_bytes
-
-# name: "go_memstats_alloc_bytes_total"
-# description: "Total number of bytes allocated, even if freed."
-# type: "counter"
-go_memstats_alloc_bytes_total
-
-# name: "go_memstats_buck_hash_sys_bytes"
-# description: "Number of bytes used by the profiling bucket hash table."
-# type: "gauge"
-go_memstats_buck_hash_sys_bytes
-
-# name: "go_memstats_frees_total"
-# description: "Total number of frees."
-# type: "counter"
-go_memstats_frees_total
-
-# name: "go_memstats_gc_sys_bytes"
-# description: "Number of bytes used for garbage collection system metadata."
-# type: "gauge"
-go_memstats_gc_sys_bytes
-
-# name: "go_memstats_heap_alloc_bytes"
-# description: "Number of heap bytes allocated and still in use."
-# type: "gauge"
-go_memstats_heap_alloc_bytes
-
-# name: "go_memstats_heap_idle_bytes"
-# description: "Number of heap bytes waiting to be used."
-# type: "gauge"
-go_memstats_heap_idle_bytes
-
-# name: "go_memstats_heap_inuse_bytes"
-# description: "Number of heap bytes that are in use."
-# type: "gauge"
-go_memstats_heap_inuse_bytes
-
-# name: "go_memstats_heap_objects"
-# description: "Number of allocated objects."
-# type: "gauge"
-go_memstats_heap_objects
-
-# name: "go_memstats_heap_released_bytes_total"
-# description: "Total number of heap bytes released to OS."
-# type: "counter"
-go_memstats_heap_released_bytes_total
-
-# name: "go_memstats_heap_sys_bytes"
-# description: "Number of heap bytes obtained from system."
-# type: "gauge"
-go_memstats_heap_sys_bytes
-
-# name: "go_memstats_last_gc_time_seconds"
-# description: "Number of seconds since 1970 of last garbage collection."
-# type: "gauge"
-go_memstats_last_gc_time_seconds
-
-# name: "go_memstats_lookups_total"
-# description: "Total number of pointer lookups."
-# type: "counter"
-go_memstats_lookups_total
-
-# name: "go_memstats_mallocs_total"
-# description: "Total number of mallocs."
-# type: "counter"
-go_memstats_mallocs_total
-
-# name: "go_memstats_mcache_inuse_bytes"
-# description: "Number of bytes in use by mcache structures."
-# type: "gauge"
-go_memstats_mcache_inuse_bytes
-
-# name: "go_memstats_mcache_sys_bytes"
-# description: "Number of bytes used for mcache structures obtained from system."
-# type: "gauge"
-go_memstats_mcache_sys_bytes
-
-# name: "go_memstats_mspan_inuse_bytes"
-# description: "Number of bytes in use by mspan structures."
-# type: "gauge"
-go_memstats_mspan_inuse_bytes
-
-# name: "go_memstats_mspan_sys_bytes"
-# description: "Number of bytes used for mspan structures obtained from system."
-# type: "gauge"
-go_memstats_mspan_sys_bytes
-
-# name: "go_memstats_next_gc_bytes"
-# description: "Number of heap bytes when next garbage collection will take place."
-# type: "gauge"
-go_memstats_next_gc_bytes
-
-# name: "go_memstats_other_sys_bytes"
-# description: "Number of bytes used for other system allocations."
-# type: "gauge"
-go_memstats_other_sys_bytes
-
-# name: "go_memstats_stack_inuse_bytes"
-# description: "Number of bytes in use by the stack allocator."
-# type: "gauge"
-go_memstats_stack_inuse_bytes
-
-# name: "go_memstats_stack_sys_bytes"
-# description: "Number of bytes obtained from system for stack allocator."
-# type: "gauge"
-go_memstats_stack_sys_bytes
-
-# name: "go_memstats_sys_bytes"
-# description: "Number of bytes obtained by system. Sum of all system allocations."
-# type: "gauge"
-go_memstats_sys_bytes
-
-# name: "grpc_server_handled_total"
-# description: "Total number of RPCs completed on the server, regardless of success or failure."
-# type: "counter"
-# gRPC codes: 
-#  - "OK"
-#  - "Unavailable"
-grpc_server_handled_total{grpc_code="CODE",grpc_method="DeleteRange",grpc_service="etcdserverpb.KV",grpc_type="unary"}
-grpc_server_handled_total{grpc_code="CODE",grpc_method="Put",grpc_service="etcdserverpb.KV",grpc_type="unary"}
-grpc_server_handled_total{grpc_code="CODE",grpc_method="Range",grpc_service="etcdserverpb.KV",grpc_type="unary"}
-grpc_server_handled_total{grpc_code="CODE",grpc_method="Watch",grpc_service="etcdserverpb.Watch",grpc_type="bidi_stream"}
-
-# name: "grpc_server_msg_received_total"
-# description: "Total number of RPC stream messages received on the server."
-# type: "counter"
-grpc_server_msg_received_total{grpc_method="DeleteRange",grpc_service="etcdserverpb.KV",grpc_type="unary"}
-grpc_server_msg_received_total{grpc_method="Put",grpc_service="etcdserverpb.KV",grpc_type="unary"}
-grpc_server_msg_received_total{grpc_method="Range",grpc_service="etcdserverpb.KV",grpc_type="unary"}
-grpc_server_msg_received_total{grpc_method="Watch",grpc_service="etcdserverpb.Watch",grpc_type="bidi_stream"}
-
-# name: "grpc_server_msg_sent_total"
-# description: "Total number of gRPC stream messages sent by the server."
-# type: "counter"
-grpc_server_msg_sent_total{grpc_method="DeleteRange",grpc_service="etcdserverpb.KV",grpc_type="unary"}
-grpc_server_msg_sent_total{grpc_method="Put",grpc_service="etcdserverpb.KV",grpc_type="unary"}
-grpc_server_msg_sent_total{grpc_method="Range",grpc_service="etcdserverpb.KV",grpc_type="unary"}
-grpc_server_msg_sent_total{grpc_method="Watch",grpc_service="etcdserverpb.Watch",grpc_type="bidi_stream"}
-
-# name: "grpc_server_started_total"
-# description: "Total number of RPCs started on the server."
-# type: "counter"
-grpc_server_started_total{grpc_method="DeleteRange",grpc_service="etcdserverpb.KV",grpc_type="unary"}
-grpc_server_started_total{grpc_method="Put",grpc_service="etcdserverpb.KV",grpc_type="unary"}
-grpc_server_started_total{grpc_method="Range",grpc_service="etcdserverpb.KV",grpc_type="unary"}
-grpc_server_started_total{grpc_method="Watch",grpc_service="etcdserverpb.Watch",grpc_type="bidi_stream"}
-
-# name: "http_request_duration_microseconds"
-# description: "The HTTP request latencies in microseconds."
-# type: "summary"
-http_request_duration_microseconds{handler="prometheus",quantile="0.5"}
-http_request_duration_microseconds{handler="prometheus",quantile="0.9"}
-http_request_duration_microseconds{handler="prometheus",quantile="0.99"}
-http_request_duration_microseconds_sum{handler="prometheus"}
-http_request_duration_microseconds_count{handler="prometheus"}
-
-# name: "http_request_size_bytes"
-# description: "The HTTP request sizes in bytes."
-# type: "summary"
-http_request_size_bytes{handler="prometheus",quantile="0.5"}
-http_request_size_bytes{handler="prometheus",quantile="0.9"}
-http_request_size_bytes{handler="prometheus",quantile="0.99"}
-http_request_size_bytes_sum{handler="prometheus"}
-http_request_size_bytes_count{handler="prometheus"}
-
-# name: "http_response_size_bytes"
-# description: "The HTTP response sizes in bytes."
-# type: "summary"
-http_response_size_bytes{handler="prometheus",quantile="0.5"}
-http_response_size_bytes{handler="prometheus",quantile="0.9"}
-http_response_size_bytes{handler="prometheus",quantile="0.99"}
-http_response_size_bytes_sum{handler="prometheus"}
-http_response_size_bytes_count{handler="prometheus"}
-

Documentation/metrics/v3.1.1

@@ -1,511 +0,0 @@
-# server version: unknown
-
-# name: "etcd_debugging_mvcc_db_compaction_pause_duration_milliseconds"
-# description: "Bucketed histogram of db compaction pause duration."
-# type: "histogram"
-etcd_debugging_mvcc_db_compaction_pause_duration_milliseconds_bucket{le="1"}
-etcd_debugging_mvcc_db_compaction_pause_duration_milliseconds_bucket{le="2"}
-etcd_debugging_mvcc_db_compaction_pause_duration_milliseconds_bucket{le="4"}
-etcd_debugging_mvcc_db_compaction_pause_duration_milliseconds_bucket{le="8"}
-etcd_debugging_mvcc_db_compaction_pause_duration_milliseconds_bucket{le="16"}
-etcd_debugging_mvcc_db_compaction_pause_duration_milliseconds_bucket{le="32"}
-etcd_debugging_mvcc_db_compaction_pause_duration_milliseconds_bucket{le="64"}
-etcd_debugging_mvcc_db_compaction_pause_duration_milliseconds_bucket{le="128"}
-etcd_debugging_mvcc_db_compaction_pause_duration_milliseconds_bucket{le="256"}
-etcd_debugging_mvcc_db_compaction_pause_duration_milliseconds_bucket{le="512"}
-etcd_debugging_mvcc_db_compaction_pause_duration_milliseconds_bucket{le="1024"}
-etcd_debugging_mvcc_db_compaction_pause_duration_milliseconds_bucket{le="2048"}
-etcd_debugging_mvcc_db_compaction_pause_duration_milliseconds_bucket{le="4096"}
-etcd_debugging_mvcc_db_compaction_pause_duration_milliseconds_bucket{le="+Inf"}
-etcd_debugging_mvcc_db_compaction_pause_duration_milliseconds_sum
-etcd_debugging_mvcc_db_compaction_pause_duration_milliseconds_count
-
-# name: "etcd_debugging_mvcc_db_compaction_total_duration_milliseconds"
-# description: "Bucketed histogram of db compaction total duration."
-# type: "histogram"
-etcd_debugging_mvcc_db_compaction_total_duration_milliseconds_bucket{le="100"}
-etcd_debugging_mvcc_db_compaction_total_duration_milliseconds_bucket{le="200"}
-etcd_debugging_mvcc_db_compaction_total_duration_milliseconds_bucket{le="400"}
-etcd_debugging_mvcc_db_compaction_total_duration_milliseconds_bucket{le="800"}
-etcd_debugging_mvcc_db_compaction_total_duration_milliseconds_bucket{le="1600"}
-etcd_debugging_mvcc_db_compaction_total_duration_milliseconds_bucket{le="3200"}
-etcd_debugging_mvcc_db_compaction_total_duration_milliseconds_bucket{le="6400"}
-etcd_debugging_mvcc_db_compaction_total_duration_milliseconds_bucket{le="12800"}
-etcd_debugging_mvcc_db_compaction_total_duration_milliseconds_bucket{le="25600"}
-etcd_debugging_mvcc_db_compaction_total_duration_milliseconds_bucket{le="51200"}
-etcd_debugging_mvcc_db_compaction_total_duration_milliseconds_bucket{le="102400"}
-etcd_debugging_mvcc_db_compaction_total_duration_milliseconds_bucket{le="204800"}
-etcd_debugging_mvcc_db_compaction_total_duration_milliseconds_bucket{le="409600"}
-etcd_debugging_mvcc_db_compaction_total_duration_milliseconds_bucket{le="819200"}
-etcd_debugging_mvcc_db_compaction_total_duration_milliseconds_bucket{le="+Inf"}
-etcd_debugging_mvcc_db_compaction_total_duration_milliseconds_sum
-etcd_debugging_mvcc_db_compaction_total_duration_milliseconds_count
-
-# name: "etcd_debugging_mvcc_db_total_size_in_bytes"
-# description: "Total size of the underlying database in bytes."
-# type: "gauge"
-etcd_debugging_mvcc_db_total_size_in_bytes
-
-# name: "etcd_debugging_mvcc_delete_total"
-# description: "Total number of deletes seen by this member."
-# type: "counter"
-etcd_debugging_mvcc_delete_total
-
-# name: "etcd_debugging_mvcc_events_total"
-# description: "Total number of events sent by this member."
-# type: "counter"
-etcd_debugging_mvcc_events_total
-
-# name: "etcd_debugging_mvcc_index_compaction_pause_duration_milliseconds"
-# description: "Bucketed histogram of index compaction pause duration."
-# type: "histogram"
-etcd_debugging_mvcc_index_compaction_pause_duration_milliseconds_bucket{le="0.5"}
-etcd_debugging_mvcc_index_compaction_pause_duration_milliseconds_bucket{le="1"}
-etcd_debugging_mvcc_index_compaction_pause_duration_milliseconds_bucket{le="2"}
-etcd_debugging_mvcc_index_compaction_pause_duration_milliseconds_bucket{le="4"}
-etcd_debugging_mvcc_index_compaction_pause_duration_milliseconds_bucket{le="8"}
-etcd_debugging_mvcc_index_compaction_pause_duration_milliseconds_bucket{le="16"}
-etcd_debugging_mvcc_index_compaction_pause_duration_milliseconds_bucket{le="32"}
-etcd_debugging_mvcc_index_compaction_pause_duration_milliseconds_bucket{le="64"}
-etcd_debugging_mvcc_index_compaction_pause_duration_milliseconds_bucket{le="128"}
-etcd_debugging_mvcc_index_compaction_pause_duration_milliseconds_bucket{le="256"}
-etcd_debugging_mvcc_index_compaction_pause_duration_milliseconds_bucket{le="512"}
-etcd_debugging_mvcc_index_compaction_pause_duration_milliseconds_bucket{le="1024"}
-etcd_debugging_mvcc_index_compaction_pause_duration_milliseconds_bucket{le="+Inf"}
-etcd_debugging_mvcc_index_compaction_pause_duration_milliseconds_sum
-etcd_debugging_mvcc_index_compaction_pause_duration_milliseconds_count
-
-# name: "etcd_debugging_mvcc_keys_total"
-# description: "Total number of keys."
-# type: "gauge"
-etcd_debugging_mvcc_keys_total
-
-# name: "etcd_debugging_mvcc_pending_events_total"
-# description: "Total number of pending events to be sent."
-# type: "gauge"
-etcd_debugging_mvcc_pending_events_total
-
-# name: "etcd_debugging_mvcc_put_total"
-# description: "Total number of puts seen by this member."
-# type: "counter"
-etcd_debugging_mvcc_put_total
-
-# name: "etcd_debugging_mvcc_range_total"
-# description: "Total number of ranges seen by this member."
-# type: "counter"
-etcd_debugging_mvcc_range_total
-
-# name: "etcd_debugging_mvcc_slow_watcher_total"
-# description: "Total number of unsynced slow watchers."
-# type: "gauge"
-etcd_debugging_mvcc_slow_watcher_total
-
-# name: "etcd_debugging_mvcc_txn_total"
-# description: "Total number of txns seen by this member."
-# type: "counter"
-etcd_debugging_mvcc_txn_total
-
-# name: "etcd_debugging_mvcc_watch_stream_total"
-# description: "Total number of watch streams."
-# type: "gauge"
-etcd_debugging_mvcc_watch_stream_total
-
-# name: "etcd_debugging_mvcc_watcher_total"
-# description: "Total number of watchers."
-# type: "gauge"
-etcd_debugging_mvcc_watcher_total
-
-# name: "etcd_debugging_snap_save_marshalling_duration_seconds"
-# description: "The marshalling cost distributions of save called by snapshot."
-# type: "histogram"
-etcd_debugging_snap_save_marshalling_duration_seconds_bucket{le="0.001"}
-etcd_debugging_snap_save_marshalling_duration_seconds_bucket{le="0.002"}
-etcd_debugging_snap_save_marshalling_duration_seconds_bucket{le="0.004"}
-etcd_debugging_snap_save_marshalling_duration_seconds_bucket{le="0.008"}
-etcd_debugging_snap_save_marshalling_duration_seconds_bucket{le="0.016"}
-etcd_debugging_snap_save_marshalling_duration_seconds_bucket{le="0.032"}
-etcd_debugging_snap_save_marshalling_duration_seconds_bucket{le="0.064"}
-etcd_debugging_snap_save_marshalling_duration_seconds_bucket{le="0.128"}
-etcd_debugging_snap_save_marshalling_duration_seconds_bucket{le="0.256"}
-etcd_debugging_snap_save_marshalling_duration_seconds_bucket{le="0.512"}
-etcd_debugging_snap_save_marshalling_duration_seconds_bucket{le="1.024"}
-etcd_debugging_snap_save_marshalling_duration_seconds_bucket{le="2.048"}
-etcd_debugging_snap_save_marshalling_duration_seconds_bucket{le="4.096"}
-etcd_debugging_snap_save_marshalling_duration_seconds_bucket{le="8.192"}
-etcd_debugging_snap_save_marshalling_duration_seconds_bucket{le="+Inf"}
-etcd_debugging_snap_save_marshalling_duration_seconds_sum
-etcd_debugging_snap_save_marshalling_duration_seconds_count
-
-# name: "etcd_debugging_snap_save_total_duration_seconds"
-# description: "The total latency distributions of save called by snapshot."
-# type: "histogram"
-etcd_debugging_snap_save_total_duration_seconds_bucket{le="0.001"}
-etcd_debugging_snap_save_total_duration_seconds_bucket{le="0.002"}
-etcd_debugging_snap_save_total_duration_seconds_bucket{le="0.004"}
-etcd_debugging_snap_save_total_duration_seconds_bucket{le="0.008"}
-etcd_debugging_snap_save_total_duration_seconds_bucket{le="0.016"}
-etcd_debugging_snap_save_total_duration_seconds_bucket{le="0.032"}
-etcd_debugging_snap_save_total_duration_seconds_bucket{le="0.064"}
-etcd_debugging_snap_save_total_duration_seconds_bucket{le="0.128"}
-etcd_debugging_snap_save_total_duration_seconds_bucket{le="0.256"}
-etcd_debugging_snap_save_total_duration_seconds_bucket{le="0.512"}
-etcd_debugging_snap_save_total_duration_seconds_bucket{le="1.024"}
-etcd_debugging_snap_save_total_duration_seconds_bucket{le="2.048"}
-etcd_debugging_snap_save_total_duration_seconds_bucket{le="4.096"}
-etcd_debugging_snap_save_total_duration_seconds_bucket{le="8.192"}
-etcd_debugging_snap_save_total_duration_seconds_bucket{le="+Inf"}
-etcd_debugging_snap_save_total_duration_seconds_sum
-etcd_debugging_snap_save_total_duration_seconds_count
-
-# name: "etcd_debugging_store_expires_total"
-# description: "Total number of expired keys."
-# type: "counter"
-etcd_debugging_store_expires_total
-
-# name: "etcd_debugging_store_reads_total"
-# description: "Total number of reads action by (get/getRecursive), local to this member."
-# type: "counter"
-etcd_debugging_store_reads_total{action="getRecursive"}
-
-# name: "etcd_debugging_store_watch_requests_total"
-# description: "Total number of incoming watch requests (new or reestablished)."
-# type: "counter"
-etcd_debugging_store_watch_requests_total
-
-# name: "etcd_debugging_store_watchers"
-# description: "Count of currently active watchers."
-# type: "gauge"
-etcd_debugging_store_watchers
-
-# name: "etcd_debugging_store_writes_total"
-# description: "Total number of writes (e.g. set/compareAndDelete) seen by this member."
-# type: "counter"
-etcd_debugging_store_writes_total{action="create"}
-etcd_debugging_store_writes_total{action="set"}
-
-# name: "etcd_disk_backend_commit_duration_seconds"
-# description: "The latency distributions of commit called by backend."
-# type: "histogram"
-etcd_disk_backend_commit_duration_seconds_bucket{le="0.001"}
-etcd_disk_backend_commit_duration_seconds_bucket{le="0.002"}
-etcd_disk_backend_commit_duration_seconds_bucket{le="0.004"}
-etcd_disk_backend_commit_duration_seconds_bucket{le="0.008"}
-etcd_disk_backend_commit_duration_seconds_bucket{le="0.016"}
-etcd_disk_backend_commit_duration_seconds_bucket{le="0.032"}
-etcd_disk_backend_commit_duration_seconds_bucket{le="0.064"}
-etcd_disk_backend_commit_duration_seconds_bucket{le="0.128"}
-etcd_disk_backend_commit_duration_seconds_bucket{le="0.256"}
-etcd_disk_backend_commit_duration_seconds_bucket{le="0.512"}
-etcd_disk_backend_commit_duration_seconds_bucket{le="1.024"}
-etcd_disk_backend_commit_duration_seconds_bucket{le="2.048"}
-etcd_disk_backend_commit_duration_seconds_bucket{le="4.096"}
-etcd_disk_backend_commit_duration_seconds_bucket{le="8.192"}
-etcd_disk_backend_commit_duration_seconds_bucket{le="+Inf"}
-etcd_disk_backend_commit_duration_seconds_sum
-etcd_disk_backend_commit_duration_seconds_count
-
-# name: "etcd_disk_wal_fsync_duration_seconds"
-# description: "The latency distributions of fsync called by wal."
-# type: "histogram"
-etcd_disk_wal_fsync_duration_seconds_bucket{le="0.001"}
-etcd_disk_wal_fsync_duration_seconds_bucket{le="0.002"}
-etcd_disk_wal_fsync_duration_seconds_bucket{le="0.004"}
-etcd_disk_wal_fsync_duration_seconds_bucket{le="0.008"}
-etcd_disk_wal_fsync_duration_seconds_bucket{le="0.016"}
-etcd_disk_wal_fsync_duration_seconds_bucket{le="0.032"}
-etcd_disk_wal_fsync_duration_seconds_bucket{le="0.064"}
-etcd_disk_wal_fsync_duration_seconds_bucket{le="0.128"}
-etcd_disk_wal_fsync_duration_seconds_bucket{le="0.256"}
-etcd_disk_wal_fsync_duration_seconds_bucket{le="0.512"}
-etcd_disk_wal_fsync_duration_seconds_bucket{le="1.024"}
-etcd_disk_wal_fsync_duration_seconds_bucket{le="2.048"}
-etcd_disk_wal_fsync_duration_seconds_bucket{le="4.096"}
-etcd_disk_wal_fsync_duration_seconds_bucket{le="8.192"}
-etcd_disk_wal_fsync_duration_seconds_bucket{le="+Inf"}
-etcd_disk_wal_fsync_duration_seconds_sum
-etcd_disk_wal_fsync_duration_seconds_count
-
-# name: "etcd_grpc_proxy_cache_hits_total"
-# description: "Total number of cache hits"
-# type: "gauge"
-etcd_grpc_proxy_cache_hits_total
-
-# name: "etcd_grpc_proxy_cache_misses_total"
-# description: "Total number of cache misses"
-# type: "gauge"
-etcd_grpc_proxy_cache_misses_total
-
-# name: "etcd_grpc_proxy_events_coalescing_total"
-# description: "Total number of events coalescing"
-# type: "counter"
-etcd_grpc_proxy_events_coalescing_total
-
-# name: "etcd_grpc_proxy_watchers_coalescing_total"
-# description: "Total number of current watchers coalescing"
-# type: "gauge"
-etcd_grpc_proxy_watchers_coalescing_total
-
-# name: "etcd_network_client_grpc_received_bytes_total"
-# description: "The total number of bytes received from grpc clients."
-# type: "counter"
-etcd_network_client_grpc_received_bytes_total
-
-# name: "etcd_network_client_grpc_sent_bytes_total"
-# description: "The total number of bytes sent to grpc clients."
-# type: "counter"
-etcd_network_client_grpc_sent_bytes_total
-
-# name: "etcd_network_peer_received_bytes_total"
-# description: "The total number of bytes received from peers."
-# type: "counter"
-etcd_network_peer_received_bytes_total{From="REMOTE_PEER_NODE_ID"}
-
-# name: "etcd_network_peer_round_trip_time_seconds"
-# description: "Round-Trip-Time histogram between peers."
-# type: "histogram"
-etcd_network_peer_round_trip_time_seconds_bucket{To="REMOTE_PEER_NODE_ID",le="+Inf"}
-etcd_network_peer_round_trip_time_seconds_bucket{To="REMOTE_PEER_NODE_ID",le="0.0001"}
-etcd_network_peer_round_trip_time_seconds_bucket{To="REMOTE_PEER_NODE_ID",le="0.0002"}
-etcd_network_peer_round_trip_time_seconds_bucket{To="REMOTE_PEER_NODE_ID",le="0.0004"}
-etcd_network_peer_round_trip_time_seconds_bucket{To="REMOTE_PEER_NODE_ID",le="0.0008"}
-etcd_network_peer_round_trip_time_seconds_bucket{To="REMOTE_PEER_NODE_ID",le="0.0016"}
-etcd_network_peer_round_trip_time_seconds_bucket{To="REMOTE_PEER_NODE_ID",le="0.0032"}
-etcd_network_peer_round_trip_time_seconds_bucket{To="REMOTE_PEER_NODE_ID",le="0.0064"}
-etcd_network_peer_round_trip_time_seconds_bucket{To="REMOTE_PEER_NODE_ID",le="0.0128"}
-etcd_network_peer_round_trip_time_seconds_bucket{To="REMOTE_PEER_NODE_ID",le="0.0256"}
-etcd_network_peer_round_trip_time_seconds_bucket{To="REMOTE_PEER_NODE_ID",le="0.0512"}
-etcd_network_peer_round_trip_time_seconds_bucket{To="REMOTE_PEER_NODE_ID",le="0.1024"}
-etcd_network_peer_round_trip_time_seconds_bucket{To="REMOTE_PEER_NODE_ID",le="0.2048"}
-etcd_network_peer_round_trip_time_seconds_bucket{To="REMOTE_PEER_NODE_ID",le="0.4096"}
-etcd_network_peer_round_trip_time_seconds_bucket{To="REMOTE_PEER_NODE_ID",le="0.8192"}
-etcd_network_peer_round_trip_time_seconds_count{To="REMOTE_PEER_NODE_ID"}
-etcd_network_peer_round_trip_time_seconds_sum{To="REMOTE_PEER_NODE_ID"}
-
-# name: "etcd_network_peer_sent_bytes_total"
-# description: "The total number of bytes sent to peers."
-# type: "counter"
-etcd_network_peer_sent_bytes_total{To="REMOTE_PEER_NODE_ID"}
-
-# name: "etcd_server_has_leader"
-# description: "Whether or not a leader exists. 1 is existence, 0 is not."
-# type: "gauge"
-etcd_server_has_leader
-
-# name: "etcd_server_leader_changes_seen_total"
-# description: "The number of leader changes seen."
-# type: "counter"
-etcd_server_leader_changes_seen_total
-
-# name: "etcd_server_proposals_applied_total"
-# description: "The total number of consensus proposals applied."
-# type: "gauge"
-etcd_server_proposals_applied_total
-
-# name: "etcd_server_proposals_committed_total"
-# description: "The total number of consensus proposals committed."
-# type: "gauge"
-etcd_server_proposals_committed_total
-
-# name: "etcd_server_proposals_failed_total"
-# description: "The total number of failed proposals seen."
-# type: "counter"
-etcd_server_proposals_failed_total
-
-# name: "etcd_server_proposals_pending"
-# description: "The current number of pending proposals to commit."
-# type: "gauge"
-etcd_server_proposals_pending
-
-# name: "go_gc_duration_seconds"
-# description: "A summary of the GC invocation durations."
-# type: "summary"
-go_gc_duration_seconds{quantile="0"}
-go_gc_duration_seconds{quantile="0.25"}
-go_gc_duration_seconds{quantile="0.5"}
-go_gc_duration_seconds{quantile="0.75"}
-go_gc_duration_seconds{quantile="1"}
-go_gc_duration_seconds_sum
-go_gc_duration_seconds_count
-
-# name: "go_goroutines"
-# description: "Number of goroutines that currently exist."
-# type: "gauge"
-go_goroutines
-
-# name: "go_memstats_alloc_bytes"
-# description: "Number of bytes allocated and still in use."
-# type: "gauge"
-go_memstats_alloc_bytes
-
-# name: "go_memstats_alloc_bytes_total"
-# description: "Total number of bytes allocated, even if freed."
-# type: "counter"
-go_memstats_alloc_bytes_total
-
-# name: "go_memstats_buck_hash_sys_bytes"
-# description: "Number of bytes used by the profiling bucket hash table."
-# type: "gauge"
-go_memstats_buck_hash_sys_bytes
-
-# name: "go_memstats_frees_total"
-# description: "Total number of frees."
-# type: "counter"
-go_memstats_frees_total
-
-# name: "go_memstats_gc_sys_bytes"
-# description: "Number of bytes used for garbage collection system metadata."
-# type: "gauge"
-go_memstats_gc_sys_bytes
-
-# name: "go_memstats_heap_alloc_bytes"
-# description: "Number of heap bytes allocated and still in use."
-# type: "gauge"
-go_memstats_heap_alloc_bytes
-
-# name: "go_memstats_heap_idle_bytes"
-# description: "Number of heap bytes waiting to be used."
-# type: "gauge"
-go_memstats_heap_idle_bytes
-
-# name: "go_memstats_heap_inuse_bytes"
-# description: "Number of heap bytes that are in use."
-# type: "gauge"
-go_memstats_heap_inuse_bytes
-
-# name: "go_memstats_heap_objects"
-# description: "Number of allocated objects."
-# type: "gauge"
-go_memstats_heap_objects
-
-# name: "go_memstats_heap_released_bytes_total"
-# description: "Total number of heap bytes released to OS."
-# type: "counter"
-go_memstats_heap_released_bytes_total
-
-# name: "go_memstats_heap_sys_bytes"
-# description: "Number of heap bytes obtained from system."
-# type: "gauge"
-go_memstats_heap_sys_bytes
-
-# name: "go_memstats_last_gc_time_seconds"
-# description: "Number of seconds since 1970 of last garbage collection."
-# type: "gauge"
-go_memstats_last_gc_time_seconds
-
-# name: "go_memstats_lookups_total"
-# description: "Total number of pointer lookups."
-# type: "counter"
-go_memstats_lookups_total
-
-# name: "go_memstats_mallocs_total"
-# description: "Total number of mallocs."
-# type: "counter"
-go_memstats_mallocs_total
-
-# name: "go_memstats_mcache_inuse_bytes"
-# description: "Number of bytes in use by mcache structures."
-# type: "gauge"
-go_memstats_mcache_inuse_bytes
-
-# name: "go_memstats_mcache_sys_bytes"
-# description: "Number of bytes used for mcache structures obtained from system."
-# type: "gauge"
-go_memstats_mcache_sys_bytes
-
-# name: "go_memstats_mspan_inuse_bytes"
-# description: "Number of bytes in use by mspan structures."
-# type: "gauge"
-go_memstats_mspan_inuse_bytes
-
-# name: "go_memstats_mspan_sys_bytes"
-# description: "Number of bytes used for mspan structures obtained from system."
-# type: "gauge"
-go_memstats_mspan_sys_bytes
-
-# name: "go_memstats_next_gc_bytes"
-# description: "Number of heap bytes when next garbage collection will take place."
-# type: "gauge"
-go_memstats_next_gc_bytes
-
-# name: "go_memstats_other_sys_bytes"
-# description: "Number of bytes used for other system allocations."
-# type: "gauge"
-go_memstats_other_sys_bytes
-
-# name: "go_memstats_stack_inuse_bytes"
-# description: "Number of bytes in use by the stack allocator."
-# type: "gauge"
-go_memstats_stack_inuse_bytes
-
-# name: "go_memstats_stack_sys_bytes"
-# description: "Number of bytes obtained from system for stack allocator."
-# type: "gauge"
-go_memstats_stack_sys_bytes
-
-# name: "go_memstats_sys_bytes"
-# description: "Number of bytes obtained by system. Sum of all system allocations."
-# type: "gauge"
-go_memstats_sys_bytes
-
-# name: "grpc_server_handled_total"
-# description: "Total number of RPCs completed on the server, regardless of success or failure."
-# type: "counter"
-# gRPC codes: 
-#  - "OK"
-#  - "Unavailable"
-grpc_server_handled_total{grpc_code="CODE",grpc_method="DeleteRange",grpc_service="etcdserverpb.KV",grpc_type="unary"}
-grpc_server_handled_total{grpc_code="CODE",grpc_method="Put",grpc_service="etcdserverpb.KV",grpc_type="unary"}
-grpc_server_handled_total{grpc_code="CODE",grpc_method="Range",grpc_service="etcdserverpb.KV",grpc_type="unary"}
-grpc_server_handled_total{grpc_code="CODE",grpc_method="Watch",grpc_service="etcdserverpb.Watch",grpc_type="bidi_stream"}
-
-# name: "grpc_server_msg_received_total"
-# description: "Total number of RPC stream messages received on the server."
-# type: "counter"
-grpc_server_msg_received_total{grpc_method="DeleteRange",grpc_service="etcdserverpb.KV",grpc_type="unary"}
-grpc_server_msg_received_total{grpc_method="Put",grpc_service="etcdserverpb.KV",grpc_type="unary"}
-grpc_server_msg_received_total{grpc_method="Range",grpc_service="etcdserverpb.KV",grpc_type="unary"}
-grpc_server_msg_received_total{grpc_method="Watch",grpc_service="etcdserverpb.Watch",grpc_type="bidi_stream"}
-
-# name: "grpc_server_msg_sent_total"
-# description: "Total number of gRPC stream messages sent by the server."
-# type: "counter"
-grpc_server_msg_sent_total{grpc_method="DeleteRange",grpc_service="etcdserverpb.KV",grpc_type="unary"}
-grpc_server_msg_sent_total{grpc_method="Put",grpc_service="etcdserverpb.KV",grpc_type="unary"}
-grpc_server_msg_sent_total{grpc_method="Range",grpc_service="etcdserverpb.KV",grpc_type="unary"}
-grpc_server_msg_sent_total{grpc_method="Watch",grpc_service="etcdserverpb.Watch",grpc_type="bidi_stream"}
-
-# name: "grpc_server_started_total"
-# description: "Total number of RPCs started on the server."
-# type: "counter"
-grpc_server_started_total{grpc_method="DeleteRange",grpc_service="etcdserverpb.KV",grpc_type="unary"}
-grpc_server_started_total{grpc_method="Put",grpc_service="etcdserverpb.KV",grpc_type="unary"}
-grpc_server_started_total{grpc_method="Range",grpc_service="etcdserverpb.KV",grpc_type="unary"}
-grpc_server_started_total{grpc_method="Watch",grpc_service="etcdserverpb.Watch",grpc_type="bidi_stream"}
-
-# name: "http_request_duration_microseconds"
-# description: "The HTTP request latencies in microseconds."
-# type: "summary"
-http_request_duration_microseconds{handler="prometheus",quantile="0.5"}
-http_request_duration_microseconds{handler="prometheus",quantile="0.9"}
-http_request_duration_microseconds{handler="prometheus",quantile="0.99"}
-http_request_duration_microseconds_sum{handler="prometheus"}
-http_request_duration_microseconds_count{handler="prometheus"}
-
-# name: "http_request_size_bytes"
-# description: "The HTTP request sizes in bytes."
-# type: "summary"
-http_request_size_bytes{handler="prometheus",quantile="0.5"}
-http_request_size_bytes{handler="prometheus",quantile="0.9"}
-http_request_size_bytes{handler="prometheus",quantile="0.99"}
-http_request_size_bytes_sum{handler="prometheus"}
-http_request_size_bytes_count{handler="prometheus"}
-
-# name: "http_response_size_bytes"
-# description: "The HTTP response sizes in bytes."
-# type: "summary"
-http_response_size_bytes{handler="prometheus",quantile="0.5"}
-http_response_size_bytes{handler="prometheus",quantile="0.9"}
-http_response_size_bytes{handler="prometheus",quantile="0.99"}
-http_response_size_bytes_sum{handler="prometheus"}
-http_response_size_bytes_count{handler="prometheus"}
-

Documentation/metrics/v3.1.10

@@ -1,511 +0,0 @@
-# server version: unknown
-
-# name: "etcd_debugging_mvcc_db_compaction_pause_duration_milliseconds"
-# description: "Bucketed histogram of db compaction pause duration."
-# type: "histogram"
-etcd_debugging_mvcc_db_compaction_pause_duration_milliseconds_bucket{le="1"}
-etcd_debugging_mvcc_db_compaction_pause_duration_milliseconds_bucket{le="2"}
-etcd_debugging_mvcc_db_compaction_pause_duration_milliseconds_bucket{le="4"}
-etcd_debugging_mvcc_db_compaction_pause_duration_milliseconds_bucket{le="8"}
-etcd_debugging_mvcc_db_compaction_pause_duration_milliseconds_bucket{le="16"}
-etcd_debugging_mvcc_db_compaction_pause_duration_milliseconds_bucket{le="32"}
-etcd_debugging_mvcc_db_compaction_pause_duration_milliseconds_bucket{le="64"}
-etcd_debugging_mvcc_db_compaction_pause_duration_milliseconds_bucket{le="128"}
-etcd_debugging_mvcc_db_compaction_pause_duration_milliseconds_bucket{le="256"}
-etcd_debugging_mvcc_db_compaction_pause_duration_milliseconds_bucket{le="512"}
-etcd_debugging_mvcc_db_compaction_pause_duration_milliseconds_bucket{le="1024"}
-etcd_debugging_mvcc_db_compaction_pause_duration_milliseconds_bucket{le="2048"}
-etcd_debugging_mvcc_db_compaction_pause_duration_milliseconds_bucket{le="4096"}
-etcd_debugging_mvcc_db_compaction_pause_duration_milliseconds_bucket{le="+Inf"}
-etcd_debugging_mvcc_db_compaction_pause_duration_milliseconds_sum
-etcd_debugging_mvcc_db_compaction_pause_duration_milliseconds_count
-
-# name: "etcd_debugging_mvcc_db_compaction_total_duration_milliseconds"
-# description: "Bucketed histogram of db compaction total duration."
-# type: "histogram"
-etcd_debugging_mvcc_db_compaction_total_duration_milliseconds_bucket{le="100"}
-etcd_debugging_mvcc_db_compaction_total_duration_milliseconds_bucket{le="200"}
-etcd_debugging_mvcc_db_compaction_total_duration_milliseconds_bucket{le="400"}
-etcd_debugging_mvcc_db_compaction_total_duration_milliseconds_bucket{le="800"}
-etcd_debugging_mvcc_db_compaction_total_duration_milliseconds_bucket{le="1600"}
-etcd_debugging_mvcc_db_compaction_total_duration_milliseconds_bucket{le="3200"}
-etcd_debugging_mvcc_db_compaction_total_duration_milliseconds_bucket{le="6400"}
-etcd_debugging_mvcc_db_compaction_total_duration_milliseconds_bucket{le="12800"}
-etcd_debugging_mvcc_db_compaction_total_duration_milliseconds_bucket{le="25600"}
-etcd_debugging_mvcc_db_compaction_total_duration_milliseconds_bucket{le="51200"}
-etcd_debugging_mvcc_db_compaction_total_duration_milliseconds_bucket{le="102400"}
-etcd_debugging_mvcc_db_compaction_total_duration_milliseconds_bucket{le="204800"}
-etcd_debugging_mvcc_db_compaction_total_duration_milliseconds_bucket{le="409600"}
-etcd_debugging_mvcc_db_compaction_total_duration_milliseconds_bucket{le="819200"}
-etcd_debugging_mvcc_db_compaction_total_duration_milliseconds_bucket{le="+Inf"}
-etcd_debugging_mvcc_db_compaction_total_duration_milliseconds_sum
-etcd_debugging_mvcc_db_compaction_total_duration_milliseconds_count
-
-# name: "etcd_debugging_mvcc_db_total_size_in_bytes"
-# description: "Total size of the underlying database in bytes."
-# type: "gauge"
-etcd_debugging_mvcc_db_total_size_in_bytes
-
-# name: "etcd_debugging_mvcc_delete_total"
-# description: "Total number of deletes seen by this member."
-# type: "counter"
-etcd_debugging_mvcc_delete_total
-
-# name: "etcd_debugging_mvcc_events_total"
-# description: "Total number of events sent by this member."
-# type: "counter"
-etcd_debugging_mvcc_events_total
-
-# name: "etcd_debugging_mvcc_index_compaction_pause_duration_milliseconds"
-# description: "Bucketed histogram of index compaction pause duration."
-# type: "histogram"
-etcd_debugging_mvcc_index_compaction_pause_duration_milliseconds_bucket{le="0.5"}
-etcd_debugging_mvcc_index_compaction_pause_duration_milliseconds_bucket{le="1"}
-etcd_debugging_mvcc_index_compaction_pause_duration_milliseconds_bucket{le="2"}
-etcd_debugging_mvcc_index_compaction_pause_duration_milliseconds_bucket{le="4"}
-etcd_debugging_mvcc_index_compaction_pause_duration_milliseconds_bucket{le="8"}
-etcd_debugging_mvcc_index_compaction_pause_duration_milliseconds_bucket{le="16"}
-etcd_debugging_mvcc_index_compaction_pause_duration_milliseconds_bucket{le="32"}
-etcd_debugging_mvcc_index_compaction_pause_duration_milliseconds_bucket{le="64"}
-etcd_debugging_mvcc_index_compaction_pause_duration_milliseconds_bucket{le="128"}
-etcd_debugging_mvcc_index_compaction_pause_duration_milliseconds_bucket{le="256"}
-etcd_debugging_mvcc_index_compaction_pause_duration_milliseconds_bucket{le="512"}
-etcd_debugging_mvcc_index_compaction_pause_duration_milliseconds_bucket{le="1024"}
-etcd_debugging_mvcc_index_compaction_pause_duration_milliseconds_bucket{le="+Inf"}
-etcd_debugging_mvcc_index_compaction_pause_duration_milliseconds_sum
-etcd_debugging_mvcc_index_compaction_pause_duration_milliseconds_count
-
-# name: "etcd_debugging_mvcc_keys_total"
-# description: "Total number of keys."
-# type: "gauge"
-etcd_debugging_mvcc_keys_total
-
-# name: "etcd_debugging_mvcc_pending_events_total"
-# description: "Total number of pending events to be sent."
-# type: "gauge"
-etcd_debugging_mvcc_pending_events_total
-
-# name: "etcd_debugging_mvcc_put_total"
-# description: "Total number of puts seen by this member."
-# type: "counter"
-etcd_debugging_mvcc_put_total
-
-# name: "etcd_debugging_mvcc_range_total"
-# description: "Total number of ranges seen by this member."
-# type: "counter"
-etcd_debugging_mvcc_range_total
-
-# name: "etcd_debugging_mvcc_slow_watcher_total"
-# description: "Total number of unsynced slow watchers."
-# type: "gauge"
-etcd_debugging_mvcc_slow_watcher_total
-
-# name: "etcd_debugging_mvcc_txn_total"
-# description: "Total number of txns seen by this member."
-# type: "counter"
-etcd_debugging_mvcc_txn_total
-
-# name: "etcd_debugging_mvcc_watch_stream_total"
-# description: "Total number of watch streams."
-# type: "gauge"
-etcd_debugging_mvcc_watch_stream_total
-
-# name: "etcd_debugging_mvcc_watcher_total"
-# description: "Total number of watchers."
-# type: "gauge"
-etcd_debugging_mvcc_watcher_total
-
-# name: "etcd_debugging_snap_save_marshalling_duration_seconds"
-# description: "The marshalling cost distributions of save called by snapshot."
-# type: "histogram"
-etcd_debugging_snap_save_marshalling_duration_seconds_bucket{le="0.001"}
-etcd_debugging_snap_save_marshalling_duration_seconds_bucket{le="0.002"}
-etcd_debugging_snap_save_marshalling_duration_seconds_bucket{le="0.004"}
-etcd_debugging_snap_save_marshalling_duration_seconds_bucket{le="0.008"}
-etcd_debugging_snap_save_marshalling_duration_seconds_bucket{le="0.016"}
-etcd_debugging_snap_save_marshalling_duration_seconds_bucket{le="0.032"}
-etcd_debugging_snap_save_marshalling_duration_seconds_bucket{le="0.064"}
-etcd_debugging_snap_save_marshalling_duration_seconds_bucket{le="0.128"}
-etcd_debugging_snap_save_marshalling_duration_seconds_bucket{le="0.256"}
-etcd_debugging_snap_save_marshalling_duration_seconds_bucket{le="0.512"}
-etcd_debugging_snap_save_marshalling_duration_seconds_bucket{le="1.024"}
-etcd_debugging_snap_save_marshalling_duration_seconds_bucket{le="2.048"}
-etcd_debugging_snap_save_marshalling_duration_seconds_bucket{le="4.096"}
-etcd_debugging_snap_save_marshalling_duration_seconds_bucket{le="8.192"}
-etcd_debugging_snap_save_marshalling_duration_seconds_bucket{le="+Inf"}
-etcd_debugging_snap_save_marshalling_duration_seconds_sum
-etcd_debugging_snap_save_marshalling_duration_seconds_count
-
-# name: "etcd_debugging_snap_save_total_duration_seconds"
-# description: "The total latency distributions of save called by snapshot."
-# type: "histogram"
-etcd_debugging_snap_save_total_duration_seconds_bucket{le="0.001"}
-etcd_debugging_snap_save_total_duration_seconds_bucket{le="0.002"}
-etcd_debugging_snap_save_total_duration_seconds_bucket{le="0.004"}
-etcd_debugging_snap_save_total_duration_seconds_bucket{le="0.008"}
-etcd_debugging_snap_save_total_duration_seconds_bucket{le="0.016"}
-etcd_debugging_snap_save_total_duration_seconds_bucket{le="0.032"}
-etcd_debugging_snap_save_total_duration_seconds_bucket{le="0.064"}
-etcd_debugging_snap_save_total_duration_seconds_bucket{le="0.128"}
-etcd_debugging_snap_save_total_duration_seconds_bucket{le="0.256"}
-etcd_debugging_snap_save_total_duration_seconds_bucket{le="0.512"}
-etcd_debugging_snap_save_total_duration_seconds_bucket{le="1.024"}
-etcd_debugging_snap_save_total_duration_seconds_bucket{le="2.048"}
-etcd_debugging_snap_save_total_duration_seconds_bucket{le="4.096"}
-etcd_debugging_snap_save_total_duration_seconds_bucket{le="8.192"}
-etcd_debugging_snap_save_total_duration_seconds_bucket{le="+Inf"}
-etcd_debugging_snap_save_total_duration_seconds_sum
-etcd_debugging_snap_save_total_duration_seconds_count
-
-# name: "etcd_debugging_store_expires_total"
-# description: "Total number of expired keys."
-# type: "counter"
-etcd_debugging_store_expires_total
-
-# name: "etcd_debugging_store_reads_total"
-# description: "Total number of reads action by (get/getRecursive), local to this member."
-# type: "counter"
-etcd_debugging_store_reads_total{action="getRecursive"}
-
-# name: "etcd_debugging_store_watch_requests_total"
-# description: "Total number of incoming watch requests (new or reestablished)."
-# type: "counter"
-etcd_debugging_store_watch_requests_total
-
-# name: "etcd_debugging_store_watchers"
-# description: "Count of currently active watchers."
-# type: "gauge"
-etcd_debugging_store_watchers
-
-# name: "etcd_debugging_store_writes_total"
-# description: "Total number of writes (e.g. set/compareAndDelete) seen by this member."
-# type: "counter"
-etcd_debugging_store_writes_total{action="create"}
-etcd_debugging_store_writes_total{action="set"}
-
-# name: "etcd_disk_backend_commit_duration_seconds"
-# description: "The latency distributions of commit called by backend."
-# type: "histogram"
-etcd_disk_backend_commit_duration_seconds_bucket{le="0.001"}
-etcd_disk_backend_commit_duration_seconds_bucket{le="0.002"}
-etcd_disk_backend_commit_duration_seconds_bucket{le="0.004"}
-etcd_disk_backend_commit_duration_seconds_bucket{le="0.008"}
-etcd_disk_backend_commit_duration_seconds_bucket{le="0.016"}
-etcd_disk_backend_commit_duration_seconds_bucket{le="0.032"}
-etcd_disk_backend_commit_duration_seconds_bucket{le="0.064"}
-etcd_disk_backend_commit_duration_seconds_bucket{le="0.128"}
-etcd_disk_backend_commit_duration_seconds_bucket{le="0.256"}
-etcd_disk_backend_commit_duration_seconds_bucket{le="0.512"}
-etcd_disk_backend_commit_duration_seconds_bucket{le="1.024"}
-etcd_disk_backend_commit_duration_seconds_bucket{le="2.048"}
-etcd_disk_backend_commit_duration_seconds_bucket{le="4.096"}
-etcd_disk_backend_commit_duration_seconds_bucket{le="8.192"}
-etcd_disk_backend_commit_duration_seconds_bucket{le="+Inf"}
-etcd_disk_backend_commit_duration_seconds_sum
-etcd_disk_backend_commit_duration_seconds_count
-
-# name: "etcd_disk_wal_fsync_duration_seconds"
-# description: "The latency distributions of fsync called by wal."
-# type: "histogram"
-etcd_disk_wal_fsync_duration_seconds_bucket{le="0.001"}
-etcd_disk_wal_fsync_duration_seconds_bucket{le="0.002"}
-etcd_disk_wal_fsync_duration_seconds_bucket{le="0.004"}
-etcd_disk_wal_fsync_duration_seconds_bucket{le="0.008"}
-etcd_disk_wal_fsync_duration_seconds_bucket{le="0.016"}
-etcd_disk_wal_fsync_duration_seconds_bucket{le="0.032"}
-etcd_disk_wal_fsync_duration_seconds_bucket{le="0.064"}
-etcd_disk_wal_fsync_duration_seconds_bucket{le="0.128"}
-etcd_disk_wal_fsync_duration_seconds_bucket{le="0.256"}
-etcd_disk_wal_fsync_duration_seconds_bucket{le="0.512"}
-etcd_disk_wal_fsync_duration_seconds_bucket{le="1.024"}
-etcd_disk_wal_fsync_duration_seconds_bucket{le="2.048"}
-etcd_disk_wal_fsync_duration_seconds_bucket{le="4.096"}
-etcd_disk_wal_fsync_duration_seconds_bucket{le="8.192"}
-etcd_disk_wal_fsync_duration_seconds_bucket{le="+Inf"}
-etcd_disk_wal_fsync_duration_seconds_sum
-etcd_disk_wal_fsync_duration_seconds_count
-
-# name: "etcd_grpc_proxy_cache_hits_total"
-# description: "Total number of cache hits"
-# type: "gauge"
-etcd_grpc_proxy_cache_hits_total
-
-# name: "etcd_grpc_proxy_cache_misses_total"
-# description: "Total number of cache misses"
-# type: "gauge"
-etcd_grpc_proxy_cache_misses_total
-
-# name: "etcd_grpc_proxy_events_coalescing_total"
-# description: "Total number of events coalescing"
-# type: "counter"
-etcd_grpc_proxy_events_coalescing_total
-
-# name: "etcd_grpc_proxy_watchers_coalescing_total"
-# description: "Total number of current watchers coalescing"
-# type: "gauge"
-etcd_grpc_proxy_watchers_coalescing_total
-
-# name: "etcd_network_client_grpc_received_bytes_total"
-# description: "The total number of bytes received from grpc clients."
-# type: "counter"
-etcd_network_client_grpc_received_bytes_total
-
-# name: "etcd_network_client_grpc_sent_bytes_total"
-# description: "The total number of bytes sent to grpc clients."
-# type: "counter"
-etcd_network_client_grpc_sent_bytes_total
-
-# name: "etcd_network_peer_received_bytes_total"
-# description: "The total number of bytes received from peers."
-# type: "counter"
-etcd_network_peer_received_bytes_total{From="REMOTE_PEER_NODE_ID"}
-
-# name: "etcd_network_peer_round_trip_time_seconds"
-# description: "Round-Trip-Time histogram between peers."
-# type: "histogram"
-etcd_network_peer_round_trip_time_seconds_bucket{To="REMOTE_PEER_NODE_ID",le="+Inf"}
-etcd_network_peer_round_trip_time_seconds_bucket{To="REMOTE_PEER_NODE_ID",le="0.0001"}
-etcd_network_peer_round_trip_time_seconds_bucket{To="REMOTE_PEER_NODE_ID",le="0.0002"}
-etcd_network_peer_round_trip_time_seconds_bucket{To="REMOTE_PEER_NODE_ID",le="0.0004"}
-etcd_network_peer_round_trip_time_seconds_bucket{To="REMOTE_PEER_NODE_ID",le="0.0008"}
-etcd_network_peer_round_trip_time_seconds_bucket{To="REMOTE_PEER_NODE_ID",le="0.0016"}
-etcd_network_peer_round_trip_time_seconds_bucket{To="REMOTE_PEER_NODE_ID",le="0.0032"}
-etcd_network_peer_round_trip_time_seconds_bucket{To="REMOTE_PEER_NODE_ID",le="0.0064"}
-etcd_network_peer_round_trip_time_seconds_bucket{To="REMOTE_PEER_NODE_ID",le="0.0128"}
-etcd_network_peer_round_trip_time_seconds_bucket{To="REMOTE_PEER_NODE_ID",le="0.0256"}
-etcd_network_peer_round_trip_time_seconds_bucket{To="REMOTE_PEER_NODE_ID",le="0.0512"}
-etcd_network_peer_round_trip_time_seconds_bucket{To="REMOTE_PEER_NODE_ID",le="0.1024"}
-etcd_network_peer_round_trip_time_seconds_bucket{To="REMOTE_PEER_NODE_ID",le="0.2048"}
-etcd_network_peer_round_trip_time_seconds_bucket{To="REMOTE_PEER_NODE_ID",le="0.4096"}
-etcd_network_peer_round_trip_time_seconds_bucket{To="REMOTE_PEER_NODE_ID",le="0.8192"}
-etcd_network_peer_round_trip_time_seconds_count{To="REMOTE_PEER_NODE_ID"}
-etcd_network_peer_round_trip_time_seconds_sum{To="REMOTE_PEER_NODE_ID"}
-
-# name: "etcd_network_peer_sent_bytes_total"
-# description: "The total number of bytes sent to peers."
-# type: "counter"
-etcd_network_peer_sent_bytes_total{To="REMOTE_PEER_NODE_ID"}
-
-# name: "etcd_server_has_leader"
-# description: "Whether or not a leader exists. 1 is existence, 0 is not."
-# type: "gauge"
-etcd_server_has_leader
-
-# name: "etcd_server_leader_changes_seen_total"
-# description: "The number of leader changes seen."
-# type: "counter"
-etcd_server_leader_changes_seen_total
-
-# name: "etcd_server_proposals_applied_total"
-# description: "The total number of consensus proposals applied."
-# type: "gauge"
-etcd_server_proposals_applied_total
-
-# name: "etcd_server_proposals_committed_total"
-# description: "The total number of consensus proposals committed."
-# type: "gauge"
-etcd_server_proposals_committed_total
-
-# name: "etcd_server_proposals_failed_total"
-# description: "The total number of failed proposals seen."
-# type: "counter"
-etcd_server_proposals_failed_total
-
-# name: "etcd_server_proposals_pending"
-# description: "The current number of pending proposals to commit."
-# type: "gauge"
-etcd_server_proposals_pending
-
-# name: "go_gc_duration_seconds"
-# description: "A summary of the GC invocation durations."
-# type: "summary"
-go_gc_duration_seconds{quantile="0"}
-go_gc_duration_seconds{quantile="0.25"}
-go_gc_duration_seconds{quantile="0.5"}
-go_gc_duration_seconds{quantile="0.75"}
-go_gc_duration_seconds{quantile="1"}
-go_gc_duration_seconds_sum
-go_gc_duration_seconds_count
-
-# name: "go_goroutines"
-# description: "Number of goroutines that currently exist."
-# type: "gauge"
-go_goroutines
-
-# name: "go_memstats_alloc_bytes"
-# description: "Number of bytes allocated and still in use."
-# type: "gauge"
-go_memstats_alloc_bytes
-
-# name: "go_memstats_alloc_bytes_total"
-# description: "Total number of bytes allocated, even if freed."
-# type: "counter"
-go_memstats_alloc_bytes_total
-
-# name: "go_memstats_buck_hash_sys_bytes"
-# description: "Number of bytes used by the profiling bucket hash table."
-# type: "gauge"
-go_memstats_buck_hash_sys_bytes
-
-# name: "go_memstats_frees_total"
-# description: "Total number of frees."
-# type: "counter"
-go_memstats_frees_total
-
-# name: "go_memstats_gc_sys_bytes"
-# description: "Number of bytes used for garbage collection system metadata."
-# type: "gauge"
-go_memstats_gc_sys_bytes
-
-# name: "go_memstats_heap_alloc_bytes"
-# description: "Number of heap bytes allocated and still in use."
-# type: "gauge"
-go_memstats_heap_alloc_bytes
-
-# name: "go_memstats_heap_idle_bytes"
-# description: "Number of heap bytes waiting to be used."
-# type: "gauge"
-go_memstats_heap_idle_bytes
-
-# name: "go_memstats_heap_inuse_bytes"
-# description: "Number of heap bytes that are in use."
-# type: "gauge"
-go_memstats_heap_inuse_bytes
-
-# name: "go_memstats_heap_objects"
-# description: "Number of allocated objects."
-# type: "gauge"
-go_memstats_heap_objects
-
-# name: "go_memstats_heap_released_bytes_total"
-# description: "Total number of heap bytes released to OS."
-# type: "counter"
-go_memstats_heap_released_bytes_total
-
-# name: "go_memstats_heap_sys_bytes"
-# description: "Number of heap bytes obtained from system."
-# type: "gauge"
-go_memstats_heap_sys_bytes
-
-# name: "go_memstats_last_gc_time_seconds"
-# description: "Number of seconds since 1970 of last garbage collection."
-# type: "gauge"
-go_memstats_last_gc_time_seconds
-
-# name: "go_memstats_lookups_total"
-# description: "Total number of pointer lookups."
-# type: "counter"
-go_memstats_lookups_total
-
-# name: "go_memstats_mallocs_total"
-# description: "Total number of mallocs."
-# type: "counter"
-go_memstats_mallocs_total
-
-# name: "go_memstats_mcache_inuse_bytes"
-# description: "Number of bytes in use by mcache structures."
-# type: "gauge"
-go_memstats_mcache_inuse_bytes
-
-# name: "go_memstats_mcache_sys_bytes"
-# description: "Number of bytes used for mcache structures obtained from system."
-# type: "gauge"
-go_memstats_mcache_sys_bytes
-
-# name: "go_memstats_mspan_inuse_bytes"
-# description: "Number of bytes in use by mspan structures."
-# type: "gauge"
-go_memstats_mspan_inuse_bytes
-
-# name: "go_memstats_mspan_sys_bytes"
-# description: "Number of bytes used for mspan structures obtained from system."
-# type: "gauge"
-go_memstats_mspan_sys_bytes
-
-# name: "go_memstats_next_gc_bytes"
-# description: "Number of heap bytes when next garbage collection will take place."
-# type: "gauge"
-go_memstats_next_gc_bytes
-
-# name: "go_memstats_other_sys_bytes"
-# description: "Number of bytes used for other system allocations."
-# type: "gauge"
-go_memstats_other_sys_bytes
-
-# name: "go_memstats_stack_inuse_bytes"
-# description: "Number of bytes in use by the stack allocator."
-# type: "gauge"
-go_memstats_stack_inuse_bytes
-
-# name: "go_memstats_stack_sys_bytes"
-# description: "Number of bytes obtained from system for stack allocator."
-# type: "gauge"
-go_memstats_stack_sys_bytes
-
-# name: "go_memstats_sys_bytes"
-# description: "Number of bytes obtained by system. Sum of all system allocations."
-# type: "gauge"
-go_memstats_sys_bytes
-
-# name: "grpc_server_handled_total"
-# description: "Total number of RPCs completed on the server, regardless of success or failure."
-# type: "counter"
-# gRPC codes: 
-#  - "Canceled"
-#  - "OK"
-grpc_server_handled_total{grpc_code="CODE",grpc_method="DeleteRange",grpc_service="etcdserverpb.KV",grpc_type="unary"}
-grpc_server_handled_total{grpc_code="CODE",grpc_method="Put",grpc_service="etcdserverpb.KV",grpc_type="unary"}
-grpc_server_handled_total{grpc_code="CODE",grpc_method="Range",grpc_service="etcdserverpb.KV",grpc_type="unary"}
-grpc_server_handled_total{grpc_code="CODE",grpc_method="Watch",grpc_service="etcdserverpb.Watch",grpc_type="bidi_stream"}
-
-# name: "grpc_server_msg_received_total"
-# description: "Total number of RPC stream messages received on the server."
-# type: "counter"
-grpc_server_msg_received_total{grpc_method="DeleteRange",grpc_service="etcdserverpb.KV",grpc_type="unary"}
-grpc_server_msg_received_total{grpc_method="Put",grpc_service="etcdserverpb.KV",grpc_type="unary"}
-grpc_server_msg_received_total{grpc_method="Range",grpc_service="etcdserverpb.KV",grpc_type="unary"}
-grpc_server_msg_received_total{grpc_method="Watch",grpc_service="etcdserverpb.Watch",grpc_type="bidi_stream"}
-
-# name: "grpc_server_msg_sent_total"
-# description: "Total number of gRPC stream messages sent by the server."
-# type: "counter"
-grpc_server_msg_sent_total{grpc_method="DeleteRange",grpc_service="etcdserverpb.KV",grpc_type="unary"}
-grpc_server_msg_sent_total{grpc_method="Put",grpc_service="etcdserverpb.KV",grpc_type="unary"}
-grpc_server_msg_sent_total{grpc_method="Range",grpc_service="etcdserverpb.KV",grpc_type="unary"}
-grpc_server_msg_sent_total{grpc_method="Watch",grpc_service="etcdserverpb.Watch",grpc_type="bidi_stream"}
-
-# name: "grpc_server_started_total"
-# description: "Total number of RPCs started on the server."
-# type: "counter"
-grpc_server_started_total{grpc_method="DeleteRange",grpc_service="etcdserverpb.KV",grpc_type="unary"}
-grpc_server_started_total{grpc_method="Put",grpc_service="etcdserverpb.KV",grpc_type="unary"}
-grpc_server_started_total{grpc_method="Range",grpc_service="etcdserverpb.KV",grpc_type="unary"}
-grpc_server_started_total{grpc_method="Watch",grpc_service="etcdserverpb.Watch",grpc_type="bidi_stream"}
-
-# name: "http_request_duration_microseconds"
-# description: "The HTTP request latencies in microseconds."
-# type: "summary"
-http_request_duration_microseconds{handler="prometheus",quantile="0.5"}
-http_request_duration_microseconds{handler="prometheus",quantile="0.9"}
-http_request_duration_microseconds{handler="prometheus",quantile="0.99"}
-http_request_duration_microseconds_sum{handler="prometheus"}
-http_request_duration_microseconds_count{handler="prometheus"}
-
-# name: "http_request_size_bytes"
-# description: "The HTTP request sizes in bytes."
-# type: "summary"
-http_request_size_bytes{handler="prometheus",quantile="0.5"}
-http_request_size_bytes{handler="prometheus",quantile="0.9"}
-http_request_size_bytes{handler="prometheus",quantile="0.99"}
-http_request_size_bytes_sum{handler="prometheus"}
-http_request_size_bytes_count{handler="prometheus"}
-
-# name: "http_response_size_bytes"
-# description: "The HTTP response sizes in bytes."
-# type: "summary"
-http_response_size_bytes{handler="prometheus",quantile="0.5"}
-http_response_size_bytes{handler="prometheus",quantile="0.9"}
-http_response_size_bytes{handler="prometheus",quantile="0.99"}
-http_response_size_bytes_sum{handler="prometheus"}
-http_response_size_bytes_count{handler="prometheus"}
-

Documentation/metrics/v3.1.11

@@ -1,511 +0,0 @@
-# server version: unknown
-
-# name: "etcd_debugging_mvcc_db_compaction_pause_duration_milliseconds"
-# description: "Bucketed histogram of db compaction pause duration."
-# type: "histogram"
-etcd_debugging_mvcc_db_compaction_pause_duration_milliseconds_bucket{le="1"}
-etcd_debugging_mvcc_db_compaction_pause_duration_milliseconds_bucket{le="2"}
-etcd_debugging_mvcc_db_compaction_pause_duration_milliseconds_bucket{le="4"}
-etcd_debugging_mvcc_db_compaction_pause_duration_milliseconds_bucket{le="8"}
-etcd_debugging_mvcc_db_compaction_pause_duration_milliseconds_bucket{le="16"}
-etcd_debugging_mvcc_db_compaction_pause_duration_milliseconds_bucket{le="32"}
-etcd_debugging_mvcc_db_compaction_pause_duration_milliseconds_bucket{le="64"}
-etcd_debugging_mvcc_db_compaction_pause_duration_milliseconds_bucket{le="128"}
-etcd_debugging_mvcc_db_compaction_pause_duration_milliseconds_bucket{le="256"}
-etcd_debugging_mvcc_db_compaction_pause_duration_milliseconds_bucket{le="512"}
-etcd_debugging_mvcc_db_compaction_pause_duration_milliseconds_bucket{le="1024"}
-etcd_debugging_mvcc_db_compaction_pause_duration_milliseconds_bucket{le="2048"}
-etcd_debugging_mvcc_db_compaction_pause_duration_milliseconds_bucket{le="4096"}
-etcd_debugging_mvcc_db_compaction_pause_duration_milliseconds_bucket{le="+Inf"}
-etcd_debugging_mvcc_db_compaction_pause_duration_milliseconds_sum
-etcd_debugging_mvcc_db_compaction_pause_duration_milliseconds_count
-
-# name: "etcd_debugging_mvcc_db_compaction_total_duration_milliseconds"
-# description: "Bucketed histogram of db compaction total duration."
-# type: "histogram"
-etcd_debugging_mvcc_db_compaction_total_duration_milliseconds_bucket{le="100"}
-etcd_debugging_mvcc_db_compaction_total_duration_milliseconds_bucket{le="200"}
-etcd_debugging_mvcc_db_compaction_total_duration_milliseconds_bucket{le="400"}
-etcd_debugging_mvcc_db_compaction_total_duration_milliseconds_bucket{le="800"}
-etcd_debugging_mvcc_db_compaction_total_duration_milliseconds_bucket{le="1600"}
-etcd_debugging_mvcc_db_compaction_total_duration_milliseconds_bucket{le="3200"}
-etcd_debugging_mvcc_db_compaction_total_duration_milliseconds_bucket{le="6400"}
-etcd_debugging_mvcc_db_compaction_total_duration_milliseconds_bucket{le="12800"}
-etcd_debugging_mvcc_db_compaction_total_duration_milliseconds_bucket{le="25600"}
-etcd_debugging_mvcc_db_compaction_total_duration_milliseconds_bucket{le="51200"}
-etcd_debugging_mvcc_db_compaction_total_duration_milliseconds_bucket{le="102400"}
-etcd_debugging_mvcc_db_compaction_total_duration_milliseconds_bucket{le="204800"}
-etcd_debugging_mvcc_db_compaction_total_duration_milliseconds_bucket{le="409600"}
-etcd_debugging_mvcc_db_compaction_total_duration_milliseconds_bucket{le="819200"}
-etcd_debugging_mvcc_db_compaction_total_duration_milliseconds_bucket{le="+Inf"}
-etcd_debugging_mvcc_db_compaction_total_duration_milliseconds_sum
-etcd_debugging_mvcc_db_compaction_total_duration_milliseconds_count
-
-# name: "etcd_debugging_mvcc_db_total_size_in_bytes"
-# description: "Total size of the underlying database in bytes."
-# type: "gauge"
-etcd_debugging_mvcc_db_total_size_in_bytes
-
-# name: "etcd_debugging_mvcc_delete_total"
-# description: "Total number of deletes seen by this member."
-# type: "counter"
-etcd_debugging_mvcc_delete_total
-
-# name: "etcd_debugging_mvcc_events_total"
-# description: "Total number of events sent by this member."
-# type: "counter"
-etcd_debugging_mvcc_events_total
-
-# name: "etcd_debugging_mvcc_index_compaction_pause_duration_milliseconds"
-# description: "Bucketed histogram of index compaction pause duration."
-# type: "histogram"
-etcd_debugging_mvcc_index_compaction_pause_duration_milliseconds_bucket{le="0.5"}
-etcd_debugging_mvcc_index_compaction_pause_duration_milliseconds_bucket{le="1"}
-etcd_debugging_mvcc_index_compaction_pause_duration_milliseconds_bucket{le="2"}
-etcd_debugging_mvcc_index_compaction_pause_duration_milliseconds_bucket{le="4"}
-etcd_debugging_mvcc_index_compaction_pause_duration_milliseconds_bucket{le="8"}
-etcd_debugging_mvcc_index_compaction_pause_duration_milliseconds_bucket{le="16"}
-etcd_debugging_mvcc_index_compaction_pause_duration_milliseconds_bucket{le="32"}
-etcd_debugging_mvcc_index_compaction_pause_duration_milliseconds_bucket{le="64"}
-etcd_debugging_mvcc_index_compaction_pause_duration_milliseconds_bucket{le="128"}
-etcd_debugging_mvcc_index_compaction_pause_duration_milliseconds_bucket{le="256"}
-etcd_debugging_mvcc_index_compaction_pause_duration_milliseconds_bucket{le="512"}
-etcd_debugging_mvcc_index_compaction_pause_duration_milliseconds_bucket{le="1024"}
-etcd_debugging_mvcc_index_compaction_pause_duration_milliseconds_bucket{le="+Inf"}
-etcd_debugging_mvcc_index_compaction_pause_duration_milliseconds_sum
-etcd_debugging_mvcc_index_compaction_pause_duration_milliseconds_count
-
-# name: "etcd_debugging_mvcc_keys_total"
-# description: "Total number of keys."
-# type: "gauge"
-etcd_debugging_mvcc_keys_total
-
-# name: "etcd_debugging_mvcc_pending_events_total"
-# description: "Total number of pending events to be sent."
-# type: "gauge"
-etcd_debugging_mvcc_pending_events_total
-
-# name: "etcd_debugging_mvcc_put_total"
-# description: "Total number of puts seen by this member."
-# type: "counter"
-etcd_debugging_mvcc_put_total
-
-# name: "etcd_debugging_mvcc_range_total"
-# description: "Total number of ranges seen by this member."
-# type: "counter"
-etcd_debugging_mvcc_range_total
-
-# name: "etcd_debugging_mvcc_slow_watcher_total"
-# description: "Total number of unsynced slow watchers."
-# type: "gauge"
-etcd_debugging_mvcc_slow_watcher_total
-
-# name: "etcd_debugging_mvcc_txn_total"
-# description: "Total number of txns seen by this member."
-# type: "counter"
-etcd_debugging_mvcc_txn_total
-
-# name: "etcd_debugging_mvcc_watch_stream_total"
-# description: "Total number of watch streams."
-# type: "gauge"
-etcd_debugging_mvcc_watch_stream_total
-
-# name: "etcd_debugging_mvcc_watcher_total"
-# description: "Total number of watchers."
-# type: "gauge"
-etcd_debugging_mvcc_watcher_total
-
-# name: "etcd_debugging_snap_save_marshalling_duration_seconds"
-# description: "The marshalling cost distributions of save called by snapshot."
-# type: "histogram"
-etcd_debugging_snap_save_marshalling_duration_seconds_bucket{le="0.001"}
-etcd_debugging_snap_save_marshalling_duration_seconds_bucket{le="0.002"}
-etcd_debugging_snap_save_marshalling_duration_seconds_bucket{le="0.004"}
-etcd_debugging_snap_save_marshalling_duration_seconds_bucket{le="0.008"}
-etcd_debugging_snap_save_marshalling_duration_seconds_bucket{le="0.016"}
-etcd_debugging_snap_save_marshalling_duration_seconds_bucket{le="0.032"}
-etcd_debugging_snap_save_marshalling_duration_seconds_bucket{le="0.064"}
-etcd_debugging_snap_save_marshalling_duration_seconds_bucket{le="0.128"}
-etcd_debugging_snap_save_marshalling_duration_seconds_bucket{le="0.256"}
-etcd_debugging_snap_save_marshalling_duration_seconds_bucket{le="0.512"}
-etcd_debugging_snap_save_marshalling_duration_seconds_bucket{le="1.024"}
-etcd_debugging_snap_save_marshalling_duration_seconds_bucket{le="2.048"}
-etcd_debugging_snap_save_marshalling_duration_seconds_bucket{le="4.096"}
-etcd_debugging_snap_save_marshalling_duration_seconds_bucket{le="8.192"}
-etcd_debugging_snap_save_marshalling_duration_seconds_bucket{le="+Inf"}
-etcd_debugging_snap_save_marshalling_duration_seconds_sum
-etcd_debugging_snap_save_marshalling_duration_seconds_count
-
-# name: "etcd_debugging_snap_save_total_duration_seconds"
-# description: "The total latency distributions of save called by snapshot."
-# type: "histogram"
-etcd_debugging_snap_save_total_duration_seconds_bucket{le="0.001"}
-etcd_debugging_snap_save_total_duration_seconds_bucket{le="0.002"}
-etcd_debugging_snap_save_total_duration_seconds_bucket{le="0.004"}
-etcd_debugging_snap_save_total_duration_seconds_bucket{le="0.008"}
-etcd_debugging_snap_save_total_duration_seconds_bucket{le="0.016"}
-etcd_debugging_snap_save_total_duration_seconds_bucket{le="0.032"}
-etcd_debugging_snap_save_total_duration_seconds_bucket{le="0.064"}
-etcd_debugging_snap_save_total_duration_seconds_bucket{le="0.128"}
-etcd_debugging_snap_save_total_duration_seconds_bucket{le="0.256"}
-etcd_debugging_snap_save_total_duration_seconds_bucket{le="0.512"}
-etcd_debugging_snap_save_total_duration_seconds_bucket{le="1.024"}
-etcd_debugging_snap_save_total_duration_seconds_bucket{le="2.048"}
-etcd_debugging_snap_save_total_duration_seconds_bucket{le="4.096"}
-etcd_debugging_snap_save_total_duration_seconds_bucket{le="8.192"}
-etcd_debugging_snap_save_total_duration_seconds_bucket{le="+Inf"}
-etcd_debugging_snap_save_total_duration_seconds_sum
-etcd_debugging_snap_save_total_duration_seconds_count
-
-# name: "etcd_debugging_store_expires_total"
-# description: "Total number of expired keys."
-# type: "counter"
-etcd_debugging_store_expires_total
-
-# name: "etcd_debugging_store_reads_total"
-# description: "Total number of reads action by (get/getRecursive), local to this member."
-# type: "counter"
-etcd_debugging_store_reads_total{action="getRecursive"}
-
-# name: "etcd_debugging_store_watch_requests_total"
-# description: "Total number of incoming watch requests (new or reestablished)."
-# type: "counter"
-etcd_debugging_store_watch_requests_total
-
-# name: "etcd_debugging_store_watchers"
-# description: "Count of currently active watchers."
-# type: "gauge"
-etcd_debugging_store_watchers
-
-# name: "etcd_debugging_store_writes_total"
-# description: "Total number of writes (e.g. set/compareAndDelete) seen by this member."
-# type: "counter"
-etcd_debugging_store_writes_total{action="create"}
-etcd_debugging_store_writes_total{action="set"}
-
-# name: "etcd_disk_backend_commit_duration_seconds"
-# description: "The latency distributions of commit called by backend."
-# type: "histogram"
-etcd_disk_backend_commit_duration_seconds_bucket{le="0.001"}
-etcd_disk_backend_commit_duration_seconds_bucket{le="0.002"}
-etcd_disk_backend_commit_duration_seconds_bucket{le="0.004"}
-etcd_disk_backend_commit_duration_seconds_bucket{le="0.008"}
-etcd_disk_backend_commit_duration_seconds_bucket{le="0.016"}
-etcd_disk_backend_commit_duration_seconds_bucket{le="0.032"}
-etcd_disk_backend_commit_duration_seconds_bucket{le="0.064"}
-etcd_disk_backend_commit_duration_seconds_bucket{le="0.128"}
-etcd_disk_backend_commit_duration_seconds_bucket{le="0.256"}
-etcd_disk_backend_commit_duration_seconds_bucket{le="0.512"}
-etcd_disk_backend_commit_duration_seconds_bucket{le="1.024"}
-etcd_disk_backend_commit_duration_seconds_bucket{le="2.048"}
-etcd_disk_backend_commit_duration_seconds_bucket{le="4.096"}
-etcd_disk_backend_commit_duration_seconds_bucket{le="8.192"}
-etcd_disk_backend_commit_duration_seconds_bucket{le="+Inf"}
-etcd_disk_backend_commit_duration_seconds_sum
-etcd_disk_backend_commit_duration_seconds_count
-
-# name: "etcd_disk_wal_fsync_duration_seconds"
-# description: "The latency distributions of fsync called by wal."
-# type: "histogram"
-etcd_disk_wal_fsync_duration_seconds_bucket{le="0.001"}
-etcd_disk_wal_fsync_duration_seconds_bucket{le="0.002"}
-etcd_disk_wal_fsync_duration_seconds_bucket{le="0.004"}
-etcd_disk_wal_fsync_duration_seconds_bucket{le="0.008"}
-etcd_disk_wal_fsync_duration_seconds_bucket{le="0.016"}
-etcd_disk_wal_fsync_duration_seconds_bucket{le="0.032"}
-etcd_disk_wal_fsync_duration_seconds_bucket{le="0.064"}
-etcd_disk_wal_fsync_duration_seconds_bucket{le="0.128"}
-etcd_disk_wal_fsync_duration_seconds_bucket{le="0.256"}
-etcd_disk_wal_fsync_duration_seconds_bucket{le="0.512"}
-etcd_disk_wal_fsync_duration_seconds_bucket{le="1.024"}
-etcd_disk_wal_fsync_duration_seconds_bucket{le="2.048"}
-etcd_disk_wal_fsync_duration_seconds_bucket{le="4.096"}
-etcd_disk_wal_fsync_duration_seconds_bucket{le="8.192"}
-etcd_disk_wal_fsync_duration_seconds_bucket{le="+Inf"}
-etcd_disk_wal_fsync_duration_seconds_sum
-etcd_disk_wal_fsync_duration_seconds_count
-
-# name: "etcd_grpc_proxy_cache_hits_total"
-# description: "Total number of cache hits"
-# type: "gauge"
-etcd_grpc_proxy_cache_hits_total
-
-# name: "etcd_grpc_proxy_cache_misses_total"
-# description: "Total number of cache misses"
-# type: "gauge"
-etcd_grpc_proxy_cache_misses_total
-
-# name: "etcd_grpc_proxy_events_coalescing_total"
-# description: "Total number of events coalescing"
-# type: "counter"
-etcd_grpc_proxy_events_coalescing_total
-
-# name: "etcd_grpc_proxy_watchers_coalescing_total"
-# description: "Total number of current watchers coalescing"
-# type: "gauge"
-etcd_grpc_proxy_watchers_coalescing_total
-
-# name: "etcd_network_client_grpc_received_bytes_total"
-# description: "The total number of bytes received from grpc clients."
-# type: "counter"
-etcd_network_client_grpc_received_bytes_total
-
-# name: "etcd_network_client_grpc_sent_bytes_total"
-# description: "The total number of bytes sent to grpc clients."
-# type: "counter"
-etcd_network_client_grpc_sent_bytes_total
-
-# name: "etcd_network_peer_received_bytes_total"
-# description: "The total number of bytes received from peers."
-# type: "counter"
-etcd_network_peer_received_bytes_total{From="REMOTE_PEER_NODE_ID"}
-
-# name: "etcd_network_peer_round_trip_time_seconds"
-# description: "Round-Trip-Time histogram between peers."
-# type: "histogram"
-etcd_network_peer_round_trip_time_seconds_bucket{To="REMOTE_PEER_NODE_ID",le="+Inf"}
-etcd_network_peer_round_trip_time_seconds_bucket{To="REMOTE_PEER_NODE_ID",le="0.0001"}
-etcd_network_peer_round_trip_time_seconds_bucket{To="REMOTE_PEER_NODE_ID",le="0.0002"}
-etcd_network_peer_round_trip_time_seconds_bucket{To="REMOTE_PEER_NODE_ID",le="0.0004"}
-etcd_network_peer_round_trip_time_seconds_bucket{To="REMOTE_PEER_NODE_ID",le="0.0008"}
-etcd_network_peer_round_trip_time_seconds_bucket{To="REMOTE_PEER_NODE_ID",le="0.0016"}
-etcd_network_peer_round_trip_time_seconds_bucket{To="REMOTE_PEER_NODE_ID",le="0.0032"}
-etcd_network_peer_round_trip_time_seconds_bucket{To="REMOTE_PEER_NODE_ID",le="0.0064"}
-etcd_network_peer_round_trip_time_seconds_bucket{To="REMOTE_PEER_NODE_ID",le="0.0128"}
-etcd_network_peer_round_trip_time_seconds_bucket{To="REMOTE_PEER_NODE_ID",le="0.0256"}
-etcd_network_peer_round_trip_time_seconds_bucket{To="REMOTE_PEER_NODE_ID",le="0.0512"}
-etcd_network_peer_round_trip_time_seconds_bucket{To="REMOTE_PEER_NODE_ID",le="0.1024"}
-etcd_network_peer_round_trip_time_seconds_bucket{To="REMOTE_PEER_NODE_ID",le="0.2048"}
-etcd_network_peer_round_trip_time_seconds_bucket{To="REMOTE_PEER_NODE_ID",le="0.4096"}
-etcd_network_peer_round_trip_time_seconds_bucket{To="REMOTE_PEER_NODE_ID",le="0.8192"}
-etcd_network_peer_round_trip_time_seconds_count{To="REMOTE_PEER_NODE_ID"}
-etcd_network_peer_round_trip_time_seconds_sum{To="REMOTE_PEER_NODE_ID"}
-
-# name: "etcd_network_peer_sent_bytes_total"
-# description: "The total number of bytes sent to peers."
-# type: "counter"
-etcd_network_peer_sent_bytes_total{To="REMOTE_PEER_NODE_ID"}
-
-# name: "etcd_server_has_leader"
-# description: "Whether or not a leader exists. 1 is existence, 0 is not."
-# type: "gauge"
-etcd_server_has_leader
-
-# name: "etcd_server_leader_changes_seen_total"
-# description: "The number of leader changes seen."
-# type: "counter"
-etcd_server_leader_changes_seen_total
-
-# name: "etcd_server_proposals_applied_total"
-# description: "The total number of consensus proposals applied."
-# type: "gauge"
-etcd_server_proposals_applied_total
-
-# name: "etcd_server_proposals_committed_total"
-# description: "The total number of consensus proposals committed."
-# type: "gauge"
-etcd_server_proposals_committed_total
-
-# name: "etcd_server_proposals_failed_total"
-# description: "The total number of failed proposals seen."
-# type: "counter"
-etcd_server_proposals_failed_total
-
-# name: "etcd_server_proposals_pending"
-# description: "The current number of pending proposals to commit."
-# type: "gauge"
-etcd_server_proposals_pending
-
-# name: "go_gc_duration_seconds"
-# description: "A summary of the GC invocation durations."
-# type: "summary"
-go_gc_duration_seconds{quantile="0"}
-go_gc_duration_seconds{quantile="0.25"}
-go_gc_duration_seconds{quantile="0.5"}
-go_gc_duration_seconds{quantile="0.75"}
-go_gc_duration_seconds{quantile="1"}
-go_gc_duration_seconds_sum
-go_gc_duration_seconds_count
-
-# name: "go_goroutines"
-# description: "Number of goroutines that currently exist."
-# type: "gauge"
-go_goroutines
-
-# name: "go_memstats_alloc_bytes"
-# description: "Number of bytes allocated and still in use."
-# type: "gauge"
-go_memstats_alloc_bytes
-
-# name: "go_memstats_alloc_bytes_total"
-# description: "Total number of bytes allocated, even if freed."
-# type: "counter"
-go_memstats_alloc_bytes_total
-
-# name: "go_memstats_buck_hash_sys_bytes"
-# description: "Number of bytes used by the profiling bucket hash table."
-# type: "gauge"
-go_memstats_buck_hash_sys_bytes
-
-# name: "go_memstats_frees_total"
-# description: "Total number of frees."
-# type: "counter"
-go_memstats_frees_total
-
-# name: "go_memstats_gc_sys_bytes"
-# description: "Number of bytes used for garbage collection system metadata."
-# type: "gauge"
-go_memstats_gc_sys_bytes
-
-# name: "go_memstats_heap_alloc_bytes"
-# description: "Number of heap bytes allocated and still in use."
-# type: "gauge"
-go_memstats_heap_alloc_bytes
-
-# name: "go_memstats_heap_idle_bytes"
-# description: "Number of heap bytes waiting to be used."
-# type: "gauge"
-go_memstats_heap_idle_bytes
-
-# name: "go_memstats_heap_inuse_bytes"
-# description: "Number of heap bytes that are in use."
-# type: "gauge"
-go_memstats_heap_inuse_bytes
-
-# name: "go_memstats_heap_objects"
-# description: "Number of allocated objects."
-# type: "gauge"
-go_memstats_heap_objects
-
-# name: "go_memstats_heap_released_bytes_total"
-# description: "Total number of heap bytes released to OS."
-# type: "counter"
-go_memstats_heap_released_bytes_total
-
-# name: "go_memstats_heap_sys_bytes"
-# description: "Number of heap bytes obtained from system."
-# type: "gauge"
-go_memstats_heap_sys_bytes
-
-# name: "go_memstats_last_gc_time_seconds"
-# description: "Number of seconds since 1970 of last garbage collection."
-# type: "gauge"
-go_memstats_last_gc_time_seconds
-
-# name: "go_memstats_lookups_total"
-# description: "Total number of pointer lookups."
-# type: "counter"
-go_memstats_lookups_total
-
-# name: "go_memstats_mallocs_total"
-# description: "Total number of mallocs."
-# type: "counter"
-go_memstats_mallocs_total
-
-# name: "go_memstats_mcache_inuse_bytes"
-# description: "Number of bytes in use by mcache structures."
-# type: "gauge"
-go_memstats_mcache_inuse_bytes
-
-# name: "go_memstats_mcache_sys_bytes"
-# description: "Number of bytes used for mcache structures obtained from system."
-# type: "gauge"
-go_memstats_mcache_sys_bytes
-
-# name: "go_memstats_mspan_inuse_bytes"
-# description: "Number of bytes in use by mspan structures."
-# type: "gauge"
-go_memstats_mspan_inuse_bytes
-
-# name: "go_memstats_mspan_sys_bytes"
-# description: "Number of bytes used for mspan structures obtained from system."
-# type: "gauge"
-go_memstats_mspan_sys_bytes
-
-# name: "go_memstats_next_gc_bytes"
-# description: "Number of heap bytes when next garbage collection will take place."
-# type: "gauge"
-go_memstats_next_gc_bytes
-
-# name: "go_memstats_other_sys_bytes"
-# description: "Number of bytes used for other system allocations."
-# type: "gauge"
-go_memstats_other_sys_bytes
-
-# name: "go_memstats_stack_inuse_bytes"
-# description: "Number of bytes in use by the stack allocator."
-# type: "gauge"
-go_memstats_stack_inuse_bytes
-
-# name: "go_memstats_stack_sys_bytes"
-# description: "Number of bytes obtained from system for stack allocator."
-# type: "gauge"
-go_memstats_stack_sys_bytes
-
-# name: "go_memstats_sys_bytes"
-# description: "Number of bytes obtained by system. Sum of all system allocations."
-# type: "gauge"
-go_memstats_sys_bytes
-
-# name: "grpc_server_handled_total"
-# description: "Total number of RPCs completed on the server, regardless of success or failure."
-# type: "counter"
-# gRPC codes: 
-#  - "OK"
-#  - "Unavailable"
-grpc_server_handled_total{grpc_code="CODE",grpc_method="DeleteRange",grpc_service="etcdserverpb.KV",grpc_type="unary"}
-grpc_server_handled_total{grpc_code="CODE",grpc_method="Put",grpc_service="etcdserverpb.KV",grpc_type="unary"}
-grpc_server_handled_total{grpc_code="CODE",grpc_method="Range",grpc_service="etcdserverpb.KV",grpc_type="unary"}
-grpc_server_handled_total{grpc_code="CODE",grpc_method="Watch",grpc_service="etcdserverpb.Watch",grpc_type="bidi_stream"}
-
-# name: "grpc_server_msg_received_total"
-# description: "Total number of RPC stream messages received on the server."
-# type: "counter"
-grpc_server_msg_received_total{grpc_method="DeleteRange",grpc_service="etcdserverpb.KV",grpc_type="unary"}
-grpc_server_msg_received_total{grpc_method="Put",grpc_service="etcdserverpb.KV",grpc_type="unary"}
-grpc_server_msg_received_total{grpc_method="Range",grpc_service="etcdserverpb.KV",grpc_type="unary"}
-grpc_server_msg_received_total{grpc_method="Watch",grpc_service="etcdserverpb.Watch",grpc_type="bidi_stream"}
-
-# name: "grpc_server_msg_sent_total"
-# description: "Total number of gRPC stream messages sent by the server."
-# type: "counter"
-grpc_server_msg_sent_total{grpc_method="DeleteRange",grpc_service="etcdserverpb.KV",grpc_type="unary"}
-grpc_server_msg_sent_total{grpc_method="Put",grpc_service="etcdserverpb.KV",grpc_type="unary"}
-grpc_server_msg_sent_total{grpc_method="Range",grpc_service="etcdserverpb.KV",grpc_type="unary"}
-grpc_server_msg_sent_total{grpc_method="Watch",grpc_service="etcdserverpb.Watch",grpc_type="bidi_stream"}
-
-# name: "grpc_server_started_total"
-# description: "Total number of RPCs started on the server."
-# type: "counter"
-grpc_server_started_total{grpc_method="DeleteRange",grpc_service="etcdserverpb.KV",grpc_type="unary"}
-grpc_server_started_total{grpc_method="Put",grpc_service="etcdserverpb.KV",grpc_type="unary"}
-grpc_server_started_total{grpc_method="Range",grpc_service="etcdserverpb.KV",grpc_type="unary"}
-grpc_server_started_total{grpc_method="Watch",grpc_service="etcdserverpb.Watch",grpc_type="bidi_stream"}
-
-# name: "http_request_duration_microseconds"
-# description: "The HTTP request latencies in microseconds."
-# type: "summary"
-http_request_duration_microseconds{handler="prometheus",quantile="0.5"}
-http_request_duration_microseconds{handler="prometheus",quantile="0.9"}
-http_request_duration_microseconds{handler="prometheus",quantile="0.99"}
-http_request_duration_microseconds_sum{handler="prometheus"}
-http_request_duration_microseconds_count{handler="prometheus"}
-
-# name: "http_request_size_bytes"
-# description: "The HTTP request sizes in bytes."
-# type: "summary"
-http_request_size_bytes{handler="prometheus",quantile="0.5"}
-http_request_size_bytes{handler="prometheus",quantile="0.9"}
-http_request_size_bytes{handler="prometheus",quantile="0.99"}
-http_request_size_bytes_sum{handler="prometheus"}
-http_request_size_bytes_count{handler="prometheus"}
-
-# name: "http_response_size_bytes"
-# description: "The HTTP response sizes in bytes."
-# type: "summary"
-http_response_size_bytes{handler="prometheus",quantile="0.5"}
-http_response_size_bytes{handler="prometheus",quantile="0.9"}
-http_response_size_bytes{handler="prometheus",quantile="0.99"}
-http_response_size_bytes_sum{handler="prometheus"}
-http_response_size_bytes_count{handler="prometheus"}
-

Documentation/metrics/v3.1.12

@@ -1,511 +0,0 @@
-# server version: unknown
-
-# name: "etcd_debugging_mvcc_db_compaction_pause_duration_milliseconds"
-# description: "Bucketed histogram of db compaction pause duration."
-# type: "histogram"
-etcd_debugging_mvcc_db_compaction_pause_duration_milliseconds_bucket{le="1"}
-etcd_debugging_mvcc_db_compaction_pause_duration_milliseconds_bucket{le="2"}
-etcd_debugging_mvcc_db_compaction_pause_duration_milliseconds_bucket{le="4"}
-etcd_debugging_mvcc_db_compaction_pause_duration_milliseconds_bucket{le="8"}
-etcd_debugging_mvcc_db_compaction_pause_duration_milliseconds_bucket{le="16"}
-etcd_debugging_mvcc_db_compaction_pause_duration_milliseconds_bucket{le="32"}
-etcd_debugging_mvcc_db_compaction_pause_duration_milliseconds_bucket{le="64"}
-etcd_debugging_mvcc_db_compaction_pause_duration_milliseconds_bucket{le="128"}
-etcd_debugging_mvcc_db_compaction_pause_duration_milliseconds_bucket{le="256"}
-etcd_debugging_mvcc_db_compaction_pause_duration_milliseconds_bucket{le="512"}
-etcd_debugging_mvcc_db_compaction_pause_duration_milliseconds_bucket{le="1024"}
-etcd_debugging_mvcc_db_compaction_pause_duration_milliseconds_bucket{le="2048"}
-etcd_debugging_mvcc_db_compaction_pause_duration_milliseconds_bucket{le="4096"}
-etcd_debugging_mvcc_db_compaction_pause_duration_milliseconds_bucket{le="+Inf"}
-etcd_debugging_mvcc_db_compaction_pause_duration_milliseconds_sum
-etcd_debugging_mvcc_db_compaction_pause_duration_milliseconds_count
-
-# name: "etcd_debugging_mvcc_db_compaction_total_duration_milliseconds"
-# description: "Bucketed histogram of db compaction total duration."
-# type: "histogram"
-etcd_debugging_mvcc_db_compaction_total_duration_milliseconds_bucket{le="100"}
-etcd_debugging_mvcc_db_compaction_total_duration_milliseconds_bucket{le="200"}
-etcd_debugging_mvcc_db_compaction_total_duration_milliseconds_bucket{le="400"}
-etcd_debugging_mvcc_db_compaction_total_duration_milliseconds_bucket{le="800"}
-etcd_debugging_mvcc_db_compaction_total_duration_milliseconds_bucket{le="1600"}
-etcd_debugging_mvcc_db_compaction_total_duration_milliseconds_bucket{le="3200"}
-etcd_debugging_mvcc_db_compaction_total_duration_milliseconds_bucket{le="6400"}
-etcd_debugging_mvcc_db_compaction_total_duration_milliseconds_bucket{le="12800"}
-etcd_debugging_mvcc_db_compaction_total_duration_milliseconds_bucket{le="25600"}
-etcd_debugging_mvcc_db_compaction_total_duration_milliseconds_bucket{le="51200"}
-etcd_debugging_mvcc_db_compaction_total_duration_milliseconds_bucket{le="102400"}
-etcd_debugging_mvcc_db_compaction_total_duration_milliseconds_bucket{le="204800"}
-etcd_debugging_mvcc_db_compaction_total_duration_milliseconds_bucket{le="409600"}
-etcd_debugging_mvcc_db_compaction_total_duration_milliseconds_bucket{le="819200"}
-etcd_debugging_mvcc_db_compaction_total_duration_milliseconds_bucket{le="+Inf"}
-etcd_debugging_mvcc_db_compaction_total_duration_milliseconds_sum
-etcd_debugging_mvcc_db_compaction_total_duration_milliseconds_count
-
-# name: "etcd_debugging_mvcc_db_total_size_in_bytes"
-# description: "Total size of the underlying database in bytes."
-# type: "gauge"
-etcd_debugging_mvcc_db_total_size_in_bytes
-
-# name: "etcd_debugging_mvcc_delete_total"
-# description: "Total number of deletes seen by this member."
-# type: "counter"
-etcd_debugging_mvcc_delete_total
-
-# name: "etcd_debugging_mvcc_events_total"
-# description: "Total number of events sent by this member."
-# type: "counter"
-etcd_debugging_mvcc_events_total
-
-# name: "etcd_debugging_mvcc_index_compaction_pause_duration_milliseconds"
-# description: "Bucketed histogram of index compaction pause duration."
-# type: "histogram"
-etcd_debugging_mvcc_index_compaction_pause_duration_milliseconds_bucket{le="0.5"}
-etcd_debugging_mvcc_index_compaction_pause_duration_milliseconds_bucket{le="1"}
-etcd_debugging_mvcc_index_compaction_pause_duration_milliseconds_bucket{le="2"}
-etcd_debugging_mvcc_index_compaction_pause_duration_milliseconds_bucket{le="4"}
-etcd_debugging_mvcc_index_compaction_pause_duration_milliseconds_bucket{le="8"}
-etcd_debugging_mvcc_index_compaction_pause_duration_milliseconds_bucket{le="16"}
-etcd_debugging_mvcc_index_compaction_pause_duration_milliseconds_bucket{le="32"}
-etcd_debugging_mvcc_index_compaction_pause_duration_milliseconds_bucket{le="64"}
-etcd_debugging_mvcc_index_compaction_pause_duration_milliseconds_bucket{le="128"}
-etcd_debugging_mvcc_index_compaction_pause_duration_milliseconds_bucket{le="256"}
-etcd_debugging_mvcc_index_compaction_pause_duration_milliseconds_bucket{le="512"}
-etcd_debugging_mvcc_index_compaction_pause_duration_milliseconds_bucket{le="1024"}
-etcd_debugging_mvcc_index_compaction_pause_duration_milliseconds_bucket{le="+Inf"}
-etcd_debugging_mvcc_index_compaction_pause_duration_milliseconds_sum
-etcd_debugging_mvcc_index_compaction_pause_duration_milliseconds_count
-
-# name: "etcd_debugging_mvcc_keys_total"
-# description: "Total number of keys."
-# type: "gauge"
-etcd_debugging_mvcc_keys_total
-
-# name: "etcd_debugging_mvcc_pending_events_total"
-# description: "Total number of pending events to be sent."
-# type: "gauge"
-etcd_debugging_mvcc_pending_events_total
-
-# name: "etcd_debugging_mvcc_put_total"
-# description: "Total number of puts seen by this member."
-# type: "counter"
-etcd_debugging_mvcc_put_total
-
-# name: "etcd_debugging_mvcc_range_total"
-# description: "Total number of ranges seen by this member."
-# type: "counter"
-etcd_debugging_mvcc_range_total
-
-# name: "etcd_debugging_mvcc_slow_watcher_total"
-# description: "Total number of unsynced slow watchers."
-# type: "gauge"
-etcd_debugging_mvcc_slow_watcher_total
-
-# name: "etcd_debugging_mvcc_txn_total"
-# description: "Total number of txns seen by this member."
-# type: "counter"
-etcd_debugging_mvcc_txn_total
-
-# name: "etcd_debugging_mvcc_watch_stream_total"
-# description: "Total number of watch streams."
-# type: "gauge"
-etcd_debugging_mvcc_watch_stream_total
-
-# name: "etcd_debugging_mvcc_watcher_total"
-# description: "Total number of watchers."
-# type: "gauge"
-etcd_debugging_mvcc_watcher_total
-
-# name: "etcd_debugging_snap_save_marshalling_duration_seconds"
-# description: "The marshalling cost distributions of save called by snapshot."
-# type: "histogram"
-etcd_debugging_snap_save_marshalling_duration_seconds_bucket{le="0.001"}
-etcd_debugging_snap_save_marshalling_duration_seconds_bucket{le="0.002"}
-etcd_debugging_snap_save_marshalling_duration_seconds_bucket{le="0.004"}
-etcd_debugging_snap_save_marshalling_duration_seconds_bucket{le="0.008"}
-etcd_debugging_snap_save_marshalling_duration_seconds_bucket{le="0.016"}
-etcd_debugging_snap_save_marshalling_duration_seconds_bucket{le="0.032"}
-etcd_debugging_snap_save_marshalling_duration_seconds_bucket{le="0.064"}
-etcd_debugging_snap_save_marshalling_duration_seconds_bucket{le="0.128"}
-etcd_debugging_snap_save_marshalling_duration_seconds_bucket{le="0.256"}
-etcd_debugging_snap_save_marshalling_duration_seconds_bucket{le="0.512"}
-etcd_debugging_snap_save_marshalling_duration_seconds_bucket{le="1.024"}
-etcd_debugging_snap_save_marshalling_duration_seconds_bucket{le="2.048"}
-etcd_debugging_snap_save_marshalling_duration_seconds_bucket{le="4.096"}
-etcd_debugging_snap_save_marshalling_duration_seconds_bucket{le="8.192"}
-etcd_debugging_snap_save_marshalling_duration_seconds_bucket{le="+Inf"}
-etcd_debugging_snap_save_marshalling_duration_seconds_sum
-etcd_debugging_snap_save_marshalling_duration_seconds_count
-
-# name: "etcd_debugging_snap_save_total_duration_seconds"
-# description: "The total latency distributions of save called by snapshot."
-# type: "histogram"
-etcd_debugging_snap_save_total_duration_seconds_bucket{le="0.001"}
-etcd_debugging_snap_save_total_duration_seconds_bucket{le="0.002"}
-etcd_debugging_snap_save_total_duration_seconds_bucket{le="0.004"}
-etcd_debugging_snap_save_total_duration_seconds_bucket{le="0.008"}
-etcd_debugging_snap_save_total_duration_seconds_bucket{le="0.016"}
-etcd_debugging_snap_save_total_duration_seconds_bucket{le="0.032"}
-etcd_debugging_snap_save_total_duration_seconds_bucket{le="0.064"}
-etcd_debugging_snap_save_total_duration_seconds_bucket{le="0.128"}
-etcd_debugging_snap_save_total_duration_seconds_bucket{le="0.256"}
-etcd_debugging_snap_save_total_duration_seconds_bucket{le="0.512"}
-etcd_debugging_snap_save_total_duration_seconds_bucket{le="1.024"}
-etcd_debugging_snap_save_total_duration_seconds_bucket{le="2.048"}
-etcd_debugging_snap_save_total_duration_seconds_bucket{le="4.096"}
-etcd_debugging_snap_save_total_duration_seconds_bucket{le="8.192"}
-etcd_debugging_snap_save_total_duration_seconds_bucket{le="+Inf"}
-etcd_debugging_snap_save_total_duration_seconds_sum
-etcd_debugging_snap_save_total_duration_seconds_count
-
-# name: "etcd_debugging_store_expires_total"
-# description: "Total number of expired keys."
-# type: "counter"
-etcd_debugging_store_expires_total
-
-# name: "etcd_debugging_store_reads_total"
-# description: "Total number of reads action by (get/getRecursive), local to this member."
-# type: "counter"
-etcd_debugging_store_reads_total{action="getRecursive"}
-
-# name: "etcd_debugging_store_watch_requests_total"
-# description: "Total number of incoming watch requests (new or reestablished)."
-# type: "counter"
-etcd_debugging_store_watch_requests_total
-
-# name: "etcd_debugging_store_watchers"
-# description: "Count of currently active watchers."
-# type: "gauge"
-etcd_debugging_store_watchers
-
-# name: "etcd_debugging_store_writes_total"
-# description: "Total number of writes (e.g. set/compareAndDelete) seen by this member."
-# type: "counter"
-etcd_debugging_store_writes_total{action="create"}
-etcd_debugging_store_writes_total{action="set"}
-
-# name: "etcd_disk_backend_commit_duration_seconds"
-# description: "The latency distributions of commit called by backend."
-# type: "histogram"
-etcd_disk_backend_commit_duration_seconds_bucket{le="0.001"}
-etcd_disk_backend_commit_duration_seconds_bucket{le="0.002"}
-etcd_disk_backend_commit_duration_seconds_bucket{le="0.004"}
-etcd_disk_backend_commit_duration_seconds_bucket{le="0.008"}
-etcd_disk_backend_commit_duration_seconds_bucket{le="0.016"}
-etcd_disk_backend_commit_duration_seconds_bucket{le="0.032"}
-etcd_disk_backend_commit_duration_seconds_bucket{le="0.064"}
-etcd_disk_backend_commit_duration_seconds_bucket{le="0.128"}
-etcd_disk_backend_commit_duration_seconds_bucket{le="0.256"}
-etcd_disk_backend_commit_duration_seconds_bucket{le="0.512"}
-etcd_disk_backend_commit_duration_seconds_bucket{le="1.024"}
-etcd_disk_backend_commit_duration_seconds_bucket{le="2.048"}
-etcd_disk_backend_commit_duration_seconds_bucket{le="4.096"}
-etcd_disk_backend_commit_duration_seconds_bucket{le="8.192"}
-etcd_disk_backend_commit_duration_seconds_bucket{le="+Inf"}
-etcd_disk_backend_commit_duration_seconds_sum
-etcd_disk_backend_commit_duration_seconds_count
-
-# name: "etcd_disk_wal_fsync_duration_seconds"
-# description: "The latency distributions of fsync called by wal."
-# type: "histogram"
-etcd_disk_wal_fsync_duration_seconds_bucket{le="0.001"}
-etcd_disk_wal_fsync_duration_seconds_bucket{le="0.002"}
-etcd_disk_wal_fsync_duration_seconds_bucket{le="0.004"}
-etcd_disk_wal_fsync_duration_seconds_bucket{le="0.008"}
-etcd_disk_wal_fsync_duration_seconds_bucket{le="0.016"}
-etcd_disk_wal_fsync_duration_seconds_bucket{le="0.032"}
-etcd_disk_wal_fsync_duration_seconds_bucket{le="0.064"}
-etcd_disk_wal_fsync_duration_seconds_bucket{le="0.128"}
-etcd_disk_wal_fsync_duration_seconds_bucket{le="0.256"}
-etcd_disk_wal_fsync_duration_seconds_bucket{le="0.512"}
-etcd_disk_wal_fsync_duration_seconds_bucket{le="1.024"}
-etcd_disk_wal_fsync_duration_seconds_bucket{le="2.048"}
-etcd_disk_wal_fsync_duration_seconds_bucket{le="4.096"}
-etcd_disk_wal_fsync_duration_seconds_bucket{le="8.192"}
-etcd_disk_wal_fsync_duration_seconds_bucket{le="+Inf"}
-etcd_disk_wal_fsync_duration_seconds_sum
-etcd_disk_wal_fsync_duration_seconds_count
-
-# name: "etcd_grpc_proxy_cache_hits_total"
-# description: "Total number of cache hits"
-# type: "gauge"
-etcd_grpc_proxy_cache_hits_total
-
-# name: "etcd_grpc_proxy_cache_misses_total"
-# description: "Total number of cache misses"
-# type: "gauge"
-etcd_grpc_proxy_cache_misses_total
-
-# name: "etcd_grpc_proxy_events_coalescing_total"
-# description: "Total number of events coalescing"
-# type: "counter"
-etcd_grpc_proxy_events_coalescing_total
-
-# name: "etcd_grpc_proxy_watchers_coalescing_total"
-# description: "Total number of current watchers coalescing"
-# type: "gauge"
-etcd_grpc_proxy_watchers_coalescing_total
-
-# name: "etcd_network_client_grpc_received_bytes_total"
-# description: "The total number of bytes received from grpc clients."
-# type: "counter"
-etcd_network_client_grpc_received_bytes_total
-
-# name: "etcd_network_client_grpc_sent_bytes_total"
-# description: "The total number of bytes sent to grpc clients."
-# type: "counter"
-etcd_network_client_grpc_sent_bytes_total
-
-# name: "etcd_network_peer_received_bytes_total"
-# description: "The total number of bytes received from peers."
-# type: "counter"
-etcd_network_peer_received_bytes_total{From="REMOTE_PEER_NODE_ID"}
-
-# name: "etcd_network_peer_round_trip_time_seconds"
-# description: "Round-Trip-Time histogram between peers."
-# type: "histogram"
-etcd_network_peer_round_trip_time_seconds_bucket{To="REMOTE_PEER_NODE_ID",le="+Inf"}
-etcd_network_peer_round_trip_time_seconds_bucket{To="REMOTE_PEER_NODE_ID",le="0.0001"}
-etcd_network_peer_round_trip_time_seconds_bucket{To="REMOTE_PEER_NODE_ID",le="0.0002"}
-etcd_network_peer_round_trip_time_seconds_bucket{To="REMOTE_PEER_NODE_ID",le="0.0004"}
-etcd_network_peer_round_trip_time_seconds_bucket{To="REMOTE_PEER_NODE_ID",le="0.0008"}
-etcd_network_peer_round_trip_time_seconds_bucket{To="REMOTE_PEER_NODE_ID",le="0.0016"}
-etcd_network_peer_round_trip_time_seconds_bucket{To="REMOTE_PEER_NODE_ID",le="0.0032"}
-etcd_network_peer_round_trip_time_seconds_bucket{To="REMOTE_PEER_NODE_ID",le="0.0064"}
-etcd_network_peer_round_trip_time_seconds_bucket{To="REMOTE_PEER_NODE_ID",le="0.0128"}
-etcd_network_peer_round_trip_time_seconds_bucket{To="REMOTE_PEER_NODE_ID",le="0.0256"}
-etcd_network_peer_round_trip_time_seconds_bucket{To="REMOTE_PEER_NODE_ID",le="0.0512"}
-etcd_network_peer_round_trip_time_seconds_bucket{To="REMOTE_PEER_NODE_ID",le="0.1024"}
-etcd_network_peer_round_trip_time_seconds_bucket{To="REMOTE_PEER_NODE_ID",le="0.2048"}
-etcd_network_peer_round_trip_time_seconds_bucket{To="REMOTE_PEER_NODE_ID",le="0.4096"}
-etcd_network_peer_round_trip_time_seconds_bucket{To="REMOTE_PEER_NODE_ID",le="0.8192"}
-etcd_network_peer_round_trip_time_seconds_count{To="REMOTE_PEER_NODE_ID"}
-etcd_network_peer_round_trip_time_seconds_sum{To="REMOTE_PEER_NODE_ID"}
-
-# name: "etcd_network_peer_sent_bytes_total"
-# description: "The total number of bytes sent to peers."
-# type: "counter"
-etcd_network_peer_sent_bytes_total{To="REMOTE_PEER_NODE_ID"}
-
-# name: "etcd_server_has_leader"
-# description: "Whether or not a leader exists. 1 is existence, 0 is not."
-# type: "gauge"
-etcd_server_has_leader
-
-# name: "etcd_server_leader_changes_seen_total"
-# description: "The number of leader changes seen."
-# type: "counter"
-etcd_server_leader_changes_seen_total
-
-# name: "etcd_server_proposals_applied_total"
-# description: "The total number of consensus proposals applied."
-# type: "gauge"
-etcd_server_proposals_applied_total
-
-# name: "etcd_server_proposals_committed_total"
-# description: "The total number of consensus proposals committed."
-# type: "gauge"
-etcd_server_proposals_committed_total
-
-# name: "etcd_server_proposals_failed_total"
-# description: "The total number of failed proposals seen."
-# type: "counter"
-etcd_server_proposals_failed_total
-
-# name: "etcd_server_proposals_pending"
-# description: "The current number of pending proposals to commit."
-# type: "gauge"
-etcd_server_proposals_pending
-
-# name: "go_gc_duration_seconds"
-# description: "A summary of the GC invocation durations."
-# type: "summary"
-go_gc_duration_seconds{quantile="0"}
-go_gc_duration_seconds{quantile="0.25"}
-go_gc_duration_seconds{quantile="0.5"}
-go_gc_duration_seconds{quantile="0.75"}
-go_gc_duration_seconds{quantile="1"}
-go_gc_duration_seconds_sum
-go_gc_duration_seconds_count
-
-# name: "go_goroutines"
-# description: "Number of goroutines that currently exist."
-# type: "gauge"
-go_goroutines
-
-# name: "go_memstats_alloc_bytes"
-# description: "Number of bytes allocated and still in use."
-# type: "gauge"
-go_memstats_alloc_bytes
-
-# name: "go_memstats_alloc_bytes_total"
-# description: "Total number of bytes allocated, even if freed."
-# type: "counter"
-go_memstats_alloc_bytes_total
-
-# name: "go_memstats_buck_hash_sys_bytes"
-# description: "Number of bytes used by the profiling bucket hash table."
-# type: "gauge"
-go_memstats_buck_hash_sys_bytes
-
-# name: "go_memstats_frees_total"
-# description: "Total number of frees."
-# type: "counter"
-go_memstats_frees_total
-
-# name: "go_memstats_gc_sys_bytes"
-# description: "Number of bytes used for garbage collection system metadata."
-# type: "gauge"
-go_memstats_gc_sys_bytes
-
-# name: "go_memstats_heap_alloc_bytes"
-# description: "Number of heap bytes allocated and still in use."
-# type: "gauge"
-go_memstats_heap_alloc_bytes
-
-# name: "go_memstats_heap_idle_bytes"
-# description: "Number of heap bytes waiting to be used."
-# type: "gauge"
-go_memstats_heap_idle_bytes
-
-# name: "go_memstats_heap_inuse_bytes"
-# description: "Number of heap bytes that are in use."
-# type: "gauge"
-go_memstats_heap_inuse_bytes
-
-# name: "go_memstats_heap_objects"
-# description: "Number of allocated objects."
-# type: "gauge"
-go_memstats_heap_objects
-
-# name: "go_memstats_heap_released_bytes_total"
-# description: "Total number of heap bytes released to OS."
-# type: "counter"
-go_memstats_heap_released_bytes_total
-
-# name: "go_memstats_heap_sys_bytes"
-# description: "Number of heap bytes obtained from system."
-# type: "gauge"
-go_memstats_heap_sys_bytes
-
-# name: "go_memstats_last_gc_time_seconds"
-# description: "Number of seconds since 1970 of last garbage collection."
-# type: "gauge"
-go_memstats_last_gc_time_seconds
-
-# name: "go_memstats_lookups_total"
-# description: "Total number of pointer lookups."
-# type: "counter"
-go_memstats_lookups_total
-
-# name: "go_memstats_mallocs_total"
-# description: "Total number of mallocs."
-# type: "counter"
-go_memstats_mallocs_total
-
-# name: "go_memstats_mcache_inuse_bytes"
-# description: "Number of bytes in use by mcache structures."
-# type: "gauge"
-go_memstats_mcache_inuse_bytes
-
-# name: "go_memstats_mcache_sys_bytes"
-# description: "Number of bytes used for mcache structures obtained from system."
-# type: "gauge"
-go_memstats_mcache_sys_bytes
-
-# name: "go_memstats_mspan_inuse_bytes"
-# description: "Number of bytes in use by mspan structures."
-# type: "gauge"
-go_memstats_mspan_inuse_bytes
-
-# name: "go_memstats_mspan_sys_bytes"
-# description: "Number of bytes used for mspan structures obtained from system."
-# type: "gauge"
-go_memstats_mspan_sys_bytes
-
-# name: "go_memstats_next_gc_bytes"
-# description: "Number of heap bytes when next garbage collection will take place."
-# type: "gauge"
-go_memstats_next_gc_bytes
-
-# name: "go_memstats_other_sys_bytes"
-# description: "Number of bytes used for other system allocations."
-# type: "gauge"
-go_memstats_other_sys_bytes
-
-# name: "go_memstats_stack_inuse_bytes"
-# description: "Number of bytes in use by the stack allocator."
-# type: "gauge"
-go_memstats_stack_inuse_bytes
-
-# name: "go_memstats_stack_sys_bytes"
-# description: "Number of bytes obtained from system for stack allocator."
-# type: "gauge"
-go_memstats_stack_sys_bytes
-
-# name: "go_memstats_sys_bytes"
-# description: "Number of bytes obtained by system. Sum of all system allocations."
-# type: "gauge"
-go_memstats_sys_bytes
-
-# name: "grpc_server_handled_total"
-# description: "Total number of RPCs completed on the server, regardless of success or failure."
-# type: "counter"
-# gRPC codes: 
-#  - "OK"
-#  - "Unavailable"
-grpc_server_handled_total{grpc_code="CODE",grpc_method="DeleteRange",grpc_service="etcdserverpb.KV",grpc_type="unary"}
-grpc_server_handled_total{grpc_code="CODE",grpc_method="Put",grpc_service="etcdserverpb.KV",grpc_type="unary"}
-grpc_server_handled_total{grpc_code="CODE",grpc_method="Range",grpc_service="etcdserverpb.KV",grpc_type="unary"}
-grpc_server_handled_total{grpc_code="CODE",grpc_method="Watch",grpc_service="etcdserverpb.Watch",grpc_type="bidi_stream"}
-
-# name: "grpc_server_msg_received_total"
-# description: "Total number of RPC stream messages received on the server."
-# type: "counter"
-grpc_server_msg_received_total{grpc_method="DeleteRange",grpc_service="etcdserverpb.KV",grpc_type="unary"}
-grpc_server_msg_received_total{grpc_method="Put",grpc_service="etcdserverpb.KV",grpc_type="unary"}
-grpc_server_msg_received_total{grpc_method="Range",grpc_service="etcdserverpb.KV",grpc_type="unary"}
-grpc_server_msg_received_total{grpc_method="Watch",grpc_service="etcdserverpb.Watch",grpc_type="bidi_stream"}
-
-# name: "grpc_server_msg_sent_total"
-# description: "Total number of gRPC stream messages sent by the server."
-# type: "counter"
-grpc_server_msg_sent_total{grpc_method="DeleteRange",grpc_service="etcdserverpb.KV",grpc_type="unary"}
-grpc_server_msg_sent_total{grpc_method="Put",grpc_service="etcdserverpb.KV",grpc_type="unary"}
-grpc_server_msg_sent_total{grpc_method="Range",grpc_service="etcdserverpb.KV",grpc_type="unary"}
-grpc_server_msg_sent_total{grpc_method="Watch",grpc_service="etcdserverpb.Watch",grpc_type="bidi_stream"}
-
-# name: "grpc_server_started_total"
-# description: "Total number of RPCs started on the server."
-# type: "counter"
-grpc_server_started_total{grpc_method="DeleteRange",grpc_service="etcdserverpb.KV",grpc_type="unary"}
-grpc_server_started_total{grpc_method="Put",grpc_service="etcdserverpb.KV",grpc_type="unary"}
-grpc_server_started_total{grpc_method="Range",grpc_service="etcdserverpb.KV",grpc_type="unary"}
-grpc_server_started_total{grpc_method="Watch",grpc_service="etcdserverpb.Watch",grpc_type="bidi_stream"}
-
-# name: "http_request_duration_microseconds"
-# description: "The HTTP request latencies in microseconds."
-# type: "summary"
-http_request_duration_microseconds{handler="prometheus",quantile="0.5"}
-http_request_duration_microseconds{handler="prometheus",quantile="0.9"}
-http_request_duration_microseconds{handler="prometheus",quantile="0.99"}
-http_request_duration_microseconds_sum{handler="prometheus"}
-http_request_duration_microseconds_count{handler="prometheus"}
-
-# name: "http_request_size_bytes"
-# description: "The HTTP request sizes in bytes."
-# type: "summary"
-http_request_size_bytes{handler="prometheus",quantile="0.5"}
-http_request_size_bytes{handler="prometheus",quantile="0.9"}
-http_request_size_bytes{handler="prometheus",quantile="0.99"}
-http_request_size_bytes_sum{handler="prometheus"}
-http_request_size_bytes_count{handler="prometheus"}
-
-# name: "http_response_size_bytes"
-# description: "The HTTP response sizes in bytes."
-# type: "summary"
-http_response_size_bytes{handler="prometheus",quantile="0.5"}
-http_response_size_bytes{handler="prometheus",quantile="0.9"}
-http_response_size_bytes{handler="prometheus",quantile="0.99"}
-http_response_size_bytes_sum{handler="prometheus"}
-http_response_size_bytes_count{handler="prometheus"}
-

Documentation/metrics/v3.1.13

@@ -1,511 +0,0 @@
-# server version: unknown
-
-# name: "etcd_debugging_mvcc_db_compaction_pause_duration_milliseconds"
-# description: "Bucketed histogram of db compaction pause duration."
-# type: "histogram"
-etcd_debugging_mvcc_db_compaction_pause_duration_milliseconds_bucket{le="1"}
-etcd_debugging_mvcc_db_compaction_pause_duration_milliseconds_bucket{le="2"}
-etcd_debugging_mvcc_db_compaction_pause_duration_milliseconds_bucket{le="4"}
-etcd_debugging_mvcc_db_compaction_pause_duration_milliseconds_bucket{le="8"}
-etcd_debugging_mvcc_db_compaction_pause_duration_milliseconds_bucket{le="16"}
-etcd_debugging_mvcc_db_compaction_pause_duration_milliseconds_bucket{le="32"}
-etcd_debugging_mvcc_db_compaction_pause_duration_milliseconds_bucket{le="64"}
-etcd_debugging_mvcc_db_compaction_pause_duration_milliseconds_bucket{le="128"}
-etcd_debugging_mvcc_db_compaction_pause_duration_milliseconds_bucket{le="256"}
-etcd_debugging_mvcc_db_compaction_pause_duration_milliseconds_bucket{le="512"}
-etcd_debugging_mvcc_db_compaction_pause_duration_milliseconds_bucket{le="1024"}
-etcd_debugging_mvcc_db_compaction_pause_duration_milliseconds_bucket{le="2048"}
-etcd_debugging_mvcc_db_compaction_pause_duration_milliseconds_bucket{le="4096"}
-etcd_debugging_mvcc_db_compaction_pause_duration_milliseconds_bucket{le="+Inf"}
-etcd_debugging_mvcc_db_compaction_pause_duration_milliseconds_sum
-etcd_debugging_mvcc_db_compaction_pause_duration_milliseconds_count
-
-# name: "etcd_debugging_mvcc_db_compaction_total_duration_milliseconds"
-# description: "Bucketed histogram of db compaction total duration."
-# type: "histogram"
-etcd_debugging_mvcc_db_compaction_total_duration_milliseconds_bucket{le="100"}
-etcd_debugging_mvcc_db_compaction_total_duration_milliseconds_bucket{le="200"}
-etcd_debugging_mvcc_db_compaction_total_duration_milliseconds_bucket{le="400"}
-etcd_debugging_mvcc_db_compaction_total_duration_milliseconds_bucket{le="800"}
-etcd_debugging_mvcc_db_compaction_total_duration_milliseconds_bucket{le="1600"}
-etcd_debugging_mvcc_db_compaction_total_duration_milliseconds_bucket{le="3200"}
-etcd_debugging_mvcc_db_compaction_total_duration_milliseconds_bucket{le="6400"}
-etcd_debugging_mvcc_db_compaction_total_duration_milliseconds_bucket{le="12800"}
-etcd_debugging_mvcc_db_compaction_total_duration_milliseconds_bucket{le="25600"}
-etcd_debugging_mvcc_db_compaction_total_duration_milliseconds_bucket{le="51200"}
-etcd_debugging_mvcc_db_compaction_total_duration_milliseconds_bucket{le="102400"}
-etcd_debugging_mvcc_db_compaction_total_duration_milliseconds_bucket{le="204800"}
-etcd_debugging_mvcc_db_compaction_total_duration_milliseconds_bucket{le="409600"}
-etcd_debugging_mvcc_db_compaction_total_duration_milliseconds_bucket{le="819200"}
-etcd_debugging_mvcc_db_compaction_total_duration_milliseconds_bucket{le="+Inf"}
-etcd_debugging_mvcc_db_compaction_total_duration_milliseconds_sum
-etcd_debugging_mvcc_db_compaction_total_duration_milliseconds_count
-
-# name: "etcd_debugging_mvcc_db_total_size_in_bytes"
-# description: "Total size of the underlying database in bytes."
-# type: "gauge"
-etcd_debugging_mvcc_db_total_size_in_bytes
-
-# name: "etcd_debugging_mvcc_delete_total"
-# description: "Total number of deletes seen by this member."
-# type: "counter"
-etcd_debugging_mvcc_delete_total
-
-# name: "etcd_debugging_mvcc_events_total"
-# description: "Total number of events sent by this member."
-# type: "counter"
-etcd_debugging_mvcc_events_total
-
-# name: "etcd_debugging_mvcc_index_compaction_pause_duration_milliseconds"
-# description: "Bucketed histogram of index compaction pause duration."
-# type: "histogram"
-etcd_debugging_mvcc_index_compaction_pause_duration_milliseconds_bucket{le="0.5"}
-etcd_debugging_mvcc_index_compaction_pause_duration_milliseconds_bucket{le="1"}
-etcd_debugging_mvcc_index_compaction_pause_duration_milliseconds_bucket{le="2"}
-etcd_debugging_mvcc_index_compaction_pause_duration_milliseconds_bucket{le="4"}
-etcd_debugging_mvcc_index_compaction_pause_duration_milliseconds_bucket{le="8"}
-etcd_debugging_mvcc_index_compaction_pause_duration_milliseconds_bucket{le="16"}
-etcd_debugging_mvcc_index_compaction_pause_duration_milliseconds_bucket{le="32"}
-etcd_debugging_mvcc_index_compaction_pause_duration_milliseconds_bucket{le="64"}
-etcd_debugging_mvcc_index_compaction_pause_duration_milliseconds_bucket{le="128"}
-etcd_debugging_mvcc_index_compaction_pause_duration_milliseconds_bucket{le="256"}
-etcd_debugging_mvcc_index_compaction_pause_duration_milliseconds_bucket{le="512"}
-etcd_debugging_mvcc_index_compaction_pause_duration_milliseconds_bucket{le="1024"}
-etcd_debugging_mvcc_index_compaction_pause_duration_milliseconds_bucket{le="+Inf"}
-etcd_debugging_mvcc_index_compaction_pause_duration_milliseconds_sum
-etcd_debugging_mvcc_index_compaction_pause_duration_milliseconds_count
-
-# name: "etcd_debugging_mvcc_keys_total"
-# description: "Total number of keys."
-# type: "gauge"
-etcd_debugging_mvcc_keys_total
-
-# name: "etcd_debugging_mvcc_pending_events_total"
-# description: "Total number of pending events to be sent."
-# type: "gauge"
-etcd_debugging_mvcc_pending_events_total
-
-# name: "etcd_debugging_mvcc_put_total"
-# description: "Total number of puts seen by this member."
-# type: "counter"
-etcd_debugging_mvcc_put_total
-
-# name: "etcd_debugging_mvcc_range_total"
-# description: "Total number of ranges seen by this member."
-# type: "counter"
-etcd_debugging_mvcc_range_total
-
-# name: "etcd_debugging_mvcc_slow_watcher_total"
-# description: "Total number of unsynced slow watchers."
-# type: "gauge"
-etcd_debugging_mvcc_slow_watcher_total
-
-# name: "etcd_debugging_mvcc_txn_total"
-# description: "Total number of txns seen by this member."
-# type: "counter"
-etcd_debugging_mvcc_txn_total
-
-# name: "etcd_debugging_mvcc_watch_stream_total"
-# description: "Total number of watch streams."
-# type: "gauge"
-etcd_debugging_mvcc_watch_stream_total
-
-# name: "etcd_debugging_mvcc_watcher_total"
-# description: "Total number of watchers."
-# type: "gauge"
-etcd_debugging_mvcc_watcher_total
-
-# name: "etcd_debugging_snap_save_marshalling_duration_seconds"
-# description: "The marshalling cost distributions of save called by snapshot."
-# type: "histogram"
-etcd_debugging_snap_save_marshalling_duration_seconds_bucket{le="0.001"}
-etcd_debugging_snap_save_marshalling_duration_seconds_bucket{le="0.002"}
-etcd_debugging_snap_save_marshalling_duration_seconds_bucket{le="0.004"}
-etcd_debugging_snap_save_marshalling_duration_seconds_bucket{le="0.008"}
-etcd_debugging_snap_save_marshalling_duration_seconds_bucket{le="0.016"}
-etcd_debugging_snap_save_marshalling_duration_seconds_bucket{le="0.032"}
-etcd_debugging_snap_save_marshalling_duration_seconds_bucket{le="0.064"}
-etcd_debugging_snap_save_marshalling_duration_seconds_bucket{le="0.128"}
-etcd_debugging_snap_save_marshalling_duration_seconds_bucket{le="0.256"}
-etcd_debugging_snap_save_marshalling_duration_seconds_bucket{le="0.512"}
-etcd_debugging_snap_save_marshalling_duration_seconds_bucket{le="1.024"}
-etcd_debugging_snap_save_marshalling_duration_seconds_bucket{le="2.048"}
-etcd_debugging_snap_save_marshalling_duration_seconds_bucket{le="4.096"}
-etcd_debugging_snap_save_marshalling_duration_seconds_bucket{le="8.192"}
-etcd_debugging_snap_save_marshalling_duration_seconds_bucket{le="+Inf"}
-etcd_debugging_snap_save_marshalling_duration_seconds_sum
-etcd_debugging_snap_save_marshalling_duration_seconds_count
-
-# name: "etcd_debugging_snap_save_total_duration_seconds"
-# description: "The total latency distributions of save called by snapshot."
-# type: "histogram"
-etcd_debugging_snap_save_total_duration_seconds_bucket{le="0.001"}
-etcd_debugging_snap_save_total_duration_seconds_bucket{le="0.002"}
-etcd_debugging_snap_save_total_duration_seconds_bucket{le="0.004"}
-etcd_debugging_snap_save_total_duration_seconds_bucket{le="0.008"}
-etcd_debugging_snap_save_total_duration_seconds_bucket{le="0.016"}
-etcd_debugging_snap_save_total_duration_seconds_bucket{le="0.032"}
-etcd_debugging_snap_save_total_duration_seconds_bucket{le="0.064"}
-etcd_debugging_snap_save_total_duration_seconds_bucket{le="0.128"}
-etcd_debugging_snap_save_total_duration_seconds_bucket{le="0.256"}
-etcd_debugging_snap_save_total_duration_seconds_bucket{le="0.512"}
-etcd_debugging_snap_save_total_duration_seconds_bucket{le="1.024"}
-etcd_debugging_snap_save_total_duration_seconds_bucket{le="2.048"}
-etcd_debugging_snap_save_total_duration_seconds_bucket{le="4.096"}
-etcd_debugging_snap_save_total_duration_seconds_bucket{le="8.192"}
-etcd_debugging_snap_save_total_duration_seconds_bucket{le="+Inf"}
-etcd_debugging_snap_save_total_duration_seconds_sum
-etcd_debugging_snap_save_total_duration_seconds_count
-
-# name: "etcd_debugging_store_expires_total"
-# description: "Total number of expired keys."
-# type: "counter"
-etcd_debugging_store_expires_total
-
-# name: "etcd_debugging_store_reads_total"
-# description: "Total number of reads action by (get/getRecursive), local to this member."
-# type: "counter"
-etcd_debugging_store_reads_total{action="getRecursive"}
-
-# name: "etcd_debugging_store_watch_requests_total"
-# description: "Total number of incoming watch requests (new or reestablished)."
-# type: "counter"
-etcd_debugging_store_watch_requests_total
-
-# name: "etcd_debugging_store_watchers"
-# description: "Count of currently active watchers."
-# type: "gauge"
-etcd_debugging_store_watchers
-
-# name: "etcd_debugging_store_writes_total"
-# description: "Total number of writes (e.g. set/compareAndDelete) seen by this member."
-# type: "counter"
-etcd_debugging_store_writes_total{action="create"}
-etcd_debugging_store_writes_total{action="set"}
-
-# name: "etcd_disk_backend_commit_duration_seconds"
-# description: "The latency distributions of commit called by backend."
-# type: "histogram"
-etcd_disk_backend_commit_duration_seconds_bucket{le="0.001"}
-etcd_disk_backend_commit_duration_seconds_bucket{le="0.002"}
-etcd_disk_backend_commit_duration_seconds_bucket{le="0.004"}
-etcd_disk_backend_commit_duration_seconds_bucket{le="0.008"}
-etcd_disk_backend_commit_duration_seconds_bucket{le="0.016"}
-etcd_disk_backend_commit_duration_seconds_bucket{le="0.032"}
-etcd_disk_backend_commit_duration_seconds_bucket{le="0.064"}
-etcd_disk_backend_commit_duration_seconds_bucket{le="0.128"}
-etcd_disk_backend_commit_duration_seconds_bucket{le="0.256"}
-etcd_disk_backend_commit_duration_seconds_bucket{le="0.512"}
-etcd_disk_backend_commit_duration_seconds_bucket{le="1.024"}
-etcd_disk_backend_commit_duration_seconds_bucket{le="2.048"}
-etcd_disk_backend_commit_duration_seconds_bucket{le="4.096"}
-etcd_disk_backend_commit_duration_seconds_bucket{le="8.192"}
-etcd_disk_backend_commit_duration_seconds_bucket{le="+Inf"}
-etcd_disk_backend_commit_duration_seconds_sum
-etcd_disk_backend_commit_duration_seconds_count
-
-# name: "etcd_disk_wal_fsync_duration_seconds"
-# description: "The latency distributions of fsync called by wal."
-# type: "histogram"
-etcd_disk_wal_fsync_duration_seconds_bucket{le="0.001"}
-etcd_disk_wal_fsync_duration_seconds_bucket{le="0.002"}
-etcd_disk_wal_fsync_duration_seconds_bucket{le="0.004"}
-etcd_disk_wal_fsync_duration_seconds_bucket{le="0.008"}
-etcd_disk_wal_fsync_duration_seconds_bucket{le="0.016"}
-etcd_disk_wal_fsync_duration_seconds_bucket{le="0.032"}
-etcd_disk_wal_fsync_duration_seconds_bucket{le="0.064"}
-etcd_disk_wal_fsync_duration_seconds_bucket{le="0.128"}
-etcd_disk_wal_fsync_duration_seconds_bucket{le="0.256"}
-etcd_disk_wal_fsync_duration_seconds_bucket{le="0.512"}
-etcd_disk_wal_fsync_duration_seconds_bucket{le="1.024"}
-etcd_disk_wal_fsync_duration_seconds_bucket{le="2.048"}
-etcd_disk_wal_fsync_duration_seconds_bucket{le="4.096"}
-etcd_disk_wal_fsync_duration_seconds_bucket{le="8.192"}
-etcd_disk_wal_fsync_duration_seconds_bucket{le="+Inf"}
-etcd_disk_wal_fsync_duration_seconds_sum
-etcd_disk_wal_fsync_duration_seconds_count
-
-# name: "etcd_grpc_proxy_cache_hits_total"
-# description: "Total number of cache hits"
-# type: "gauge"
-etcd_grpc_proxy_cache_hits_total
-
-# name: "etcd_grpc_proxy_cache_misses_total"
-# description: "Total number of cache misses"
-# type: "gauge"
-etcd_grpc_proxy_cache_misses_total
-
-# name: "etcd_grpc_proxy_events_coalescing_total"
-# description: "Total number of events coalescing"
-# type: "counter"
-etcd_grpc_proxy_events_coalescing_total
-
-# name: "etcd_grpc_proxy_watchers_coalescing_total"
-# description: "Total number of current watchers coalescing"
-# type: "gauge"
-etcd_grpc_proxy_watchers_coalescing_total
-
-# name: "etcd_network_client_grpc_received_bytes_total"
-# description: "The total number of bytes received from grpc clients."
-# type: "counter"
-etcd_network_client_grpc_received_bytes_total
-
-# name: "etcd_network_client_grpc_sent_bytes_total"
-# description: "The total number of bytes sent to grpc clients."
-# type: "counter"
-etcd_network_client_grpc_sent_bytes_total
-
-# name: "etcd_network_peer_received_bytes_total"
-# description: "The total number of bytes received from peers."
-# type: "counter"
-etcd_network_peer_received_bytes_total{From="REMOTE_PEER_NODE_ID"}
-
-# name: "etcd_network_peer_round_trip_time_seconds"
-# description: "Round-Trip-Time histogram between peers."
-# type: "histogram"
-etcd_network_peer_round_trip_time_seconds_bucket{To="REMOTE_PEER_NODE_ID",le="+Inf"}
-etcd_network_peer_round_trip_time_seconds_bucket{To="REMOTE_PEER_NODE_ID",le="0.0001"}
-etcd_network_peer_round_trip_time_seconds_bucket{To="REMOTE_PEER_NODE_ID",le="0.0002"}
-etcd_network_peer_round_trip_time_seconds_bucket{To="REMOTE_PEER_NODE_ID",le="0.0004"}
-etcd_network_peer_round_trip_time_seconds_bucket{To="REMOTE_PEER_NODE_ID",le="0.0008"}
-etcd_network_peer_round_trip_time_seconds_bucket{To="REMOTE_PEER_NODE_ID",le="0.0016"}
-etcd_network_peer_round_trip_time_seconds_bucket{To="REMOTE_PEER_NODE_ID",le="0.0032"}
-etcd_network_peer_round_trip_time_seconds_bucket{To="REMOTE_PEER_NODE_ID",le="0.0064"}
-etcd_network_peer_round_trip_time_seconds_bucket{To="REMOTE_PEER_NODE_ID",le="0.0128"}
-etcd_network_peer_round_trip_time_seconds_bucket{To="REMOTE_PEER_NODE_ID",le="0.0256"}
-etcd_network_peer_round_trip_time_seconds_bucket{To="REMOTE_PEER_NODE_ID",le="0.0512"}
-etcd_network_peer_round_trip_time_seconds_bucket{To="REMOTE_PEER_NODE_ID",le="0.1024"}
-etcd_network_peer_round_trip_time_seconds_bucket{To="REMOTE_PEER_NODE_ID",le="0.2048"}
-etcd_network_peer_round_trip_time_seconds_bucket{To="REMOTE_PEER_NODE_ID",le="0.4096"}
-etcd_network_peer_round_trip_time_seconds_bucket{To="REMOTE_PEER_NODE_ID",le="0.8192"}
-etcd_network_peer_round_trip_time_seconds_count{To="REMOTE_PEER_NODE_ID"}
-etcd_network_peer_round_trip_time_seconds_sum{To="REMOTE_PEER_NODE_ID"}
-
-# name: "etcd_network_peer_sent_bytes_total"
-# description: "The total number of bytes sent to peers."
-# type: "counter"
-etcd_network_peer_sent_bytes_total{To="REMOTE_PEER_NODE_ID"}
-
-# name: "etcd_server_has_leader"
-# description: "Whether or not a leader exists. 1 is existence, 0 is not."
-# type: "gauge"
-etcd_server_has_leader
-
-# name: "etcd_server_leader_changes_seen_total"
-# description: "The number of leader changes seen."
-# type: "counter"
-etcd_server_leader_changes_seen_total
-
-# name: "etcd_server_proposals_applied_total"
-# description: "The total number of consensus proposals applied."
-# type: "gauge"
-etcd_server_proposals_applied_total
-
-# name: "etcd_server_proposals_committed_total"
-# description: "The total number of consensus proposals committed."
-# type: "gauge"
-etcd_server_proposals_committed_total
-
-# name: "etcd_server_proposals_failed_total"
-# description: "The total number of failed proposals seen."
-# type: "counter"
-etcd_server_proposals_failed_total
-
-# name: "etcd_server_proposals_pending"
-# description: "The current number of pending proposals to commit."
-# type: "gauge"
-etcd_server_proposals_pending
-
-# name: "go_gc_duration_seconds"
-# description: "A summary of the GC invocation durations."
-# type: "summary"
-go_gc_duration_seconds{quantile="0"}
-go_gc_duration_seconds{quantile="0.25"}
-go_gc_duration_seconds{quantile="0.5"}
-go_gc_duration_seconds{quantile="0.75"}
-go_gc_duration_seconds{quantile="1"}
-go_gc_duration_seconds_sum
-go_gc_duration_seconds_count
-
-# name: "go_goroutines"
-# description: "Number of goroutines that currently exist."
-# type: "gauge"
-go_goroutines
-
-# name: "go_memstats_alloc_bytes"
-# description: "Number of bytes allocated and still in use."
-# type: "gauge"
-go_memstats_alloc_bytes
-
-# name: "go_memstats_alloc_bytes_total"
-# description: "Total number of bytes allocated, even if freed."
-# type: "counter"
-go_memstats_alloc_bytes_total
-
-# name: "go_memstats_buck_hash_sys_bytes"
-# description: "Number of bytes used by the profiling bucket hash table."
-# type: "gauge"
-go_memstats_buck_hash_sys_bytes
-
-# name: "go_memstats_frees_total"
-# description: "Total number of frees."
-# type: "counter"
-go_memstats_frees_total
-
-# name: "go_memstats_gc_sys_bytes"
-# description: "Number of bytes used for garbage collection system metadata."
-# type: "gauge"
-go_memstats_gc_sys_bytes
-
-# name: "go_memstats_heap_alloc_bytes"
-# description: "Number of heap bytes allocated and still in use."
-# type: "gauge"
-go_memstats_heap_alloc_bytes
-
-# name: "go_memstats_heap_idle_bytes"
-# description: "Number of heap bytes waiting to be used."
-# type: "gauge"
-go_memstats_heap_idle_bytes
-
-# name: "go_memstats_heap_inuse_bytes"
-# description: "Number of heap bytes that are in use."
-# type: "gauge"
-go_memstats_heap_inuse_bytes
-
-# name: "go_memstats_heap_objects"
-# description: "Number of allocated objects."
-# type: "gauge"
-go_memstats_heap_objects
-
-# name: "go_memstats_heap_released_bytes_total"
-# description: "Total number of heap bytes released to OS."
-# type: "counter"
-go_memstats_heap_released_bytes_total
-
-# name: "go_memstats_heap_sys_bytes"
-# description: "Number of heap bytes obtained from system."
-# type: "gauge"
-go_memstats_heap_sys_bytes
-
-# name: "go_memstats_last_gc_time_seconds"
-# description: "Number of seconds since 1970 of last garbage collection."
-# type: "gauge"
-go_memstats_last_gc_time_seconds
-
-# name: "go_memstats_lookups_total"
-# description: "Total number of pointer lookups."
-# type: "counter"
-go_memstats_lookups_total
-
-# name: "go_memstats_mallocs_total"
-# description: "Total number of mallocs."
-# type: "counter"
-go_memstats_mallocs_total
-
-# name: "go_memstats_mcache_inuse_bytes"
-# description: "Number of bytes in use by mcache structures."
-# type: "gauge"
-go_memstats_mcache_inuse_bytes
-
-# name: "go_memstats_mcache_sys_bytes"
-# description: "Number of bytes used for mcache structures obtained from system."
-# type: "gauge"
-go_memstats_mcache_sys_bytes
-
-# name: "go_memstats_mspan_inuse_bytes"
-# description: "Number of bytes in use by mspan structures."
-# type: "gauge"
-go_memstats_mspan_inuse_bytes
-
-# name: "go_memstats_mspan_sys_bytes"
-# description: "Number of bytes used for mspan structures obtained from system."
-# type: "gauge"
-go_memstats_mspan_sys_bytes
-
-# name: "go_memstats_next_gc_bytes"
-# description: "Number of heap bytes when next garbage collection will take place."
-# type: "gauge"
-go_memstats_next_gc_bytes
-
-# name: "go_memstats_other_sys_bytes"
-# description: "Number of bytes used for other system allocations."
-# type: "gauge"
-go_memstats_other_sys_bytes
-
-# name: "go_memstats_stack_inuse_bytes"
-# description: "Number of bytes in use by the stack allocator."
-# type: "gauge"
-go_memstats_stack_inuse_bytes
-
-# name: "go_memstats_stack_sys_bytes"
-# description: "Number of bytes obtained from system for stack allocator."
-# type: "gauge"
-go_memstats_stack_sys_bytes
-
-# name: "go_memstats_sys_bytes"
-# description: "Number of bytes obtained by system. Sum of all system allocations."
-# type: "gauge"
-go_memstats_sys_bytes
-
-# name: "grpc_server_handled_total"
-# description: "Total number of RPCs completed on the server, regardless of success or failure."
-# type: "counter"
-# gRPC codes: 
-#  - "OK"
-#  - "Unavailable"
-grpc_server_handled_total{grpc_code="CODE",grpc_method="DeleteRange",grpc_service="etcdserverpb.KV",grpc_type="unary"}
-grpc_server_handled_total{grpc_code="CODE",grpc_method="Put",grpc_service="etcdserverpb.KV",grpc_type="unary"}
-grpc_server_handled_total{grpc_code="CODE",grpc_method="Range",grpc_service="etcdserverpb.KV",grpc_type="unary"}
-grpc_server_handled_total{grpc_code="CODE",grpc_method="Watch",grpc_service="etcdserverpb.Watch",grpc_type="bidi_stream"}
-
-# name: "grpc_server_msg_received_total"
-# description: "Total number of RPC stream messages received on the server."
-# type: "counter"
-grpc_server_msg_received_total{grpc_method="DeleteRange",grpc_service="etcdserverpb.KV",grpc_type="unary"}
-grpc_server_msg_received_total{grpc_method="Put",grpc_service="etcdserverpb.KV",grpc_type="unary"}
-grpc_server_msg_received_total{grpc_method="Range",grpc_service="etcdserverpb.KV",grpc_type="unary"}
-grpc_server_msg_received_total{grpc_method="Watch",grpc_service="etcdserverpb.Watch",grpc_type="bidi_stream"}
-
-# name: "grpc_server_msg_sent_total"
-# description: "Total number of gRPC stream messages sent by the server."
-# type: "counter"
-grpc_server_msg_sent_total{grpc_method="DeleteRange",grpc_service="etcdserverpb.KV",grpc_type="unary"}
-grpc_server_msg_sent_total{grpc_method="Put",grpc_service="etcdserverpb.KV",grpc_type="unary"}
-grpc_server_msg_sent_total{grpc_method="Range",grpc_service="etcdserverpb.KV",grpc_type="unary"}
-grpc_server_msg_sent_total{grpc_method="Watch",grpc_service="etcdserverpb.Watch",grpc_type="bidi_stream"}
-
-# name: "grpc_server_started_total"
-# description: "Total number of RPCs started on the server."
-# type: "counter"
-grpc_server_started_total{grpc_method="DeleteRange",grpc_service="etcdserverpb.KV",grpc_type="unary"}
-grpc_server_started_total{grpc_method="Put",grpc_service="etcdserverpb.KV",grpc_type="unary"}
-grpc_server_started_total{grpc_method="Range",grpc_service="etcdserverpb.KV",grpc_type="unary"}
-grpc_server_started_total{grpc_method="Watch",grpc_service="etcdserverpb.Watch",grpc_type="bidi_stream"}
-
-# name: "http_request_duration_microseconds"
-# description: "The HTTP request latencies in microseconds."
-# type: "summary"
-http_request_duration_microseconds{handler="prometheus",quantile="0.5"}
-http_request_duration_microseconds{handler="prometheus",quantile="0.9"}
-http_request_duration_microseconds{handler="prometheus",quantile="0.99"}
-http_request_duration_microseconds_sum{handler="prometheus"}
-http_request_duration_microseconds_count{handler="prometheus"}
-
-# name: "http_request_size_bytes"
-# description: "The HTTP request sizes in bytes."
-# type: "summary"
-http_request_size_bytes{handler="prometheus",quantile="0.5"}
-http_request_size_bytes{handler="prometheus",quantile="0.9"}
-http_request_size_bytes{handler="prometheus",quantile="0.99"}
-http_request_size_bytes_sum{handler="prometheus"}
-http_request_size_bytes_count{handler="prometheus"}
-
-# name: "http_response_size_bytes"
-# description: "The HTTP response sizes in bytes."
-# type: "summary"
-http_response_size_bytes{handler="prometheus",quantile="0.5"}
-http_response_size_bytes{handler="prometheus",quantile="0.9"}
-http_response_size_bytes{handler="prometheus",quantile="0.99"}
-http_response_size_bytes_sum{handler="prometheus"}
-http_response_size_bytes_count{handler="prometheus"}
-

Documentation/metrics/v3.1.14

@@ -1,516 +0,0 @@
-# server version: unknown
-
-# name: "etcd_debugging_mvcc_db_compaction_pause_duration_milliseconds"
-# description: "Bucketed histogram of db compaction pause duration."
-# type: "histogram"
-etcd_debugging_mvcc_db_compaction_pause_duration_milliseconds_bucket{le="1"}
-etcd_debugging_mvcc_db_compaction_pause_duration_milliseconds_bucket{le="2"}
-etcd_debugging_mvcc_db_compaction_pause_duration_milliseconds_bucket{le="4"}
-etcd_debugging_mvcc_db_compaction_pause_duration_milliseconds_bucket{le="8"}
-etcd_debugging_mvcc_db_compaction_pause_duration_milliseconds_bucket{le="16"}
-etcd_debugging_mvcc_db_compaction_pause_duration_milliseconds_bucket{le="32"}
-etcd_debugging_mvcc_db_compaction_pause_duration_milliseconds_bucket{le="64"}
-etcd_debugging_mvcc_db_compaction_pause_duration_milliseconds_bucket{le="128"}
-etcd_debugging_mvcc_db_compaction_pause_duration_milliseconds_bucket{le="256"}
-etcd_debugging_mvcc_db_compaction_pause_duration_milliseconds_bucket{le="512"}
-etcd_debugging_mvcc_db_compaction_pause_duration_milliseconds_bucket{le="1024"}
-etcd_debugging_mvcc_db_compaction_pause_duration_milliseconds_bucket{le="2048"}
-etcd_debugging_mvcc_db_compaction_pause_duration_milliseconds_bucket{le="4096"}
-etcd_debugging_mvcc_db_compaction_pause_duration_milliseconds_bucket{le="+Inf"}
-etcd_debugging_mvcc_db_compaction_pause_duration_milliseconds_sum
-etcd_debugging_mvcc_db_compaction_pause_duration_milliseconds_count
-
-# name: "etcd_debugging_mvcc_db_compaction_total_duration_milliseconds"
-# description: "Bucketed histogram of db compaction total duration."
-# type: "histogram"
-etcd_debugging_mvcc_db_compaction_total_duration_milliseconds_bucket{le="100"}
-etcd_debugging_mvcc_db_compaction_total_duration_milliseconds_bucket{le="200"}
-etcd_debugging_mvcc_db_compaction_total_duration_milliseconds_bucket{le="400"}
-etcd_debugging_mvcc_db_compaction_total_duration_milliseconds_bucket{le="800"}
-etcd_debugging_mvcc_db_compaction_total_duration_milliseconds_bucket{le="1600"}
-etcd_debugging_mvcc_db_compaction_total_duration_milliseconds_bucket{le="3200"}
-etcd_debugging_mvcc_db_compaction_total_duration_milliseconds_bucket{le="6400"}
-etcd_debugging_mvcc_db_compaction_total_duration_milliseconds_bucket{le="12800"}
-etcd_debugging_mvcc_db_compaction_total_duration_milliseconds_bucket{le="25600"}
-etcd_debugging_mvcc_db_compaction_total_duration_milliseconds_bucket{le="51200"}
-etcd_debugging_mvcc_db_compaction_total_duration_milliseconds_bucket{le="102400"}
-etcd_debugging_mvcc_db_compaction_total_duration_milliseconds_bucket{le="204800"}
-etcd_debugging_mvcc_db_compaction_total_duration_milliseconds_bucket{le="409600"}
-etcd_debugging_mvcc_db_compaction_total_duration_milliseconds_bucket{le="819200"}
-etcd_debugging_mvcc_db_compaction_total_duration_milliseconds_bucket{le="+Inf"}
-etcd_debugging_mvcc_db_compaction_total_duration_milliseconds_sum
-etcd_debugging_mvcc_db_compaction_total_duration_milliseconds_count
-
-# name: "etcd_debugging_mvcc_db_total_size_in_bytes"
-# description: "Total size of the underlying database in bytes."
-# type: "gauge"
-etcd_debugging_mvcc_db_total_size_in_bytes
-
-# name: "etcd_debugging_mvcc_delete_total"
-# description: "Total number of deletes seen by this member."
-# type: "counter"
-etcd_debugging_mvcc_delete_total
-
-# name: "etcd_debugging_mvcc_events_total"
-# description: "Total number of events sent by this member."
-# type: "counter"
-etcd_debugging_mvcc_events_total
-
-# name: "etcd_debugging_mvcc_index_compaction_pause_duration_milliseconds"
-# description: "Bucketed histogram of index compaction pause duration."
-# type: "histogram"
-etcd_debugging_mvcc_index_compaction_pause_duration_milliseconds_bucket{le="0.5"}
-etcd_debugging_mvcc_index_compaction_pause_duration_milliseconds_bucket{le="1"}
-etcd_debugging_mvcc_index_compaction_pause_duration_milliseconds_bucket{le="2"}
-etcd_debugging_mvcc_index_compaction_pause_duration_milliseconds_bucket{le="4"}
-etcd_debugging_mvcc_index_compaction_pause_duration_milliseconds_bucket{le="8"}
-etcd_debugging_mvcc_index_compaction_pause_duration_milliseconds_bucket{le="16"}
-etcd_debugging_mvcc_index_compaction_pause_duration_milliseconds_bucket{le="32"}
-etcd_debugging_mvcc_index_compaction_pause_duration_milliseconds_bucket{le="64"}
-etcd_debugging_mvcc_index_compaction_pause_duration_milliseconds_bucket{le="128"}
-etcd_debugging_mvcc_index_compaction_pause_duration_milliseconds_bucket{le="256"}
-etcd_debugging_mvcc_index_compaction_pause_duration_milliseconds_bucket{le="512"}
-etcd_debugging_mvcc_index_compaction_pause_duration_milliseconds_bucket{le="1024"}
-etcd_debugging_mvcc_index_compaction_pause_duration_milliseconds_bucket{le="+Inf"}
-etcd_debugging_mvcc_index_compaction_pause_duration_milliseconds_sum
-etcd_debugging_mvcc_index_compaction_pause_duration_milliseconds_count
-
-# name: "etcd_debugging_mvcc_keys_total"
-# description: "Total number of keys."
-# type: "gauge"
-etcd_debugging_mvcc_keys_total
-
-# name: "etcd_debugging_mvcc_pending_events_total"
-# description: "Total number of pending events to be sent."
-# type: "gauge"
-etcd_debugging_mvcc_pending_events_total
-
-# name: "etcd_debugging_mvcc_put_total"
-# description: "Total number of puts seen by this member."
-# type: "counter"
-etcd_debugging_mvcc_put_total
-
-# name: "etcd_debugging_mvcc_range_total"
-# description: "Total number of ranges seen by this member."
-# type: "counter"
-etcd_debugging_mvcc_range_total
-
-# name: "etcd_debugging_mvcc_slow_watcher_total"
-# description: "Total number of unsynced slow watchers."
-# type: "gauge"
-etcd_debugging_mvcc_slow_watcher_total
-
-# name: "etcd_debugging_mvcc_txn_total"
-# description: "Total number of txns seen by this member."
-# type: "counter"
-etcd_debugging_mvcc_txn_total
-
-# name: "etcd_debugging_mvcc_watch_stream_total"
-# description: "Total number of watch streams."
-# type: "gauge"
-etcd_debugging_mvcc_watch_stream_total
-
-# name: "etcd_debugging_mvcc_watcher_total"
-# description: "Total number of watchers."
-# type: "gauge"
-etcd_debugging_mvcc_watcher_total
-
-# name: "etcd_debugging_snap_save_marshalling_duration_seconds"
-# description: "The marshalling cost distributions of save called by snapshot."
-# type: "histogram"
-etcd_debugging_snap_save_marshalling_duration_seconds_bucket{le="0.001"}
-etcd_debugging_snap_save_marshalling_duration_seconds_bucket{le="0.002"}
-etcd_debugging_snap_save_marshalling_duration_seconds_bucket{le="0.004"}
-etcd_debugging_snap_save_marshalling_duration_seconds_bucket{le="0.008"}
-etcd_debugging_snap_save_marshalling_duration_seconds_bucket{le="0.016"}
-etcd_debugging_snap_save_marshalling_duration_seconds_bucket{le="0.032"}
-etcd_debugging_snap_save_marshalling_duration_seconds_bucket{le="0.064"}
-etcd_debugging_snap_save_marshalling_duration_seconds_bucket{le="0.128"}
-etcd_debugging_snap_save_marshalling_duration_seconds_bucket{le="0.256"}
-etcd_debugging_snap_save_marshalling_duration_seconds_bucket{le="0.512"}
-etcd_debugging_snap_save_marshalling_duration_seconds_bucket{le="1.024"}
-etcd_debugging_snap_save_marshalling_duration_seconds_bucket{le="2.048"}
-etcd_debugging_snap_save_marshalling_duration_seconds_bucket{le="4.096"}
-etcd_debugging_snap_save_marshalling_duration_seconds_bucket{le="8.192"}
-etcd_debugging_snap_save_marshalling_duration_seconds_bucket{le="+Inf"}
-etcd_debugging_snap_save_marshalling_duration_seconds_sum
-etcd_debugging_snap_save_marshalling_duration_seconds_count
-
-# name: "etcd_debugging_snap_save_total_duration_seconds"
-# description: "The total latency distributions of save called by snapshot."
-# type: "histogram"
-etcd_debugging_snap_save_total_duration_seconds_bucket{le="0.001"}
-etcd_debugging_snap_save_total_duration_seconds_bucket{le="0.002"}
-etcd_debugging_snap_save_total_duration_seconds_bucket{le="0.004"}
-etcd_debugging_snap_save_total_duration_seconds_bucket{le="0.008"}
-etcd_debugging_snap_save_total_duration_seconds_bucket{le="0.016"}
-etcd_debugging_snap_save_total_duration_seconds_bucket{le="0.032"}
-etcd_debugging_snap_save_total_duration_seconds_bucket{le="0.064"}
-etcd_debugging_snap_save_total_duration_seconds_bucket{le="0.128"}
-etcd_debugging_snap_save_total_duration_seconds_bucket{le="0.256"}
-etcd_debugging_snap_save_total_duration_seconds_bucket{le="0.512"}
-etcd_debugging_snap_save_total_duration_seconds_bucket{le="1.024"}
-etcd_debugging_snap_save_total_duration_seconds_bucket{le="2.048"}
-etcd_debugging_snap_save_total_duration_seconds_bucket{le="4.096"}
-etcd_debugging_snap_save_total_duration_seconds_bucket{le="8.192"}
-etcd_debugging_snap_save_total_duration_seconds_bucket{le="+Inf"}
-etcd_debugging_snap_save_total_duration_seconds_sum
-etcd_debugging_snap_save_total_duration_seconds_count
-
-# name: "etcd_debugging_store_expires_total"
-# description: "Total number of expired keys."
-# type: "counter"
-etcd_debugging_store_expires_total
-
-# name: "etcd_debugging_store_reads_total"
-# description: "Total number of reads action by (get/getRecursive), local to this member."
-# type: "counter"
-etcd_debugging_store_reads_total{action="getRecursive"}
-
-# name: "etcd_debugging_store_watch_requests_total"
-# description: "Total number of incoming watch requests (new or reestablished)."
-# type: "counter"
-etcd_debugging_store_watch_requests_total
-
-# name: "etcd_debugging_store_watchers"
-# description: "Count of currently active watchers."
-# type: "gauge"
-etcd_debugging_store_watchers
-
-# name: "etcd_debugging_store_writes_total"
-# description: "Total number of writes (e.g. set/compareAndDelete) seen by this member."
-# type: "counter"
-etcd_debugging_store_writes_total{action="create"}
-etcd_debugging_store_writes_total{action="set"}
-
-# name: "etcd_disk_backend_commit_duration_seconds"
-# description: "The latency distributions of commit called by backend."
-# type: "histogram"
-etcd_disk_backend_commit_duration_seconds_bucket{le="0.001"}
-etcd_disk_backend_commit_duration_seconds_bucket{le="0.002"}
-etcd_disk_backend_commit_duration_seconds_bucket{le="0.004"}
-etcd_disk_backend_commit_duration_seconds_bucket{le="0.008"}
-etcd_disk_backend_commit_duration_seconds_bucket{le="0.016"}
-etcd_disk_backend_commit_duration_seconds_bucket{le="0.032"}
-etcd_disk_backend_commit_duration_seconds_bucket{le="0.064"}
-etcd_disk_backend_commit_duration_seconds_bucket{le="0.128"}
-etcd_disk_backend_commit_duration_seconds_bucket{le="0.256"}
-etcd_disk_backend_commit_duration_seconds_bucket{le="0.512"}
-etcd_disk_backend_commit_duration_seconds_bucket{le="1.024"}
-etcd_disk_backend_commit_duration_seconds_bucket{le="2.048"}
-etcd_disk_backend_commit_duration_seconds_bucket{le="4.096"}
-etcd_disk_backend_commit_duration_seconds_bucket{le="8.192"}
-etcd_disk_backend_commit_duration_seconds_bucket{le="+Inf"}
-etcd_disk_backend_commit_duration_seconds_sum
-etcd_disk_backend_commit_duration_seconds_count
-
-# name: "etcd_disk_wal_fsync_duration_seconds"
-# description: "The latency distributions of fsync called by wal."
-# type: "histogram"
-etcd_disk_wal_fsync_duration_seconds_bucket{le="0.001"}
-etcd_disk_wal_fsync_duration_seconds_bucket{le="0.002"}
-etcd_disk_wal_fsync_duration_seconds_bucket{le="0.004"}
-etcd_disk_wal_fsync_duration_seconds_bucket{le="0.008"}
-etcd_disk_wal_fsync_duration_seconds_bucket{le="0.016"}
-etcd_disk_wal_fsync_duration_seconds_bucket{le="0.032"}
-etcd_disk_wal_fsync_duration_seconds_bucket{le="0.064"}
-etcd_disk_wal_fsync_duration_seconds_bucket{le="0.128"}
-etcd_disk_wal_fsync_duration_seconds_bucket{le="0.256"}
-etcd_disk_wal_fsync_duration_seconds_bucket{le="0.512"}
-etcd_disk_wal_fsync_duration_seconds_bucket{le="1.024"}
-etcd_disk_wal_fsync_duration_seconds_bucket{le="2.048"}
-etcd_disk_wal_fsync_duration_seconds_bucket{le="4.096"}
-etcd_disk_wal_fsync_duration_seconds_bucket{le="8.192"}
-etcd_disk_wal_fsync_duration_seconds_bucket{le="+Inf"}
-etcd_disk_wal_fsync_duration_seconds_sum
-etcd_disk_wal_fsync_duration_seconds_count
-
-# name: "etcd_grpc_proxy_cache_hits_total"
-# description: "Total number of cache hits"
-# type: "gauge"
-etcd_grpc_proxy_cache_hits_total
-
-# name: "etcd_grpc_proxy_cache_misses_total"
-# description: "Total number of cache misses"
-# type: "gauge"
-etcd_grpc_proxy_cache_misses_total
-
-# name: "etcd_grpc_proxy_events_coalescing_total"
-# description: "Total number of events coalescing"
-# type: "counter"
-etcd_grpc_proxy_events_coalescing_total
-
-# name: "etcd_grpc_proxy_watchers_coalescing_total"
-# description: "Total number of current watchers coalescing"
-# type: "gauge"
-etcd_grpc_proxy_watchers_coalescing_total
-
-# name: "etcd_network_client_grpc_received_bytes_total"
-# description: "The total number of bytes received from grpc clients."
-# type: "counter"
-etcd_network_client_grpc_received_bytes_total
-
-# name: "etcd_network_client_grpc_sent_bytes_total"
-# description: "The total number of bytes sent to grpc clients."
-# type: "counter"
-etcd_network_client_grpc_sent_bytes_total
-
-# name: "etcd_network_peer_received_bytes_total"
-# description: "The total number of bytes received from peers."
-# type: "counter"
-etcd_network_peer_received_bytes_total{From="REMOTE_PEER_NODE_ID"}
-
-# name: "etcd_network_peer_round_trip_time_seconds"
-# description: "Round-Trip-Time histogram between peers."
-# type: "histogram"
-etcd_network_peer_round_trip_time_seconds_bucket{To="REMOTE_PEER_NODE_ID",le="+Inf"}
-etcd_network_peer_round_trip_time_seconds_bucket{To="REMOTE_PEER_NODE_ID",le="0.0001"}
-etcd_network_peer_round_trip_time_seconds_bucket{To="REMOTE_PEER_NODE_ID",le="0.0002"}
-etcd_network_peer_round_trip_time_seconds_bucket{To="REMOTE_PEER_NODE_ID",le="0.0004"}
-etcd_network_peer_round_trip_time_seconds_bucket{To="REMOTE_PEER_NODE_ID",le="0.0008"}
-etcd_network_peer_round_trip_time_seconds_bucket{To="REMOTE_PEER_NODE_ID",le="0.0016"}
-etcd_network_peer_round_trip_time_seconds_bucket{To="REMOTE_PEER_NODE_ID",le="0.0032"}
-etcd_network_peer_round_trip_time_seconds_bucket{To="REMOTE_PEER_NODE_ID",le="0.0064"}
-etcd_network_peer_round_trip_time_seconds_bucket{To="REMOTE_PEER_NODE_ID",le="0.0128"}
-etcd_network_peer_round_trip_time_seconds_bucket{To="REMOTE_PEER_NODE_ID",le="0.0256"}
-etcd_network_peer_round_trip_time_seconds_bucket{To="REMOTE_PEER_NODE_ID",le="0.0512"}
-etcd_network_peer_round_trip_time_seconds_bucket{To="REMOTE_PEER_NODE_ID",le="0.1024"}
-etcd_network_peer_round_trip_time_seconds_bucket{To="REMOTE_PEER_NODE_ID",le="0.2048"}
-etcd_network_peer_round_trip_time_seconds_bucket{To="REMOTE_PEER_NODE_ID",le="0.4096"}
-etcd_network_peer_round_trip_time_seconds_bucket{To="REMOTE_PEER_NODE_ID",le="0.8192"}
-etcd_network_peer_round_trip_time_seconds_count{To="REMOTE_PEER_NODE_ID"}
-etcd_network_peer_round_trip_time_seconds_sum{To="REMOTE_PEER_NODE_ID"}
-
-# name: "etcd_network_peer_sent_bytes_total"
-# description: "The total number of bytes sent to peers."
-# type: "counter"
-etcd_network_peer_sent_bytes_total{To="REMOTE_PEER_NODE_ID"}
-
-# name: "etcd_server_has_leader"
-# description: "Whether or not a leader exists. 1 is existence, 0 is not."
-# type: "gauge"
-etcd_server_has_leader
-
-# name: "etcd_server_is_leader"
-# description: "Whether or not this member is a leader. 1 if is, 0 otherwise."
-# type: "gauge"
-etcd_server_is_leader
-
-# name: "etcd_server_leader_changes_seen_total"
-# description: "The number of leader changes seen."
-# type: "counter"
-etcd_server_leader_changes_seen_total
-
-# name: "etcd_server_proposals_applied_total"
-# description: "The total number of consensus proposals applied."
-# type: "gauge"
-etcd_server_proposals_applied_total
-
-# name: "etcd_server_proposals_committed_total"
-# description: "The total number of consensus proposals committed."
-# type: "gauge"
-etcd_server_proposals_committed_total
-
-# name: "etcd_server_proposals_failed_total"
-# description: "The total number of failed proposals seen."
-# type: "counter"
-etcd_server_proposals_failed_total
-
-# name: "etcd_server_proposals_pending"
-# description: "The current number of pending proposals to commit."
-# type: "gauge"
-etcd_server_proposals_pending
-
-# name: "go_gc_duration_seconds"
-# description: "A summary of the GC invocation durations."
-# type: "summary"
-go_gc_duration_seconds{quantile="0"}
-go_gc_duration_seconds{quantile="0.25"}
-go_gc_duration_seconds{quantile="0.5"}
-go_gc_duration_seconds{quantile="0.75"}
-go_gc_duration_seconds{quantile="1"}
-go_gc_duration_seconds_sum
-go_gc_duration_seconds_count
-
-# name: "go_goroutines"
-# description: "Number of goroutines that currently exist."
-# type: "gauge"
-go_goroutines
-
-# name: "go_memstats_alloc_bytes"
-# description: "Number of bytes allocated and still in use."
-# type: "gauge"
-go_memstats_alloc_bytes
-
-# name: "go_memstats_alloc_bytes_total"
-# description: "Total number of bytes allocated, even if freed."
-# type: "counter"
-go_memstats_alloc_bytes_total
-
-# name: "go_memstats_buck_hash_sys_bytes"
-# description: "Number of bytes used by the profiling bucket hash table."
-# type: "gauge"
-go_memstats_buck_hash_sys_bytes
-
-# name: "go_memstats_frees_total"
-# description: "Total number of frees."
-# type: "counter"
-go_memstats_frees_total
-
-# name: "go_memstats_gc_sys_bytes"
-# description: "Number of bytes used for garbage collection system metadata."
-# type: "gauge"
-go_memstats_gc_sys_bytes
-
-# name: "go_memstats_heap_alloc_bytes"
-# description: "Number of heap bytes allocated and still in use."
-# type: "gauge"
-go_memstats_heap_alloc_bytes
-
-# name: "go_memstats_heap_idle_bytes"
-# description: "Number of heap bytes waiting to be used."
-# type: "gauge"
-go_memstats_heap_idle_bytes
-
-# name: "go_memstats_heap_inuse_bytes"
-# description: "Number of heap bytes that are in use."
-# type: "gauge"
-go_memstats_heap_inuse_bytes
-
-# name: "go_memstats_heap_objects"
-# description: "Number of allocated objects."
-# type: "gauge"
-go_memstats_heap_objects
-
-# name: "go_memstats_heap_released_bytes_total"
-# description: "Total number of heap bytes released to OS."
-# type: "counter"
-go_memstats_heap_released_bytes_total
-
-# name: "go_memstats_heap_sys_bytes"
-# description: "Number of heap bytes obtained from system."
-# type: "gauge"
-go_memstats_heap_sys_bytes
-
-# name: "go_memstats_last_gc_time_seconds"
-# description: "Number of seconds since 1970 of last garbage collection."
-# type: "gauge"
-go_memstats_last_gc_time_seconds
-
-# name: "go_memstats_lookups_total"
-# description: "Total number of pointer lookups."
-# type: "counter"
-go_memstats_lookups_total
-
-# name: "go_memstats_mallocs_total"
-# description: "Total number of mallocs."
-# type: "counter"
-go_memstats_mallocs_total
-
-# name: "go_memstats_mcache_inuse_bytes"
-# description: "Number of bytes in use by mcache structures."
-# type: "gauge"
-go_memstats_mcache_inuse_bytes
-
-# name: "go_memstats_mcache_sys_bytes"
-# description: "Number of bytes used for mcache structures obtained from system."
-# type: "gauge"
-go_memstats_mcache_sys_bytes
-
-# name: "go_memstats_mspan_inuse_bytes"
-# description: "Number of bytes in use by mspan structures."
-# type: "gauge"
-go_memstats_mspan_inuse_bytes
-
-# name: "go_memstats_mspan_sys_bytes"
-# description: "Number of bytes used for mspan structures obtained from system."
-# type: "gauge"
-go_memstats_mspan_sys_bytes
-
-# name: "go_memstats_next_gc_bytes"
-# description: "Number of heap bytes when next garbage collection will take place."
-# type: "gauge"
-go_memstats_next_gc_bytes
-
-# name: "go_memstats_other_sys_bytes"
-# description: "Number of bytes used for other system allocations."
-# type: "gauge"
-go_memstats_other_sys_bytes
-
-# name: "go_memstats_stack_inuse_bytes"
-# description: "Number of bytes in use by the stack allocator."
-# type: "gauge"
-go_memstats_stack_inuse_bytes
-
-# name: "go_memstats_stack_sys_bytes"
-# description: "Number of bytes obtained from system for stack allocator."
-# type: "gauge"
-go_memstats_stack_sys_bytes
-
-# name: "go_memstats_sys_bytes"
-# description: "Number of bytes obtained by system. Sum of all system allocations."
-# type: "gauge"
-go_memstats_sys_bytes
-
-# name: "grpc_server_handled_total"
-# description: "Total number of RPCs completed on the server, regardless of success or failure."
-# type: "counter"
-# gRPC codes: 
-#  - "Canceled"
-#  - "OK"
-grpc_server_handled_total{grpc_code="CODE",grpc_method="DeleteRange",grpc_service="etcdserverpb.KV",grpc_type="unary"}
-grpc_server_handled_total{grpc_code="CODE",grpc_method="Put",grpc_service="etcdserverpb.KV",grpc_type="unary"}
-grpc_server_handled_total{grpc_code="CODE",grpc_method="Range",grpc_service="etcdserverpb.KV",grpc_type="unary"}
-grpc_server_handled_total{grpc_code="CODE",grpc_method="Watch",grpc_service="etcdserverpb.Watch",grpc_type="bidi_stream"}
-
-# name: "grpc_server_msg_received_total"
-# description: "Total number of RPC stream messages received on the server."
-# type: "counter"
-grpc_server_msg_received_total{grpc_method="DeleteRange",grpc_service="etcdserverpb.KV",grpc_type="unary"}
-grpc_server_msg_received_total{grpc_method="Put",grpc_service="etcdserverpb.KV",grpc_type="unary"}
-grpc_server_msg_received_total{grpc_method="Range",grpc_service="etcdserverpb.KV",grpc_type="unary"}
-grpc_server_msg_received_total{grpc_method="Watch",grpc_service="etcdserverpb.Watch",grpc_type="bidi_stream"}
-
-# name: "grpc_server_msg_sent_total"
-# description: "Total number of gRPC stream messages sent by the server."
-# type: "counter"
-grpc_server_msg_sent_total{grpc_method="DeleteRange",grpc_service="etcdserverpb.KV",grpc_type="unary"}
-grpc_server_msg_sent_total{grpc_method="Put",grpc_service="etcdserverpb.KV",grpc_type="unary"}
-grpc_server_msg_sent_total{grpc_method="Range",grpc_service="etcdserverpb.KV",grpc_type="unary"}
-grpc_server_msg_sent_total{grpc_method="Watch",grpc_service="etcdserverpb.Watch",grpc_type="bidi_stream"}
-
-# name: "grpc_server_started_total"
-# description: "Total number of RPCs started on the server."
-# type: "counter"
-grpc_server_started_total{grpc_method="DeleteRange",grpc_service="etcdserverpb.KV",grpc_type="unary"}
-grpc_server_started_total{grpc_method="Put",grpc_service="etcdserverpb.KV",grpc_type="unary"}
-grpc_server_started_total{grpc_method="Range",grpc_service="etcdserverpb.KV",grpc_type="unary"}
-grpc_server_started_total{grpc_method="Watch",grpc_service="etcdserverpb.Watch",grpc_type="bidi_stream"}
-
-# name: "http_request_duration_microseconds"
-# description: "The HTTP request latencies in microseconds."
-# type: "summary"
-http_request_duration_microseconds{handler="prometheus",quantile="0.5"}
-http_request_duration_microseconds{handler="prometheus",quantile="0.9"}
-http_request_duration_microseconds{handler="prometheus",quantile="0.99"}
-http_request_duration_microseconds_sum{handler="prometheus"}
-http_request_duration_microseconds_count{handler="prometheus"}
-
-# name: "http_request_size_bytes"
-# description: "The HTTP request sizes in bytes."
-# type: "summary"
-http_request_size_bytes{handler="prometheus",quantile="0.5"}
-http_request_size_bytes{handler="prometheus",quantile="0.9"}
-http_request_size_bytes{handler="prometheus",quantile="0.99"}
-http_request_size_bytes_sum{handler="prometheus"}
-http_request_size_bytes_count{handler="prometheus"}
-
-# name: "http_response_size_bytes"
-# description: "The HTTP response sizes in bytes."
-# type: "summary"
-http_response_size_bytes{handler="prometheus",quantile="0.5"}
-http_response_size_bytes{handler="prometheus",quantile="0.9"}
-http_response_size_bytes{handler="prometheus",quantile="0.99"}
-http_response_size_bytes_sum{handler="prometheus"}
-http_response_size_bytes_count{handler="prometheus"}
-