datatechnology / cornerstone Goto Github PK

Hello,
Can you please provide your inputs -
Consider I have 5 servers (S1,S2,S3,S4,S5) , and 7 tasks which are running on these servers. Each task needs 2 replicas.
For task T1 - I can have S1,S2,S3 where S1 is the leader
For task T2 - I can have S2,S1,S3 where S2 is the leader
and so on. Its possible one of the server goes down, then I should be able to add one of the existing server like say if S1 goes down, I should be able to S4 instead.

Can cornerstone be used for such kind of use case, do you have some pointers for this.
regards

Currently there is a recursive lock in raft_server which is used to concurrent all resource access in side that object, we should reduce the contention by using small locks

I had a look through the code, but no raft implementation could be correct if doesn't call fsync or equivalent at the appropriate places. Please forgive me if I missed it, but does this code call fsync?

I'm trying to do the bootstrap like this:

• Startup a single server (id=1). There's only one server (i.e. itself) in the config.
• Startup another server (id=2).
• Send an add_server_request with LastLogIndex=0, LastLogTerm=0, EntriesLength=1, CommitIndex=0 and Term=0 to server 1 using a dedicated client with id=0.
• Then I found that the dest in the response message generated by server 1 was set as server 1 (i.e. itself) but not server 0 (the source of the request message).

Related code is here

I would like to point out that identifiers like “_CORNERSTONE_HXX_” and “_RAFT_SERVER_HXX_” do eventually not fit to the expected naming convention of the C++ language standard.
Would you like to adjust your selection for unique names?

We need to have pre-vote support for this library