-
-
Notifications
You must be signed in to change notification settings - Fork 2.1k
Conversation
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.
other than comment LGTM
docs/workers.rst
Outdated
|
||
``synapse.app.federation_reader`` | ||
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ | ||
handles receiving federation traffic (including public_rooms API). In |
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.
not all traffic though
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.
#NotAllEndpoints
The above endpoints should all be routed to the synchrotron worker by the | ||
reverse-proxy configuration. | ||
|
||
It is possible to run multiple instances of the synchrotron to scale |
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.
for clarity, the other workers should indicate that they cannot be load balanced. Probably just a paragraph above the workers saying "All workers cannot be load balanced unless otherwise stated".
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 don't actually think that's true: I think that most of them can be load-balanced, though the greatest gains are to be found via the synchrotrons. I've identified the ones that definitely can't be load-balanced in 879adee.
docs/workers.rst
Outdated
the ``worker_main_http_uri`` setting in the frontend_proxy worker configuration | ||
file. For example:: | ||
|
||
worker_main_http_uri: http://127.0.0.1:8080 |
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.
:8008
instead?
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.
ours is on :8080. but fair enough, I guess :8008 is more common.
I'll merge this in a bit if nobody spots any more problems |
879adee
to
a0c6688
Compare
Fixes #2554