Disable AOF

[sign0]

Hello everyone,

Is it possible to disable AOF on a Tile38 instance?
I do not have a SSD, and I think that my intensive writes are at the origin of a bottleneck...

Thank you

[tidwall]

Hi @sign0,

There's isn't an explicit option to disable AOF at the moment.

But it's possible to symlink the AOF file to /dev/null

$ cd data
$ ln -s /dev/null appendonly.aof

Also avoid the AOFSHRINK command when using a symlink.

I hope to add an --appendonly no flag in the future.

[sign0]

Thanks for your advice !

This is really problematic for me, because in 4 days of use, the file already weighs 570GB, to store only data with TTL ...

Moreover, I feel like having another bug (EPIPE) after a few days of intensive use : dozens of inserts containing hundreds of big points (10 fields + geojson + big key) via the redis protocol (redis-cli), per minutes. But I'm not sure that the bug comes from you, although I directly pipe the data into via nodeJS spawn and redis-cli --pipe (I believe that is the case because the problem occurs after several days). And the problem persists as long as I do not have reset tile38 with cleaned appendonly.aof.

events.js:160
throw er; // Unhandled 'error' event
^

Error: write EPIPE
at exports._errnoException (util.js:1020:11)
at WriteWrap.afterWrite (net.js:800:14)

It is also possible that the problem comes from my keys. Indeed, I have a little tweaked to get my way. Here is my key model : ID1__ID2__ID3### (to use both INTERSECT, MATCH, WHERE and retrieve json + fields in one query). My database not exceeds the 2-3 million key:values with TTL, do you think this could cause bugs / problems within Tile38?

Anyway, I'm really a fan of tile38, I really looked for months before finding you! :)