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
Is your feature request related to a problem? Please describe.
Currently the octopoes workers rely on the katalogus to know which organizations are present in the install. This information can be sourced more locally since each organization also has a 'node' available in the XTDB server.
We should try to fetch such information locally, and possibly cached locally if we can to avoid unnecessary lookups.
Describe the solution you'd like
Maybe the XTDB multinode api can support a 'listnodes' endpoint, or maybe we can keep track of the organizations in the worker some other way (by observing create/delete orga requests somewhere)
Describe alternatives you've considered
None as of yet.
Additional context
Due to a katalogus url not being parsed / set correctly, we lost scan level propagation at some point. This was hard to debug because of the unexpected location of the data, and the seemingly unrelated katalogus errors. #2105
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
Currently the octopoes workers rely on the katalogus to know which organizations are present in the install. This information can be sourced more locally since each organization also has a 'node' available in the XTDB server.
We should try to fetch such information locally, and possibly cached locally if we can to avoid unnecessary lookups.
Describe the solution you'd like
Maybe the XTDB multinode api can support a 'listnodes' endpoint, or maybe we can keep track of the organizations in the worker some other way (by observing create/delete orga requests somewhere)
Describe alternatives you've considered
None as of yet.
Additional context
Due to a katalogus url not being parsed / set correctly, we lost scan level propagation at some point. This was hard to debug because of the unexpected location of the data, and the seemingly unrelated katalogus errors.
#2105
The text was updated successfully, but these errors were encountered: