You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
but this information not enough for client to connect to nsqd instance,for example when client use tcp protocol connect nsqd and then send IDENTIFY command,client may want to configure heartbeat_interval、output_buffer_size、output_buffer_timeout and deflate_level,the maximum value of these four configurations controlled by nsqd config:
1、heartbeat_interval value range [1000,configured_max] --max-heartbeat-interval flag controls the configured_max value
2、output_buffer_size value range [64,configured_max] --max-output-buffer-size flag controls the configured_max value
3、output_buffer_timeout value range [1ms,configured_max] --max-output-buffer-timeout flag controls the configured_max value and default is 250ms
4、deflate_level value range [1,configured_max] --max-deflate-level flag controls the configured_max value
so if /info api can return these four configurations value is helpful,api returns may looks like below:
mreiferson
changed the title
nsqd /info api returns more information about nsqd instance.
nsqd: /info api should return more configuration metadata
May 1, 2022
run one nsqd instance on the localhost with default config,current /info api returns looks like below:
but this information not enough for client to connect to nsqd instance,for example when client use tcp protocol connect nsqd and then send
IDENTIFY
command,client may want to configureheartbeat_interval
、output_buffer_size
、output_buffer_timeout
anddeflate_level
,the maximum value of these four configurations controlled by nsqd config:so if /info api can return these four configurations value is helpful,api returns may looks like below:
The text was updated successfully, but these errors were encountered: