You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Because of some unfortunate dependency chain a new Server will not run if one server is down. This can be avoided though.
The reason for this following:
The room ensurer is supposed to join the broadcast rooms from the first server in the list
It will also connect to all servers to ensure rooms. If one server is down the room ensurer will fail and not join the rooms
Neither PFS, MS nor Matrix will function without the fetched broadcast rooms
This can be easily avoided if we loosen the policy if a server is not available.
Suggestion
Since the room ensurer always ensures the roomwith the first server in the list, it is only necessary to connect to that server. The room ensurer can still ensure the rooms from the others but will not break if the server is not available. If the first server is offline it could use the second to ensure rooms, and so on.
The text was updated successfully, but these errors were encountered:
I looked again into this issue and found the following improvements (regardless any improvement which comes with #180)
do not break if server cannot connect to a server which is down
add admin power levels for new servers
remove admin power levels for removed servers This is not possible. Same power levels cannot change each other
try to join broadcast rooms beginning at the first server in the list, if down then second, and so on...
RE crashes at first run due to setting power levels
The question comes up, do we need to ensure broadcast rooms of other servers than the first reachable one? If I recall correctly it only gives a warning and since we only ensure with the first server we do not act other than printing the warning.
Description
Because of some unfortunate dependency chain a new Server will not run if one server is down. This can be avoided though.
The reason for this following:
This can be easily avoided if we loosen the policy if a server is not available.
Suggestion
Since the room ensurer always ensures the roomwith the first server in the list, it is only necessary to connect to that server. The room ensurer can still ensure the rooms from the others but will not break if the server is not available. If the first server is offline it could use the second to ensure rooms, and so on.
The text was updated successfully, but these errors were encountered: