Return-Path: X-Original-To: apmail-flink-user-archive@minotaur.apache.org Delivered-To: apmail-flink-user-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 8280917AF6 for ; Fri, 10 Oct 2014 12:04:46 +0000 (UTC) Received: (qmail 42429 invoked by uid 500); 10 Oct 2014 12:04:46 -0000 Delivered-To: apmail-flink-user-archive@flink.apache.org Received: (qmail 42376 invoked by uid 500); 10 Oct 2014 12:04:46 -0000 Mailing-List: contact user-help@flink.incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@flink.incubator.apache.org Delivered-To: mailing list user@flink.incubator.apache.org Received: (qmail 42367 invoked by uid 99); 10 Oct 2014 12:04:46 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 10 Oct 2014 12:04:46 +0000 X-ASF-Spam-Status: No, hits=-1996.7 required=5.0 tests=ALL_TRUSTED,DATE_IN_PAST_03_06,HTML_MESSAGE,T_RP_MATCHES_RCVD X-Spam-Check-By: apache.org Received: from [140.211.11.3] (HELO mail.apache.org) (140.211.11.3) by apache.org (qpsmtpd/0.29) with SMTP; Fri, 10 Oct 2014 12:04:45 +0000 Received: (qmail 42306 invoked by uid 99); 10 Oct 2014 12:04:25 -0000 Received: from mail-relay.apache.org (HELO mail-relay.apache.org) (140.211.11.15) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 10 Oct 2014 12:04:25 +0000 Received: from mail-la0-f50.google.com (mail-la0-f50.google.com [209.85.215.50]) by mail-relay.apache.org (ASF Mail Server at mail-relay.apache.org) with ESMTPSA id 1E26C1A054F for ; Fri, 10 Oct 2014 12:04:16 +0000 (UTC) Received: by mail-la0-f50.google.com with SMTP id s18so3121509lam.9 for ; Fri, 10 Oct 2014 05:04:19 -0700 (PDT) X-Gm-Message-State: ALoCoQnkl+kEH+sUs7nhVdavsJ2JSoArwA7E871q/NLMqQKoW9Zbch8tDldVjemoK7eisVGxV6pq MIME-Version: 1.0 X-Received: by 10.112.130.226 with SMTP id oh2mr1240334lbb.100.1412928843999; Fri, 10 Oct 2014 01:14:03 -0700 (PDT) Received: by 10.112.1.3 with HTTP; Fri, 10 Oct 2014 01:14:03 -0700 (PDT) In-Reply-To: <201410101018241318528@gmail.com> References: <1412866048.70097.ezmlm@flink.incubator.apache.org> <201410101018241318528@gmail.com> Date: Fri, 10 Oct 2014 10:14:03 +0200 Message-ID: Subject: Re: Two question about flink From: Ufuk Celebi To: "user@flink.incubator.apache.org" Content-Type: multipart/alternative; boundary=047d7b3a82b0d70ffc05050d21f2 X-Virus-Checked: Checked by ClamAV on apache.org --047d7b3a82b0d70ffc05050d21f2 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Hey! Thanks for writing! On Friday, October 10, 2014, hustjackie wrote: > > 1. in cluster mode, if one node has crash, what's the failover? is there > one mechanism to guarantees fault-tolerance? > We currently support coarse-grained fault tolerance via program restarts. This will be soon extended to more fine grained fault tolerance, where only necessary parts of a program are re-executed. > 2. is there a performance report? > There are some new performance numbers coming up soon. I think there are also some older numbers from Robert. Let's wait what he has to say. =E2=80=93 Ufuk > --047d7b3a82b0d70ffc05050d21f2 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Hey! Thanks for writing!

On Friday, October 10, 2014, hustjackie <= ;hustjackie@gmail.com> wrote= :
1. in cluster= =20 mode, if one node has crash, what's the failover? is there one mechanis= m to=20 guarantees=20 fault-tolerance?

We currently s= upport coarse-grained fault tolerance via program restarts. This will be so= on extended to more fine grained fault tolerance, where only necessary=C2= =A0parts of a program are re-executed.
=C2=A0
2.=20 is there a performance report?

There are some new=C2=A0performance numbers coming up soo= n. I think there are also some older numbers from Robert. Let's wait wh= at he has to say.

=E2=80=93 Ufuk
--047d7b3a82b0d70ffc05050d21f2--