[
https://issues.apache.org/jira/browse/IMPALA-8128?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16757833#comment-16757833
]
Michael Ho commented on IMPALA-8128:
------------------------------------
Just hit a similar case. Seems to be unsynchronized clock in the VM:
{noformat}
Log line format: [IWEF]mmdd hh:mm:ss.uuuuuu threadid file:line] msg
F0131 13:19:06.405735 14545 tablet_server_main.cc:80] Check failed: _s.ok() Bad
status: Service unavailable: Cannot initialize clock: Error reading clock.
Clock considered unsynchronized
Log file created at: 2019/01/31 13:19:06
Running on machine:
impala-ec2-centos74-m5-4xlarge-ondemand-12f6.vpc.cloudera.com
Log line format: [IWEF]mmdd hh:mm:ss.uuuuuu threadid file:line] msg
F0131 13:19:06.405642 14570 tablet_server_main.cc:80] Check failed: _s.ok() Bad
status: Service unavailable: Cannot initialize clock: Error reading clock.
Clock considered unsynchronized
Log file created at: 2019/01/31 13:19:06
Running on machine:
impala-ec2-centos74-m5-4xlarge-ondemand-12f6.vpc.cloudera.com
Log line format: [IWEF]mmdd hh:mm:ss.uuuuuu threadid file:line] msg
F0131 13:19:06.405911 14529 tablet_server_main.cc:80] Check failed: _s.ok() Bad
status: Service unavailable: Cannot initialize clock: Error reading clock.
Clock considered unsynchronized
{noformat}
> Build failure: Kudu functional data load - Kudu crashed
> -------------------------------------------------------
>
> Key: IMPALA-8128
> URL: https://issues.apache.org/jira/browse/IMPALA-8128
> Project: IMPALA
> Issue Type: Bug
> Components: Infrastructure
> Affects Versions: Impala 3.1.0
> Reporter: Paul Rogers
> Assignee: Lenisha Gandhi
> Priority: Blocker
> Labels: broken-build
> Fix For: Impala 3.1.0
>
>
> ASAN and core builds failed due, it seems, to a Kudu crash when loading data.
> Looks like tpcds, tech and functional all failed.
> {noformat}
> 20:28:01 + msg='Loading functional-query data'
> ...
> 20:31:42 20:31:41 Error executing impala SQL:
> /data/jenkins/workspace/impala-asf-master-core-asan/repos/Impala/logs/data_loading/sql/tpch/create-tpch-core-impala-generated-kudu-none-none.sql
> See:
> /data/jenkins/workspace/impala-asf-master-core-asan/repos/Impala/logs/data_loading/sql/tpch/create-tpch-core-impala-generated-kudu-none-none.sql.log
> ...
> 20:40:52 FAILED (Took: 12 min 51 sec)
> ...
> 20:40:52 20:40:52 Error executing impala SQL:
> /data/jenkins/workspace/impala-asf-master-core-asan/repos/Impala/logs/data_loading/sql/functional/create-functional-query-exhaustive-impala-generated-kudu-none-none.sql
> See:
> /data/jenkins/workspace/impala-asf-master-core-asan/repos/Impala/logs/data_loading/sql/functional/create-functional-query-exhaustive-impala-generated-kudu-none-none.sql.log
> ...
> 20:41:16 2019-01-25 20:41:16,863 - archive_core_dumps - INFO - Found binary
> path through GDB:
> /data/jenkins/workspace/impala-asf-master-core-asan/Impala-Toolchain/cdh_compon
> 20:41:17 2019-01-25 20:41:17,043 - archive_core_dumps - WARNING - Failed to
> determine binary because multiple candidate binaries were found and none of
> their paths contained 'latest' to disambiguate:
> 20:41:17 Core:./core.1548476819.29942.kudu-tserver
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-all-unsubscr...@impala.apache.org
For additional commands, e-mail: issues-all-h...@impala.apache.org
