# Group replication slow down existing asynchronous replication

**URL:** <https://forums.percona.com/t/group-replication-slow-down-existing-asynchronous-replication/28581>\
**Category:** MySQL & MariaDB\
**Created:** [February 20, 2024, 9:19pm UTC](https://forums.percona.com/t/group-replication-slow-down-existing-asynchronous-replication/28581 "2024-02-20T21:19:45Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![egel](https://avatars.discourse-cdn.com/v4/letter/e/e36b37/32.png) [@egel](https://forums.percona.com/u/egel)\
**Post date:** [February 20, 2024, 9:19pm UTC](https://forums.percona.com/t/group-replication-slow-down-existing-asynchronous-replication/28581/1 "2024-02-20T21:19:45Z")

</div>

I am running group replication using 8.0.35-27 and this cluster receive transactions from outside using regular asynchronous replication.  
The setup described there: [https://bugs.mysql.com/114072](https://bugs.mysql.com/114072)  
I’ve noticed that once latency of network increase between members the asynchronous replication accumulating lag till I am stopping all secondary members.  
I am curious if any one else had similar issue.

Thanks  
Evgeni

---

<div class="post-metadata">

**Author:** ![daniil.bazhenov](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/daniil.bazhenov/32/62_2.png) [@daniil.bazhenov](https://forums.percona.com/u/daniil.bazhenov)\
**Post date:** [March 20, 2024, 11:10am UTC](https://forums.percona.com/t/group-replication-slow-down-existing-asynchronous-replication/28581/2 "2024-03-20T11:10:53Z")

</div>

Thank you for contacting us,

I asked my colleagues and they don’t seem to have encountered this issue.

As I see you already have a discussion going on in the MySQL bug tracker, hopefully the problem will be resolved.

---

<div class="post-metadata">

**Author:** ![egel](https://avatars.discourse-cdn.com/v4/letter/e/e36b37/32.png) [@egel](https://forums.percona.com/u/egel)\
**Post date:** [March 22, 2024, 3:23pm UTC](https://forums.percona.com/t/group-replication-slow-down-existing-asynchronous-replication/28581/3 "2024-03-22T15:23:29Z")

</div>

Thank you very much for your time.

No, the issue is not resolved.  
We, most probably, would avoid GR over WAN as of now.

Best Regards

---

<div class="post-metadata">

**Author:** ![Michael\_Coburn](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/michael_coburn/32/18_2.png) [@Michael\_Coburn](https://forums.percona.com/u/Michael_Coburn)\
**Post date:** [March 24, 2024, 7:41pm UTC](https://forums.percona.com/t/group-replication-slow-down-existing-asynchronous-replication/28581/4 "2024-03-24T19:41:30Z")

</div>

Hi @egel thank you for sharing your use case with us here on the Forum  
Have you deployed any monitoring software against this environment? If not may I suggest PMM as it ships with GR support whereby we can review the throughput and latency between nodes to better understand your issue

> **[Percona Monitoring and Management - Quickstart guide](https://docs.percona.com/percona-monitoring-and-management/quickstart/index.html)**
>
> To get up and running with Percona Monitoring and Management (PMM) in no time, install PMM on Bare Metal/Virtual using the Easy-install script for Docker.

> [@egel](#):
>
> avoid GR over WAN as of now.

Yes absolutely, you should NOT be running your GR members across a WAN. It will “work”, however since GR is virtually synchronous, each write requires cluster-wide communications which can get expensive over slow links.  
Best Practices are to run your GR members in the same Region if you can reliably count on fast inter-availability zone communications.

---

<div class="post-metadata">

**Author:** ![egel](https://avatars.discourse-cdn.com/v4/letter/e/e36b37/32.png) [@egel](https://forums.percona.com/u/egel)\
**Post date:** [March 25, 2024, 7:21pm UTC](https://forums.percona.com/t/group-replication-slow-down-existing-asynchronous-replication/28581/5 "2024-03-25T19:21:54Z")

</div>

Yes, but galera based PXC working just fine in the same WAN. Therefore I was surprised to see such a issue with GR.

Thanks

---

<div class="post-metadata">

**Author:** ![Michael\_Coburn](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/michael_coburn/32/18_2.png) [@Michael\_Coburn](https://forums.percona.com/u/Michael_Coburn)\
**Post date:** [March 26, 2024, 7:27pm UTC](https://forums.percona.com/t/group-replication-slow-down-existing-asynchronous-replication/28581/6 "2024-03-26T19:27:43Z")

</div>

Thank you for the feedback @egel ! Marking this topic as solved, we can re-visit this topic if you can share some graphs from PMM

---

<div class="post-metadata">

**Author:** ![Michael\_Coburn](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/michael_coburn/32/18_2.png) [@Michael\_Coburn](https://forums.percona.com/u/Michael_Coburn)\
**Post date:** [March 26, 2024, 7:27pm UTC](https://forums.percona.com/t/group-replication-slow-down-existing-asynchronous-replication/28581/7 "2024-03-26T19:27:47Z")

</div>


