[jira] [Created] (IMPALA-8150) AuditingTest.TestAccessEventsOnAuthFailure

Michael Ho created IMPALA-8150: -- Summary: AuditingTest.TestAccessEventsOnAuthFailure Key: IMPALA-8150 URL: https://issues.apache.org/jira/browse/IMPALA-8150 Project: IMPALA Issue Type: Bug

[jira] [Updated] (IMPALA-6159) DataStreamSender should transparently handle some connection reset by peer

[ https://issues.apache.org/jira/browse/IMPALA-6159?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Ho updated IMPALA-6159: --- Affects Version/s: Impala 2.12.0 > DataStreamSender should transparently handle some connection

[jira] [Updated] (IMPALA-6159) DataStreamSender should transparently handle some connection reset by peer

[ https://issues.apache.org/jira/browse/IMPALA-6159?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Ho updated IMPALA-6159: --- Priority: Critical (was: Major) > DataStreamSender should transparently handle some connection

[jira] [Updated] (IMPALA-8138) Re-introduce rpc debugging options

[ https://issues.apache.org/jira/browse/IMPALA-8138?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Ho updated IMPALA-8138: --- Component/s: Distributed Exec > Re-introduce rpc debugging options >

[jira] [Commented] (IMPALA-8138) Re-introduce rpc debugging options

[ https://issues.apache.org/jira/browse/IMPALA-8138?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16755333#comment-16755333 ] Michael Ho commented on IMPALA-8138: We should consider switching to using DebugAction for the fault

[jira] [Created] (IMPALA-8111) Document workaround for some authentication issues with KRPC

Michael Ho created IMPALA-8111: -- Summary: Document workaround for some authentication issues with KRPC Key: IMPALA-8111 URL: https://issues.apache.org/jira/browse/IMPALA-8111 Project: IMPALA

[jira] [Commented] (IMPALA-8027) KRPC datastream timing out on both the receiver and sender side even in a minicluster

[ https://issues.apache.org/jira/browse/IMPALA-8027?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16749308#comment-16749308 ] Michael Ho commented on IMPALA-8027: The profile didn't suggest much either. The last report time

[jira] [Commented] (IMPALA-8027) KRPC datastream timing out on both the receiver and sender side even in a minicluster

[ https://issues.apache.org/jira/browse/IMPALA-8027?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16749067#comment-16749067 ] Michael Ho commented on IMPALA-8027: Looks like the coordinator seems to be slow somehow between

[jira] [Created] (IMPALA-8006) Consider replacing the modulus in KrpcDatastreamSender with fast mod

Michael Ho created IMPALA-8006: -- Summary: Consider replacing the modulus in KrpcDatastreamSender with fast mod Key: IMPALA-8006 URL: https://issues.apache.org/jira/browse/IMPALA-8006 Project: IMPALA

[jira] [Created] (IMPALA-7984) Port UpdateFilter() and PublishFilter() to KRPC

Michael Ho created IMPALA-7984: -- Summary: Port UpdateFilter() and PublishFilter() to KRPC Key: IMPALA-7984 URL: https://issues.apache.org/jira/browse/IMPALA-7984 Project: IMPALA Issue Type:

[jira] [Resolved] (IMPALA-4255) Consider deprecating support for LLVM IR UDF

[ https://issues.apache.org/jira/browse/IMPALA-4255?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Ho resolved IMPALA-4255. Resolution: Won't Fix Apparently, some users of Impala still rely on this fancy features to get

[jira] [Comment Edited] (IMPALA-6692) When partition exchange is followed by sort each sort node becomes a synchronization point across the cluster

[ https://issues.apache.org/jira/browse/IMPALA-6692?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16720709#comment-16720709 ] Michael Ho edited comment on IMPALA-6692 at 12/13/18 11:55 PM: --- {quote}

[jira] [Commented] (IMPALA-6692) When partition exchange is followed by sort each sort node becomes a synchronization point across the cluster

[ https://issues.apache.org/jira/browse/IMPALA-6692?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16720709#comment-16720709 ] Michael Ho commented on IMPALA-6692: {quote} Have we seen problems with any operators except for

[jira] [Updated] (IMPALA-6692) When partition exchange is followed by sort each sort node becomes a synchronization point across the cluster

[ https://issues.apache.org/jira/browse/IMPALA-6692?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Ho updated IMPALA-6692: --- Attachment: profile-spilling.txt > When partition exchange is followed by sort each sort node

[jira] [Resolved] (IMPALA-4889) Use sidecars for Thrift-wrapped RPC payloads

[ https://issues.apache.org/jira/browse/IMPALA-4889?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Ho resolved IMPALA-4889. Resolution: Fixed Fix Version/s: (was: Not Applicable) Impala 3.2.0

[jira] [Updated] (IMPALA-7467) Port ExecQueryFInstances() to KPRC

[ https://issues.apache.org/jira/browse/IMPALA-7467?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Ho updated IMPALA-7467: --- Target Version: Product Backlog (was: Impala 3.2.0) > Port ExecQueryFInstances() to KPRC >

[jira] [Updated] (IMPALA-3380) Add TCP timeouts to all RPCs that don't block

[ https://issues.apache.org/jira/browse/IMPALA-3380?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Ho updated IMPALA-3380: --- Target Version: Product Backlog, Impala 2.13.0 (was: Impala 2.13.0) > Add TCP timeouts to all RPCs

[jira] [Updated] (IMPALA-5119) Don't make RPCs from Coordinator::UpdateBackendExecStatus()

[ https://issues.apache.org/jira/browse/IMPALA-5119?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Ho updated IMPALA-5119: --- Target Version: Product Backlog > Don't make RPCs from Coordinator::UpdateBackendExecStatus() >

[jira] [Updated] (IMPALA-6788) Query fragments can spend lots of time starting up then fail right after "starting" all backends

[ https://issues.apache.org/jira/browse/IMPALA-6788?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Ho updated IMPALA-6788: --- Target Version: Product Backlog > Query fragments can spend lots of time starting up then fail

[jira] [Commented] (IMPALA-7931) test_shutdown_executor fails with timeout waiting for query target state

[ https://issues.apache.org/jira/browse/IMPALA-7931?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16716039#comment-16716039 ] Michael Ho commented on IMPALA-7931: [~tarmstrong], this sounds reasonable to me too. i took a

[jira] [Resolved] (IMPALA-6741) Profiles of running queries should tell last update time of counters

[ https://issues.apache.org/jira/browse/IMPALA-6741?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Ho resolved IMPALA-6741. Resolution: Fixed Fix Version/s: Impala 3.2.0 > Profiles of running queries should tell

[jira] [Resolved] (IMPALA-6754) Exchange node includes FirstBatchArrivalWaitTime in summary

[ https://issues.apache.org/jira/browse/IMPALA-6754?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Ho resolved IMPALA-6754. Resolution: Fixed Fix Version/s: Impala 2.12.0 Impala 3.1.0 The problem

[jira] [Commented] (IMPALA-6754) Exchange node includes FirstBatchArrivalWaitTime in summary

[ https://issues.apache.org/jira/browse/IMPALA-6754?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16708058#comment-16708058 ] Michael Ho commented on IMPALA-6754: Things have definitely improved with KRPC. Please find a sample

[jira] [Updated] (IMPALA-7232) Display whether fragment instances' profile is complete

[ https://issues.apache.org/jira/browse/IMPALA-7232?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Ho updated IMPALA-7232: --- Labels: supportability (was: ) > Display whether fragment instances' profile is complete >

[jira] [Updated] (IMPALA-7473) RawValue::PrintValue() hits general protection fault with VLOG level 3

[ https://issues.apache.org/jira/browse/IMPALA-7473?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Ho updated IMPALA-7473: --- Description: DecimalValue does not seem to be 16 bytes aligned and impala hits a GPF. I could only

[jira] [Updated] (IMPALA-7473) RawValue::PrintValue() hits general protection fault with VLOG level 3

[ https://issues.apache.org/jira/browse/IMPALA-7473?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Ho updated IMPALA-7473: --- Description: DecimalValue does not seem to be 16 bytes aligned and impala hits a GPF. I could only

[jira] [Updated] (IMPALA-7473) RawValue::PrintValue() hits general protection fault with VLOG level 3

[ https://issues.apache.org/jira/browse/IMPALA-7473?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Ho updated IMPALA-7473: --- Summary: RawValue::PrintValue() hits general protection fault with VLOG level 3 (was: Impala hits

[jira] [Comment Edited] (IMPALA-7903) DCHECK in RawValue::PrintValue() hit with VLOG level 3

[ https://issues.apache.org/jira/browse/IMPALA-7903?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16701189#comment-16701189 ] Michael Ho edited comment on IMPALA-7903 at 11/28/18 12:02 AM: --- Btw, we

[jira] [Commented] (IMPALA-7903) DCHECK in RawValue::PrintValue() hit with VLOG level 3

[ https://issues.apache.org/jira/browse/IMPALA-7903?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16701189#comment-16701189 ] Michael Ho commented on IMPALA-7903: Btw, we have seen similar problem in IMPALA-7473 due to

[jira] [Commented] (IMPALA-2990) Coordinator should timeout a connection for an unresponsive backend

[ https://issues.apache.org/jira/browse/IMPALA-2990?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16701132#comment-16701132 ] Michael Ho commented on IMPALA-2990: The remaining major work item (IMPALA-4555) is now owned by

[jira] [Assigned] (IMPALA-2990) Coordinator should timeout a connection for an unresponsive backend

[ https://issues.apache.org/jira/browse/IMPALA-2990?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Ho reassigned IMPALA-2990: -- Assignee: Thomas Tauber-Marshall (was: Michael Ho) > Coordinator should timeout a

[jira] [Resolved] (IMPALA-2885) Scanners store per-split objects in per-query object pool

[ https://issues.apache.org/jira/browse/IMPALA-2885?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Ho resolved IMPALA-2885. Resolution: Fixed Fix Version/s: Impala 2.7.0 The other patch I was working on was

[jira] [Assigned] (IMPALA-2797) scanner threads can act like a thundering herd

[ https://issues.apache.org/jira/browse/IMPALA-2797?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Ho reassigned IMPALA-2797: -- Assignee: (was: Michael Ho) > scanner threads can act like a thundering herd >

[jira] [Resolved] (IMPALA-7829) Send the final profile only after all fragment instances have been closed

[ https://issues.apache.org/jira/browse/IMPALA-7829?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Ho resolved IMPALA-7829. Resolution: Fixed Fix Version/s: Impala 3.2.0 > Send the final profile only after all

[jira] [Resolved] (IMPALA-7852) test_hash_join_timer flakiness on s3 testing build

[ https://issues.apache.org/jira/browse/IMPALA-7852?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Ho resolved IMPALA-7852. Resolution: Fixed Fix Version/s: Impala 3.2.0 > test_hash_join_timer flakiness on s3

[jira] [Updated] (IMPALA-7879) Final profiles of queries should be reliably retrievable

[ https://issues.apache.org/jira/browse/IMPALA-7879?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Ho updated IMPALA-7879: --- Issue Type: Improvement (was: Bug) > Final profiles of queries should be reliably retrievable >

[jira] [Created] (IMPALA-7879) Final profiles of queries should be reliably retrievable

Michael Ho created IMPALA-7879: -- Summary: Final profiles of queries should be reliably retrievable Key: IMPALA-7879 URL: https://issues.apache.org/jira/browse/IMPALA-7879 Project: IMPALA Issue

[jira] [Updated] (IMPALA-4475) Compress ExecPlanFragment before shipping it to worker nodes to reduce network traffic

[ https://issues.apache.org/jira/browse/IMPALA-4475?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Ho updated IMPALA-4475: --- A patch from [~vukercegovac] is out for review here:  https://gerrit.cloudera.org/#/c/9251/ > Compress

[jira] [Commented] (IMPALA-4475) Compress ExecPlanFragment before shipping it to worker nodes to reduce network traffic

[ https://issues.apache.org/jira/browse/IMPALA-4475?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16693818#comment-16693818 ] Michael Ho commented on IMPALA-4475: Whatever is done here will still have benefit even after

[jira] [Updated] (IMPALA-6984) Coordinator should cancel backends when returning EOS

[ https://issues.apache.org/jira/browse/IMPALA-6984?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Ho updated IMPALA-6984: --- Issue Type: Sub-task (was: Improvement) Parent: IMPALA-5486 > Coordinator should cancel

[jira] [Commented] (IMPALA-539) Impala should gather final runtime profile from fragments for aborted/cancelled query

[ https://issues.apache.org/jira/browse/IMPALA-539?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16693795#comment-16693795 ] Michael Ho commented on IMPALA-539: --- Given that we probably need a timeout for response of the

[jira] [Commented] (IMPALA-539) Impala should gather final runtime profile from fragments for aborted/cancelled query

[ https://issues.apache.org/jira/browse/IMPALA-539?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16692475#comment-16692475 ] Michael Ho commented on IMPALA-539: --- Ideally, we should always wait for all backend completion even in

[jira] [Comment Edited] (IMPALA-6984) Coordinator should cancel backends when returning EOS

[ https://issues.apache.org/jira/browse/IMPALA-6984?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16692357#comment-16692357 ] Michael Ho edited comment on IMPALA-6984 at 11/19/18 10:19 PM: --- Now that

[jira] [Commented] (IMPALA-6984) Coordinator should cancel backends when returning EOS

[ https://issues.apache.org/jira/browse/IMPALA-6984?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16692357#comment-16692357 ] Michael Ho commented on IMPALA-6984: Now that IMPALA-4063 is fixed, we should have a guarantee that

[jira] [Commented] (IMPALA-7852) test_hash_join_timer flakiness on s3 testing build

[ https://issues.apache.org/jira/browse/IMPALA-7852?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16690202#comment-16690202 ] Michael Ho commented on IMPALA-7852: This may be caused by IMPALA-4063. In particular, the

[jira] [Commented] (IMPALA-7072) Support Kerberos auth_to_local rules

[ https://issues.apache.org/jira/browse/IMPALA-7072?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16687138#comment-16687138 ] Michael Ho commented on IMPALA-7072: I think we do:

[jira] [Comment Edited] (IMPALA-7072) Support Kerberos auth_to_local rules

[ https://issues.apache.org/jira/browse/IMPALA-7072?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16687138#comment-16687138 ] Michael Ho edited comment on IMPALA-7072 at 11/14/18 9:20 PM: -- I think we

[jira] [Updated] (IMPALA-4978) Impala should set the kerberos principal to the FQDN

[ https://issues.apache.org/jira/browse/IMPALA-4978?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Ho updated IMPALA-4978: --- Labels: kerberos security (was: security) > Impala should set the kerberos principal to the FQDN >

[jira] [Updated] (IMPALA-4712) Transient kerberos authentication error during table loading requires "invalidate metadata" to resolve

[ https://issues.apache.org/jira/browse/IMPALA-4712?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Ho updated IMPALA-4712: --- Labels: catalog-server kerberos security (was: catalog-server security) > Transient kerberos

[jira] [Updated] (IMPALA-6871) SSL_shutdown: shutdown while in init

[ https://issues.apache.org/jira/browse/IMPALA-6871?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Ho updated IMPALA-6871: --- Component/s: Security > SSL_shutdown: shutdown while in init >

[jira] [Assigned] (IMPALA-7021) Impala query fails with BlockMissingException while HDFS throws SSLHandshakeException

[ https://issues.apache.org/jira/browse/IMPALA-7021?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Ho reassigned IMPALA-7021: -- Assignee: (was: Sailesh Mukil) > Impala query fails with BlockMissingException while

[jira] [Updated] (IMPALA-5023) supportability: DNS GLSB in front of IMPALA (env: Kerberos+SSL)

[ https://issues.apache.org/jira/browse/IMPALA-5023?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Ho updated IMPALA-5023: --- Labels: kerberos (was: ) > supportability: DNS GLSB in front of IMPALA (env: Kerberos+SSL) >

[jira] [Updated] (IMPALA-6071) impala-shell hang during Kerberos authentication

[ https://issues.apache.org/jira/browse/IMPALA-6071?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Ho updated IMPALA-6071: --- Labels: kerberos supportability (was: supportability) > impala-shell hang during Kerberos

[jira] [Assigned] (IMPALA-6143) Impala returns a series of SSL_connect failures during secure stress test

[ https://issues.apache.org/jira/browse/IMPALA-6143?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Ho reassigned IMPALA-6143: -- Assignee: (was: Sailesh Mukil) > Impala returns a series of SSL_connect failures during

[jira] [Updated] (IMPALA-4855) Complex query on large cluster with Kerberos+SSL enabled failed with Couldn't open transport for vd1328.foo:22000 (SASL(-1): generic failure: GSSAPI Error: Invalid token

[ https://issues.apache.org/jira/browse/IMPALA-4855?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Ho updated IMPALA-4855: --- Labels: kerberos scalability security (was: scalability security) > Complex query on large cluster

[jira] [Updated] (IMPALA-4709) [KERBEROS] Improve the error message for impala-shell on Kerberised environment with LoadBalancer

[ https://issues.apache.org/jira/browse/IMPALA-4709?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Ho updated IMPALA-4709: --- Labels: kerberos (was: ) > [KERBEROS] Improve the error message for impala-shell on Kerberised >

[jira] [Updated] (IMPALA-1770) Concurrent query right after impala restart can cause connection error in a secure cluster

[ https://issues.apache.org/jira/browse/IMPALA-1770?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Ho updated IMPALA-1770: --- Labels: kerberos security (was: security) > Concurrent query right after impala restart can cause

[jira] [Updated] (IMPALA-3189) Address scalability issue with N^2 KDC requests on cluster startup

[ https://issues.apache.org/jira/browse/IMPALA-3189?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Ho updated IMPALA-3189: --- Labels: kerberos (was: ) > Address scalability issue with N^2 KDC requests on cluster startup >

[jira] [Updated] (IMPALA-7650) Enable Kerberos by default for mini-cluster test

[ https://issues.apache.org/jira/browse/IMPALA-7650?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Ho updated IMPALA-7650: --- Labels: kerbreos (was: ) > Enable Kerberos by default for mini-cluster test >

[jira] [Updated] (IMPALA-7650) Enable Kerberos by default for mini-cluster test

[ https://issues.apache.org/jira/browse/IMPALA-7650?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Ho updated IMPALA-7650: --- Labels: kerberos (was: kerbreos) > Enable Kerberos by default for mini-cluster test >

[jira] [Updated] (IMPALA-7638) Lower default timeout for connection setup

[ https://issues.apache.org/jira/browse/IMPALA-7638?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Ho updated IMPALA-7638: --- Labels: kerberos (was: ) > Lower default timeout for connection setup >

[jira] [Resolved] (IMPALA-4860) Stagger impala TGS_REQ to KDC

[ https://issues.apache.org/jira/browse/IMPALA-4860?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Ho resolved IMPALA-4860. Resolution: Duplicate Fix Version/s: Not Applicable > Stagger impala TGS_REQ to KDC >

[jira] [Updated] (IMPALA-3189) Address scalability issue with N^2 KDC requests on cluster startup

[ https://issues.apache.org/jira/browse/IMPALA-3189?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Ho updated IMPALA-3189: --- Labels: kerberos scalability (was: kerberos) > Address scalability issue with N^2 KDC requests on

[jira] [Assigned] (IMPALA-3189) Address scalability issue with N^2 KDC requests on cluster startup

[ https://issues.apache.org/jira/browse/IMPALA-3189?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Ho reassigned IMPALA-3189: -- Assignee: (was: Henry Robinson) > Address scalability issue with N^2 KDC requests on

[jira] [Updated] (IMPALA-7072) Support Kerberos auth_to_local rules

[ https://issues.apache.org/jira/browse/IMPALA-7072?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Ho updated IMPALA-7072: --- Labels: kerberos (was: ) > Support Kerberos auth_to_local rules >

[jira] [Updated] (IMPALA-4860) Stagger impala TGS_REQ to KDC

[ https://issues.apache.org/jira/browse/IMPALA-4860?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Ho updated IMPALA-4860: --- Labels: kerberos scalability supportability (was: scalability supportability) > Stagger impala

[jira] [Updated] (IMPALA-6143) Impala returns a series of SSL_connect failures during secure stress test

[ https://issues.apache.org/jira/browse/IMPALA-6143?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Ho updated IMPALA-6143: --- Labels: kerberos (was: ) > Impala returns a series of SSL_connect failures during secure stress

[jira] [Commented] (IMPALA-4069) Introduce startup option to create and cache backend connections on startup

[ https://issues.apache.org/jira/browse/IMPALA-4069?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16687018#comment-16687018 ] Michael Ho commented on IMPALA-4069: Now that IMPALA-7213 and IMPALA-4063 are fixed, the number of

[jira] [Assigned] (IMPALA-7072) Support Kerberos auth_to_local rules

[ https://issues.apache.org/jira/browse/IMPALA-7072?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Ho reassigned IMPALA-7072: -- Assignee: (was: Sailesh Mukil) > Support Kerberos auth_to_local rules >

[jira] [Assigned] (IMPALA-4978) Impala should set the kerberos principal to the FQDN

[ https://issues.apache.org/jira/browse/IMPALA-4978?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Ho reassigned IMPALA-4978: -- Assignee: (was: Sailesh Mukil) > Impala should set the kerberos principal to the FQDN >

[jira] [Resolved] (IMPALA-4855) Complex query on large cluster with Kerberos+SSL enabled failed with Couldn't open transport for vd1328.foo:22000 (SASL(-1): generic failure: GSSAPI Error: Invalid toke

[ https://issues.apache.org/jira/browse/IMPALA-4855?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Ho resolved IMPALA-4855. Resolution: Cannot Reproduce Fix Version/s: Not Applicable Things have changed quite a lot

[jira] [Assigned] (IMPALA-5904) Enable ThreadSanitizer for Impala

[ https://issues.apache.org/jira/browse/IMPALA-5904?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Ho reassigned IMPALA-5904: -- Assignee: (was: Michal Ostrowski) > Enable ThreadSanitizer for Impala >

[jira] [Assigned] (IMPALA-6852) Add a section to the query profile covering number of fragments and total bytes scanned per host

[ https://issues.apache.org/jira/browse/IMPALA-6852?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Ho reassigned IMPALA-6852: -- Assignee: (was: Michal Ostrowski) > Add a section to the query profile covering number

[jira] [Assigned] (IMPALA-7183) We should print the sender name when logging a report for an unknown status report on the coordinatior

[ https://issues.apache.org/jira/browse/IMPALA-7183?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Ho reassigned IMPALA-7183: -- Assignee: (was: Michal Ostrowski) > We should print the sender name when logging a

[jira] [Assigned] (IMPALA-6590) Disable expr rewrites and codegen for VALUES() statements

[ https://issues.apache.org/jira/browse/IMPALA-6590?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Ho reassigned IMPALA-6590: -- Assignee: (was: Michal Ostrowski) > Disable expr rewrites and codegen for VALUES()

[jira] [Assigned] (IMPALA-2515) Impala is unable to read a Parquet decimal column if size is larger than needed

[ https://issues.apache.org/jira/browse/IMPALA-2515?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Ho reassigned IMPALA-2515: -- Assignee: (was: Michal Ostrowski) > Impala is unable to read a Parquet decimal column if

[jira] [Resolved] (IMPALA-7148) test_profile_fragment_instances is flaky

[ https://issues.apache.org/jira/browse/IMPALA-7148?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Ho resolved IMPALA-7148. Resolution: Fixed Fix Version/s: Impala 3.2.0 All tests have been re-enabled and the flaky

[jira] [Resolved] (IMPALA-7828) test_mem_leak() is flaky

[ https://issues.apache.org/jira/browse/IMPALA-7828?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Ho resolved IMPALA-7828. Resolution: Fixed Fix Version/s: Impala 3.2.0 Workaround has been merged. >

[jira] [Commented] (IMPALA-7148) Re-enable tests disabled in IMPALA-6338

[ https://issues.apache.org/jira/browse/IMPALA-7148?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16678707#comment-16678707 ] Michael Ho commented on IMPALA-7148: All the tests have been re-enabled now that IMPALA-4063 has

[jira] [Updated] (IMPALA-7148) Re-enable tests disabled in IMPALA-6338

[ https://issues.apache.org/jira/browse/IMPALA-7148?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Ho updated IMPALA-7148: --- Description: The underlying bug in IMPALA-6338 was causing a large number of flaky tests and was

[jira] [Updated] (IMPALA-7148) test_profile_fragment_instances is flaky

[ https://issues.apache.org/jira/browse/IMPALA-7148?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Ho updated IMPALA-7148: --- Summary: test_profile_fragment_instances is flaky (was: Re-enable tests disabled in IMPALA-6338)

[jira] [Created] (IMPALA-7829) Send the final profile only after all fragment instances have been closed

Michael Ho created IMPALA-7829: -- Summary: Send the final profile only after all fragment instances have been closed Key: IMPALA-7829 URL: https://issues.apache.org/jira/browse/IMPALA-7829 Project:

[jira] [Updated] (IMPALA-7828) test_mem_leak() is flaky

[ https://issues.apache.org/jira/browse/IMPALA-7828?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Ho updated IMPALA-7828: --- Description: Before IMPALA-4063, the error message detected during

[jira] [Created] (IMPALA-7828) test_mem_leak() is flaky

Michael Ho created IMPALA-7828: -- Summary: test_mem_leak() is flaky Key: IMPALA-7828 URL: https://issues.apache.org/jira/browse/IMPALA-7828 Project: IMPALA Issue Type: Bug Components:

[jira] [Resolved] (IMPALA-7810) query-state.cc:295] Check failed: profile_buf == nullptr

[ https://issues.apache.org/jira/browse/IMPALA-7810?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Ho resolved IMPALA-7810. Resolution: Fixed Fix Version/s: Impala 3.2.0 Fixed at this commit

[jira] [Resolved] (IMPALA-4063) Make fragment instance reports per-query (or per-host) instead of per-fragment instance.

[ https://issues.apache.org/jira/browse/IMPALA-4063?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Ho resolved IMPALA-4063. Resolution: Fixed Fix Version/s: Impala 3.2.0 The proposed release of Impala 3.1.0 will

[jira] [Updated] (IMPALA-7810) query-state.cc:295] Check failed: profile_buf == nullptr

[ https://issues.apache.org/jira/browse/IMPALA-7810?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Ho updated IMPALA-7810: --- Labels: broken-build (was: ) > query-state.cc:295] Check failed: profile_buf == nullptr >

[jira] [Created] (IMPALA-7810) query-state.cc:295] Check failed: profile_buf == nullptr

Michael Ho created IMPALA-7810: -- Summary: query-state.cc:295] Check failed: profile_buf == nullptr Key: IMPALA-7810 URL: https://issues.apache.org/jira/browse/IMPALA-7810 Project: IMPALA Issue

[jira] [Resolved] (IMPALA-7241) progress-updater.cc:43] Check failed: delta >= 0 (-3 vs. 0)

[ https://issues.apache.org/jira/browse/IMPALA-7241?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Ho resolved IMPALA-7241. Resolution: Fixed Fix Version/s: Impala 3.2.0 > progress-updater.cc:43] Check failed:

[jira] [Created] (IMPALA-7802) Implement support for closing idle sessions

Michael Ho created IMPALA-7802: -- Summary: Implement support for closing idle sessions Key: IMPALA-7802 URL: https://issues.apache.org/jira/browse/IMPALA-7802 Project: IMPALA Issue Type:

[jira] [Resolved] (IMPALA-7379) test_random_rpc_timeout failed on exhaustive build: Debug webpage did not become available in expected time

[ https://issues.apache.org/jira/browse/IMPALA-7379?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Ho resolved IMPALA-7379. Resolution: Cannot Reproduce Fix Version/s: Not Applicable > test_random_rpc_timeout

[jira] [Commented] (IMPALA-7379) test_random_rpc_timeout failed on exhaustive build: Debug webpage did not become available in expected time

[ https://issues.apache.org/jira/browse/IMPALA-7379?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16672345#comment-16672345 ] Michael Ho commented on IMPALA-7379: This hasn't happened for a while. The [fix for

[jira] [Resolved] (IMPALA-7213) Port ReportExecStatus() RPCs to KRPC

[ https://issues.apache.org/jira/browse/IMPALA-7213?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Ho resolved IMPALA-7213. Resolution: Fixed Fix Version/s: Impala 3.2.0 > Port ReportExecStatus() RPCs to KRPC >

[jira] [Created] (IMPALA-7800) Reject or timeout new incoming connections once --fe_service_threads limit is reached

Michael Ho created IMPALA-7800: -- Summary: Reject or timeout new incoming connections once --fe_service_threads limit is reached Key: IMPALA-7800 URL: https://issues.apache.org/jira/browse/IMPALA-7800

[jira] [Comment Edited] (IMPALA-7799) Store periodic snapshots of Impalad metrics

[ https://issues.apache.org/jira/browse/IMPALA-7799?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16672294#comment-16672294 ] Michael Ho edited comment on IMPALA-7799 at 11/1/18 10:15 PM: -- Yes,

[jira] [Commented] (IMPALA-7799) Store periodic snapshots of Impalad metrics

[ https://issues.apache.org/jira/browse/IMPALA-7799?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16672294#comment-16672294 ] Michael Ho commented on IMPALA-7799: Yes, something simple should suffice. > Store periodic

[jira] [Updated] (IMPALA-7799) Store periodic snapshots of Impalad metrics

[ https://issues.apache.org/jira/browse/IMPALA-7799?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Ho updated IMPALA-7799: --- Description: Currently, each Impala demon exposes a set of metrics exposed via the debug webpage

[jira] [Created] (IMPALA-7799) Store periodic snapshots of Impalad metrics

Michael Ho created IMPALA-7799: -- Summary: Store periodic snapshots of Impalad metrics Key: IMPALA-7799 URL: https://issues.apache.org/jira/browse/IMPALA-7799 Project: IMPALA Issue Type:

[jira] [Updated] (IMPALA-7732) Check / Implement resource limits documented in IMPALA-5605

[ https://issues.apache.org/jira/browse/IMPALA-7732?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Ho updated IMPALA-7732: --- Target Version: Impala 3.2.0 (was: Impala 3.1.0) > Check / Implement resource limits documented in

[jira] [Comment Edited] (IMPALA-7565) Extends TAcceptQueueServer connection_setup_pool to be multi-threaded

[ https://issues.apache.org/jira/browse/IMPALA-7565?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16667597#comment-16667597 ] Michael Ho edited comment on IMPALA-7565 at 10/29/18 6:56 PM: -- A minor

<    1   2   3   4   5   >