[tarantool-patches] Re: [PATCH 9/9] wal: trigger checkpoint if there are too many WALs
Konstantin Osipov
kostja at tarantool.org
Tue Dec 4 15:53:43 MSK 2018
* Vladimir Davydov <vdavydov.dev at gmail.com> [18/12/04 15:38]:
> On Mon, Dec 03, 2018 at 11:34:17PM +0300, Konstantin Osipov wrote:
> > * Vladimir Davydov <vdavydov.dev at gmail.com> [18/11/28 19:16]:
> >
> > Please avoid using 0 for infinity: Tarantool doesn't use 0 to mean
> > anything special.
>
> As a matter of fact, we do - setting checkpoint_interval/count to 0
> results in infinite checkpoint interval/count.
Actually I could just as well say that it results in 0
checkpoints.
0 checkpoint interval for a non-zero value of checkpoint_count
should be forbidden - it doesn't make any sense.
> I want to make
> checkpoint_wal_threshold consistent with those configuration options.
> Anyway, if 0 doesn't mean infinity, what should one set
> checkpoint_wal_threshold to to disable this feature? A very large value?
> What value? 100 GB, 100 TB? Would look weird in box.cfg IMO.
Yes, please set it to 2^64-1
--
Konstantin Osipov, Moscow, Russia, +7 903 626 22 32
http://tarantool.io - www.twitter.com/kostja_osipov
More information about the Tarantool-patches
mailing list