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

Can't cleanup overlapped ranges due to out-or-order keys #11673

Closed
tabokie opened this issue Dec 17, 2021 · 1 comment
Closed

Can't cleanup overlapped ranges due to out-or-order keys #11673

tabokie opened this issue Dec 17, 2021 · 1 comment
Labels
severity/major type/bug Type: Issue - Confirmed a bug

Comments

@tabokie
Copy link
Member

tabokie commented Dec 17, 2021

Bug Report

What version of TiKV are you using?

v5.2.2

What operating system and CPU are you using?

N/A

Steps to reproduce

Internal issue: https://internal.pingcap.net/jira/browse/ONCALL-4226

What did you expect?

What did happened?

failed to cleanup stale range: Keys must be added in order.

Workaround

Disable deletion by SST writer: raftstore.use-delete-range = true

@tabokie tabokie changed the title Can't cleanup snapshots due to duplicate keys Can't cleanup overlapped ranges due to out-or-order keys Dec 17, 2021
@tabokie tabokie added severity/major type/bug Type: Issue - Confirmed a bug labels Dec 17, 2021
@tabokie
Copy link
Member Author

tabokie commented Jan 4, 2022

Suspect to be data corruption. The same TiKV node experienced out-of-order insertion during compaction later that week. We can't pursue the investigation because user already scale-in the problematic node.

Next time, it's advised to run the following commands to check whether the corruption is at memory level (block-cache) or persistent level:

for filename in /path/to/tikv/data/*.sst; do
  echo dump $filename && tikv-ctl ldb dump --path=$filename > /dev/null
done

@tabokie tabokie closed this as completed Jan 4, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
severity/major type/bug Type: Issue - Confirmed a bug
Projects
None yet
Development

No branches or pull requests

1 participant