failover

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 goes live 2) Minimum 3 node limitation for create cluster As per bit understanding, redis-trib.rb not

I've read why is it bad practice to call System.gc() , and many others, e.g. this one describing a really disastrous misuse of System.gc() . However, there are cases when the GC takes too long and avoiding long pauses, e.g., by avoiding garbage is not exactly trivial and makes the code harder to maintain. IMHO calling GC manually is fine in the following common scenario: There are multiple interchangeable webserves with a failover in front of them. Every server uses a few gigabytes of heap and the STW pauses take much longer than an average request. The failover has no idea when GC is going to

I've had a few outages of 10 to 15 minutes, because apparently Microsoft had a 'blip' on their storages. They told me that it is because of a shared file system between the instances (making it a single point of failure?) I didn't understand it and asked how file share is involved , because I would assume a really dumb stateless IIS app that communicates with SQL Azure for it's data. I would assume the situation below: This is their reply to my question (I didn't include the drawing) The file shares are not necessarily for your web app to communicate to another resources but they are on our

Can someone provide a straightforward (but not simpler than possible) explanation of a transaction as applied to computing (even if copied from Wikipedia)? Vilx- A transaction is a unit of work that you want to treat as "a whole." It has to either happen in full or not at all. A classical example is transferring money from one bank account to another. To do that you have first to withdraw the amount from the source account, and then deposit it to the destination account. The operation has to succeed in full. If you stop halfway, the money will be lost, and that is Very Bad. In modern databases