increase object store (jwd05e) weight #1362
Closed
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.
It seems that a few jobs using
jwd02f
are getting stuck in theD
state.I see all the
query_tabular
jobs (from the micro galaxy hackathon) are usingjwd02f
, and they are stuck. Each of them is running on different compute nodes, and I also see several other jobs stuck in the D state that are also utilizing the same JWD NFS share (running on the same compute nodes as the others). It could be an NFS issue.This is a temporary fix to shift the load to
jwd05e
.jwd02f
is still active, though. I also see some jobs utilizingjwd02f
running.@bgruening: Feel free to close this PR if you don't think this is ideal.