Uploaded image for project: 'Help-Desk'
  1. Help-Desk
  2. HELP-14847

[fiware-askbot] Can multiple fiware orion work with same mongodb backend?

    Details

      Description

      Created question in FIWARE Q/A platform on 20-10-2018 at 04:10
      Please, ANSWER this question AT https://ask.fiware.org/question/1040/can-multiple-fiware-orion-work-with-same-mongodb-backend/

      Question:
      Can multiple fiware orion work with same mongodb backend?

      Description:
      I have tried connecting multiple orion instances from different machines to the same mongodb backend.
      The issue I have observed is that only one among the orion instances is able to process onchange subscription registered against attribute of an entity.

      My question is - is it a valid practice of having multiple active instances of orion independantly handling incoming requests connected to the same mongodb backend. Does such a deployment configuration work in the same manner, in comparision to single instance of orion connected to mongodb backend.

      I have tried this with orion version 0.23 and mongodb version 3.4

        Activity

        fla Fernando Lopez made changes -
        Fix Version/s 2021 [ 12600 ]
        fla Fernando Lopez made changes -
        HD-Enabler Orion [ 10875 ]
        Description
        Created question in FIWARE Q/A platform on 20-10-2018 at 04:10
        {color: red}Please, ANSWER this question AT{color} https://ask.fiware.org/question/1040/can-multiple-fiware-orion-work-with-same-mongodb-backend/


        +Question:+
        Can multiple fiware orion work with same mongodb backend?

        +Description:+
        I have tried connecting multiple orion instances from different machines to the same mongodb backend.
        The issue I have observed is that only one among the orion instances is able to process onchange subscription registered against attribute of an entity.

        My question is - is it a valid practice of having multiple active instances of orion independantly handling incoming requests connected to the same mongodb backend. Does such a deployment configuration work in the same manner, in comparision to single instance of orion connected to mongodb backend.

        I have tried this with orion version 0.23 and mongodb version 3.4
        Created question in FIWARE Q/A platform on 20-10-2018 at 04:10
        {color: red}Please, ANSWER this question AT{color} https://ask.fiware.org/question/1040/can-multiple-fiware-orion-work-with-same-mongodb-backend/


        +Question:+
        Can multiple fiware orion work with same mongodb backend?

        +Description:+
        I have tried connecting multiple orion instances from different machines to the same mongodb backend.
        The issue I have observed is that only one among the orion instances is able to process onchange subscription registered against attribute of an entity.

        My question is - is it a valid practice of having multiple active instances of orion independantly handling incoming requests connected to the same mongodb backend. Does such a deployment configuration work in the same manner, in comparision to single instance of orion connected to mongodb backend.

        I have tried this with orion version 0.23 and mongodb version 3.4
        jmcantera Jose Manuel Cantera made changes -
        Resolution Done [ 10000 ]
        Status Answered [ 10104 ] Closed [ 6 ]
        backlogmanager Backlog Manager made changes -
        Status In Progress [ 3 ] Answered [ 10104 ]
        backlogmanager Backlog Manager made changes -
        Status Open [ 1 ] In Progress [ 3 ]
        veronika Veronika Vlnkova made changes -
        Field Original Value New Value
        Assignee Jose Manuel Cantera [ jmcantera ]
        backlogmanager Backlog Manager created issue -

          People

          • Assignee:
            jmcantera Jose Manuel Cantera
            Reporter:
            backlogmanager Backlog Manager
          • Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved: