[jira] [Commented] (IMPALA-6975) TestRuntimeRowFilters.test_row_filters failing with Memory limit exceeded

[ https://issues.apache.org/jira/browse/IMPALA-6975?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16464243#comment-16464243 ] Tim Armstrong commented on IMPALA-6975: --- A MEM_LIMIT probably just needs to be adjusted... >

[jira] [Resolved] (IMPALA-6507) Consider removing --disable_mem_pools debugging feature

[ https://issues.apache.org/jira/browse/IMPALA-6507?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Armstrong resolved IMPALA-6507. --- Resolution: Fixed Fix Version/s: Impala 3.1.0 Impala 2.13.0 >

[jira] [Comment Edited] (IMPALA-6227) TestAdmissionControllerStress can be flaky

[ https://issues.apache.org/jira/browse/IMPALA-6227?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16464480#comment-16464480 ] Tim Armstrong edited comment on IMPALA-6227 at 5/4/18 11:04 PM: Attached

[jira] [Updated] (IMPALA-6227) TestAdmissionControllerStress can be flaky

[ https://issues.apache.org/jira/browse/IMPALA-6227?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Armstrong updated IMPALA-6227: -- Attachment: TEST-impala-custom-cluster.xml > TestAdmissionControllerStress can be flaky >

[jira] [Commented] (IMPALA-6227) TestAdmissionControllerStress can be flaky

[ https://issues.apache.org/jira/browse/IMPALA-6227?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16464480#comment-16464480 ] Tim Armstrong commented on IMPALA-6227: --- Attached logs. I think this is the interesting part:

[jira] [Created] (IMPALA-6977) Report CPU usage (user/sys) per fragment

Tim Armstrong created IMPALA-6977: - Summary: Report CPU usage (user/sys) per fragment Key: IMPALA-6977 URL: https://issues.apache.org/jira/browse/IMPALA-6977 Project: IMPALA Issue Type:

[jira] [Commented] (IMPALA-6975) TestRuntimeRowFilters.test_row_filters failing with Memory limit exceeded

[ https://issues.apache.org/jira/browse/IMPALA-6975?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16464269#comment-16464269 ] Tim Armstrong commented on IMPALA-6975: --- We probably just need to increase mem_limit slightly.

[jira] [Commented] (IMPALA-6970) DiskMgr::AllocateBuffersForRange crashes on failed DCHECK

[ https://issues.apache.org/jira/browse/IMPALA-6970?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16464283#comment-16464283 ] Tim Armstrong commented on IMPALA-6970: --- I can't reproduce locally but there is definitely a race

[jira] [Commented] (IMPALA-6997) Query execution should notice UDF MemLimitExceeded errors more quickly

[ https://issues.apache.org/jira/browse/IMPALA-6997?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16468065#comment-16468065 ] Tim Armstrong commented on IMPALA-6997: --- IMPALA-2399 is meant to be the ultimate fix for this. It

[jira] [Created] (IMPALA-6995) False-positive DCHECK when converting whitespace-only strings to timestamp

Tim Armstrong created IMPALA-6995: - Summary: False-positive DCHECK when converting whitespace-only strings to timestamp Key: IMPALA-6995 URL: https://issues.apache.org/jira/browse/IMPALA-6995

[jira] [Commented] (IMPALA-6996) PartitionedAggregationNode::Close() should not allocate memory

[ https://issues.apache.org/jira/browse/IMPALA-6996?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16467999#comment-16467999 ] Tim Armstrong commented on IMPALA-6996: --- We can't necessarily avoid the memory allocation in

[jira] [Commented] (IMPALA-4268) Allow PlanRootSink to buffer more than a batch of rows

[ https://issues.apache.org/jira/browse/IMPALA-4268?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16474669#comment-16474669 ] Tim Armstrong commented on IMPALA-4268: --- I think it would solve that as a side-effect. > Allow

[jira] [Commented] (IMPALA-7025) PlannerTest.testTableSample has wrong mem-reservation

[ https://issues.apache.org/jira/browse/IMPALA-7025?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16474666#comment-16474666 ] Tim Armstrong commented on IMPALA-7025: --- Is this on a 2.x or 3.x branch? >

[jira] [Assigned] (IMPALA-7025) PlannerTest.testTableSample has wrong mem-reservation

[ https://issues.apache.org/jira/browse/IMPALA-7025?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Armstrong reassigned IMPALA-7025: - Assignee: Tim Armstrong > PlannerTest.testTableSample has wrong mem-reservation >

[jira] [Updated] (IMPALA-7027) Multiple Cast to Varchar with different limit fails with "AnalysisException: null CAUSED BY: IllegalArgumentException: "

[ https://issues.apache.org/jira/browse/IMPALA-7027?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Armstrong updated IMPALA-7027: -- Target Version: Impala 2.13.0, Impala 3.1.0 > Multiple Cast to Varchar with different limit

[jira] [Updated] (IMPALA-7027) Multiple Cast to Varchar with different limit fails with "AnalysisException: null CAUSED BY: IllegalArgumentException: "

[ https://issues.apache.org/jira/browse/IMPALA-7027?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Armstrong updated IMPALA-7027: -- Priority: Critical (was: Major) > Multiple Cast to Varchar with different limit fails with

[jira] [Updated] (IMPALA-7027) Multiple Cast to Varchar with different limit fails with "AnalysisException: null CAUSED BY: IllegalArgumentException: "

[ https://issues.apache.org/jira/browse/IMPALA-7027?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Armstrong updated IMPALA-7027: -- Component/s: (was: Clients) Frontend > Multiple Cast to Varchar with

[jira] [Assigned] (IMPALA-7022) TestQueries.test_subquery: Subquery must not return more than one row

[ https://issues.apache.org/jira/browse/IMPALA-7022?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Armstrong reassigned IMPALA-7022: - Assignee: Zoltán Borók-Nagy > TestQueries.test_subquery: Subquery must not return more

[jira] [Commented] (IMPALA-7025) PlannerTest.testTableSample has wrong mem-reservation

[ https://issues.apache.org/jira/browse/IMPALA-7025?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16475099#comment-16475099 ] Tim Armstrong commented on IMPALA-7025: --- It could be because a different set of files was selected

[jira] [Resolved] (IMPALA-6946) Hit DCHECK in impala::RleBatchDecoder::GetRepeatedValue

[ https://issues.apache.org/jira/browse/IMPALA-6946?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Armstrong resolved IMPALA-6946. --- Resolution: Fixed Fix Version/s: Impala 3.1.0 Impala 2.13.0 > Hit

[jira] [Assigned] (IMPALA-6035) Add query option that rejects queries based on query complexity

[ https://issues.apache.org/jira/browse/IMPALA-6035?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Armstrong reassigned IMPALA-6035: - Assignee: Tim Armstrong > Add query option that rejects queries based on query

[jira] [Assigned] (IMPALA-6034) Add query option that rejects queries based on estimate number of scanned bytes

[ https://issues.apache.org/jira/browse/IMPALA-6034?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Armstrong reassigned IMPALA-6034: - Assignee: Mostafa Mokhtar > Add query option that rejects queries based on estimate

[jira] [Commented] (IMPALA-6996) PartitionedAggregationNode::Close() should not dump stack trace

[ https://issues.apache.org/jira/browse/IMPALA-6996?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16469089#comment-16469089 ] Tim Armstrong commented on IMPALA-6996: --- +1, just avoiding unnecessary work seems like a clear win

[jira] [Updated] (IMPALA-6034) Add query option that limits scanned bytes at runtime

[ https://issues.apache.org/jira/browse/IMPALA-6034?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Armstrong updated IMPALA-6034: -- Summary: Add query option that limits scanned bytes at runtime (was: Add query option that

[jira] [Commented] (IMPALA-6996) PartitionedAggregationNode::Close() should not dump stack trace

[ https://issues.apache.org/jira/browse/IMPALA-6996?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16469237#comment-16469237 ] Tim Armstrong commented on IMPALA-6996: --- Just to add some context about why this is so slow, since

[jira] [Resolved] (IMPALA-605) HBASE_CACHING default incorrectly displayed

[ https://issues.apache.org/jira/browse/IMPALA-605?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Armstrong resolved IMPALA-605. -- Resolution: Duplicate > HBASE_CACHING default incorrectly displayed >

[jira] [Updated] (IMPALA-6946) Hit DCHECK in impala::RleBatchDecoder::GetRepeatedValue

[ https://issues.apache.org/jira/browse/IMPALA-6946?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Armstrong updated IMPALA-6946: -- Target Version: Impala 2.13.0, Impala 3.1.0 > Hit DCHECK in

[jira] [Updated] (IMPALA-7010) Multiple flaky tests failing with MemLimitExceeded on S3

[ https://issues.apache.org/jira/browse/IMPALA-7010?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Armstrong updated IMPALA-7010: -- Labels: flaky (was: ) > Multiple flaky tests failing with MemLimitExceeded on S3 >

[jira] [Resolved] (IMPALA-5735) Avoid fork() in ProcessStateInfo

[ https://issues.apache.org/jira/browse/IMPALA-5735?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Armstrong resolved IMPALA-5735. --- Resolution: Duplicate > Avoid fork() in ProcessStateInfo >

[jira] [Work started] (IMPALA-7010) Multiple flaky tests failing with MemLimitExceeded on S3

[ https://issues.apache.org/jira/browse/IMPALA-7010?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on IMPALA-7010 started by Tim Armstrong. - > Multiple flaky tests failing with MemLimitExceeded on S3 >

[jira] [Commented] (IMPALA-7010) Multiple flaky tests failing with MemLimitExceeded on S3

[ https://issues.apache.org/jira/browse/IMPALA-7010?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16471252#comment-16471252 ] Tim Armstrong commented on IMPALA-7010: --- I'm looking at this. I'll try to move a bunch of these

[jira] [Resolved] (IMPALA-7010) Multiple flaky tests failing with MemLimitExceeded on S3

[ https://issues.apache.org/jira/browse/IMPALA-7010?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Armstrong resolved IMPALA-7010. --- Resolution: Fixed Fix Version/s: Impala 3.1.0 Impala 2.13.0 >

[jira] [Commented] (IMPALA-4268) Allow PlanRootSink to buffer more than a batch of rows

[ https://issues.apache.org/jira/browse/IMPALA-4268?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16472642#comment-16472642 ] Tim Armstrong commented on IMPALA-4268: --- I'm going to steal this JIRA and extend it slightly. I

[jira] [Created] (IMPALA-7012) NullPointerException with CTAS query

Tim Armstrong created IMPALA-7012: - Summary: NullPointerException with CTAS query Key: IMPALA-7012 URL: https://issues.apache.org/jira/browse/IMPALA-7012 Project: IMPALA Issue Type: Bug

[jira] [Resolved] (IMPALA-6970) DiskMgr::AllocateBuffersForRange crashes on failed DCHECK

[ https://issues.apache.org/jira/browse/IMPALA-6970?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Armstrong resolved IMPALA-6970. --- Resolution: Fixed Fix Version/s: Impala 3.1.0 Impala 2.13.0 >

[jira] [Commented] (IMPALA-6979) BloomFilterBenchmark hits DCHECK

[ https://issues.apache.org/jira/browse/IMPALA-6979?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16466251#comment-16466251 ] Tim Armstrong commented on IMPALA-6979: --- No I didn't, I assume it's reproducible though >

[jira] [Assigned] (IMPALA-5843) Use page index in Parquet files to skip pages

[ https://issues.apache.org/jira/browse/IMPALA-5843?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Armstrong reassigned IMPALA-5843: - Assignee: Zoltán Borók-Nagy > Use page index in Parquet files to skip pages >

[jira] [Commented] (IMPALA-7030) crash in impala::PartitionedAggregationNode::ProcessBatchNoGrouping

[ https://issues.apache.org/jira/browse/IMPALA-7030?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16476076#comment-16476076 ] Tim Armstrong commented on IMPALA-7030: --- I also saw a crash in codegen'd code on the same job. I

[jira] [Commented] (IMPALA-7031) Detailed failure reason for clients when a query is cancelled from the WebUi

[ https://issues.apache.org/jira/browse/IMPALA-7031?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16476046#comment-16476046 ] Tim Armstrong commented on IMPALA-7031: --- [~adrenas] I think this is only possible if the query is

[jira] [Updated] (IMPALA-7032) Codegen crash when UNIONing NULL and CHAR(N)

[ https://issues.apache.org/jira/browse/IMPALA-7032?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Armstrong updated IMPALA-7032: -- Affects Version/s: Impala 3.1.0 > Codegen crash when UNIONing NULL and CHAR(N) >

[jira] [Updated] (IMPALA-7000) Wrong info about Impala dedicated executors

[ https://issues.apache.org/jira/browse/IMPALA-7000?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Armstrong updated IMPALA-7000: -- Summary: Wrong info about Impala dedicated executors (was: Wrong info about Impala dedicated

[jira] [Resolved] (IMPALA-6645) Consider enabling disk spill encryption by default

[ https://issues.apache.org/jira/browse/IMPALA-6645?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Armstrong resolved IMPALA-6645. --- Resolution: Fixed Fix Version/s: Impala 3.1.0 Impala 2.13.0 >

[jira] [Work started] (IMPALA-6035) Add query option that rejects queries based on query complexity

[ https://issues.apache.org/jira/browse/IMPALA-6035?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on IMPALA-6035 started by Tim Armstrong. - > Add query option that rejects queries based on query complexity >

[jira] [Commented] (IMPALA-7044) int32 overflow in HdfsTableSink::CreateNewTmpFile()

[ https://issues.apache.org/jira/browse/IMPALA-7044?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16482642#comment-16482642 ] Tim Armstrong commented on IMPALA-7044: --- [~lv] maybe we should just cap the number of columns that

[jira] [Created] (IMPALA-7053) Reorganise query options into groups

Tim Armstrong created IMPALA-7053: - Summary: Reorganise query options into groups Key: IMPALA-7053 URL: https://issues.apache.org/jira/browse/IMPALA-7053 Project: IMPALA Issue Type:

[jira] [Commented] (IMPALA-7044) int32 overflow in HdfsTableSink::CreateNewTmpFile()

[ https://issues.apache.org/jira/browse/IMPALA-7044?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16482775#comment-16482775 ] Tim Armstrong commented on IMPALA-7044: --- Yeah, so regardless I think we should pick an upper limit

[jira] [Resolved] (IMPALA-7057) crash when DiskIoMgr::GetFreeBuffer(long*)+0xa9

[ https://issues.apache.org/jira/browse/IMPALA-7057?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Armstrong resolved IMPALA-7057. --- Resolution: Duplicate We changed the code to prevent the crash in Impala 2.7.0. I believe

[jira] [Updated] (IMPALA-3544) crash in DiskIoMgr::GetFreeBuffer

[ https://issues.apache.org/jira/browse/IMPALA-3544?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Armstrong updated IMPALA-3544: -- Summary: crash in DiskIoMgr::GetFreeBuffer (was: data-stream-sender.cc:261 channel send

[jira] [Commented] (IMPALA-7055) test_avro_writer failing on upstream Jenkins (Expected exception: "Writing to table format AVRO is not supported")

[ https://issues.apache.org/jira/browse/IMPALA-7055?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16488020#comment-16488020 ] Tim Armstrong commented on IMPALA-7055: --- I can repro by adding a sleep: {code:java}   if

[jira] [Updated] (IMPALA-7055) test_avro_writer failing on upstream Jenkins (Expected exception: "Writing to table format AVRO is not supported")

[ https://issues.apache.org/jira/browse/IMPALA-7055?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Armstrong updated IMPALA-7055: -- Target Version: Impala 3.1.0 > test_avro_writer failing on upstream Jenkins (Expected

[jira] [Updated] (IMPALA-7055) test_avro_writer failing on upstream Jenkins (Expected exception: "Writing to table format AVRO is not supported")

[ https://issues.apache.org/jira/browse/IMPALA-7055?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Armstrong updated IMPALA-7055: -- Priority: Blocker (was: Major) > test_avro_writer failing on upstream Jenkins (Expected

[jira] [Assigned] (IMPALA-6998) test_bloom_wait_time fails due to late arrival of filters on Isilon

[ https://issues.apache.org/jira/browse/IMPALA-6998?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Armstrong reassigned IMPALA-6998: - Assignee: Tim Armstrong > test_bloom_wait_time fails due to late arrival of filters on

[jira] [Assigned] (IMPALA-6998) test_bloom_wait_time fails due to late arrival of filters on Isilon

[ https://issues.apache.org/jira/browse/IMPALA-6998?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Armstrong reassigned IMPALA-6998: - Assignee: Sailesh Mukil (was: Tim Armstrong) > test_bloom_wait_time fails due to late

[jira] [Resolved] (IMPALA-3833) Fix invalid data handling in Sequence and RCFile scanners

[ https://issues.apache.org/jira/browse/IMPALA-3833?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Armstrong resolved IMPALA-3833. --- Resolution: Fixed Fix Version/s: Impala 3.1.0 Impala 2.13.0 The

[jira] [Updated] (IMPALA-7055) test_avro_writer failing on upstream Jenkins (Expected exception: "Writing to table format AVRO is not supported")

[ https://issues.apache.org/jira/browse/IMPALA-7055?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Armstrong updated IMPALA-7055: -- Labels: correctness flaky (was: flaky) > test_avro_writer failing on upstream Jenkins

[jira] [Assigned] (IMPALA-7055) test_avro_writer failing on upstream Jenkins (Expected exception: "Writing to table format AVRO is not supported")

[ https://issues.apache.org/jira/browse/IMPALA-7055?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Armstrong reassigned IMPALA-7055: - Assignee: Tim Armstrong > test_avro_writer failing on upstream Jenkins (Expected

[jira] [Created] (IMPALA-7065) Fix remaining invalid data handling bugs in RC and sequence file

Tim Armstrong created IMPALA-7065: - Summary: Fix remaining invalid data handling bugs in RC and sequence file Key: IMPALA-7065 URL: https://issues.apache.org/jira/browse/IMPALA-7065 Project: IMPALA

[jira] [Updated] (IMPALA-7055) test_avro_writer failing on upstream Jenkins (Expected exception: "Writing to table format AVRO is not supported")

[ https://issues.apache.org/jira/browse/IMPALA-7055?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Armstrong updated IMPALA-7055: -- Description: This failure occurred while verifying https://gerrit.cloudera.org/c/10455/, but

[jira] [Commented] (IMPALA-7055) test_avro_writer failing on upstream Jenkins (Expected exception: "Writing to table format AVRO is not supported")

[ https://issues.apache.org/jira/browse/IMPALA-7055?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16487993#comment-16487993 ] Tim Armstrong commented on IMPALA-7055: --- Here are the log lines with the query id. It ran on the

[jira] [Created] (IMPALA-7067) sleep(100000) command from test_shell_commandline.py can hang around and cause test_metrics_are_zero to fail

Tim Armstrong created IMPALA-7067: - Summary: sleep(10) command from test_shell_commandline.py can hang around and cause test_metrics_are_zero to fail Key: IMPALA-7067 URL:

[jira] [Updated] (IMPALA-7067) sleep(100000) command from test_shell_commandline.py can hang around and cause test_metrics_are_zero to fail

[ https://issues.apache.org/jira/browse/IMPALA-7067?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Armstrong updated IMPALA-7067: -- Target Version: Impala 2.13.0, Impala 3.1.0 (was: Impala 3.1.0) > sleep(10) command from

[jira] [Resolved] (IMPALA-5837) TestImpalaShell.test_cancellation fails on ASAN build: Could not execute command: select sleep(10000)

[ https://issues.apache.org/jira/browse/IMPALA-5837?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Armstrong resolved IMPALA-5837. --- Resolution: Cannot Reproduce > TestImpalaShell.test_cancellation fails on ASAN build: Could

[jira] [Updated] (IMPALA-7073) Failed test: query_test.test_scanners.TestScannerReservation.test_scanners

[ https://issues.apache.org/jira/browse/IMPALA-7073?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Armstrong updated IMPALA-7073: -- Description: Possibly flaky test:  {code:java} Stacktrace query_test/test_scanners.py:1064: in

[jira] [Commented] (IMPALA-7067) sleep(100000) command from test_shell_commandline.py can hang around and cause test_metrics_are_zero to fail

[ https://issues.apache.org/jira/browse/IMPALA-7067?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16489329#comment-16489329 ] Tim Armstrong commented on IMPALA-7067: --- It's a test bug - the fragment thread is stuck in the

[jira] [Created] (IMPALA-7069) Java UDF tests can trigger a crash in java.util.concurrent.ConcurrentHashMap.putVal()

Tim Armstrong created IMPALA-7069: - Summary: Java UDF tests can trigger a crash in java.util.concurrent.ConcurrentHashMap.putVal() Key: IMPALA-7069 URL: https://issues.apache.org/jira/browse/IMPALA-7069

[jira] [Commented] (IMPALA-7069) Java UDF tests can trigger a crash in Java ClassLoader

[ https://issues.apache.org/jira/browse/IMPALA-7069?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16489358#comment-16489358 ] Tim Armstrong commented on IMPALA-7069: --- Assigned to Vuk since he's looked at the UDF loading most

[jira] [Updated] (IMPALA-7069) Java UDF tests can trigger a crash in Java ClassLoader

[ https://issues.apache.org/jira/browse/IMPALA-7069?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Armstrong updated IMPALA-7069: -- Summary: Java UDF tests can trigger a crash in Java ClassLoader (was: Java UDF tests can

[jira] [Commented] (IMPALA-7069) Java UDF tests can trigger a crash in Java ClassLoader

[ https://issues.apache.org/jira/browse/IMPALA-7069?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16489522#comment-16489522 ] Tim Armstrong commented on IMPALA-7069: --- I saw it on a commit branched off

[jira] [Resolved] (IMPALA-7055) test_avro_writer failing on upstream Jenkins (Expected exception: "Writing to table format AVRO is not supported")

[ https://issues.apache.org/jira/browse/IMPALA-7055?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Armstrong resolved IMPALA-7055. --- Resolution: Fixed Fix Version/s: Impala 3.1.0 Impala 2.13.0 >

[jira] [Commented] (IMPALA-7012) NullPointerException with CTAS query

[ https://issues.apache.org/jira/browse/IMPALA-7012?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16489849#comment-16489849 ] Tim Armstrong commented on IMPALA-7012: --- I'm not sure, I was probably doing something wrong here,

[jira] [Resolved] (IMPALA-7067) sleep(100000) command from test_shell_commandline.py can hang around and cause test_metrics_are_zero to fail

[ https://issues.apache.org/jira/browse/IMPALA-7067?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Armstrong resolved IMPALA-7067. --- Resolution: Fixed Fix Version/s: Impala 3.1.0 Impala 2.13.0 >

[jira] [Commented] (IMPALA-7073) Failed test: query_test.test_scanners.TestScannerReservation.test_scanners

[ https://issues.apache.org/jira/browse/IMPALA-7073?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16490275#comment-16490275 ] Tim Armstrong commented on IMPALA-7073: --- I added this test so I'll take it for now. I'm guessing

[jira] [Commented] (IMPALA-7023) TestInsertQueries.test_insert_overwrite fails by hitting memory limit

[ https://issues.apache.org/jira/browse/IMPALA-7023?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16476086#comment-16476086 ] Tim Armstrong commented on IMPALA-7023: --- So there's some bug or other issue causing those queries

[jira] [Commented] (IMPALA-7049) Scan node reservation calculation seems off

[ https://issues.apache.org/jira/browse/IMPALA-7049?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16481320#comment-16481320 ] Tim Armstrong commented on IMPALA-7049: --- Attached a profile from an affected query. It doesn't

[jira] [Resolved] (IMPALA-6995) False-positive DCHECK when converting whitespace-only strings to timestamp

[ https://issues.apache.org/jira/browse/IMPALA-6995?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Armstrong resolved IMPALA-6995. --- Resolution: Fixed Fix Version/s: Impala 3.1.0 Impala 2.13.0 >

[jira] [Assigned] (IMPALA-1034) Verify RSS stays within mem_limit + JVM heapsize

[ https://issues.apache.org/jira/browse/IMPALA-1034?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Armstrong reassigned IMPALA-1034: - Assignee: (was: Tim Armstrong) > Verify RSS stays within mem_limit + JVM heapsize >

[jira] [Work started] (IMPALA-6969) Profile doesn't include the reason that a query couldn't be dequeued from admission controller

[ https://issues.apache.org/jira/browse/IMPALA-6969?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on IMPALA-6969 started by Tim Armstrong. - > Profile doesn't include the reason that a query couldn't be dequeued from

[jira] [Commented] (IMPALA-6969) Profile doesn't include the reason that a query couldn't be dequeued from admission controller

[ https://issues.apache.org/jira/browse/IMPALA-6969?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16476583#comment-16476583 ] Tim Armstrong commented on IMPALA-6969: --- I prototyped a fix of this. It touches the same code as

[jira] [Work stopped] (IMPALA-6969) Profile doesn't include the reason that a query couldn't be dequeued from admission controller

[ https://issues.apache.org/jira/browse/IMPALA-6969?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on IMPALA-6969 stopped by Tim Armstrong. - > Profile doesn't include the reason that a query couldn't be dequeued from

[jira] [Commented] (IMPALA-7058) Crash in exhaustive tests for rhel7

[ https://issues.apache.org/jira/browse/IMPALA-7058?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16487648#comment-16487648 ] Tim Armstrong commented on IMPALA-7058: --- I'll push out a fix to disable the fuzz test. We should

[jira] [Updated] (IMPALA-7058) RC and Seq fuzz tests cause crash

[ https://issues.apache.org/jira/browse/IMPALA-7058?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Armstrong updated IMPALA-7058: -- Summary: RC and Seq fuzz tests cause crash (was: Crash in exhaustive tests for rhel7 ) > RC

[jira] [Resolved] (IMPALA-6960) TestMtDopParquet.test_parquet_filtering flaky

[ https://issues.apache.org/jira/browse/IMPALA-6960?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Armstrong resolved IMPALA-6960. --- Resolution: Duplicate I'll mark this as a dupe. If we see this specific failure happen

[jira] [Assigned] (IMPALA-7008) TestSpillingDebugActionDimensions.test_spilling test setup fails

[ https://issues.apache.org/jira/browse/IMPALA-7008?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Armstrong reassigned IMPALA-7008: - Assignee: David Knupp > TestSpillingDebugActionDimensions.test_spilling test setup

[jira] [Commented] (IMPALA-5212) consider switching to pread by default

[ https://issues.apache.org/jira/browse/IMPALA-5212?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16487761#comment-16487761 ] Tim Armstrong commented on IMPALA-5212: --- I think it's possible that this could affect remote read

[jira] [Comment Edited] (IMPALA-7028) TestKuduOperations.test_kudu_update fails due to wrong NumModifiedRows

[ https://issues.apache.org/jira/browse/IMPALA-7028?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16487685#comment-16487685 ] Tim Armstrong edited comment on IMPALA-7028 at 5/23/18 6:44 PM: -Probably

[jira] [Updated] (IMPALA-6338) test_profile_fragment_instances failing

[ https://issues.apache.org/jira/browse/IMPALA-6338?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Armstrong updated IMPALA-6338: -- Attachment: kudu-update-profile.txt > test_profile_fragment_instances failing >

[jira] [Commented] (IMPALA-7028) TestKuduOperations.test_kudu_update fails due to wrong NumModifiedRows

[ https://issues.apache.org/jira/browse/IMPALA-7028?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16487846#comment-16487846 ] Tim Armstrong commented on IMPALA-7028: --- According to the profile, all of the Kudu scan nodes

[jira] [Updated] (IMPALA-7028) TestKuduOperations.test_kudu_update fails due to wrong NumModifiedRows

[ https://issues.apache.org/jira/browse/IMPALA-7028?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Armstrong updated IMPALA-7028: -- Labels: broken-build correctness flaky (was: broken-build flaky) >

[jira] [Updated] (IMPALA-7028) TestKuduOperations.test_kudu_update fails due to wrong NumModifiedRows

[ https://issues.apache.org/jira/browse/IMPALA-7028?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Armstrong updated IMPALA-7028: -- Attachment: kudu-update-profile.txt > TestKuduOperations.test_kudu_update fails due to wrong

[jira] [Updated] (IMPALA-7156) Many authorization tests failed with "User 'jenkins' does not have privileges to access"

[ https://issues.apache.org/jira/browse/IMPALA-7156?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Armstrong updated IMPALA-7156: -- Attachment: 0001-Fix-IMPALA-7156-breakage-in-Sentry.patch > Many authorization tests failed

[jira] [Commented] (IMPALA-7156) Many authorization tests failed with "User 'jenkins' does not have privileges to access"

[ https://issues.apache.org/jira/browse/IMPALA-7156?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16507215#comment-16507215 ] Tim Armstrong commented on IMPALA-7156: --- The attached patch is sufficient to fix the tests. >

[jira] [Commented] (IMPALA-7156) Many authorization tests failed with "User 'jenkins' does not have privileges to access"

[ https://issues.apache.org/jira/browse/IMPALA-7156?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16507056#comment-16507056 ] Tim Armstrong commented on IMPALA-7156: --- I'm testing to see if reverting the Sentry dependency to

[jira] [Reopened] (IMPALA-7111) ASAN heap-use-after-free in impala::HdfsPluginTextScanner::CheckPluginEnabled

[ https://issues.apache.org/jira/browse/IMPALA-7111?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Armstrong reopened IMPALA-7111: --- Looks like we hit this on a non-ASAN build: {noformat}

[jira] [Comment Edited] (IMPALA-7111) ASAN heap-use-after-free in impala::HdfsPluginTextScanner::CheckPluginEnabled

[ https://issues.apache.org/jira/browse/IMPALA-7111?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16508308#comment-16508308 ] Tim Armstrong edited comment on IMPALA-7111 at 6/11/18 4:24 PM: Looks

[jira] [Resolved] (IMPALA-7078) Selective Avro scans of wide tables use more memory than necessary

[ https://issues.apache.org/jira/browse/IMPALA-7078?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Armstrong resolved IMPALA-7078. --- Resolution: Fixed Fix Version/s: Impala 3.1.0 Impala 2.13.0 >

[jira] [Resolved] (IMPALA-411) Add testing for ReadWriteUtil

[ https://issues.apache.org/jira/browse/IMPALA-411?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Armstrong resolved IMPALA-411. -- Resolution: Later This isn't a terrible idea but we don't need a JIRA to track adding more

[jira] [Commented] (IMPALA-6942) "Cancelled due to unreachable impalad(s)" error message is misleading

[ https://issues.apache.org/jira/browse/IMPALA-6942?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16508962#comment-16508962 ] Tim Armstrong commented on IMPALA-6942: --- [~dhecht] this seems to be a one-word change. Any reason

[jira] [Assigned] (IMPALA-6160) tpcds-q22a.test breaks run-workload.py

[ https://issues.apache.org/jira/browse/IMPALA-6160?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Armstrong reassigned IMPALA-6160: - Assignee: (was: Tim Wood) > tpcds-q22a.test breaks run-workload.py >

[jira] [Resolved] (IMPALA-6199) Flaky test: metadata/test_hdfs_permissions.py

[ https://issues.apache.org/jira/browse/IMPALA-6199?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Armstrong resolved IMPALA-6199. --- Resolution: Cannot Reproduce > Flaky test: metadata/test_hdfs_permissions.py >

[jira] [Commented] (IMPALA-6074) All Build Options Jenkins job can fail when running on a previously-used node

[ https://issues.apache.org/jira/browse/IMPALA-6074?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16508932#comment-16508932 ] Tim Armstrong commented on IMPALA-6074: --- [~jbapple] I guess this hasn't reoccurred? > All Build

  1   2   3   4   5   6   7   8   9   10   >