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

ASF GitHub Bot commented on FLINK-10601:
----------------------------------------

link3280 commented on issue #6887: [FLINK-10601] [YARN] Make user home dir 
consistent with Flink default filesystem
URL: https://github.com/apache/flink/pull/6887#issuecomment-445095013
 
 
   This may break [FLINK-6376] for the application probably will not apply for 
the HDFS delegation that YARN uses for log aggregation, hence close this PR.

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on 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


> Make user home dir consistent with Flink default filesystem
> -----------------------------------------------------------
>
>                 Key: FLINK-10601
>                 URL: https://issues.apache.org/jira/browse/FLINK-10601
>             Project: Flink
>          Issue Type: Improvement
>          Components: YARN
>    Affects Versions: 1.6.1
>            Reporter: Paul Lin
>            Assignee: Paul Lin
>            Priority: Major
>              Labels: pull-request-available
>
> Currently, Flink client uses the raw default Hadoop filesystem to upload 
> local files, and this could be problematic when using a non-default 
> filesystem for HA or checkpointing in delegation tokens scenarios. The 
> jobmanager only has the delegation tokens for the default FS, so it gets 
> authentication errors when trying to connect a non-default filesystem.
> So I propose to replace the default FS property in yarn configuration with 
> the Flink filesystem property `fs.default-scheme` on the client side 
> (AbstractYarnClusterDescriptor), to avoid this problem and also make the 
> client behavior more configurable.



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

Reply via email to