raft-dev

The state machine's idempotency is critical here since RAFT cannot guarantee exactly-once command

Hi saurabh ratna, Since that sounds very specific to the braft implementation, you might want to ask

For a crashed node, we can assign it a new UUID and use reconfiguration to remove the one with old

Actually, I have only a purpose is performance analysis for raft and PoW consensus protocols. As a

Yup my bad, thank you for the clarification! Will it be safe to assume that the persistent state

Sorry if what I said was ambiguous... The majority *may* include the leader, but doesn't have to,

On Mon, Jun 3, 2024 at 2:58 PM H Wang <howard.w...@gmail.com> wrote: a fresh new S1,

I'm just sending a brief follow up here. Dong confirmed (off-list) that the mp4 is accessible

Replicated logs should use the original term number. It is not safe to change them to the new term

Hi Dongbin, I'll begin with a disclaimer that I've forgotten many of Raft's details, so

Wrap your TLS Listener (and Dialer) in this interface: https://pkg.go.dev/github.com/hashicorp/raft#

If a voter that has the most recent logs, ie, greatest `(last_term, last_log_index)`, and can not

The way I see it, if an empty log node manages to get a majority, some of the raft properties would

On Sunday, January 7, 2024 at 8:25:10 PM UTC-6 Pablo Pessolani wrote: In this case, the Candidate

Hi all, This is to inform that the issue has been resolved. We need to keep only one version of

You said two different things: (a) avoiding where "two nodes can lead at the same time" and

Thanks Diego -- this is an interesting list to be part of, and it was a pity to see it being abused.

In $6.3 of the dissertation, it explains how we can handle duplicated requests which causes problem

Log compaction is a separate step Let's assume that you don't _have_ log compaction, and you

* Srinivas V <sriniv...@gmail.com> [23/07/03 09:55]: > Hi All, > I had a quick design

thank you Karlis for your advice .. really it is magical solution of this problem :) On Friday, April

One clarification on this. Updating nextIndex doesn't have to be perfect, since it will self-

Your understanding of the approach is correct, but I'm not so sure about the second scenario. Yes

Thanks, I got your point. On Saturday, March 4, 2023 at 3:54:45 PM UTC-6 ous...@cs.stanford.edu wrote

The way I imagine this looking is something like this: class LogEntry: term: int command: Command log

To clarify, I am assuming a synchronous update to the state machine along with the commitIndex. The

No, a new election timeout must be chosen for each election. This ensures that if multiple nodes

Aha! Correct - sorry I missed that. /Jesper > 7 dec. 2022 kl. 10:27 skrev Free Ekanayaka <free.

Did you ensure that each follower grants at most one vote per term? zeroes18...@gmail.com schrieb am

Hey, I can surely provide some clarification about how to use dqlite, if needed, but unfortunately