Sets the mulled resolution cache lock dir to local #402
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
On the current deployment, it created it on its own, but it was just a single level directory. I will restart my deployment with this path to confirm that the behaviour is recursive. |
|
I can confirm that the directories requested get created by some process without the helm chart having to take care of it. |
nuwang
approved these changes
Jan 6, 2023
|
Thanks @pcm32! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The mulled cache lock dir is often accessed and it doesn't need to be on the shared file system. Then each galaxy process that needs it will have it's own and performance on local disk should be better than on the shared file system.
Helps with #399 .