Mailing-List: contact dev-help@apex.incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@apex.incubator.apache.org
MIME-Version: 1.0
In-Reply-To: 
 <CA+QE8bcce1yWvSKXPWPAzuKgDtBcANnbbVn7hngcaEH6b-oGBA@mail.gmail.com>
References: 
 <CA+QE8bcce1yWvSKXPWPAzuKgDtBcANnbbVn7hngcaEH6b-oGBA@mail.gmail.com>
Date: Mon, 14 Dec 2015 23:58:12 -0800
Message-ID: 
 <CADS+zCsrs47D7ZBxsNZDLSrzW-Mp0NYc1pc64wbL+rqGHhx48A@mail.gmail.com>
Subject: Re: operator recovery window
From: Timothy Farkas <tim@datatorrent.com>
To: dev@apex.incubator.apache.org
Content-Type: multipart/alternative; boundary=001a11331ca2bac98a0526eb26b6

--001a11331ca2bac98a0526eb26b6
Content-Type: text/plain; charset=UTF-8

Hi Ashwin,

The recovery checkpoint for operator A is computed by taking the checkpoint
with the largest window id that is less than or equal to the checkpoint
with the largest window id among all the operators down stream to A. The
output operators in a dag will always recover to their most recent
checkpoint. The input operator of the dag may recover to the earliest
checkpoint. Operators between the input and ouput operators could recover
to a window in between.

I don't think you can ever recover to a committed window, the earliest I
think you can recover to is the window after the committed window (may be
wrong on this).

On Mon, Dec 14, 2015 at 11:05 PM, Ashwin Chandra Putta <
ashwinchandrap@gmail.com> wrote:

> In the apex architecture there is concept of checkpointing and concept of
> committed when all operator have crossed a common checkpoint.
>
> So, in which scenarios does a given operator recover at last checkpoint
> window vs last committed window vs some other checkpoint window in between?
> --
>
> Regards,
> Ashwin.
>

--001a11331ca2bac98a0526eb26b6--