[jira] [Created] (FLINK-10214) why is job applying as many TMs as default parallelism when starting, each parallelism is 1

lzh9 created FLINK-10214: Summary: why is job applying as many TMs as default parallelism when starting, each parallelism is 1 Key: FLINK-10214 URL: https://issues.apache.org/jira/browse/FLINK-10214 Project:

[jira] [Created] (FLINK-10213) Task managers cache a negative DNS lookup of the blob server indefinitely

Joey Echeverria created FLINK-10213: --- Summary: Task managers cache a negative DNS lookup of the blob server indefinitely Key: FLINK-10213 URL: https://issues.apache.org/jira/browse/FLINK-10213 Proje

[jira] [Created] (FLINK-10212) REST API for listing all the available save points

Marc Rooding created FLINK-10212: Summary: REST API for listing all the available save points Key: FLINK-10212 URL: https://issues.apache.org/jira/browse/FLINK-10212 Project: Flink Issue Type

Re: Flink cluster crashing going from 1.4.0 -> 1.5.3

With `latencyTrackingInterval` set to `0` cluster runs fine. So, is this something which make sense to be improved? JIRA I can track or file one? On Fri, Aug 24, 2018 at 11:50 AM Chesnay Schepler wrote: > I believe the only thing you can do is disable latency tracking, by > setting the `latencyT

[jira] [Created] (FLINK-10211) Time indicators are not always materialised for LogicalJoin

Piotr Nowojski created FLINK-10211: -- Summary: Time indicators are not always materialised for LogicalJoin Key: FLINK-10211 URL: https://issues.apache.org/jira/browse/FLINK-10211 Project: Flink

[jira] [Created] (FLINK-10210) Time indicators are not always materialised for LogicalCorrelate

Piotr Nowojski created FLINK-10210: -- Summary: Time indicators are not always materialised for LogicalCorrelate Key: FLINK-10210 URL: https://issues.apache.org/jira/browse/FLINK-10210 Project: Flink

Re: Flink cluster crashing going from 1.4.0 -> 1.5.3

I believe the only thing you can do is disable latency tracking, by setting the `latencyTrackingInterval` in `env.getExecutionConfig()` to 0 or a negative value. The update frequency is not configurable and currently set to 10 seconds. Latency metrics are tracked as the cross-product of all su

Re: Flink cluster crashing going from 1.4.0 -> 1.5.3

For my small job, I see ~24k those latency metrics @ '/jobs/.../metrics'. That job is much smaller in terms of production parallelism. Are there any options here. Can it be turned off, reduced histogram metrics, reduced update frequency, ... ? Also, keeping it flat seems to use quite some memory o

[jira] [Created] (FLINK-10209) Exclude jdk.tools dependency from hadoop when running with java 9

Chesnay Schepler created FLINK-10209: Summary: Exclude jdk.tools dependency from hadoop when running with java 9 Key: FLINK-10209 URL: https://issues.apache.org/jira/browse/FLINK-10209 Project: Fl

[jira] [Created] (FLINK-10208) Bump mockito to 2.0+

Chesnay Schepler created FLINK-10208: Summary: Bump mockito to 2.0+ Key: FLINK-10208 URL: https://issues.apache.org/jira/browse/FLINK-10208 Project: Flink Issue Type: Sub-task C

[jira] [Created] (FLINK-10207) Bump checkstyle-plugo to 8.9

Chesnay Schepler created FLINK-10207: Summary: Bump checkstyle-plugo to 8.9 Key: FLINK-10207 URL: https://issues.apache.org/jira/browse/FLINK-10207 Project: Flink Issue Type: Sub-task

Re: Flink cluster crashing going from 1.4.0 -> 1.5.3

In 1.5 the latency metric was changed to be reported on the job-level, that's why you see it under /jobs/.../metrics now, but not in 1.4. In 1.4 you would see something similar under /jobs/.../vertices/.../metrics, for each vertex. Additionally it is now a proper histogram, which significantly

[jira] [Created] (FLINK-10206) Add hbase stream connector

Igloo created FLINK-10206: - Summary: Add hbase stream connector Key: FLINK-10206 URL: https://issues.apache.org/jira/browse/FLINK-10206 Project: Flink Issue Type: Improvement Components: St