[jira] [Commented] (TEZ-3954) Reduce Tez Shuffle Handler Memory needs for holding TezIndexRecords
[ https://issues.apache.org/jira/browse/TEZ-3954?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16534245#comment-16534245 ] Kuhu Shukla commented on TEZ-3954: -- Thank you Jon. +1. I will commit this tomorrow in case someone else wants to chime in by then. > Reduce Tez Shuffle Handler Memory needs for holding TezIndexRecords > --- > > Key: TEZ-3954 > URL: https://issues.apache.org/jira/browse/TEZ-3954 > Project: Apache Tez > Issue Type: Bug >Reporter: Jonathan Eagles >Assignee: Jonathan Eagles >Priority: Major > Attachments: TEZ-3954.001.patch > > > Tez Shuffle Handler holds on to entire SpillRecord to better accommodate for > range fetch operation. For single reduce fetch holding on to spillRecord can > overwhelm memory if Index Cache is overrun. In the case of single fetch, only > keep the single tez index record needed and for range fetch, keep the entire > spill record in memory, but free it after it is needed. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (TEZ-3963) Possible InflaterInputStream leaked in TezCommonUtils and related classes
[
https://issues.apache.org/jira/browse/TEZ-3963?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16534239#comment-16534239
]
TezQA commented on TEZ-3963:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12930443/TEZ-3963.001.patch
against master revision 06757e9.
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include
any new or modified tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 javadoc{color}. There were no new javadoc warning messages.
{color:green}+1 findbugs{color}. The patch does not introduce any new
Findbugs (version 3.0.1) warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in .
Test results:
https://builds.apache.org/job/PreCommit-TEZ-Build/2851//testReport/
Console output: https://builds.apache.org/job/PreCommit-TEZ-Build/2851//console
This message is automatically generated.
> Possible InflaterInputStream leaked in TezCommonUtils and related classes
> --
>
> Key: TEZ-3963
> URL: https://issues.apache.org/jira/browse/TEZ-3963
> Project: Apache Tez
> Issue Type: Bug
>Affects Versions: 0.9.1
>Reporter: Jaume M
>Assignee: Jaume M
>Priority: Major
> Attachments: TEZ-3963.001.patch
>
>
> I don't think [this is
> closed|https://github.com/apache/tez/blob/314dfc79b4b3f528b680b4fee73ad0dca3a3a19b/tez-api/src/main/java/org/apache/tez/common/TezCommonUtils.java#L397]
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
Failed: TEZ-3963 PreCommit Build #2851
Jira: https://issues.apache.org/jira/browse/TEZ-3963
Build: https://builds.apache.org/job/PreCommit-TEZ-Build/2851/
###
## LAST 60 LINES OF THE CONSOLE
###
[...truncated 376.69 KB...]
[INFO] BUILD SUCCESS
[INFO]
[INFO] Total time: 58:00 min
[INFO] Finished at: 2018-07-05T22:31:39Z
[INFO] Final Memory: 100M/1699M
[INFO]
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12930443/TEZ-3963.001.patch
against master revision 06757e9.
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include
any new or modified tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 javadoc{color}. There were no new javadoc warning messages.
{color:green}+1 findbugs{color}. The patch does not introduce any new
Findbugs (version 3.0.1) warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in .
Test results:
https://builds.apache.org/job/PreCommit-TEZ-Build/2851//testReport/
Console output: https://builds.apache.org/job/PreCommit-TEZ-Build/2851//console
This message is automatically generated.
==
==
Adding comment to Jira.
==
==
==
==
Finished build.
==
==
Build step 'Execute shell' marked build as failure
Archiving artifacts
[Fast Archiver] Compressed 4.09 MB of artifacts by 22.2% relative to #2805
[description-setter] Could not determine description.
Recording test results
Email was triggered for: Failure - Any
Sending email for trigger: Failure - Any
###
## FAILED TESTS (if any)
##
All tests passed
[jira] [Updated] (TEZ-3953) Restore ABI-compat for DAGClient for TEZ-3951
[ https://issues.apache.org/jira/browse/TEZ-3953?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Lowe updated TEZ-3953: Fix Version/s: 0.9.2 Description: I committed this to branch-0.9. > Restore ABI-compat for DAGClient for TEZ-3951 > - > > Key: TEZ-3953 > URL: https://issues.apache.org/jira/browse/TEZ-3953 > Project: Apache Tez > Issue Type: Bug >Affects Versions: 0.10.0 >Reporter: Sergey Shelukhin >Assignee: Sergey Shelukhin >Priority: Major > Fix For: 0.9.2, 0.10.0 > > Attachments: TEZ-3953.patch > > > I committed this to branch-0.9. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (TEZ-3904) an API to update tokens for Tez AM and the DAG
[ https://issues.apache.org/jira/browse/TEZ-3904?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jaume M reassigned TEZ-3904: Assignee: Jaume M > an API to update tokens for Tez AM and the DAG > -- > > Key: TEZ-3904 > URL: https://issues.apache.org/jira/browse/TEZ-3904 > Project: Apache Tez > Issue Type: Bug >Reporter: Sergey Shelukhin >Assignee: Jaume M >Priority: Major > Attachments: TEZ-3904.1.patch > > > Nothing is permanent in this world, lest of all delegation tokens. > The current way around token expiration (the one where you cannot keep > renewing anymore) in Hive when Tez AM is used in session mode is to cycle Tez > AM. It may happen though that a query is running at that time, and so the AM > cannot be restarted with new tokens. We let the query run its course and it > usually dies because it tries to do something with an expired token. > To get around that, we cycle AMs a few hours before tokens are going to > expire. > However, that is still not ideal because it puts an upper bound on safe Hive > query runtime (a query longer than 3 hours with current config may fail due > to an expired token if its timing is unlucky), and also precludes setting > tokens to expire much faster than the standard 7-day time frame. > There should be a mechanism to replace tokens in the AM, including for a > running DAG. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (TEZ-3964) Inflater not closed in some places
[
https://issues.apache.org/jira/browse/TEZ-3964?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16534215#comment-16534215
]
Jaume M commented on TEZ-3964:
--
Thank you for reviewing [~jlowe]. Looks like the method doesn't throw
{{IOException}} despite being declared in the method. Maybe we can remove the
{{throws IOException}} from the declaration. We can still do the refactor you
mentioned in case some returns early in the future.
> Inflater not closed in some places
> --
>
> Key: TEZ-3964
> URL: https://issues.apache.org/jira/browse/TEZ-3964
> Project: Apache Tez
> Issue Type: Bug
>Affects Versions: 0.9.1
>Reporter: Jaume M
>Assignee: Jaume M
>Priority: Major
>
> We call [this
> method|https://github.com/apache/tez/blob/314dfc79b4b3f528b680b4fee73ad0dca3a3a19b/tez-api/src/main/java/org/apache/tez/common/TezCommonUtils.java#L363]
> from a few places. We don't call {{end()}} from most of the place where we
> call and although it's not necessary to call it explicitly it's the
> recommended way in the docs to do so.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (TEZ-3963) Possible InflaterInputStream leaked in TezCommonUtils and related classes
[ https://issues.apache.org/jira/browse/TEZ-3963?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Lowe updated TEZ-3963: Attachment: TEZ-3963.001.patch > Possible InflaterInputStream leaked in TezCommonUtils and related classes > -- > > Key: TEZ-3963 > URL: https://issues.apache.org/jira/browse/TEZ-3963 > Project: Apache Tez > Issue Type: Bug >Affects Versions: 0.9.1 >Reporter: Jaume M >Assignee: Jaume M >Priority: Major > Attachments: TEZ-3963.001.patch > > > I don't think [this is > closed|https://github.com/apache/tez/blob/314dfc79b4b3f528b680b4fee73ad0dca3a3a19b/tez-api/src/main/java/org/apache/tez/common/TezCommonUtils.java#L397] -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (TEZ-3963) Possible InflaterInputStream leaked in TezCommonUtils and related classes
[ https://issues.apache.org/jira/browse/TEZ-3963?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16534158#comment-16534158 ] Jason Lowe commented on TEZ-3963: - Not sure the QA bot supports pull requests, so uploading the patch that is equivalent to the PR on github. > Possible InflaterInputStream leaked in TezCommonUtils and related classes > -- > > Key: TEZ-3963 > URL: https://issues.apache.org/jira/browse/TEZ-3963 > Project: Apache Tez > Issue Type: Bug >Affects Versions: 0.9.1 >Reporter: Jaume M >Assignee: Jaume M >Priority: Major > Attachments: TEZ-3963.001.patch > > > I don't think [this is > closed|https://github.com/apache/tez/blob/314dfc79b4b3f528b680b4fee73ad0dca3a3a19b/tez-api/src/main/java/org/apache/tez/common/TezCommonUtils.java#L397] -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (TEZ-3964) Inflater not closed in some places
[
https://issues.apache.org/jira/browse/TEZ-3964?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jason Lowe reassigned TEZ-3964:
---
Assignee: Jaume M
Thanks for the report and patch!
Looks good overall. I think it would be prudent to wrap the code in
convertDAGPlanToATSMap in a try..finally block for future maintenance. The
signature already declares it can throw IOException, so if someone adds some
code that does throw and forgets to handle the inflater.end call the bug will
reappear. I'd recommend refactoring the body into a private method that takes
an Inflater argument rather than indenting the whole body with the patch --
it's already a really long method.
> Inflater not closed in some places
> --
>
> Key: TEZ-3964
> URL: https://issues.apache.org/jira/browse/TEZ-3964
> Project: Apache Tez
> Issue Type: Bug
>Affects Versions: 0.9.1
>Reporter: Jaume M
>Assignee: Jaume M
>Priority: Major
>
> We call [this
> method|https://github.com/apache/tez/blob/314dfc79b4b3f528b680b4fee73ad0dca3a3a19b/tez-api/src/main/java/org/apache/tez/common/TezCommonUtils.java#L363]
> from a few places. We don't call {{end()}} from most of the place where we
> call and although it's not necessary to call it explicitly it's the
> recommended way in the docs to do so.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (TEZ-3966) Tez UI config couldn't be executed in browser
[
https://issues.apache.org/jira/browse/TEZ-3966?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16534151#comment-16534151
]
Jonathan Eagles commented on TEZ-3966:
--
[~rlukin], Was looking at this change to trying to reproduce. Uploaded a simple
server I was using to induce the nosniff as well as other options. However, I
was never able to reproduce this.
{code}
// build the tez ui
$ mvn clean install -DskipTests -Dmaven.javadoc.skip
// run a server with nosnif enabled
$ cd $TEZ/tez-ui/target/tez-ui-0.10.0-SNAPSHOT
$ $BIN/simple-cors-http-server.py
// navigate to 127.0.0.1:8000
{code}
Unless I am mistaken (which is highly possible as I am no expert in Web Tech).
I think this has little to do with Tez UI and instead to do with Ambari
config.env loading. config.env is fetched from the browser under the tez ui
under a
[jira] [Updated] (TEZ-3966) Tez UI config couldn't be executed in browser
[ https://issues.apache.org/jira/browse/TEZ-3966?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jonathan Eagles updated TEZ-3966: - Attachment: simple-cors-http-server.py > Tez UI config couldn't be executed in browser > -- > > Key: TEZ-3966 > URL: https://issues.apache.org/jira/browse/TEZ-3966 > Project: Apache Tez > Issue Type: Bug > Components: UI >Reporter: Roman Lukin >Priority: Major > Attachments: Selection_043.png, Selection_044.png, > simple-cors-http-server.py > > > Current name convention applied to the ui configuration file, produce the > following error in web browser - mime type check fails (which based on file > extesion) and if header `X-Content-Type-Options: nosniff` enabled config > wouldn't be executed and used. As a result we may have problems, for instance > links based on variable `yarnProtocol`. > More about header - > [https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/X-Content-Type-Options] > Possible solution - rename file `config.env` to `config.js` > [https://github.com/apache/tez/pull/26] > [https://github.com/rlukin/tez/commit/8db8c04faee04dc161c90c3961233ec5aa40518e] > > Steps to reproduce: > * Enable aforementioned header on web server > * Try to load tez ui -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (TEZ-3953) Restore ABI-compat for DAGClient for TEZ-3951
[ https://issues.apache.org/jira/browse/TEZ-3953?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16534116#comment-16534116 ] Sergey Shelukhin commented on TEZ-3953: --- [~jlowe] yes, can you push it there? Thanks > Restore ABI-compat for DAGClient for TEZ-3951 > - > > Key: TEZ-3953 > URL: https://issues.apache.org/jira/browse/TEZ-3953 > Project: Apache Tez > Issue Type: Bug >Affects Versions: 0.10.0 >Reporter: Sergey Shelukhin >Assignee: Sergey Shelukhin >Priority: Major > Fix For: 0.10.0 > > Attachments: TEZ-3953.patch > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (TEZ-3951) TezClient wait too long for the DAGClient for prewarm; tries to shut down the wrong DAG
[ https://issues.apache.org/jira/browse/TEZ-3951?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Lowe updated TEZ-3951: Fix Version/s: (was: 0.9.next) 0.9.2 > TezClient wait too long for the DAGClient for prewarm; tries to shut down the > wrong DAG > --- > > Key: TEZ-3951 > URL: https://issues.apache.org/jira/browse/TEZ-3951 > Project: Apache Tez > Issue Type: Bug >Reporter: Sergey Shelukhin >Assignee: Sergey Shelukhin >Priority: Major > Fix For: 0.9.2, 0.10.0 > > Attachments: TEZ-3951.01.patch, TEZ-3951.patch > > > Follow-up from TEZ-3943 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (TEZ-3953) Restore ABI-compat for DAGClient for TEZ-3951
[ https://issues.apache.org/jira/browse/TEZ-3953?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16534109#comment-16534109 ] Jason Lowe commented on TEZ-3953: - Does this need to be committed to branch-0.9 since TEZ-3951 went to branch-0.9? > Restore ABI-compat for DAGClient for TEZ-3951 > - > > Key: TEZ-3953 > URL: https://issues.apache.org/jira/browse/TEZ-3953 > Project: Apache Tez > Issue Type: Bug >Affects Versions: 0.10.0 >Reporter: Sergey Shelukhin >Assignee: Sergey Shelukhin >Priority: Major > Fix For: 0.10.0 > > Attachments: TEZ-3953.patch > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (TEZ-3954) Reduce Tez Shuffle Handler Memory needs for holding TezIndexRecords
[ https://issues.apache.org/jira/browse/TEZ-3954?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16534045#comment-16534045 ] Jonathan Eagles commented on TEZ-3954: -- The patch design is a hybrid approach between a) optimizing for the single partition fetch and b) optimizing for the ranged partition fetch. A single partition fetch only stores (separate from the IndexCache) the IndexRecord and not the whole TezSpillRecord with the ReduceContext. In this way if there are many hundreds of outstanding fetch requests we can keep the memory demand low. A ranged partition fetch will store the entire TezSpillRecord with the ReduceContext. In this way we can reduce memory for ranged fetch by not maintaining a separate list of IndexRecords for each partition fetched. In addition, this patch "frees" the TezSpillRecord once it is no longer needed (upstream task has only a spill record) in this way a ranged fetch over dozens of upstream tasks can remove the memory demand for subsequent ranged partitions fetches for sister upstream tasks. > Reduce Tez Shuffle Handler Memory needs for holding TezIndexRecords > --- > > Key: TEZ-3954 > URL: https://issues.apache.org/jira/browse/TEZ-3954 > Project: Apache Tez > Issue Type: Bug >Reporter: Jonathan Eagles >Assignee: Jonathan Eagles >Priority: Major > Attachments: TEZ-3954.001.patch > > > Tez Shuffle Handler holds on to entire SpillRecord to better accommodate for > range fetch operation. For single reduce fetch holding on to spillRecord can > overwhelm memory if Index Cache is overrun. In the case of single fetch, only > keep the single tez index record needed and for range fetch, keep the entire > spill record in memory, but free it after it is needed. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (TEZ-3954) Reduce Tez Shuffle Handler Memory needs for holding TezIndexRecords
[ https://issues.apache.org/jira/browse/TEZ-3954?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16534006#comment-16534006 ] Kuhu Shukla commented on TEZ-3954: -- The patch looks good to me . It would be nice to have a bit of a description on what the issue was and how it manifested to put the patch's approach in context. Thanks [~jeagles]. > Reduce Tez Shuffle Handler Memory needs for holding TezIndexRecords > --- > > Key: TEZ-3954 > URL: https://issues.apache.org/jira/browse/TEZ-3954 > Project: Apache Tez > Issue Type: Bug >Reporter: Jonathan Eagles >Assignee: Jonathan Eagles >Priority: Major > Attachments: TEZ-3954.001.patch > > > Tez Shuffle Handler holds on to entire SpillRecord to better accommodate for > range fetch operation. For single reduce fetch holding on to spillRecord can > overwhelm memory if Index Cache is overrun. In the case of single fetch, only > keep the single tez index record needed and for range fetch, keep the entire > spill record in memory, but free it after it is needed. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (TEZ-3963) Possible InflaterInputStream leaked in TezCommonUtils and related classes
[ https://issues.apache.org/jira/browse/TEZ-3963?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gopal V reassigned TEZ-3963: Assignee: Jaume M > Possible InflaterInputStream leaked in TezCommonUtils and related classes > -- > > Key: TEZ-3963 > URL: https://issues.apache.org/jira/browse/TEZ-3963 > Project: Apache Tez > Issue Type: Bug >Affects Versions: 0.9.1 >Reporter: Jaume M >Assignee: Jaume M >Priority: Major > > I don't think [this is > closed|https://github.com/apache/tez/blob/314dfc79b4b3f528b680b4fee73ad0dca3a3a19b/tez-api/src/main/java/org/apache/tez/common/TezCommonUtils.java#L397] -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (TEZ-3966) Tez UI config couldn't be executed in browser
[ https://issues.apache.org/jira/browse/TEZ-3966?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Roman Lukin updated TEZ-3966: - Description: Current name convention applied to the ui configuration file, produce the following error in web browser - mime type check fails (which based on file extesion) and if header `X-Content-Type-Options: nosniff` enabled config wouldn't be executed and used. As a result we may have problems, for instance links based on variable `yarnProtocol`. More about header - [https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/X-Content-Type-Options] Possible solution - rename file `config.env` to `config.js` [https://github.com/apache/tez/pull/26] [https://github.com/rlukin/tez/commit/8db8c04faee04dc161c90c3961233ec5aa40518e] Steps to reproduce: * Enable aforementioned header on web server * Try to load tez ui was: Current name convention applied to the ui configuration file, produce the following error in web browser - mime type check fails (which based on file extesion) and if header `X-Content-Type-Options: nosniff` enabled config wouldn't be executed and used. As a result we may have problems, for instance links based on variable `yarnProtocol`. More about header - [https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/X-Content-Type-Options] Possible solution - rename file `config.env` to `config.js` [https://github.com/apache/tez/pull/26] [https://github.com/rlukin/tez/commit/8db8c04faee04dc161c90c3961233ec5aa40518e] Steps to reproduce: * Enable header on web server * Try to load tez ui > Tez UI config couldn't be executed in browser > -- > > Key: TEZ-3966 > URL: https://issues.apache.org/jira/browse/TEZ-3966 > Project: Apache Tez > Issue Type: Bug > Components: UI >Reporter: Roman Lukin >Priority: Major > Attachments: Selection_043.png, Selection_044.png > > > Current name convention applied to the ui configuration file, produce the > following error in web browser - mime type check fails (which based on file > extesion) and if header `X-Content-Type-Options: nosniff` enabled config > wouldn't be executed and used. As a result we may have problems, for instance > links based on variable `yarnProtocol`. > More about header - > [https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/X-Content-Type-Options] > Possible solution - rename file `config.env` to `config.js` > [https://github.com/apache/tez/pull/26] > [https://github.com/rlukin/tez/commit/8db8c04faee04dc161c90c3961233ec5aa40518e] > > Steps to reproduce: > * Enable aforementioned header on web server > * Try to load tez ui -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (TEZ-3966) Tez UI config couldn't be executed in browser
[ https://issues.apache.org/jira/browse/TEZ-3966?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Roman Lukin updated TEZ-3966: - Description: Current name convention applied to the ui configuration file, produce the following error in web browser - mime type check fails (which based on file extesion) and if header `X-Content-Type-Options: nosniff` enabled config wouldn't be executed and used. As a result we may have problems, for instance links based on variable `yarnProtocol`. More about header - [https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/X-Content-Type-Options] Possible solution - rename file `config.env` to `config.js` [https://github.com/apache/tez/pull/26] [https://github.com/rlukin/tez/commit/8db8c04faee04dc161c90c3961233ec5aa40518e] Steps to reproduce: * Enable header on web server * Try to load tez ui was: Current name convention applied to the ui configuration file, produce the following error in web browser - mime type check fails (which based on file extesion) and if header `X-Content-Type-Options: nosniff` enabled config wouldn't be executed and used. As a result we may have problems, for instance links based on variable `yarnProtocol`. More about header - [https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/X-Content-Type-Options] Possible solution - rename file `config.env` to `config.js` [https://github.com/apache/tez/pull/26] [https://github.com/rlukin/tez/commit/8db8c04faee04dc161c90c3961233ec5aa40518e] Steps to reproduce: * Enable header on web server * Try to load tez ui * !Selection_043.png! > Tez UI config couldn't be executed in browser > -- > > Key: TEZ-3966 > URL: https://issues.apache.org/jira/browse/TEZ-3966 > Project: Apache Tez > Issue Type: Bug > Components: UI >Reporter: Roman Lukin >Priority: Major > Attachments: Selection_043.png, Selection_044.png > > > Current name convention applied to the ui configuration file, produce the > following error in web browser - mime type check fails (which based on file > extesion) and if header `X-Content-Type-Options: nosniff` enabled config > wouldn't be executed and used. As a result we may have problems, for instance > links based on variable `yarnProtocol`. > More about header - > [https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/X-Content-Type-Options] > Possible solution - rename file `config.env` to `config.js` > [https://github.com/apache/tez/pull/26] > [https://github.com/rlukin/tez/commit/8db8c04faee04dc161c90c3961233ec5aa40518e] > > Steps to reproduce: > * Enable header on web server > * Try to load tez ui -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (TEZ-3966) Tez UI config couldn't be executed in browser
[ https://issues.apache.org/jira/browse/TEZ-3966?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Roman Lukin updated TEZ-3966: - Description: Current name convention applied to the ui configuration file, produce the following error in web browser - mime type check fails (which based on file extesion) and if header `X-Content-Type-Options: nosniff` enabled config wouldn't be executed and used. As a result we may have problems, for instance links based on variable `yarnProtocol`. More about header - [https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/X-Content-Type-Options] Possible solution - rename file `config.env` to `config.js` [https://github.com/apache/tez/pull/26] [https://github.com/rlukin/tez/commit/8db8c04faee04dc161c90c3961233ec5aa40518e] Steps to reproduce: * Enable header on web server * Try to load tez ui * !Selection_043.png! was: Current name convention applied to the ui configuration file, produce the following error in web browser - mime type check fails (which based on file extesion) and if we enable header `X-Content-Type-Options: nosniff` config wouldn't be executed and used. As a result we may have problems, for instance links based on variable `yarnProtocol`. More about header - [https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/X-Content-Type-Options] Possible solution - rename file `config.env` to `config.js` [https://github.com/apache/tez/pull/26] [https://github.com/rlukin/tez/commit/8db8c04faee04dc161c90c3961233ec5aa40518e] Steps to reproduce: * Enable header on web server * Try to load tez ui * !Selection_043.png! > Tez UI config couldn't be executed in browser > -- > > Key: TEZ-3966 > URL: https://issues.apache.org/jira/browse/TEZ-3966 > Project: Apache Tez > Issue Type: Bug > Components: UI >Reporter: Roman Lukin >Priority: Major > Attachments: Selection_043.png, Selection_044.png > > > Current name convention applied to the ui configuration file, produce the > following error in web browser - mime type check fails (which based on file > extesion) and if header `X-Content-Type-Options: nosniff` enabled config > wouldn't be executed and used. As a result we may have problems, for instance > links based on variable `yarnProtocol`. > More about header - > [https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/X-Content-Type-Options] > Possible solution - rename file `config.env` to `config.js` > [https://github.com/apache/tez/pull/26] > [https://github.com/rlukin/tez/commit/8db8c04faee04dc161c90c3961233ec5aa40518e] > > Steps to reproduce: > * Enable header on web server > * Try to load tez ui > * !Selection_043.png! -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (TEZ-3966) Tez UI config couldn't be executed in browser
[ https://issues.apache.org/jira/browse/TEZ-3966?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16533410#comment-16533410 ] ASF GitHub Bot commented on TEZ-3966: - Github user rlukin commented on the issue: https://github.com/apache/tez/pull/26 @jteagles https://issues.apache.org/jira/browse/TEZ-3966 > Tez UI config couldn't be executed in browser > -- > > Key: TEZ-3966 > URL: https://issues.apache.org/jira/browse/TEZ-3966 > Project: Apache Tez > Issue Type: Bug > Components: UI >Reporter: Roman Lukin >Priority: Major > Attachments: Selection_043.png, Selection_044.png > > > Current name convention applied to the ui configuration file, produce the > following error in web browser - mime type check fails (which based on file > extesion) and if we enable header `X-Content-Type-Options: nosniff` config > wouldn't be executed and used. As a result we may have problems, for instance > links based on variable `yarnProtocol`. > More about header - > [https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/X-Content-Type-Options] > Possible solution - rename file `config.env` to `config.js` > [https://github.com/apache/tez/pull/26] > [https://github.com/rlukin/tez/commit/8db8c04faee04dc161c90c3961233ec5aa40518e] > > Steps to reproduce: > * Enable header on web server > * Try to load tez ui > * !Selection_043.png! -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (TEZ-3966) Tez UI config couldn't be executed in browser
Roman Lukin created TEZ-3966: Summary: Tez UI config couldn't be executed in browser Key: TEZ-3966 URL: https://issues.apache.org/jira/browse/TEZ-3966 Project: Apache Tez Issue Type: Bug Components: UI Reporter: Roman Lukin Attachments: Selection_043.png, Selection_044.png Current name convention applied to the ui configuration file, produce the following error in web browser - mime type check fails (which based on file extesion) and if we enable header `X-Content-Type-Options: nosniff` config wouldn't be executed and used. As a result we may have problems, for instance links based on variable `yarnProtocol`. More about header - [https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/X-Content-Type-Options] Possible solution - rename file `config.env` to `config.js` [https://github.com/apache/tez/pull/26] [https://github.com/rlukin/tez/commit/8db8c04faee04dc161c90c3961233ec5aa40518e] Steps to reproduce: * Enable header on web server * Try to load tez ui * !Selection_043.png! -- This message was sent by Atlassian JIRA (v7.6.3#76005)
