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

Split PV, one for Postgres and for Galaxy Data #23

Open
sneumann opened this issue Jun 18, 2018 · 1 comment
Open

Split PV, one for Postgres and for Galaxy Data #23

sneumann opened this issue Jun 18, 2018 · 1 comment

Comments

@sneumann
Copy link
Member

Hi, before tackling #22 I'd like to work on splitting the PV into
one for Postgres /var/lib/ and one for /export Galaxy data.
Then we can also try to apply fixes found in these comments, updated in 2018:

https://bugzilla.redhat.com/show_bug.cgi?id=1512691
https://bugzilla.redhat.com/show_bug.cgi?id=1518710

Additional info: When the following volume options are turned off the benchmark runs smoothly without errors and delivers the expected output above.
  performance.open-behind: off
  performance.write-behind: off
@andersla
Copy link
Contributor

@sneumann Should I add only those two performance options on the gluster-disk.
I think It is a good idéa to put those as default on all gluster PVs? Or?

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

No branches or pull requests

2 participants