[
https://issues.apache.org/jira/browse/ARTEMIS-4675?focusedWorklogId=911665&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-911665
]
ASF GitHub Bot logged work on ARTEMIS-4675:
-------------------------------------------
Author: ASF GitHub Bot
Created on: 26/Mar/24 18:29
Start Date: 26/Mar/24 18:29
Worklog Time Spent: 10m
Work Description: jbertram commented on PR #4844:
URL:
https://github.com/apache/activemq-artemis/pull/4844#issuecomment-2021186434
> With the current state of this PR the synchronizing is returning 0 and the
replica sync is returning 1.
I see the replica sync metric, but I don't see the "synchronizing" metric
you're referring to. Can you clarify which metrics you're inspecting?
The replica sync metric indicates whether the initial synchronization has
completed. Once the initial synchronization is done the primary is guaranteed
to be in sync with the backup unless the replication connection between the
brokers fails for some reason. It's not clear to me at this point if the
replication manager actually exposes metrics to track the current status
properly.
Issue Time Tracking
-------------------
Worklog Id: (was: 911665)
Time Spent: 1h (was: 50m)
> Add replication status metrics
> ------------------------------
>
> Key: ARTEMIS-4675
> URL: https://issues.apache.org/jira/browse/ARTEMIS-4675
> Project: ActiveMQ Artemis
> Issue Type: New Feature
> Components: Clustering
> Affects Versions: 2.32.0
> Reporter: Alvin Kwekel
> Priority: Major
> Time Spent: 1h
> Remaining Estimate: 0h
>
> Add metrics to be able to monitor the cluster replication status.
> Somewhat related to feature request ARTEMIS-4479.
> I've created a PR for this:
> https://github.com/apache/activemq-artemis/pull/4844
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
