Skip to content

Commit e04d5b4

Browse files
committed
Force recovery sample
1 parent f61f57f commit e04d5b4

File tree

5 files changed

+28
-0
lines changed

5 files changed

+28
-0
lines changed
Lines changed: 18 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,18 @@
1+
# Force recovery
2+
3+
A sample application demonstrating how to start an instance with a corrupted write-ahead log file.
4+
5+
## Running
6+
7+
- To start the instance using the `tt` utility, execute the following command in the [config](../../../config) directory:
8+
9+
```console
10+
$ TT_FORCE_RECOVERY=true tt start force_recovery
11+
```
12+
13+
- To start the instance using the `tarantool` command, you can use both the `TT_FORCE_RECOVERY` environment variable and add the `--force-recovery` option.
14+
In the example below, the `tarantool` command is executed in the [config/instances.enabled/force_recovery](../../../config/instances.enabled/force_recovery) directory:
15+
16+
```console
17+
$ tarantool --name instance001 --config config.yaml --force-recovery -i
18+
```
Lines changed: 9 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,9 @@
1+
groups:
2+
group001:
3+
replicasets:
4+
replicaset001:
5+
instances:
6+
instance001:
7+
iproto:
8+
listen:
9+
- uri: '127.0.0.1:3301'
Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1 @@
1+
instance001:

0 commit comments

Comments
 (0)