[nats] Release v2.7.0

Details can be found [here](https://github.com/nats-io/nats-server/releases/tag/v2.7.0)

Signed-off-by: Ivan Kozlovic <ivan@synadia.com>
This commit is contained in:
Ivan Kozlovic 2022-01-13 18:46:43 -07:00
parent a60043ddf2
commit 0fe0b60555
1 changed files with 20 additions and 27 deletions

View File

@ -35,16 +35,15 @@ The routing protocol has been dramatically improved and adds support for account
$ docker run -d --name nats-main -p 4222:4222 -p 6222:6222 -p 8222:8222 %%IMAGE%% $ docker run -d --name nats-main -p 4222:4222 -p 6222:6222 -p 8222:8222 %%IMAGE%%
[INF] Starting nats-server [INF] Starting nats-server
[INF] Version: 2.6.0 [INF] Version: 2.7.0
[INF] Git: [3a4fd2b] [INF] Git: [bb87a650]
[INF] Name: NCFUZPNOENMPXL5LKXDN3LCXUXAVMH6CQUQEAKHRFYLYSI4URAV53RKE [INF] Name: NDO57CEPOVHEL4O5SROTRJC4LLHPO6AO7RZTJGZF3T2EGRKIEPSQHN6H
[INF] ID: NCFUZPNOENMPXL5LKXDN3LCXUXAVMH6CQUQEAKHRFYLYSI4URAV53RKE [INF] ID: NDO57CEPOVHEL4O5SROTRJC4LLHPO6AO7RZTJGZF3T2EGRKIEPSQHN6H
[INF] Using configuration file: /etc/nats/nats-server.conf [INF] Using configuration file: /etc/nats/nats-server.conf
[INF] Starting http monitor on 0.0.0.0:8222 [INF] Starting http monitor on 0.0.0.0:8222
[INF] Listening for client connections on 0.0.0.0:4222 [INF] Listening for client connections on 0.0.0.0:4222
[INF] Server is ready [INF] Server is ready
[INF] Cluster name is AdttP4E65rO4kboXExo1f7 [INF] Cluster name is my_cluster
[WRN] Cluster name was dynamically generated, consider setting one
[INF] Listening for route connections on 0.0.0.0:6222 [INF] Listening for route connections on 0.0.0.0:6222
... ...
@ -52,36 +51,30 @@ $ docker run -d --name nats-main -p 4222:4222 -p 6222:6222 -p 8222:8222 %%IMAGE%
# Note that since you are passing arguments, this overrides the CMD section # Note that since you are passing arguments, this overrides the CMD section
# of the Dockerfile, so you need to pass all arguments, including the # of the Dockerfile, so you need to pass all arguments, including the
# config file. # config file.
$ docker run -d --name=nats-2 --link nats-main -p 4222:4222 -p 6222:6222 -p 8222:8222 %%IMAGE%% -c nats-server.conf --routes=nats-route://ruser:T0pS3cr3t@nats-main:6222 $ docker run -d --name=nats-2 --link nats-main -p 4222:4222 -p 6222:6222 -p 8222:8222 %%IMAGE%% -c /etc/nats/nats-server.conf --routes=nats-route://ruser:T0pS3cr3t@nats-main:6222
# If you want to verify the routes are connected, try this instead: # If you want to verify the routes are connected, try this instead:
$ docker run -d --name=nats-2 --link nats-main -p 4222:4222 -p 6222:6222 -p 8222:8222 %%IMAGE%% -c nats-server.conf --routes=nats-route://ruser:T0pS3cr3t@nats-main:6222 -DV $ docker run -d --name=nats-2 --link nats-main -p 4222:4222 -p 6222:6222 -p 8222:8222 %%IMAGE%% -c /etc/nats/nats-server.conf --routes=nats-route://ruser:T0pS3cr3t@nats-main:6222 -DV
[INF] Starting nats-server [INF] Starting nats-server
[INF] Version: 2.6.0 [INF] Version: 2.7.0
[INF] Git: [3a4fd2b] [INF] Git: [not set]
[DBG] Go build: go1.16.8 [DBG] Go build: go1.17.6
[INF] Name: NCFUE5VRTU3L4ACSQGXFD4Q2ZG2LZZMNNQGKEOGYLIYQANO7HGYXJBYK [INF] Name: NBREZDV5RYHNFFTRCF6SEYEVSWZN362A756M5R53UFSNKEKCSNY4TYRQ
[INF] ID: NCFUE5VRTU3L4ACSQGXFD4Q2ZG2LZZMNNQGKEOGYLIYQANO7HGYXJBYK [INF] ID: NBREZDV5RYHNFFTRCF6SEYEVSWZN362A756M5R53UFSNKEKCSNY4TYRQ
[INF] Using configuration file: /etc/nats/nats-server.conf [INF] Using configuration file: /etc/nats/nats-server.conf
[DBG] Created system account: "$SYS" [DBG] Created system account: "$SYS"
[INF] Starting http monitor on 0.0.0.0:8222 [INF] Starting http monitor on 0.0.0.0:8222
[INF] Listening for client connections on 0.0.0.0:4222 [INF] Listening for client connections on 0.0.0.0:4222
[DBG] Get non local IPs for "0.0.0.0" [DBG] Get non local IPs for "0.0.0.0"
[DBG] ip=172.17.0.3 [DBG] ip=172.17.0.4
[INF] Server is ready [INF] Server is ready
[INF] Cluster name is IOJhRHKsF3h9itDTOzSpeY [INF] Cluster name is my_cluster
[WRN] Cluster name was dynamically generated, consider setting one
[INF] Listening for route connections on 0.0.0.0:6222 [INF] Listening for route connections on 0.0.0.0:6222
[DBG] Trying to connect to route on nats-main:6222 (172.17.0.2:6222) [DBG] Trying to connect to route on nats-main:6222 (172.17.0.3:6222)
[DBG] 172.17.0.2:6222 - rid:4 - Route connect msg sent [DBG] 172.17.0.3:6222 - rid:4 - Route connect msg sent
[INF] 172.17.0.2:6222 - rid:4 - Route connection created [INF] 172.17.0.3:6222 - rid:4 - Route connection created
[INF] 172.17.0.2:6222 - rid:4 - Router connection closed: Cluster Name Conflict [DBG] 172.17.0.3:6222 - rid:4 - Registering remote route "NAFMDWWB7ZNUGID6PEQ7ESRPWHMFFZN4IW5NEW2CHZD262MAIXKGDXVF"
[DBG] Attempting reconnect for solicited route "nats-route://ruser:T0pS3cr3t@nats-main:6222" [DBG] 172.17.0.3:6222 - rid:4 - Sent local subscriptions to route
[DBG] Trying to connect to route on nats-main:6222 (172.17.0.2:6222)
[DBG] 172.17.0.2:6222 - rid:5 - Route connect msg sent
[INF] 172.17.0.2:6222 - rid:5 - Route connection created
[DBG] 172.17.0.2:6222 - rid:5 - Registering remote route "NBPVQ52MK5SD2CHZ6VUIMOVTMHJ5M5RQZKTGG5Z5GD32NH6YCB6C3DYB"
[DBG] 172.17.0.2:6222 - rid:5 - Sent local subscriptions to route
``` ```
The server will load the configuration file below. Any command line flags can override these values. The server will load the configuration file below. Any command line flags can override these values.
@ -108,7 +101,7 @@ cluster {
authorization { authorization {
user: ruser user: ruser
password: T0pS3cr3t password: T0pS3cr3t
timeout: 0.75 timeout: 2
} }
# Routes are actively solicited and connected to from this server. # Routes are actively solicited and connected to from this server.