* origin/engine-vs-velocystream: (91 commits)
removed useless include
removed JsonParser
removed JsonHelper
Fixed another failed nullptr handling in LogicalCollection cluster case.
Fixed undefined behaviour in rest error creation
Implemented updated of LogicalCollectionInfo. Right now this is only used in Cluster Mode
agency startup changed to bootstrapping
Mention howto control core files on linux.
shutdown fixed
Removed create / drop system collection from Cluster test. This is forbidden now
The logical colleciton now knows it's journalSize
Fixed a bug in collectionNameResolver. It now returns cid 0 for not found collections in cluster again.
pushing corrected unittest script and cluster startup scripts
adjusting startup scripts
missing source file added
we have a bootstrapping agency
votes are processed correctly again
Add module.context.createDocumentationRouter
Don't implicitely build the windows packages.
remove debug print
...
Conflicts:
arangod/Cluster/ClusterComm.cpp
arangod/GeneralServer/VppCommTask.h
arangod/RestHandler/RestBaseHandler.cpp
lib/Rest/VppRequest.h
This creates a fast path in performRequests for the case that only
one request is given. We use syncRequest instead of asyncRequest
to save a network roundtrip. Furthermore, all queues and locks
in ClusterComm are circumvented.
* origin/devel: (43 commits)
added dev button to graphs view [ci skip]
grunt build [ci skip]
Remove jshint
Mention updating license info
Prevent World War 3
Always use --global-style when installing npm deps
gv - editable & createable nodes, edges [ci skip]
Rebuild aardvark
Make sure Show Interface check asks for HTML
oops, @not supported here.
Fix phrase explaining when the collections are dropped alongside the graph definition.
fixed issue #1941
gv [ci skip]
added test for "fake" _key values
fixed issue #1942
In Farbe und in STEREREOOOUU!
grunt [ci skip]
gv [ci skip]
Fix documentation.
Fix fix.
...
asyncRequest has now two timeouts, one for the connection phase
leading to retries for failover situations, the other for the
completion of the whole operation.
I have added a thorough description of events to the comments
in ClusterComm.h. This should enable everybody to do proper
error handling when using ClusterComm::asyncRequest and
ClusterComm::syncRequest.