New answers tagged

0

My best setup is to mount /var and /media via nfs on all webnides since no php will be executed (since the old php bug running over nfs) and then lsyncd rest of folders over to webnodes . This will ensure performance and media replication


1

I know this is an old question, but I found it because I've been using Putty Command Sender for about five years and always thought it was pretty terrible. I didn't use it enough to go looking for alternatives until now. Just came across puttyCluster -- https://github.com/mingbowan/puttyCluster -- and holy sht, it's unreal I've been wasting time with stupid ...


0

If not already being used, you should consider using a replica set cluster. This will give your database high availability. The MongoDB documentation then provides a guide on performing version changes from 2.6 to 3.0 and from 3.0 to 3.2, respectively: https://docs.mongodb.com/manual/release-notes/3.0-upgrade/#upgrade-a-replica-set-to-3-0 https://docs....


2

Hot swapping components is a hardware feature, and has nothing to do with the software installed on the hardware. If your machines allow for cpu and ram hotswap then you should be able to do just that. But that's not really a heard of option of course.


5

Think about the question here: Hyperconverged solutions are focused on combining virtualization compute and storage resources together. These are still built atop commodity servers (Supermicro, Dell, HP, etc.), so the reasonable expectation is that you can hot-swap disks, but you likely would not be able hot-swap RAM. The point of these solutions is ...


0

It sounds like this is all happening on your one virtual machine, so no, if anything adding more nodes will increase the CPU load. The idea behind this kind of scaling is to spread out the load across multiple physical servers. If you only have one server to do it on, you aren't helping much by adding more nodes. Setting up this kind of environment on a ...


0

this is an issue with any Microsoft failover cluster using Server 2012 or below using either disk majority or node and disk majority. The Disk witness is a point of failure for the cluster. Even if all nodes are up, if the disk witness fails (we loose access to it) the cluster goes down. so what to do? 1) Make sure your disk witness is highly available so ...


-1

I was facing the same issue and when tried creating the cluster locally to have the cluster.conf file created but it doesnt seems to work. yum install pacemaker corosync haproxy pcs fence-agents-all systemctl disable firewalld ; systemctl stop firewalld systemctl enable pcsd.service pacemaker.service corosync.service haproxy.service pcs cluster setup --...


0

This is a common cause in IBM MQ: http://www-01.ibm.com/support/docview.wss?uid=swg21194313


0

As maxmlnkn answer states, you need a mechanism to setup/launch the appropriate Spark daemons in a Slurm allocation before a Spark jar can be executed via spark-submit. Several scripts/systems to do this setup for you have been developed. The answer you linked above mentions Magpie @ https://github.com/LLNL/magpie (full disclosure: I'm the developer/...



Top 50 recent answers are included