Josh Haile
Josh Haile
* Should we make a new configuration variable for the process cap? like e.g.: `max_processes_per_worker=4` * If not, should this implementation have a UI component? If its in the UI...
Okay thats do-able Getting a UI input that is configurable on the fly, after deployment/installation, would take extra effort. What do you think, @galenatjpl ?
Alright, thanks for the response. Will get start on this soon. If any requirements change, let me know
Alright, the coordination for avoiding is Starvation is what I'm working on per `ProcessCounter` . Thanks for the added detail @galenatjpl
Hi @Gillingham , thanks for feedback on this issue. I believe the problem you're having with the "cws-config.props" reverting is with the cws re-runs. One of the current functions of...
@Gillingham I did a few rounds of reconfig and recreated your case. The right approach to preserving your `cws-config.props` file while passing it to configure.sh on multiple runs is to...
Hi @Gillingham , i'll be updating the Wiki https://wiki.jpl.nasa.gov/display/cws/CWS+Platform+Prerequisites before CWSv2.2 release with the new config details and features. It should be up by this coming Monday. And I agree...
Update: https://github.com/NASA-AMMOS/common-workflow-service/pull/97
Fix: https://github.com/NASA-AMMOS/common-workflow-service/pull/106