Dan Blanchard
Dan Blanchard
It appears the ssh2-python is currently incompatible with PyPy, so I'm going to hold off on this until ParallelSSH/ssh2-python#16 gets addressed.
ssh2-python has fixed the issue on their end, but still waiting for a new parallel-ssh release with the fix there.
This needs more testing before merging. I've found a few cases where it seems like options aren't being resolved or sent to Storm properly.
This is very close to being ready to merge. I am currently being foiled by ParallelSSH/ssh2-python#51 though.
I've tested this with submitting topologies and running them locally, and it all seems to work now.
Ugh, the ssh2-python devs removed the wheels from PyPI (breaking the cardinal rule of never removing packages from PyPI). The pypy build will continue to fail until they put the...
Seems like there's still an issue with getting all of the options resolved properly with this branch. A `topology.subprocess.timeout` setting I had in `config.json` was not being applied when deploying...
I'm reopening this because if you're not seeing acks and fails work when running in local mode (with `sparse run`), there's something wrong somewhere (although it may be on the...
@fedelemantuano Just to confirm, you are seeing this issue when running your topology with `sparse run`, correct? It is not recommended that you Storm topologies in production in local mode...
@ManofWax Technically, it's not really the entire topology that restarts. The Java worker process that communicates with your Python subprocesses restarts when any of the subprocesses exits. There is usually...