[
https://issues.apache.org/jira/browse/BEAM-8293?focusedWorklogId=317787&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-317787
]
ASF GitHub Bot logged work on BEAM-8293:
----------------------------------------
Author: ASF GitHub Bot
Created on: 24/Sep/19 19:44
Start Date: 24/Sep/19 19:44
Worklog Time Spent: 10m
Work Description: robertwb commented on pull request #9646: [BEAM-8293]
prescriptive log message for artifact retrieval failure
URL: https://github.com/apache/beam/pull/9646
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
[email protected]
Issue Time Tracking
-------------------
Worklog Id: (was: 317787)
Time Spent: 20m (was: 10m)
> Document or log file system issues with docker
> ----------------------------------------------
>
> Key: BEAM-8293
> URL: https://issues.apache.org/jira/browse/BEAM-8293
> Project: Beam
> Issue Type: Improvement
> Components: java-fn-execution
> Reporter: Kyle Weaver
> Assignee: Kyle Weaver
> Priority: Minor
> Time Spent: 20m
> Remaining Estimate: 0h
>
> A frequently asked question about portability in the mailing list is, "Why am
> I getting IOExceptions in my job?" where the answer is often, because the SDK
> harness is using docker, which does not have access to the local filesystem
> by default, so when users try to read/write via transforms or don't set a
> artifact_staging_location, they get errors. We should at least document this
> on the website. Even better would be to log something, especially for
> artifact_staging_location, which is implicit and users might not be aware of.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
