[jira] [Resolved] (KNOX-1744) [Spark History UI Service] Executor logs (stdout/stderr) links are broken
[
https://issues.apache.org/jira/browse/KNOX-1744?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sandeep More resolved KNOX-1744.
Resolution: Fixed
> [Spark History UI Service] Executor logs (stdout/stderr) links are broken
> --
>
> Key: KNOX-1744
> URL: https://issues.apache.org/jira/browse/KNOX-1744
> Project: Apache Knox
> Issue Type: Bug
>Affects Versions: 1.2.0
>Reporter: Nicolas Colomer
>Priority: Minor
> Fix For: 1.4.0
>
> Attachments: image-2019-01-22-13-04-53-935.png,
> image-2019-01-22-13-11-55-412.png
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> The executor logs (stdout/stderr) links from the Yarn UI Service all directly
> points to the slaves nodes.
> !image-2019-01-22-13-11-55-412.png!
> Eg. the link:
> {noformat}
> http://emr-slave-hostname:8042/node/containerlogs/container_1547901130703_0034_01_01/hadoop/stdout?start=-4096{noformat}
> Should have been instead:
> {noformat}
> https://knox/gateway/cluster/yarn/nodemanager/node/containerlogs/container_1547901130703_0034_01_01/hadoop?scheme=http&host=emr-slave-hostname&port=8042{noformat}
> And finally respect pattern:
> {noformat}
> https://knox/gateway/emr/yarn/nodemanager/node/containerlogs/{your container
> id}/hadoop?scheme=http&host={executor host}&port=8042 {noformat}
> I guess adding some voodoo in the Knox yarnui's
> [rewrite.xml|https://github.com/apache/knox/blob/master/gateway-service-definitions/src/main/resources/services/yarnui/2.7.0/rewrite.xml]
> file might be enough to fix this.
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
[jira] [Commented] (KNOX-1744) [Spark History UI Service] Executor logs (stdout/stderr) links are broken
[
https://issues.apache.org/jira/browse/KNOX-1744?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16887556#comment-16887556
]
Sandeep More commented on KNOX-1744:
Thanks [~ankur.gupta] for your contribution, the fix is in master.
> [Spark History UI Service] Executor logs (stdout/stderr) links are broken
> --
>
> Key: KNOX-1744
> URL: https://issues.apache.org/jira/browse/KNOX-1744
> Project: Apache Knox
> Issue Type: Bug
>Affects Versions: 1.2.0
>Reporter: Nicolas Colomer
>Priority: Minor
> Fix For: 1.4.0
>
> Attachments: image-2019-01-22-13-04-53-935.png,
> image-2019-01-22-13-11-55-412.png
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> The executor logs (stdout/stderr) links from the Yarn UI Service all directly
> points to the slaves nodes.
> !image-2019-01-22-13-11-55-412.png!
> Eg. the link:
> {noformat}
> http://emr-slave-hostname:8042/node/containerlogs/container_1547901130703_0034_01_01/hadoop/stdout?start=-4096{noformat}
> Should have been instead:
> {noformat}
> https://knox/gateway/cluster/yarn/nodemanager/node/containerlogs/container_1547901130703_0034_01_01/hadoop?scheme=http&host=emr-slave-hostname&port=8042{noformat}
> And finally respect pattern:
> {noformat}
> https://knox/gateway/emr/yarn/nodemanager/node/containerlogs/{your container
> id}/hadoop?scheme=http&host={executor host}&port=8042 {noformat}
> I guess adding some voodoo in the Knox yarnui's
> [rewrite.xml|https://github.com/apache/knox/blob/master/gateway-service-definitions/src/main/resources/services/yarnui/2.7.0/rewrite.xml]
> file might be enough to fix this.
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
[GitHub] [knox] moresandeep merged pull request #120: KNOX-1744 - Add rewrite rules to fix executor stdout/stderr links in Spark History Server UI
moresandeep merged pull request #120: KNOX-1744 - Add rewrite rules to fix executor stdout/stderr links in Spark History Server UI URL: https://github.com/apache/knox/pull/120 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[jira] [Work logged] (KNOX-1744) [Spark History UI Service] Executor logs (stdout/stderr) links are broken
[
https://issues.apache.org/jira/browse/KNOX-1744?focusedWorklogId=278666&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-278666
]
ASF GitHub Bot logged work on KNOX-1744:
Author: ASF GitHub Bot
Created on: 18/Jul/19 02:34
Start Date: 18/Jul/19 02:34
Worklog Time Spent: 10m
Work Description: moresandeep commented on pull request #120: KNOX-1744 -
Add rewrite rules to fix executor stdout/stderr links in Spark History Server UI
URL: https://github.com/apache/knox/pull/120
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
Issue Time Tracking
---
Worklog Id: (was: 278666)
Time Spent: 0.5h (was: 20m)
> [Spark History UI Service] Executor logs (stdout/stderr) links are broken
> --
>
> Key: KNOX-1744
> URL: https://issues.apache.org/jira/browse/KNOX-1744
> Project: Apache Knox
> Issue Type: Bug
>Affects Versions: 1.2.0
>Reporter: Nicolas Colomer
>Priority: Minor
> Fix For: 1.4.0
>
> Attachments: image-2019-01-22-13-04-53-935.png,
> image-2019-01-22-13-11-55-412.png
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> The executor logs (stdout/stderr) links from the Yarn UI Service all directly
> points to the slaves nodes.
> !image-2019-01-22-13-11-55-412.png!
> Eg. the link:
> {noformat}
> http://emr-slave-hostname:8042/node/containerlogs/container_1547901130703_0034_01_01/hadoop/stdout?start=-4096{noformat}
> Should have been instead:
> {noformat}
> https://knox/gateway/cluster/yarn/nodemanager/node/containerlogs/container_1547901130703_0034_01_01/hadoop?scheme=http&host=emr-slave-hostname&port=8042{noformat}
> And finally respect pattern:
> {noformat}
> https://knox/gateway/emr/yarn/nodemanager/node/containerlogs/{your container
> id}/hadoop?scheme=http&host={executor host}&port=8042 {noformat}
> I guess adding some voodoo in the Knox yarnui's
> [rewrite.xml|https://github.com/apache/knox/blob/master/gateway-service-definitions/src/main/resources/services/yarnui/2.7.0/rewrite.xml]
> file might be enough to fix this.
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
[jira] [Commented] (KNOX-1744) [Spark History UI Service] Executor logs (stdout/stderr) links are broken
[
https://issues.apache.org/jira/browse/KNOX-1744?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16887555#comment-16887555
]
ASF subversion and git services commented on KNOX-1744:
---
Commit 40485c5ac3edb492ffd2494d03f3a46f6eab23dd in knox's branch
refs/heads/master from Ankur Gupta
[ https://gitbox.apache.org/repos/asf?p=knox.git;h=40485c5 ]
KNOX-1744 - Add rewrite rules to fix executor stdout/stderr links in Spark
History Server UI (#120)
> [Spark History UI Service] Executor logs (stdout/stderr) links are broken
> --
>
> Key: KNOX-1744
> URL: https://issues.apache.org/jira/browse/KNOX-1744
> Project: Apache Knox
> Issue Type: Bug
>Affects Versions: 1.2.0
>Reporter: Nicolas Colomer
>Priority: Minor
> Fix For: 1.4.0
>
> Attachments: image-2019-01-22-13-04-53-935.png,
> image-2019-01-22-13-11-55-412.png
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> The executor logs (stdout/stderr) links from the Yarn UI Service all directly
> points to the slaves nodes.
> !image-2019-01-22-13-11-55-412.png!
> Eg. the link:
> {noformat}
> http://emr-slave-hostname:8042/node/containerlogs/container_1547901130703_0034_01_01/hadoop/stdout?start=-4096{noformat}
> Should have been instead:
> {noformat}
> https://knox/gateway/cluster/yarn/nodemanager/node/containerlogs/container_1547901130703_0034_01_01/hadoop?scheme=http&host=emr-slave-hostname&port=8042{noformat}
> And finally respect pattern:
> {noformat}
> https://knox/gateway/emr/yarn/nodemanager/node/containerlogs/{your container
> id}/hadoop?scheme=http&host={executor host}&port=8042 {noformat}
> I guess adding some voodoo in the Knox yarnui's
> [rewrite.xml|https://github.com/apache/knox/blob/master/gateway-service-definitions/src/main/resources/services/yarnui/2.7.0/rewrite.xml]
> file might be enough to fix this.
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
[jira] [Work logged] (KNOX-1744) [Spark History UI Service] Executor logs (stdout/stderr) links are broken
[
https://issues.apache.org/jira/browse/KNOX-1744?focusedWorklogId=278551&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-278551
]
ASF GitHub Bot logged work on KNOX-1744:
Author: ASF GitHub Bot
Created on: 17/Jul/19 22:22
Start Date: 17/Jul/19 22:22
Worklog Time Spent: 10m
Work Description: ankuriitg commented on pull request #120: KNOX-1744 -
Add rewrite rules to fix executor stdout/stderr links in Spark History Server UI
URL: https://github.com/apache/knox/pull/120
Testing Done:
Deployed on a cluster with Knox and ensured that the URLs are rewritten
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
Issue Time Tracking
---
Worklog Id: (was: 278551)
Time Spent: 10m
Remaining Estimate: 0h
> [Spark History UI Service] Executor logs (stdout/stderr) links are broken
> --
>
> Key: KNOX-1744
> URL: https://issues.apache.org/jira/browse/KNOX-1744
> Project: Apache Knox
> Issue Type: Bug
>Affects Versions: 1.2.0
>Reporter: Nicolas Colomer
>Priority: Minor
> Fix For: 1.4.0
>
> Attachments: image-2019-01-22-13-04-53-935.png,
> image-2019-01-22-13-11-55-412.png
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> The executor logs (stdout/stderr) links from the Yarn UI Service all directly
> points to the slaves nodes.
> !image-2019-01-22-13-11-55-412.png!
> Eg. the link:
> {noformat}
> http://emr-slave-hostname:8042/node/containerlogs/container_1547901130703_0034_01_01/hadoop/stdout?start=-4096{noformat}
> Should have been instead:
> {noformat}
> https://knox/gateway/cluster/yarn/nodemanager/node/containerlogs/container_1547901130703_0034_01_01/hadoop?scheme=http&host=emr-slave-hostname&port=8042{noformat}
> And finally respect pattern:
> {noformat}
> https://knox/gateway/emr/yarn/nodemanager/node/containerlogs/{your container
> id}/hadoop?scheme=http&host={executor host}&port=8042 {noformat}
> I guess adding some voodoo in the Knox yarnui's
> [rewrite.xml|https://github.com/apache/knox/blob/master/gateway-service-definitions/src/main/resources/services/yarnui/2.7.0/rewrite.xml]
> file might be enough to fix this.
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
[jira] [Work logged] (KNOX-1744) [Spark History UI Service] Executor logs (stdout/stderr) links are broken
[
https://issues.apache.org/jira/browse/KNOX-1744?focusedWorklogId=278552&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-278552
]
ASF GitHub Bot logged work on KNOX-1744:
Author: ASF GitHub Bot
Created on: 17/Jul/19 22:22
Start Date: 17/Jul/19 22:22
Worklog Time Spent: 10m
Work Description: ankuriitg commented on issue #120: KNOX-1744 - Add
rewrite rules to fix executor stdout/stderr links in Spark History Server UI
URL: https://github.com/apache/knox/pull/120#issuecomment-512590626
@moresandeep
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
Issue Time Tracking
---
Worklog Id: (was: 278552)
Time Spent: 20m (was: 10m)
> [Spark History UI Service] Executor logs (stdout/stderr) links are broken
> --
>
> Key: KNOX-1744
> URL: https://issues.apache.org/jira/browse/KNOX-1744
> Project: Apache Knox
> Issue Type: Bug
>Affects Versions: 1.2.0
>Reporter: Nicolas Colomer
>Priority: Minor
> Fix For: 1.4.0
>
> Attachments: image-2019-01-22-13-04-53-935.png,
> image-2019-01-22-13-11-55-412.png
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> The executor logs (stdout/stderr) links from the Yarn UI Service all directly
> points to the slaves nodes.
> !image-2019-01-22-13-11-55-412.png!
> Eg. the link:
> {noformat}
> http://emr-slave-hostname:8042/node/containerlogs/container_1547901130703_0034_01_01/hadoop/stdout?start=-4096{noformat}
> Should have been instead:
> {noformat}
> https://knox/gateway/cluster/yarn/nodemanager/node/containerlogs/container_1547901130703_0034_01_01/hadoop?scheme=http&host=emr-slave-hostname&port=8042{noformat}
> And finally respect pattern:
> {noformat}
> https://knox/gateway/emr/yarn/nodemanager/node/containerlogs/{your container
> id}/hadoop?scheme=http&host={executor host}&port=8042 {noformat}
> I guess adding some voodoo in the Knox yarnui's
> [rewrite.xml|https://github.com/apache/knox/blob/master/gateway-service-definitions/src/main/resources/services/yarnui/2.7.0/rewrite.xml]
> file might be enough to fix this.
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
[GitHub] [knox] ankuriitg commented on issue #120: KNOX-1744 - Add rewrite rules to fix executor stdout/stderr links in Spark History Server UI
ankuriitg commented on issue #120: KNOX-1744 - Add rewrite rules to fix executor stdout/stderr links in Spark History Server UI URL: https://github.com/apache/knox/pull/120#issuecomment-512590626 @moresandeep This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] [knox] ankuriitg opened a new pull request #120: KNOX-1744 - Add rewrite rules to fix executor stdout/stderr links in Spark History Server UI
ankuriitg opened a new pull request #120: KNOX-1744 - Add rewrite rules to fix executor stdout/stderr links in Spark History Server UI URL: https://github.com/apache/knox/pull/120 Testing Done: Deployed on a cluster with Knox and ensured that the URLs are rewritten This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[jira] [Work logged] (KNOX-1933) [Livy UI] Yarn application and driver log links are broken
[ https://issues.apache.org/jira/browse/KNOX-1933?focusedWorklogId=278519&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-278519 ] ASF GitHub Bot logged work on KNOX-1933: Author: ASF GitHub Bot Created on: 17/Jul/19 22:05 Start Date: 17/Jul/19 22:05 Worklog Time Spent: 10m Work Description: ankuriitg commented on issue #119: KNOX-1933 - Add rewrite rules to fix Yarn RM application and logs URL URL: https://github.com/apache/knox/pull/119#issuecomment-512586180 @moresandeep This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org Issue Time Tracking --- Worklog Id: (was: 278519) Time Spent: 20m (was: 10m) > [Livy UI] Yarn application and driver log links are broken > -- > > Key: KNOX-1933 > URL: https://issues.apache.org/jira/browse/KNOX-1933 > Project: Apache Knox > Issue Type: Improvement >Affects Versions: 1.3.0 >Reporter: Ankur Gupta >Priority: Major > Fix For: 1.4.0 > > Attachments: Screen Shot 2019-07-17 at 1.50.45 PM.png > > Time Spent: 20m > Remaining Estimate: 0h > > Attached the screenshot for Livy UI. -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Work logged] (KNOX-1933) [Livy UI] Yarn application and driver log links are broken
[ https://issues.apache.org/jira/browse/KNOX-1933?focusedWorklogId=278518&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-278518 ] ASF GitHub Bot logged work on KNOX-1933: Author: ASF GitHub Bot Created on: 17/Jul/19 22:05 Start Date: 17/Jul/19 22:05 Worklog Time Spent: 10m Work Description: ankuriitg commented on pull request #119: KNOX-1933 - Add rewrite rules to fix Yarn RM application and logs URL URL: https://github.com/apache/knox/pull/119 Testing Done: Deployed on a cluster with Knox and made sure these links worked This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org Issue Time Tracking --- Worklog Id: (was: 278518) Time Spent: 10m Remaining Estimate: 0h > [Livy UI] Yarn application and driver log links are broken > -- > > Key: KNOX-1933 > URL: https://issues.apache.org/jira/browse/KNOX-1933 > Project: Apache Knox > Issue Type: Improvement >Affects Versions: 1.3.0 >Reporter: Ankur Gupta >Priority: Major > Fix For: 1.4.0 > > Attachments: Screen Shot 2019-07-17 at 1.50.45 PM.png > > Time Spent: 10m > Remaining Estimate: 0h > > Attached the screenshot for Livy UI. -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[GitHub] [knox] ankuriitg opened a new pull request #119: KNOX-1933 - Add rewrite rules to fix Yarn RM application and logs URL
ankuriitg opened a new pull request #119: KNOX-1933 - Add rewrite rules to fix Yarn RM application and logs URL URL: https://github.com/apache/knox/pull/119 Testing Done: Deployed on a cluster with Knox and made sure these links worked This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] [knox] ankuriitg commented on issue #119: KNOX-1933 - Add rewrite rules to fix Yarn RM application and logs URL
ankuriitg commented on issue #119: KNOX-1933 - Add rewrite rules to fix Yarn RM application and logs URL URL: https://github.com/apache/knox/pull/119#issuecomment-512586180 @moresandeep This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[jira] [Commented] (KNOX-1933) [Livy UI] Yarn application and driver log links are broken
[ https://issues.apache.org/jira/browse/KNOX-1933?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16887423#comment-16887423 ] Ankur Gupta commented on KNOX-1933: --- I worked on fixing those using rewrite urls. I will post that PR soon. > [Livy UI] Yarn application and driver log links are broken > -- > > Key: KNOX-1933 > URL: https://issues.apache.org/jira/browse/KNOX-1933 > Project: Apache Knox > Issue Type: Improvement >Affects Versions: 1.3.0 >Reporter: Ankur Gupta >Priority: Major > Fix For: 1.4.0 > > Attachments: Screen Shot 2019-07-17 at 1.50.45 PM.png > > > Attached the screenshot for Livy UI. -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Commented] (KNOX-1933) [Livy UI] Yarn application and driver log links are broken
[ https://issues.apache.org/jira/browse/KNOX-1933?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16887420#comment-16887420 ] Kevin Risden commented on KNOX-1933: I would guess these links come back from the Livy API though? Maybe they can be fixed as part of the API and don't need to do anything specific for the UI. > [Livy UI] Yarn application and driver log links are broken > -- > > Key: KNOX-1933 > URL: https://issues.apache.org/jira/browse/KNOX-1933 > Project: Apache Knox > Issue Type: Improvement >Affects Versions: 1.3.0 >Reporter: Ankur Gupta >Priority: Major > Fix For: 1.4.0 > > Attachments: Screen Shot 2019-07-17 at 1.50.45 PM.png > > > Attached the screenshot for Livy UI. -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Commented] (KNOX-1933) [Livy UI] Yarn application and driver log links are broken
[ https://issues.apache.org/jira/browse/KNOX-1933?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16887417#comment-16887417 ] Kevin Risden commented on KNOX-1933: Currently there are no Livy UI specific rewrite rules. Livy added support for checking the x forwarded header. > [Livy UI] Yarn application and driver log links are broken > -- > > Key: KNOX-1933 > URL: https://issues.apache.org/jira/browse/KNOX-1933 > Project: Apache Knox > Issue Type: Improvement >Affects Versions: 1.3.0 >Reporter: Ankur Gupta >Priority: Major > Fix For: 1.4.0 > > Attachments: Screen Shot 2019-07-17 at 1.50.45 PM.png > > > Attached the screenshot for Livy UI. -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Comment Edited] (KNOX-1933) [Livy UI] Yarn application and driver log links are broken
[ https://issues.apache.org/jira/browse/KNOX-1933?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16887417#comment-16887417 ] Kevin Risden edited comment on KNOX-1933 at 7/17/19 9:09 PM: - Currently there are no Livy UI specific rewrite rules. Livy added support for checking the x forwarded header. So these log links would be the first to try to rewrite for Livy UI. was (Author: risdenk): Currently there are no Livy UI specific rewrite rules. Livy added support for checking the x forwarded header. > [Livy UI] Yarn application and driver log links are broken > -- > > Key: KNOX-1933 > URL: https://issues.apache.org/jira/browse/KNOX-1933 > Project: Apache Knox > Issue Type: Improvement >Affects Versions: 1.3.0 >Reporter: Ankur Gupta >Priority: Major > Fix For: 1.4.0 > > Attachments: Screen Shot 2019-07-17 at 1.50.45 PM.png > > > Attached the screenshot for Livy UI. -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Updated] (KNOX-1933) [Livy UI] Yarn application and driver log links are broken
[ https://issues.apache.org/jira/browse/KNOX-1933?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kevin Risden updated KNOX-1933: --- Affects Version/s: (was: 1.2.0) > [Livy UI] Yarn application and driver log links are broken > -- > > Key: KNOX-1933 > URL: https://issues.apache.org/jira/browse/KNOX-1933 > Project: Apache Knox > Issue Type: Improvement > Components: ClientDSL >Reporter: Ankur Gupta >Priority: Major > Attachments: Screen Shot 2019-07-17 at 1.50.45 PM.png > > > Attached the screenshot for Livy UI. -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Updated] (KNOX-1933) [Livy UI] Yarn application and driver log links are broken
[ https://issues.apache.org/jira/browse/KNOX-1933?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kevin Risden updated KNOX-1933: --- Component/s: (was: ClientDSL) > [Livy UI] Yarn application and driver log links are broken > -- > > Key: KNOX-1933 > URL: https://issues.apache.org/jira/browse/KNOX-1933 > Project: Apache Knox > Issue Type: Improvement >Affects Versions: 1.3.0 >Reporter: Ankur Gupta >Priority: Major > Fix For: 1.4.0 > > Attachments: Screen Shot 2019-07-17 at 1.50.45 PM.png > > > Attached the screenshot for Livy UI. -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Updated] (KNOX-1933) [Livy UI] Yarn application and driver log links are broken
[ https://issues.apache.org/jira/browse/KNOX-1933?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kevin Risden updated KNOX-1933: --- Fix Version/s: 1.4.0 > [Livy UI] Yarn application and driver log links are broken > -- > > Key: KNOX-1933 > URL: https://issues.apache.org/jira/browse/KNOX-1933 > Project: Apache Knox > Issue Type: Improvement > Components: ClientDSL >Affects Versions: 1.3.0 >Reporter: Ankur Gupta >Priority: Major > Fix For: 1.4.0 > > Attachments: Screen Shot 2019-07-17 at 1.50.45 PM.png > > > Attached the screenshot for Livy UI. -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Updated] (KNOX-1933) [Livy UI] Yarn application and driver log links are broken
[ https://issues.apache.org/jira/browse/KNOX-1933?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kevin Risden updated KNOX-1933: --- Affects Version/s: 1.3.0 > [Livy UI] Yarn application and driver log links are broken > -- > > Key: KNOX-1933 > URL: https://issues.apache.org/jira/browse/KNOX-1933 > Project: Apache Knox > Issue Type: Improvement > Components: ClientDSL >Affects Versions: 1.3.0 >Reporter: Ankur Gupta >Priority: Major > Attachments: Screen Shot 2019-07-17 at 1.50.45 PM.png > > > Attached the screenshot for Livy UI. -- This message was sent by Atlassian JIRA (v7.6.14#76016)
Re: [VOTE] Release RC 2 as Apache Knox 1.3.0
* Downloaded and built from source * Checked signatures, README, NOTICE, LICENSE * Ran samples * Tested WebHDFS from external nodejs client * Tested HiveServer2 from KnoxShell based SQL client * Tested KnoxSSO Form based IDP * Tested Knox Admin UI * Tested Kerberized +1 On Wed, Jul 17, 2019 at 3:56 PM Phil Zampino wrote: > +1 to release RC2 as Apache Knox 1.3.0 > >- Built from source >- Ran a bunch of the samples (Admin API, WebHdfs, etc...) >- Exercised some proxied UIs (e.g., yarnuiv2, oozie, sparkhistoryui, >jobhistoryui, rangerui) >- Tested ClouderaManager-based discovery and the associated UI changes > > I've only found issues with CM-based discovery, the support for which isn't > complete yet anyway, so this is expected. > > > On Wed, Jul 17, 2019 at 3:14 PM Jeffrey Rodriguez > wrote: > > > Excellent job!! Thank you. > > > > I am able to build on the scenario where I had problems. > > > > Also tested a few of the scenarios where I use Knox. > > > > +1 Release this package as Knox 1.3.0 is my vote. > > > > Jeffrey E Rodriguez > > > > On Wed, Jul 17, 2019 at 5:37 AM larry mccay wrote: > > > > > > All - > > > > > > A candidate for the Apache Knox 1.3.0 release is available at: > > > > > > https://dist.apache.org/repos/dist/dev/knox/knox-1.3.0/ > > > > > > This RC addresses multiple issues identified in the testing of RC 1: > > > 1. Build problem related to DNS and SAN within the self signed cert > > > 2. libpam4j issue > > > 3. Upgrade to latest LTS of npm > > > > > > The release candidate is a zip archive of the sources in: > > > > > > https://https://gitbox.apache.org/repos/asf/knox.git > > > Branch v1.3.0 (git checkout -b v1.3.0) > > > > > > The KEYS file for signature validation is available at: > > > https://dist.apache.org/repos/dist/release/knox/KEYS > > > > > > Please vote on releasing this package as Apache Knox 1.3.0. > > > The vote is open for the next 72 hours and passes if a majority of at > > > least three +1 Apache Knox PMC votes are cast. > > > > > > [ ] +1 Release this package as Apache Knox 1.3.0 > > > [ ] -1 Do not release this package because... > > > > > > thanks, > > > > > > --larry > > >
[jira] [Created] (KNOX-1933) [Livy UI] Yarn application and driver log links are broken
Ankur Gupta created KNOX-1933: - Summary: [Livy UI] Yarn application and driver log links are broken Key: KNOX-1933 URL: https://issues.apache.org/jira/browse/KNOX-1933 Project: Apache Knox Issue Type: Improvement Components: ClientDSL Affects Versions: 1.2.0 Reporter: Ankur Gupta Attachments: Screen Shot 2019-07-17 at 1.50.45 PM.png Attached the screenshot for Livy UI. -- This message was sent by Atlassian JIRA (v7.6.14#76016)
Re: [VOTE] Release RC 2 as Apache Knox 1.3.0
+1 to release RC2 as Apache Knox 1.3.0 - Built from source - Ran a bunch of the samples (Admin API, WebHdfs, etc...) - Exercised some proxied UIs (e.g., yarnuiv2, oozie, sparkhistoryui, jobhistoryui, rangerui) - Tested ClouderaManager-based discovery and the associated UI changes I've only found issues with CM-based discovery, the support for which isn't complete yet anyway, so this is expected. On Wed, Jul 17, 2019 at 3:14 PM Jeffrey Rodriguez wrote: > Excellent job!! Thank you. > > I am able to build on the scenario where I had problems. > > Also tested a few of the scenarios where I use Knox. > > +1 Release this package as Knox 1.3.0 is my vote. > > Jeffrey E Rodriguez > > On Wed, Jul 17, 2019 at 5:37 AM larry mccay wrote: > > > > All - > > > > A candidate for the Apache Knox 1.3.0 release is available at: > > > > https://dist.apache.org/repos/dist/dev/knox/knox-1.3.0/ > > > > This RC addresses multiple issues identified in the testing of RC 1: > > 1. Build problem related to DNS and SAN within the self signed cert > > 2. libpam4j issue > > 3. Upgrade to latest LTS of npm > > > > The release candidate is a zip archive of the sources in: > > > > https://https://gitbox.apache.org/repos/asf/knox.git > > Branch v1.3.0 (git checkout -b v1.3.0) > > > > The KEYS file for signature validation is available at: > > https://dist.apache.org/repos/dist/release/knox/KEYS > > > > Please vote on releasing this package as Apache Knox 1.3.0. > > The vote is open for the next 72 hours and passes if a majority of at > > least three +1 Apache Knox PMC votes are cast. > > > > [ ] +1 Release this package as Apache Knox 1.3.0 > > [ ] -1 Do not release this package because... > > > > thanks, > > > > --larry >
[jira] [Commented] (KNOX-1932) CM discovery - WEBHCAT URLs not discovered
[ https://issues.apache.org/jira/browse/KNOX-1932?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16887373#comment-16887373 ] Kevin Risden commented on KNOX-1932: I'm 90% sure that WebHCAT is not a thing in CM. > CM discovery - WEBHCAT URLs not discovered > -- > > Key: KNOX-1932 > URL: https://issues.apache.org/jira/browse/KNOX-1932 > Project: Apache Knox > Issue Type: Sub-task > Components: cm-discovery >Affects Versions: 1.3.0 >Reporter: Phil Zampino >Assignee: Phil Zampino >Priority: Major > Fix For: 1.4.0 > > -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Updated] (KNOX-1931) CM discovery - WEBHBASE URLs not discovered
[ https://issues.apache.org/jira/browse/KNOX-1931?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Phil Zampino updated KNOX-1931: --- Description: This may be because the required REST server role (HBASERESTSERVER role type) hasn't been configured, but this needs to be confirmed. (was: This may be because the required REST server component hasn't been configured, but this needs to be confirmed.) > CM discovery - WEBHBASE URLs not discovered > --- > > Key: KNOX-1931 > URL: https://issues.apache.org/jira/browse/KNOX-1931 > Project: Apache Knox > Issue Type: Sub-task > Components: cm-discovery >Affects Versions: 1.3.0 >Reporter: Phil Zampino >Assignee: Phil Zampino >Priority: Major > Fix For: 1.4.0 > > > This may be because the required REST server role (HBASERESTSERVER role type) > hasn't been configured, but this needs to be confirmed. -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Updated] (KNOX-1931) CM discovery - WEBHBASE URLs not discovered
[ https://issues.apache.org/jira/browse/KNOX-1931?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Phil Zampino updated KNOX-1931: --- Description: This may be because the required REST server component hasn't been configured, but this needs to be confirmed. > CM discovery - WEBHBASE URLs not discovered > --- > > Key: KNOX-1931 > URL: https://issues.apache.org/jira/browse/KNOX-1931 > Project: Apache Knox > Issue Type: Sub-task > Components: cm-discovery >Affects Versions: 1.3.0 >Reporter: Phil Zampino >Assignee: Phil Zampino >Priority: Major > Fix For: 1.4.0 > > > This may be because the required REST server component hasn't been > configured, but this needs to be confirmed. -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Assigned] (KNOX-1932) CM discovery - WEBHCAT URLs not discovered
[ https://issues.apache.org/jira/browse/KNOX-1932?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Phil Zampino reassigned KNOX-1932: -- Assignee: Phil Zampino Affects Version/s: 1.3.0 Fix Version/s: 1.4.0 Component/s: cm-discovery > CM discovery - WEBHCAT URLs not discovered > -- > > Key: KNOX-1932 > URL: https://issues.apache.org/jira/browse/KNOX-1932 > Project: Apache Knox > Issue Type: Sub-task > Components: cm-discovery >Affects Versions: 1.3.0 >Reporter: Phil Zampino >Assignee: Phil Zampino >Priority: Major > Fix For: 1.4.0 > > -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Created] (KNOX-1932) CM discovery - WEBHCAT URLs not discovered
Phil Zampino created KNOX-1932: -- Summary: CM discovery - WEBHCAT URLs not discovered Key: KNOX-1932 URL: https://issues.apache.org/jira/browse/KNOX-1932 Project: Apache Knox Issue Type: Sub-task Reporter: Phil Zampino -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Created] (KNOX-1931) CM discovery - WEBHBASE URLs not discovered
Phil Zampino created KNOX-1931: -- Summary: CM discovery - WEBHBASE URLs not discovered Key: KNOX-1931 URL: https://issues.apache.org/jira/browse/KNOX-1931 Project: Apache Knox Issue Type: Sub-task Components: cm-discovery Affects Versions: 1.3.0 Reporter: Phil Zampino Assignee: Phil Zampino Fix For: 1.4.0 -- This message was sent by Atlassian JIRA (v7.6.14#76016)
Re: [VOTE] Release RC 2 as Apache Knox 1.3.0
Excellent job!! Thank you. I am able to build on the scenario where I had problems. Also tested a few of the scenarios where I use Knox. +1 Release this package as Knox 1.3.0 is my vote. Jeffrey E Rodriguez On Wed, Jul 17, 2019 at 5:37 AM larry mccay wrote: > > All - > > A candidate for the Apache Knox 1.3.0 release is available at: > > https://dist.apache.org/repos/dist/dev/knox/knox-1.3.0/ > > This RC addresses multiple issues identified in the testing of RC 1: > 1. Build problem related to DNS and SAN within the self signed cert > 2. libpam4j issue > 3. Upgrade to latest LTS of npm > > The release candidate is a zip archive of the sources in: > > https://https://gitbox.apache.org/repos/asf/knox.git > Branch v1.3.0 (git checkout -b v1.3.0) > > The KEYS file for signature validation is available at: > https://dist.apache.org/repos/dist/release/knox/KEYS > > Please vote on releasing this package as Apache Knox 1.3.0. > The vote is open for the next 72 hours and passes if a majority of at > least three +1 Apache Knox PMC votes are cast. > > [ ] +1 Release this package as Apache Knox 1.3.0 > [ ] -1 Do not release this package because... > > thanks, > > --larry
[jira] [Created] (KNOX-1930) CM discovery - JOBTRACKER URLs not discovered
Phil Zampino created KNOX-1930: -- Summary: CM discovery - JOBTRACKER URLs not discovered Key: KNOX-1930 URL: https://issues.apache.org/jira/browse/KNOX-1930 Project: Apache Knox Issue Type: Sub-task Components: cm-discovery Affects Versions: 1.3.0 Reporter: Phil Zampino Assignee: Phil Zampino Fix For: 1.4.0 -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Commented] (KNOX-1929) CM discovery - HIVE URLs not discovered when HIVE_ON_TEZ is deployed
[ https://issues.apache.org/jira/browse/KNOX-1929?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16887353#comment-16887353 ] Kevin Risden commented on KNOX-1929: I think we have to be careful here. Since there could be both a HIVE_ON_TEZ HS2 and a HIVE HS2. Meaning that we DON'T want to combine the urls. Since we can't have multiple of the same service in a topology, need to be careful about this case. > CM discovery - HIVE URLs not discovered when HIVE_ON_TEZ is deployed > > > Key: KNOX-1929 > URL: https://issues.apache.org/jira/browse/KNOX-1929 > Project: Apache Knox > Issue Type: Sub-task > Components: cm-discovery >Affects Versions: 1.3.0 >Reporter: Phil Zampino >Assignee: Phil Zampino >Priority: Major > Fix For: 1.4.0 > > > When HIVESERVER2 is deployed as HIVE_ON_TEZ, the CM discovery implementation > does not correctly identify it, and thusly fails to generate a valid URL for > Knox to proxy. > It looks like the implementation should consider only role type (i.e., > HIVESERVER2), rather than the service type (i.e., HIVE, HIVE_ON_TEZ) to > determine if it should "handle" the config. -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Updated] (KNOX-1929) CM discovery - HIVE URLs not discovered when HIVE_ON_TEZ is deployed
[ https://issues.apache.org/jira/browse/KNOX-1929?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kevin Risden updated KNOX-1929: --- Summary: CM discovery - HIVE URLs not discovered when HIVE_ON_TEZ is deployed (was: HIVE URLs not discovered when HIVE_ON_TEZ is deployed) > CM discovery - HIVE URLs not discovered when HIVE_ON_TEZ is deployed > > > Key: KNOX-1929 > URL: https://issues.apache.org/jira/browse/KNOX-1929 > Project: Apache Knox > Issue Type: Sub-task > Components: cm-discovery >Affects Versions: 1.3.0 >Reporter: Phil Zampino >Assignee: Phil Zampino >Priority: Major > Fix For: 1.4.0 > > > When HIVESERVER2 is deployed as HIVE_ON_TEZ, the CM discovery implementation > does not correctly identify it, and thusly fails to generate a valid URL for > Knox to proxy. > It looks like the implementation should consider only role type (i.e., > HIVESERVER2), rather than the service type (i.e., HIVE, HIVE_ON_TEZ) to > determine if it should "handle" the config. -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Commented] (KNOX-1928) CM discovery - Multiple of same url are added to descriptor?
[ https://issues.apache.org/jira/browse/KNOX-1928?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16887316#comment-16887316 ] Phil Zampino commented on KNOX-1928: RANGER and ATLAS-API behave similarly. > CM discovery - Multiple of same url are added to descriptor? > > > Key: KNOX-1928 > URL: https://issues.apache.org/jira/browse/KNOX-1928 > Project: Apache Knox > Issue Type: Sub-task > Components: cm-discovery >Affects Versions: 1.3.0 >Reporter: Kevin Risden >Assignee: Phil Zampino >Priority: Major > Fix For: 1.4.0 > > > In the generated topology, sometimes there are multiple of the same exact > url. SOLR exhibited this behavior but there looked to be others. -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Assigned] (KNOX-1929) HIVE URLs not discovered when HIVE_ON_TEZ is deployed
[ https://issues.apache.org/jira/browse/KNOX-1929?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Phil Zampino reassigned KNOX-1929: -- Assignee: Phil Zampino > HIVE URLs not discovered when HIVE_ON_TEZ is deployed > - > > Key: KNOX-1929 > URL: https://issues.apache.org/jira/browse/KNOX-1929 > Project: Apache Knox > Issue Type: Sub-task > Components: cm-discovery >Affects Versions: 1.3.0 >Reporter: Phil Zampino >Assignee: Phil Zampino >Priority: Major > Fix For: 1.4.0 > > > When HIVESERVER2 is deployed as HIVE_ON_TEZ, the CM discovery implementation > does not correctly identify it, and thusly fails to generate a valid URL for > Knox to proxy. > It looks like the implementation should consider only role type (i.e., > HIVESERVER2), rather than the service type (i.e., HIVE, HIVE_ON_TEZ) to > determine if it should "handle" the config. -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Created] (KNOX-1929) HIVE URLs not discovered when HIVE_ON_TEZ is deployed
Phil Zampino created KNOX-1929: -- Summary: HIVE URLs not discovered when HIVE_ON_TEZ is deployed Key: KNOX-1929 URL: https://issues.apache.org/jira/browse/KNOX-1929 Project: Apache Knox Issue Type: Sub-task Components: cm-discovery Affects Versions: 1.3.0 Reporter: Phil Zampino Fix For: 1.4.0 When HIVESERVER2 is deployed as HIVE_ON_TEZ, the CM discovery implementation does not correctly identify it, and thusly fails to generate a valid URL for Knox to proxy. It looks like the implementation should consider only role type (i.e., HIVESERVER2), rather than the service type (i.e., HIVE, HIVE_ON_TEZ) to determine if it should "handle" the config. -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Updated] (KNOX-1927) CM discovery - ZEPPELINUI / ZEPPELINWS urls are not discovered
[ https://issues.apache.org/jira/browse/KNOX-1927?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kevin Risden updated KNOX-1927: --- Affects Version/s: 1.3.0 > CM discovery - ZEPPELINUI / ZEPPELINWS urls are not discovered > -- > > Key: KNOX-1927 > URL: https://issues.apache.org/jira/browse/KNOX-1927 > Project: Apache Knox > Issue Type: Sub-task > Components: cm-discovery >Affects Versions: 1.3.0 >Reporter: Kevin Risden >Assignee: Phil Zampino >Priority: Major > Fix For: 1.4.0 > > > ZEPPELINUI/ZEPPELINWS is added to the descriptor but urls are empty? -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Created] (KNOX-1928) CM discovery - Multiple of same url are added to descriptor?
Kevin Risden created KNOX-1928: -- Summary: CM discovery - Multiple of same url are added to descriptor? Key: KNOX-1928 URL: https://issues.apache.org/jira/browse/KNOX-1928 Project: Apache Knox Issue Type: Sub-task Components: cm-discovery Affects Versions: 1.3.0 Reporter: Kevin Risden Assignee: Phil Zampino Fix For: 1.4.0 In the generated topology, sometimes there are multiple of the same exact url. SOLR exhibited this behavior but there looked to be others. -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Assigned] (KNOX-1921) Cloudera Manager service discovery Hue Load balancer scheme
[ https://issues.apache.org/jira/browse/KNOX-1921?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kevin Risden reassigned KNOX-1921: -- Assignee: Phil Zampino > Cloudera Manager service discovery Hue Load balancer scheme > --- > > Key: KNOX-1921 > URL: https://issues.apache.org/jira/browse/KNOX-1921 > Project: Apache Knox > Issue Type: Sub-task > Components: cm-discovery >Affects Versions: 1.3.0 >Reporter: Jean-Francois Desjeans Gauthier >Assignee: Phil Zampino >Priority: Major > Fix For: 1.4.0 > > > With KNOX-1875, the Hue scheme is determined dynamically, but the Hue load > balancer scheme is not. Is it possible to enable the same dynamic scheme > determination for the load balancer? > [https://gitbox.apache.org/repos/asf?p=knox.git;a=blob;f=gateway-discovery-cm/src/main/java/org/apache/knox/gateway/topology/discovery/cm/model/hue/HueLBServiceModelGenerator.java;h=63eb0b690c9635230285bb84a7c939b0f4cfcf44;hb=248f08c#l45] > [https://gitbox.apache.org/repos/asf?p=knox.git;a=blob;f=gateway-discovery-cm/src/main/java/org/apache/knox/gateway/topology/discovery/cm/model/hue/HueServiceModelGenerator.java;h=12e4eb314d730193430745b480bcf77081375a59;hb=248f08c#l48] -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Created] (KNOX-1927) CM discovery - ZEPPELINUI / ZEPPELINWS urls are not discovered
Kevin Risden created KNOX-1927: -- Summary: CM discovery - ZEPPELINUI / ZEPPELINWS urls are not discovered Key: KNOX-1927 URL: https://issues.apache.org/jira/browse/KNOX-1927 Project: Apache Knox Issue Type: Sub-task Components: cm-discovery Reporter: Kevin Risden Assignee: Phil Zampino Fix For: 1.4.0 ZEPPELINUI/ZEPPELINWS is added to the descriptor but urls are empty? -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Updated] (KNOX-1921) CM discovery Hue Load balancer scheme
[ https://issues.apache.org/jira/browse/KNOX-1921?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kevin Risden updated KNOX-1921: --- Summary: CM discovery Hue Load balancer scheme (was: Cloudera Manager service discovery Hue Load balancer scheme) > CM discovery Hue Load balancer scheme > - > > Key: KNOX-1921 > URL: https://issues.apache.org/jira/browse/KNOX-1921 > Project: Apache Knox > Issue Type: Sub-task > Components: cm-discovery >Affects Versions: 1.3.0 >Reporter: Jean-Francois Desjeans Gauthier >Assignee: Phil Zampino >Priority: Major > Fix For: 1.4.0 > > > With KNOX-1875, the Hue scheme is determined dynamically, but the Hue load > balancer scheme is not. Is it possible to enable the same dynamic scheme > determination for the load balancer? > [https://gitbox.apache.org/repos/asf?p=knox.git;a=blob;f=gateway-discovery-cm/src/main/java/org/apache/knox/gateway/topology/discovery/cm/model/hue/HueLBServiceModelGenerator.java;h=63eb0b690c9635230285bb84a7c939b0f4cfcf44;hb=248f08c#l45] > [https://gitbox.apache.org/repos/asf?p=knox.git;a=blob;f=gateway-discovery-cm/src/main/java/org/apache/knox/gateway/topology/discovery/cm/model/hue/HueServiceModelGenerator.java;h=12e4eb314d730193430745b480bcf77081375a59;hb=248f08c#l48] -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Updated] (KNOX-1921) CM discovery - Hue Load balancer HTTP/HTTPS scheme
[ https://issues.apache.org/jira/browse/KNOX-1921?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kevin Risden updated KNOX-1921: --- Summary: CM discovery - Hue Load balancer HTTP/HTTPS scheme (was: CM discovery Hue Load balancer scheme) > CM discovery - Hue Load balancer HTTP/HTTPS scheme > -- > > Key: KNOX-1921 > URL: https://issues.apache.org/jira/browse/KNOX-1921 > Project: Apache Knox > Issue Type: Sub-task > Components: cm-discovery >Affects Versions: 1.3.0 >Reporter: Jean-Francois Desjeans Gauthier >Assignee: Phil Zampino >Priority: Major > Fix For: 1.4.0 > > > With KNOX-1875, the Hue scheme is determined dynamically, but the Hue load > balancer scheme is not. Is it possible to enable the same dynamic scheme > determination for the load balancer? > [https://gitbox.apache.org/repos/asf?p=knox.git;a=blob;f=gateway-discovery-cm/src/main/java/org/apache/knox/gateway/topology/discovery/cm/model/hue/HueLBServiceModelGenerator.java;h=63eb0b690c9635230285bb84a7c939b0f4cfcf44;hb=248f08c#l45] > [https://gitbox.apache.org/repos/asf?p=knox.git;a=blob;f=gateway-discovery-cm/src/main/java/org/apache/knox/gateway/topology/discovery/cm/model/hue/HueServiceModelGenerator.java;h=12e4eb314d730193430745b480bcf77081375a59;hb=248f08c#l48] -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Updated] (KNOX-1921) Cloudera Manager service discovery Hue Load balancer scheme
[ https://issues.apache.org/jira/browse/KNOX-1921?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kevin Risden updated KNOX-1921: --- Issue Type: Sub-task (was: Bug) Parent: KNOX-1926 > Cloudera Manager service discovery Hue Load balancer scheme > --- > > Key: KNOX-1921 > URL: https://issues.apache.org/jira/browse/KNOX-1921 > Project: Apache Knox > Issue Type: Sub-task > Components: cm-discovery >Affects Versions: 1.3.0 >Reporter: Jean-Francois Desjeans Gauthier >Priority: Major > Fix For: 1.4.0 > > > With KNOX-1875, the Hue scheme is determined dynamically, but the Hue load > balancer scheme is not. Is it possible to enable the same dynamic scheme > determination for the load balancer? > [https://gitbox.apache.org/repos/asf?p=knox.git;a=blob;f=gateway-discovery-cm/src/main/java/org/apache/knox/gateway/topology/discovery/cm/model/hue/HueLBServiceModelGenerator.java;h=63eb0b690c9635230285bb84a7c939b0f4cfcf44;hb=248f08c#l45] > [https://gitbox.apache.org/repos/asf?p=knox.git;a=blob;f=gateway-discovery-cm/src/main/java/org/apache/knox/gateway/topology/discovery/cm/model/hue/HueServiceModelGenerator.java;h=12e4eb314d730193430745b480bcf77081375a59;hb=248f08c#l48] -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Created] (KNOX-1926) Cloudera Manager discovery improvements
Kevin Risden created KNOX-1926: -- Summary: Cloudera Manager discovery improvements Key: KNOX-1926 URL: https://issues.apache.org/jira/browse/KNOX-1926 Project: Apache Knox Issue Type: Improvement Components: cm-discovery Affects Versions: 1.3.0 Reporter: Kevin Risden Assignee: Phil Zampino Fix For: 1.4.0 KNOX-1875 implemented initial Cloudera Manager discovery. There are improvements that can be made. -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[VOTE] Release RC 2 as Apache Knox 1.3.0
All - A candidate for the Apache Knox 1.3.0 release is available at: https://dist.apache.org/repos/dist/dev/knox/knox-1.3.0/ This RC addresses multiple issues identified in the testing of RC 1: 1. Build problem related to DNS and SAN within the self signed cert 2. libpam4j issue 3. Upgrade to latest LTS of npm The release candidate is a zip archive of the sources in: https://https://gitbox.apache.org/repos/asf/knox.git Branch v1.3.0 (git checkout -b v1.3.0) The KEYS file for signature validation is available at: https://dist.apache.org/repos/dist/release/knox/KEYS Please vote on releasing this package as Apache Knox 1.3.0. The vote is open for the next 72 hours and passes if a majority of at least three +1 Apache Knox PMC votes are cast. [ ] +1 Release this package as Apache Knox 1.3.0 [ ] -1 Do not release this package because... thanks, --larry
[jira] [Assigned] (KNOX-1593) YARN v2 UI - Application - View logs for running application
[ https://issues.apache.org/jira/browse/KNOX-1593?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prabhu Joseph reassigned KNOX-1593: --- Assignee: Prabhu Joseph > YARN v2 UI - Application - View logs for running application > > > Key: KNOX-1593 > URL: https://issues.apache.org/jira/browse/KNOX-1593 > Project: Apache Knox > Issue Type: Sub-task >Reporter: Kevin Risden >Assignee: Prabhu Joseph >Priority: Major > Fix For: 1.4.0 > > Attachments: Screen Shot 2018-11-09 at 4.10.34 PM.png > > > http://localhost:8443/gateway/test/yarnuiv2/redirect#/yarn-app/application_1541786998835_0007/logs > From the application page if you try to fetch logs you end up with this error > in the console: > [http://ambari:8042/ws/v1/node/containers/container_e03_1541786998835_0007_01_01/logs?_=1541797702070] > The nodemanager is trying to be directly accessed as part of the request for > logs instead of it being rewritten to go through Knox. -- This message was sent by Atlassian JIRA (v7.6.14#76016)
