Terracotta Discussion Forums (LEGACY READ-ONLY ARCHIVE)

If all you want to do is add a field to the class of a shared object, you probably don't need to do anything other than add the field to the class. New fields on already shared objects will be null or default value if those fields are not initialized in the default constructor of the class.

Could you provide a little more context? What are you trying to add to ManagerUtil and why?

We actually use Terracotta internally to run distributed tests. There's a bunch of stuff in there to start the terracotta server, run tests on multiple clients, collect and report results.

FYI, Jetty support is apparently very close.

A further point is that, if an object is resident in only one JVM (as happens when work on a particular set of objects happens on a particular JVM), then changes to that object will not be replicated across the cluster.

When work is partitioned well with, for example, a load balancer or the master-worker architecture, lock acquisition and object change will become very efficient.

Lock acquisition will become local (rather than clustered) due to greedy locks and object changes will only get sent from the JVM with the changing thread down to the Terracotta server-- the rest of the cluster won't see any of it, unless and until that object is used on another JVM.

For more information on the difference between physical and logical change management, see this page in the docs: http://www.terracotta.org/confluence/display/docs1/Concept+and+Architecture+Guide#ConceptandArchitectureGuide-physicalvslogical

This is the url to that document: http://www.terracotta.org/confluence/display/devdocs/Sessions+Architecture

I'm trying to think of how to get the user-facing stuff in this document into the regular documentation. In the meantime, Alex V. should probably update this to the current values.

I'm pretty sure the new cluster events stuff in 2.3 can tell you when the server goes down. I'm still researching how it works to write the docs. Alex V. might be best able to answer this one.

The problem is that the docdraft space in confluence isn't publically visible. I did that so it doesn't show up in searches while we're working on the new docs. But, it does make the links break in the nightly builds.

I should probably change the permissions to the docdraft space. That way, people using nightly builds can get the draft documentation.

I've put up some example code on clustering Lucene with Terracotta:

http://wiki.terracotta.org/confluence/display/labs/Lucene+Clustering

Most of the infrastructure for the Terracotta Forge Labs project is in place. You can read about it here: http://wiki.terracotta.org/confluence/display/labs/Home