dispy icon indicating copy to clipboard operation
dispy copied to clipboard

Distributed and Parallel Computing Framework with / for Python

Results 87 dispy issues
Sort by recently updated
recently updated
newest added

This happens _very_ rarely, but it does happen on occasion... ``` ... 2019-03-05 11:50:16 dispy - Closing node 10.92.161.42 for archive / 1551804595176 2019-03-05 11:50:16 dispy - Closing node 10.92.161.39...

Sometimes killing jobs can fail: ``` 2019-02-28 16:11:00 dispynode - New job id 75357808 from 10.57.46.47/10.57.46.47 2019-02-28 16:11:08 dispynode - Terminating job 75357936 of "compute" (35244) 2019-02-28 16:11:10 dispynode -...

My requirement is to add a new node/agent/machine to existing cluster when the client program is already running. I am aware that their is allocate_node() but that didn't serve my...

_Some times_, at the end of a run I get the following error on the Dispy-client's `stderr`: ``` Exception happened during processing of request from ('10.9.211.113', 54290) Traceback (most recent...

I've stumbled across a little bit of an issue with how the `_Cluster` class adds items to its `worker_Q`. Around line: https://github.com/pgiri/dispy/blob/master/py3/dispy/__init__.py#L1851 the `job` object reference is mutated with the...

Is there any way to monitor nodes where dispynode.py was running (something like `DispyHTTPServer`, but for nodes)? For example, how many jobs (from different clients/job clusters) are running on this...

I found a bug in dispycosnode 4.10.2. If you use dispycosnode.py with parameter --peer it raises an unhandled exception: > Traceback (most recent call last): > File "/opt/pycharm-community-2018.1/helpers/pydev/pydevd.py", line 1664,...

For a disaster-recovery test, we started a batch using 128 nodes -- in two data-centers. A few minutes through it, we `kill`ed 64 of the nodes (all in one of...

Any exception thrown by the job's call-back is silently ignored (at least, in 4.9.1) and that's not right. The execution simply stops on that line of the callback, with nothing...

My use-case is this: - the actual computations performed by each node require various additional things to be right on every participating computer, which Dispy can not set right on...