[
https://issues.apache.org/jira/browse/IMPALA-13278?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17871497#comment-17871497
]
Quanlong Huang edited comment on IMPALA-13278 at 8/7/24 12:46 AM:
------------------------------------------------------------------
Got the query in the logs:
{code:sql}
I0805 00:14:06.090651 775524 Frontend.java:2182]
4d4e5d4e693e5f9f:d7b795e200000000] Analyzing query: SELECT count(*) from
hadoop_catalog_test_external
where event_time > to_timestamp('2020-01-01 09:00:00','yyyy-MM-dd HH:mm:ss')
db: functional_parquet{code}
The test is
{code}
query_test.test_scanners.TestIceberg.test_iceberg_query[protocol: beeswax |
exec_option: {'test_replan': 1, 'batch_size': 0, 'num_nodes': 0,
'disable_codegen_rows_threshold': 0, 'disable_codegen': True, 'abort_on_error':
1, 'debug_action': '-1:OPEN:[email protected]',
'exec_single_node_rows_threshold': 0} | table_format: parquet/none]{code}
was (Author: stiga-huang):
Got the query in the logs:
{noformat}
I0805 00:14:06.090651 775524 Frontend.java:2182]
4d4e5d4e693e5f9f:d7b795e200000000] Analyzing query: SELECT count(*) from
hadoop_catalog_test_external
where event_time > to_timestamp('2020-01-01 09:00:00','yyyy-MM-dd HH:mm:ss')
db: functional_parquet{noformat}
> DCHECK for monotonic clock failed
> ---------------------------------
>
> Key: IMPALA-13278
> URL: https://issues.apache.org/jira/browse/IMPALA-13278
> Project: IMPALA
> Issue Type: Bug
> Reporter: Andrew Sherman
> Assignee: Andrew Sherman
> Priority: Critical
>
> The DCHECK that validates MonotonicStopWatch::Now() failed on m7g.4xlarge and
> killed a the server.
> {code:java}
> F0805 00:14:06.098425 788345 runtime-profile-counters.h:656]
> 4d4e5d4e693e5f9f:d7b795e200000003] Check failed: offset_ >= -3 (-5 vs. -3)
> *** Check failure stack trace: ***
> @ 0x35cf28b google::LogMessage::Fail()
> @ 0x35d125b google::LogMessage::SendToLog()
> @ 0x35cecaf google::LogMessage::Flush()
> @ 0x35d168f google::LogMessageFatal::~LogMessageFatal()
> @ 0x1453197 impala::FragmentInstanceState::Prepare()
> @ 0x1454387 impala::FragmentInstanceState::Exec()
> @ 0x13e0d77 impala::QueryState::ExecFInstance()
> @ 0x13e1147
> _ZN5boost6detail8function26void_function_obj_invoker0IZN6impala10QueryState15StartFInstancesEvEUlvE_vE6invokeERNS1_15function_bufferE
> @ 0x197f45f impala::Thread::SuperviseThread()
> @ 0x198027b boost::detail::thread_data<>::run()
> @ 0x23090d7 thread_proxy
> @ 0xffff906378b7 start_thread
> @ 0xffff8e613afb thread_start
> {code}
> It would be easy to bump the check last changed in IMPALA-4631 but let's see
> if this happens again
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
