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

[Fix](job)Fix CAS competition failure leading to message publishing failure. #45018

Merged
merged 2 commits into from
Dec 5, 2024

Conversation

CalvinKirs
Copy link
Member

What problem does this PR solve?

tryPublish returns false in case of CAS competition failure or when the queue is full. Therefore, we need to first check if there is enough capacity and then use the publish method for serial publishing.

Release note

None

Check List (For Author)

  • Test

    • Regression test
    • Unit Test
    • Manual test (add detailed scripts or steps below)
    • No need to test or manual test. Explain why:
      • This is a refactor/code format and no logic has been changed.
      • Previous test can cover this change.
      • No code files have been changed.
      • Other reason
  • Behavior changed:

    • No.
    • Yes.
  • Does this need documentation?

    • No.
    • Yes.

Check List (For Reviewer who merge this PR)

  • Confirm the release note
  • Confirm test cases
  • Confirm document
  • Add branch pick label

@doris-robot
Copy link

Thank you for your contribution to Apache Doris.
Don't know what should be done next? See How to process your PR.

Please clearly describe your PR:

  1. What problem was fixed (it's best to include specific error reporting information). How it was fixed.
  2. Which behaviors were modified. What was the previous behavior, what is it now, why was it modified, and what possible impacts might there be.
  3. What features were added. Why was this function added?
  4. Which code was refactored and why was this part of the code refactored?
  5. Which functions were optimized and what is the difference before and after the optimization?

@CalvinKirs
Copy link
Member Author

run buildall

morrySnow
morrySnow previously approved these changes Dec 5, 2024
@morrySnow morrySnow added the p0_b label Dec 5, 2024
@github-actions github-actions bot added the approved Indicates a PR has been approved by one committer. label Dec 5, 2024
Copy link
Contributor

github-actions bot commented Dec 5, 2024

PR approved by at least one committer and no changes requested.

Copy link
Contributor

github-actions bot commented Dec 5, 2024

PR approved by anyone and no changes requested.

@CalvinKirs
Copy link
Member Author

run buildall

Copy link
Contributor

@zddr zddr left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@CalvinKirs
Copy link
Member Author

run feut

…ailure.

 tryPublish returns false in case of CAS competition failure or when the queue is full. Therefore, we need to first check if there is enough capacity and then use the publish method for serial publishing.
@CalvinKirs CalvinKirs force-pushed the master-disruptor-sizes branch from d638637 to 85028e2 Compare December 5, 2024 04:33
@github-actions github-actions bot removed the approved Indicates a PR has been approved by one committer. label Dec 5, 2024
@CalvinKirs
Copy link
Member Author

run buildall

@CalvinKirs CalvinKirs force-pushed the master-disruptor-sizes branch from dc477f9 to f7e26af Compare December 5, 2024 04:36
@CalvinKirs
Copy link
Member Author

run buildall

@github-actions github-actions bot added the approved Indicates a PR has been approved by one committer. label Dec 5, 2024
Copy link
Contributor

github-actions bot commented Dec 5, 2024

PR approved by at least one committer and no changes requested.

@CalvinKirs CalvinKirs merged commit c477fd1 into apache:master Dec 5, 2024
22 of 23 checks passed
@CalvinKirs CalvinKirs deleted the master-disruptor-sizes branch December 5, 2024 06:06
github-actions bot pushed a commit that referenced this pull request Dec 5, 2024
…ailure. (#45018)

### What problem does this PR solve?

**tryPublish** returns false in case of CAS competition failure or when
the queue is full. Therefore, we need to first check if there is enough
capacity and then use the **publish** method for serial publishing.
github-actions bot pushed a commit that referenced this pull request Dec 5, 2024
…ailure. (#45018)

### What problem does this PR solve?

**tryPublish** returns false in case of CAS competition failure or when
the queue is full. Therefore, we need to first check if there is enough
capacity and then use the **publish** method for serial publishing.
yiguolei pushed a commit that referenced this pull request Dec 6, 2024
…publishing failure. #45018 (#45030)

Cherry-picked from #45018

Co-authored-by: Calvin Kirs <[email protected]>
morningman pushed a commit that referenced this pull request Dec 8, 2024
…publishing failure. #45018 (#45029)

Cherry-picked from #45018

Co-authored-by: Calvin Kirs <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by one committer. dev/2.1.8-merged dev/3.0.4-merged p0_b reviewed
Projects
None yet
Development

Successfully merging this pull request may close these issues.

7 participants