[
https://issues.apache.org/jira/browse/DRILL-6453?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16531980#comment-16531980
]
Khurram Faraaz commented on DRILL-6453:
---------------------------------------
[~ben-zvi] [~priteshm]
Apache Drill 1.14.0 on a 4 node cluster, TPC-DS query 72 fails (in Canceled
state) after running for 2hrs and 11 mins
and we see the same Exception as before towards the end of the drillbit.log
file.
git.commit.id.abbrev=f481a7c
{noformat}
message: "SYSTEM ERROR: IllegalStateException: Record count not set for this
vector container\n\nFragment 4:87\n\n[Error Id:
ed305d45-742f-48df-b1ad-6813bb5fdfc4 on qa102-48.qa.lab:31010]"
exception {
exception_class: "java.lang.IllegalStateException"
message: "Record count not set for this vector container"
stack_trace {
class_name: "com.google.common.base.Preconditions"
file_name: "Preconditions.java"
line_number: 173
method_name: "checkState"
is_native_method: false
}
stack_trace {
class_name: "org.apache.drill.exec.record.VectorContainer"
file_name: "VectorContainer.java"
line_number: 394
method_name: "getRecordCount"
is_native_method: false
}
stack_trace {
class_name: "org.apache.drill.exec.physical.impl.svremover.RemovingRecordBatch"
file_name: "RemovingRecordBatch.java"
line_number: 49
method_name: "getRecordCount"
is_native_method: false
}
stack_trace {
class_name: "org.apache.drill.exec.record.RecordBatchSizer"
file_name: "RecordBatchSizer.java"
line_number: 714
method_name: "<init>"
is_native_method: false
}
stack_trace {
class_name: "org.apache.drill.exec.record.RecordBatchSizer"
file_name: "RecordBatchSizer.java"
line_number: 686
method_name: "<init>"
is_native_method: false
}
stack_trace {
class_name{ "org.apache.drill.exec.record.JoinBatchMemoryManager"
file_name: "JoinBatchMemoryManager.java"
line_number: 74
method_name: "update"
{noformat}
> TPC-DS query 72 has regressed
> -----------------------------
>
> Key: DRILL-6453
> URL: https://issues.apache.org/jira/browse/DRILL-6453
> Project: Apache Drill
> Issue Type: Bug
> Components: Execution - Flow
> Affects Versions: 1.14.0
> Reporter: Khurram Faraaz
> Assignee: Boaz Ben-Zvi
> Priority: Blocker
> Fix For: 1.14.0
>
> Attachments: 24f75b18-014a-fb58-21d2-baeab5c3352c.sys.drill
>
>
> TPC-DS query 72 seems to have regressed, query profile for the case where it
> Canceled after 2 hours on Drill 1.14.0 is attached here.
> {noformat}
> On, Drill 1.14.0-SNAPSHOT
> commit : 931b43e (TPC-DS query 72 executed successfully on this commit, took
> around 55 seconds to execute)
> SF1 parquet data on 4 nodes;
> planner.memory.max_query_memory_per_node = 10737418240.
> drill.exec.hashagg.fallback.enabled = true
> TPC-DS query 72 executed successfully & took 47 seconds to complete execution.
> {noformat}
> {noformat}
> TPC-DS data in the below run has date values stored as DATE datatype and not
> VARCHAR type
> On, Drill 1.14.0-SNAPSHOT
> commit : 82e1a12
> SF1 parquet data on 4 nodes;
> planner.memory.max_query_memory_per_node = 10737418240.
> drill.exec.hashagg.fallback.enabled = true
> and
> alter system set `exec.hashjoin.num_partitions` = 1;
> TPC-DS query 72 executed for 2 hrs and 11 mins and did not complete, I had to
> Cancel it by stopping the Foreman drillbit.
> As a result several minor fragments are reported to be in
> CANCELLATION_REQUESTED state on UI.
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
