failover

问题 I have two Azure Web Sites in two different regions with AWS Route 53 set as DNS Failover (I think Azure Traffic Manager would be the same). Is there a way to share auth cookie between the two sites? 来源： https://stackoverflow.com/questions/27702205/auth-cookie-azure-web-sites-and-dns-failover

问题 We're using currently c3p0 with postgresql. Does c3p0 supports any fail-over mechanisms (no info in documentation so I assume that unfortunately no)? I've found that mysql,oracle and ms sql supports some failover options in jdbc url, e.g. jdbcUrl="jdbc:sqlserver://mainserver:1433;failoverPartner=backupserver; Are pgpool and pgpool-II only posibilities for postgresql? 回答1: I don't know of any built-in failover in either the JDBC driver or the PostgreSQL core Other options besides pgpool-II are

问题 I am currently using activemq failover uir for client reconnecting to the broker, and I also don't want "send" operation to be blocked when it disconnect, so I am using URI like failover:(tcp://192.168.193.177:61616)?timeout=1 , while the problem is if I can't get connection for the first time, the connecting will time out and the reconnecting doesn't work, the exception I got: Dec 7, 2011 3:39:28 PM org.apache.activemq.transport.failover.FailoverTransport oneway INFO: Failover timed out

问题 I am using NLog for DB logging. If the DB is down then I only need it to log to a file. Is there a way to do this? I don't want to record log entries log in both a file and the DB. If the DB target fails to log (if DB is down) only then do I have to log to the file. Is there any fail over or fallback feature with Nlog? 回答1: Yes, there is a way. It's called a FallbackGroup . Documentation can be found here: https://github.com/nlog/NLog/wiki/FallbackGroup-target Here is an example taken

问题 I am working on the high availability aspect of a webapp deployed in tomcat. I require a mechanism for failover such that it should not be apparent to the webapp user and have am looking at tomcat clustering as a solution for the same. If I am looking only at failover and not on load balancing(not required at this point) , how should I configure the tomcat cluster ? EDIT I am aware about the mechanism but am looking at the configuration aspect. 回答1: looking for this myself, I finally found

问题 I know I'm asking something very obvious about cluster failover. I read on redis.io that, if any master cluster node fails it will affect to other master nodes until slave come to take in charge. In my structure, I'm not defining any slave and just working with 3 masters. I'm thinking to modify the redis-trib.rb file, which will remove the defected server and will start the cluster with other 2 nodes. I'm confused about a couple of things, 1) Resharding Could not possible until failed server

问题 As per MarkLogic cluster recommendation, we need to configure it as per below link MarkLogic Cluster - Configure Forest with all documents Forest configuration is done as per MarkLogic on Azure Guide Page No. 28 i.e. Azure storage key has been set in Security -> Credentials -> Azure Data directory has been set as azure:// This is working fine and every forest on cluster host has been set in a different container within same azure Blob. Now i want to configure failover cluster by replicating

问题 Namenode HA (NFS, QJM) is available in hadoop 2.x (HDFS-1623). It provides fast failover for Namenode, but I can't find any description on how long does it take to recover from a failure. Can any one tell me? Thanks for your answer.As the matter of fact,I want to know the time between the transformation of two nodes(active namenode and standby namenode).can you tell me how long? 回答1: Here are some qualified examples of times for failover with a standby NameNode: A 60 node cluster with 6

问题 I have configured Multi-AZ RDS mysql instance with no read replicas in a development environment and I am testing Multi-AZ RDS fail-over by rebooting the DB instance. Below is my observation: During RDS fail-over, the client application will not lost connection but at the same time it won't be able to access the database as well and once fail-over completes, client will able to access the database. Update 1: Above observation is wrong.What I observed just now is that after fail-over

问题 I'm using .Net 4.0 and SqlConnection/SqlCommand to connect to a 2008 R2 SQL server that has mirroring setup. The ConnectionString specifies a Failover Partner Can anyone explain how the ConnectionTimeout setting affects the ability for a client to failover to the mirror? Ie does it always wait the ConnectionTimeout before going to the failover server? Or does the failover becoming primary mean the client will immediately switch to connecting to the failover disregarding the ConnectionTimeout?