-
Notifications
You must be signed in to change notification settings - Fork 34
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
Scheduler instance boot failure #85
Comments
The other version of this error message is here:
|
Might be related to boto/boto3#1592 as I think we're using session objects across threads. |
Message today
|
Perhaps related, but when trying to load ~96K accessions in to the scheduler I get the following error (happened on 3x attempts). Reducing input to 20K per batch now.
|
So while I was booting today it appears that the credentials error arises when you run the The adding 90K accessions at once issue is semi-resolved as I just add 20K 'batch' of accessions. So far I have 60K loaded into the scheduler and nothing has blown up. |
I don't remember which commit closed this, but it is no longer an issue. |
When running
Serratus
viaterraform apply
, all the initial instances are going online and about 20% of the time thescheduler
runs into a problem with what appears to beaws credentials
(IAM is attached correctly) and therefore the cluster has to be restarted. This only happens at initiation so it's easy to fix but kind of annoyingCloudwatch logs
The text was updated successfully, but these errors were encountered: