Skip to content

Conversation

@junkaixue
Copy link
Contributor

@junkaixue junkaixue commented Dec 5, 2024

Issues

  • [] My PR addresses the following Helix issues and references them in the PR description:

Description

  • Here are some details about my PR, including screenshots of any UI changes:

Once tag removed from instance for assignment purpose, current behavior is: 1) no new tagged tasks assigns to that instance.
2) drop the existing running tasks.

Change behavior for this:

  1. keep no new tagged tasks assigns to that instance. 2) let existing tasks running to complete

Test added.

Tests

  • The following tests are written for this issue:
    AfterClass: TestJobTagRemoval called.
    Shut down zookeeper at port 2183 in thread main
    Default Suite
    Total tests run: 1, Failures: 0, Skips: 0

  • The following is the result of the "mvn test" command on the appropriate module:

Changes that Break Backward Compatibility (Optional)

  • My PR contains changes that break backward compatibility or previous assumptions for certain methods or API. They include:

(Consider including all behavior changes for public methods or API. Also include these changes in merge description so that other developers are aware of these changes. This allows them to make relevant code changes in feature branches accounting for the new method/API behavior.)

Documentation (Optional)

  • In case of new functionality, my PR adds documentation in the following wiki page:

(Link the GitHub wiki you added)

Commits

  • My commits all reference appropriate Apache Helix GitHub issues in their subject lines. In addition, my commits follow the guidelines from "How to write a good git commit message":
    1. Subject is separated from body by a blank line
    2. Subject is limited to 50 characters (not including Jira issue reference)
    3. Subject does not end with a period
    4. Subject uses the imperative mood ("add", not "adding")
    5. Body wraps at 72 characters
    6. Body explains "what" and "why", not "how"

Code Quality

  • My diff has been formatted using helix-style.xml
    (helix-style-intellij.xml if IntelliJ IDE is used)

Once tag removed from instance for assignment purpose, current behavior is:
1) no new tagged tasks assigns to that instance.
2) drop the existing running tasks.

Change behavior for this:
1) keep no new tagged tasks assigns to that instance.
2) let existing tasks running to complete

Test added.
@junkaixue junkaixue merged commit 162dc29 into apache:master Dec 6, 2024
2 checks passed
@soumitra-st
Copy link

@junkaixue , when can we cut a Helix release?

zpinto pushed a commit to zpinto/helix that referenced this pull request Jan 22, 2025
Once tag removed from instance for assignment purpose, current behavior is:
1) no new tagged tasks assigns to that instance.
2) drop the existing running tasks.

Change behavior for this:
1) keep no new tagged tasks assigns to that instance.
2) let existing tasks running to complete

Test added.

Co-authored-by: Junkai <jxue@pinterest.com>
@somandal
Copy link

somandal commented May 8, 2025

@junkaixue @xyuanlu is it possible to hotfix this fix into a 1.3.* Helix version so that we can get this fix without the full 1.4+ Helix upgrade?

asf-gitbox-commits pushed a commit that referenced this pull request Jun 18, 2025
Once tag removed from instance for assignment purpose, current behavior is:
1) no new tagged tasks assigns to that instance.
2) drop the existing running tasks.

Change behavior for this:
1) keep no new tagged tasks assigns to that instance.
2) let existing tasks running to complete

Test added.

Co-authored-by: Junkai <jxue@pinterest.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants