TiKV Crash, Please Assist in Troubleshooting the Cause, v7.1.3

This topic has been translated from a Chinese forum by GPT and might contain errors.

Original topic: tikv crash,请协助排查原因, v7.1.3

| username: TiDBer_KugsyWcF

[TiDB Usage Environment] Production Environment
[TiDB Version] 7.1.3
[Reproduction Path] Not clear how to reproduce
[Encountered Problem: Phenomenon and Impact] tikv crash
[Resource Configuration]

[Attachment: Screenshot/Log/Monitoring]

tikv error log:
tikv.log (4.5 KB)

| username: xfworld | Original post link

alloc::boxed::Box<F,A> as core::ops::function

There is too little memory to allocate, resulting in an OOM (Out of Memory) error.

| username: Jellybean | Original post link

Do other TiKV nodes in the cluster have similar issues? Is it an occasional phenomenon or a frequent event? Has the latency and QPS of business access been affected?

| username: 哈喽沃德 | Original post link

The configuration is too low.

| username: 路在何chu | Original post link

Is this related to memory?

| username: lemonade010 | Original post link

It’s probably a memory issue with std::thread::Builder::spawn_unchecked_::{{closure}}::{{closure}}.

| username: 双开门变频冰箱 | Original post link

Out of memory

| username: TiDBer_KugsyWcF | Original post link

But the memory did not spike.
At the same time, there are two “monotonic time jumped back” errors. I don’t know if they are related to this.

| username: xfworld | Original post link

Why does the time rollback issue occur? What’s this about? Let’s start another thread to discuss it.

| username: TiDBer_KugsyWcF | Original post link

Is it possible that this issue is caused by a time rollback?

| username: system | Original post link

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.