Known issues on GCP

Files left in cloud storage

ElasticBLAST uses cloud storage to temporarily store query sequences and internal logs and metadata so that they are easily accessible during its operation. Sometimes deleting these files after the search is not successful. To double check and delete them, please run the commands below. ELB_RESULTS below represents the location where your results are stored.

gsutil ls gs://${ELB_RESULTS}/query_batches  # to list query files
gsutil -m rm gs://${ELB_RESULTS}/query_batches/*  # to delete query files

gsutil ls gs://${ELB_RESULTS}/logs  # to list log files
gsutil -m rm gs://${ELB_RESULTS}/logs/*  # to delete log files

gsutil ls gs://${ELB_RESULTS}/metadata  # list metadata files
gsutil -m rm gs://${ELB_RESULTS}/logs/*  # to delete metadata files

Too many query batches leads to failed execution

ElasticBLAST divides query sequences into batches and searches them in parallel. The Batch length parameter controls the size of a single batch. If the ElasticBLAST configuration leads to more than 5,000 query batches, ElasticBLAST will exit with an error message prompting you to increase Batch length parameter to decrease the number of query batches.

blast-tuner application requires csp-target

If the --csp-target parameter is not specified to blast-tuner.py, an error message will be displayed. Please always use –csp-target parameter and specify the appropriate cloud service provider to prevent this error.

This issue will be addressed in an upcoming release of ElasticBLAST.