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 incorrect entryId in warn log when reading entry from tiered storage #14685

Merged

Conversation

hangc0276
Copy link
Contributor

Motivation

When read offload data failed, it prints a warn log. However, the actual read entryId doesn't print correctly, which will makes hard to debug.

WARN  org.apache.bookkeeper.mledger.offload.jcloud.impl.BlobStoreBackedReadHandleImpl - Read an unexpected entry id [] which is smaller than the next expected entry id 49648, seeking to the right position

Modification

  1. Print correct actual entryId

@github-actions
Copy link

@hangc0276:Thanks for your contribution. For this PR, do we need to update docs?
(The PR template contains info about doc, which helps others know more about the changes. Can you provide doc-related info in this and future PR descriptions? Thanks)

@Anonymitaet
Copy link
Member

@hangc0276 seems that we do not update docs for this PR?

@hangc0276 hangc0276 added the doc-not-needed Your PR changes do not impact docs label Mar 15, 2022
@hangc0276
Copy link
Contributor Author

@hangc0276 seems that we do not update docs for this PR?

@Anonymitaet Yes, it doesn't need doc updates.

@github-actions
Copy link

@hangc0276:Thanks for providing doc info!

@michaeljmarshall michaeljmarshall added type/cleanup Code or doc cleanups e.g. remove the outdated documentation or remove the code no longer in use area/tieredstorage labels Mar 15, 2022
@hezhangjian hezhangjian merged commit bcba273 into apache:master Mar 15, 2022
codelipenghui pushed a commit that referenced this pull request Mar 18, 2022
### Motivation
When read offload data failed, it prints a warn log. However, the actual read entryId doesn't print correctly, which will makes hard to debug.
```
WARN  org.apache.bookkeeper.mledger.offload.jcloud.impl.BlobStoreBackedReadHandleImpl - Read an unexpected entry id [] which is smaller than the next expected entry id 49648, seeking to the right position
```

### Modification
1. Print correct actual entryId

(cherry picked from commit bcba273)
@codelipenghui codelipenghui added the cherry-picked/branch-2.9 Archived: 2.9 is end of life label Mar 18, 2022
codelipenghui pushed a commit that referenced this pull request Mar 18, 2022
### Motivation
When read offload data failed, it prints a warn log. However, the actual read entryId doesn't print correctly, which will makes hard to debug.
```
WARN  org.apache.bookkeeper.mledger.offload.jcloud.impl.BlobStoreBackedReadHandleImpl - Read an unexpected entry id [] which is smaller than the next expected entry id 49648, seeking to the right position
```

### Modification
1. Print correct actual entryId

(cherry picked from commit bcba273)
@codelipenghui codelipenghui added the cherry-picked/branch-2.8 Archived: 2.8 is end of life label Mar 18, 2022
Nicklee007 pushed a commit to Nicklee007/pulsar that referenced this pull request Apr 20, 2022
### Motivation
When read offload data failed, it prints a warn log. However, the actual read entryId doesn't print correctly, which will makes hard to debug.
```
WARN  org.apache.bookkeeper.mledger.offload.jcloud.impl.BlobStoreBackedReadHandleImpl - Read an unexpected entry id [] which is smaller than the next expected entry id 49648, seeking to the right position
```

### Modification
1. Print correct actual entryId
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/broker area/tieredstorage cherry-picked/branch-2.8 Archived: 2.8 is end of life cherry-picked/branch-2.9 Archived: 2.9 is end of life doc-not-needed Your PR changes do not impact docs release/2.8.4 release/2.9.3 type/cleanup Code or doc cleanups e.g. remove the outdated documentation or remove the code no longer in use
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

8 participants