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
{{ message }}
Repository navigation
Admin UIs metadata never recovers when missing a new knowledge base #899
The MetadataKB queries all metadata of all KBs in the network once after startup and after that relies on notifications of new/changed/removed KBs to update its metadata store. Whenever one of these notifications is missed (which can easily happen, especially in distributed setup), the metadata store will never automatically recover. Currently, the AdminUI provides the /reload REST operation that allows manual triggering of the initial metadata query to remedy such errors, but we want its method to be more robust by not only quering for metadata once at startup, but also at regular (configurable) intervals. If we combine this with the notification based updates, we get the advantages of both methods:
automatically recover from missed notifications due to regular querying of metdata
direct respnoses to changes in the network based on notifications received from other KBs
Activity