You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
poetry run hathor-cli run_node --memory-storage --status 8080 --testnet --enable-event-queue
27
24
```
28
25
29
-
**ATTENTION**: While the Event Queue is in beta, it's considered unsafe. You must not use it in production environments.
30
-
31
26
### First run
32
27
33
28
If this is the first time your full node is running with the event queue enabled, there are 3 possibilities:
@@ -45,7 +40,7 @@ For case 2.2, an extra loading step will be performed during full node initializ
45
40
46
41
After running the full node with the Event Queue enabled, if you restart your full node (that is, stop it and then run it again), there are 2 possibilities:
47
42
48
-
1. You run the full node with the `--x-enable-event-queue` CLI option, that is, you keep the Event Queue enabled, or
43
+
1. You run the full node with the `--enable-event-queue` CLI option, that is, you keep the Event Queue enabled, or
49
44
2. You run the full node without the CLI option, that is, you don't enable it, but you **have to clear the event data in the database**.
50
45
51
46
For case 1, the full node will start normally, and continue to generate new events for synced vertices from where it stopped in the previous run.
0 commit comments