Elastic search is creating huge nodes on my system.
We had 200G on our server and our repositories have grown to 96G.
Elastic search consumed the addtional 100G in less than a week.
So we increased the storage to 400g and elastic_search consumed 300G in less than 3 weeks.
What can I do to minimize disk usage for elastic search?
Unfortunately there's little you can do at the moment. We're considering changes to improve this, including better treatment of forks. Could you give us an idea as to the nature of your instance? Do you have many repos, large repos (especially with large text files), or lots of forks? Feel free to raise a support issue at support.atlassian.com and mention me/this thread if you want to share more sensitive info (eg support tools zip, instance details).
This community is celebrating its one-year anniversary and Atlassian co-founder Mike Cannon-Brookes has all the feels.Read more
Bitbucket Pipelines helps me manage and automate a number of serverless deployments to AWS Lambda and this is how I do it. I'm building Node.js Lambda functions using node-lambda ...
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
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs