cluster-computing

This question is related to pbs job no output when busy . i.e Some of the jobs I submit produce no output when PBS/Torque is 'busy'. I imagine that it is busier when many jobs are being submitted one after another, and as it so happens, of the jobs submitted in this fashion, I often get some that do not produce any output. Here're some codes. Suppose I have a python script called "x_analyse.py" that takes as its input a file containing some data, and analyses the data stored in the file: ./x_analyse.py data_1.pkl Now, suppose I need to: (1) Prepare N such data files: data_1.pkl, data_2.pkl, ..

I've successfully setup a cluster of 2 JBoss AS 7 instances, and deployed the following SLSB: @Stateless @Remote(TestEJBRemote.class) @Clustered public class TestEJB implements TestEJBRemote { private static final long serialVersionUID = 1L; private static final Logger logger = Logger.getLogger(...); @Override public void test() { String nodeName = System.getProperty("jboss.node.name"); logger.info(nodeName); } } From the log files I can see that the bean is correctly deployed on the cluster. On the client side I then create a number of threads that lookup and invoke an instance of TestEJB .

I have a Glassfish 3.1.2 that runs in a cluster and a EJB 3.1 application. And I need two kind of Scheduled Methods in my application: one kind that runs only once (on a single node) once a day and other kind that runs on all nodes (every 1-2 Minutes) -- They do NOT need to run a syncron way! The requirement is just that this kind run on every node. I have no clue how to start with this cluster - problem, is this possible with @Schedule (and how) or do I need something else? I faced the exact same issue (need one cluster timer and a per node timer) and came across this question. So, for anyone

From a purest perspective, they kind of feel like identical concepts. Both manage sets of reosurces/nodes and control their access from or by external components. With a pool, you borrow and return these resources/nodes to and from the pool. With a cluster, you have a load balancer sitting in front of the resources/nodes and you hit the load balancer with a request. In both cases you have absolutely no control over which resource/node your request/borrow gets mapped to. So I pose the question: what's the fundamental difference between the "pool" pattern and a load-balanced cluster? A pool is