[jira] [Created] (FLINK-1546) Failed job causes JobManager to shutdown due to uncatched WebFrontend exception

Robert Metzger created FLINK-1546: - Summary: Failed job causes JobManager to shutdown due to uncatched WebFrontend exception Key: FLINK-1546 URL: https://issues.apache.org/jira/browse/FLINK-1546

Re: Measuring Iteration Timings

Hi, Right now, you have to parse the logs (of the TaskManager running the Sync Task). We've created the linked images using this (very hacky) tool: https://github.com/project-flink/flink-perf/blob/master/flink-jobs/src/main/java/com/github/projectflink/utils/IterationParser.java . I'm currently

Re: Measuring Iteration Timings

Johannes! You can also customize your messages by printing a message to standard out in the open() and close() methods of your functions. You have to extend the RichFunction in that case. Greetings, Stephan On Sat, Feb 14, 2015 at 4:47 PM, Kirschnick, Johannes johannes.kirschn...@tu-berlin.de

[jira] [Created] (FLINK-1547) Disable automated ApplicationMaster restart

Robert Metzger created FLINK-1547: - Summary: Disable automated ApplicationMaster restart Key: FLINK-1547 URL: https://issues.apache.org/jira/browse/FLINK-1547 Project: Flink Issue Type: Bug

[jira] [Created] (FLINK-1548) [DISCUSS] Make Scala implicit parameters explicit in the runtime

Stephan Ewen created FLINK-1548: --- Summary: [DISCUSS] Make Scala implicit parameters explicit in the runtime Key: FLINK-1548 URL: https://issues.apache.org/jira/browse/FLINK-1548 Project: Flink

Measuring Iteration Timings

Hi, I have a simple question on to how one could measure the individual execution times for an iteration step, without parsing the logs :) Is there a best practise for that? I'm interested in producing something like this http://data-artisans.com/img/blog/bulk_runtimes.png From the blog

Re: Measuring Iteration Timings

Hi, thanks for the quick answer - this tool might just do the job for the moment. Johannes Von: Robert Metzger rmetz...@apache.org Gesendet: Samstag, 14. Februar 2015 16:38 An: dev@flink.apache.org Betreff: Re: Measuring Iteration Timings Hi, Right now,

Re: [DISCUSS] Scala code style - explicit vs implicit code behavior

+1 to the idea I suppose no really action item for FLINK-1548? Maybe add doc about contributing to Scala portion? On Saturday, February 14, 2015, Stephan Ewen se...@apache.org wrote: Hi everyone! Since a sizable portion of the Flink code is now in Scala (and more is coming in the API

Re: [Gelly]Distributed Minimum Spanning Tree Example

Hi Andra, I haven't had a detailed look at Gelly and its functions, but Flink has only few operators which can cause undeterministic behavior. In general, user code should be implemented without side effects, i.e., the result of each function call may only depend on its arguments. This principle

[jira] [Created] (FLINK-1549) Add proper exception handling for YarnJobManager

Till Rohrmann created FLINK-1549: Summary: Add proper exception handling for YarnJobManager Key: FLINK-1549 URL: https://issues.apache.org/jira/browse/FLINK-1549 Project: Flink Issue Type: