You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@solr.apache.org by "David Smiley (Jira)" <ji...@apache.org> on 2025/11/09 17:05:00 UTC
[jira] [Commented] (SOLR-17857) Investigate potential memory leaks from OTEL metrics
[ https://issues.apache.org/jira/browse/SOLR-17857?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18036612#comment-18036612 ]
David Smiley commented on SOLR-17857:
-------------------------------------
Probably the best protection technique is Solr's great ObjectReleaseTracker – using this on SolrMetricsContext. I have some WIP. My _preliminary_ observation is that there are some non-closed contexts but they seem unlikely to pose a threat – at least with Solr's built-in plugins. For example contexts for container handlers aren't getting closed. But the risk/concern is core level. I see the UpdateLog's context isn't getting closed. And there's some weird V2 handler that seems special somehow; it's context isn't getting closed. *I think SolrMetricsContext should implement AutoCloseable*
> Investigate potential memory leaks from OTEL metrics
> ----------------------------------------------------
>
> Key: SOLR-17857
> URL: https://issues.apache.org/jira/browse/SOLR-17857
> Project: Solr
> Issue Type: Sub-task
> Reporter: Matthew Biscocho
> Assignee: David Smiley
> Priority: Major
>
> There was a memory leak from gauges in SOLR-13677
> We should do some testing and investigation that this issue hasn't resurfaced with the migration to OTEL.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@solr.apache.org
For additional commands, e-mail: issues-help@solr.apache.org