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 1uoiDK-008lVw-U3 for pgsql-admin@arkaria.postgresql.org; Wed, 20 Aug 2025 12:46:52 +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 1uoiDK-008A7J-AL for pgsql-admin@arkaria.postgresql.org; Wed, 20 Aug 2025 12:46:50 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1uoiDJ-008A7A-TR for pgsql-admin@lists.postgresql.org; Wed, 20 Aug 2025 12:46:50 +0000 Received: from mailout.easymail.ca ([64.68.200.34]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1uoiDH-000uMN-0v for pgsql-admin@lists.postgresql.org; Wed, 20 Aug 2025 12:46:49 +0000 Received: from localhost (localhost [127.0.0.1]) by mailout.easymail.ca (Postfix) with ESMTP id 7B5A9620F6; Wed, 20 Aug 2025 12:46:44 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=elevated-dev.com; s=easymail; t=1755694004; bh=htO8L/mkX6DZPidvud8fbnNhDp3yBI7R9YBCgOSvkyE=; h=Subject:From:In-Reply-To:Date:Cc:References:To:From; b=u+zBzHghi0UCph9xsvVPOkfTpCBHqa8yB/aat+neYb5QvUdSpz3o5XcuZKTNn/N/P zexyDYe3JVjYBeDgLOODBp5r96YJij2fPkqdrYUg3XQxusw1zrXawxTs26bO9iOeli Ok6z4p8e/a7YubiMWE7VBcmcBbao03tnrG0+RuU1CdD/ZitEDj7UXnldh4lyeWCwL2 7H55yWQ0cDEOEW1wabuaqrPLA1YwJYdWdwMGHZm47l7a1i+OkBX2TG0qy0oZ/ZRoBn L4G99hXFf0Sn2h2fAAvBxWD9oUxm7kmZ2vwWXFnc431jgYfEoYjhA6HnyoLSHuxaro cgi+ylYK+QYIw== X-Virus-Scanned: Debian amavisd-new at emo09-pco.easydns.vpn Received: from mailout.easymail.ca ([127.0.0.1]) by localhost (emo09-pco.easydns.vpn [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BupSeNv8Yi7c; Wed, 20 Aug 2025 12:46:44 +0000 (UTC) Received: from smtpclient.apple (165.140.184.195.ip.vcn.com [165.140.184.195]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mailout.easymail.ca (Postfix) with ESMTPSA id 029A361DED; Wed, 20 Aug 2025 12:46:43 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=elevated-dev.com; s=easymail; t=1755694004; bh=htO8L/mkX6DZPidvud8fbnNhDp3yBI7R9YBCgOSvkyE=; h=Subject:From:In-Reply-To:Date:Cc:References:To:From; b=u+zBzHghi0UCph9xsvVPOkfTpCBHqa8yB/aat+neYb5QvUdSpz3o5XcuZKTNn/N/P zexyDYe3JVjYBeDgLOODBp5r96YJij2fPkqdrYUg3XQxusw1zrXawxTs26bO9iOeli Ok6z4p8e/a7YubiMWE7VBcmcBbao03tnrG0+RuU1CdD/ZitEDj7UXnldh4lyeWCwL2 7H55yWQ0cDEOEW1wabuaqrPLA1YwJYdWdwMGHZm47l7a1i+OkBX2TG0qy0oZ/ZRoBn L4G99hXFf0Sn2h2fAAvBxWD9oUxm7kmZ2vwWXFnc431jgYfEoYjhA6HnyoLSHuxaro cgi+ylYK+QYIw== Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3826.700.81\)) Subject: Re: PostgreSQL - HA Cluster / Etcd Issue From: Scott Ribe In-Reply-To: Date: Wed, 20 Aug 2025 06:46:40 -0600 Cc: Pgsql-admin Content-Transfer-Encoding: quoted-printable Message-Id: References: To: SOzcn X-Mailer: Apple Mail (2.3826.700.81) List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk This is a PostgreSQL mailing list, and your question has nothing to do = with PostgreSQL. -- Scott Ribe scott_ribe@elevated-dev.com https://www.linkedin.com/in/scottribe/ > On Aug 20, 2025, at 1:40=E2=80=AFAM, SOzcn = wrote: >=20 > Hello, >=20 > In my database architecture, I use Etcd, Patroni, HAProxy, and = Keepalived. >=20 > 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. >=20 > 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? >=20 > Best regards. >=20 >=20 > [Unit] > Description=3Detcd service > Documentation=3Dhttps://github.com/etcd-io/etcd > After=3Dnetwork.target >=20 > [Service] > User=3Detcd > Type=3Dnotify > ExecStart=3D/usr/local/sbin/etcd \ > --name etcd1 \ > --data-dir=3D/etc/etcd \ > --initial-advertise-peer-urls=3Dhttp://10.115.208.168:2380 \ > --listen-peer-urls=3Dhttp://192.168.1.1:2380 \ > --listen-client-urls=3Dhttp://192.168.1.1:2379,http://127.0.0.1:2379 = \ > --advertise-client-urls=3D192.168.1.1:2379 \ > --initial-cluster-token=3D"etcd-cluster" \ > = --initial-cluster=3D"etcd1=3Dhttp://192.168.1.1:2380,etcd2=3Dhttp://192.16= 8.1.2:2380,etcd3=3Dhttp://3:2380" \ > --initial-cluster-state=3D"new" \ > --log-level=3D"error" >=20 > [Install] > WantedBy=3Dmulti-user.target