Releases: ncbi/elastic-blast
Releases · ncbi/elastic-blast
1.3.1
1.3.0
Improvements:
- Upgrade to BLAST+ 2.16.0, including runtime improvements to blastp, blastx, and psiblast
Bug fixes:
- Better tracking of cloud resource IDs to facilitate resource clean up in case of errors
- Use specified AWS region when getting available instance types
1.2.0
Improvements:
- Upgrade to BLAST+ 2.15.0, including improved performance for taxonomy limited searches and automatic selection of threading model
- Automatically select client vs. cloud query splitting based on query file size
- Support for kubernetes versions 1.26 and greater
- New ElasticBLAST batch lengths for threading by query
Bug fixes:
- Fixed bug that led to timeouts in GCP waiting for the persistent volume claim (PVC) to bind
- Improve error message if -entrez_query option is given
1.1.0
Improvements:
- Default batch sizes for blastn and dc-megablast lead to improved runtimes
- Improve AWS quota check based on the number of vCPUs per instance
- Improved logging of dependent tools
Bug fixes:
- Fixed AWS API calls to select instances on all AWS regions
1.0.0
Note to ElasticBLAST users on GCP
ElasticBLAST versions prior to 1.0.0 will stop working after January 31, 2023 because they rely on version 1.21 of kubernetes, which will reach its end of life on the Google Kubernetes Engine on that date. Please upgrade your installation of ElasticBLAST to its latest version.
Improvements:
- ElasticBLAST on AWS now defaults to the faster and cheaper EBS gp3 disk type
- ElasticBLAST on GCP now supports all of the versions of kubernetes offered by Google Kubernetes Engine
- ElasticBLAST on GCP defaults to the stable version of kubernetes offered by Google Kubernetes Engine
Bug fixes:
- ElasticBLAST uses GCP's recommended way of dealing with read/write persistent disk
- Long user names no longer cause errors in AWS
- Fixed error caused by APIs not being enabled in GCP
0.2.7
0.2.6
New features:
- A new config parameter
cloud-providers/gke-version
to select Google Kubernetes Engine version, defaults to 1.21
Improvements:
- GCP project config parameter is now optional. If missing elastic-blast will use
CLOUDSDK_CORE_PROJECT
environment variable or the default GCP project set ingcloud
config. - GCP zone config parameter now defaults to
us-east4-b
- Improved error message when persistent disk size exceeds user’s quota
Bug fixes:
- Fixed a persistent disk problem in GCP
- Invalid janitor schedule string does not cause resource leak and is properly reported