[
https://issues.apache.org/jira/browse/ARTEMIS-4675?focusedWorklogId=910067&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-910067
]
ASF GitHub Bot logged work on ARTEMIS-4675:
-------------------------------------------
Author: ASF GitHub Bot
Created on: 15/Mar/24 09:02
Start Date: 15/Mar/24 09:02
Worklog Time Spent: 10m
Work Description: alvinkwekel commented on PR #4844:
URL:
https://github.com/apache/activemq-artemis/pull/4844#issuecomment-1999212609
Your feedback is much appreciated.
I absolutely follow your reasoning on the purpose of metrics. I'll remove
the activation sequence metric as its has no direct purpose in our current use
case.
Currently we check the replica sync with a jolokia query before we restart
the servers for maintenance. When its not synced we halt the process and
manually correct. This happend a few times. With these metrics we want to
detect these issues sooner, so we can correct them when they happen.
With the current state of this PR the synchronizing is returning 0 and the
replica sync is returning 1. Based on the description of the replica sync I
understand this is the _initial_ replication synchronization. I was hoping to
get more insight on the running/current synchronization with the synchronizing
metric. But if its basically returning the same underlying data I will remove
the "synchronizing" metric.
Could you elaborate, is the replica sync indeed fixed to either true or
false after the initial synchronization of will it reflect the current state?
Or can we use an other method to get the current replication state - after the
initial synchronization?
Issue Time Tracking
-------------------
Worklog Id: (was: 910067)
Time Spent: 50m (was: 40m)
> 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: 50m
> 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)
