preventCompose not changing
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 6.5k
- Forks
- 456
- Avg merge
- 1d 5h
- Merged PRs (30d)
- 5
Description
Hi,
I'm currently using shareDB for real-time editor websites.
I scaled up my server using pm2.
Since there are multiple processes, the shareDB is not sharing some of the properties.
I'm also using database adapter sharedb-mongo.
Even if I could fetch the doc object when there is an update from another process, it seems like when one process changes the preventCompose property to serialize ops, another process does not detect the change.
Is there a way to fix this? Any suggestion for this issue?
Thank you.
Contributor guide
No contributing guide indexed for this repository
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
No files or tests are named. Start by tracing how preventCompose changes are handled across ShareDB processes and how the sharedb-mongo adapter propagates updates between pm2 workers. Done means a change in one process is detected by the others and prevents composition consistently.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, mongodb
- Domain
- backend, databases, distributed-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100