nsq v0.2.21 Release Notes

Release Date: 2013-06-07 // almost 11 years ago
  • โฌ†๏ธ Upgrading from 0.2.20: there are no backward incompatible changes in this release.

    ๐Ÿš€ This release introduces a significant new client feature as well as a slew of consistency and recovery improvements to diskqueue.

    First, we expanded the feature negotiation options for clients. There are many cases where you want different output buffering semantics from nsqd to your client. You can now control both โฑ output buffer size and the output buffer timeout via new fields in the IDENTIFY command. You can ๐Ÿšค even disable output buffering if low latency is a priority.

    ๐Ÿ”€ You can now specify a duration between fsyncs via --sync-timeout. This is a far better way to ๐Ÿ”€ manage when the process fsyncs messages to disk (vs the existing --sync-every which is based on # ๐Ÿ”€ of messages). --sync-every is now considered a deprecated option and will be removed in a future ๐Ÿš€ release.

    Finally, 0.2.20 introduced a significant regression in #176 where a topic would not write messages ๐Ÿš€ to its channels. It is recommended that all users running 0.2.20 upgrade to this release. For โž• additional information see #217.

    ๐Ÿ†• New Features / Enhancements:

    • #214 - add --sync-timeout for time based fsync, improve when diskqueue syncs
    • #196 - client configurable output buffering
    • #190 - nsq_tail generates a random #ephemeral channel

    ๐Ÿ› Bug Fixes:

    • #218/#220 - expose --statsd-interval for nsqadmin to handle non 60s statsd intervals
    • #217 - fix new topic channel creation regression from #176 (thanks @elubow)
    • #212 - dont use port in nsqadmin cookies
    • #214 - dont open diskqueue writeFile with O_APPEND
    • #203/#211 - diskqueue depth accounting consistency
    • #207 - failure to write a heartbeat is fatal / reduce error log noise
    • #206 - use broadcast address for statsd prefix
    • #205 - cleanup example utils exit