@beepbeepbopbop that’s what they do in khepri here so you should be good. I’m gonna try this approach as well.
ostinelli
groovyda
Thanks @ostinelli. Yes please - restarting the cluster is the main use case I was looking for indeed.
0
groovyda
Exadra37
So, in my understanding :ets is not used directly, but ra seems to use :ets.
I couldn’t find in the docs a reference to configure the ets table type. I am asking because I would like to use the duplicate_bag type.
0
mmmries
@ostinelli thanks for starting this project, it looks really cool. I was curious if you have ever used lbm_kv before? GitHub - lindenbaum/lbm_kv: A dynamically-distributed, highly-available, partition-tolerant, in-memory key-value store built with Mnesia. · GitHub
It uses mnesia and handles a dynamic cluster so nodes can join and leave
0
ostinelli
I haven’t, but from a quick glance it still uses the unsplit mechanisms to merge nodes after a netsplit (code here), and in my experience this mechanism does not work well with clusters > 2 nodes.
Ulf still wanted to test it on more than 2 nodes, and if I’m not mistaken evenlbm_kv does only test it on a two nodes conflict.
I still like mnesia but I’ve had way too many issues with it, after all it was born even before the CAP theorem or modern cloud solutions came to life. I also moved away from mnesia in my syn library, which in v3 only uses ETS.
1
shifters98
Is there a configuration option to only have the data in memory i.e. i don’t want or need to persist it to disk
I have checked the RA and RAM config options but nothing obvious springs out
thanks
Tom
0
hst337
shifters98
ostinelli
That’s unfortunately not true. ra uses persistency to store the raft log, and so does ram. I understand that the naming can make you think otherwise, and that’s because originally that’s what I was aiming for.
ram has just been an experiment up to now and I wouldn’t recommend running it in production anyways, rather, maybe for some inspiration on how to use ra.
0