New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Remove clustering from streaming API #23518
Conversation
This pull request has merge conflicts that must be resolved before it can be merged. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm in favour of this code change, if you want, I could continue this? (e.g., removing the throng dependency, adding nginx/systemd configuration to show how to "cluster" at nginx level, etc)
const startWorker = async (workerId) => { | ||
log.warn(`Starting worker ${workerId}`); | ||
|
||
const startWorker = async () => { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
const startWorker = async () => { | |
const startServer = async () => { |
master: startMaster, | ||
}); | ||
}); | ||
startWorker(); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
startWorker(); | |
startServer(); |
These two changes get rid of the verbage of workers
from this code.
@Gargron I'm currently looking into how this code could be improved further, and I'm suspecting that the current redis setup for pub/sub is inefficient (that is, the topic model doesn't actually fit with how streaming is working in the wild in production environments) |
No description provided.