Tag Info

New answers tagged

0

First you have see the differences between both options load balancing (without cluster) and Cluster with replication. Clustering has a formal meaning. A cluster is a group of resources that are trying to achieve a common objective, and are aware of one another. Clustering usually involves setting up the resources (servers usually) to exchange ...


0

Check whether the corresponding variables in /etc/ha.d/shellfuncs are set correctly: : ${HA_DIR=/etc/ha.d} : ${HA_RESOURCEDIR=$HA_DIR/resource.d} and verifies in /etc/init.d/heartbeat: . $HA_DIR/shellfuncs


6

The public cloud providers generally don't support broadcast/multicast methods, so any solution that relies on those will not be 'best'. At least for values of 'best' that include significant components of platform independence. In unicast-land, you have a bunch of options and a lot depends on just what it is you want to do with those images and what ...


3

As I understand it, the proper way of doing this is by using the API that your cloud provider offers to you. Trying to do this from the hosts is a little bit "stone-axe" territory. Use the nice space-age infrastructure that you're paying for.


0

An amazing recipe is given in the nginx Dockerfile: # forward request and error logs to docker log collector RUN ln -sf /dev/stdout /var/log/nginx/access.log RUN ln -sf /dev/stderr /var/log/nginx/error.log Simply, the app can continue writing to it as a file, but as a result the lines will go to stdout & stderr!


0

Try srv1 IPaddr::192.168.1.199/24/eth0 httpd instead of srv1 192.168.1.199 httpd


0

In September, Azure Websites gained support for Virtual Networks. If you have your MongoDB cluster configured to be in a virtual network, you can now add your website to that same virtual network. Once you do this, you can have your MongoDB driver access the nodes directly (via internal IP address for each node), rather than needing to open external ...


1

The article which you're reading is most likely long outdated. Using Heartbeat for resource management (stoping and starting resources upon failover) has been deprecated since about 2008. Pacemaker is the new standard solution for Linux-HA resource management. However, Pacemaker still requires something to handle cluster communication. For the communication ...


1

You need to run a cleanup on the old nodes, and perhaps a repair -- it won't move the data around of its own accord. See the documentation here for adding new nodes to a cluster.


0

Instead of using udev rules to maintain the name, you have a couple of options: With the iscsi target, you should be able to use the WWID instead by using the /dev/disk/by-id/scsi-.... address. If you list the contents of that directory, a symbolic link should exist to the relevant iscsi disk (/dev/sda2). This target will not change even if the device ...


0

It was my fault. Since 9.3 PostgreSQL does not symlink the files into the data folder anymore but instead uses the following two configuration options - which are cleaner. ssl_cert_file = '/etc/ssl/certs/ssl-cert-snakeoil.pem' # (change requires restart) ssl_key_file = '/etc/ssl/private/ssl-cert-snakeoil.key' # (change requires restart)



Top 50 recent answers are included