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
Rarely, the streaming API server is also updated and requires a restart: systemctl restart mastodon-streaming
The streaming API server is updated very rarely, and in most releases, does not require a restart. Restarting the streaming API leads to an increased load on your server as disconnected clients attempt to reconnect or poll the REST API instead, so avoid it whenever you can.
Look at the Release Notes of the last couple of release lines...
Excluding backports to older versions, The following contain 'Restart all Mastodon processes'
4.0.2
4.0.0
3.5.3
3.5.2
3.5.1
3.5.0
Whilst, excluding backports, the following releases do not say to 'restart all mastodon processes'
4.0.1 does not, but it doesn't have any regular release notes covering the upgrade steps
Expected behaviour
The release notes should rarely say to update all processess
Actual behaviour
The release notes often say to update all processess
Detailed description
Are the release notes wrong in so often saying to restart 'all' mastodon processes, or should the docs be updated to reflect that restarting mastodon-streaming is perhaps more common than anticipated?
Specifications
Current live docs and release notes.
The text was updated successfully, but these errors were encountered:
Steps to reproduce the problem
Excluding backports to older versions, The following contain 'Restart all Mastodon processes'
Whilst, excluding backports, the following releases do not say to 'restart all mastodon processes'
Expected behaviour
The release notes should rarely say to update all processess
Actual behaviour
The release notes often say to update all processess
Detailed description
Are the release notes wrong in so often saying to restart 'all' mastodon processes, or should the docs be updated to reflect that restarting mastodon-streaming is perhaps more common than anticipated?
Specifications
Current live docs and release notes.
The text was updated successfully, but these errors were encountered: