Uploaded image for project: 'Geode'
  1. Geode
  2. GEODE-6878

Remove documentation around enableLocalCache for Tomcat session peer-to-peer topology

    Details

    • Type: Improvement
    • Status: Open
    • Priority: Major
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: docs, http session
    • Labels:
      None

      Description

      There isn't any use case for enabling local caching in a peer-to-peer topology when using the Tomcat session state module, because the session region type is REPLICATE so an additional local ("fronting") region adds no benefit.  At one time the peer-to-peer session region type was not REPLICATE so a local region could have added performance benefits, but this is no longer the case.  As such, we should remove any documentation around enableLocalCache JUST for peer-to-peer topology.  The documentation for client-server should remain.

       

      Default: false for peer-to-peer, true for client/server
      The GemFire API equivalent to setting this parameter:
      // For peer-to-peer members: Cache.createRegionFactory(REPLICATE_PROXY); // For client members: ClientCache.createClientRegionFactory(CACHING_PROXY_HEAP_LRU);
      

      should become something like:

       

      enableLocalCache is only useful in a client/server topology.  Local caching is enabled by default in this topology.
      
      The GemFire API equivalent to setting this parameter:
      ClientCache.createClientRegionFactory(CACHING_PROXY_HEAP_LRU);
      

       

       

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                Unassigned
                Reporter:
                rmcmahon Ryan McMahon
              • Votes:
                0 Vote for this issue
                Watchers:
                1 Start watching this issue

                Dates

                • Created:
                  Updated: