This week we are installing new version of communication protocol between our storage nodes. Although we do not expect any impact on the storage system in general and ready for any kind of troubles including the ability to perform hot restore of telematics data there are some updates in storage system behavior for flespi users. This is related to storage system replies performance and is interesting only for those who are using containers directly.
Currently up to a certain level our storage system provides asynchronous buffering of the uploaded data and thus responses for REST API calls for data upload are very fast as the receiver just put them into internal buffer.
Once we will finish actual update the database engine won't buffer uploaded data and will wait for uploaded data acknowledgment on at least 2 of 3 database mirrors. This is to ensure data durability, but at the same time this may delay storage containers REST API calls up to a few milliseconds, please be aware.
Once protocol is upgraded we will move to updated storage format for the mirrors and re-synchronize all the data we have. But this should not be visible to the external world at all (looking from flespi side) - we do it quite often with zero impact on our users.
Once we will move to the new data format we are one step closer to installation of flespi database system in second datacenter.