Skip to content
This repository has been archived by the owner on Feb 27, 2023. It is now read-only.

Commit

Permalink
doc: config multiple supernodes for dfget
Browse files Browse the repository at this point in the history
Signed-off-by: Starnop <starnop@163.com>
  • Loading branch information
starnop committed Apr 16, 2019
1 parent 1731891 commit 8e61a85
Showing 1 changed file with 30 additions and 1 deletion.
31 changes: 30 additions & 1 deletion FAQ.md
Expand Up @@ -143,7 +143,36 @@ In addition, with `HTTP_PROXY` enabled, Dragonfly only supports protocol scheme

## Do we support HA of supernode in Dragonfly

Currently no. Supernode in Dragonfly suffers the single node of failure. In the later release, we will try to realise the HA of Dragonfly.
Currently no. In the later release, we will try to realise the HA of Dragonfly.

In fact, you can [provide multiple supernodes for dfget](#how-to-config-supernodes-for-dfget) as an alternative. When a peer started to download a task, it will register to one of the supernode list randomly. And when the supernode suffers failure, the task being downloaded on it will automatically migrate to the other supdernodes in the supernode list.

## How to config supernodes for dfget

There are two ways to config one or multiple supernodes for dfget

- config with config file

```shell
cat <<EOD > /etc/dragonfly/dfget.yml
nodes:
- supernode01
- supernode02
- supernode03
EOD
```

- config with cli

```shell
dfget --node supernode01 --node supernode02 --node supernode03

or

dfget --node supernode01,supernode02,supernode03
```

NOTE: If you use dfdaemon to call dfget, you can also pass this parameter to dfget via `dfdaemon --node`.

## How to use Dragonfly in Kubernetes

Expand Down

0 comments on commit 8e61a85

Please sign in to comment.