Discussions
Categories
- 196.8K All Categories
- 2.2K Data
- 239 Big Data Appliance
- 1.9K Data Science
- 450.3K Databases
- 221.7K General Database Discussions
- 3.8K Java and JavaScript in the Database
- 31 Multilingual Engine
- 550 MySQL Community Space
- 478 NoSQL Database
- 7.9K Oracle Database Express Edition (XE)
- 3K ORDS, SODA & JSON in the Database
- 544 SQLcl
- 4K SQL Developer Data Modeler
- 187K SQL & PL/SQL
- 21.3K SQL Developer
- 295.9K Development
- 17 Developer Projects
- 138 Programming Languages
- 292.5K Development Tools
- 107 DevOps
- 3.1K QA/Testing
- 646K Java
- 28 Java Learning Subscription
- 37K Database Connectivity
- 155 Java Community Process
- 105 Java 25
- 22.1K Java APIs
- 138.1K Java Development Tools
- 165.3K Java EE (Java Enterprise Edition)
- 18 Java Essentials
- 160 Java 8 Questions
- 86K Java Programming
- 80 Java Puzzle Ball
- 65.1K New To Java
- 1.7K Training / Learning / Certification
- 13.8K Java HotSpot Virtual Machine
- 94.3K Java SE
- 13.8K Java Security
- 204 Java User Groups
- 24 JavaScript - Nashorn
- Programs
- 439 LiveLabs
- 38 Workshops
- 10.2K Software
- 6.7K Berkeley DB Family
- 3.5K JHeadstart
- 5.7K Other Languages
- 2.3K Chinese
- 171 Deutsche Oracle Community
- 1.1K Español
- 1.9K Japanese
- 232 Portuguese
Missing status node in a MySQL 5.7 Multi Master Cluster

Dear all,
We have a problem with a MySQL 5.7 Multi Master Cluster. The last 2022/03/03 we had the 3 cluster nodes in online status but a day 2 of these nodes changed their status to missing.
We have try to change the missing nodes status to online status but we can't do and for this we need your help. In the cluster we have the online node called srvrh3 and a missing node called srvrh2.
Both nodes are in a production environment and have been fine until the 2022/03/03. When we try the to add the srvrh2 node to the cluster from the mysql shell installed in srvrh3 with the command cluster.addInstance("ic:<$PASSWORD>@<$HOST_NODE>:3306") we obtain the next errors:
2022-03-15T15:41:48.059796Z 1124340 [Note] Slave I/O thread for channel 'group_replication_recovery': connected to master '[email protected]:3306',replication started in log 'FIRST' at position 4
2022-03-15T15:41:48.095095Z 1124341 [ERROR] Slave SQL for channel 'group_replication_recovery': Error 'Can't find any matching row in the user table' on query. Default database: 'mysql_innodb_cluster_metadata'. Query: 'GRANT REPLICATION SLAVE ON *.* TO 'mysql_innodb_cluster_r0440653904'@'%'', Error_code: 1133
2022-03-15T15:41:48.095184Z 1124341 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log '1.000001' position 9205.