Skip to content

Per Replica Throttle -- 3rd: pending messages with load/recovery test#3

Open
kaisun2000 wants to merge 1 commit into
throttle_p2from
throttle_p3
Open

Per Replica Throttle -- 3rd: pending messages with load/recovery test#3
kaisun2000 wants to merge 1 commit into
throttle_p2from
throttle_p3

Conversation

@kaisun2000

@kaisun2000 kaisun2000 commented Jan 29, 2021

Copy link
Copy Markdown
Owner

Issues

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

enhance apache#343; pending messages with load/recovery tests

Description

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

(Write a concise description including what, why, how)

Tests

  • The following tests are written for this issue:

(List the names of added unit/integration tests)

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

(Before CI test pass, please copy & paste the result of "mvn test")

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)

@kaisun2000 kaisun2000 changed the title Per Replica Throttle -- 3rd: pending messages with load/recovery base case test Per Replica Throttle -- 3rd: pending messages with load/recovery test Jan 29, 2021
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.

1 participant