Replication issue

Steps to reproduce:
List the minimal actions needed to reproduce the behavior.

1. Create simulation of 1800 variables ingested from a NodeRed OPC UA client over time periods of 2, 5 and 10 seconds (4 x WinCC OPA UA Server).
2. Create the replication from local bucket (Windows Desktop - container) to remote bucket (NAS container)
3. The Current Queues Bytes is cumulated, I noticed the variables been replicated to the remote Bucket but why the Current Queues Bytes do not reduced?

Expected behavior:
the Current Queues Bytes is reduced after the variables been replicated to remote Bucket.

Actual behavior:
The Current Queues Bytes is cumulated.

noticed that "Current Queue Bytes" has been reduced from 10451563 to 58001, see attached image below.
Here is the addition information:

Environment info:

• System info: Linux 5.15.79.1-microsoft-standard-WSL2 x86_64
• InfluxDB version: InfluxDB v2.6.1 (git: 9dcf880fe0) build_date: 2022-12-29T15:53:07Z
• Other relevant environment details: Container runtime, disk info, etc

Questions:

1. Can you explain how replication works? Why the queue never drops off since the data has been replicated to the remote bucket?
2. How to control the accumulation of "Current Queue Bytes" and make it stable?
3. How to monitor the health of the replication?
4. Why is there such a big delay? Can you explain when the drop happens based on our replication configuration?

Start with the reported replication setup: a local bucket in a Windows Desktop container replicating to a remote NAS container, using InfluxDB v2.6.1 under WSL2. Review how Current Queue Bytes is expected to change and how replication health and delay are monitored; reproduce with the stated ingestion intervals if possible. Done means identifying why the queue remains high and documenting the expected drop behavior and monitoring approach.