4 Replies Latest reply on Feb 4, 2011 10:37 AM by Sudheer Krishna

    Clarifications on Distributed mode & L1 caching

    Sudheer Krishna Novice

      HI,

       

      Distributed mode looks very appleaing , but i had a few clarificatiosn on the same

       

      1.  Quoting from the docs

       

      "Doing a PUT would result in at most num_copies remote calls, and doing a GET anywhere in the cluster would result in at most 1 remote call. In reality, num_copies remote calls are made even for a GET, but these are done in parallel and as soon as any one of these returns, the entry is passed back to the caller."

       

      Is there any specific reason to make num_copies remote calls ? . Can i disable this to make only 1 call ? [I know this will not reduce time involved , but surely will reduce network trafic]

       

      2. Quoting from docs [L1 caching]

       

       

      "L1 caching is not free though. Enabling it comes at a cost, and this cost is that every time a key is updated, an invalidation message needs to be multicast to ensure nodes with the entry in L1 invalidates the entry"

       

      So i understand that  this invalidation message is sent and L1 cache becomes dirty(handled by infinispan). So next time i try to access , since L1 cache is dirty it will go across teh network and fetch the latest update.

       

      Based on this can i assume that i will always get the "latest correct value" , even if i give L1 cache timeout as infinite(very high value) ?.