1
0
mirror of https://github.com/taigrr/nats.docs synced 2025-01-18 04:03:23 -08:00

Merge pull request #83 from nats-io/matthiashanel-patch-3

ping_interval is parsed as duration now
This commit is contained in:
Ginger Collison 2020-04-10 09:28:53 -05:00 committed by GitHub
commit 542bb62cfd
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23

View File

@ -120,7 +120,7 @@ authorization: {
### Connection Timeouts ### Connection Timeouts
| Property | Description | Default | | Property | Description | Default |
| :--- | :--- | :--- | | :--- | :--- | :--- |
| `ping_interval` | Interval in seconds, at which pings are sent to clients, leaf nodes and routes. In the presence of client traffic, such as messages or client side pings, the server will not send pings. Therefore it is recommended to keep this value bigger than what [clients use](../../developing-with-nats/connecting/pingpong.md). | `120`, 2 Minutes. | | `ping_interval` | Duration at which pings are sent to clients, leaf nodes and routes. In the presence of client traffic, such as messages or client side pings, the server will not send pings. Therefore it is recommended to keep this value bigger than what [clients use](../../developing-with-nats/connecting/pingpong.md). | `"2m"` |
| `ping_max` | After how many unanswered pings the server will allow before closing the connection. | `2` | | `ping_max` | After how many unanswered pings the server will allow before closing the connection. | `2` |
| `write_deadline` | Maximum number of seconds the server will block when writing. Once this threshold is exceeded the connection will be closed. See [_slow consumer_](../../developing-with-nats/events/slow.md) on how to deal with this on the client. | `"2s"` | | `write_deadline` | Maximum number of seconds the server will block when writing. Once this threshold is exceeded the connection will be closed. See [_slow consumer_](../../developing-with-nats/events/slow.md) on how to deal with this on the client. | `"2s"` |