foster/bitcoin-bitcoin-core
0
0
Fork 0
mirror of https://github.com/bitcoin/bitcoin.git synced 2025-02-08 10:31:50 -05:00
Code Issues Activity

Merge #14704: doc: add detached release notes for #14060

Browse source 
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
This commit is contained in:
Wladimir J. van der Laan 2018-11-14 13:43:53 +01:00
commit 2e8f9dc2bb
No known key found for this signature in database
GPG key ID: 1E4AED62986CD25D
1 changed files with 21 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

21
doc/release-notes-14060.md Normal file
View file

@ -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.