Nice!
No, you probably want to find some way to partition/shard your edits
across multiple logs.
I think the only logic which exists was to close a log when the quorum
members die unexpectedly. There is no kind of "lease" which will
automatically close a log if the client goes away.
On 7/14/20 1:14 AM, Göktürk Gezer wrote:
Hello,
We are currently experimenting with the ratis log-service to store file-system
edit logs.
For storing a billion entries;
- Would advise against using a single log instance?
- When a log instance has no active reader/writer clients, is there any
optimization available to isolate and close its internal resources?
Thanks,
Gokturk
