[ 
https://issues.apache.org/jira/browse/SPARK-21487?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

lishuming updated SPARK-21487:
------------------------------
    Description: 
We upgraded Spark version from 2.0.2 to 2.1.1 recently,  WebUI `Executors Page` 
becomed empty, with the exception below.

`Executor Page` rendering using javascript language rather than scala in 2.1.1, 
but I don't know why causes this result?

"two queries are submitted at the same time and have the same timestamp may 
cause this result", but I'm not sure?

ResouceManager log:
{code:java}
2017-07-20 20:39:09,371 WARN 
org.apache.hadoop.security.authentication.server.AuthenticationFilter: 
Authentication exception: GSSException: Failure unspecified at GSS-API level 
(Mechanism level: Request is a replay (34))
{code}

Safari explorer console
{code:java}
Failed to load resource: the server responded with a status of 403 
(GSSException: Failure unspecified at GSS-API level (Mechanism level: Request 
is a replay 
(34)))http://hadoop-rm-host:8088/proxy/application_1494564992156_2751285/static/executorspage-template.html
{code}

Related Links:
https://issues.apache.org/jira/browse/HIVE-12481
https://issues.apache.org/jira/browse/HADOOP-8830

  was:
We upgraded Spark version from 2.0.2 to 2.1.1 recently,  WebUI `Executors Page` 
becomed empty, with the exception below.

`Executor Page` rendering using javascript language rather than scala in 2.1.1, 
but I don't know why causes this result?

"two queries are submitted at the same time and have the same timestamp may 
cause this result", but I'm not sure?

ResouceManager log:
{code:java}
2017-07-20 20:39:09,371 WARN 
org.apache.hadoop.security.authentication.server.AuthenticationFilter: 
Authentication exception: GSSException: Failure unspecified at GSS-API level 
(Mechanism level: Request is a replay (34))
{code}

Safari explorer console
{code:java}
Failed to load resource: the server responded with a status of 403 
(GSSException: Failure unspecified at GSS-API level (Mechanism level: Request 
is a replay 
(34)))http://hadoop280.lt.163.org:8088/proxy/application_1494564992156_2751285/static/executorspage-template.html
{code}

Recent Links:
https://issues.apache.org/jira/browse/HIVE-12481
https://issues.apache.org/jira/browse/HADOOP-8830


> WebUI-Executors Page results in "Request is a replay (34) attack"
> -----------------------------------------------------------------
>
>                 Key: SPARK-21487
>                 URL: https://issues.apache.org/jira/browse/SPARK-21487
>             Project: Spark
>          Issue Type: Bug
>          Components: Web UI
>    Affects Versions: 2.1.1
>            Reporter: lishuming
>            Priority: Minor
>
> We upgraded Spark version from 2.0.2 to 2.1.1 recently,  WebUI `Executors 
> Page` becomed empty, with the exception below.
> `Executor Page` rendering using javascript language rather than scala in 
> 2.1.1, but I don't know why causes this result?
> "two queries are submitted at the same time and have the same timestamp may 
> cause this result", but I'm not sure?
> ResouceManager log:
> {code:java}
> 2017-07-20 20:39:09,371 WARN 
> org.apache.hadoop.security.authentication.server.AuthenticationFilter: 
> Authentication exception: GSSException: Failure unspecified at GSS-API level 
> (Mechanism level: Request is a replay (34))
> {code}
> Safari explorer console
> {code:java}
> Failed to load resource: the server responded with a status of 403 
> (GSSException: Failure unspecified at GSS-API level (Mechanism level: Request 
> is a replay 
> (34)))http://hadoop-rm-host:8088/proxy/application_1494564992156_2751285/static/executorspage-template.html
> {code}
> Related Links:
> https://issues.apache.org/jira/browse/HIVE-12481
> https://issues.apache.org/jira/browse/HADOOP-8830



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@spark.apache.org
For additional commands, e-mail: issues-h...@spark.apache.org

Reply via email to