New answers tagged clustering
You can decrease the errors during failover by putting database load balancing software in front of SQL Server. While SQL Server completes the failover, that software will hold inbound writes in a queue and will send inbound reads to other secondaries that are still up. Once failover is done, the software will drain the queue, sending the writes to the new ...
There are so many factors in place here as you can have multiple failover paths defined both in VMWare and the failover cluster. So the answers are almost as many as there are configuration options. But in general if a single EXI host stops. VMWare will migrate it's VM's to another and as all the virtual machines will have shut down the second windows ...
You could stop the passive node, drop it out of the cluster, unplug its LAN cable or otherwise disable the passive node before restarting the acitve services. The consequences could be .. um .. "intertesting", depending on how cleanly this process is handled and how skilled the tech team that configured the cluster were.
Yes, it is fine to run MySQL Cluster on two machines. You may need additional machine to put management process as an arbitrator - for details see https://dev.mysql.com/doc/refman/5.6/en/mysql-cluster-ndbd-definition.html#ndbparam-ndbd-arbitration. But it isn't critical, depends on what overall system reliability you would like to achieve.
Moving to Galera would be an option. Then your application has to be aware of 'deadlock detected try restarting transaction' errors. Another possibility is to set up a read slave and configure your application to use this slave for read_only queries. If one slave isn't enough you can add more and use them with a loadbalancer of any kind. Examples are ...
You should be able to migrate to MySQL Cluster (NDB Cluster), as new versions support foreign keys already and it is easy for scaling the load. However, as stated by Rick, maybe it would be good first to make sure, if dealing with response times by putting additional servers is the only option here. Please also note MySQL Cluster keeps all data in memory, ...
I would pause the node instead. This will prevent any role from starting on the node.
Disabling the service will not impact the cluster configuration. I would disable the node in possible owners as well to make sure that the server will not try to failover.
The issue turned out to be with the VIP addresses not being allowed to be accessed via port 1521 due to our firewall policy. These IPs are now permitted and the problem has been resolved. thanks to Balazs for all the help/
There may be problem in port allocation. If more then one instance running on single server OS gives separate ports for each instance other then 1433 (default port). TO resolve the issue go to SQL Server Configuration Manager TCP/IP change to fix port and give a port no the (TCP/IP) Network provide. And use same port No. in connection string of your web ...
The servers are using Dynamic quorum which is the default setting on Windows Server 2012. You can check the current votes of the cluster by running Get-ClusterNode | ft name, dynamicweight, nodeweight, state -AutoSize As Explained at WindowsItPro " When there are only two nodes left, one of the nodes loses its DynamicWeight so only one of the nodes ...
Top 50 recent answers are included