JSON Publish retry

What does the ODK Aggregate Z-ALPHA JSON publish do when the POST fails?
Does it retry? It would be great if it kept retrying for a set period of
time if the initial POST failed.

I have created a little node.js app to publish to Github. If using a Heroku
free dyno which goes into idle after 60 mins of inactivity then the initial
POST may fail because Heroku can take about 30 seconds to spin up a dyno
from idle.

Gregor

Gregor,

I don't remember if it retries, but I've filed it as a feature request
at https://code.google.com/p/opendatakit/issues/detail?id=967.

Yaw

··· -- Need ODK services? http://nafundi.com provides form design, server setup, professional support, and software development for ODK.

On Mon, Jan 27, 2014 at 9:30 AM, Gregor MacLennan gmaclennan@digital-democracy.org wrote:

What does the ODK Aggregate Z-ALPHA JSON publish do when the POST fails?
Does it retry? It would be great if it kept retrying for a set period of
time if the initial POST failed.

I have created a little node.js app to publish to Github. If using a Heroku
free dyno which goes into idle after 60 mins of inactivity then the initial
POST may fail because Heroku can take about 30 seconds to spin up a dyno
from idle.

https://github.com/digidem/odk-to-github/

Gregor

--
You received this message because you are subscribed to the Google Groups
"ODK Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to opendatakit-developers+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

All publishers retry on failure.

To control resource usage on AppEngine, when a failure occurs, the next
publishing attempt is delayed for 60 seconds. If that fails, then we
attempt to publish only every 7.5 minutes.

If there is no website activity (no submissions coming in and no page
views), we further slow our publishing to every 15 minutes.

The 7.5 minute back-off is intended to allow human intervention to correct
the published-to server's problems.

Mitch

··· On Tue, Jan 28, 2014 at 3:12 PM, Yaw Anokwa wrote:

Gregor,

I don't remember if it retries, but I've filed it as a feature request
at https://code.google.com/p/opendatakit/issues/detail?id=967.

Yaw

Need ODK services? http://nafundi.com provides form design, server
setup, professional support, and software development for ODK.

On Mon, Jan 27, 2014 at 9:30 AM, Gregor MacLennan gmaclennan@digital-democracy.org wrote:

What does the ODK Aggregate Z-ALPHA JSON publish do when the POST fails?
Does it retry? It would be great if it kept retrying for a set period of
time if the initial POST failed.

I have created a little node.js app to publish to Github. If using a
Heroku
free dyno which goes into idle after 60 mins of inactivity then the
initial
POST may fail because Heroku can take about 30 seconds to spin up a dyno
from idle.

https://github.com/digidem/odk-to-github/

Gregor

--
You received this message because you are subscribed to the Google Groups
"ODK Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to opendatakit-developers+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

--
You received this message because you are subscribed to the Google Groups
"ODK Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to opendatakit-developers+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

--
Mitch Sundt
Software Engineer
University of Washington
mitchellsundt@gmail.com

I should add -- because of the nature of web service interactions, this
retry behavior can cause duplicate records to be inserted into the
published-to server.

The end-user (or recipient server) is responsible for detecting and
filtering out those duplicates.

··· On Wed, Jan 29, 2014 at 10:09 AM, Mitch Sundt wrote:

All publishers retry on failure.

To control resource usage on AppEngine, when a failure occurs, the next
publishing attempt is delayed for 60 seconds. If that fails, then we
attempt to publish only every 7.5 minutes.

If there is no website activity (no submissions coming in and no page
views), we further slow our publishing to every 15 minutes.

The 7.5 minute back-off is intended to allow human intervention to correct
the published-to server's problems.

Mitch

On Tue, Jan 28, 2014 at 3:12 PM, Yaw Anokwa yanokwa@nafundi.com wrote:

Gregor,

I don't remember if it retries, but I've filed it as a feature request
at https://code.google.com/p/opendatakit/issues/detail?id=967.

Yaw

Need ODK services? http://nafundi.com provides form design, server
setup, professional support, and software development for ODK.

On Mon, Jan 27, 2014 at 9:30 AM, Gregor MacLennan gmaclennan@digital-democracy.org wrote:

What does the ODK Aggregate Z-ALPHA JSON publish do when the POST fails?
Does it retry? It would be great if it kept retrying for a set period of
time if the initial POST failed.

I have created a little node.js app to publish to Github. If using a
Heroku
free dyno which goes into idle after 60 mins of inactivity then the
initial
POST may fail because Heroku can take about 30 seconds to spin up a dyno
from idle.

https://github.com/digidem/odk-to-github/

Gregor

--
You received this message because you are subscribed to the Google
Groups
"ODK Developers" group.
To unsubscribe from this group and stop receiving emails from it, send
an
email to opendatakit-developers+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

--
You received this message because you are subscribed to the Google Groups
"ODK Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to opendatakit-developers+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

--
Mitch Sundt
Software Engineer
University of Washington
mitchellsundt@gmail.com

--
Mitch Sundt
Software Engineer
University of Washington
mitchellsundt@gmail.com