| … | |
… | |
| 116 | seed node that blocks for long periods will slow down everybody else. |
116 | seed node that blocks for long periods will slow down everybody else. |
| 117 | |
117 | |
| 118 | =item seeds - C<host:port> |
118 | =item seeds - C<host:port> |
| 119 | |
119 | |
| 120 | Seeds are transport endpoint(s) (usually a hostname/IP address and a |
120 | Seeds are transport endpoint(s) (usually a hostname/IP address and a |
| 121 | TCP port) of nodes thta should be used as seed nodes. |
121 | TCP port) of nodes that should be used as seed nodes. |
| 122 | |
122 | |
| 123 | The nodes listening on those endpoints are expected to be long-running, |
123 | The nodes listening on those endpoints are expected to be long-running, |
| 124 | and at least one of those should always be available. When nodes run out |
124 | and at least one of those should always be available. When nodes run out |
| 125 | of connections (e.g. due to a network error), they try to re-establish |
125 | of connections (e.g. due to a network error), they try to re-establish |
| 126 | connections to some seednodes again to join the network. |
126 | connections to some seednodes again to join the network. |
| … | |
… | |
| 523 | delivered again. |
523 | delivered again. |
| 524 | |
524 | |
| 525 | Inter-host-connection timeouts and monitoring depend on the transport |
525 | Inter-host-connection timeouts and monitoring depend on the transport |
| 526 | used. The only transport currently implemented is TCP, and AnyEvent::MP |
526 | used. The only transport currently implemented is TCP, and AnyEvent::MP |
| 527 | relies on TCP to detect node-downs (this can take 10-15 minutes on a |
527 | relies on TCP to detect node-downs (this can take 10-15 minutes on a |
| 528 | non-idle connection, and usually around two hours for idle conenctions). |
528 | non-idle connection, and usually around two hours for idle connections). |
| 529 | |
529 | |
| 530 | This means that monitoring is good for program errors and cleaning up |
530 | This means that monitoring is good for program errors and cleaning up |
| 531 | stuff eventually, but they are no replacement for a timeout when you need |
531 | stuff eventually, but they are no replacement for a timeout when you need |
| 532 | to ensure some maximum latency. |
532 | to ensure some maximum latency. |
| 533 | |
533 | |
