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

[Bug]: The expired tombstone object has not been GC #16101

Closed
1 task done
LeftHandCold opened this issue May 14, 2024 · 0 comments
Closed
1 task done

[Bug]: The expired tombstone object has not been GC #16101

LeftHandCold opened this issue May 14, 2024 · 0 comments
Assignees
Labels
kind/bug Something isn't working severity/s0 Extreme impact: Cause the application to break down and seriously affect the use
Milestone

Comments

@LeftHandCold
Copy link
Contributor

Is there an existing issue for the same bug?

  • I have checked the existing issues.

Branch Name

1.2-dev

Commit ID

c6b036c

Other Environment Information

- Hardware parameters:
- OS type:
- Others:

Actual Behavior

The expired tombstone object has not been GC

Expected Behavior

No response

Steps to Reproduce

run mo-service 5 hour

Additional information

No response

@LeftHandCold LeftHandCold added kind/bug Something isn't working needs-triage labels May 14, 2024
@LeftHandCold LeftHandCold self-assigned this May 14, 2024
@LeftHandCold LeftHandCold added severity/s0 Extreme impact: Cause the application to break down and seriously affect the use and removed needs-triage labels May 14, 2024
@matrix-meow matrix-meow added this to the 1.2.0 milestone May 14, 2024
@LeftHandCold LeftHandCold modified the milestones: 1.2.0, 1.2.1 May 14, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Something isn't working severity/s0 Extreme impact: Cause the application to break down and seriously affect the use
Projects
None yet
Development

No branches or pull requests

2 participants