-
Notifications
You must be signed in to change notification settings - Fork 89
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Antidote configuration #397
Conversation
fcd7568
to
aefb101
Compare
The new dockerfile can be seen here. |
Why are we bumping from v0.1.1. to v0.4.0? |
There are multiple versions everywhere and I didn't know which version to take. The Actually, I don't know how the rebar release version and the app.src version relates to the release tagged version/dockerfile version. Are they related at all? |
…s replaced by vm argument +Q. Furthermore, the default is much higher (65536) than this value (4096).
… limited anymore, and 8000 is a reasonable default size of the internally used table for named tables.
* Changed shell command to use the release shell instead * Added part on how to use the relase in the Readme * Rebar now understands symlinks for _checkouts, fixed readme * Removed deprecated env entrypoint script * Removed launch-nodes script, uses legacy RELX_REPLACE_OS_VARS functionality * Removed all schema files except the riak_core schema for compatibility purposes. Especially the erlang-vm.schema file caused problems when trying to use the NODE_NAME env variable * Configuration use the new .src functionality to enable native OS variable replacement in the root configuration file * Split up smaller configuration files, currently only for the network configuration * Enabled packing files (data antidote, data riak, logging files) in a root directory if specified via ROOT_DIR_PREFIX * Same for logging and data dirs (LOGGER_DIR_PREFIX, DATA_DIR_PREFIX) * Removed vars.config, it was only used for the Mustache templating system of Rebar, which was only used for the schema files of cuttlefish, which we do not use * Fixed ranch to version 1.7.1 for now, otherwise it would upgrade to a release candidate with breaking API changes * Bumped antidote to version 0.4.0 (both rebar.config and antidote.app.src) * Moved documentation from antidote.app.src to config/sys.config where all configuration for the release resides * Added a validation function to ensure the antidote data directory exists * Commented out stats calls which are not implemented yet in the antidote_stats module (metadata_updated, metadata_update_stable) Consequences: * Docker files have to be updated
…_opts. Verbose output is worse than default output, as it doesn't show failures at the end. Eunit_logs is not useful. Added eunit.coverdata to coverage stats. Silenced added test case
…cify export_cover_name with ct_run directly
4be7d06
to
84897dc
Compare
… the internal supervision tree
… Fixed riak ring metrics. Added process info metrics
9290b25
to
906f231
Compare
* Redirected lager output to logger via lager backend. * Added expensive statistics enabled by `extended_stats` application setting * Added warning monitor for logger warning messages * Bumped antidote_stats version * Added `antidote_stats` back again into the supervision tree, removed by mistake
906f231
to
6edacb9
Compare
Unified and simplified Antidote configuration.
antidote_stats
repositoryct_slave_ext
Consequences:
antidote_stats
repository-Application Key Value
parameter tuple, for whichValue
can be used for OS variable configurationct_run