is allowed to be executed on server by sending via HTTP to the API endpoint
/_admin/execute with an authenticated user account.
The default value is false, which disables the execution of user-defined
code. This is also the recommended setting for production. In test environments,
it may be convenient to turn the option on in order to send arbitrary setup
or teardown commands for execution on the server.
Note that this value configures the maximum number of V8 contexts that can be
used in parallel. Upon server start only as many V8 contexts will be created as
are configured in option
available V8 contexts may float at runtime between
the server’s garbage collector thread will automatically delete them.
Specifies the minimum number of V8 contexts that will be present at any time
the server is running. The actual number of V8 contexts will never drop below this
value, but it may go up as high as specified via the option
When there are unused V8 contexts that linger around and the number of V8 contexts
is greater than
thread will automatically delete them.
Specifies the maximum number of invocations after which a used V8 context is
disposed. The default value of
meaning that the maximum number of invocations per context is unlimited.
Specifies the time duration (in seconds) after which time a V8 context is disposed
automatically after its creation. If the time is elapsed, the context will be disposed.
The default value for
are set, then the context will be destroyed when either of the specified threshold
values is reached.
Garbage collection frequency (time-based)
Garbage collection interval (request-based)
Options need to be passed in one string, with V8 option names being prefixed with double dashes. Multiple options need to be separated by whitespace. To get a list of all available V8 options, you can use the value ”--help” as follows:
Another example of specific V8 options being set at startup:
Names and features or usable options depend on the version of V8 being used, and might change in the future if a different version of V8 is being used in ArangoDB. Not all options offered by V8 might be sensible to use in the context of ArangoDB. Use the specific options only if you are sure that they are not harmful for the regular database operation.
This option is expected to only work reliably on a single server, DB-Server, or Agency. Do not try to use this feature on a Coordinator or in the ActiveFailover setup.