You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@ignite.apache.org by Evgenii Zhuravlev <e....@gmail.com> on 2017/06/01 12:39:00 UTC
Re: Client Server Persistent Store Fault Tolerance
>so that the other clients are missing the value that they
should write (they didn't show any error/exception)
I don't understand, which values are they missing?
When transaction should be rolled back, nodes will re-read values from db,
because, when you use write-through, it has consistent data.
What did you mean by "inconsistent data"? Did you lost data within one
transaction?
Evgenii
2017-05-31 12:16 GMT+03:00 rickynauvaldy <ri...@sci.ui.ac.id>:
> In addition, it is not a problem if I only run 1 client. The problem arise
> when I run more than 1 client.
>
>
>
> -----
> -- Ricky
> --
> View this message in context: http://apache-ignite-users.
> 70518.x6.nabble.com/Client-Server-Persistent-Store-Fault-
> Tolerance-tp13054p13263.html
> Sent from the Apache Ignite Users mailing list archive at Nabble.com.
>
Re: Client Server Persistent Store Fault Tolerance
Posted by Evgenii Zhuravlev <e....@gmail.com>.
You have 2998 instead of 3000, because 2 of your transactions were rolled
back. You should handle this exceptions and run transaction again, if it
was rolled back.
It's not inconsistent data.
2017-06-02 6:01 GMT+03:00 rickynauvaldy <ri...@sci.ui.ac.id>:
> Evgenii Zhuravlev wrote
> > What did you mean by "inconsistent data"? Did you lost data within one
> > transaction?
>
> I run 3 server nodes and 3 client nodes, that in this example each of the
> client node run 1000 transaction for one row by adding '1' in each loop.
> When I stop 1 server nodes, all 3 client nodes will pause for a moment, and
> then only one of them will catch the CacheException that happened because
> of
> an exception in transaction try-catch, while the others not. Then, 1 of the
> alive server node will perform 'load data from database', and the process
> continue.
>
> When the process finished, the value of the changed row should be 3000,
> right? But actually it's only 2998. This is what I mean by "inconsistent
> data", I apologize if I get the term wrong.
>
>
>
>
>
> -----
> -- Ricky
> --
> View this message in context: http://apache-ignite-users.
> 70518.x6.nabble.com/Client-Server-Persistent-Store-Fault-
> Tolerance-tp13054p13329.html
> Sent from the Apache Ignite Users mailing list archive at Nabble.com.
>
Re: Client Server Persistent Store Fault Tolerance
Posted by rickynauvaldy <ri...@sci.ui.ac.id>.
Evgenii Zhuravlev wrote
> What did you mean by "inconsistent data"? Did you lost data within one
> transaction?
I run 3 server nodes and 3 client nodes, that in this example each of the
client node run 1000 transaction for one row by adding '1' in each loop.
When I stop 1 server nodes, all 3 client nodes will pause for a moment, and
then only one of them will catch the CacheException that happened because of
an exception in transaction try-catch, while the others not. Then, 1 of the
alive server node will perform 'load data from database', and the process
continue.
When the process finished, the value of the changed row should be 3000,
right? But actually it's only 2998. This is what I mean by "inconsistent
data", I apologize if I get the term wrong.
-----
-- Ricky
--
View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Client-Server-Persistent-Store-Fault-Tolerance-tp13054p13329.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.