New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
✨✨ Needs of an easy way to asign second hdd to deploy Elasticsearch DB #424
Comments
If this is just a storage size issue - would expanding the volume work ? |
Hi pevma, thanks for fast response. May be it would . So I tried with symlink mv /var/lib/docker /mnt/docker |
Not sure i understand - you are saying it worked or it is still not working as expected ? |
What is the time span - it seems there are alerts? |
There should be data i mean. Is it the same if you change the timespan / reload? |
Could it be browser cache ? If you clear it would there be any effect? |
Hi,
|
Is there an existing feature request that has already been created?
Is your feature request related to a problem? Please describe.
Hi SELKS gurus. I have a propusal and question at the same time.
First my question:
I want to deploy Elasticsearch DB on second hdd wich is moined in /mnt/elasticdb as /dev/sdb1. My knowledge about docker is not enough to make this deploy by myself.
This is the step in installer that I can't over it:
By default, elasticsearch database is stored in a docker volume in /var/lib/docker (free space: 62G
With SELKS running, database can take up a lot of disk space
You might want to save them on an other disk/partition
How to pass trought this step to set up all it in right way?
p.p. I searched about /var/lib/docker in docker-compose.yaml but only thing that I found about elastic is this row:
${ELASTIC_DATAPATH:-elastic-data}:/usr/share/elasticsearch/data
I think that will be wrong if I set this /mnt/elasticdb:/usr/share/elasticsearch/data
Describe the solution you would like?
Second propusal:
Will be nice to have opinion to setup this important step trought installer directly without many modificaton from user side in docker files
Alternative Solutions
No response
Additional Context
No response
The text was updated successfully, but these errors were encountered: