From 240058a633aca95e2788fcd31437c5357a45bb05 Mon Sep 17 00:00:00 2001 From: Luis Paris Date: Thu, 28 May 2020 18:28:46 -0400 Subject: [PATCH 1/3] fix how-to fast start without old history --- .../10_how-to-fast-start-without-old-history.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/docs/01_nodeos/03_plugins/state_history_plugin/10_how-to-fast-start-without-old-history.md b/docs/01_nodeos/03_plugins/state_history_plugin/10_how-to-fast-start-without-old-history.md index 52ba3906700..a6a65874ad0 100644 --- a/docs/01_nodeos/03_plugins/state_history_plugin/10_how-to-fast-start-without-old-history.md +++ b/docs/01_nodeos/03_plugins/state_history_plugin/10_how-to-fast-start-without-old-history.md @@ -24,7 +24,7 @@ This procedure records the current chain state and future history, without previ 4. Look for `Placing initial state in block n` in the log, where n is the start block number. -5. Start a filler with `--fpg-create` (if PostgreSQL), `--fill-skip-to n`, and `--fill-trim`. Replace `n` with the value above. +5. If using a database filler, start the filler with `--fpg-create` (if PostgreSQL), `--fill-skip-to n`, and `--fill-trim`. Replace `n` with the value above. 6. Do not stop `nodeos` until it has received at least 1 block from the network, or it won't be able to restart. @@ -36,7 +36,7 @@ If `nodeos` fails to receive blocks from the network, then try the above using ` | Either use a firewall to block access to your `http-server-address`, or change it to `localhost:8888` to disable remote access. [[info]] -| Whenever you run a filler after this point, use the `--fill-trim` option. Only use `--fpg-create` and `--fill-skip-to` the first time. +| If you run a database filler after this point, use the `--fill-trim` option. Only use `--fpg-create` and `--fill-skip-to` the first time. [[info]] -| On large chains, this procedure creates a delta record that is too large for javascript processes to handle. 64-bit C++ processes can handle the large record. `fill-pg` and `fill-lmdb` break up the large record into smaller records when filling databases. +| On large chains, this procedure creates a delta record that is too large for javascript processes to handle. 64-bit C++ processes can handle the large record. For database fillers, `fill-pg` and `fill-lmdb` break up the large record into smaller records when filling databases. From 2f7864e4e88e3a212bb0485fd1523dc81c09beb7 Mon Sep 17 00:00:00 2001 From: Luis Paris Date: Thu, 28 May 2020 18:31:45 -0400 Subject: [PATCH 2/3] minor edit on how-to fast start --- .../10_how-to-fast-start-without-old-history.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/01_nodeos/03_plugins/state_history_plugin/10_how-to-fast-start-without-old-history.md b/docs/01_nodeos/03_plugins/state_history_plugin/10_how-to-fast-start-without-old-history.md index a6a65874ad0..a477a0597b1 100644 --- a/docs/01_nodeos/03_plugins/state_history_plugin/10_how-to-fast-start-without-old-history.md +++ b/docs/01_nodeos/03_plugins/state_history_plugin/10_how-to-fast-start-without-old-history.md @@ -39,4 +39,4 @@ If `nodeos` fails to receive blocks from the network, then try the above using ` | If you run a database filler after this point, use the `--fill-trim` option. Only use `--fpg-create` and `--fill-skip-to` the first time. [[info]] -| On large chains, this procedure creates a delta record that is too large for javascript processes to handle. 64-bit C++ processes can handle the large record. For database fillers, `fill-pg` and `fill-lmdb` break up the large record into smaller records when filling databases. +| On large chains, this procedure creates a delta record that is too large for javascript processes to handle. 64-bit C++ processes can handle the large record. If using a database filler, `fill-pg` and `fill-lmdb` break up the large record into smaller records when filling databases. From 9ee3f412ef0d1fc98dc8864872262632944c0b8e Mon Sep 17 00:00:00 2001 From: Luis Paris Date: Thu, 28 May 2020 19:01:05 -0400 Subject: [PATCH 3/3] minor edit on fill-trim option --- .../10_how-to-fast-start-without-old-history.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/01_nodeos/03_plugins/state_history_plugin/10_how-to-fast-start-without-old-history.md b/docs/01_nodeos/03_plugins/state_history_plugin/10_how-to-fast-start-without-old-history.md index a477a0597b1..4e1f5344830 100644 --- a/docs/01_nodeos/03_plugins/state_history_plugin/10_how-to-fast-start-without-old-history.md +++ b/docs/01_nodeos/03_plugins/state_history_plugin/10_how-to-fast-start-without-old-history.md @@ -36,7 +36,7 @@ If `nodeos` fails to receive blocks from the network, then try the above using ` | Either use a firewall to block access to your `http-server-address`, or change it to `localhost:8888` to disable remote access. [[info]] -| If you run a database filler after this point, use the `--fill-trim` option. Only use `--fpg-create` and `--fill-skip-to` the first time. +| If you run a database filler after this point, use the `--fill-trim` option when restarting. Only use `--fpg-create` and `--fill-skip-to` the first time. [[info]] | On large chains, this procedure creates a delta record that is too large for javascript processes to handle. 64-bit C++ processes can handle the large record. If using a database filler, `fill-pg` and `fill-lmdb` break up the large record into smaller records when filling databases.