Giridhar Pemmasani
Giridhar Pemmasani
Does it work if you uncomment `or` part (so `bind_addr` is `` in your case)? Exception message can be fixed by checking errno (will commit this fix in the next...
Instead of `ff05::1`, can you try configured interface address (starts with `fd`)?
If your problem is also because the address used is `ff05::1`, then, as mentioned above, can you explicitly use configured interface address (e.g., for `eth0`) with both dispynode (with `-i`...
I don't quite understand what the question is, so likely this may not work: You may want to run another function (e.g., by creating another cluster, as done in [MapReduce...
See `node_shvars.py` in examples.
I am not sure I understand your question, but in case you are asking about replacing in-memory data, see latest release and example `replace_inmem.py`.
The message about `Could not send node status` at the end is harmless: The scheduler sends status messages to client. While cluster is alive, these messages are received by the...
I assume "nodes will break down" means the client and nodes lose connection? This can happen if "pulse" messages (exchanged at `pulse_interval` period) are lost. If 5 consecutive pulse messages...
The issue of SharedJobCluster not removing fault recovery file is fixed (in github master). The above log shows that sending a job failed, although I don't know why errno 32...
You can get latest code from github as either git clone or [zip](https://github.com/pgiri/dispy/archive/master.zip). If the first error is not due to sending job, then ignore my concern about large arguments....