[
https://issues.apache.org/jira/browse/IMPALA-10160?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17697702#comment-17697702
]
YifanZhang commented on IMPALA-10160:
-------------------------------------
In our K8S environment, both kernel stack and user stack can't be printed:
{code:java}
W0307 16:26:44.019208 399 kernel_stack_watchdog.cc:198] Thread 545 stuck at
/data/apache-impala/be/src/kudu/rpc/outbound_call.cc:273 for 256ms:
Kernel stack:
(could not read kernel stack)
User stack:
<Not implemented: unable to take thread stack: signal handler unavailable>
{code}
> kernel_stack_watchdog cannot print user stack
> ---------------------------------------------
>
> Key: IMPALA-10160
> URL: https://issues.apache.org/jira/browse/IMPALA-10160
> Project: IMPALA
> Issue Type: Bug
> Components: Backend
> Reporter: Sahil Takiar
> Priority: Major
> Labels: supportability
>
> I've seen this a few times now, the kernel_stack_watchdog is used in a few
> places in the KRPC code and it prints out the kernel + user stack whenever a
> thread is stuck in some method call for too long. The issue is that the user
> stack does not get printed:
> {code}
> W0908 17:15:00.365721 6605 kernel_stack_watchdog.cc:198] Thread 6612 stuck
> at outbound_call.cc:273 for 120ms:
> Kernel stack:
> [<ffffffff810f5126>] futex_wait_queue_me+0xc6/0x130
> [<ffffffff810f5deb>] futex_wait+0x17b/0x280
> [<ffffffff810f7b26>] do_futex+0x106/0x5a0
> [<ffffffff810f8040>] SyS_futex+0x80/0x180
> [<ffffffff816b4fc9>] system_call_fastpath+0x16/0x1b
> [<ffffffffffffffff>] 0xffffffffffffffff
> User stack:
> <Not implemented: unable to take thread stack: signal handler unavailable>
> {code}
> It says that the signal handler of taking the thread stack is unavailable.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
