[ 
https://issues.apache.org/jira/browse/IMPALA-10808?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17384711#comment-17384711
 ] 

Quanlong Huang commented on IMPALA-10808:
-----------------------------------------

The stacktrace isĀ 
[https://jenkins.impala.io/job/ubuntu-16.04-from-scratch/14381/testReport/junit/generate_junitxml/finalize/minidumps/]
{code:java}
Thread 651 (crashed)
 0  libc-2.23.so + 0x35438
 1  impalad!google::LogMessage::Flush() + 0x1eb
 2  impalad!google::LogMessageFatal::~LogMessageFatal() + 0x9
 3  impalad!impala::ColumnType::GetDecimalByteSize(int) [types.h : 282 + 0xc]
 4  impalad!impala::ParquetDataConverter<impala::DecimalValue<int>, 
true>::CheckIfNeedsConversion() [parquet-data-converter.h : 74 + 0x11]
 5  impalad!impala::ParquetDataConverter<impala::DecimalValue<int>, 
true>::ParquetDataConverter(parquet::SchemaElement const*, impala::ColumnType 
const*) [parquet-data-converter.h : 36 + 0xc]
 6  impalad!impala::ScalarColumnReader<impala::DecimalValue<int>, 
(parquet::Type::type)7, true>::ScalarColumnReader(impala::HdfsParquetScanner*, 
impala::SchemaNode const&, impala::SlotDescriptor const*) 
[parquet-column-readers.cc : 282 + 0xb]
 7  impalad!impala::CreateDecimalColumnReader [parquet-column-readers.cc : 1403 
+ 0x24]
 8  impalad!impala::ParquetColumnReader::Create(impala::SchemaNode const&, 
bool, impala::SlotDescriptor const*, impala::HdfsParquetScanner*) 
[parquet-column-readers.cc : 1494 + 0x17]
 9  
impalad!impala::HdfsParquetScanner::CreateColumnReaders(impala::TupleDescriptor 
const&, impala::ParquetSchemaResolver const&, 
std::vector<impala::ParquetColumnReader*, 
std::allocator<impala::ParquetColumnReader*> >*) [hdfs-parquet-scanner.cc : 
2494 + 0x1d]
10  impalad!impala::HdfsParquetScanner::Open(impala::ScannerContext*) 
[hdfs-parquet-scanner.cc : 227 + 0x58]
11  
impalad!impala::HdfsScanNodeBase::CreateAndOpenScannerHelper(impala::HdfsPartitionDescriptor*,
 impala::ScannerContext*, boost::scoped_ptr<impala::HdfsScanner>*) 
[hdfs-scan-node-base.cc : 874 + 0x2c]
12  
impalad!impala::HdfsScanNode::ProcessSplit(std::vector<impala::FilterContext, 
std::allocator<impala::FilterContext> > const&, impala::MemPool*, 
impala::io::ScanRange*, long*) [hdfs-scan-node.cc : 480 + 0x2b]
13  impalad!impala::HdfsScanNode::ScannerThread(bool, long) [hdfs-scan-node.cc 
: 418 + 0x27] {code}

> Crash of illegal decimal schema in test_fuzz_decimal_tbl
> --------------------------------------------------------
>
>                 Key: IMPALA-10808
>                 URL: https://issues.apache.org/jira/browse/IMPALA-10808
>             Project: IMPALA
>          Issue Type: Bug
>    Affects Versions: Impala 4.1
>            Reporter: Quanlong Huang
>            Assignee: Quanlong Huang
>            Priority: Blocker
>
> Recently saw two unrelated jobs failed by the same crash:
>  * [https://jenkins.impala.io/job/ubuntu-16.04-from-scratch/14369]
>  * [https://jenkins.impala.io/job/ubuntu-16.04-from-scratch/14381]
> For example in the second job, the test that crashes impalad is {code}
> query_test/test_scanners_fuzz.py::TestScannersFuzzing::()::test_fuzz_decimal_tbl[protocol:beeswax|exec_option:{'debug_action':'-1:OPEN:[email protected]';'abort_on_error':False;'mem_limit':'512m';'num_nodes':0}|table_format:parquet/none
> {code}
> The failure is
> {code:java}
> I0720 03:34:53.168516 126039 runtime-state.cc:196] 
> 8a42e69ff49106c8:d2096a7000000001] Error from query 
> 8a42e69ff49106c8:d2096a7000000000: File 
> 'hdfs://localhost:20500/test-warehouse/test_fuzz_decimal_tbl_4a8e12be.db/decimal_tbl/d6=1/copy1_6b48619353a75ffb-66460f7400000000_973668612_data.0.parq'
>  column 'd1' does not have the decimal precision set.
> F0720 03:34:53.168567 126039 types.h:282] 8a42e69ff49106c8:d2096a7000000001] 
> Check failed: precision > 0 (0 vs. 0)
> {code}
> CC [~boroknagyz] who owns the first job.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to