document locking in dvc run/repro

Fixes #860
iterative · Dec 22, 2019 · 28dc9a3 · 28dc9a3
1 parent 5b3bf77
commit 28dc9a3
Show file tree

Hide file tree

Showing 2 changed files with 12 additions and 0 deletions.
diff --git a/static/docs/command-reference/repro.md b/static/docs/command-reference/repro.md
@@ -45,6 +45,10 @@ files, intermediate or final results. It saves all the data files, intermediate
 or final results into the <abbr>DVC cache</abbr> (unless `--no-commit` option is
 specified), and updates stage files with the new checksum information.
 
+### Parallel execution
+
+See [Parallel execution](/doc/command-reference/run#Parallel execution).
+
 ## Options
 
 - `-f`, `--force` - reproduce a pipeline, regenerating its results, even if no

diff --git a/static/docs/command-reference/run.md b/static/docs/command-reference/run.md
@@ -52,6 +52,14 @@ captures data and <abbr>caches</abbr> relevant <abbr>data artifacts</abbr> along
 the way. See [this example](/doc/get-started/example-pipeline) to learn more and
 try creating a pipeline.
 
+### Parallel execution
+
+When running your command, DVC will remove the project lock (`.dvc/lock` file),
+so that you will be able to run other DVC commands in parallel. However, it uses
+per-path read-write locking instead, to guarantee that no two DVC instances
+would be writing to the same path and don't write to paths that are being read
+from by another instance.
+
 ### Avoiding unexpected behavior
 
 We don't want to tell you how to write your code! However, please be aware that