Thats correct. With the fully async option the checkpoints take longer but
you don't impact ongoing processing of elements. With the semi-async method
snapshots take a shorter time but during the synchronous part no element
processing can happen.
On Fri, 20 May 2016 at 15:04 Abhishek Singh
wrote:
Yes. Thanks for explaining.
On Friday, May 20, 2016, Ufuk Celebi wrote:
> On Thu, May 19, 2016 at 8:54 PM, Abhishek R. Singh
> > wrote:
> > If you can take atomic in-memory copies, then it works (at the cost of
> > doubling your instantaneous memory). For larger state (say rocks DB),
> won’t
> >
On Thu, May 19, 2016 at 8:54 PM, Abhishek R. Singh
wrote:
> If you can take atomic in-memory copies, then it works (at the cost of
> doubling your instantaneous memory). For larger state (say rocks DB), won’t
> you have to stop the world (atomic snapshot) and make a copy? Doesn’t that
> make it sy
No problem ;)
On Thu, May 19, 2016 at 9:54 PM, Abhishek R. Singh <
abhis...@tetrationanalytics.com> wrote:
> If you can take atomic in-memory copies, then it works (at the cost of
> doubling your instantaneous memory). For larger state (say rocks DB), won’t
> you have to stop the world (atomic s
If you can take atomic in-memory copies, then it works (at the cost of doubling
your instantaneous memory). For larger state (say rocks DB), won’t you have to
stop the world (atomic snapshot) and make a copy? Doesn’t that make it
synchronous, instead of background/async?
Sorry Stravros - for bu
