-
Notifications
You must be signed in to change notification settings - Fork 523
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
runtime error with tsuru unit-remove #1204
Comments
@vmalaga can you see the tsuru log output. By default tsuru send log to syslog (/var/log/syslog) |
@vmalaga I think you found a bug in the latest release. The default scheduler isn't working anymore, this default scheduler isn't recommended for production environments but it should either be removed or remain working.
This will enable the segregate scheduler and should get you past this error. |
@cezarsa you're right, with the segregate scheduler there is not any problem. thanks |
@cezarsa I am testing the units scale and see that the segregate scheduler fails removing units from system. Now don't generate a runtime error, but the unit is not removed from pool
and at syslog i see that, but the node choosen to remove the unit is invalid
|
@vmalaga This was caused by another bug in the unit-remove scheduling algorithm, we'll release 0.11.1 probably later today and it will fix this issue. |
If I can help you testing any thing say me |
this issue is fixed since 0.11.1. @vmalaga can we close this issue? |
yes, sorry |
Hey all
after add some units to app, if I try to remove any unit, the tsr daemon crack with runtime error.
I send the trace at the tsr
The text was updated successfully, but these errors were encountered: