This is an automated email from the ASF dual-hosted git repository.
vatamane pushed a change to branch improve-replicator-app-stopping
in repository https://gitbox.apache.org/repos/asf/couchdb.git
discard fc69a0a3a Make replicator shutdown a bit more orderly
discard 89e3c7a61 Avoid making a mess in the logs when stopping replicator app
add 331f02025 fix couch_util:set_value/3
add 1b3b8415d Populate zone from `COUCHDB_ZONE` env variable
add 88e23b5b9 update docs
add 025ec2694 Merge pull request #5588 from apache/placement-zone-join
add 38d209c6f Avoid making a mess in the logs when stopping replicator app
add 5c394edae Make replicator shutdown a bit more orderly
This update added new revisions after undoing existing revisions.
That is to say, some revisions that were in the old version of the
branch are not in the new version. This situation occurs
when a user --force pushes a change and generates a repository
containing something like this:
* -- * -- B -- O -- O -- O (fc69a0a3a)
\
N -- N -- N refs/heads/improve-replicator-app-stopping
(5c394edae)
You should already have received notification emails for all of the O
revisions, and so the following emails describe only the N revisions
from the common base, B.
Any revisions marked "omit" are not gone; other references still
refer to them. Any revisions marked "discard" are gone forever.
No new revisions were added by this update.
Summary of changes:
src/couch/src/couch_util.erl | 10 ++++-
src/docs/src/cluster/databases.rst | 3 ++
src/docs/src/cluster/sharding.rst | 5 ++-
src/mem3/src/mem3_nodes.erl | 61 +++++++++++++++++++++++++--
src/mem3/test/eunit/mem3_zone_test.erl | 77 ++++++++++++++++++++++++++++++++++
5 files changed, 149 insertions(+), 7 deletions(-)
create mode 100644 src/mem3/test/eunit/mem3_zone_test.erl
