Search for a command to run...
A DevOps/Cloud Architect experienced with building and automating DevOps processes and tools for engineering teams encompassing cloud-native applications. Extensive background experience working with AWS and Microsoft Azure cloud services building hands-on robust and scalable solutions and services.
No comments yet. Be the first to comment.
The Evolution of DevOps - The Golden Age Let's wind the clock back a couple of decades to the late 90s and early 2000s, a time when most organisations had a single gatekeeper: the system or IT administrator. If engineering teams needed to run their a...
This guide presents a comprehensive set of rules for software engineering inspired by the movie Zombieland. The rules are not simply a list of arbitrary guidelines, but rather a carefully crafted set of principles that are designed to promote efficie...
Organisations today are increasingly adopting cloud services from different providers to meet their business needs. However, managing multi-cloud infrastructure can be challenging, especially when it comes to infrastructure management, which is where...
What is AWS CloudFront? AWS CloudFront is a content delivery network (CDN). It securely delivers data, videos, applications, and APIs to customers globally with low latency and high transfer speeds. It offers a simple and cost-effective way to distri...
DevOps is more than just a software development methodology – it's a culture. The DevOps culture emphasizes 3 main pillars: collaboration, communication, and shared responsibility between development and operations teams. In this post, we will discus...
Index aliasing is a powerful feature in Elasticsearch that gives us the ability to control the indices. One could create as many indices as possible and use an alias to point to the right index or one can point the index alias to all indices, depending on your application needs.
Imagine if you had the following scenarios when working with Elasticsearch for your application needs:
Scenario 1: A snapshot of your index that needs to be restored to a new cluster, however, you forgot to restore it, and instead, you created a new index. As time passed, you realised that new data had amassed in the newly created index and you needed to combine the data from the snapshot with the new index.
Scenario 2: You have an index that requires certain schema changes or re-indexing. To be able to ensure your users can search from your instance with almost no downtime, set up a new index with new schema changes and re-index the data.
Introducing multi-index aliasing. You can create a single index alias that points to multiple indices. There's an endpoint from Elasticsearch that allows you to perform one or more alias actions in a single atomic operation.
Verify if the alias you'd like to use has not been used yet by using the _alias/alias-name endpoint - HEAD _alias/my-alias
If it returns a 404, it means the alias is available and can be used in setting up the multi-index aliasing
If it returns a 200, it means it's being used and you need to choose another alias
Verify your indices are readily available within your cluster/instance.
Ensure that your old snapshot is ready (if you don't have your secondary index setup).
When you do restore the snapshot index, ensure that the index name is different than the newly created one to avoid conflicts.
Run the following POST request to your designated cluster:
POST /_aliases
{
"actions": [
{
"add": {
"index": "new_index",
"alias": "new_index_alias"
}
},
{
"add": {
"index": "old_index",
"alias": "new_index_alias"
}
}
]
}
You can pass in the **is_write_index** parameter in the payload as follows:
POST /_aliases
{
"actions": [
{
"add": {
"index": "new_index",
"alias": "new_index_alias",
**"is_write_index": true**
}
},
{
"add": {
"index": "old_index",
"alias": "new_index_alias"
}
}
]
}
As you can see, it's fairly straightforward to set up an index alias that points to multiple indices within your Elasticsearch instance.
If you want to query data from the alias, simply perform the following:
GET /new_index_alias/_search
This would help you query across two indices **new_index** and **old_index**.
Zero downtime: Bring up a new index with new changes, and point the alias to the new index when it's ready. Keep the old index stale, in case it's needed for future reference or just as a backup.
Multiple Indices: We want to be able to query multiple indices? Then create an alias that points to multiple indices.