Fixed error when uploading CBA when Hazelcast cluster is not initialized 52/120952/2 1.1.4
authorJulien Fontaine <julien.fontaine@bell.ca>
Wed, 20 Jan 2021 23:28:49 +0000 (18:28 -0500)
committerJulien Fontaine <julien.fontaine@bell.ca>
Wed, 28 Apr 2021 22:07:59 +0000 (18:07 -0400)
commit084009b62202c25ee9a3020a9943ef335b898df3
tree78635757a986490f89df04788a73dfe1252ae219
parent83edeed4748644314453654aa853ad5674fc899e
Fixed error when uploading CBA when Hazelcast cluster is not initialized

Hazelcast is used to enable CDS pods to notify the rest of the CDS cluster when a CBA got updated locally so they clean their compile cache (if they have an entry for that CBA). Though, the code doesn't make sure that hazelcast cluster is fully initialized before trying to notify using a hazelcast topic.
Fixed that error by making sure that the cluster is fully initialized before pushing notification to hazelcast topic.

Issue-ID: CCSDK-3277
Change-Id: I44211c63c5a991269005bcc238f18b19979cb718
Signed-off-by: Julien Fontaine <julien.fontaine@bell.ca>
ms/blueprintsprocessor/modules/commons/db-lib/src/main/kotlin/org/onap/ccsdk/cds/blueprintsprocessor/db/primary/service/BlueprintProcessorCatalogServiceImpl.kt