Hi, 1) Dht nodes is remote nodes which actually store data. Let's I explain it on simple example. You start transaction and update 10 keys. This keys mapped on dht 3 nodes (this entries phisycly will be stored on this nodes). You need to consisitency updates data on all nodes and persiste them CacheStore too. Ignite is not able to transactionally update store from 3 nodes. (It different processe, JVM and etc. Also how many db do you khow that support it? ;) ) By this reasons near node (which started transaction) propagate an updates to store.
2) As Yakov said about it you can do it by org.apache.ignite.lifecycle.LifecycleAware. Look at org.apache.ignite.cache.store.jdbc.CacheAbstractJdbcStore as example. Also you could use store factory for initialization CacheConfiguration#setCacheStoreFactory 3) Are you sure that you invoked loadLoad() and got write() on client node? Could you share logs from both nodes: server and client? 4) To be honest this question not clear. Could you provide more context about what you mean? On Thu, Jun 1, 2017 at 4:42 PM, rick_tem <[email protected]> wrote: > Hi Yakov, > > Thanks for you reply, it is appreciated, but I still have questions. > > When you say: 1) we don't have an option to write-through from dht nodes? > What is a dht node? Are you saying I can't write my own write-through > cache > store? > 2) I agree that initialization isn't the best in loadCache. But how do I > then do it? It is Ignite that is creating this class and the cache > returned > from ignite.getCache is not an instance of my class. > 3) Client mode seems inconsistent. It is not calling loadCache() as > expected but why would it call write()...It should be a proxy to the server > node, not acting as a server. > 4) Are you saying Ignite does not keep transactional state consistent > across > nodes for write-through? For any cache store? Even JDBC cache store? > > Thanks, > Rick > > > > > -- > View this message in context: http://apache-ignite-users. > 70518.x6.nabble.com/Why-is-custom-cacheStore-write-being- > called-in-clientMode-tp13309p13317.html > Sent from the Apache Ignite Users mailing list archive at Nabble.com. >
