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

improve poll logging #2719

Merged
merged 3 commits into from
Jul 24, 2018
Merged

Conversation

oliver-sanders
Copy link
Member

  • Improve the readability of poll messages in the job activity log.
  • Add a new metric batch_sys_call_no_lines which provides the number of lines of stdout output received from the batch system call (e.g. qstat for pbs) for help with debugging polling issues.

@oliver-sanders oliver-sanders self-assigned this Jul 10, 2018
@hjoliver
Copy link
Member

Can you explain why the "number of lines" of batch sys stdout is helpful here?

@oliver-sanders
Copy link
Member Author

We've had an interesting episode here with running tasks being marked as failed. We can't quite fathom how this has happened, our best bet is that qstat is returning a null stdout or something to that effect. As we are using negative rather than positive checking (i.e. check something isn't there rather than check that it is) in this event all tasks which are presumed to be running would be marked as failed. Later on when the still happily running job completes and cylc message sends back the "I'm done" message the task gets bumped from failed to succeeded.

We were hoping that if this were to happen again knowing whether qstat returned any output might help to determine where this bug lies.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants