The applys count of memory trace keeps growing #15371
Labels
affects-6.1
affects-6.2
affects-6.3
affects-6.4
affects-6.5
affects-6.6
affects-7.0
affects-7.1
affects-7.2
affects-7.3
severity/minor
type/bug
Type: Issue - Confirmed a bug
Comments
Connor1996
added a commit
to Connor1996/tikv
that referenced
this issue
Aug 21, 2023
Signed-off-by: Connor1996 <zbk602423539@gmail.com>
ti-chi-bot bot
pushed a commit
that referenced
this issue
Aug 23, 2023
close #15371 Fix incorrect raftstore applys memory trace. When performing dropping apply fsm, it should reset the memory trace to zero instead of calling `update_memory_trace`, otherwise it would record extra footage of the interior vector capacity. Signed-off-by: Connor1996 <zbk602423539@gmail.com> Co-authored-by: tonyxuqqi <tonyxuqi@outlook.com>
Connor1996
added a commit
to Connor1996/tikv
that referenced
this issue
Aug 25, 2023
close tikv#15371 Fix incorrect raftstore applys memory trace. When performing dropping apply fsm, it should reset the memory trace to zero instead of calling `update_memory_trace`, otherwise it would record extra footage of the interior vector capacity. Signed-off-by: Connor1996 <zbk602423539@gmail.com> Co-authored-by: tonyxuqqi <tonyxuqi@outlook.com>
|
/cherry-pick release-7.1 |
ti-chi-bot
pushed a commit
to ti-chi-bot/tikv
that referenced
this issue
Oct 12, 2023
Signed-off-by: Connor1996 <zbk602423539@gmail.com>
ti-chi-bot bot
added a commit
that referenced
this issue
Oct 12, 2023
close #15371 Fix incorrect raftstore applys memory trace. When performing dropping apply fsm, it should reset the memory trace to zero instead of calling `update_memory_trace`, otherwise it would record extra footage of the interior vector capacity. Signed-off-by: Connor1996 <zbk602423539@gmail.com> Co-authored-by: Connor1996 <zbk602423539@gmail.com> Co-authored-by: ti-chi-bot[bot] <108142056+ti-chi-bot[bot]@users.noreply.github.com>
ti-chi-bot
pushed a commit
to ti-chi-bot/tikv
that referenced
this issue
Nov 27, 2023
Signed-off-by: Connor1996 <zbk602423539@gmail.com>
ti-chi-bot bot
added a commit
that referenced
this issue
Nov 27, 2023
close #15371 Fix incorrect raftstore applys memory trace. When performing dropping apply fsm, it should reset the memory trace to zero instead of calling `update_memory_trace`, otherwise it would record extra footage of the interior vector capacity. Signed-off-by: Connor1996 <zbk602423539@gmail.com> Co-authored-by: Connor1996 <zbk602423539@gmail.com> Co-authored-by: ti-chi-bot[bot] <108142056+ti-chi-bot[bot]@users.noreply.github.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Bug Report
What version of TiKV are you using?
master
What operating system and CPU are you using?
Not related
Steps to reproduce
What did you expect?
The applys count of memory trace keeps growing when merging and spliting regions back and forth.
What did happened?
The text was updated successfully, but these errors were encountered: