Conversation
|
|
||
| ## Running Postgres | ||
|
|
||
| We will use Docker Compose to run Redis |
There was a problem hiding this comment.
| We will use Docker Compose to run Redis | |
| We will use Docker Compose to run Postgres |
shaspitz
left a comment
shaspitz
left a comment
There was a problem hiding this comment.
Looks solid, will have to take a deeper look when I have more time. To avoid confusion imo we should replace instances of singlenode with singleleader, since this setup isn't just for a single node anymore, and it's enabling single leader replication
| ### Run the Single Node Application | ||
| **Leader Node:** | ||
|
|
||
| - `SNODE_PRIORITY_FEE_RECIPIENT` |
There was a problem hiding this comment.
Might be more clear to prefix these with LEADER instead of SNODE to match the member node env vars
| @@ -0,0 +1,617 @@ | |||
| package membernode | |||
There was a problem hiding this comment.
The new directory name here could be a bit semantically confusing. This file should probably be in the same directory as the leader's code
|
Also is there a reason we implemented our own solution here instead of using https://www.postgresql.org/docs/current/runtime-config-replication.html#RUNTIME-CONFIG-REPLICATION |
Here it's a bit different mechanism, member nodes don't have their own postgres instances, they are applying payloads to their geth instances |
4 participants
Describe your changes
Added member nodes for single node consensus. Leader node is saving payloads to the postgres db, and member nodes are polling payload through api from the leader node.
Checklist before requesting a review