mirror of https://github.com/bitcoin/bitcoin
86cddf0856
doc: add detached release notes for #14060 (mruddy)
Pull request description:
Adding detached release notes for #14060 in order to assist with https://github.com/bitcoin/bitcoin/pull/14688.
Tree-SHA512: 170cd0b6ac27237f58875f301132e0695dee36eec5d90a0c1234c0fa9db125151e6cebd94e63e634ddc4ddcfb77d7a4a07434ffd3725cb0dfa13fc4ccfbde2a0
pull/14687/head
commit
2e8f9dc2bb
@ -0,0 +1,21 @@
|
||||
Configuration
|
||||
-------------
|
||||
|
||||
The outbound message high water mark of the ZMQ PUB sockets are now
|
||||
configurable via the options:
|
||||
|
||||
`-zmqpubhashtxhwm=n`
|
||||
|
||||
`-zmqpubhashblockhwm=n`
|
||||
|
||||
`-zmqpubrawblockhwm=n`
|
||||
|
||||
`-zmqpubrawtxhwm=n`
|
||||
|
||||
Each high water mark value must be an integer greater than or equal to 0.
|
||||
The high water mark limits the maximum number of messages that ZMQ will
|
||||
queue in memory for any single subscriber. A value of 0 means no limit.
|
||||
When not specified, the default value continues to be 1000.
|
||||
When a ZMQ PUB socket reaches its high water mark for a subscriber, then
|
||||
additional messages to the subscriber are dropped until the number of
|
||||
queued messages again falls below the high water mark value.
|
Loading…
Reference in new issue