Merge pull request #1709 from filecoin-project/docs/sealworker-updates
docs: Seal-worker updates
This commit is contained in:
commit
b462d7eb0b
@ -25,6 +25,8 @@ FULLNODE_API_INFO="JWT_TOKEN:/ip4/127.0.0.1/tcp/1234/http"
|
||||
STORAGE_API_INFO="JWT_TOKEN:/ip4/127.0.0.1/tcp/2345/http"
|
||||
```
|
||||
|
||||
You can also use `lotus auth api-info --perm admin` to quickly create _API_INFO env vars
|
||||
|
||||
- The **Lotus Node**'s `mutliaddr` is in `~/.lotus/api`.
|
||||
- The default token is in `~/.lotus/token`.
|
||||
- The **Lotus Storage Miner**'s `multiaddr` is in `~/.lotusstorage/config`.
|
||||
|
@ -27,15 +27,17 @@ To do this, simply run `lotus-seal-worker run`, and the seal worker will automat
|
||||
To check that the **Lotus Seal Worker** is properly connected to your storage miner, run `lotus-storage-miner info` and check that the remote worker count has increased.
|
||||
|
||||
```sh
|
||||
why@computer ~/lotus> lotus-storage-miner info
|
||||
Miner: t0103
|
||||
Sector Size: 16.0 MiB
|
||||
Power: 0 B / 16.0 MiB (0%)
|
||||
Worker use:
|
||||
Local: 0 / 2 (+1 reserved)
|
||||
**Remote: 0 / 1**
|
||||
PoSt Submissions: Not Proving
|
||||
Sectors: map[Committing:0 Proving:0 Total:0]
|
||||
why@computer ~/lotus> lotus-storage-miner workers list
|
||||
Worker 0, host computer
|
||||
CPU: [ ] 0 core(s) in use
|
||||
RAM: [|||||||||||||||||| ] 28% 18.1 GiB/62.7 GiB
|
||||
VMEM: [|||||||||||||||||| ] 28% 18.1 GiB/62.7 GiB
|
||||
GPU: GeForce RTX 2080, not used
|
||||
Worker 1, host computer
|
||||
CPU: [ ] 0 core(s) in use
|
||||
RAM: [|||||||||||||||||| ] 28% 18.1 GiB/62.7 GiB
|
||||
VMEM: [|||||||||||||||||| ] 28% 18.1 GiB/62.7 GiB
|
||||
GPU: GeForce RTX 2080, not used
|
||||
```
|
||||
|
||||
## Running Over the Network
|
||||
@ -53,12 +55,15 @@ Default config:
|
||||
```toml
|
||||
[API]
|
||||
ListenAddress = "/ip4/127.0.0.1/tcp/2345/http"
|
||||
RemoteListenAddress = "127.0.0.1:2345"
|
||||
```
|
||||
|
||||
To make your node accessible over the local area network, you will need to determine your machines IP on the LAN, and change the `127.0.0.1` in the file to that address.
|
||||
|
||||
A more permissive and less secure option is to change it to `0.0.0.0`. This will allow anyone who can connect to your computer on that port to access the [API](https://docs.lotu.sh/en+api). They will still need an auth token.
|
||||
|
||||
`RemoteListenAddress` must be set to an address which other nodes on your network will be able to reach
|
||||
|
||||
Next, you will need to [create an authentication token](https://docs.lotu.sh/en+api-scripting-support#generate-a-jwt-46). All Lotus APIs require authentication tokens to ensure your processes are as secure against attackers attempting to make unauthenticated requests to them.
|
||||
|
||||
### Connect the Lotus Seal Worker
|
||||
@ -71,17 +76,19 @@ Once this is set, run:
|
||||
lotus-seal-worker run
|
||||
```
|
||||
|
||||
To check that the **Lotus Seal Worker** is connected to your **Lotus Storage Miner**, run `lotus-storage-miner info` and check that the remote worker count has increased.
|
||||
To check that the **Lotus Seal Worker** is connected to your **Lotus Storage Miner**, run `lotus-storage-miner workers list` and check that the remote worker count has increased.
|
||||
|
||||
```sh
|
||||
why@computer ~/lotus> lotus-storage-miner info
|
||||
Miner: t05749
|
||||
Sector Size: 1 GiB
|
||||
Power: 0 B / 136 TiB (0.0000%)
|
||||
Committed: 1 GiB
|
||||
Proving: 1 GiB
|
||||
Worker use:
|
||||
Local: 0 / 1 (+1 reserved)
|
||||
**Remote: 0 / 1**
|
||||
Sectors: map[Proving:1 Total:1]
|
||||
why@computer ~/lotus> lotus-storage-miner workers list
|
||||
Worker 0, host computer
|
||||
CPU: [ ] 0 core(s) in use
|
||||
RAM: [|||||||||||||||||| ] 28% 18.1 GiB/62.7 GiB
|
||||
VMEM: [|||||||||||||||||| ] 28% 18.1 GiB/62.7 GiB
|
||||
GPU: GeForce RTX 2080, not used
|
||||
|
||||
Worker 1, host othercomputer
|
||||
CPU: [ ] 0 core(s) in use
|
||||
RAM: [|||||||||||||| ] 23% 14 GiB/62.7 GiB
|
||||
VMEM: [|||||||||||||| ] 23% 14 GiB/62.7 GiB
|
||||
GPU: GeForce RTX 2080, not used
|
||||
```
|
||||
|
@ -74,7 +74,7 @@ lotus-storage-miner info
|
||||
**Seal** random data to start producing **PoSts**:
|
||||
|
||||
```sh
|
||||
lotus-storage-miner pledge-sector
|
||||
lotus-storage-miner sectors pledge
|
||||
```
|
||||
|
||||
- Warning: On Linux configurations, this command will write data to `$TMPDIR` which is not usually the largest partition. You should point the value to a larger partition if possible.
|
||||
@ -90,11 +90,12 @@ lotus-storage-miner state power <miner>
|
||||
lotus-storage-miner state sectors <miner>
|
||||
```
|
||||
|
||||
## Change nickname
|
||||
## Performance tuning
|
||||
|
||||
Update `~/.lotus/config.toml` with:
|
||||
### `FIL_PROOFS_MAXIMIZE_CACHING=1` Environment variable
|
||||
|
||||
```sh
|
||||
[Metrics]
|
||||
Nickname="fun"
|
||||
```
|
||||
This env var can be used with `lotus-storage-miner`, `lotus-seal-worker`, and `lotus-bench` to make the precommit1 step faster at the cost of some memory use (1x sector size)
|
||||
|
||||
### `FIL_PROOFS_USE_GPU_COLUMN_BUILDER=1` Environment variable
|
||||
|
||||
This env var can be used with `lotus-storage-miner`, `lotus-seal-worker`, and `lotus-bench` to enable experimental precommit2 GPU acceleration
|
||||
|
Loading…
Reference in New Issue
Block a user