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.8K 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
MySQL Enterprise Cluster Issues after Network Gateway Change
Recently we had to change the network gateway for our 2 node MySQL cluster running on top of Oracle Grid (RHEL). None of the IPs changed. We noted the following behavior:
1) Once the change was made on the network, we could access the cluster successfully but we were unable to access the servers directly.
2) Once we updated the default Gateway on each of the two nodes under /etc/sysconfig/network-scripts the reverse became true. We were able to access the nodes individually but the cluster was no longer accessible.
We restarted the cluster and the network on both of the nodes and no change was noted. After being unable to locate any other location with either the old or new gateway configured, we are stuck. Current systems are accessing the active node but if it goes down, our system will fail as they will be unable to switch over. We are looking for guidance to resolve this issue so that we can restore the cluster to full operations.
Answers
-
What specifically did you change in your Network Gateway?
-
Only the IP Address changed from A.B.C.D to A.B.C.E
-
That's what I thought. In your question mentioned that no IP was changed.
Recently we had to change the network gateway for our 2 node MySQL cluster running on top of Oracle Grid (RHEL). None of the IPs changed. We noted the following behavior:
Can you look in the location below and make sure that the file reflects your changed IP.
/etc/hosts
-
The gateway IP address is not in the hosts file, it is (and has only ever been) in a routing table.