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.

Sign up for GitHub

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

Jump to bottom

bug: backup compatible bug in v1.10 #17923

Closed
MrCroxx opened this issue Aug 5, 2024 · 1 comment
Closed

bug: backup compatible bug in v1.10 #17923

MrCroxx opened this issue Aug 5, 2024 · 1 comment
Labels
type/bug Something isn't working
Milestone
release-2.0

Comments

@MrCroxx
Copy link
Contributor

MrCroxx commented Aug 5, 2024

Describe the bug

When upgrading to v1.10, the meta node panics because of missing fields when parsing the manifest of backups.

Error message/log

thread 'rw-main' panicked at src/meta/node/src/server.rs:337:10:
Unable to start leader services: Encoding error: missing field `state_table_info` at line 1 column 77013

To Reproduce

No response

Expected behavior

No response

How did you deploy RisingWave?

No response

The version of RisingWave

No response

Additional context

No response
@MrCroxx MrCroxx added the type/bug Something isn't working label Aug 5, 2024
@github-actions github-actions bot added this to the release-1.11 milestone Aug 5, 2024
@hzxa21
Copy link
Collaborator

hzxa21 commented Aug 9, 2024

Duplicated with #17926.

@hzxa21 hzxa21 closed this as completed Aug 9, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
type/bug Something isn't working
Projects
None yet
Milestone
release-2.0
Development

No branches or pull requests
2 participants
@hzxa21 @MrCroxx