Re: [VOTE] Release 1.8.0, release candidate #4

2019-03-30 Thread Aljoscha Krettek
Thanks everyone, for discovering these! @Richard Could you open a Jira issue for this and mark it as blocking? > On 29. Mar 2019, at 09:22, Tzu-Li (Gordon) Tai wrote: > > @Yu discovered this issue, which IMO is probably a blocker for the > release: https://issues.apache.org/jira/browse/FLINK-1

Re: [VOTE] Release 1.8.0, release candidate #4

2019-03-30 Thread Aljoscha Krettek
@Richard Did this work for you previously? From the change, it seems that the port was always set to 0 on YARN even before. > On 28. Mar 2019, at 16:13, Richard Deurwaarder wrote: > > -1 (non-binding) > > - Ran integration tests locally (1000+) of our flink job, all succeeded. > - Attempted to

[jira] [Created] (FLINK-12071) HadoopRecoverableWriterTest fails on Travis

2019-03-30 Thread Chesnay Schepler (JIRA)
Chesnay Schepler created FLINK-12071: Summary: HadoopRecoverableWriterTest fails on Travis Key: FLINK-12071 URL: https://issues.apache.org/jira/browse/FLINK-12071 Project: Flink Issue Typ

Re: [VOTE] Release 1.8.0, release candidate #4

2019-03-30 Thread Rong Rong
Hi @Aljoscha, Based on the previous commit [1] that adds the random port selection code, it seems like the important part is to unset whatever 'rest.port' setting previously done. I don't think the current way of setting the BIND_PORT actually overrides any existing PORT setting. However, I wasn't

[jira] [Created] (FLINK-12072) Unable to Capture Metrics of AsyncIO

2019-03-30 Thread sravan.korumilli (JIRA)
sravan.korumilli created FLINK-12072: Summary: Unable to Capture Metrics of AsyncIO Key: FLINK-12072 URL: https://issues.apache.org/jira/browse/FLINK-12072 Project: Flink Issue Type: Bug