AntidoteDB / antidote

80%

master: 83%

LAST BUILD ON BRANCH v0.2.2

branch: v0.2.2

CHANGE BRANCH

x

Reset

• v0.2.2
• 374-update-ranch-dependency-to-new-major-version-2
• 391-encapsulate-ets-tables
• 396-make-antidote-dc-manager-create-dc-idempotent
• 400-connected-dcs-metadata-not-updated
• 400-connected-dcs-metadata-not-updated-wip
• 421-revert
• 440-the-command-make-test-fails-when-performed-locally
• all-keys
• antidote-configuration
• antidote_channels
• aql-strong-consistency-3-patched
• chain
• chainrep
• checkout-description
• chumak2
• clean_config
• cleanup_pb_interface
• clocksi_interactive_coord_refactor
• clocksi_readitem
• cluster-management-pb-fix
• ct-refactor
• ct_fix
• dc_managemant_pb
• distributed-tests
• encapsulate-ets-tables
• fix-readme-link
• fix-riak
• fix-riak-calls
• fix-riak-cli-usage
• fix-riak-dynamic-join-leave
• fix-sync-log-setting
• fix_aborted_txns
• gc-hack
• github-workflow
• hooks_migrate
• interdc_log
• log_metrics
• logging_refactor
• master
• more_dialyzer
• multi-dc-tests
• palash25-more-docs
• rebar_upgrade
• refactor-stats
• remove_randcompat
• revert-363-typo-fix
• riak_migrate
• strong-consistency-3
• strong-consistency-3-patched
• strong-consistency-3-patched-2
• switch-long-short-name-at-runtime
• test-replicate-after-join
• update-local-docker
• update-stats
• use-dc-manager-in-tests
• v0.1.1
• v0.2.1
• v0.2.1-rc1
• vectorclock_abstraction

Build # 1450

Build Type

push

travis-ci

Committed by web-flow

Commit Message

Improve DC and InterDC Functionality (#408)

* Test case for issue #400 
* Removed stable riak metadata and improved create dc.
* Changed level of pending changes log messages
* Added a better named function to add nodes to a current dc
* Changed description and test case for dc descriptors. Fixed #400
* Reverted handle call for periodic updates, not needed
* Bumped to version 0.2.2
* Reduced severity of log message for missing external_descriptors
* Update include/antidote.hrl
* Added leave_dc functionality

We maintain our own dc id based on the riak_core_ring:cluster_name/1 command.
Riak maintains the cluster name itself, and contrary to the comment in dc_utilities,
it is restored on fail and restart correctly, even if all nodes fail at the same time.
This caused errors in maintaining the ring members after simplifying the create_dc function
and errors in shard count meta data. Switching back to the riak internal meta data
(which is managed and updated by riak_core anyway) fixes these issues.
The create_dc simplification also improved joining an empty cluster significantly (10 seconds for 8 shards).
This is also work towards being able to add/remove nodes dynamically to scale after some time elapsed.

Co-Authored-By: Peter Zeller <p_zeller@cs.uni-kl.de>

Run Details

2601 of 3271 relevant lines covered (79.52%)

1690.63 hits per line