mirror of
https://github.com/iSharkFly-Docs/opensearch-docs-cn
synced 2025-03-08 10:12:26 +00:00
* Add refresh, flush, clear cache, and notifications documentation for index management in Dashboards Signed-off-by: Fanit Kolchina <kolchfa@amazon.com> * Tech review comment Signed-off-by: Fanit Kolchina <kolchfa@amazon.com> * Implemented tech review comments Signed-off-by: Fanit Kolchina <kolchfa@amazon.com> * Apply suggestions from code review Co-authored-by: suzhou <suzhou@amazon.com> Signed-off-by: kolchfa-aws <105444904+kolchfa-aws@users.noreply.github.com> * Updated images Signed-off-by: Fanit Kolchina <kolchfa@amazon.com> * Formatting change Signed-off-by: Fanit Kolchina <kolchfa@amazon.com> * Implemented tech review comments Signed-off-by: Fanit Kolchina <kolchfa@amazon.com> * Apply suggestions from code review Co-authored-by: Melissa Vagi <vagimeli@amazon.com> Signed-off-by: kolchfa-aws <105444904+kolchfa-aws@users.noreply.github.com> * Even spacing Signed-off-by: Fanit Kolchina <kolchfa@amazon.com> * Apply suggestions from code review Co-authored-by: Nathan Bower <nbower@amazon.com> Signed-off-by: kolchfa-aws <105444904+kolchfa-aws@users.noreply.github.com> * Implemented editorial comments Signed-off-by: Fanit Kolchina <kolchfa@amazon.com> --------- Signed-off-by: Fanit Kolchina <kolchfa@amazon.com> Signed-off-by: kolchfa-aws <105444904+kolchfa-aws@users.noreply.github.com> Co-authored-by: suzhou <suzhou@amazon.com> Co-authored-by: Melissa Vagi <vagimeli@amazon.com> Co-authored-by: Nathan Bower <nbower@amazon.com>
115 lines
4.5 KiB
Markdown
115 lines
4.5 KiB
Markdown
---
|
|
layout: default
|
|
title: Data streams
|
|
parent: Index management in Dashboards
|
|
nav_order: 20
|
|
redirect_from:
|
|
- /dashboards/admin-ui-index/datastream/
|
|
- /opensearch/data-streams/
|
|
---
|
|
|
|
# Data streams
|
|
Introduced 2.6
|
|
{: .label .label-purple }
|
|
|
|
In OpenSearch Dashboards, the **Index Management** application allows you to view and manage [data streams]({{site.url}}{{site.baseurl}}/im-plugin/data-streams/) as shown in the following image.
|
|
|
|

|
|
|
|
## Viewing a data stream
|
|
|
|
To view a data stream and its health status, choose **Data streams** under **Index management** as shown in the following image.
|
|
|
|

|
|
|
|
The following are the three data stream health statuses:
|
|
|
|
- Green: All primary and replica shards are assigned.
|
|
- Yellow: At least one replica shard is not assigned.
|
|
- Red: At least one primary shard is not assigned.
|
|
|
|
## Creating a data stream
|
|
|
|
To create a data stream, perform the following steps:
|
|
|
|
1. Under **Index Management**, choose **Data streams**.
|
|
|
|
1. Choose **Create data stream**.
|
|
|
|
1. Enter a name for the data stream under **Data stream name**.
|
|
|
|
1. Ensure that you have a matching index template. This will be populated under **Matching index template**, as shown in the following image.
|
|
|
|

|
|
|
|
1. The **Inherited settings from template** and **Index alias** sections are read-only, and display the backing indexes that are contained in the data stream.
|
|
|
|
1. The number of primary shards, number of replicas, and the refresh interval are inherited from the template, as shown in the following image.
|
|
|
|

|
|
|
|
1. Choose **Create data stream**.
|
|
|
|
## Deleting a data stream
|
|
|
|
To delete a data stream, perform the following steps:
|
|
|
|
1. Under **Index Management**, choose **Data streams**.
|
|
|
|
1. Select the data stream that you want to delete.
|
|
|
|
1. Choose **Actions**, and then choose **Delete**.
|
|
|
|
## Rolling over a data stream
|
|
|
|
To perform a rollover operation on a data stream, perform the following steps:
|
|
|
|
1. Under **Index Management**, choose **Data streams**.
|
|
|
|
1. Choose **Actions**, and then choose **Roll over**, as shown in the following image.
|
|
|
|

|
|
|
|
1. Under **Configure source**, select the source data stream on which you want to perform the rollover operation.
|
|
|
|
1. Choose **Roll over**, as shown in the following image.
|
|
|
|

|
|
|
|
## Force merging data streams
|
|
|
|
To perform a force merge operation on two or more indexes, perform the following steps:
|
|
|
|
1. Under **Index Management**, choose **Data streams**.
|
|
|
|
1. Select the data streams on which you want to perform the force merge operation.
|
|
|
|
1. Choose **Actions**, and then choose **Force merge**.
|
|
|
|
1. Under **Configure source index**, specify the data streams you want to force merge.
|
|
|
|
1. Optionally, under **Advanced settings** you can to choose to **Flush indices** or **Only expunge delete** and then specify the **Max number of segments** to merge to as shown in the following image.
|
|
|
|

|
|
|
|
## Refreshing a data stream
|
|
|
|
Refreshing a data stream makes new updates to the index visible to search operations.
|
|
|
|
The refresh operation can be applied only to open indexes associated with the specified data streams.
|
|
|
|
To refresh a data stream, select the data stream from the **Data streams** list under **Index Management**. Then select **Refresh** from the **Actions** dropdown list.
|
|
|
|
## Flushing a data stream
|
|
|
|
The flush operation performs a Lucene commit, writing segments to disk and starting a new translog.
|
|
|
|
The flush operation can be applied only to open indexes associated with the specified data streams.
|
|
|
|
To flush a data stream, select the data stream from the **Data streams** list under **Index Management**. Then select **Flush** from the **Actions** dropdown list.
|
|
|
|
## Clearing a data stream cache
|
|
|
|
The [clear cache operation]({{site.url}}{{site.baseurl}}/api-reference/index-apis/clear-index-cache/) can be applied only to open indexes associated with the specified data streams.
|
|
|
|
To clear a data stream cache, select the index from the **Indices** list under **Index Management**. Then select **Clear cache** from the **Actions** dropdown list. |