Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,458,380
Community Members
 
Community Events
176
Community Groups

Hosting Jira Home on NFS

Howdy,

      Our organization uses NFS mounts for both the SHARED home and the individual NODE home for Jira data center.  There is some discussion about whether it is supported or in general a good idea.  I'm hoping someone from Atlassian can settle this argument for us. 

 

Thanks!

1 comment

I'm not sure where you might think there has been any "discussion".

Atlassian do not support it, and it has always been a really bad idea.  The Lucene indexing fails when it is on NFS. 

See https://confluence.atlassian.com/kb/health-check-lucene-index-files-location-873918046.html

And move yours to a supported file system as soon as possible before it fails and takes out your Jira.

Like Cameron Jeffries likes this

The top-level JIRA_HOME directory must be local, but you can relocate some of the directories to alternate locations (like NFS) with a symlink, as Atlassian advise this for relocating attachments.

I would think "caches" and "tmp" are definitely off-limits.  Are the other directories fair game?

EDIT:  Played around with this a bit and would add "plugins" to the list of subdirectories you definitely shouldn't move off the local disk.

 

The discussion I was hoping there would have been was in the forums, where you graciously provided some!  Thanks!

I was mostly just trying to cement what I considered to be a generally "bad idea" as an "unsupported configuration" or even a "don't do that, it's an awful idea".  We were able to convince the architect to make the change to using block devices and everything started working swimmingly.  I also wanted to put this in the forums so that anyone else in my position could have a document to look at and say "see, using the local home on a network drive is a bad idea".  For those of you doing that.  It's a REALLY bad idea.

Comment

Log in or Sign up to comment