Topic
  • 3 replies
  • Latest Post - ‏2013-06-10T11:44:55Z by jhanders
AnkiaP
AnkiaP
4 Posts

Pinned topic Dynamic Cache Provider - cache entry locks

‏2013-05-30T07:32:16Z |
When configuring WebSphere eXtreme Scale as the cache provider for an existing Object Cache Instance on WebSphere Application Server with remote topology, how does one control / show intent to upgrade an entry in the cache, to result in a U-lock being established on that entry as opposed to intent to only read an entry in the cache and thereby establishing an S-lock on that entry? When using the ObjectMap API in the case of a Simple Side Cache the user is in control of this by deliberatly using either get(key)/keyAll() or getForUpdate(key)/getAllForUpdate(). 
Also, am I correct to make the assumption that where a remote topology is configured that the locking strategy will automatically be set to Pessimistic and does the user have any control over this?
We are making use of WXS Client 8.5.0.3 and XC10 firmware 2.1.0.3
  • jhanders
    jhanders
    261 Posts
    ACCEPTED ANSWER

    Re: Dynamic Cache Provider - cache entry locks

    ‏2013-06-10T10:28:13Z  

    eXtreme Scale follows the Dynamic Cache contract which does not give the user the ability to lock an entry with intent to update it.  The API only has get and put operations.  If you need more control, it is recommended to use the eXtreme Scale APIs.  The eXtreme Scale Dynamic Cache Provider is provided for existing Dynamic Cache application and it not necessarily intended for new applications.  New applications that need caching should use the eXtreme Scale APIs if possible.

    In version 8.5, you did not have the control to change the locking strategy.  In version 8.6, a new Dynamic Cache configuration was introduced where you can choose to use an optimistic locking strategy with a near cache if desired.  The 8.6 eXtreme Scale Dynamic Cache Provider makes use of additional features in 8.6 as well.  These include near cache invalidation for the optimistic locking configuration and global index for either pessimistic or optimistic locking configurations.  These are optional and can be enabled or disabled depending on your application requirements.  Near cache invalidation allows you to keep the near cache from being stale.  Global index improves your invalidation response time.

    I hope that covers all your questions.  If not let us know.

    Jared Anderson

  • jhanders
    jhanders
    261 Posts
    ACCEPTED ANSWER

    Re: Dynamic Cache Provider - cache entry locks

    ‏2013-06-10T11:44:55Z  
    • AnkiaP
    • ‏2013-06-10T11:33:06Z

    Thank you, Jared. This makes sense.

    Now just urgently awaiting firmware upgrade for XC10 appliance that will be compatible with XIO functionality in WXS 8.6 so that we can make use of the much needed near cache invalidation and global index features.

    It will be here soon as previously announced here.

    Jared

  • jhanders
    jhanders
    261 Posts

    Re: Dynamic Cache Provider - cache entry locks

    ‏2013-06-10T10:28:13Z  

    eXtreme Scale follows the Dynamic Cache contract which does not give the user the ability to lock an entry with intent to update it.  The API only has get and put operations.  If you need more control, it is recommended to use the eXtreme Scale APIs.  The eXtreme Scale Dynamic Cache Provider is provided for existing Dynamic Cache application and it not necessarily intended for new applications.  New applications that need caching should use the eXtreme Scale APIs if possible.

    In version 8.5, you did not have the control to change the locking strategy.  In version 8.6, a new Dynamic Cache configuration was introduced where you can choose to use an optimistic locking strategy with a near cache if desired.  The 8.6 eXtreme Scale Dynamic Cache Provider makes use of additional features in 8.6 as well.  These include near cache invalidation for the optimistic locking configuration and global index for either pessimistic or optimistic locking configurations.  These are optional and can be enabled or disabled depending on your application requirements.  Near cache invalidation allows you to keep the near cache from being stale.  Global index improves your invalidation response time.

    I hope that covers all your questions.  If not let us know.

    Jared Anderson

  • AnkiaP
    AnkiaP
    4 Posts

    Re: Dynamic Cache Provider - cache entry locks

    ‏2013-06-10T11:33:06Z  
    • jhanders
    • ‏2013-06-10T10:28:13Z

    eXtreme Scale follows the Dynamic Cache contract which does not give the user the ability to lock an entry with intent to update it.  The API only has get and put operations.  If you need more control, it is recommended to use the eXtreme Scale APIs.  The eXtreme Scale Dynamic Cache Provider is provided for existing Dynamic Cache application and it not necessarily intended for new applications.  New applications that need caching should use the eXtreme Scale APIs if possible.

    In version 8.5, you did not have the control to change the locking strategy.  In version 8.6, a new Dynamic Cache configuration was introduced where you can choose to use an optimistic locking strategy with a near cache if desired.  The 8.6 eXtreme Scale Dynamic Cache Provider makes use of additional features in 8.6 as well.  These include near cache invalidation for the optimistic locking configuration and global index for either pessimistic or optimistic locking configurations.  These are optional and can be enabled or disabled depending on your application requirements.  Near cache invalidation allows you to keep the near cache from being stale.  Global index improves your invalidation response time.

    I hope that covers all your questions.  If not let us know.

    Jared Anderson

    Thank you, Jared. This makes sense.

    Now just urgently awaiting firmware upgrade for XC10 appliance that will be compatible with XIO functionality in WXS 8.6 so that we can make use of the much needed near cache invalidation and global index features.

  • jhanders
    jhanders
    261 Posts

    Re: Dynamic Cache Provider - cache entry locks

    ‏2013-06-10T11:44:55Z  
    • AnkiaP
    • ‏2013-06-10T11:33:06Z

    Thank you, Jared. This makes sense.

    Now just urgently awaiting firmware upgrade for XC10 appliance that will be compatible with XIO functionality in WXS 8.6 so that we can make use of the much needed near cache invalidation and global index features.

    It will be here soon as previously announced here.

    Jared