Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1uodR9-007FOf-4t for pgsql-admin@arkaria.postgresql.org; Wed, 20 Aug 2025 07:40:48 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1uodR8-005giS-JO for pgsql-admin@arkaria.postgresql.org; Wed, 20 Aug 2025 07:40:47 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1uodR8-005gi7-69 for pgsql-admin@lists.postgresql.org; Wed, 20 Aug 2025 07:40:46 +0000 Received: from mail-wm1-x333.google.com ([2a00:1450:4864:20::333]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.96) (envelope-from ) id 1uodR4-000nyz-2P for pgsql-admin@lists.postgresql.org; Wed, 20 Aug 2025 07:40:45 +0000 Received: by mail-wm1-x333.google.com with SMTP id 5b1f17b1804b1-45a1b0b6ac4so32014065e9.2 for ; Wed, 20 Aug 2025 00:40:43 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1755675640; x=1756280440; darn=lists.postgresql.org; h=to:subject:message-id:date:from:mime-version:from:to:cc:subject :date:message-id:reply-to; bh=AlVGJk+TF1Zi6EI6R8MQlaFApzc2Zh9P8zPCzlSS+l4=; b=Zi1XCU04lxhSI1/sp+8IhoUszp8GwNn7WEzPRV+4uVTTk3gxORm/CZj6171aDpOjaR 978lZkV+yWN91/mwSraM6wcfgJDB1uy6xo/nbxrUDjxR+p7sHxjbqnfdEIxEEiCBTVmO rhfQVSTgP0ysV8tj/hQ+Tnv2Ifp+sB4MjsgvSlYuNVUyv31REBxLw7BF8VSs2cn3Yvxt +I2/J3wZXBcY/bv+v7VpEhWa4d56m+oOodFo9bT8yfoFlZ4ZX2zQrKD1M6vJBjHUVpnG RVRIVNt1iH++X1+7ilvDjLosZw0eFBeJn/ueWC2F5YaZUF4EbalEqajDwjx5+oZFLYL2 JzAg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1755675640; x=1756280440; h=to:subject:message-id:date:from:mime-version:x-gm-message-state :from:to:cc:subject:date:message-id:reply-to; bh=AlVGJk+TF1Zi6EI6R8MQlaFApzc2Zh9P8zPCzlSS+l4=; b=CjZO+STM3+affe8eJNuE5EKe6X+c8DucujhZ+gHGD5+y6eyZ+CTxKLPGgOzW0SUQZZ TcpGsP/9GGuVh8MVNF1p2WYhpg/c1oxgSIJpQZSSf5DhGOq2LvpxcpX12xQzrse9nH0d mcNJ6/PaT6r/+AwccCGS3jWoVwcgF2Xeyv3HJj9Eh+QXF/tfFDPxhQwZKfebsDMQOOBL stmU6Ia2zXS0cTpqY4nQej2abgJMS4nFCROGNGxU6X9Kw0N7T6Wl8Ar3oUAcIZi+NvUk xCe5xYWamm41i915dS6osN9X2z6DSerxICT5FS7nf1jccj4aAHRY5cGnMJ9nuxTk/dUM BHAg== X-Gm-Message-State: AOJu0YzVOwBy4+oK36SixQPcxTX24R29s/xtT1ASkBQJEeEcmavHeuIy 8X4O0op0+ldF48m6JZ/v0PVfUDF8SBZNMf+rWRMWvxEw1XrwJNLiM4q1e9qIMvChLMccofguOl3 nrsgAcHF9Dk7ad9z/BrMMf4ne0hDTHpQobuv82wzBSw== X-Gm-Gg: ASbGnctTqtvmea1rnTF7BaGZjsIvn524FT0DMGA6wsXEt+AQeSVco6WFdbj9GrxxTGg Mkd3IaDkulEkNt6tnNY4PExqJ/Or/XufX6clA3nhgdmjmN9bOvzt3C+MJgpxQA2CBzbmqmlSdk3 QX2QnuRN0aOk4382rTbIkY1umC0A0TrNAckjoEeYYyJMgrTHKkQ2voEVM9579UT54sOgUBbybU+ m9izpWZ X-Google-Smtp-Source: AGHT+IGuYkeCDErQVOhGOty8hwonzi2tUd1UV6uIf7mKj+H685rt1nFRs3HJdJhrfK6s3DJkqMMxscmVPxN0BvS7+z8= X-Received: by 2002:a05:600c:1e89:b0:459:e398:ed80 with SMTP id 5b1f17b1804b1-45b47a0700bmr10050445e9.32.1755675640264; Wed, 20 Aug 2025 00:40:40 -0700 (PDT) MIME-Version: 1.0 From: SOzcn Date: Wed, 20 Aug 2025 10:40:22 +0300 X-Gm-Features: Ac12FXxwsmo-dklTBmW0-fEMSIXqqYt6i1GRMTVQqimCdyTffUJ9jN4zHkYm-Wg Message-ID: Subject: PostgreSQL - HA Cluster / Etcd Issue To: Pgsql-admin Content-Type: multipart/alternative; boundary="000000000000e0fd0c063cc71653" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --000000000000e0fd0c063cc71653 Content-Type: text/plain; charset="UTF-8" Hello, In my database architecture, I use Etcd, Patroni, HAProxy, and Keepalived. Although many things in this architecture work as expected, Etcd encounters the error "memberID:5960773920904691185 alarm:NOSPACE" once every 2 or 3 months. The root cause is that the database size reaches the specified limit and Etcd does not clean it up through rotation. I am aware of this, but despite reviewing the maintenance documentation, I could not find the most appropriate parameter values for this rotation. I am sharing an example of my own Etcd configuration below. I kindly ask you to share your experience on this matter. I am kinda stuck on this issue. In particular, is it possible to schedule the parameter that performs this cleanup with a time setting? For example, can I tell it to run the compact operation at around 01:00 AM? Best regards. [Unit] Description=etcd service Documentation=https://github.com/etcd-io/etcd After=network.target [Service] User=etcd Type=notify ExecStart=/usr/local/sbin/etcd \ --name etcd1 \ --data-dir=/etc/etcd \ --initial-advertise-peer-urls=http://10.115.208.168:2380 \ --listen-peer-urls=http://192.168.1.1:2380 \ --listen-client-urls=http://192.168.1.1:2379,http://127.0.0.1:2379 \ --advertise-client-urls=192.168.1.1:2379 \ --initial-cluster-token="etcd-cluster" \ --initial-cluster="etcd1=http://192.168.1.1:2380,etcd2= http://192.168.1.2:2380,etcd3=http://3:2380" \ --initial-cluster-state="new" \ --log-level="error" [Install] WantedBy=multi-user.target --000000000000e0fd0c063cc71653 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hello,

In my database architecture, I use Etcd, Pat= roni, HAProxy, and Keepalived.

Although many things in this architec= ture work as expected, Etcd encounters the error "memberID:59607739209= 04691185 alarm:NOSPACE" once every 2 or 3 months. The root cause is th= at the database size reaches the specified limit and Etcd does not clean it= up through rotation. I am aware of this, but despite reviewing the mainten= ance documentation, I could not find the most appropriate parameter values = for this rotation. I am sharing an example of my own Etcd configuration bel= ow. I kindly ask you to share your experience on this matter. I am kinda st= uck on this issue.

In particular, is it possible to schedule the par= ameter that performs this cleanup with a time setting? For example, can I t= ell it to run the compact operation at around=C2=A001:00=C2=A0AM?

<= /div>
Best regards.


[Unit]
D= escription=3Detcd service
Documentation=3Dhttps://github.com/etcd-io/etcd
After=3Dnetwork.target=

[Service]
User=3Detcd
Type=3Dnotify
ExecStart=3D/usr/local= /sbin/etcd \
=C2=A0 --name etcd1 \
=C2=A0 --data-dir=3D/etc/etcd \=C2=A0 --initial-advertise-peer-urls=3Dhttp://10.115.208.168:2380 \
=C2=A0 --listen-peer-urls=3Dhttp://192.168.1.1:2380 \
=C2=A0 --list= en-client-urls=3Dhttp://192.168.1.1:237= 9,http://127.0.0.1:2379 \
=C2= =A0 --advertise-client-urls=3D192.168.1= .1:2379 \
=C2=A0 --initial-cluster-token=3D"etcd-cluster" = \
=C2=A0 --initial-cluster=3D"etcd1=3Dhttp://192.168.1.1:2380,etcd2=3Dhttp://192.168.1.2:2380,etcd3=3Dhttp://3:= 2380" \
=C2=A0 --initial-cluster-state=3D"new" \
= =C2=A0 --log-level=3D"error"

[Install]
WantedBy=3Dmulti= -user.target
--000000000000e0fd0c063cc71653--