Monitor reference table copy progress during master_add_node
Open
- Dominant language
- C
- Stars
- 12.8k
- Forks
- 794
- Avg merge
- 2d 14h
- Merged PRs (30d)
- 31
Description
When there are large reference tables, master_add_node can take a long time and it's a black box. We should have some way of monitoring its progress from the coordinator.
Contributor guide
Research direction
The only named entry point is master_add_node; trace how reference-table copies are initiated and what coordinator-visible state exists. Define the progress signal and its completion semantics before identifying the implementation and tests; the issue names no files or tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c, postgresql
- Domain
- databases, distributed-systems
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 15/100