[ https://issues.apache.org/jira/browse/IMPALA-4631?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17041407#comment-17041407 ]
Tim Armstrong commented on IMPALA-4631: --------------------------------------- I saw this again. This happened on a CentOS 6.4 vm on a m2-4xlarge ec2 instance. {noformat} F0217 02:10:47.921636 14885 runtime-profile-counters.h:572] 9945dfcfab2eb54c:1609788600000001] Check failed: offset_ >= -3 (-15 vs. -3) {noformat} > plan-fragment-executor.cc:518] Check failed: other_time <= total_time > (25999394 vs. 25999393) > --------------------------------------------------------------------------------------------- > > Key: IMPALA-4631 > URL: https://issues.apache.org/jira/browse/IMPALA-4631 > Project: IMPALA > Issue Type: Bug > Components: Backend > Affects Versions: Impala 2.8.0 > Reporter: Daniel Hecht > Priority: Major > Labels: flaky > > This dcheck occasionally fires: > {code} > impalad.FATAL:F1201 22:35:58.617157 30293 plan-fragment-executor.cc:518] > Check failed: other_time <= total_time (25999394 vs. 25999393) > {code} > I suspect the problem is with using floating point operations in places like > this: > {code} > timespec ts; > clock_gettime(OsInfo::fast_clock(), &ts); > return ts.tv_sec * 1e9 + ts.tv_nsec; > {code} > and because floating point doesn't distribute, and we can end up with > {noformat} c * (a + b) < c * a + c * b {noformat} which is effectively what > the dcheck does. -- This message was sent by Atlassian Jira (v8.3.4#803005) --------------------------------------------------------------------- To unsubscribe, e-mail: issues-all-unsubscr...@impala.apache.org For additional commands, e-mail: issues-all-h...@impala.apache.org