-
Notifications
You must be signed in to change notification settings - Fork 16
Conversation
src/rabbit_mgmt_gc.erl
Outdated
handle_info({run_gc_soon, Interval}, State) -> | ||
{noreply, start_timer(Interval, State)}; | ||
handle_info(run_gc_soon, State) -> | ||
{noreply, start_timer(5000, State)}; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Use an interval from config, so the default could be easily changed.
Else we'd have to wait for a full stats background gc which can take a very long time during which metrics may be duplicated in the UI. [#147753285]
de8cc0a
to
983a228
Compare
When zeroing out stats after deletion. [#147753285]
@kjnilsson - there used to be a change to this line to use |
@lukebakken that is correct. Management GC needs to use the cluster-wide list of queues in order to retain historical queue metrics for queues that used to reside on the current node. |
[insert_entry(queue_msg_stats, Queue, TS, | ||
QNegStats, Size, Interval, false) | ||
|| {Size, Interval} <- BPolicies], | ||
% these need to be delayed by an interval |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@kjnilsson - is this comment still relevant? i.e, should a delay be introduced?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good point that can be removed.
…q-management-agent into rabbitmq-management-427
Fixes rabbitmq/rabbitmq-management#427
Depends on rabbitmq/rabbitmq-server#1278