HQebupt opened a new issue, #15060: URL: https://github.com/apache/pulsar/issues/15060
**Describe the bug** Geo-replication is the replication of persistently stored message data across multiple clusters of a Pulsar instance. I set up 3 geo replication clusters, and found the metric `pulsar_replication_rate_in` and `pulsar_replication_throughput_in` are duplicate calculation in Cluster B and Cluster C. <img width="714" alt="image" src="https://user-images.githubusercontent.com/4970972/162137568-5647dc34-4514-44b3-a5e8-71f84bb9fde1.png"> **To Reproduce** Set up 3 geo replication clusters: ClusterA, ClusterB, ClusterC Steps to reproduce the behavior: 1. Only produce message in ClusterA, watch PROM metric in ClusterA: `pulsar_rate_in` and `pulsar_throughput_in` 2. watch `pulsar_replication_rate_in` and `pulsar_replication_throughput_in` in ClusterB 3. watch `pulsar_replication_rate_in` and `pulsar_replication_throughput_in` in ClusterC 4. See `pulsar_replication_rate_in` in Cluster B is double value as `pulsar_rate_in` in Cluster A. the `pulsar_throughput_in ` does the same. **Expected behavior** The `pulsar_replication_rate_in` and `pulsar_replication_throughput_in` in ClusterB are equal to `pulsar_rate_in` and `pulsar_throughput_in` in Cluster A. **Screenshots** Here is ClusterA's metric. <img width="1671" alt="image" src="https://user-images.githubusercontent.com/4970972/162143955-8da8dec6-e24d-431c-a819-6e929d363f0d.png"> <img width="1671" alt="image" src="https://user-images.githubusercontent.com/4970972/162143796-1091722e-399d-42d8-b9c7-c4af2f623878.png"> Here is ClusterB's metric <img width="1678" alt="image" src="https://user-images.githubusercontent.com/4970972/162144288-f63e95e9-5d05-4272-83d4-78e001c04367.png"> <img width="1678" alt="image" src="https://user-images.githubusercontent.com/4970972/162144530-ec616921-19e3-48fc-bb82-74a686200394.png"> **Desktop (please complete the following information):** - Linux CentOS 7.2 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
