I’m running on Flink 1.7.0 trying to use the StreamingFileSink with an S3A URI. What I’m seeing is that whenever the RollingPolicy determines that it’s time to roll to a new part file, the whole Sink just hangs, and the in progress MultiPart
Upload never gets completed. I’ve looked at the traffic between Flink and the S3 endpoint, and I don’t ever see the POST message that should close off a completed upload. Has anyone else run into something like that? Nick Martin Notice: This e-mail is intended solely for use of the individual or entity to which it is addressed and may contain information that is proprietary, privileged and/or exempt from disclosure under applicable law. If the reader is not the intended recipient or agent responsible for delivering the message to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. This communication may also contain data subject to U.S. export laws. If so, data subject to the International Traffic in Arms Regulation cannot be disseminated, distributed, transferred, or copied, whether incorporated or in its original form, to foreign nationals residing in the U.S. or abroad, absent the express prior approval of the U.S. Department of State. Data subject to the Export Administration Act may not be disseminated, distributed, transferred or copied contrary to U. S. Department of Commerce regulations. If you have received this communication in error, please notify the sender by reply e-mail and destroy the e-mail message and any physical copies made of the communication. Thank you. ********************* |
Hi Nick, This is a known issue with 1.7.0, I have an issue opened up here: https://issues.apache.org/jira/browse/FLINK-11187 On Wed, Jan 2, 2019 at 5:00 PM Martin, Nick <[hidden email]> wrote:
|
Hi Addison, From the information that Nick provides, how can you be sure that the root cause is the same? Cheers, Kostas On Fri, Jan 4, 2019, 22:10 Addison Higham <[hidden email] wrote:
|
The not seeing the final post from the logs was what initially clued me into the same issue, so I figured it was the same issue, but I should have worded it better that it is one possible explanation. Sorry for the confusion! Addison On Fri, Jan 4, 2019 at 11:24 PM Kostas Kloudas <[hidden email]> wrote:
|
No problem and thanks for looking into the problem! I also commented on the JIRA. Cheers, Kostas On Mon, Jan 7, 2019, 18:13 Addison Higham <[hidden email] wrote:
|
Free forum by Nabble | Edit this page |