Hot and Cold Data Storage
CSS provides you with cold data nodes. You can store data that requires query response in seconds on high-performance nodes and store data that requires query response in minutes on cold data nodes with large capacity and low specifications.
- When creating a cluster, you need to configure nodes as data nodes. Only after you select the cold data node, data nodes become hot nodes.
- You can select the cold data node, master node, and client node at the same time.
- You can increase nodes and expand storage capacity of cold data nodes. The maximum storage capacity is determined by the node specifications. Local disks do not support storage capacity expansion.
Hot and Cold Data Node Switchover
After you enable the cold data node function, the cold data node is labeled with cold. In addition, data nodes are labeled with hot and become hot nodes. You can specify index to distribute data to the cold or hot nodes.
You can configure a template to store index to the specified cold or hot node.
The following figure shows this process. Log in to the Kibana Console page of the cluster, modify the template by configuring the index starting with myindex, and store the indice on the cold node. In this case, the myindex* date is stored on the cold data node by modifying the template.
PUT _template/test
{
"order": 1,
"template": "myindex*",
"settings": {
"index": {
"refresh_interval": "30s",
"number_of_shards": "3",
"number_of_replicas": "1",
"routing.allocation.require.box_type": "cold"
}
}
}
You can also perform operations on the created index.
PUT myindex/_settings
{
"index.routing.allocation.require.box_type": "cold"
}
You can also cancel the configurations of hot and cold data nodes.
PUT myindex/_settings
{
"index.routing.allocation.require.box_type": null
}
Last Article: Managing Plugins
Next Article: Configuring Parameters
Did this article solve your problem?
Thank you for your score!Your feedback would help us improve the website.