From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Date: Wed, 24 Oct 2018 19:53:34 +0300 From: Konstantin Osipov Subject: Re: [PATCH v2 4/4] wal: delete old wal files when running out of disk space Message-ID: <20181024165334.GC12973@chai> References: <20181023184645.GC29694@chai> <20181024095116.ldsc3j2dn4kmzsjy@esperanza> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20181024095116.ldsc3j2dn4kmzsjy@esperanza> To: Vladimir Davydov Cc: tarantool-patches@freelists.org List-ID: * Vladimir Davydov [18/10/24 12:55]: > No, this isn't true. WAL watcher was introduced as a generic > notification channel built over cbus in the first place. Before > it was made available, we used inotify to track WAL directory > changes in relays. > > > Now you can send a direct message to gc. Why use wal watcher api at > > all? > > Because we already have a generic abstraction, and I think we'd better > use it instead of adding another wal-tx pipe to the wal_thread and > implementing home-brewed notifications on top of it. Well, the pipe costs nearly nothing at runtime. It is point to point delivery. The watcher api is broadcast by nature. Can't we use the existing pipe? We no longer delete any files on the receiving side. -- Konstantin Osipov, Moscow, Russia, +7 903 626 22 32 http://tarantool.io - www.twitter.com/kostja_osipov