1 2 3 Previous Next 35 Replies Latest reply on Jul 31, 2006 5:38 AM by Galder Zamarreño

    Reactivating SharedStoreCacheLoader

    Galder Zamarreño Master

      As per conversations with Bela and Manik, I'm planning to have a go at
      http://jira.jboss.com/jira/browse/JBCACHE-650 which refers to
      reactivating SharedStoreCacheLoader. Had a quick look at it and this is
      what I think needs to be done:

      - Refactor SharedStoreCacheLoader to SingletonCacheLoader
      - Adding a tag to cacheloader element called, for example, singleton?
      This'd be a similar to what it was done with AsyncCacheLoader.
      - Enable, via configuration, dumping of the in-memory state when a node
      becomes the coordinator. Maybe using a pushStateWhenCoordinator
      attribute in the singleton element (defaul value would be true)? i.e.

      <singleton pushStateWhenCoordinator="true">

      - Configuration changes will need to be backported to 1.2.x using the old
      CacheLoader configuration style (http://wiki.jboss.org/wiki/Wiki.jsp?page=JBossCacheCacheLoaders)
      - viewChange in SingletonCacheLoader would have to change in order to
      transfer the in-memory state into the underlying cache loader. Haven't
      looked at the specific details of this, but I expect to do that in the next few
      days. Just wanted to start the discussion.
      - Validate that singleton is not used when the cache has been configured
      with evictions.

      This JIRA task is also very similar to http://jira.jboss.com/jira/browse/JBCACHE-623.
      We probably wanna merge them into one? JBCACHE-623 mentions the
      configuration requirements and the need to dump the in-memory state
      when changing the coordinator. But it also adds the fact that
      CacheLoaderShared needs to be false, which makes sense anyway.

        1 2 3 Previous Next