tree 98ce9e9d8dc3c2320e2563d0e5f3a7536050a582
parent 537ed491d44f72f1045467587f30601cf9e6a5f3
author Justin Berstler <bjustin@us.ibm.com> 1498506471 -0400
committer Carlos Santana <csantana23@gmail.com> 1498506471 -0400

automatically monitor and restore the health of the DB changes feed (#186)

* Monitor the DB changes feed by generating canary documents

Periodically add non-trigger (AKA "canary") documents into the DB. The changes feed loop checks for these canaries to verify that the changes feed is still working. If the time between canaries exceeds the limit, the changes feed is automatically restarted.

* return the trigger UUID from the feed action

* add test to ensure a new trigger can be created

* Update to latest cloudant client

It may contain a fix for the disappearing changes feed

* add comment explaining the for-loop break