Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Appearance settings

[Bug] Delete ConsumeQueue index before CommitLog in tiered storage #9371

Copy link
Copy link
@lizhimins

Description

@lizhimins
Issue body actions

Before Creating the Bug Report

  • I found a bug, not just asking a question, which should be created in GitHub Discussions.
  • I have searched the GitHub Issues and GitHub Discussions of this repository and believe that this is not a duplicate.
  • I have confirmed that this bug belongs to the current repository, not other repositories of RocketMQ.

Runtime platform environment

Linux 5.19

RocketMQ version

5.3.3

JDK Version

JDK11

Describe the Bug

在分级存储中,为了避免因读请求并发而导致空指针异常(NPE),应该先删除索引,然后再删除数据文件。

In tiered storage, to avoid null pointer exceptions (NPE) caused by concurrent read requests, the cq index should be deleted first, followed by the data files.

Steps to Reproduce

None

What Did You Expect to See?

read message normally

What Did You See Instead?

NPE

Additional Context

None

Reactions are currently unavailable

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions

      Morty Proxy This is a proxified and sanitized view of the page, visit original site.