Tag Info

New answers tagged

0

Well obviously you didn't bother to read the manual, because the option to do so is fairly obvious: backup When "backup" is present on a server line, the server is only used in load balancing when all other non-backup servers are unavailable. Requests coming with a persistence cookie referencing the server will always be served though. By ...


2

Absolutely. You can use any kind of storage for these kinds of applications. But I suspect your SAN is not configured properly for what you need. For something like this you don't just need space, you need speed, which means physical disks to share the load. If they are giving you a slice of a RAID5 array shared with 20 other hosts...that's not going to ...


0

When upgrading from one major or minor version of RabbitMQ to another (i.e. from 3.0.x to 3.1.x, or from 2.x.x to 3.x.x), or when upgrading Erlang, the whole cluster must be taken down for the upgrade (since clusters cannot run mixed versions like this). This will not be the case when upgrading from one patch version to another (i.e. from 3.0.x to 3.0.y); ...


1

Feel free to add this to comments, but you need to provide more details - what OS are you on, how is your listener configured, how many nodes in your cluster, how many replicas, how is your quorum configured, are all nodes/replicas in the same submask??? I can throw out a handful of reasons you aren't auto failing If you are on an OS earlier than 2012, ...


1

stat()-ing the files from the client mountpoint is how Gluster knows that the files need to be re-replicated, so basically the answer to your question is "no". The solution though is just to stat() every file - which is actually easier than it sounds, just run this from a client: find /mnt/repl1 -exec stat {} \; This is documented here.


2

Use an Elfiq Link Balancer to handle inbound and outbound ISP load balancing and failover. The outbound is set according to a dozen available load-balancing algorithms. The inbound is handled through DNS delegation. It's extremely effective. See: Internet connection redundancy with 2 ISP


1

Your intuition is likely correct. You can verify that the SIDs are different between your nodes by running: select name, sid from sys.server_principals on each node and comparing them. As far as how you're supposed to keep them in sync, do so at creation time (unfortunately, there's no way that I know of to change the SID post facto). That is, the create ...



Top 50 recent answers are included