[Backlogmanager] [FIWARE-JIRA] (HELP-8857) [fiware-stackoverflow] Fiware: Data loss prevention

[José Ignacio Carretero Guarde (JIRA)]

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

José Ignacio Carretero Guarde resolved HELP-8857.
-------------------------------------------------
    Resolution: Done

> [fiware-stackoverflow] Fiware: Data loss prevention
> ---------------------------------------------------
>
>                 Key: HELP-8857
>                 URL: https://jira.fiware.org/browse/HELP-8857
>             Project: Help-Desk
>          Issue Type: Monitor
>          Components: FIWARE-TECH-HELP
>            Reporter: Backlog Manager
>            Assignee: Francisco Romero
>              Labels: fiware, fiware-cygnus, fiware-orion
>
> Created question in FIWARE Q/A platform on 17-02-2016 at 09:02
> {color: red}Please, ANSWER this question AT{color} https://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: 
> # 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?



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