From 9eebb5e6015af1aa7c0ca3d6ca7ff2a8b2f3cb35 Mon Sep 17 00:00:00 2001 From: Matthias Hanel Date: Thu, 2 Apr 2020 15:05:27 -0400 Subject: [PATCH] ping_interval is parsed as duration now --- nats-server/configuration/README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/nats-server/configuration/README.md b/nats-server/configuration/README.md index 4799a37..84f40fa 100644 --- a/nats-server/configuration/README.md +++ b/nats-server/configuration/README.md @@ -120,7 +120,7 @@ authorization: { ### Connection Timeouts | 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` | | `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"` |