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

region_requst: add req info in flashback region error #852

Closed
wants to merge 2 commits into from

Conversation

Defined2014
Copy link
Contributor

add more log for flashback when it meets error, ref pingcap/tidb#43673

Signed-off-by: Jason Mo <mohangjie1995@gmail.com>
@@ -1752,6 +1752,9 @@ func (s *RegionRequestSender) onRegionError(
return true, nil
}
}
logutil.BgLogger().Error("Region is in flashback progress",
zap.Stringer("req", req),
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm inclined to contain these info inside the returned error, also consider the req can be nil.

Also, req.String() return weird things that no meaningful information is inside it. Maybe we should format some key fields of it.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Updated.

@you06
Copy link
Contributor

you06 commented Jun 29, 2023

@Defined2014 I suggest to attach the addtional info like this:
https://github.com/tikv/client-go/compare/master...you06:client-go:add-log?expand=1

@Defined2014
Copy link
Contributor Author

Defined2014 commented Jun 29, 2023

@Defined2014 I suggest to attach the addtional info like this: https://github.com/tikv/client-go/compare/master...you06:client-go:add-log?expand=1

ok. I found that we already have debug log in for this part, maybe we could try open debug log firstly.

And not sure return such internal information in Error Msg is good or not. It's useless for user.

@you06
Copy link
Contributor

you06 commented Jun 29, 2023

ok. I found that we already have debug log in for this part, maybe we could try open debug log firstly.

Debug mode print too many logs...

Signed-off-by: Jason Mo <mohangjie1995@gmail.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants