edgent-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dale LaBossiere (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (EDGENT-192) event resiliency
Date Tue, 23 Aug 2016 19:20:20 GMT

    [ https://issues.apache.org/jira/browse/EDGENT-192?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15433423#comment-15433423
] 

Dale LaBossiere commented on EDGENT-192:
----------------------------------------

Response to above iot-java question:

@dlaboss The Watson iot-java library just picked up new Paho Java client 1.1 which provides
auto reconnect and offline publishing capabilities. I am thinking to add 2 new options "Auto-Reconnect"
and "Offline-Publishing." Note that this does not mean that the device can publish before
initial connect. The device must have successfully connected once.

> event resiliency
> ----------------
>
>                 Key: EDGENT-192
>                 URL: https://issues.apache.org/jira/browse/EDGENT-192
>             Project: Edgent
>          Issue Type: Improvement
>            Reporter: Jerome Chailloux
>
> Assuming that I have a Raspberry Pi that ingest data and doing some aggregate.
> I have to send information to Watson IoT.
> What if if I lost the network ?
> Could we have a mechanism that send data at all time and if network is not available
store all events in a file ?
> As soon as the network is available again play back the file and send new events.
> We have to be sure that all events are sent in the correct order from file to "real time".
> The computation engine (IBM Streams in this case) will then apply some policies to deal
with or not with out of order events for the real time computation but at least able to store
data received from sensors.
> Any idea about how to achieve this ?



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message