This content has been marked as final.
Show 1 reply
-
1. Re: Asynchronous replication on REPL_SYNC
otaylor Sep 29, 2006 8:55 AM (in response to ruchiahuja10)It looks to me like you are using the Hibernate "TreeCache" cache provider. What the last two messages are from is a cache "put' - reading data from the cache failed, so after Hibernate fetched the data from the database it stored it into the cache. The store into the cache is done in a special manner so it:
- Is independent from the current transaction (it's data read from the database, so even if the transaction is rolled back, it's still valid). Thta's what "Non-tx crud meth" means.
- Is replicated to other nodes asynchronously (if other nodes don't have the data before the replication happens, they'll just read it from the database.) That's what "forcing asynchronous replicatoin for putFailFast()" means.