« FUD OF THE WEEK: JBossCache to Terracotta migration...a response to JBoss from Terracotta | Main | Terracotta, the book »

December 5, 2007

Have you heard? JIRA was clustered using Terracotta

posted by ari

SourceSense did this without our help. And, JIRA is closed-source software from Atlassian...pretty amazing actually. (I know one can get the source quite readily. I don't know if Sourcesense had it at hand to do the job.)

http://sbtourist.blogspot.com/2007/12/news-about-scarlet.html


My favorite part of this is that Atlassian clustered Confluence over a year ago on their own and their CEO presented the results at a few conferences. I would paraphrase his presentation as:

clustering is _really hard_ and impacts the application in significant ways. Don't undertake it lightly! But it is possible.

Here's a 3rd party summary of Mike's presentation from Javapolis, 2006.

I discussed this with Mike via his blog in the past, but with Terracotta, Lucene and Quartz are both clustered out of the box.

Lessons learned in my opinion are that our ability to cluster transparently is very important. It might have made Confluence clustering easier. Not sure. It definitely made JIRA clustering possible for developers outside Atlassian. Enough said.

--Ari


Trackback Pings

TrackBack URL for this entry:
http://blog.terracottatech.com/cgi-bin/mt/mt-tb.cgi/29

Comments

Hi Ari,

thanks for your kind words!

Clustering Atlassian Jira was a very hard work indeed, and without Terracotta transparent clustering capabilities it would have been harder and harder.

Too bad, it wasn't possible to use the already shipped configuration modules for Lucene and Quartz, so we had to cluster them by hand. That was because:


  • Lucene configuration module didn't work with the version of Lucene used by Jira.

  • Quartz configuration module clusters Quartz itself, but we had to cluster the service classes used by Jira inside Quartz jobs. Moreover, we had to provide a way to distribute Jira services in the cluster, that is, to run a single service in each node.

However, it's just as you said: Terracotta made it possible to cluster Jira without requiring deep knowledge of Jira (very) inner workings, and without having to deeply modify Jira internal behavior.

Posted by: Sergio Bossa at December 6, 2007 3:14 AM

Hi Ari,
I posted some thoughts on your comment.


Posted by: Ugo Landini at December 6, 2007 1:04 PM

Post a comment




Remember Me?

(you may use HTML tags for style)