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
Currently we fetch information about the partition-host mapping once during the initialisation of the PartitionRouter. Should the mapping change, for example because of the addition of another replica, some cache-misses will occur as there is no update-mechanism. Thus, it is advisable to introduce such a mechanism, i.e. the possibility to update the mapping dynamically.
A possible approach:
If there is a host-miss, the request is forwarded to the correct replica without any error,
In addition, a prompt to update the cache is written into a header,
The gateway uses this info to forward it to the router which reinits (updates) the mapping.
The text was updated successfully, but these errors were encountered:
Currently we fetch information about the partition-host mapping once during the initialisation of the PartitionRouter. Should the mapping change, for example because of the addition of another replica, some cache-misses will occur as there is no update-mechanism. Thus, it is advisable to introduce such a mechanism, i.e. the possibility to update the mapping dynamically.
A possible approach:
The text was updated successfully, but these errors were encountered: