Open taliaga opened 7 years ago
Thanks for the feedback!
How Orion has been started? The output of the ps ax | grep contextBroker
in the system where Orion runs will show that information.
Right, I forgot that. See below...
$ ps ax | grep contextBroker
1 ? Ssl 0:00 /usr/bin/contextBroker -fg -multiservice -logLevel DEBUG -dbhost mongo
I launch it using docker with a compose looking like this:
version: '3'
services:
orion:
image: fiware/orion:1.7.0
ports:
- "1026:1026"
command: -logLevel DEBUG -dbhost mongo
depends_on:
- mongo
healthcheck:
test: ["CMD", "curl", "-f", "http://0.0.0.0:1026/version"]
interval: 1m
timeout: 10s
retries: 3
mongo:
image: mongo:3.2
ports:
- "27017:27017"
There's something else to comment that I've noticed for the first time now. It can happen that after some notifications coming without the metada, at some point notifications come with metadata again. So, it's not that the metadata is dropped to never come back. This makes the issue less critical than I originally thought. :)
In order to isolate the issue, could you try using -noCache
at ContextBroker startup and tell us if the problem happens or not in that case, please? Thanks!
Sorry for the silence. I've tested today a couple of times using that -noCache
flag and it seems to workaround the problem; i.e, I have not seen a dropped metadata so far :)
Thank for the feedback!
So it seems some kind of issue in the csubs cache refreshing logic. Need to be debugged and found, but I'm happy to see the problem has been narrowed quite a lot.
Hi guys,
I'm experiencing a strange behaviour in Orion notifications that is becoming a blocking issue for us.
Specifically, I've created a subscription to receive notifications with the dateCreated and dateModified metadata. It works fine for a couple of seconds, but after a handful of notifications (from 4 to 13) notifications drop the metadata (the modification time I need) and keep on coming only with the new values.
I haven't found the culprit yet, but I've realized that between the last complete notification and the first incomplete notification, Orion is doing something in the middle (looks like a sync with subscription object, but I can't tell for sure) as you can see below.
Orion version:
Orion debug output: Last complete notification (i.e, including the metadata):
Orion debug output: Suspicious Operation in-between
Orion debug output: First incomplete notification missing the metadata:
Output from the echo server receiving the notifications:
Subscription used
The subscription object looks fine with "metadata" throughout the experiment:
Any idea what could be going on? I'm happy to provide any further detail.