@marcj i discovered that current version is balancing requests bad
kz it always tries to found free worker the begining of the list
Marc J. Schmidt
@marcj
ohwe, what does bad mean?
kugu
@kugu
so first workers would be used much often then from bottom of the list
Marc J. Schmidt
@marcj
maybe because the first worker is fast as hell ? :P
kugu
@kugu
yeap
Marc J. Schmidt
@marcj
yeah thats normal, it means the worker hasn't much to do
kugu
@kugu
but anyway last worker is used only when all others is busy
Marc J. Schmidt
@marcj
yes, correctly
_
kugu
@kugu
so it means that first worker is restarting more often)
don't think this is the best behavior)
Marc J. Schmidt
@marcj
I actually like it more, because it saves memory :)
Franz Liedke
@franzliedke
So how do I do debugging in PPM? I have some scenarios where requests just don't receive any response, and need to find out the reason....
Marc J. Schmidt
@marcj
you can use xdebug
place breakpoints
Franz Liedke
@franzliedke
@marcj Is there some kind of verbose console logging to at least see which part is hanging?
(e.g. worker 123 during request execution)
Marc J. Schmidt
@marcj
you can try to use -vv
try use --workers=1 which should make things simple
Martin Lonský
@visitek
zf2 is stable now :-)
i've pulled requst with setting null service into controller plugin.. still waiting for merge
Marc J. Schmidt
@marcj
they made a release?
I dont' get it
Martin Lonský
@visitek
it is in my fork of zend servicemanager
your version of zf2 is principiall
y wrong :-)
i'll fix it
Franz Liedke
@franzliedke
Does PPM swallow HTTP 500 responses from the workers?
(As in, replace them with a simpler message?)
Marc J. Schmidt
@marcj
from the workers? PPM sends everything waht the worker sends
Franz Liedke
@franzliedke
okay...
Franz Liedke
@franzliedke
Can we start tagging some releases? The dev-master dependency messes with our minimum-stability...
Marc J. Schmidt
@marcj
we still wait for react/http.
alexlis
@alexlis
hi
Martin Lonský
@visitek
Marc. do you havy any idea, how to say nginx balancer that pm is dead for new requests? We have more production pms balanced by nginx. When i want to deploy them i need deploy it step by step by without terminating processes incomming before..when it is ready to kill, any new request shouldnt come to it. thats mean: two instances: eg 16 workers are alive. while deploing there are only 8. without loosing any request/reaponse