-
-
Notifications
You must be signed in to change notification settings - Fork 96
Allow for separating persistent state and log directories #758
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
Conversation
9b1cc47
to
3abff93
Compare
This is useful. However, from a UX perspective I think it's weird to specify both |
I mean, speaking from a UX perspective, it is usually expected that Adding a separate DB directory can be done, but I'm not sure if it makes any sense. In any case, the defaults would then have to be changed:
This would be not be a backwards-compatible change. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just a wording nit on the changelog.
Yeah, that actually remains the same. My point was more like that we are now starting to differentiate, maybe we'll even get |
Let’s discuss this on Monday. I’d rather change the directory option to work like most other UNIX CLI tools have their directory option work. Especially with regards to our focus on UX. |
@mavam I have discussed this with @0ortmann, in order to determine what the natural and expected behavior is for him from a UX standpoint. This is what we converged on:
|
d58ed52
to
e57d3b0
Compare
e57d3b0
to
cdf44e5
Compare
It's currently not possible to have different directories for the persistent state and the log files.
The
--directory
option is the only way to specify the directory for all state. Inside this dir, VAST creates a directory log that contains all ASCII logs.This PR adds a new option named
--log-directory
that optionally allows setting the directory for the logs only.