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

FIWARE.Question.Tech.Data.BigData-Analysis.Fiware: Data loss prevention

    Details

      Description

      Created question in FIWARE Q/A platform on 17-02-2016 at 09:02
      Please, ANSWER this question AT http://stackoverflow.com/questions/35451531/fiware-data-loss-prevention

      Question:
      Fiware: Data loss prevention

      Description:
      I’m working with the 0.27.0 version of context broker. I'm using the Cygnus generic enabler and I have established a MQTT agent that connects external devices to the context broker.

      My major concern right now is how to prevent from data loss. I established the context broker and the Cygnus mongodb databases as replica sets, but that won't ensure that all data will be persisted into the databases. I have seen that Cygnus uses Apache flume. Looking at its configuration, the re-injection retries can be configured:

      1. Number of channel re-injection retries before a Flume event is definitely discarded (-1 means infinite retries)
        cygnusagent.sources.http-source.handler.events_ttl = -1

      ¿It is a good idea to establish the retries value to -1? I have read about events re-injected in the channel forever.
      ¿What can be done to ensure that all the data will be persisted?
      ¿Is there any functionality into fiware ecosystem oriented to that purpose?

        Activity

        Hide
        backlogmanager Backlog Manager added a comment -

        2016-02-17 12:05|CREATED monitor | # answers= 0, accepted answer= False

        Show
        backlogmanager Backlog Manager added a comment - 2016-02-17 12:05|CREATED monitor | # answers= 0, accepted answer= False
        Hide
        backlogmanager Backlog Manager added a comment -

        2016-02-19 15:05|UPDATED status: transition Answer| # answers= 1, accepted answer= False

        Show
        backlogmanager Backlog Manager added a comment - 2016-02-19 15:05|UPDATED status: transition Answer| # answers= 1, accepted answer= False
        Hide
        backlogmanager Backlog Manager added a comment -

        2016-02-19 18:05|UPDATED status: transition Answered| # answers= 1, accepted answer= False

        Show
        backlogmanager Backlog Manager added a comment - 2016-02-19 18:05|UPDATED status: transition Answered| # answers= 1, accepted answer= False
        Hide
        backlogmanager Backlog Manager added a comment -

        2016-02-21 15:05|UPDATED status: transition Finish| # answers= 1, accepted answer= False

        Show
        backlogmanager Backlog Manager added a comment - 2016-02-21 15:05|UPDATED status: transition Finish| # answers= 1, accepted answer= False

          People

          • Assignee:
            frb Francisco Romero
            Reporter:
            backlogmanager Backlog Manager
          • Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved: