Skip to content
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

Config path for database storage #1265

Closed
dazoot opened this issue Apr 6, 2020 · 8 comments
Closed

Config path for database storage #1265

dazoot opened this issue Apr 6, 2020 · 8 comments

Comments

@dazoot
Copy link

dazoot commented Apr 6, 2020

We store the files on a shared drive (cifs mounted).
We have local SSD drives.
Would like to specify the weed volume server to used an alternate folder for database storage.
So instead of storing .idx files on the network drive, store them local on fast SSD.

@chrislusf
Copy link
Collaborator

Which volume index are you using? memory or leveldb?

Well, yes, there will be two writes, one to .dat and one to .idx files.

If in memory, seems no need to store the index on SSD specifically, especially for reads.

@dazoot
Copy link
Author

dazoot commented Nov 16, 2020

Leveldb.

@chrislusf
Copy link
Collaborator

In your case, how large are the SSD and HDD sizes respectively?

@dazoot
Copy link
Author

dazoot commented Nov 16, 2020

we store 5TB of data.
SSD is 960GB

@chrislusf
Copy link
Collaborator

chrislusf commented Nov 16, 2020

ok. btw: planning to support ssd-only volumes. it is different from your request. would that be useful to your use case?

@dazoot
Copy link
Author

dazoot commented Nov 18, 2020

Should be configurable:

  • data_storage paths
  • index_storage paths

So users can choose what suits them better.

@chrislusf
Copy link
Collaborator

chrislusf commented Nov 27, 2020

Added this feature. Let me know how it works for you.

When starting volume server, use -dir.idx=... for index storage path.

@chrislusf
Copy link
Collaborator

fixed in 2.13

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants