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

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

link3280 opened a new pull request #6887: [FLINK-10601] [YARN] Make user home 
dir consistent with Flink default filesystem
URL: https://github.com/apache/flink/pull/6887
 
 
   ## What is the purpose of the change
   
   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 make the default FS consistent with the Flink filesystem 
property fs.default-scheme (if it's set) on the client side 
(AbstractYarnClusterDescriptor), to avoid this problem and also make the client 
behavior more configurable.
   
   ## Brief change log
   
   - Replace the fs.defaultFS property in the yarn configuration with the 
initiated Flink filesystem's default scheme if it's not local.
   
   ## Verifying this change
   
   This change added tests and can be verified as follows:
   
   - Set the default fs in core.xml to a non-exist fs, and set the 
fs.default-scheme property to a valid one in flink-conf.yaml, then run the 
WordCount example to see if it works well. There would be errors while the 
client tries to upload the files to the remote system if things go wrong.
   
   ## Does this pull request potentially affect one of the following parts:
   
     - Dependencies (does it add or upgrade a dependency): no
     - The public API, i.e., is any changed class annotated with 
`@Public(Evolving)`: no
     - The serializers: no
     - The runtime per-record code paths (performance sensitive): no
     - Anything that affects deployment or recovery: JobManager (and its 
components), Checkpointing, Yarn/Mesos, ZooKeeper: no
     - The S3 file system connector: no
   
   ## Documentation
   
     - Does this pull request introduce a new feature? no
     - If yes, how is the feature documented? not applicable
   

----------------------------------------------------------------
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:
[email protected]


> 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
>            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