gitlab-com-seaweedfs/seaweedfs
1
0
Fork 0
mirror of https://github.com/seaweedfs/seaweedfs.git synced 2024-01-19 02:48:24 +00:00
Code Issues Projects Releases Wiki Activity

Updated FAQ (markdown)

Chris Lu 2021-09-16 11:10:36 -07:00
parent 3d38be04e0
commit 0fcc0b475d
1 changed files with 4 additions and 2 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

6
FAQ.md

@ -111,7 +111,7 @@ Usually the logs are collected during a long period of time span. Let's say each
## gRPC Ports
gRPC can be derived from the `-port` number and adding 10000 on top of it, i.g., `-port=8080` means gRPC port is `18080`.
If you **must** have custom gRPC ports, you can specify a custom gRPC port when `master`, `volume server` or `filer` starts. But for all the other places referencing `master` and `filer`, you need to specify in this format:
If you **must** have custom gRPC ports, you can specify a custom gRPC port when `master`, `volume server` or `filer` starts. And for all the other places referencing `master` and `filer`, you also need to specify in this format:
```
<host>:<port>.<grpcPort>
```
@ -125,9 +125,11 @@ For example:
```
## Support ipv6?
Yes. A common error is when binding a link-scoped ipv6 address without a proper scope. This will cause `connect: invalid argument`.
e.g.
Note that the `-ip` and `-ip.bind` have different format, e.g.:
```
# invalid
-ip="[fe80::4c3:3cff:fe4f:7e0b]" -ip.bind="[fe80::4c3:3cff:fe4f:7e0b]"