Skip to content

Commit 527bae0

Browse files
adding the new flag store-tx-result-error-messages to the execution data sync doc (#1507)
* adding the new flag store-tx-result-error-messages to the execution data sync doc * Apply suggestion from @peterargue Co-authored-by: Peter Argue <89119817+peterargue@users.noreply.github.com> * Apply suggestion from @peterargue Co-authored-by: Peter Argue <89119817+peterargue@users.noreply.github.com> * Apply suggestion from @peterargue Co-authored-by: Peter Argue <89119817+peterargue@users.noreply.github.com> * remoing an extra flag --------- Co-authored-by: Peter Argue <89119817+peterargue@users.noreply.github.com>
1 parent 36aa7fe commit 527bae0

File tree

1 file changed

+7
-5
lines changed

1 file changed

+7
-5
lines changed

docs/protocol/node-ops/access-nodes/access-node-configuration-options.md

Lines changed: 7 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -135,21 +135,22 @@ Store the **`root-protocol-state-snapshot.json`** into the **`/bootstrap/public-
135135

136136
Now you have the execution sync setup and the root checkpoint in place, it’s time to configure the node to index all of the data so it can be used for script execution.
137137

138-
There are 2 cli flags that you will need to add:
138+
There are 3 cli flags that you will need to add:
139139

140140
- `--execution-data-indexing-enabled=true` This will enable the indexer.
141+
- `--store-tx-result-error-messages=true` This will fetch and index transaction result error messages from execution nodes.
141142
- `--execution-state-dir` This defines the path where the registers db will be stored. A good default is on the same drive as the protocol db. e.g. `/data/execution-state`
142143

143144
# Start your node
144145

145-
Now that all of the settings to enable indexing are in place, you can start your node.
146+
Now that all the settings to enable indexing are in place, you can start your node.
146147

147148
At a minimum, you will need the following flags:
148149

149150
```
150151
--execution-data-indexing-enabled=true
152+
--store-tx-result-error-messages=true
151153
--execution-state-dir=/data/execution-state
152-
--execution-data-sync-enabled=true
153154
--execution-data-dir=/data/execution-data
154155
```
155156

@@ -249,8 +250,9 @@ As a best practice, specify a path with `--execution-data-dir`. A sensible defau
249250
Below is a list of the available CLI flags to control the behavior of Execution Data Indexer.
250251

251252
| Flag | Type | Description |
252-
| ------------------------------- | ------ | ----------------------------------------------------------------------------------------------------------- |
253-
| execution-data-indexing-enabled | bool | Whether to enable the execution data indexing. Default is false |
253+
|---------------------------------|--------|-------------------------------------------------------------------------------------------------------------|
254+
| execution-data-indexing-enabled | bool | Whether to enable the execution data indexing. Default is false. |
255+
| store-tx-result-error-messages | bool | Whether to enable storing transaction error messages into the db. Default is false. |
254256
| execution-state-dir | string | Directory to use for execution-state database. Default is in the user’s home directory. |
255257
| execution-state-checkpoint | string | Location of execution-state checkpoint (root.checkpoint.\*) files. |
256258
| event-query-mode | string | Mode to use when querying events. one of [local-only, execution-nodes-only(default), failover] |

0 commit comments

Comments
 (0)