Bulk Operations

Cumulus implements bulk operations through the use of AsyncOperations, which are long-running processes executed on an AWS ECS cluster.

Submitting a bulk API request

Bulk operations are generally submitted via the endpoint for the relevant data type, e.g. granules. For a list of supported API requests, refer to the Cumulus API documentation. Bulk operations are denoted with the keyword 'bulk'.

Starting bulk operations from the Cumulus dashboard

Using a Kibana query

caution

You must have configured your dashboard build with a KIBANAROOT environment variable in order for the Kibana link to render in the bulk granules modal.

1. From the Granules dashboard page, click on the "Run Bulk Granules" button, then select what type of action you would like to perform.

note

The rest of the process is the same regardless of what type of bulk action you perform.

2. From the bulk granules modal, click the "Open Kibana" link:

   

3. Once you have accessed Kibana, navigate to the "Discover" page. If this is your first time using Kibana, you may see a message like this at the top of the page:

   In order to visualize and explore data in Kibana, you'll need to create an index pattern to retrieve data from Elasticsearch.

   In that case, see the docs for creating an index pattern for Kibana

   

4. Enter a query that returns the granule records that you want to use for bulk operations:

   

5. Once the Kibana query is returning the results you want, click the "Inspect" link near the top of the page. A slide out tab with request details will appear on the right side of the page:

   

6. In the slide out tab that appears on the right side of the page, click the "Request" link near the top and scroll down until you see the query property:

   

7. Highlight and copy the query contents from Kibana. Go back to the Cumulus dashboard and paste the query contents from Kibana inside of the query property in the bulk granules request payload. It is expected that you should have a property of query nested inside of the existing query property:

   

8. Add values for the index and workflowName to the bulk granules request payload. The value for index will vary based on your Elasticsearch setup, but it is good to target an index specifically for granule data if possible:

   

9. Click the "Run Bulk Operations" button. You should see a confirmation message, including an ID for the async operation that was started to handle your bulk action. You can track the status of this async operation on the Operations dashboard page, which can be visited by clicking the "Go To Operations" button:

   ![Screenshot of Cumulus dashboard showing confirmation message with async operation ID for bulk granules request](../assets/bulk-granules-submitted.png)

Creating an index pattern for Kibana

1. Define the index pattern for the indices that your Kibana queries should use. A wildcard character, *, will match across multiple indices. Once you are satisfied with your index pattern, click the "Next step" button:

   

2. Choose whether to use a Time Filter for your data, which is not required. Then click the "Create index pattern" button:

   ![Screenshot of Kibana user interface for configuring the settings of an index pattern](../assets/kibana-create-index-pattern-2.png)

Status Tracking

All bulk operations return an AsyncOperationId which can be submitted to the /asyncOperations endpoint.

The /asyncOperations endpoint allows listing of AsyncOperation records as well as record retrieval for individual records, which will contain the status. The Cumulus API documentation shows sample requests for these actions.

The Cumulus Dashboard also includes an Operations monitoring page, where operations and their status are visible: