It takes unnecessarily long to restart the portal API and subsequently let all the other components restart correctly. This is due to the following issues:
After the portal API has restarted, it usually has a differing configuration has (due to the changed configuration)
Calls to the portal API are then rejected by default due to the wrong config hash
This does not have to be like that - the portal API can accept calls with the old config hash for a certain period of time (e.g. one minute or similar), making sure that the components can reload as quick as possible.
It takes unnecessarily long to restart the portal API and subsequently let all the other components restart correctly. This is due to the following issues:
This does not have to be like that - the portal API can accept calls with the old config hash for a certain period of time (e.g. one minute or similar), making sure that the components can reload as quick as possible.