Bug 981547
Summary: | Rack process of non-scaling ruby apps is killed after dumping its thread | ||
---|---|---|---|
Product: | OpenShift Online | Reporter: | Lei Zhang <lzhang> |
Component: | oc | Assignee: | Clayton Coleman <ccoleman> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | libra bugs <libra-bugs> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 2.x | CC: | ccoleman, mpatel, xtian |
Target Milestone: | --- | Keywords: | Reopened |
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2013-07-22 15:21:34 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Lei Zhang
2013-07-05 06:43:04 UTC
This is by design due to the change in how threaddump is done. It's documented here: https://github.com/openshift/origin-server/tree/master/cartridges/openshift-origin-cartridge-ruby#threaddump-command The last sentence "Note also that scaled applications are not supported by the threaddump command" of the document https://github.com/openshift/origin-server/tree/master/cartridges/openshift-origin-cartridge-ruby#threaddump-command. My question is that since the scaled app are not suppported by the threaddump command, why the scaled ruby app still can do threaddump and Rack process won't be terminated. Is it a bug for the scaled ruby app? Check on deven_3456 [rayzhang@rayzhang Work]$ rhc app create myruby19 ruby-1.9 -s Application Options ------------------- Namespace: rayzhang Cartridges: ruby-1.9 Gear Size: default Scaling: yes Creating application 'myruby19' ... done Application myruby19 was created. HAProxy instance is started Waiting for your DNS name to be available ... done Initialized empty Git repository in /home/rayzhang/Work/myruby19/.git/ Your application 'myruby19' is now available. URL: http://myruby19-rayzhang.dev.rhcloud.com/ SSH to: 51da223d3265fa0c4c000001.rhcloud.com Git remote: ssh://51da223d3265fa0c4c000001.rhcloud.com/~/git/myruby19.git/ Cloned to: /home/rayzhang/Work/myruby19 Run 'rhc show-app myruby19' for more details about your app. [rayzhang@rayzhang Work]$ rhc threaddump myruby19 Success The thread dump file will be available via: rhc tail myruby19 -f /var/lib/openshift/51da223d3265fa0c4c000001/ruby//logs//error_log-20130708-* -o '-n 250' Success The thread dump file will be available via: rhc tail myruby19 -f /var/lib/openshift/51da223d3265fa0c4c000001/ruby//logs//error_log-20130708-* -o '-n 250' [rayzhang@rayzhang Work]$ rhc threaddump myruby19 Success The thread dump file will be available via: rhc tail myruby19 -f /var/lib/openshift/51da223d3265fa0c4c000001/ruby//logs//error_log-20130708-* -o '-n 250' Success The thread dump file will be available via: rhc tail myruby19 -f /var/lib/openshift/51da223d3265fa0c4c000001/ruby//logs//error_log-20130708-* -o '-n 250' I think CLI is displaying the message indiscriminately. It might be reasonable to expect CLI to warn the user, in that case. Reassigning this ticket to CLI. Note: thread dump for scaling app has been updated to allow thread dump scaled up gears by ssh to the gears: https://bugzilla.redhat.com/show_bug.cgi?id=974933#c4 https://bugzilla.redhat.com/show_bug.cgi?id=974933#c7 Verified on INT(devenv_3470), for non-scalable ruby app, it's work by design. so move it verified. [rayzhang@rayzhang Work]$ rhc threaddump myruby18 Success The thread dump file will be available via: rhc tail myruby18 -f /var/lib/openshift/51dcf64b6cec0e6d6b0000c2/ruby//logs//error_log-20130710-* -o '-n 250' [rayzhang@rayzhang Work]$ rhc threaddump myruby18 Unable to detect application PID. Check the application's availability by accessing http://myruby18-rayzhang.int.rhcloud.com |