raft | An implementation of the Raft distributed consensus | Architecture library

I'm trying to add a new organization to Fabric's v2.2 test-network. When I execute the command (on configUpdate.sh; env vars are correctly setup):

Given this simple dataset:

I'm looking for a way to add new members to existing Aeron cluster without reconfiguring existing ones.

It seems cluster members are defined statically during startup as described in the Cluster Tutorial:

i am trying to train my data with spacy v3.0 and appareantly the nlp.update do not accept any tuples. Here is the piece of code:

So I do understand the concept of the Raft Protocol.
But I struggle with it in the use case of a Hyperledger Fabric Ordering Service.

What I understand so far:
When a transaction is proposed and endorsed by peers the application forwards it to the ordering service. The Raft Leader-Node receives this transaction and writes it to his Log then sends it to his Follower-Nodes that also update their Logs.

What I don't understand:

• Where and how are the blocks created?
• Do all Nodes create a Block and check if a majority has the same?

I read somewhere that a Blockcutter-method is invoked by the Leader and the resulting Block is then proposed to the local Raft Finite State Machine (what is this?).

I'm learning Raft from the paper's extended version. In section 5.2 (Leader Election) of the paper, it says:

If a follower receives no communication over a period of time called the election timeout, then it assumes there is no viable leader and begins an election to choose a new leader.

At the same time, the paper says in some cases an RPC can be rejected, for example when it contains a smaller term number.

My question is: when should a follower recognize an RPC as a valid "communication" and record it to prevent itself from timing out?

Edit:

My current implementation is as follows:

• RequestVote resets the timeout only when the server grants vote
• AppendEntries resets the timeout if its term is no smaller than the server's

This works fine in most cases, but sometimes causes a long election. Consider a Raft cluster with 2 servers, both followers. Server #1 has a more up-to-date log, but server #2 has a larger term.

In this setting, server #1 has to continuously start 2 elections to become a leader, which (intuitively) happens with <50% probability. If server #2 starts an election and timeouts, its term increases and the next election by server #1 will fail again. In practice this can cause the whole election to last for several seconds even if there are only a few servers. I wonder if there are some approaches to solve this problem (or if this is in fact not a problem).

I've been struggling to deploy my containers to Docker swarm on Ubuntu server 20.04. I'm trying to use Docker swarm on a single VPS host for zero-downtime deployments.

Running containers with docker-compose everything works.

Now trying to deploy the same docker-compose file to docker swarm.

I see there are a lot of questions about this error, I have seen this solution Raft bad format but I doubled checked and the folders are right and the certs are in there, I also looked at Sans problem but for what I understand I don't need Sans when using Raft (I may be wrong). I think my problem its because I'm not handling the intermediate certificates correctly and I'm getting the error both creating a channel and in the Raft consensus.

So here is what I've done so far:

I created my genesis block using a configtx.yaml and this msp folder structure:

configtx.yaml

I deployed hashicorp vault with 3 replicas. Pod vault-0 is running but the other two pods are in pending status. enter image description here

This is my override yaml,