Data synchronization issue between Docker Swarm nodes
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 3.7k
- Forks
- 676
- Avg merge
- 4d 9h
- Merged PRs (30d)
- 6
Description
I have been trying to deploy services and stacks using Docker Swarm recently, but I encountered an issue with volume data synchronization. If multiple workers are running the service and stack, how can we ensure data synchronization between nodes? Is there a better way to achieve volume data synchronization between nodes using Docker Swarm, which can be solved through NFS or CFS on the internet but requires additional services and servers to support? This is more conducive to the development of Docker Swarm clusters.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue names no files, tests, or entry points. First clarify whether SwarmKit should provide built-in cross-node volume synchronization rather than external NFS or CFS; done would require an agreed design and acceptance criteria.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, go
- Domain
- distributed-systems, infrastructure
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100