You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@couchdb.apache.org by va...@apache.org on 2019/02/15 18:27:02 UTC

[couchdb] branch shard-split updated: Fix small typo in readme

This is an automated email from the ASF dual-hosted git repository.

vatamane pushed a commit to branch shard-split
in repository https://gitbox.apache.org/repos/asf/couchdb.git


The following commit(s) were added to refs/heads/shard-split by this push:
     new 10e2141  Fix small typo in readme
10e2141 is described below

commit 10e2141a14676fb094a1be52127dbd9d0a41404f
Author: Nick Vatamaniuc <va...@apache.org>
AuthorDate: Fri Feb 15 13:26:54 2019 -0500

    Fix small typo in readme
---
 src/mem3/README_reshard.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/src/mem3/README_reshard.md b/src/mem3/README_reshard.md
index a3984e2..ccfaa29 100644
--- a/src/mem3/README_reshard.md
+++ b/src/mem3/README_reshard.md
@@ -13,8 +13,8 @@ Jobs creation happens in the `mem3_reshard_httpd` API handler module. That modul
 
 A single shard splitting job will be running in a gen_server from the `mem3_reshard_job` module. That job will go through a series of steps such as `initial_copy`, `build_indices`, `update_shard_map`, .... So, it will copy the data from the source to the targets, then build indices, then update the shard map and so on. After each splitting step is complete, the job goes to the next step and immediately "checkpoints" where it reports back to `mem3_reshard` manager. The manager persists th [...]
 
-Data!Definitions
-------------------------
+Data Definitions
+----------------
 
 Right below the `mem3_reshard:start_split_job/1` API level a job is converted to a `#job{}` record defined in the `mem3_reshard.hrl` internal header file. That record is then used throughout the resharding logic: the job manager `mem3_reshard` gen_server stores it in its jobs ets table as is. When a job process is started in `mem3_reshard_job` it gets passed a `#job{}` record as well. Then as the job process is running it will periodically report state back to the `mem3_reshard` manager  [...]