* Really enforce the hidden option --server.maximal-threads if given.
* Switch off --log.force-direct in scripts/startStandAloneAgency.sh
* Lower the timeout for sending AppendEntriesRPC to 150s.
* Erase _earliestPackage when becoming a leader.
* Challenge leadership in agent main loop.
* Use steady_clock for _earliestPackage.
* Change _lastAcked and _leaderSince to steady_clock as well.
* time difference calculations based on old readSystemClock to steadyClockToDouble
* All system_clock transitioned to steady_clock in Agent. Remaining system_clock are user input / output or timestamps
* Inception system_clock to steady_clock
Store parameters of startLocalCluster.sh
This should help you to bring the cluster up again when you
continue to work after some time without investigating the
port numbers.
Restore parameters if no arguments are given
* Cleanup after each testrun
- add a success testsuite next to the fail testsuite
- create temporary directories in the fail & success testsuites
- add a function to cleanup the last unshifted directory
- don't say we're crashed when exiting with the help message
* Specify temp path for SUT so its files will be removed after cleanup.
- cleanup
- don't use getTempFile(), it will create another subdirectory that we don't clean up afterwards...
* Fix temp path usage
- creating a 'bundles' directory wherein we would keep our temporary bundle files would collide if we'd clean it up.
- create 'bundles-tmpxxxx' instead so its individual to us and we can remove it when done without problems.
* properly create & pass in a temporary directory - as we now require this.
* Remove intermediate directory recursive - for some unknown reason there may be temp files created.
* we need to unify tempfilenames here too.
* use individual suite names
* use the standart performTests to run the backup tests - so we have the proper directory and server handling from the infrastructure.
* fix temporary directory handling in the recovery tests.
* script to build debugging debian packages
* Improve test shutdown
- handle a set of options globally per testsuite, so they don't need to clone them inside.
- properly cleanup the slave instance of the replication tests after each run.
- The per testsuite options vector will fix the behaviour that after one failed testsuite
all other suites won't be cleaned up anymore.
* don't call the overal cleanup if anything failed.
* fix cleaning up of directories.
* cleanup, fix directory creation / deletion / dummy creation.
* cleanup, fix directory creation / deletion / dummy creation.
* fix tempdir handling for the recovery tests
* Count as checksum
* Make readLockId optional as well so upgrades are possible
* fix option name in startup script
* fix some replication issues with RocksDB engine
* do not rely on non-existing feature "AQL"
using such feature makes the server throw two exceptions (which will be caught) on startup, but its silly for debugging
* use condition variable for signalling shutdown
* do not hard-code the log levels for recovery tests
this has taken so many developers so much of their time that it is about time to fix it
* ensure the 'unittests' script properly finds 'arangosh' and the build directory
* fix traverse and modify
* fix filter deletion in geo index optimization rule
* update test definitions
* fix second traverse function
* use port ranges when starting cluster
* reduce memory consumption of cluster test
Now we execute 6 instead of 12 test concurrently.
* Add testcase to demonstrate #2499
- In subqueries inserts get pushed to the DB-Servers
- these create documents documents on each DB-Server that don't respect the shard-key
- subsequent deletes will fail to detect the shard correctly and will also fail.
* fix for #2499
* Migrate documentation build process to pure bash.
- the old makefile contained multiple shell snippets which were hard to maintain
- Convert it from Makefile to pure bash build.sh
- Fix error reporting in companion python scripts
- adjust README_maintainers.md to the new script
- provide wrapper GNUMakefile for automatic jobs for compatibility
- use the new shellscript inside the docker wrapper
- use the systems available processors inside the docker container if we build arangod
- strive to build enterprise binaries, since some examples require it.
* fix wrapper makefile
* add warmup documentation - #188
* warn when relinking build directory
* add warmup documentation - #188
* warn when relinking build directory
* Renamed warmup to loadIndexesInMemory which is a better name for the current implementation of this feature.
* Adapted WebUI to state 'load indexes in memory' instead of 'warmup'
* Added loadIndexesInMemory documentation.
* Renamed loadIndexesInMemory => loadIndexesIntoMemory