Here's the problem:
How do I "safely" determine JIRA attachment sizes with minimal impact to my end users?
Here is the solution I used:
nice -n 20 ionice -c 3 find /opt/j2ee/domains/atlassian.com/support/jira-home/data/attachments/ -size +25M -exec ls -lah {} \; | awk '{print "size:"$5"\tname: "$9}' > /opt/scratch/attachments_over_25MB.txt
Where I am looking to find attachments greater than 25MB.
Note how I use ionice -c 3 which ensures that I will not have io contention between JIRA and my search. I also used nice to minimize CPU contention.
Thank you for sharing this resource.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.