Mailing-List: contact user-help@ignite.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@ignite.apache.org
MIME-Version: 1.0
In-Reply-To: <1493281599713-12287.post@n6.nabble.com>
References: <1493136744840-12242.post@n6.nabble.com> <1493145245309-12247.post@n6.nabble.com>
 <58ff9f9e.09ab1c0a.2071.c01b@mx.google.com> <1493193409284-12256.post@n6.nabble.com>
 <010f01d2be72$a86a8cb0$f93fa610$@gmail.com> <1493279726308-12285.post@n6.nabble.com>
 <1493281599713-12287.post@n6.nabble.com>
From: Gaurav Bajaj <gauravhbajaj@gmail.com>
Date: Thu, 27 Apr 2017 10:53:24 +0200
Message-ID: <CAFbb4Pww9AchaiXmRkMKRKXfNyUv=CzON0yJB9J_qqk0xvTUqg@mail.gmail.com>
Subject: Re: Write behind and eventual consistency
To: user@ignite.apache.org
Content-Type: multipart/alternative; boundary=f403045ea2b6024a7f054e221724
archived-at: Thu, 27 Apr 2017 08:53:32 -0000

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

Hi Val,

Our use case :

1. Read records from file
2. Do computations on each record
3. Put them in the cache and persistence using write behind.
4. When all the records from file are processed, updated in Cache and also
persisted to DB, we want to
 trigger some other process which will do next set of operations on these
records from cache.
5. We want to trigger this next process and mark original file as
processed, only when we are sure data is persisted, so that in case of Node
failure we need not process that file again.


On Thu, Apr 27, 2017 at 10:26 AM, steve.hostettler <
steve.hostettler@gmail.com> wrote:

> Hi Val,
>
> the use case is the following
>
> 1) Load data into the database from an external system
> 2) Once ready load it into the grid
> 3) Process something that does massive write behinds
> 4) Take a snapshot of the results (or) Do a backup of the tables   <<--- At
> this point I need the eventual consistency to ...eventually be
>
> At step 4 I cannot afford to have some update still in progress. This is
> even more important since because of write behind I cannot maintain
> referential integrity (since the insert/update are done in a random order)
>
>
>
> --
> View this message in context: http://apache-ignite-users.
> 70518.x6.nabble.com/Write-behind-and-eventual-
> consistency-tp12242p12287.html
> Sent from the Apache Ignite Users mailing list archive at Nabble.com.
>

--f403045ea2b6024a7f054e221724
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Hi Val,<div><br></div><div>Our use case :</div><div><br></=
div><div>1. Read records from file</div><div>2. Do computations on each rec=
ord</div><div>3. Put them in the cache and persistence using write behind.<=
/div><div>4. When all the records from file are processed, updated in Cache=
 and also persisted to DB, we want to</div><div>=C2=A0trigger some other pr=
ocess which will do next set of operations on these records from cache.</di=
v><div>5. We want to trigger this next process and mark original file as pr=
ocessed, only when we are sure data is persisted, so that in case of Node f=
ailure we need not process that file again.</div><div><br></div><div><br></=
div><div><br></div><div><br></div><div><br></div><div><br></div><div><br></=
div><div><br></div><div><br></div><div><br></div><div><br></div><div><br></=
div><div><br></div><div><br></div><div><br></div><div><br></div><div><br></=
div><div><br></div><div><br></div></div><div class=3D"gmail_extra"><br><div=
 class=3D"gmail_quote">On Thu, Apr 27, 2017 at 10:26 AM, steve.hostettler <=
span dir=3D"ltr">&lt;<a href=3D"mailto:steve.hostettler@gmail.com" target=
=3D"_blank">steve.hostettler@gmail.com</a>&gt;</span> wrote:<br><blockquote=
 class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc soli=
d;padding-left:1ex">Hi Val,<br>
<br>
the use case is the following<br>
<br>
1) Load data into the database from an external system<br>
2) Once ready load it into the grid<br>
3) Process something that does massive write behinds<br>
4) Take a snapshot of the results (or) Do a backup of the tables=C2=A0 =C2=
=A0&lt;&lt;--- At<br>
this point I need the eventual consistency to ...eventually be<br>
<br>
At step 4 I cannot afford to have some update still in progress. This is<br=
>
even more important since because of write behind I cannot maintain<br>
referential integrity (since the insert/update are done in a random order)<=
br>
<br>
<br>
<br>
--<br>
View this message in context: <a href=3D"http://apache-ignite-users.70518.x=
6.nabble.com/Write-behind-and-eventual-consistency-tp12242p12287.html" rel=
=3D"noreferrer" target=3D"_blank">http://apache-ignite-users.<wbr>70518.x6.=
nabble.com/Write-<wbr>behind-and-eventual-<wbr>consistency-tp12242p12287.ht=
ml</a><br>
<div class=3D"HOEnZb"><div class=3D"h5">Sent from the Apache Ignite Users m=
ailing list archive at Nabble.com.<br>
</div></div></blockquote></div><br></div>

--f403045ea2b6024a7f054e221724--