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?
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.
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
We're bringing product updates and pro tips on teamwork to ten cities around the world.Save your spot