Tag Info

New answers tagged

1

In some cases, it could be routing problems that are outside Amazon's control, hence why it won't show up on their status pages as being a problem. Look into using multiple regions for S3 or using Cloudfront instead. Since this case may be specific to your configuration, contacting Amazon about the problem would be the first step in resolving this, although ...


1

In summary, you're right and he's wrong; HA is much simpler, FT is very strict. VMware High Availability (HA) Restart virtual machines on other vSphere hosts in the cluster without manual intervention when a server outage is detected. http://www.vmware.com/uk/products/vsphere/features/high-availability An individual virtual machine can't be set ...


0

There a few things that you can try. Firstly make sure that the nodes can "see" each other. node1:~# ping node2 && node2:~# ping node1 There other thing that you shouldn't forget is that Pacemaker must control DRBD. DRBD can't be running when pacemaker starts. If it is you will get all kinds of weird things happening. Other than that you could ...


0

Having a bit more logs would be helpful, but at f first look it seems odd to me that you have a "target-role=Started" for a master/slave resource. Try removing it.


0

1: you need to be sure, the resource agent is there /usr/lib/ocf/resource.d/heartbeat/nginx 2: i don't seen nginx in your previous output 3: i'm using Suse 11 Sp2 and i have the nginx installed, without using extra package node01:~ # rpm -qf /usr/lib/ocf/resource.d/heartbeat/nginx resource-agents-3.9.2-0.25.5 I know Redhat has removed many resource ...


1

You have exchanged the values ​​of the options, you must use: crypto_cipher: aes256 crypto_hash: sha1 instead of crypto_cipher: sha1 crypto_hash: aes256


1

Implementing a web service that never fails to process even a single HTTP request is very hard. And it is probably not worth the effort. Even if you manage to get the service to handle every single POST request and send a successful reply, there are other problems the client could experience: Some middle-box between client and server tracks connection and ...


0

I'm working on an open source failover cluster manager written in shell script. It's in good shape even if it can miss some integration you will need. Check it out and let me know if there are some missing feature that you would like to see and use: https://code.google.com/p/back-to-work/ if you are good at shell programming (POSIX shell) you are welcome to ...


2

First and foremost, if you absolutely can't handle even small amounts of downtime (such as when a fail over occurs) then you should implement retry logic in your client application. If the response to these requests aren't time sensitive (eg. it's a log and it doesn't matter if the log isn't delivered immediately so long as it's recorded) then I'd ...



Top 50 recent answers are included