-
Notifications
You must be signed in to change notification settings - Fork 6.6k
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
Fix buffer size for trace collection #21020
Fix buffer size for trace collection #21020
Conversation
BTW query profiler can profile itself (for example Real time profiler can measure how frequently CPU time profiler was active). This is somewhat useful property. |
I see, thanks. Okay, let's truncate the buffer size to 4K then. |
072521c
to
88ebfa2
Compare
88ebfa2
to
7525103
Compare
7525103
to
89c3119
Compare
@azat Do you know why fuzzer did not stop after first segfault? |
It should be because SIGSEGV handler does not call _exit, so when thread got SIGSEGV it just send information about the signal to the pipe, and the server will be terminated only once this message in pipe will be served, but this may take a while, in the meantime SIGSEGV in another handler may happen. |
But they are from different queries (check query_id) and fuzzer is sending queries sequentially. |
Yep, but the problem is that the first query failed with different error -
This is because fatal thread handler was called when the TCPHandler was sending totals:
And client will have 20 seconds to send other queries |
Changelog category (leave one):