Quartz Where - permitting control of where jobs execute in a clustered environment through node groups and node type constraints A getting-started page for using Quartz Scheduler Locality API is available: Getting Started With Quartz Scheduler Locality API

Clustered Quartz performance improvements

Additional Improvements

Developer console improvements

Platform Updates

Certification on JDK 1.6.0_24

About Ehcache Search

The Ehcache Search API allows you to execute arbitrarily complex queries against Ehcache. The standalone Ehcache Search implementation is limited to the memoryStore (ie it has no support for diskStore or BigMemory - aka offHeapStore). Ehcache Search support for distributed caches is an Enterprise-only feature, and is designed to work across all Terracotta server storage tiers (memory, BigMemory, and disk).

The easiest way to get started with the API is to try the sample application posted on github. This includes a ready to run bundle for *nix (just download, unpack, and execute with 'sh run.sh'). This bundle also includes a maven pom to rebuild (using the latest SNAPSHOT rather than that in the bundle): https://github.com/sharrissf/Ehcache-Search-Sample/downloads

New configuration options

NonStopCache is disabled by default, to enable non-stop, update the <terracotta> element in each <cache>

Code Block

xml

xml

<terracotta clustered="true">
<nonstop enabled="true"/>
</terracotta>

Ehcache rejoin on disconnect from Terracotta Server Array is disabled by default and can be enabled as follows in ehcache.xml. Note: that rejoin enable is dependent on NonStopCache being enabled.

Code Block

xml

xml

<terracottaConfig rejoin="true" url="localhost:9510" />

Ehcache now has three transaction modes:

local, which will use a local transaction manager (rather than a JTA one), and permit users to create ACID operations across multiple caches

Code Block

xml

xml

transactionalMode="local"

xa, which in Beta1 was temporarily called jta_local will use a JTA transaction manager, but will be designed for use with a single resource manager in mind and to work with a lower level of recoverability than the "xa_strict" mode. (it won't recover transaction is the case of catastrophic failure).

Code Block

xml

xml

transactionalMode="xa"

The original "xa" mode is now "xa_strict". Transactional caches can be made nonstop only in xa_strict mode.

About Quartz Scheduler 2.0

Note: Quartz Where is only supported when using the TerracottaJobStore, and is an enterprise-only feature.

Upgrade Information

Brief descriptions of major changes that may affect upgrades from previous versions of Terracotta product installations are listed in this section. See the product documentation for more information.

Change to <cache> "coherent" Attribute

The <cache> coherent attributed is deprecated in favor of consistency=[strong | eventual]. For example, where you've used coherent="true" use consistency="strong". For coherent="false" use consistency="eventual" (eventually consistent). If you've set the coherent attribute programmatically, the setting will continue to be honored and mapped as described.

New Transactionnal Modes

The <cache> attribute transactionalMode can now have one of the following values:

off – Default.

local – Transactional to a local store; no external XA resource used.

xa – Basic JTA support.

xa_strict – Full JTA support.

Note that with a transactional cache, the <cache> attribute coherent must be set to "strong".

NonStopCache Becomes a <cache> Subelement

NonStopCache is no longer a decorator. Default values for NonStopCache behavior settings have also changed.

Change in default storageStrategy for distributed Ehcache

The DCV2 strategy is now the default. The old strategy is deprecated, but can be accessed by setting storageStrategy=classic. Note: many of the new features (such as eventual consistency, rejoin, and nonstop) are not compatible with classic.

DCV2 is optimized for large data sets. In certain environments, including ones with small data sets, this optimization may need to be tuned to avoid higher latency and memory usage. If your cluster experiences these issues after upgrading, reduce cache concurrency from the default 2048 to a lower number using the concurrency attribute of the <cache> element's <terracotta> subelement:

Code Block

xml

xml

<cache ... >
...
<terracotta concurrence="10" ... />
</cache>

Change in server side eviction precedence for distributed Ehcache

Server side eviction now gives precedence to the maxElementsOnDisk setting over TTI/TTL, and thus if the total number of elements reaches maxElementsOnDisk, entries will be evicted from cache irrespective of whether they have expired or not.