Skip to content
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

Tracing the reason of task launch failure #336

Closed
hanahmily opened this issue May 26, 2017 · 0 comments
Closed

Tracing the reason of task launch failure #336

hanahmily opened this issue May 26, 2017 · 0 comments

Comments

@hanahmily
Copy link
Contributor

Which version of Elastic-Job do you using?

2.1.2

Which feature you expected

When the task fails to launch, the framework gets a TASK_ERROR message. But this message does not contain the specific reasons for failure, it is difficult to locate the problem.

So add some details of the failure to the message body, such as exception message or java stack information, can solve this problems

hanahmily added a commit to Esjob-Cloud-DevOps/elastic-job that referenced this issue May 26, 2017
hanahmily pushed a commit to Esjob-Cloud-DevOps/elastic-job that referenced this issue May 26, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants