etcd-io/etcd

Find and classify all the exit codes returned by etcdserver

Open

#21032 opened on Dec 17, 2025

View on GitHub
 (9 comments) (0 reactions) (0 assignees)Go (51,701 stars) (10,352 forks)batch import
area/robustness-testinghelp wantedtype/feature

Description

What would you like to be added?

Would be great to understand what are exit codes generated by etcd

Expectation: Table with linking to code paths that call os.Exit (or similar) and the exit code it returns. Possibly a explanation. Could send a PR to documentation.

Why is this needed?

find why we return code 1 here:

https://linuxfoundation.antithesis.com/report/tIS34e56zvz8EGo02cE4NaiW/oHVZIeQ_MCxANyR4-diuJdY5hL7hR4AiRfNN2BmFUS4.html?auth=v2.public.eyJuYmYiOiIyMDI1LTEyLTE3VDEyOjQ0OjMzLjM0NDA0OTQ5M1oiLCJzY29wZSI6eyJSZXBvcnRTY29wZVYxIjp7ImFzc2V0Ijoib0hWWkllUV9NQ3hBTnlSNC1kaXVKZFk1aEw3aFI0QWlSZk5OMkJtRlVTNC5odG1sIiwicmVwb3J0X2lkIjoidElTMzRlNTZ6dno4RUdvMDJjRTROYWlXIn19fXPuVD228qmdQXwuV-pSQCQqosYoQZAdtsyzTbcbBZ1vkRRFyoV8dGb-sepLluyd39_Qcy19G0GRmd7WAHi1pAw#/run/d88bbffe0d5c03a180e1ed7f085a7fd7-44-16/finding/606b95a49077f8782c4e4e9f00f1480e23232903

Contributor guide

Tech stack
go
Domain
backenddatabase
Issue type
documentation
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
Go programmingbasic understanding of etcd architecture
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
80
Research direction
Start by searching the etcd codebase for all calls to os.Exit in the etcdserver package. Focus on the server/ directory, particularly files like server/etcdserver/server.go, server/etcdserver/bootstrap.go, and server/etcdserver/errors.go. Look for exit codes in the range 0-255 and note the context. The issue mentions a specific report where exit code 1 is returned; begin by tracing that path. After collection, compile a table mapping each exit code to its source location and reason. Consider also checking the main.go files in cmd/etcd and any wrapper scripts. The issue expects a PR to docs, so the final output should be a Markdown table ready for inclusion in the documentation.