[ 
https://issues.apache.org/jira/browse/YARN-7909?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16359125#comment-16359125
 ] 

Gour Saha commented on YARN-7909:
---------------------------------

We see similar issue in unsecure cluster too, like when trying to flex a 
component with an invalid component name via CLI -
{code:java}
$ yarn app -flex sleeper-1 -component sleeper-bad 2
WARNING: YARN_LOG_DIR has been replaced by HADOOP_LOG_DIR. Using value of 
YARN_LOG_DIR.
WARNING: YARN_LOGFILE has been replaced by HADOOP_LOGFILE. Using value of 
YARN_LOGFILE.
WARNING: YARN_PID_DIR has been replaced by HADOOP_PID_DIR. Using value of 
YARN_PID_DIR.
WARNING: YARN_OPTS has been replaced by HADOOP_OPTS. Using value of YARN_OPTS.
18/02/09 23:49:05 WARN util.NativeCodeLoader: Unable to load native-hadoop 
library for your platform... using builtin-java classes where applicable
18/02/09 23:49:05 INFO client.RMProxy: Connecting to ResourceManager at 
ctr-e138-1518143905142-1244-01-000002.hwx.site/172.27.47.0:8050
18/02/09 23:49:06 INFO client.AHSProxy: Connecting to Application History 
server at ctr-e138-1518143905142-1244-01-000003.hwx.site/172.27.47.192:10200
18/02/09 23:49:06 INFO client.RMProxy: Connecting to ResourceManager at 
ctr-e138-1518143905142-1244-01-000002.hwx.site/172.27.47.0:8050
18/02/09 23:49:06 INFO client.AHSProxy: Connecting to Application History 
server at ctr-e138-1518143905142-1244-01-000003.hwx.site/172.27.47.192:10200
18/02/09 23:49:06 INFO util.log: Logging initialized @2216ms
18/02/09 23:49:07 ERROR client.ApiServiceClient: Fail to flex application:
java.nio.charset.UnsupportedCharsetException: null
at java.nio.charset.Charset.forName(Charset.java:531)
at com.sun.jersey.core.util.ReaderWriter.getCharset(ReaderWriter.java:143)
at com.sun.jersey.core.util.ReaderWriter.readFromAsString(ReaderWriter.java:157)
at 
com.sun.jersey.core.provider.AbstractMessageReaderWriterProvider.readFromAsString(AbstractMessageReaderWriterProvider.java:114)
at 
com.sun.jersey.core.impl.provider.entity.StringProvider.readFrom(StringProvider.java:73)
at 
com.sun.jersey.core.impl.provider.entity.StringProvider.readFrom(StringProvider.java:58)
at com.sun.jersey.api.client.ClientResponse.getEntity(ClientResponse.java:634)
at com.sun.jersey.api.client.ClientResponse.getEntity(ClientResponse.java:586)
at 
org.apache.hadoop.yarn.service.client.ApiServiceClient.processResponse(ApiServiceClient.java:200)
at 
org.apache.hadoop.yarn.service.client.ApiServiceClient.actionFlex(ApiServiceClient.java:418)
at org.apache.hadoop.yarn.client.cli.ApplicationCLI.run(ApplicationCLI.java:519)
at org.apache.hadoop.util.ToolRunner.run(ToolRunner.java:76)
at org.apache.hadoop.util.ToolRunner.run(ToolRunner.java:90)
at 
org.apache.hadoop.yarn.client.cli.ApplicationCLI.main(ApplicationCLI.java:111){code}
But the 001 patch fixes this issue though. So I would say the patch looks good.

 

 

> YARN service REST API returns charset=null when kerberos enabled
> ----------------------------------------------------------------
>
>                 Key: YARN-7909
>                 URL: https://issues.apache.org/jira/browse/YARN-7909
>             Project: Hadoop YARN
>          Issue Type: Bug
>          Components: yarn-native-services
>    Affects Versions: 3.1.0
>            Reporter: Eric Yang
>            Assignee: Eric Yang
>            Priority: Major
>         Attachments: YARN-7909.001.patch
>
>
> When kerberos is enabled, the response header will reply with:
> {code:java}
> Content-Type: application/json;charset=null{code}
> This appears to be somehow AuthenticationFilter is trigger charset to become 
> undefined.
> The same problem is not observed when simple security is enabled.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

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

Reply via email to