kmemcache无响应
Closed this issue · 1 comments
millken commented
准备测试一下插入1K万数据的性能,不知怎么搞的,请求服务端都没有回应了,好像被阻塞了。
INFO: task kmcworker2:6286 blocked for more than 120 seconds.
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
kmcworker2 D 0000000000000000 0 6286 2 0x00000000
ffff8800acec3b50 0000000000000046 ffff8800acec3ab0 ffffffff814ec71b
ffff8800acec3ae0 ffffffff81419fde ffff8801fdd05c00 0000000000000026
ffff88001f9e45f8 ffff8800acec3fd8 000000000000fb88 ffff88001f9e45f8
Call Trace:
[<ffffffff814ec71b>] ? _spin_unlock_bh+0x1b/0x20
[<ffffffff81419fde>] ? release_sock+0xce/0xe0
[<ffffffff814eaac5>] schedule_timeout+0x215/0x2e0
[<ffffffff81416b03>] ? sock_sendmsg+0x123/0x150
[<ffffffff814ea743>] wait_for_common+0x123/0x180
[<ffffffff8105fa40>] ? default_wake_function+0x0/0x20
[<ffffffff814ea85d>] wait_for_completion+0x1d/0x20
[<ffffffff8108bc53>] __cancel_work_timer+0x1b3/0x1e0
[<ffffffff8108b5a0>] ? wq_barrier_func+0x0/0x20
[<ffffffff8108bcb0>] cancel_work_sync+0x10/0x20
[<ffffffffa056bf6d>] update_event+0xad/0xe0 [kmemcache]
[<ffffffffa0573043>] mc_worker_machine+0xc3/0xea0 [kmemcache]
[<ffffffffa056adf0>] ? mc_conn_work+0x0/0x40 [kmemcache]
[<ffffffffa056ae10>] mc_conn_work+0x20/0x40 [kmemcache]
[<ffffffff8108b120>] worker_thread+0x170/0x2a0
[<ffffffff81090990>] ? autoremove_wake_function+0x0/0x40
[<ffffffff8108afb0>] ? worker_thread+0x0/0x2a0
[<ffffffff81090626>] kthread+0x96/0xa0
[<ffffffff8100c0ca>] child_rip+0xa/0x20
[<ffffffff81090590>] ? kthread+0x0/0xa0
[<ffffffff8100c0c0>] ? child_rip+0x0/0x20
INFO: task kmcworker3:6287 blocked for more than 120 seconds.
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
kmcworker3 D 0000000000000001 0 6287 2 0x00000000
ffff88001f973b50 0000000000000046 ffff88001f973ab0 ffffffff814ec71b
ffff88001f973ae0 ffffffff81419fde ffff8801b911d800 0000000000000026
ffff88001f9e5ab8 ffff88001f973fd8 000000000000fb88 ffff88001f9e5ab8
Call Trace:
[<ffffffff814ec71b>] ? _spin_unlock_bh+0x1b/0x20
[<ffffffff81419fde>] ? release_sock+0xce/0xe0
[<ffffffff814eaac5>] schedule_timeout+0x215/0x2e0
[<ffffffff81416b03>] ? sock_sendmsg+0x123/0x150
[<ffffffff814ea743>] wait_for_common+0x123/0x180
[<ffffffff8105fa40>] ? default_wake_function+0x0/0x20
[<ffffffff814ea85d>] wait_for_completion+0x1d/0x20
[<ffffffff8108bc53>] __cancel_work_timer+0x1b3/0x1e0
[<ffffffff8108b5a0>] ? wq_barrier_func+0x0/0x20
[<ffffffff8108bcb0>] cancel_work_sync+0x10/0x20
[<ffffffffa056bf6d>] update_event+0xad/0xe0 [kmemcache]
[<ffffffffa0573043>] mc_worker_machine+0xc3/0xea0 [kmemcache]
[<ffffffffa056adf0>] ? mc_conn_work+0x0/0x40 [kmemcache]
[<ffffffffa056ae10>] mc_conn_work+0x20/0x40 [kmemcache]
[<ffffffff8108b120>] worker_thread+0x170/0x2a0
[<ffffffff81090990>] ? autoremove_wake_function+0x0/0x40
[<ffffffff8108afb0>] ? worker_thread+0x0/0x2a0
[<ffffffff81090626>] kthread+0x96/0xa0
[<ffffffff8100c0ca>] child_rip+0xa/0x20
[<ffffffff81090590>] ? kthread+0x0/0xa0
[<ffffffff8100c0c0>] ? child_rip+0x0/0x20
jgli commented
工作者线程被阻塞了,现已修复