Multiple orion with single mongodb instance fails to process subscriptions

asked 2018-10-18 11:53:50 +0100

Fiware user
1 ●2 ●2 ●2

I am trying to connect multiple orion instances to the same mongodb backend. While I am able to recieve context data from South bound iot devices into orion, only one among the orion instances is processing the onchange subscription request registered for onchange of context data of an entity attribute.

Is it a valid practice to have multiple orion instances connect to the same mongodb backend and if so, if 2 different orion instances recieve context attribute data of the same entity will it trigger pre-registered onchange subscription.

Do I need to configure something in orion or Mongo for this to work

I am using orion 0.23 and Mongo 3.4

answered 2018-10-26 12:17:08 +0100

ffacca
1 ●1 ●1 ●2

hi, can you better describe the scenario you are trying to achieve?

if what you are looking for is HA deployment (more replicas of the same orion service), then it should work easily. you find a guide here: https://github.com/telefonicaid/fiwar...

in the ha case, it is the expected behaviour that only one notification will be triggered, because once triggered the db is updated with such information.

if your purpose is to have different separate services (different data in the different orions) you need to be careful to configure different db for them.

edit flag offensive delete link

Comments

I have tried the following configuration. Multiple orion instances are active at the same time and the proxy dynamically distributes load among the orion instances. In such a deployment what I find - only one among the active orion instances is able to process onchange subscription for an entity

Fiware user ( 2018-10-30 05:50:58 +0100 )edit

add a comment

Multiple orion with single mongodb instance fails to process subscriptions

1 answer

Comments

Question Tools

Stats

Related questions