-
Bug
-
Resolution: Done
-
Medium
-
Casablanca Release
As a follow up from: https://jira.onap.org/browse/LOG-793
I am (internal lab) able to see that we can send a orchestration complete even to DR which is then consumed by message router. The next step is for the Context Aggregator to consume this event and reach out to the various context builders. However this is not happening at the aggregator level.
When posting to DR:
2018-11-01T17:56:08.518Z||pool-2-thread-1|DataRouter||com.att.nsa.mr.client.impl.MRSimplerBatchPublisher||INFO|sending 1 msgs to http://message-router.onap:3904/events/POA-AUDIT-INIT?partitionKey=0. Oldest: 298 ms
2018-11-01T17:56:08.528Z||pool-2-thread-1|DataRouter||com.att.nsa.mr.client.impl.MRSimplerBatchPublisher||INFO|MR reply ok (10 ms):{"serverTimeMs":0,"count":1,"status":200}
Need to investigate why the CtxAggregator is not consuming the INIT event(s)
Workaround
Simply restarting the Context Aggregator after the DMaaP POA-AUDIT-INIT topic has been created should allow the component to begin reading from the queue.
(To create the POA-AUDIT-INIT topic when one does not yet exist, you may simply send in an initial sacrificial audit request.)
- is cloned by
-
LOG-824 POMBA: ContextAggregator is not picking up posted events
- Closed
- relates to
-
LOG-659 Initial POMBA messages for topics may be dropped if topic does not exist already
- Closed
-
LOG-845 POMBA pomba-contextaggregator pod failing init during deploy since 6 Nov 2018 1500 UTC
- Closed
-
LOG-793 POMBA Data Router doesnt accept audit requests
- Closed
-
LOG-795 POMBA/ND: Service Decomposition's AAI config points to 127.0.0.1
- Closed