jira home on network drive

Hi

we have set up all our Jiras to use our SAN area for their JIRA Homes. This is for a resilient area for storing backups and attachments and because or virtualised servers have limited space.

However we have found that is there is an interruption in access to the SAN e.g. network outage or maintenance then JIRA will crash when writing to disk.

Some posts on this forum hint that a network home may not be a good idea.

Is there a preferred way to approach this?

Is there any JIRA configuration to enable connections to be re-established periodically link a pooled db connection would?

Regards

Tom Lister

2 answers

1 accepted

0 vote

I would not have said "hint", I would have said there's a vast amount of very clear "do not put the home directory on a shared drive" messages.  (Unless you're on data-centre, but that's a different story)

Yes, it's crashing, and it's also slowing your systems down, and gradually corrupting your indices.

You need to put the home directory on a fast disk, and that absolutely means a  local disk.  The documentation explictly states that the index cannot be placed on NFS or SAN.  It's not a case of reconnecting, you need to move those home directories to local disks.

That said, you can put some sub-directories of home on shares - attachments and the backup directories stand out as things that can work, as JIRA doesn't need fast read/write access to them.   You could get away with logs too, but I tend to stick to just attachments.

Thanks - we'll plan how to do this

in order to put attachments and backups onto shares, is that via symbolic links? As all directories are hanging off JIRA Home root.

Yes, symbolic links work fine.

Could you please share how did you mention your shared network folder location as the jira home ? I am trying a cluster set up and my jira.shared.home is never taken.

@Nic Brough [Adaptavist], what did you mean by:

 Unless you're on data-centre, but that's a different story

DC does support shared storage for some parts of the installation, as it needs to.

But you should not try to use shared storage for Server (or try to cluster it or anything like that)

Hi All,

I resolved my issue in Windows by mapping the networked folder location (NFS) into a local drive letter in my load balancer's host. It is working fine now. Thanks!

Suggest an answer

Log in or Join to answer
Community showcase
Emilee Spencer
Published Friday in Marketplace Apps

Marketplace Spotlight: DeepAffects

Hello Atlassian Community! My name is Emilee, and I’m a Product Marketing Manager for the Marketplace team. Starting with this post, I'm kicking off a monthly series of Spotlights to highlight Ma...

56 views 0 3
Read article

Atlassian User Groups

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!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you
Atlassian Team Tour

Join us on the Team Tour

We're bringing product updates and pro tips on teamwork to ten cities around the world.

Save your spot