NSQ 1.2.0 release, distributed real-time messaging platform

NSQ is no center design, automatic node discovery and registration open source messaging system. As a basis for internal communications framework, easy to configure and publish. NSQ 1.2.0 has been released, as follows:

upgrade

• nsqd: Removed support for the old metadata scheme v0.3.8 and earlier versions used (you can not directly upgrade from 0.3.8 to v1.2.0, but by v1.0.0-compat or v1.1.0)
• Use Go module manages dependencies: dep are still supported, but not recommended

 characteristic

• nsqd：
  • Add --max-channel-consumers
  • Add timeout --min-output-buffer-timeout limit a user may request (increase the default value --max-output-buffer-timeout to 30 seconds)
  • Add flag to adjust the default value --output-buffer-timeout
  • Request to add a random load balancing Authd
  • TLS cert CommonName includes a client request in Authd
  • Add parameters to / stats endpoint to allow the skip of each client state
  • The producer client tcp connection to your stats
• nsq_to_file：
  • Including topic / channel at most log messages
  • Add  --log-level and --log-prefix
  • Large reconstruction, more robust file switch, synchronization and error handling
  • It supports the use of a separate working directory of --work-dir
  • The new logo --sync-interval
• nsq_to_http: Add --header
• nsqadmin: Add --base-path 

repair

• nsqd：
  • Close does not send the "magic" of the title connection
• nsqd, nsqlookupd, nsqadmin: reconstructed log level, general reconstruction in order to better quit all fatal errors
• nsqadmin: Switch to use as JudWhite / go-svc like nsqd and nsqadmin, repair the client message count and overall channel rate, Elint report repair / cleaning

For details, see the change log:

https://github.com/nsqio/nsq/releases/tag/v1.2.0