[jira] [Updated] (TEZ-3637) TezMerger logs too much on INFO level
[ https://issues.apache.org/jira/browse/TEZ-3637?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Siddharth Seth updated TEZ-3637: Attachment: TEZ-3637.01.patch Moves a bunch of stuff to debug level. Aggregates some info logs. Logs at info level at an interval (if a closeInMemFile / closeOnDiskFile) happens after the interval. [~rajesh.balamohan], [~harishjp] - could you please take a look. > TezMerger logs too much on INFO level > - > > Key: TEZ-3637 > URL: https://issues.apache.org/jira/browse/TEZ-3637 > Project: Apache Tez > Issue Type: Bug >Reporter: Sergey Shelukhin >Assignee: Siddharth Seth > Attachments: TEZ-3637.01.patch > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (TEZ-3637) TezMerger logs too much on INFO level
[ https://issues.apache.org/jira/browse/TEZ-3637?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Siddharth Seth updated TEZ-3637: Target Version/s: 0.9.0 Fix Version/s: (was: 0.9.0) > TezMerger logs too much on INFO level > - > > Key: TEZ-3637 > URL: https://issues.apache.org/jira/browse/TEZ-3637 > Project: Apache Tez > Issue Type: Bug >Reporter: Sergey Shelukhin >Assignee: Siddharth Seth > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (TEZ-3636) Tez UI: Move status strings to individual models
[ https://issues.apache.org/jira/browse/TEZ-3636?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sreenath Somarajapuram updated TEZ-3636: Attachment: TEZ-3636.1.patch [~sseth] Please let me know if this looks good. > Tez UI: Move status strings to individual models > > > Key: TEZ-3636 > URL: https://issues.apache.org/jira/browse/TEZ-3636 > Project: Apache Tez > Issue Type: Bug >Reporter: Sreenath Somarajapuram >Assignee: Sreenath Somarajapuram > Attachments: TEZ-3636.1.patch > > > Right now status check for completion of all entities (App, DAG, Vertex etc) > is handled by one single function definition @ > https://github.com/apache/tez/blob/master/tez-ui/src/main/webapp/app/models/abstract.js#L49 > As per the discussions that happened @ > https://issues.apache.org/jira/browse/TEZ-3630?focusedCommentId=15879901=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-15879901 > I'm creating this ticket to move the status strings to each of the > respective data model. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (TEZ-3637) TezMerger logs too much
[ https://issues.apache.org/jira/browse/TEZ-3637?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sergey Shelukhin updated TEZ-3637: -- Fix Version/s: 0.9.0 > TezMerger logs too much > --- > > Key: TEZ-3637 > URL: https://issues.apache.org/jira/browse/TEZ-3637 > Project: Apache Tez > Issue Type: Bug >Reporter: Sergey Shelukhin >Assignee: Siddharth Seth > Fix For: 0.9.0 > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (TEZ-3637) TezMerger logs too much on INFO level
[ https://issues.apache.org/jira/browse/TEZ-3637?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sergey Shelukhin updated TEZ-3637: -- Summary: TezMerger logs too much on INFO level (was: TezMerger logs too much) > TezMerger logs too much on INFO level > - > > Key: TEZ-3637 > URL: https://issues.apache.org/jira/browse/TEZ-3637 > Project: Apache Tez > Issue Type: Bug >Reporter: Sergey Shelukhin >Assignee: Siddharth Seth > Fix For: 0.9.0 > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (TEZ-3637) TezMerger logs too much
Sergey Shelukhin created TEZ-3637: - Summary: TezMerger logs too much Key: TEZ-3637 URL: https://issues.apache.org/jira/browse/TEZ-3637 Project: Apache Tez Issue Type: Bug Reporter: Sergey Shelukhin Assignee: Siddharth Seth -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (TEZ-3503) Tez UI: Support search by queue name
[ https://issues.apache.org/jira/browse/TEZ-3503?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sreenath Somarajapuram updated TEZ-3503: Attachment: TEZ-3503.3.patch [~sseth] Attaching a rebased patch. But there is a confusing item now. When the queueName is missing we load it from the AHS and display. In this case if the user search with a visible queue name, no records would be displayed. That would feel like a bug. - Should we display "Not Available!" instead of loading from AHS? - And just display it in the DAG details page? > Tez UI: Support search by queue name > > > Key: TEZ-3503 > URL: https://issues.apache.org/jira/browse/TEZ-3503 > Project: Apache Tez > Issue Type: Bug >Reporter: Sreenath Somarajapuram >Assignee: Sreenath Somarajapuram > Attachments: TEZ-3503.1.patch, TEZ-3503.2.patch, TEZ-3503.3.patch > > > - Support search by queue name in All DAGs table > - Use queue from DAG info and display the value in Queue column > - If not available in DAG info, take it form AHS. > - Display queue name in DAG details page. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (TEZ-3636) Tez UI: Move status strings to individual models
[ https://issues.apache.org/jira/browse/TEZ-3636?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sreenath Somarajapuram updated TEZ-3636: Target Version/s: 0.9.0 > Tez UI: Move status strings to individual models > > > Key: TEZ-3636 > URL: https://issues.apache.org/jira/browse/TEZ-3636 > Project: Apache Tez > Issue Type: Bug >Reporter: Sreenath Somarajapuram >Assignee: Sreenath Somarajapuram > > Right now status check for completion of all entities (App, DAG, Vertex etc) > is handled by one single function definition @ > https://github.com/apache/tez/blob/master/tez-ui/src/main/webapp/app/models/abstract.js#L49 > As per the discussions that happened @ > https://issues.apache.org/jira/browse/TEZ-3630?focusedCommentId=15879901=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-15879901 > I'm creating this ticket to move the status strings to each of the > respective data model. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (TEZ-3636) Tez UI: Move status strings to individual models
Sreenath Somarajapuram created TEZ-3636: --- Summary: Tez UI: Move status strings to individual models Key: TEZ-3636 URL: https://issues.apache.org/jira/browse/TEZ-3636 Project: Apache Tez Issue Type: Bug Reporter: Sreenath Somarajapuram Assignee: Sreenath Somarajapuram Right now status check for completion of all entities (App, DAG, Vertex etc) is handled by one single function definition @ https://github.com/apache/tez/blob/master/tez-ui/src/main/webapp/app/models/abstract.js#L49 As per the discussions that happened @ https://issues.apache.org/jira/browse/TEZ-3630?focusedCommentId=15879901=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-15879901 I'm creating this ticket to move the status strings to each of the respective data model. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (TEZ-3633) Implement keep-alive timeout in tez shuffle handler
[ https://issues.apache.org/jira/browse/TEZ-3633?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15880617#comment-15880617 ] Jonathan Eagles commented on TEZ-3633: -- [~rajesh.balamohan], I will go ahead and file a MapReduce jira and port the patch as well. > Implement keep-alive timeout in tez shuffle handler > --- > > Key: TEZ-3633 > URL: https://issues.apache.org/jira/browse/TEZ-3633 > Project: Apache Tez > Issue Type: Sub-task >Reporter: Jonathan Eagles >Assignee: Jonathan Eagles > Attachments: TEZ-3633.1.patch, with_hadoop_2.7.3.png > > > MAPREDUCE-5787 which added keep-alive to mapreduce shuffle handler was not > fully functional as despite advertising keep-alive option and adding the > header to the response, all connections were closed immediately after write. > This reduced the performance of certain fetches as now time is spent > requesting a second get to the same serve, only for that server to reset the > connection forcing the client to reestablish the connection on another port. > The details of this is hidden behind HttpURLConnection and doesn't show in > any log file at default logging level. However TCP sniffing does show errant > behavior. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (TEZ-3633) Implement keep-alive timeout in tez shuffle handler
[ https://issues.apache.org/jira/browse/TEZ-3633?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15880508#comment-15880508 ] Jason Lowe commented on TEZ-3633: - The original keep-alive patch simply attached the keep-alive header and expected Netty to automatically do something different if it was there. The patch didn't have any changes to prevent the connection from closing immediately after the transfer if keep-alive was enabled nor idle connection logic to make sure the connection eventually closed. > Implement keep-alive timeout in tez shuffle handler > --- > > Key: TEZ-3633 > URL: https://issues.apache.org/jira/browse/TEZ-3633 > Project: Apache Tez > Issue Type: Sub-task >Reporter: Jonathan Eagles >Assignee: Jonathan Eagles > Attachments: TEZ-3633.1.patch, with_hadoop_2.7.3.png > > > MAPREDUCE-5787 which added keep-alive to mapreduce shuffle handler was not > fully functional as despite advertising keep-alive option and adding the > header to the response, all connections were closed immediately after write. > This reduced the performance of certain fetches as now time is spent > requesting a second get to the same serve, only for that server to reset the > connection forcing the client to reestablish the connection on another port. > The details of this is hidden behind HttpURLConnection and doesn't show in > any log file at default logging level. However TCP sniffing does show errant > behavior. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
