You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Replace some boost to std in OlapScanNode.
This refactor seems solve the problem describe in #3929.
Because I found that BE will crash to calling `boost::condition_variable.notify_all()`.
But after upgrade to this, BE does not crash any more.
Replace some boost to std in OlapScanNode.
This refactor seems solve the problem describe in apache#3929.
Because I found that BE will crash to calling `boost::condition_variable.notify_all()`.
But after upgrade to this, BE does not crash any more.
Change-Id: I4baeeb6e76ecc751cb042796d52692d79432994e
wuyunfeng
pushed a commit
to wuyunfeng/incubator-doris
that referenced
this issue
Jun 30, 2020
Replace some boost to std in OlapScanNode.
This refactor seems solve the problem describe in apache#3929.
Because I found that BE will crash to calling `boost::condition_variable.notify_all()`.
But after upgrade to this, BE does not crash any more.
Describe the bug
BE crash occasionally and
be.out
shows:The reason is that when trying to lock a mutex, the assertion failed at
mutex->__data.__owner == 0
. It expected__owner == 0
, which is not.But when I look into the core dump file, the
__owner
field of that mutex is 0.That mutex is a internal mutex of
boost::condition_variable
. I have no idea why.The text was updated successfully, but these errors were encountered: