Anyone have any inside information on the state of play re clustering?
I see 6.1 has new tables that look like they are to support replication, eg ReplicatedIndexOperation and ClusterMessage. I have heard about a new (expensive) jira archiving product - are these tables just for that, or is there genuine movement on clustering, or horizontal scaling?
Hi Jamie and all.
Yes the Atlassian JIRA team is working on a clusterable solution for JIRA that will provide both HA and Scale across several nodes. This is in addition to another solution we are looking at to help with large instance performance - JIRA Archiving.
We're still early in the development and we hope to have it released mid next year.
JIRA Product Management
2100 fields is not being restrictive with fields, it implies you've got business and configuration problems, as well as technical ones. One of my clients had 800 when I started with them, and by simply talking to the users, we were able to reduce it to 90, which helped a bit with performance, and a LOT with business reporting and consistency.
Atlassian are trialling clustering, which should help with most of the issues with larger installations.
We have customers requiring clustering. At AtlasCamp I discussed with them (Atl) and they said to me that they are looking into the clustering - again. They said it's going to be very expensive (I personally don't care, but customers will do).
The target for a solution (but it's kinda blurry) would be half of 2014 (at least that's what I understood).
I will let Atl comment on this, I'm intrested as well ....
I think the problem with clustering is the Confluence / JIRA home folders. Unless that mostly disappears and a few other things, clustering won't happen. I don't see how they'd get customers to cluster and also arrange a distributed file system and other things all just to get it working.
Anything is doable. Usability is the key. Once it gets too complex, add a lot of instructions - it's no longer feasible. It'll be a support/maintenance hell and neither the vendor nor the customers want to touch it.
It also greatly increases costs and diminishes the competitive advantages vs many other products in the market.
Having seen a large Websphere cluster being deployed and run, I'd say I don't want to deal with anything like it in the near future.
I don't see why it will be so difficult. If you index something you also index it on the other nodes. It's the same database at the backend.
Also, this is not going to be free - my guess is each node will be the same price as jira, therefore the support you get will be commensurate with that.
BTW, you should be a bit more pro-clustering, given your company name!
I am pro clustering. I did NOT say clustering is difficult. I'm merely pointing out the implementation problems due to the way Atlassian has currently structured it and how it can improve.
It's difficult because it's been made difficult. I'm sure Atlassian are aware of this and will try to address it. No sharing would be easiest to cluster with a traditional model of web servers, server side sessions etc - hence the home folder being an issue.
Can you define "too complex"? If you think, the way WAS does clustering is quite simple. Of course, they could offer you a button and a list for you to say "cluster these instances using the default values", but in some cases, it will not be what you want.
What is trully killing is the clustering of an WebSphere Portal (which has been a nightmare from the very beginning).
Anyway, clustering is not *usually* attempted by stupid people ....
Hey Community mates! Claire here from the Software Product Marketing team. We all know software development changes rapidly, and it's often tough to keep up. But from our research, we've found the h...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG