[jira] [Commented] (TEZ-3985) Correctness: Throw a clear exception for DMEs sent during cleanup

2019-02-08 Thread Gopal V (JIRA)
[ https://issues.apache.org/jira/browse/TEZ-3985?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16763925#comment-16763925 ] Gopal V commented on TEZ-3985: -- Fixed minor nits. > Correctness: Throw a clear exception for DMEs sent during

[jira] [Assigned] (TEZ-4038) Add a /prof profiler endpoint like HiveServer2 has

2019-02-08 Thread Gopal V (JIRA)
[ https://issues.apache.org/jira/browse/TEZ-4038?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gopal V reassigned TEZ-4038: Assignee: Gopal V > Add a /prof profiler endpoint like HiveServer2 has >

[jira] [Assigned] (TEZ-4033) Add a -Pozone flag to include Ozone/HDDS

2019-01-28 Thread Gopal V (JIRA)
[ https://issues.apache.org/jira/browse/TEZ-4033?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gopal V reassigned TEZ-4033: Assignee: Gopal V > Add a -Pozone flag to include Ozone/HDDS > - >

[jira] [Updated] (TEZ-4033) Add a -Pozone flag to include Ozone/HDDS

2019-01-28 Thread Gopal V (JIRA)
[ https://issues.apache.org/jira/browse/TEZ-4033?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gopal V updated TEZ-4033: - Issue Type: New Feature (was: Bug) > Add a -Pozone flag to include Ozone/HDDS >

[jira] [Created] (TEZ-4033) Add a -Pozone flag to include Ozone/HDDS

2019-01-28 Thread Gopal V (JIRA)
Gopal V created TEZ-4033: Summary: Add a -Pozone flag to include Ozone/HDDS Key: TEZ-4033 URL: https://issues.apache.org/jira/browse/TEZ-4033 Project: Apache Tez Issue Type: Bug

[jira] [Commented] (TEZ-4028) Events not visible from proto history logging for s3a filesystem until dag completes.

2019-01-25 Thread Gopal V (JIRA)
[ https://issues.apache.org/jira/browse/TEZ-4028?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16752776#comment-16752776 ] Gopal V commented on TEZ-4028: -- LGTM - +1 The DAG now gets a flush the moment it starts, so that the configs

[jira] [Commented] (TEZ-4073) Configuration: Reduce Vertex and DAG Payload Size

2019-05-31 Thread Gopal V (JIRA)
[ https://issues.apache.org/jira/browse/TEZ-4073?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16853529#comment-16853529 ] Gopal V commented on TEZ-4073: -- We can also differentiate between the configs set via HiveConf::initialize()

[jira] [Commented] (TEZ-4073) Configuration: Reduce Vertex and DAG Payload Size

2019-05-31 Thread Gopal V (JIRA)
[ https://issues.apache.org/jira/browse/TEZ-4073?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16853527#comment-16853527 ] Gopal V commented on TEZ-4073: -- The trivial version of this is to skip all the configs which have *.xml when

[jira] [Comment Edited] (TEZ-4073) Configuration: Reduce Vertex and DAG Payload Size

2019-05-30 Thread Gopal V (JIRA)
[ https://issues.apache.org/jira/browse/TEZ-4073?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16851545#comment-16851545 ] Gopal V edited comment on TEZ-4073 at 5/30/19 6:07 AM: --- Async dispatcher CPU is

[jira] [Updated] (TEZ-4073) Configuration: Reduce Vertex and DAG Payload Size

2019-05-30 Thread Gopal V (JIRA)
[ https://issues.apache.org/jira/browse/TEZ-4073?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gopal V updated TEZ-4073: - Description: As the total number of vertices go up, the Tez protobuf transport starts to show up as a potential

[jira] [Updated] (TEZ-4073) Configuration: Reduce Vertex and DAG Payload Size

2019-05-30 Thread Gopal V (JIRA)
[ https://issues.apache.org/jira/browse/TEZ-4073?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gopal V updated TEZ-4073: - Attachment: tez-am-protobuf-reading.png > Configuration: Reduce Vertex and DAG Payload Size >

[jira] [Commented] (TEZ-4073) Configuration: Reduce Vertex and DAG Payload Size

2019-05-30 Thread Gopal V (JIRA)
[ https://issues.apache.org/jira/browse/TEZ-4073?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16851545#comment-16851545 ] Gopal V commented on TEZ-4073: -- Async dispatcher CPU is mostly spent on the protobuf codepaths. >

[jira] [Updated] (TEZ-4073) Configuration: Reduce Vertex and DAG Payload Size

2019-05-30 Thread Gopal V (JIRA)
[ https://issues.apache.org/jira/browse/TEZ-4073?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gopal V updated TEZ-4073: - Attachment: tez-protobuf-writing.png > Configuration: Reduce Vertex and DAG Payload Size >

[jira] [Created] (TEZ-4073) Configuration: Reduce Vertex and DAG Payload Size

2019-05-30 Thread Gopal V (JIRA)
Gopal V created TEZ-4073: Summary: Configuration: Reduce Vertex and DAG Payload Size Key: TEZ-4073 URL: https://issues.apache.org/jira/browse/TEZ-4073 Project: Apache Tez Issue Type: Bug

[jira] [Commented] (TEZ-4073) Configuration: Reduce Vertex and DAG Payload Size

2019-06-01 Thread Gopal V (JIRA)
[ https://issues.apache.org/jira/browse/TEZ-4073?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16853602#comment-16853602 ] Gopal V commented on TEZ-4073: -- The HiveConf source annotation, allows for a source filter version of {{public

[jira] [Commented] (TEZ-4075) Tez: Reimplement tez.runtime.transfer.data-via-events.enabled

2019-06-20 Thread Gopal V (JIRA)
[ https://issues.apache.org/jira/browse/TEZ-4075?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16868950#comment-16868950 ] Gopal V commented on TEZ-4075: -- The corresponding test-scenario for this is

[jira] [Created] (TEZ-4075) Tez: Reimplement tez.runtime.transfer.data-via-events.enabled

2019-06-20 Thread Gopal V (JIRA)
Gopal V created TEZ-4075: Summary: Tez: Reimplement tez.runtime.transfer.data-via-events.enabled Key: TEZ-4075 URL: https://issues.apache.org/jira/browse/TEZ-4075 Project: Apache Tez Issue Type:

[jira] [Commented] (TEZ-3310) Handle splits grouping better when locality information is not available (or only when localhost is available)

2019-05-06 Thread Gopal V (JIRA)
[ https://issues.apache.org/jira/browse/TEZ-3310?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16833956#comment-16833956 ] Gopal V commented on TEZ-3310: -- The reason "localhost" is scrubbed is because RM was waiting for "localhost"

[jira] [Commented] (TEZ-4076) Add hadoop-cloud-storage jar to aws and azure mvn profiles

2019-07-10 Thread Gopal V (JIRA)
[ https://issues.apache.org/jira/browse/TEZ-4076?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16882550#comment-16882550 ] Gopal V commented on TEZ-4076: -- LGTM - +1 > Add hadoop-cloud-storage jar to aws and azure mvn profiles >

[jira] [Assigned] (TEZ-4076) Add hadoop-cloud-storage jar to aws and azure mvn profiles

2019-07-10 Thread Gopal V (JIRA)
[ https://issues.apache.org/jira/browse/TEZ-4076?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gopal V reassigned TEZ-4076: Assignee: Jesus Camacho Rodriguez > Add hadoop-cloud-storage jar to aws and azure mvn profiles >

[jira] [Updated] (TEZ-4076) Add hadoop-cloud-storage jar to aws and azure mvn profiles

2019-07-16 Thread Gopal V (JIRA)
[ https://issues.apache.org/jira/browse/TEZ-4076?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gopal V updated TEZ-4076: - Fix Version/s: 0.10.1 > Add hadoop-cloud-storage jar to aws and azure mvn profiles >

<    1   2   3   4   5   6