xinyiZzz opened a new pull request, #20450:
URL: https://github.com/apache/doris/pull/20450
## Proposed changes
Issue Number: close #xxx
1. Only switch to bthread local when modifying the mem tracker in the thread
context. No longer switches to bthread local by default when bthread starts
2. mem tracker increases brpc `IOBufBlockMemory` memory
3. remove thread mem tracker metrics
core stack:
```
#0 __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50
#1 0x00007f9220937859 in __GI_abort () at abort.c:79
#2 0x000056079b8365e9 in ?? ()
#3 0x000056079b82bbfd in google::LogMessage::Fail() ()
#4 0x000056079b82e139 in google::LogMessage::SendToLog() ()
#5 0x000056079b82b766 in google::LogMessage::Flush() ()
#6 0x000056079b82e7a9 in google::LogMessageFatal::~LogMessageFatal() ()
#7 0x000056079bff62af in bthread_setspecific ()
#8 0x00005607950e15db in doris::pthread_attach_bthread ()
at doris_master/doris/be/src/runtime/thread_context.h:219
#9 doris::thread_context ()
at doris_master/doris/be/src/runtime/thread_context.h:228
#10 0x00005607950e131c in doris_malloc (size=30504)
at doris_master/doris/be/src/runtime/memory/jemalloc_hook.cpp:44
#11 0x000056079e4b5ef8 in operator new (sz=30504) at
../../../../libstdc+-v3/libsupc+/new_op.cc:50
#12 0x000056079b82ade0 in google::LogMessage::Init(char const*, int, int,
void (google::LogMessage::*)()) ()
#13 0x000056079c1a6e60 in brpc::Socket::CheckHealth() ()
#14 0x000056079c1ae55b in brpc::HealthCheckTask::OnTriggeringTask(timespec*)
()
-Type <RET> for more, q to quit, c to continue without paging-
#15 0x000056079c1af61b in ?? ()
#16 0x000056079c009daf in bthread::TaskGroup::task_runner(long) ()
#17 0x000056079bff53e1 in bthread_make_fcontext ()
#18 0x0000000000000000 in ?? ()
```
## Further comments
If this is a relatively large or complex change, kick off the discussion at
[[email protected]](mailto:[email protected]) by explaining why you
chose the solution you did and what alternatives you considered, etc...
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
