You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@beam.apache.org by "ASF GitHub Bot (Jira)" <ji...@apache.org> on 2022/05/06 22:15:00 UTC

[jira] [Work logged] (BEAM-13666) Stuck inventory jobs should be cancelled and rescheduled for next run

     [ https://issues.apache.org/jira/browse/BEAM-13666?focusedWorklogId=767436&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-767436 ]

ASF GitHub Bot logged work on BEAM-13666:
-----------------------------------------

                Author: ASF GitHub Bot
            Created on: 06/May/22 22:14
            Start Date: 06/May/22 22:14
    Worklog Time Spent: 10m 
      Work Description: elink21 opened a new pull request, #17582:
URL: https://github.com/apache/beam/pull/17582

   As Valentyn mentioned on the Jira Ticket, if a worker is marked as temporarily offline and an Inventory job started during that process, then the job is going to stuck and it's necessary to cancel it manually and run it again later, even if the worker is back online it can not retake the job. 
   
   The reason behind that was the eligibility option set in the code, [Eligibility options ](https://jenkinsci.github.io/job-dsl-plugin/#path/javaposse.jobdsl.dsl.helpers.BuildParametersContext.nodeParam-eligibility), by changing it to all nodes the job will continue it's execution after the worker is online again.
   
   This change doesn't affect the stablished workers-job mapping, as the allowed nodes and default node options are already set.
   
   ------------------------
   
   Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:
   
    - [ ] [**Choose reviewer(s)**](https://beam.apache.org/contribute/#make-your-change) and mention them in a comment (`R: @username`).
    - [ ] Format the pull request title like `[BEAM-XXX] Fixes bug in ApproximateQuantiles`, where you replace `BEAM-XXX` with the appropriate JIRA issue, if applicable. This will automatically link the pull request to the issue.
    - [ ] Update `CHANGES.md` with noteworthy changes.
    - [ ] If this contribution is large, please file an Apache [Individual Contributor License Agreement](https://www.apache.org/licenses/icla.pdf).
   
   See the [Contributor Guide](https://beam.apache.org/contribute) for more tips on [how to make review process smoother](https://beam.apache.org/contribute/#make-reviewers-job-easier).
   
   To check the build health, please visit [https://github.com/apache/beam/blob/master/.test-infra/BUILD_STATUS.md](https://github.com/apache/beam/blob/master/.test-infra/BUILD_STATUS.md)
   
   GitHub Actions Tests Status (on master branch)
   ------------------------------------------------------------------------------------------------
   [![Build python source distribution and wheels](https://github.com/apache/beam/workflows/Build%20python%20source%20distribution%20and%20wheels/badge.svg?branch=master&event=schedule)](https://github.com/apache/beam/actions?query=workflow%3A%22Build+python+source+distribution+and+wheels%22+branch%3Amaster+event%3Aschedule)
   [![Python tests](https://github.com/apache/beam/workflows/Python%20tests/badge.svg?branch=master&event=schedule)](https://github.com/apache/beam/actions?query=workflow%3A%22Python+Tests%22+branch%3Amaster+event%3Aschedule)
   [![Java tests](https://github.com/apache/beam/workflows/Java%20Tests/badge.svg?branch=master&event=schedule)](https://github.com/apache/beam/actions?query=workflow%3A%22Java+Tests%22+branch%3Amaster+event%3Aschedule)
   
   See [CI.md](https://github.com/apache/beam/blob/master/CI.md) for more information about GitHub Actions CI.
   




Issue Time Tracking
-------------------

            Worklog Id:     (was: 767436)
    Remaining Estimate: 0h
            Time Spent: 10m

> Stuck inventory jobs should be cancelled and rescheduled for next run
> ---------------------------------------------------------------------
>
>                 Key: BEAM-13666
>                 URL: https://issues.apache.org/jira/browse/BEAM-13666
>             Project: Beam
>          Issue Type: Improvement
>          Components: testing
>            Reporter: Valentyn Tymofieiev
>            Assignee: Elias Edgardo Segundo Antonio
>            Priority: P2
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> When we take a jenkins node offline and then back online, sometimes an inventory job can get stuck, and we need to unblock it manually.
> Ideally, Jenkins should cancel the stuck jobs. There is some mechanism where we can cancel Jenkins Jobs for PRs that had new commits. Perhaps it can be reused here.
> Context: https://lists.apache.org/thread/5pzj6pycw1lo15v66p7c2gzy4xh44bjx



--
This message was sent by Atlassian Jira
(v8.20.7#820007)