> For the complete documentation index, see [llms.txt](https://docs.digit.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.digit.org/works/reference-implementations/muktasoft-v2.2/deployment/configuration/dashboard-reindexing.md).

# Dashboard Reindexing

## Overview

Dashboard reindexing is a way to refresh and update both wage bill and muster roll indices once the "gender" field is added to the additional details of an individual. The following sections explain how to do this.

## Reindex Elastic Search Indices - Steps

1. In Elasticsearch, back up the original index and create a new migrate index.
2. Define a new migrate topic in the indexer and link it to the migrate index.
3. Ensure you have Python3 installed on your local system.
4. Start a Kafka client and set up port forwarding for Elasticsearch, pointing Kafka bootstrap servers to the Elasticsearch port (usually localhost:9200).
5. Launch an indexer service using indexer files.
6. Retrieve data from services via API, either in bulk or individual search.
7. Formulate an insert request for the indexer, whether for bulk or single data.
8. Send the insert request to the migrate topic.
9. Verify the data in the migrate index.
10. Delete the original index, create a new one, and transfer data from the migrate index to the new original index.

These steps help you update and manage Elasticsearch indices effectively.

## Services To Reindex

* expense-bill-index
* muster-inbox

## Reindexing Scripts

Refer to [Reindex](https://github.com/odisha-muktasoft/MUKTA_IMPL/tree/UAT/utilities/reindex) and run the migrate scripts using python3.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.digit.org/works/reference-implementations/muktasoft-v2.2/deployment/configuration/dashboard-reindexing.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.