luxolus
/
open-consul
2
0
Fork 0
Code Issues 1 Pull Requests Packages Releases Wiki Activity

website: FAQ for delta updates

This commit is contained in:
Armon Dadgar 2015-05-04 14:23:33 -07:00
parent 9d1abfd1cb
commit 1b121b703c
1 changed files with 12 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

12
website/source/docs/faq.html.markdown
View File

@ -73,3 +73,15 @@ To prevent an accumulation of dead nodes, Consul will automatically reap failed
nodes out of the catalog. This is currently done on a non-configurable interval
of 72 hours. Reaping is similar to leaving, causing all associated services to
be deregistered.
## Q: Does Consul support delta updates for watchers or blocking queries?
Consul does not currently support sending a delta or a change only response
to a watcher or a blocking query. The API simply allows for an edge-trigger
return with the full result. A client should keep the results of their last
read and compute the delta client side.
By design, Consul offloads this to clients instead of attempting to support
the delta calculation. This avoids expensive state maintenance on the servers
as well as race conditions between data updates and watch registrations.