Skip to content

Replace gen_leader with locks_leader for gproc_dist - #207

Open
uwiger wants to merge 5 commits into
masterfrom
uw-new-locks_leader
Open

Replace gen_leader with locks_leader for gproc_dist#207
uwiger wants to merge 5 commits into
masterfrom
uw-new-locks_leader

Conversation

@uwiger

@uwiger uwiger commented Jul 30, 2026

Copy link
Copy Markdown
Owner

Port distributed registry to locks_leader: optional locks application,
conditional gproc_dist start when locks_server is present, and optional
peer connect via {gproc, gproc_dist} node list.

Testing: Common Test gproc_dist_SUITE with peer nodes and per-node
disk logs; eunit keeps local coverage (dist eunit generator removed).
Drop rebar.config.script that previously gated gen_leader.

uwiger added 5 commits July 30, 2026 13:04
Port distributed registry to locks_leader: optional locks application,
conditional gproc_dist start when locks_server is present, and optional
peer connect via {gproc, gproc_dist} node list.

Testing: Common Test gproc_dist_SUITE with peer nodes and per-node
disk logs; eunit keeps local coverage (dist eunit generator removed).
Drop rebar.config.script that previously gated gen_leader.
Stop ignoring rebar.lock so CI and clones pin locks (and plain_fsm)
to the same refs as development.
wait_gproc_leader now probes with a long-lived process until a global
name is visible on every node (leader agreement alone is not enough;
broadcast only reaches synced followers). Increase lookup retries for
CI load. Upload _build/test/logs as an artifact when make fails.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant