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

FIWARE.Request.Lab.Re: Help Multiple Orion Instances on FiLab.

    Details

    • Type: extRequest
    • Status: Closed
    • Priority: Major
    • Resolution: Done
    • Fix Version/s: Sprint 4.1.3
    • Component/s: FIWARE-LAB-HELP
    • Labels:
      None

      Description

      Hi Gioacchino,

      yes, you can have two instances of the orion context broker running in the same machine.
      You need to be a little careful on how you start them though, e.g. they cannot both listen to the same port, obviously.
      The listen port is chosen using the '-port' option.

      The first instance of orion you can start without any options, just using the default values.
      The second instance however, must be told to use different ports, paths etc, in order not to use the same stuff as the first instance.

      You will want separate log files for the instances, this is fixed using the -logDir option
      (just give one of them a directory != the default directory, which is '/tmp').

      The file where the Process IDentifier is stored should also be changed for the second instance of orion. Option: -pidpath <path to pidfile>.
      You probaly don't want the second instance attacking the same database as the first one: option: -db <name of database>.

      So, an example on successfully running two brokers in the same machine:

      $ contextBroker
      $ contextBroker -db secondBroker -pidpath /tmp/secondBroker.pid -logDir /tmp/secondBroker -port 1099

      [ The directory '/tmp/secondBroker' must exist and be writable ]
      [ The mongo database named 'secondBroker' is created automatically ]

      Good luck,

      /KZ

      ________________________________

      Este mensaje y sus adjuntos se dirigen exclusivamente a su destinatario, puede contener información privilegiada o confidencial y es para uso exclusivo de la persona o entidad de destino. Si no es usted. el destinatario indicado, queda notificado de que la lectura, utilización, divulgación y/o copia sin autorización puede estar prohibida en virtud de la legislación vigente. Si ha recibido este mensaje por error, le rogamos que nos lo comunique inmediatamente por esta misma vía y proceda a su destrucción.

      The information contained in this transmission is privileged and confidential information intended only for the use of the individual or entity named above. If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this transmission in error, do not read it. Please immediately reply to the sender that you have received this communication in error and then delete it.

      Esta mensagem e seus anexos se dirigem exclusivamente ao seu destinatário, pode conter informação privilegiada ou confidencial e é para uso exclusivo da pessoa ou entidade de destino. Se não é vossa senhoria o destinatário indicado, fica notificado de que a leitura, utilização, divulgação e/ou cópia sem autorização pode estar proibida em virtude da legislação vigente. Se recebeu esta mensagem por erro, rogamos-lhe que nos o comunique imediatamente por esta mesma via e proceda a sua destruição
      _______________________________________________
      Fiware-lab-help mailing list
      Fiware-lab-help@lists.fi-ware.org
      https://lists.fi-ware.org/listinfo/fiware-lab-help

      [Created via e-mail received from: Ken Zangelin <kengunnar.zangelin@telefonica.com>]

        Activity

        Hide
        danieles Daniele Santoro added a comment -

        duplicate: 1540

        Show
        danieles Daniele Santoro added a comment - duplicate: 1540

          People

          • Assignee:
            danieles Daniele Santoro
            Reporter:
            fw.ext.user FW External User
          • Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved: