You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ozone.apache.org by "Janus Chow (Jira)" <ji...@apache.org> on 2023/12/16 23:44:06 UTC
[jira] [Updated] (HDDS-9235) ReplicationManager metrics not collected after restart
[ https://issues.apache.org/jira/browse/HDDS-9235?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Janus Chow updated HDDS-9235:
-----------------------------
Target Version/s: 1.5.0 (was: 1.4.0)
I am managing the 1.4.0 release and we currently have more than 500 issues targeted for 1.4.0. I am moving the target field to 1.5.0.
If you are actively working on this jira and believe this should be targeted for the 1.4.0 release, Please reach out to me via Apache email or Slack.
> ReplicationManager metrics not collected after restart
> ------------------------------------------------------
>
> Key: HDDS-9235
> URL: https://issues.apache.org/jira/browse/HDDS-9235
> Project: Apache Ozone
> Issue Type: Bug
> Components: SCM
> Affects Versions: 1.4.0
> Reporter: Attila Doroszlai
> Assignee: Aswin Shakil
> Priority: Major
>
> {{ReplicationManager}} can be stopped/restarted by admin from CLI.
> {{stop()}} unregisters the metrics source, and {{start()}} used to (re)create it. But now after HDDS-9090 it isn't re-created, so it won't work after restart. One way to fix this is to add a method in {{ReplicationManagerMetrics}} to register it with the metrics system (without creating a new instance), and call this new method from {{start()}}.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@ozone.apache.org
For additional commands, e-mail: issues-help@ozone.apache.org