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][ml] No rollover inactive ledgers when metadata service invalid #22284

Merged
merged 2 commits into from
Mar 30, 2024

Conversation

AnonHxy
Copy link
Contributor

@AnonHxy AnonHxy commented Mar 16, 2024

Motivation

We should not rollover inactive ledgers when metadata service is invailable.

Modifications

Checking metadata service is vailable when schedule checkInactiveLedgerAndRollOver

Verifying this change

  • Make sure that the change passes the CI checks.
  • Add UT
    org.apache.bookkeeper.mledger.impl.ManagedLedgerTest#testDontRollOverInactiveLedgersWhenMetadataServiceInvalid

Documentation

  • doc
  • doc-required
  • doc-not-needed
  • doc-complete

Matching PR in forked repository

PR in forked repository:

AnonHxy#49

@codecov-commenter
Copy link

codecov-commenter commented Mar 16, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 73.73%. Comparing base (bbc6224) to head (2cf7ad7).
Report is 107 commits behind head on master.

Additional details and impacted files

Impacted file tree graph

@@             Coverage Diff              @@
##             master   #22284      +/-   ##
============================================
+ Coverage     73.57%   73.73%   +0.15%     
+ Complexity    32624    32297     -327     
============================================
  Files          1877     1885       +8     
  Lines        139502   139867     +365     
  Branches      15299    15320      +21     
============================================
+ Hits         102638   103129     +491     
+ Misses        28908    28796     -112     
+ Partials       7956     7942      -14     
Flag Coverage Δ
inttests 27.03% <0.00%> (+2.44%) ⬆️
systests 24.51% <0.00%> (+0.19%) ⬆️
unittests 72.99% <100.00%> (+0.14%) ⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

Files Coverage Δ
...che/bookkeeper/mledger/impl/ManagedLedgerImpl.java 80.77% <100.00%> (+0.11%) ⬆️

... and 180 files with indirect coverage changes

@AnonHxy AnonHxy changed the title [fix][ml] No rollover inactive ledgers when metadata service is invailable [fix][ml] No rollover inactive ledgers when metadata service invalid Mar 24, 2024
@AnonHxy AnonHxy force-pushed the fix_ledger_rollover branch from b15f7c7 to 71fec57 Compare March 24, 2024 06:12
@AnonHxy
Copy link
Contributor Author

AnonHxy commented Mar 24, 2024

/pulsarbot run-failure-checks

Copy link
Member

@lhotari lhotari left a comment

Choose a reason for hiding this comment

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

LGTM

@AnonHxy AnonHxy force-pushed the fix_ledger_rollover branch from 71fec57 to 2cf7ad7 Compare March 30, 2024 05:15
@AnonHxy AnonHxy merged commit 9529738 into apache:master Mar 30, 2024
50 checks passed
Technoboy- pushed a commit to Technoboy-/pulsar that referenced this pull request Apr 1, 2024
…pache#22284)

### Motivation

We should not rollover inactive ledgers when metadata service is invailable.

### Modifications

Checking metadata service is vailable when schedule `checkInactiveLedgerAndRollOver`
Technoboy- pushed a commit that referenced this pull request Apr 3, 2024
…22284)

### Motivation

We should not rollover inactive ledgers when metadata service is invailable.

### Modifications

Checking metadata service is vailable when schedule `checkInactiveLedgerAndRollOver`
Technoboy- pushed a commit that referenced this pull request Apr 8, 2024
…22284)

### Motivation

We should not rollover inactive ledgers when metadata service is invailable.

### Modifications

Checking metadata service is vailable when schedule `checkInactiveLedgerAndRollOver`
mukesh-ctds pushed a commit to datastax/pulsar that referenced this pull request Apr 15, 2024
…pache#22284)

### Motivation

We should not rollover inactive ledgers when metadata service is invailable.

### Modifications

Checking metadata service is vailable when schedule `checkInactiveLedgerAndRollOver`

(cherry picked from commit b9bf0a8)
mukesh-ctds pushed a commit to datastax/pulsar that referenced this pull request Apr 17, 2024
…pache#22284)

### Motivation

We should not rollover inactive ledgers when metadata service is invailable.

### Modifications

Checking metadata service is vailable when schedule `checkInactiveLedgerAndRollOver`

(cherry picked from commit b9bf0a8)
mukesh-ctds pushed a commit to datastax/pulsar that referenced this pull request Apr 17, 2024
…pache#22284)

### Motivation

We should not rollover inactive ledgers when metadata service is invailable.

### Modifications

Checking metadata service is vailable when schedule `checkInactiveLedgerAndRollOver`

(cherry picked from commit b9bf0a8)
mukesh-ctds pushed a commit to datastax/pulsar that referenced this pull request Apr 19, 2024
…pache#22284)

### Motivation

We should not rollover inactive ledgers when metadata service is invailable.

### Modifications

Checking metadata service is vailable when schedule `checkInactiveLedgerAndRollOver`

(cherry picked from commit b9bf0a8)
srinath-ctds pushed a commit to datastax/pulsar that referenced this pull request Apr 23, 2024
…pache#22284)

### Motivation

We should not rollover inactive ledgers when metadata service is invailable.

### Modifications

Checking metadata service is vailable when schedule `checkInactiveLedgerAndRollOver`

(cherry picked from commit b9bf0a8)
hanmz pushed a commit to hanmz/pulsar that referenced this pull request Feb 12, 2025
…pache#22284)

### Motivation

We should not rollover inactive ledgers when metadata service is invailable.

### Modifications

Checking metadata service is vailable when schedule `checkInactiveLedgerAndRollOver`
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.

7 participants