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

edison realtime queue 25 nodes #650

Merged
merged 1 commit into from Jun 29, 2018
Merged

edison realtime queue 25 nodes #650

merged 1 commit into from Jun 29, 2018

Conversation

sbailey
Copy link
Contributor

@sbailey sbailey commented Jun 29, 2018

This PR updates the edison realtime queue config to be 25 nodes instead of the previous 10. This is needed for testing of the data transfer -> spectro pipeline.

@tskisner and/or @weaverba137 may have already done this in a separate branch, in which case they can close this PR.

Note: the testing will need this PR or equivalent, but it doesn't require the latest desiconda which isn't installed on edison yet.

@sbailey sbailey requested a review from tskisner June 29, 2018 17:03
@tskisner
Copy link
Member

Hi @sbailey, this change looks fine to me, thanks for updating the max nodes for the realtime queue.

@weaverba137
Copy link
Member

weaverba137 commented Jun 29, 2018 via email

@weaverba137
Copy link
Member

To clarify, you're saying that desi_night update ... --nersc edison --nersc_queue realtime --nersc_maxnodes 25 is invalid because the number of nodes was hardcoded?

@tskisner
Copy link
Member

The command line option for --nersc_maxnodes is a way of restricting the number to be something smaller than the "hard" maximum, which is set by NERSC for each queue. The realtime queue is sort of a special case, since NERSC can change that for us. This PR changes that "hard" maximum to be what NERSC has recently configured for us

@weaverba137
Copy link
Member

Well, then it sounds like the realtime parameters shouldn't be hardcoded at all!

@tskisner
Copy link
Member

In practice, once we are set up for actual operations, that number will be fixed. It is only in these early days that it is changing. This hardcoded maximum is the fallback value if --nersc_maxnodes is not specified. This number is set for each queue, in order to relieve the user of knowing the details about the particular NERSC queue limits.

@weaverba137
Copy link
Member

OK, let's get this in, because I'll have to merge it with my dts-scripts branch.

@sbailey sbailey merged commit eca0d68 into master Jun 29, 2018
@sbailey sbailey deleted the realtimequeue branch June 29, 2018 18:58
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

Successfully merging this pull request may close these issues.

None yet

3 participants