> For the complete documentation index, see [llms.txt](https://docs.pentaho.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.pentaho.com/install/10.2-install/use-hadoop-with-pentaho/big-data-issues/legacy-mode-activated-if-named-cluster-configuration-cannot-be-located.md).

# Legacy mode activated when named cluster configuration cannot be located

If you run a transformation or job for which PDI cannot locate and load a named configuration cluster, then PDI activates a legacy mode. This legacy, or fallback, mode is only available in Pentaho 9.0 and later.

When the legacy mode is activated, PDI attempts to run the transformation by finding any existing cluster configuration you have set up in the PDI Big Data plugin. PDI then migrates the existing configuration to the latest PDI instance that you are currently running.

**Note:** You cannot connect to more than one cluster.

The legacy mode is helpful for transformations built with previous versions of PDI and includes individual steps that are not associated to a named cluster. You can run the transformation in legacy mode without revising the cluster configuration in each individual step. For information about setting up a named connection, see the **Pentaho Data Integration** document.

When legacy mode is active, the transformation log displays the following message:

`Could not find cluster configuration file {0} for cluster {1} in expected metastore locations or a legacy shim configuration.`

If the Big Data plugin is present and PDI accesses it to successfully activate legacy mode, the transfomation log displays the following message:

`Cluster configuration not found in expected location; trying legacy configuration location.`

For more information about working with clusters, see [Get started with Hadoop and PDI](/install/10.2-install/use-hadoop-with-pentaho/get-started-with-hadoop-and-pdi.md).


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.pentaho.com/install/10.2-install/use-hadoop-with-pentaho/big-data-issues/legacy-mode-activated-if-named-cluster-configuration-cannot-be-located.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.