* fix some deadlocks found by evil lock manager (tm)
* fix duplicate lock
* fix indentation
* ensure proper lock dependencies
* fix lock acquisition
* removed useless comment
* do not lock twice
* create either a V8 transaction context or a standalone transaction context, depending on if we are called from within V8 or not
* AQL micro optimizations
* use explicit constructor
* only use V8DealerFeature's ConditionLocker for acquiring a free V8 context
entering and exiting the selected context is then done later on without having to hold the ConditionLocker
* remove some recursive locks
* Disable custom deadlock detection when Thread Sanitizer is enabled
* Changing ifdef's
* grr
* broke gcc
* Using atomic for ApplicationServer::_server
* fix premature unlock
* add some asserts
* honor collection locking in cluster
* yet one more lock fix
* removed assertion
* some more bugfixes
* Fixing assert
(cherry picked from commit 1155df173bfb67303077fbe04ee8d909517bfd21)
* Switching from ttl to supervision based failover mechanism
* Allowing canceling of ongoing actions
* refactored asyncjobmanager
* refactoring some code
* adding read-only flag
* catching some exceptions to reduce log pollution, removing unnecessary code, removing tests for _changeMode
* fixing "createsANewDatabaseWithAnInvalidUser"
* auth = off does not longer make everyone superuser
* Fixing cluster_sync and maybe resilience
* we must now ignore that datafiles are not sealed
this is because an unsealed datafile may have been produced by
renaming multiple journals to datafiles at server start
* acquire collection count after we have acquired the lock
* count the null byte as well
* fix count value acquisition
* send query fragments to the correct servers, even after failover or when a follower drops
the problem with using the previous shard-based approach is that responsibilities for shards may change at runtime
however, an AQL query must send all requests for the query to the initially used servers.
if there is a failover while the query is executing, we must still send all following requests to the same servers, and not the newly responsible servers
otherwise we potentially would try to get data from a query from server B while the query was only
instanciated on server A.
* Testing hash for documents
* fixing logspam error
* added base support for kHash in the edge index
* Current version of hash enabled edge index
* removed rocksdb key type byte, dynamic prefixes for hash-index
* Fixing issues with key classes
* Fixing merge conflict
* Fixing version with semi-working hash index
* fixing various issues
* Fixing hanger in EdgeIndexIterator nextExta, when _cache is disabled. Reenable cache
* Fixing geo index bounds, and fillIndexes error handling
* Adding back failure point
* Fixing RocksDBKey::vertexId
* Added version check on startup
* Fixing version check
* added one more check
* properly detect column families at startup
* Adding additional sanity checking
* Adding missing column family
* some fixes
* Turned off geoindex sync
* fixed error
* added asserts (untested)
* Adding more asserts
Jan
Simon Grätzer
jsteemann
Jan Christoph Uhde
Dan Larkin