-
Story
-
Resolution: Won't Do
-
Lowest
-
None
-
None
Currently the AAI-Resources defaults to only using real-time connections to the database, but the AAI-Traversal defaults to using cached connections instead.
There are pitfalls associated with cached connections because it takes several seconds to see updated AAI-Resources data in the cache of AAI-Traversal.
These pitfalls are avoided when forcing the use of real-time connections in AAI-Traversal, e.g. by adding the "Real-Time:true" header to the REST API call.
However, the JanusGraph implementation treats cached connections and real-time connections as two separate connection pools, so AAI-Resources data seen from a real-time connection might not be observable from a cached connection even though the two calls are done one immediately after the other.
Suggestion is to deprecate/remove the cached mode connections so that only real-time connections are used by default.
- relates to
-
MULTICLOUD-602 Error when registering a cloud after deleting it
- Closed