[Backlogmanager] [FIWARE-JIRA] (HELP-14259) [fiware-askbot] Strange Comet issues

[Veronika Vlnkova (JIRA)]

     [ https://jira.fiware.org/browse/HELP-14259?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Veronika Vlnkova resolved HELP-14259.
-------------------------------------
    Resolution: Done

> [fiware-askbot] Strange Comet issues
> ------------------------------------
>
>                 Key: HELP-14259
>                 URL: https://jira.fiware.org/browse/HELP-14259
>             Project: Help-Desk
>          Issue Type: Monitor
>            Reporter: Backlog Manager
>            Assignee: Joaquín Salvachúa 
>              Labels: fiware-orion, orion
>
> Created question in FIWARE Q/A platform on 09-06-2018 at 13:06
> {color: red}Please, ANSWER this question AT{color} https://ask.fiware.org/question/1002/strange-comet-issues/
> +Question:+
> Strange Comet issues
> +Description:+
> Dear Fiware,
> I am trying to connect STH Comet to Orion in order to aggregate some events.
> However I am having some errors:
> In order to reproduce this errors for you to analyze, I have created this small project that isolates Orion and STH Comet, and reproduces the error in the log messages: https://github.com/PedroD/comet_demo
> When you run it, you will find log messages.
> These log messages contain all commands that the coordinator app sends to Orion and STH Comet, so that you don't need to worry about the Kotlin project's source.
> In sum, the issues we are having are:
> 1) Comet is, for some reason, overflowing like this:
> sth_1          | time=2018-06-09T11:04:02.626Z | lvl=WARN | corr=n/a | trans=n/a | op=OPER_STH_DB_LOG | from=n/a | srv=n/a | subsrv=n/a | comp=STH | msg=The size in bytes of the namespace for storing the aggregated data ("sth_sensei_service" plus "sth_/sensei,/sensei,/sensei,/sensei,/sensei,/sensei,/sensei,/sensei,/sensei,/sensei_PersonDetection_PersonDetection.aggr", 138 bytes) is bigger than 120 bytes
> 2) Comet is for some reason, having issues persisting some data in mongo, despite that the coordinator only tries to register the entities once:
> sth_1          | time=2018-06-09T11:04:12.870Z | lvl=ERROR | corr=d78056a4-6bd4-11e8-97dd-0242ac120005 | trans=745ad73e-ebd0-49a4-b843-261981c8f9b2 | op=OPER_STH_POST | from=n/a | srv=sensei_service | subsrv=/sensei | comp=STH | msg=Error when getting the raw data collection for storing:MongoError: a collection 'sth_sensei_service.sth_/sensei_PersonDetection_PersonDetection' already exists
> 3) When asked for aggregations, using the url below, Comet returns empty values:
> URL: http://sth:8666/STH/v1/contextEntities/type/PersonDetection/id/PersonDetection/attributes/positionX?aggrMethod=sum&aggrPeriod=second&dateFrom=2016-02-01T00:00:00.000Z&dateTo=2019-01-01T23:59:59.999Z
> demo_1         | Requesting aggregation to Comet:
> demo_1         | {"contextResponses":[{"contextElement":{"attributes":[{"name":"positionX","values":[]}],"id":"PersonDetection","isPattern":false,"type":"PersonDetection"},"statusCode":{"code":"200","reasonPhrase":"OK"}}]}
> demo_1         |
> demo_1         |        Comet seems to be sending an empty "values" array. What is going on?
> demo_1         |
> What is going on? How can we solve these issues?
> Thanks!



--
This message was sent by Atlassian JIRA
(v6.4.1#64016)