From 28dc9a3d5b85b284594698cb3dcee009a257e71a Mon Sep 17 00:00:00 2001 From: Ruslan Kuprieiev Date: Mon, 16 Dec 2019 13:34:11 +0200 Subject: [PATCH] document locking in `dvc run/repro` Fixes #860 --- static/docs/command-reference/repro.md | 4 ++++ static/docs/command-reference/run.md | 8 ++++++++ 2 files changed, 12 insertions(+) diff --git a/static/docs/command-reference/repro.md b/static/docs/command-reference/repro.md index a990c2b76c2..d0e978afb42 100644 --- 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 DVC cache (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 index 7c953794059..ba0c6ff9b61 100644 --- a/static/docs/command-reference/run.md +++ b/static/docs/command-reference/run.md @@ -52,6 +52,14 @@ captures data and caches relevant data artifacts 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