- Always set values to keys that have no defaults in schema, as setting a value to `undefined` does not return the "default" value when application:get_env/3 is called
- Provide an easier way to get the configuration by creating the config record, with appropriate defaults
- Code cleanup on BKV1/2/3 - make them easier to read/understand and for future work in refactoring the tests and removing some of the complexity.
- Now that test is running more consistently, tighten tests to actually test something in test_vnode_protection.
- Bump vnode protection to ?THRESHOLD+1 as 2.0 seems to have one extra message.
- Convert lager:info to lager:debug in successful get cases to reduce noise.
- Remove use of ConsistentType (use macros & pass BKV down to validate).
- Actually test FSM protection - previous limits didn't actually test overload at all. Now stop vnode and do an exact count of how many FSMs should have spun up.
- Make sure to wait for riak_kv before suspending any vnodes.
- Found sidejob race condition and updated test to compensate.
Added send of junk message through proxy to force vnode proxies into
overload state - without it, the first messgage would be forwarded to
the vnode and time out, which caused the test to fail.
Specifically, introduce the `gen_keys/1` and `assert_search/6` functions
into yokozuna_rt module and refactor tests to use them instead of copied
and pasted code fragments.
(cherry picked from commit 49d5c361c5)
There is a race in riak_snmp_stat_poller, which occurs when realtime
replication is enabled for more than two clusters. If the replication is
enabled quickly enough, then the bug does not manifest itself. This
change introduces a sleep between enabling replication between the
individual clusters, thus causing the test to fail consistently instead
of sporadically.
Specifically, introduce the `gen_keys/1` and `assert_search/6` functions
into yokozuna_rt module and refactor tests to use them instead of copied
and pasted code fragments.
There is a race in riak_snmp_stat_poller, which occurs when realtime
replication is enabled for more than two clusters. If the replication is
enabled quickly enough, then the bug does not manifest itself. This
change introduces a sleep between enabling replication between the
individual clusters, thus causing the test to fail consistently instead
of sporadically.
- Forward merge verify_stage_clustering fix
- Updates to allow either strings or atoms for node names in config & allow them to be different (atom or string) in test vs. config.
`riak_test_runner` does not support tagged tuples for failures. Fix
verify_snmp_repl module so that it returns the bare atom `fail` when it
fails, and write more detailed error messages to the log instead.
specify it wants all nodes in the cluster to have the type before
continuing. Update http_bucket_types to use said function.
(cherry picked from commit 31b1002b3e)
