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
Whenever there is a conn_error, riak_core_connection_mgr_stats will create or update a stat which includes the entire error: https://github.com/basho/riak_repl/blob/develop/src/riak_core_connection_mgr_stats.erl#L231-L239. However, in the case of a noproc error, the PID and port number will be included as part of this error tuple essentially making this error unique. When a node hits such an error repeatedly this can lead to hundreds of thousands folsom spirals and counters being created and until all available memory is used by these statistics. Rather than store the entire Error tuple in the statistic, perhaps only the error slogan, of which there should only be a finite number, should be included?
The text was updated successfully, but these errors were encountered:
Basho-JIRA
changed the title
Memory Leak in riak_core_connection_mgr_stats
Memory Leak in riak_core_connection_mgr_stats [JIRA: RIAK-2231]
Oct 16, 2015
Whenever there is a conn_error, riak_core_connection_mgr_stats will create or update a stat which includes the entire error: https://github.com/basho/riak_repl/blob/develop/src/riak_core_connection_mgr_stats.erl#L231-L239. However, in the case of a noproc error, the PID and port number will be included as part of this error tuple essentially making this error unique. When a node hits such an error repeatedly this can lead to hundreds of thousands folsom spirals and counters being created and until all available memory is used by these statistics. Rather than store the entire Error tuple in the statistic, perhaps only the error slogan, of which there should only be a finite number, should be included?
The text was updated successfully, but these errors were encountered: